Session Manager question - regarding how CM routes calls received from SM

[heathersuzanne]

Hi Everyone,

I have a global phone system - the main call processor is in the US (along with other shared components like voicemail and session manager). All other sites globally are LSPs off of the US main processor.

Lets say Session Manager receives a request from an associate in Brazil to route a call from their Microsoft Office Communicator (which is integrated w/ Avaya) across the PSTN. Session Manager can do so, however Session Manager sends the call to CM in E.164 format and then the CM routes the call out over the US trunks. The US should not have to pay for a call that is being made by an associate in Brazil...Id like the call to route over the trunks in Brazil.

Anyone have any good documentation on how I can set up CM to intercept the call and then route it out the trunks that I choose? Thanks!!

HSE

 

[kyle555]

What kind of Communicator/Lync integration are you using? What does that call flow look like?

 

[heathersuzanne]

Hi Kyle555,

The call flow for this particular example is as follows:

MOC user in Brazil calls external phone number (lets say +32xxx in Belgium)
The phone nubmer is sent to Avaya's Session Manager server (US based) via SIP trunk in E.164 format.
SIP server translates the number to the necessary format via Adaptation Rule (as you know, E.164 is not enough to route a call through Avaya...it may need digit manipulation to route correcly, which we have happening)
So now, CM is ready to send 901132xxx. Remember the CM and Session Manager are centralized in the US and Brazil is just an LSP off that...so the CM routes the call via the loacation-based ARS rules for the US. The call completes.

But I wanted the call to route over the Brazil trunks because someone in Brazil is actually making the call.

Any way you know of to allow me to route over the appropriate trunks given the scenario where we only have one CM and one SM?

This is just one eample of a routing issue caused by this consolidated global PBX Config - I also have this issue with the Aura Messaging Server's Reach Me Feature. Every time one of our customers activates this feature, calls route over the Us trunks instead of the trunks at the callers home location.

Thanks!



HSE

 

[kyle555]

Short answer is you'd need to find a way to segregate that traffic. Maybe different Lync trunks to SM on different ports or with different domains - br.yourco.com, usa.yourco.com, etc

Once you can use some more elements of dial plan routing in SM, like originating location or domain, then you'll be able to treat the same strings from different users on the other side of Lync differently.[ul]