Dear Members.

We have two peering networks connected via SBC. Let me explain the issue.

The call is dropped by the peering end (Side-B)  using the 200OK for the
BYE. but still the Side A continue sending the CANCEL messages.

I want to know in which circumstances the side A keeps sending the CANCEL
messages.  and which side is complaint to RFC standards,I have been to the
RFC3261 and feel that both sides are complaint to the RFC. I have attached
the wire shark traces in text format. RFC 3261  section 15 is used as
reference.

Kindly advise.

-- 
Br,
Imran Saleem
+966-533-414475
INVITE sip:1234567890@2.2.2.2:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
CSeq: 1 INVITE
Contact: <sip:1.1.1.1:5060;transport=udp>
MIME-Version: 1.03
Supported: timer,100rel
Max-Forwards: 69
P-Asserted-Identity: <sip:0987654321@1.1.1.1;user=phone>
Session-Expires: 1800
Allow: ACK,INFO,BYE,CANCEL,INVITE,OPTIONS,NOTIFY,PRACK,UPDATE
Content-Type: application/sdp
Content-Length: 333

v=0
o=   575320141103134747 1813774454 IN IP4 1.1.1.1
s=SIP
c=IN IP4 1.1.1.1
t=0 0
m=audio 40236 RTP/AVP 8 18 100 13
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 telephone-event/8000
a=fmtp:100 0-15
a=rtpmap:13 CN/8000
a=sqn: 0
a=cdsc: 1 image udptl t38
a=sendrecv
a=ptime:20

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>
CSeq: 1 INVITE
Content-Length: 0

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>
CSeq: 1 INVITE
Content-Length: 0

SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
Record-Route: <sip:2.2.2.2:9130;transport=udp;lr>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>;tag=JZeHBccHelleHYYH
CSeq: 1 INVITE
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,UPDATE
Contact: <sip:2.2.2.2:9130>
Require: 100rel
RSeq: 1
Content-Length: 198
Content-Type: application/sdp

v=0
o=- 1077081774 1077081775 IN IP4 2.2.2.3
s=SBC call
c=IN IP4 2.2.2.3
t=0 0
m=audio 46814 RTP/AVP 8 100
a=rtpmap:8 PCMA/8000
a=rtpmap:100 telephone-event/8000
a=ptime:20


SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
Record-Route: <sip:2.2.2.2:9130;transport=udp;lr>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>;tag=JZeHBccHelleHYYH
CSeq: 1 INVITE
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,UPDATE
Contact: <sip:2.2.2.2:9130>
Require: 100rel
RSeq: 1
Content-Length: 198
Content-Type: application/sdp

v=0
o=- 1077081774 1077081775 IN IP4 2.2.2.3
s=SBC call
c=IN IP4 2.2.2.3
t=0 0
m=audio 46814 RTP/AVP 8 100
a=rtpmap:8 PCMA/8000
a=rtpmap:100 telephone-event/8000
a=ptime:20


PRACK sip:2.2.2.2:9130 SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK2aaklc107ot1hrgrk2o1.1
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>;tag=JZeHBccHelleHYYH
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
CSeq: 2 PRACK
Supported: timer
Max-Forwards: 69
RAck: 1 1 INVITE
Content-Length: 0
Route: <sip:2.2.2.2:9130;transport=udp;lr>

SIP/2.0 200 OK
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK2aaklc107ot1hrgrk2o1.1
Record-Route: <sip:2.2.2.2:9130;transport=udp;lr>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>;tag=JZeHBccHelleHYYH
CSeq: 2 PRACK
Content-Length: 0

SIP/2.0 200 OK
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK2aaklc107ot1hrgrk2o1.1
Record-Route: <sip:2.2.2.2:9130;transport=udp;lr>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>;tag=JZeHBccHelleHYYH
CSeq: 2 PRACK
Content-Length: 0


SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
Record-Route: <sip:2.2.2.2:9130;transport=udp;lr>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>;tag=JZeHBccHelleHYYH
CSeq: 1 INVITE
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,UPDATE
Contact: <sip:2.2.2.2:9130>
Require: 100rel
P-Early-Media: sendrecv
RSeq: 2
Content-Length: 0


SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
Record-Route: <sip:2.2.2.2:9130;transport=udp;lr>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>;tag=JZeHBccHelleHYYH
CSeq: 1 INVITE
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,PRACK,NOTIFY,MESSAGE,UPDATE
Contact: <sip:2.2.2.2:9130>
Require: 100rel
P-Early-Media: sendrecv
RSeq: 2
Content-Length: 0

PRACK sip:2.2.2.2:9130 SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bKsq11fd10c830vt499221.1
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>;tag=JZeHBccHelleHYYH
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
CSeq: 3 PRACK
Supported: timer
Max-Forwards: 69
RAck: 2 1 INVITE
Content-Length: 0
Route: <sip:2.2.2.2:9130;transport=udp;lr>


SIP/2.0 200 OK
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bKsq11fd10c830vt499221.1
Record-Route: <sip:2.2.2.2:9130;transport=udp;lr>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>;tag=JZeHBccHelleHYYH
CSeq: 3 PRACK
Content-Length: 0

SIP/2.0 200 OK
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bKsq11fd10c830vt499221.1
Record-Route: <sip:2.2.2.2:9130;transport=udp;lr>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>;tag=JZeHBccHelleHYYH
CSeq: 3 PRACK
Content-Length: 0

BYE sip:2.2.2.2:9130 SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bKqut31h00507g9l8hu341.1
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>;tag=JZeHBccHelleHYYH
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
CSeq: 4 BYE
Supported: timer
Max-Forwards: 69
Reason: Q.850 ;cause=16 ;text="Normal call clearing"
Content-Length: 0
Route: <sip:2.2.2.2:9130;transport=udp;lr>

SIP/2.0 200 OK
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bKqut31h00507g9l8hu341.1
Record-Route: <sip:2.2.2.2:9130;transport=udp;lr>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>;tag=JZeHBccHelleHYYH
CSeq: 4 BYE
Content-Length: 0

SIP/2.0 200 OK
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bKqut31h00507g9l8hu341.1
Record-Route: <sip:2.2.2.2:9130;transport=udp;lr>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>;tag=JZeHBccHelleHYYH
CSeq: 4 BYE
Content-Length: 0


CANCEL sip:1234567890@2.2.2.2:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
CSeq: 1 CANCEL
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
Max-Forwards: 69
Content-Length: 0

CANCEL sip:1234567890@2.2.2.2:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
CSeq: 1 CANCEL
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
Max-Forwards: 69
Content-Length: 0

CANCEL sip:1234567890@2.2.2.2:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
CSeq: 1 CANCEL
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
Max-Forwards: 69
Content-Length: 0

CANCEL sip:1234567890@2.2.2.2:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
CSeq: 1 CANCEL
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
Max-Forwards: 69
Content-Length: 0

CANCEL sip:1234567890@2.2.2.2:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
CSeq: 1 CANCEL
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
Max-Forwards: 69
Content-Length: 0

CANCEL sip:1234567890@2.2.2.2:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
CSeq: 1 CANCEL
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
Max-Forwards: 69
Content-Length: 0

CANCEL sip:1234567890@2.2.2.2:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
CSeq: 1 CANCEL
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
Max-Forwards: 69
Content-Length: 0

CANCEL sip:1234567890@2.2.2.2:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
CSeq: 1 CANCEL
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
Max-Forwards: 69
Content-Length: 0

CANCEL sip:1234567890@2.2.2.2:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
CSeq: 1 CANCEL
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
Max-Forwards: 69
Content-Length: 0

CANCEL sip:1234567890@2.2.2.2:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
CSeq: 1 CANCEL
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
Max-Forwards: 69
Content-Length: 0

CANCEL sip:1234567890@2.2.2.2:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK59nh4500b8pgfqsrk541.1
CSeq: 1 CANCEL
From: 
<sip:0987654321@1.1.1.1;user=phone>;tag=SDbd1d401-547EEA53-970608D-0AD01111
To: <sip:1234567890@2.2.2.2:5060;user=phone>
Call-ID: SDbd1d401-d2c800aec080151ba30cdb92b5a979a3-v300g00
Max-Forwards: 69
Content-Length: 0




_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to