Session Manager routing of calls

[steve64]

We currently have system/session Manger along with our CS1000Es and CS1000M MGs. Internal calls route properly as do calls to local PSTN numbers. Long distance numbers also route to the desired number, but the CLID does not show up correctly on the distant end. Checking the D channel monitoring the calls are leaving the CS1000E with the proper call type, E164/National. The problem is that when the call arrives at the CS1000M, where or PSTN trunks live, the Session manager has changed the call type to "Unknown/Unknown". This being the case when the telco sends the call out they either send out our billing number, you can't call that number, or no number. The called party CLID displays the errounus number or no number. Local numbers to the PSTN work properly. I have experimented with the adaptations and added the "+" in front of the number but when you do this the number increases to 13 digits and now when looking at the MSGI on the 1000M it shows E164/International. I believe this is due to the 13 digits and is somewaht supported by what is in the Avaya docs. Dialing string: 9 1 xxx-xxx-xxxx, the 9 is stripped but a new 9 is inserted by the DMI table so the number shows up at the session manager as 9 1 xxx-xxx-xxxx. It also arrives at the CS1000M in this format. It's just that the call type has changed.
Anyone have any ideas on how to fix this?

 

[rumelihavasi]

Similar things happend to me. But not with session manager. We had 2 cs1000 and were calling each other via SIP.
Compare PNI and VPNI numbers on both sides and equalize them. It may help you to fix the problem.

Regards,

 

[steve64]

PNI and VPNI are set the same. The issue seems to be that the Session Manager will not pass the calling number or called number types. They just send them as UNKNOWN/UNKNOWN(UNKNOWN). The CS1000M that has the PSTN trunks is smart enough that it corrects the called number type to E164/NATIONAL/ NPA but doesn't correct the calling number type.

 

[bignose21]

I pretty much do nothing to the traffic as it goes through the session manager and it seems to maintain its TON the adaptation I use is:

Inbound
Matching Pattern min max phone context delete digits insert digits address to modify
* 1 36 public 0 both

Outbound
Matching Pattern min max phone context delete digits insert digits address to modify
* 1 36 public 0 both

We would route calls at this with just the country code onwards with a type of international.