Use different trunks for same digits dialled

[eugenej]

So I'm in the planning phase for a big project.

I need phones to use different routes/trunks depending on their location when dialing the same number. Example phone A dials 9087xxxxxxx and it uses a particular trunk/route. Phone B dials the same number, 9087xxxxxxx but it now needs to use a different trunk/route.

Now how I would normally do this is to use route lists with COR numbers - I think most of you understand this method (I'll explain/elaborate if needed)
This method though won't work for me (I think) in this scenario simply because I'd need almost 70 different routes since there are almost 70 different locations (geo) that I need to cater for.

There will be a single MiVB system hosting almost 3000 users and they are split over 70 odd countries each with their own unique local breakout (non-Mitel gateways) that will be connected via SIP to the MiVB.

Any suggestions and ideas are highly appreciated

[ralph]

OK. This might take me a bit to explain.
There's probably an easier way to do this.  I tend to overthink things.
I'll base this example on the NPA dialing plan since I don't know the South African dial plan.

1: Create a loop back trunk.
2: program an ARS route that uses that trunk group.  Set up the Digit mod to absorb 1 and insert the extensions account code "<a>".
example account code: 9999
3: Set up your outbound ARS to use 9999+1+10 digits.  Absorb 4 digits.  Do this for each outbound trunk group you need.  Use different ARS access codes. 9999, 9998,9997, etc.
4: assign default account codes to each phone.  The account code will need to match whatever ARS trunk group they need to use.
5: How it works: 
a: when the user dials 9 the call is routed through the loopback trunk group.
b: the digit mod table absorbs the 9 and inserts the account code.
c: The system now sees the call as 9999+<11 digits>
d: The call is now routed out the trunk group based on ARS digits dialed.  9999+<11 digits> is now routed out the trunk group you need it to.

Ralph





 

[eugenej]

Ralph,

I see what you are trying to do and the logic applied is precisely what I'd need.
Question: what type of loopback are you referring to?

[ralph]

A loop back trunk is an XNET trunk that connects to the same PBX it originates from.

Ralph

[eugenej]

A loop back trunk is an XNET trunk that connects to the same PBX it originates from.

Ralph

Have done plenty ISDN loopback and analogue but never IP. Will give this a go. I assume sine it is XNET it will have the 200 call limit?

[ralph]

A loop back trunk is an XNET trunk that connects to the same PBX it originates from.

Ralph

Have done plenty ISDN loopback and analogue but never IP. Will give this a go. I assume sine it is XNET it will have the 200 call limit?

I've never tried to go beyond the 200 limit but I can't see why it wouldn't go further.

Ralph

[v2win]

What about tenanting?

[martyn]

I would use intercepts and tenanting to block out trunks.

[johnp]

I think it could also be done with location based numbering

[eugenej]

I'm busy working on a ARS plan with the loopback option and def account codes.

I would use intercepts and tenanting to block out trunks.

Not sure this will work for me. Perhaps elaborate if you don't mind.

I think it could also be done with location based numbering

First place I checked. Problem is LBN can only be up to 7 or 9 digits long. I'm not sure I can cover all my ARS entries with this. This is mostly for service type numbers which are generally pretty short. I'll relook this option at some point

Thanks all for the repllies..

[johnp]

My thought was if you add the leading digit to location based, ars would then consist of location inserted numbers and cluster digits

[eugenej]

My thought was if you add the leading digit to location based, ars would then consist of location inserted numbers and cluster digits

Not a terrible notion by any means Will per sue it from the angle you described and see what it does.
I haven't used LBN yet so I don't know how flexible or inflexible it is; have just looked at the help files. I'm looking into all possibilities.