[SIPForum-discussion] Mutliple 183 Message Issue

Tue Feb 5 12:57:41 UTC 2013

Hi,

One of my carrier is sending me more than one 183 Messages.

First they are sending 183 Session Progress, followed by 180 ringing and then again 183 Session Progress.

So my questions are.

1. Why were are getting more than 183 Session Progress messages and if we get such messages how should they be treated.
2. Why is there a 180 Ringing message after 183 Session Progress.
3. What is the default signalling related to 180, 183 when and what should be the sequence.

A detailed explanation or if some documentation/link is provided then that will be really appreciated 

Find the below SIP trace for reference.

INVITE sip:919999999999 at 2.2.2.2:5060 SIP/2.0

Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK1sansay935497615rdb37177

Record-Route: <sip:sansay935497615rdb37177 at 1.1.1.1:5060;lr;transport=udp>

To: <sip:919999999999 at 2.2.2.2>

From: "100167" <sip:12127773456 at 1.1.1.1>;tag=sansay935497615rdb37177

Call-ID: 472337620-0-2186210730 at 1.1.1.3

CSeq: 1 INVITE

Contact: <sip:12127773456 at 1.1.1.1:5060>

Supported: timer,replaces

Session-Expires: 1800;refresher=uac

Min-SE: 90

Max-Forwards: 69

Content-Type: application/sdp

Content-Length: 343

v=0

o=Sansay-VSXi 188 1 IN IP4 1.1.1.1

s=Session Controller

c=IN IP4 1.1.1.2

t=0 0

m=audio 36874 RTP/AVP 18 4 0 101

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=no

a=rtpmap:4 G723/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:4 annexa=no

a=fmtp:101 0-16

a=silenceSupp:off - - - -

a=ptime:20

a=sendrecv

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK1sansay935497615rdb37177

To: <sip:919999999999 at 2.2.2.2>

From: "100167"<sip:12127773456 at 1.1.1.1>;tag=sansay935497615rdb37177

Call-ID: 472337620-0-2186210730 at 1.1.1.3

CSeq: 1 INVITE

User-Agent: MySBC-SBC

Content-Length: 0

SIP/2.0 183 Session Progress

Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK1sansay935497615rdb37177

To: <sip:919999999999 at 2.2.2.2>;tag=ac101602-ObxG26a33255

From: "100167"<sip:12127773456 at 1.1.1.1>;tag=sansay935497615rdb37177

Call-ID: 472337620-0-2186210730 at 1.1.1.3

CSeq: 1 INVITE

Contact: <sip:919999999999 at 2.2.2.2:5060>

Record-Route: <sip:sansay935497615rdb37177 at 1.1.1.1:5060;transport=udp;lr>

User-Agent: MySBC Softswitch/1.0.0

Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,REFER,NOTIFY,SUBSCRIBE,PRACK,UPDATE

Content-Type: application/sdp

Content-Length: 210

v=0

o=MySBC 1725 18942 IN IP4 2.2.2.3

s=phone-call

c=IN IP4 2.2.2.3

t=0 0

m=audio 20456 RTP/AVP 18 101

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:20

a=rtpmap:18 G729/8000/1

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK1sansay935497615rdb37177

To: <sip:919999999999 at 2.2.2.2>;tag=ac101602-ObxG26a33255

From: "100167"<sip:12127773456 at 1.1.1.1>;tag=sansay935497615rdb37177

Call-ID: 472337620-0-2186210730 at 1.1.1.3

CSeq: 1 INVITE

Contact: <sip:919999999999 at 2.2.2.2:5060>

Record-Route: <sip:sansay935497615rdb37177 at 1.1.1.1:5060;transport=udp;lr>

User-Agent: MySBC Softswitch/1.0.0

Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,REFER,NOTIFY,SUBSCRIBE,PRACK,UPDATE

Content-Type: application/sdp

Content-Length: 210

v=0

o=MySBC 1725 18943 IN IP4 2.2.2.3

s=phone-call

c=IN IP4 2.2.2.3

t=0 0

m=audio 20456 RTP/AVP 18 101

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:20

a=rtpmap:18 G729/8000/1

SIP/2.0 183 Session Progress

Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK1sansay935497615rdb37177

To: <sip:919999999999 at 2.2.2.2>;tag=ac101602-ObxG26a33255

From: "100167"<sip:12127773456 at 1.1.1.1>;tag=sansay935497615rdb37177

Call-ID: 472337620-0-2186210730 at 1.1.1.3

CSeq: 1 INVITE

Contact: <sip:919999999999 at 2.2.2.2:5060>

Record-Route: <sip:sansay935497615rdb37177 at 1.1.1.1:5060;transport=udp;lr>

User-Agent: MySBC Softswitch/1.0.0

Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,REFER,NOTIFY,SUBSCRIBE,PRACK,UPDATE

Content-Type: application/sdp

Content-Length: 210

v=0

o=MySBC 1725 18944 IN IP4 2.2.2.3

s=phone-call

c=IN IP4 2.2.2.3

t=0 0

m=audio 20456 RTP/AVP 18 101

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:20

a=rtpmap:18 G729/8000/1

CANCEL sip:919999999999 at 2.2.2.2:5060 SIP/2.0

Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK1sansay935497615rdb37177

To: <sip:919999999999 at 2.2.2.2>

From: "100167" <sip:12127773456 at 1.1.1.1>;tag=sansay935497615rdb37177

Call-ID: 472337620-0-2186210730 at 1.1.1.3

CSeq: 1 CANCEL

Max-Forwards: 69

Content-Length: 0

SIP/2.0 200 OK

Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK1sansay935497615rdb37177

To: <sip:919999999999 at 2.2.2.2>;tag=39cd873a150a9b21-283b4ef86fc85d5f-cbsxz

From: "100167"<sip:12127773456 at 1.1.1.1>;tag=sansay935497615rdb37177

Call-ID: 472337620-0-2186210730 at 1.1.1.3

CSeq: 1 CANCEL

User-Agent: MySBC-SBC

X-MySBC-Cause: "SBC-4401-2002"

Content-Length: 0

SIP/2.0 487 Request Terminated

Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK1sansay935497615rdb37177

To: <sip:919999999999 at 2.2.2.2>;tag=ac101602-ObxG26a33255

From: "100167"<sip:12127773456 at 1.1.1.1>;tag=sansay935497615rdb37177

Call-ID: 472337620-0-2186210730 at 1.1.1.3

CSeq: 1 INVITE

Record-Route: <sip:sansay935497615rdb37177 at 1.1.1.1:5060;transport=udp;lr>

User-Agent: MySBC Softswitch/1.0.0

Content-Length: 0

ACK sip:919999999999 at 2.2.2.2:5060 SIP/2.0

Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK1sansay935497615rdb37177

To: <sip:919999999999 at 2.2.2.2>;tag=ac101602-ObxG26a33255

From: "100167" <sip:12127773456 at 1.1.1.1>;tag=sansay935497615rdb37177

Call-ID: 472337620-0-2186210730 at 1.1.1.3

CSeq: 1 ACK

Max-Forwards: 70

Content-Length: 0

Thanking you in advance. 

Rgds..

Prakash Singh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20130205/1dc02c5c/attachment-0002.html>