RE: [reSIProcate] INVITE, dialog and tags
- From: "Alexander Altshuler" <alt@xxxxxxxxx>
- Date: Sat, 22 Oct 2005 13:40:19 +0400
Hi
Read rfc3261 more closely.
First INVITE is not request within dialog.
Dialog is established when you get first 1XX or 2XX response (except 100).
So you must use tag from 183 response (in your scenario) to construct any
requests within dialog - re-INVITES, BYE etc.
Regards,
Alex
-----Original Message-----
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
Christian_Gavin@xxxxxxxxxxxx
Sent: Saturday, October 22, 2005 4:20 AM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] INVITE, dialog and tags
Hi,
With resip 0.9 on Windows XP service pack 2...
I am getting a 481 error from the proxy when trying to cancel a call.
Should the BYE request be sent with exactly the same To: and From: header
field as the original INVITE, or should the BYE use the tag from the To: in
the 183 Session Progress?
Here the To: in the BYE request has used the tag that was supplied in the
183 response. Is that correct? According to RFC 3261,
"15.1.1 UAC Behavior
A BYE request is constructed as would any other request within a
dialog, as described in Section 12."
Trace is attached below.
Thanks,
Christian
============================================================================
===
Frame 249 (1113 bytes on wire, 1113 bytes captured)
Ethernet II, Src: 00:11:43:6c:01:fe, Dst: 00:00:0c:07:ac:01
Destination: 00:00:0c:07:ac:01 (172.17.72.1)
Source: 00:11:43:6c:01:fe (172.17.72.86)
Type: IP (0x0800)
Internet Protocol, Src Addr: 172.17.72.86 (172.17.72.86), Dst Addr:
129.132.178.178 (129.132.178.178)
User Datagram Protocol, Src Port: 35323 (35323), Dst Port: 5060 (5060)
Session Initiation Protocol
Request-Line: INVITE sip:0015107134411@xxxxxxx SIP/2.0
Message Header
To: <sip:0015107134411@xxxxxxx>
From: "Christian"<sip:0586580790@xxxxxxx>;tag=6859674d
Via: SIP/2.0/UDP
172.17.72.86:35323;branch=z9hG4bK-d87543-fe7c7955db485228-1--d87543-;rport
Call-ID: f72cd44a4a0a4a3f@TmV3QWdlTGFwdG9w
CSeq: 2 INVITE
Contact: <sip:0586580790@xxxxxxxxxxx:61065>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, MESSAGE, SUBSCRIBE,
NOTIFY
Content-Type: application/sdp
User-Agent: Test.exe version 1.0.0.1
Authorization: Digest
username="cgavin",realm="xxxx.xx",nonce="<nounce
removed>",uri="sip:0015107134411@xxxxxxx",response="<response
removed>",algorithm=MD5
Content-Length: 366
Message body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): - 127743841910780000
127743841898280000 IN IP4 67.17.144.2
Session Name (s): Test.exe version 1.0.0.1
Connection Information (c): IN IP4 67.17.144.2
Bandwidth Information (b): CT:1000
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 61071 RTP/AVP 0
8 98 101
Media Attribute (a): rtpmap:0 pcmu/8000
Media Attribute (a): rtpmap:8 pcma/8000
Media Attribute (a): rtpmap:98 ILBC/8000
Media Attribute (a): rtpmap:101 telephone-event/8000
Media Attribute (a): fmtp:101 0-15
Media Attribute (a): rtcp:61073
Media Description, name and address (m): video 61074 RTP/AVP 34
Media Attribute (a): rtpmap:34 h263/90000
Media Attribute (a): rtcp:61075
Frame 253 (416 bytes on wire, 416 bytes captured)
Ethernet II, Src: 00:07:b3:cd:3b:00, Dst: 00:11:43:6c:01:fe
Destination: 00:11:43:6c:01:fe (172.17.72.86)
Source: 00:07:b3:cd:3b:00 (172.17.72.2)
Type: IP (0x0800)
Internet Protocol, Src Addr: 129.132.178.178 (129.132.178.178), Dst Addr:
172.17.72.86 (172.17.72.86)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 35323 (35323)
Session Initiation Protocol
Status-Line: SIP/2.0 100 trying -- your call is important to us
Message Header
To: <sip:0015107134411@xxxxxxx>
From: "Christian"<sip:0586580790@xxxxxxx>;tag=6859674d
Via: SIP/2.0/UDP
172.17.72.86:35323;branch=z9hG4bK-d87543-fe7c7955db485228-1--d87543-;rport=6
1065
Call-ID: f72cd44a4a0a4a3f@TmV3QWdlTGFwdG9w
CSeq: 2 INVITE
Server: Sip EXpress router (0.9.0-tls (i386/linux))
Content-Length: 0
Frame 469 (924 bytes on wire, 924 bytes captured)
Ethernet II, Src: 00:07:b3:cd:3b:00, Dst: 00:11:43:6c:01:fe
Destination: 00:11:43:6c:01:fe (172.17.72.86)
Source: 00:07:b3:cd:3b:00 (172.17.72.2)
Type: IP (0x0800)
Internet Protocol, Src Addr: 129.132.178.178 (129.132.178.178), Dst Addr:
172.17.72.86 (172.17.72.86)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 35323 (35323)
Session Initiation Protocol
Status-Line: SIP/2.0 183 Session Progress
Message Header
Via: SIP/2.0/UDP
172.17.72.86:35323;branch=z9hG4bK-d87543-fe7c7955db485228-1--d87543-;rport=6
1065
From: "Christian"<sip:0586580790@xxxxxxx>;tag=6859674d
To: <sip:0015107134411@xxxxxxx>;tag=D63DD0F8-1AD4
Date: Fri, 21 Oct 2005 23:03:14 GMT
Call-ID: f72cd44a4a0a4a3f@TmV3QWdlTGFwdG9w
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 2 INVITE
Allow-Events: telephone-event
Contact: <sip:99990015107134411@xxxxxxxxxxx:5060>
Record-Route: <sip:129.132.178.178;ftag=6859674d;lr=on>
Content-Disposition: session;handling=required
Content-Type: application/sdp
Content-Length: 273
Message body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): CiscoSystemsSIP-GW-UserAgent
2462 3281 IN IP4 192.33.95.2
Session Name (s): SIP Call
Connection Information (c): IN IP4 192.33.95.2
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 16996 RTP/AVP 0
101
Connection Information (c): IN IP4 192.33.95.2
Media Attribute (a): rtpmap:0 PCMU/8000
Media Attribute (a): rtpmap:101 telephone-event/8000
Media Attribute (a): fmtp:101 0-15
Media Description, name and address (m): video 0 RTP/AVP
Connection Information (c): IN IP4 192.33.95.2
Frame 478 (729 bytes on wire, 729 bytes captured)
Ethernet II, Src: 00:11:43:6c:01:fe, Dst: 00:00:0c:07:ac:01
Destination: 00:00:0c:07:ac:01 (172.17.72.1)
Source: 00:11:43:6c:01:fe (172.17.72.86)
Type: IP (0x0800)
Internet Protocol, Src Addr: 172.17.72.86 (172.17.72.86), Dst Addr:
129.132.178.178 (129.132.178.178)
User Datagram Protocol, Src Port: 35323 (35323), Dst Port: 5060 (5060)
Session Initiation Protocol
Request-Line: BYE sip:99990015107134411@xxxxxxxxxxx:5060 SIP/2.0
Message Header
To: <sip:0015107134411@xxxxxxx>;tag=D63DD0F8-1AD4
From: "Christian"<sip:0586580790@xxxxxxx>;tag=6859674d
Via: SIP/2.0/UDP
172.17.72.86:35323;branch=z9hG4bK-d87543-2740973b59298a13-1--d87543-;rport
Call-ID: f72cd44a4a0a4a3f@TmV3QWdlTGFwdG9w
CSeq: 3 BYE
Route: <sip:129.132.178.178;lr;ftag=6859674d>
Contact: <sip:0586580790@xxxxxxxxxxx:61065>
Max-Forwards: 70
User-Agent: Test.exe version 1.0.0.1
Authorization: Digest
username="cgavin",realm="xxxx.xx",nonce="<nounce
removed>",uri="sip:99990015107134411@xxxxxxxxxxx:5060",response="<response
removed>",algorithm=MD5
Content-Length: 0
Frame 479 (375 bytes on wire, 375 bytes captured)
Ethernet II, Src: 00:07:b3:cd:3b:00, Dst: 00:11:43:6c:01:fe
Destination: 00:11:43:6c:01:fe (172.17.72.86)
Source: 00:07:b3:cd:3b:00 (172.17.72.2)
Type: IP (0x0800)
Internet Protocol, Src Addr: 129.132.178.178 (129.132.178.178), Dst Addr:
172.17.72.86 (172.17.72.86)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 35323 (35323)
Session Initiation Protocol
Status-Line: SIP/2.0 481 Call Leg/Transaction Does Not Exist
Message Header
Via: SIP/2.0/UDP
172.17.72.86:35323;branch=z9hG4bK-d87543-2740973b59298a13-1--d87543-;rport=6
1065
From: "Christian"<sip:0586580790@xxxxxxx>;tag=6859674d
To: <sip:0015107134411@xxxxxxx>;tag=D63DD0F8-1AD4
Call-ID: f72cd44a4a0a4a3f@TmV3QWdlTGFwdG9w
CSeq: 3 BYE
Content-Length: 0
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel