Session Manager Dial Patterns

[steve64]

We have a system/session manager running with cs1000Es and routing of calls works properly for internal CDP calls. We have recently just added SIP trunks to the telco and calls to NXXs and NPAs work fine. The problem is that if an international call, dial pattern 011, is placed the call fails to ever get through the session manager. In doing a traceSM in the session manager we see "Route not found". Our interface to the telco is an AudioCodes Mediant 3000 SBC. When looking at the SIP messaging on that device there are no SIP messages if the call was international. NPAs and NXXs are just fine incoming and out going. We have not been able to find any meaningful Avaya documentation that would explain this problem. When looking at the D channel messaging the call is tagged as E164 international so the CS1000e is sending it correctly. Also if we point the 011 dial pattern to one of our other PBXs with Long distance access via Pri circuits the calls go out without any problem. Anyone have experience on how this should be configured in the Session Manager? Avaya's answer as usual is we'll do it but it is billable. That seems to be their answer to everything.

 

[allenmac]

I don't have any SIP trunks to the carrier, but when I route international calls through Session Manager, I first strip off the 011 and mark the call as INTL, so what goes out the SIP D-Channel to session manager is the <Country Code><City Code><Telephone Number> in E.164 format.

The Session Manager sees this as: '+'<Country Code><City Code><Telephone Number>. I have a dial pattern of '+' configured with Min=7, Max=36 with appropriate Originating locations and Routing Policies configured to terminate the call.

I do not outpulse the '011' access code. All of my CS1000 systems have the CNTC and INTC codes configured so that they automatically recognize how to route the call and insert the appropriate access code prior to sending the call to the PSTN.