Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BSR222/BCM50RLS5/SIP trunk problems

Status
Not open for further replies.

RLSbutton

Technical User
Mar 2, 2010
712
US
Can anyone make anything out of these traces I received back from my 3rd party carrier when trying to make calls from an 1140e phone to SIP trunks? Again, I can make calls via the T7316 digital phones, but not 1140e. I need some help figuring out how to get the IP addressed of the phones to route the calls properly. My codecs are set up properly.

Here is an attached trace that I received from the SIP provider a month or so ago, see if there is anything helpful in here: (nV stands for Nexvortex, the 3rd party SIP carrier)

Beginning of Trace:

call from 13122615594 to 17738002600


we send an INVITE to your network

U 2010/05/10 03:16:52.294516 66.23.129.253:5060 -> 75.3.124.10:10052
INVITE sip:17738002600@75.3.124.10:10052;transport=UDP;transport=udp
SIP/2.0..Record-Route: [sip:17738002600@66.23.129.253:5060;
nat=yes;ftag=a9d5ed0-13c 4-4be77aa4-edda6cc-58c0dfbf;lr=on]..
From: [sip:13122615594@208.94.157.10:5060];tag=a9d5ed0-13c4-4be77a
a4-edda6cc-58c0dfbf..To: [sip:17738002600@66.23.129.253:5060]..
Call-ID: CXC-484-658498b0-a9d5ed0-13c4-4be77aa4-edda6cc-
127d6d19@208.94.157.10..CSeq: 1 INVITE..Via: SIP/2.0/UDP 66.23.129.253:5060;
branch=z9hG4bK1c7b.80d4b786.0..Via: SIP/2.0/UDP 208.94.157.10:5060;
branch=z9hG4bK-3fb92-4be77aa4-edda6cc-1b0 5a68c..
Max-Forwards: 16..Supported: 100rel..Remote-Party-ID:
[sip:13122615594@cxc.dashcs.com:5060];id-type=subscriber;pri vacy=off;screen=no..
Content-Disposition: session;handling=optional..Contact:
[sip:13122615594@208.94.157.10:5060;transport=udp]..
Min-SE: 900..Session-Expires: 1800..Content-Type: application/sdp..
Content-Length: 238....v=0..o=Acme_UAS 0 1 IN IP4 208.94.157.10..
s=SIP Media Capabilities..c=IN IP4 208.94.157.10..t=0 0..m=audio
21098 RTP/AVP 0 18 101..a=rtpmap:0 PCMU/8000..


U 2010/05/10 03:16:54.130022 75.3.124.10:10052 -> 66.23.129.253:5060
SIP/2.0 200 OK..From: [sip:13122615594@208.94.157.10:5060];
tag=a9d5ed0-13c4-4be77a a4-edda6cc-58c0dfbf..To: [sip:17738002600@66.23.129.253:5060];
tag=10902448-c0a80102-1 3c4-4be77ac0-40024148-4be77ac0..
Call-ID: CXC-484-658498b0-a9d5ed0-13c4-4be77aa4-edda6cc-127d6d19@208. 94.157.10..
CSeq: 1 INVITE..Via: SIP/2.0/UDP 66.23.129.253:5060;branch=z9hG4bK1c7b.80d4b786.0..
Via: SIP/2.0/UDP 208.94.157.10:5060;branch=z9hG4bK-3fb92-4be77aa4-edda6cc-1b0 5a68c..
Supported: 100rel,sipvc,x-nortel-sipvc,replaces..User-Agent: Nortel Networks BCM
VoIP Gateway release_45 version_45.25.0.33..x-nt-corr-id: CXC-484-658498b0-a9d5ed0-
13c4-4be77aa4-edda6cc-127d6d19@208. 94.157.10..Contact:
[sip:17738002600@75.3.124.10:10052;transport=udp;user=phone] ..
Record-Route: [sip:17738002600@66.23.129.253:5060;lr;nat=yes;ftag=a9d5ed0-
13c4-4be77aa4-edda6cc-58c0dfbf]..Allow: INVITE,UPDATE,INFO,ACK,OPTIONS,
CANCEL,BYE,NOTIFY,PRACK,REFER ..
Content-Type: application/SDP..Content-Length: 257....v=0..
o=- 1273461442 1273461442 IN IP4 75.3.124.10..s=-..
c=IN IP4 75.3.124.10..t=0 0..a=sqn:0.

your system sends a 200 OK

U 2010/05/10 03:16:54.222290 192.168.1.50:5060 -> 75.3.124.10:10052
ACK sip:17738002600@75.3.124.10:10052;transport=udp;
user=phone SIP/2.0..Record-Route: [sip:17738002600@66.23.129.253:5060;
nat=yes;ftag=a9d5ed0-13c 4-4be77aa4-edda6cc-58c0dfbf;lr=on]..From: [sip:13122615594@208.94.157.10:5060];tag=a9d5ed0-13c4-4be77a a4-edda6cc-58c0dfbf..
To: [sip:17738002600@66.23.129.253:5060];tag=10902448-c0a80102-1
3c4-4be77ac0-40024148-4be77ac0..Call-ID: CXC-484-658498b0-a9d5ed0-
13c4-4be77aa4-edda6cc-127d6d19@208. 94.157.10..CSeq:1 ACK..
Via: SIP/2.0/UDP 66.23.129.253:5060;branch=0..Via: SIP/2.0/UDP 208.94.157.10:5060;
branch=z9hG4bK-3fb9a-4be77aa6-eddae6e-25f 14ca7..Max-Forwards: 16..
Contact: [sip:13122615594@208.94.157.10:5060;transport=udp]..
Content- Length: 0....

we send an ACK that we got the 200 OK


it sends another INVITE but to 13122615594 the caller number and the carrier disconnects the call

U 2010/05/10 03:17:06.565116 75.3.124.10:10052 -> 66.23.129.253:5060
INVITE sip:13122615594@208.94.157.10:5060;transport=udp SIP/2.0..
From: [sip:17738002600@66.23.129.253:5060];tag=10902448-c0a80102-1
3c4-4be77ac0-40024148-4be77ac0..To: [sip:13122615594@208.94.157.10:5060];
tag=a9d5ed0-13c4-4be77a a4-edda6cc-58c0dfbf..Call-ID: CXC-484-658498b0-a9d5ed0-
13c4-4be77aa4-edda6cc-127d6d19@208. 94.157.10..CSeq: 2 INVITE..
Via: SIP/2.0/UDP 75.3.124.10:10052;branch=z9hG4bK-4be77ace-8037b803-40ef967..
Max-Forwards: 70..Supported: 100rel,sipvc,x-nortel-sipvc,replaces..
User-Agent: Nortel Networks BCM VoIP Gateway release_45 version_45.25.0.33..
x-nt-corr-id: CXC-484-658498b0-a9d5ed0-13c4-4be77aa4-edda6cc-127d6d19@208.94.157.10..
Contact: [sip:17738002600@75.3.124.10:10052;transport=udp;user=phone] ..
Route: [sip:17738002600@66.23.129.253:5060;lr;nat=yes;
ftag=a9d5ed0- 13c4-4be77aa4-edda6cc-58c0dfbf]..Allow:
INVITE,UPDATE,INFO,ACK,OPTIONS,CANCEL,BYE,NOTIFY,PRACK,REFER ..
Content-Type: application/SDP..Content-Length: 298....v=0..o=-
1273461442 1273461444 IN IP4 75.3.124.10..s=-..c=IN IP4 75.3.124.1051..t=0 0..
a=sqn:0..a=cdsc:1 im


What's the purpose of reINVITE to the caller 13122615594 , why would it attempt an outbound call to 13122615594 ?

What is the BCM trying to accomplish by sending a reINVITE to the caller number?

End of Trace

ALSO,


Here are some translations of those errors by a Nortel guy I know.

I took a look at your traces, here is my analysis.

- 1140E basic outbound: You're seeing a fast busy because nV is sending back a 400 Bad Request response when your BCM tries to initiate a call to them. I don't know why nV is sending that when you initiate an outbound call from the i2004 set. My hunch would be that the nV endpoint that the call is ultimately sent to is not liking it (it's possible that they route calls to different PSTN gateways for each call placed). You would have to check with nV, as they are sending the error response.

- Parked and transferred calls to 1140E: I'm seeing a 500 Internal Server Error response from nV when you try to pick up on the 1140E set. It's another one of those calls where nV needs to see what they don't like.

- i2004 calls with one-way media: You're seeing this because of the BSR port issue. The BSR is sending audio packets still to the BCM (192.168.1.2) when it should be going to the i2004 set (192.168.1.8) - this would be a limitation and feature gap on the SIP ALG on the router.


You may have to use your digital sets for the time being, until R6 comes out.



Joseph Sus Jr. Nortel Enthusiast
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top