PRI to SIP traffic move caused issues with EC500 and "Route To" statements

[Mark G]

Hi,
Over the weekend we moved traffic from a PRI to SIP trunks. Well, it worked fine except that we have 2 issues.

1) EC500 Calls do not go out. On the SBC trace we get an error of "400 Bad Request". We are unclear why.

2) Certain "route to" statements seem to be affected.

For now, we moved things back to outbound PRI and EC500 as well as "route to" statements are working again. We really need to resolve the EC500 and "route to" issues.

Any thoughts?

Thanks!

 

[7deedtz]

Hi,

Please advise CM version, Configurations, what versions? DO you have SBC, SM so we may fully understand your problem?

 

[Mark G]

CM 6.3.3 and we do have an SBC and Session Manager. EC500 failed trace shows as:

LIST TRACE

time data

13:25:16 TRACE STARTED 02/03/2020 CM Release String cold-03.0.141.0-24403
13:25:24 SIP<INVITE sip:XXXX@sip SIP/2.0
13:25:24 Call-ID: ec82797a1a0d165e0c4576510af5a954
13:25:24 SIP>SIP/2.0 180 Ringing
13:25:24 Call-ID: ec82797a1a0d165e0c4576510af5a954
13:25:24 Calling party trunk-group 97 member 63 cid 0x18f5
13:25:24 Calling Number & Name XXXXXXXXXX Doe, John
13:25:24 dial XXXX
13:25:24 ring station XXXX cid 0x18f5
13:25:24 G711MU ssff ps:20
rgn:1 [X.X.X.X]:20636
rgn:1 [X.X.X.X]:2334
13:25:24 G711MU ssff ps:20
rgn:1 [X.X.X.X]:36866
rgn:1 [X.X.X.X]:2142

LIST TRACE

time data
13:25:24 xoip options: fax:Relay modemT ttyff uid:0x507ed
xoip ip: [X.X.X.X]:2142
13:25:24 dial XXXXXXXXXX
13:25:24 seize trunk-group 97 member 35 cid 0x18f6
13:25:24 Calling Number & Name XXXXXXXXXX Doe, John
13:25:24 SIP>INVITE sip:XXXXXXXXXX@sip SIP/2.0
13:25:24 Call-ID: 07a4873e453ea1471c5d155d700
13:25:24 Setup digits XXXXXXXXXX
13:25:24 Calling Number & Name XXXXXXXXXX Doe, John
13:25:24 SIP<SIP/2.0 100 Trying
13:25:24 Call-ID: 07a4873e453ea1471c5d155d700
13:25:24 Proceed trunk-group 97 member 35 cid 0x18f6
13:25:24 SIP<PRACK sip:+XXXXXXXXXX@X.X.X.X;transport=tcp SIP/2
13:25:24 SIP<.0
13:25:24 Call-ID: ec82797a1a0d165e0c4576510af5a954
13:25:24 SIP>SIP/2.0 200 OK
LIST TRACE

time data
13:25:24 Call-ID: ec82797a1a0d165e0c4576510af5a954
13:25:24 SIP<SIP/2.0 400 Bad Request
13:25:24 Call-ID: 07a4873e453ea1471c5d155d700
13:25:24 SIP>ACK sip:XXXXXXXXXX@sip SIP/2.0
13:25:24 Call-ID: 07a4873e453ea1471c5d155d700
13:25:24 denial event 1192: Temporary failure D1=0xe0011 D2=0x29
13:25:24 idle trunk-group 97 member 35 cid 0x18f6
13:25:39 SIP>SIP/2.0 181 Call Is Being Forwarded
13:25:39 Call-ID: ec82797a1a0d165e0c4576510af5a954
13:25:39 no answer station XXXX cid 0x18f5
13:25:39 coverage-path 100 point 1 cid 0x18f5
13:25:39 SIP>PUBLISH sip:+XXXXXXXXXX@sip:5062 SIP/2.0
13:25:39 Call-ID: 80886f7ae453ea1741c5d155d700
13:25:39 call-forwarding *603111
13:25:39 term trunk-group 100 cid 0x18f5
13:25:39 call-forwarding *603111

 

[kyle555]

you'd want to see it on a traceSBC to see what's going in and out. It's possible the carrier doesn't like the FROM or PAI being the calling party

 

[Mark G]

Thanks kyle555- The error I see via Wireshark is "SIP Syntax error". Any thoughts on what to look for next? Thanks.

 

[kyle555]

post a pcap