< Previous by Date	Date Index	Next by Date >
< Previous in Thread	Thread Index

Re: [reSIProcate] Updated Contact header in NOTIFY changes request uri in SUBSCRIBE dialogs

From: Robert Sparks <rjsparks@xxxxxxxxxxx>
Date: Thu, 11 Jan 2007 14:58:03 -0600

NOTIFY _is_ a target refresh request.

(There's a bug against 3265 to make this more explicit: http://bugs.sipit.net/show_bug.cgi?id=699)


RjS

On Jan 11, 2007, at 1:08 PM, Jeremy Geras wrote:

Hi,

I'm using the latest resip/dum from subversion, and I'm encountering a
problem where a soft switch is sending me in-dialog NOTIFYs thatcontainan updated Contact header, which is causing my client (using resip/dum)
to use that updated Contact header as the new request uri for
re-SUBSCRIBE and un-SUBSCRIBE requests that it sends.

Reading RFC 3261 section 12.2.1.1:
"requests that are not target refresh requests do not affect theremote
target URI for the dialog"

The NOTIFY is not a target refresh request, yet resip/dum seems to be
updating the remote target URI from the NOTIFY anyways.  Am I
understanding things correctly here -- i.e. does this sound like a bug
in resip/dum?

For reference, I'll paste in the full text of a SUBSCRIBE/un-SUBSCRIBE
attempt below.

Thanks,
 - Jeremy -



Sip Scenario Trace

File: jan8_484addressincomplete.pcap
Generated: Thu Jan 11 10:50:58 2007
Traced on: Mon Jan  8 12:44:56 2007
Created by:sip_scenario version=1.2.7


192.168.1.115:5060             192.168.1.168:28663
|                              | <Call><PFrame><Time>
|                              |
|<--------------- SUBSCRIBE F1<|  1 PF:1   12:44:56.0996
|                              |
|>F2 401 Unauthorized -------->|  1 PF:2   12:44:56.2625
|                              |
|<--------------- SUBSCRIBE F3<|  1 PF:3   12:44:56.2902
|                              |
|>F4 200 OK ------------------>|  1 PF:4   12:44:56.4557
|                              |
|>F5 NOTIFY (xml)------------->|  1 PF:5   12:44:56.4757
|                              |
|<------------------ OK 200 F6<|  1 PF:6   12:44:56.5021
|                              |
|<--------------- SUBSCRIBE F7<|  1 PF:7   12:45:0.7365
|                              |
|>F8 401 Unauthorized -------->|  1 PF:8   12:45:0.9030
|                              |
|<--------------- SUBSCRIBE F9<|  1 PF:9   12:45:0.9316
|                              |
|>F10 484 Address Incomplete ->|  1 PF:10  12:45:1.0920
========================================================================
========
SIP MESSAGE 1 192.168.1.168:28663() ->192.168.1.115:5060()
     UDP Frame 1        8/Jan/07 12:44:56.0996
TimeFromPreviousSipFrame=0.0000 TimeFromStart=0.0000
SUBSCRIBE sip:2012030238@xxxxxxxxxxxxxxxx SIP/2.0
Via: SIP/2.0/UDP
192.168.1.168:28663;branch=z9hG4bK-d87543-8e6faf32ab56b345-1--d87543-;rp
ort
Max-Forwards: 70
Contact: <sip:pcm.2012030206@xxxxxxxxxxxxx:28663>
To: <sip:2012030238@xxxxxxxxxxxxxxxx>
From: <sip:pcm.2012030206@xxxxxxxxxxxxxxxx>;tag=233c563f
Call-ID: ZDQwOGEyZGQ5MjFkNmRkMTg0ODRmZjdjMmQ3ZTZiZjI.
CSeq: 1 SUBSCRIBE
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, INVITE, UPDATE, PRACK,NOTIFY,
REFER, SUBSCRIBE, MESSAGE, OPTIONS
Supported: 100rel, path
User-Agent: DA 2.0.0.9
Event: dialog
Allow-Events: refer, dialog, message-summary, line-seize,
x-call-service, x-call-history
Content-Length: 0
========================================================================
========
SIP MESSAGE 2 192.168.1.115:5060() ->192.168.1.168:28663()
     UDP Frame 2        8/Jan/07 12:44:56.2625
TimeFromPreviousSipFrame=0.1629 TimeFromStart=0.1629
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP
192.168.1.168:28663;received=139.142.123.131;rport=5963;branch=z9hG4bK-d
87543-8e6faf32ab56b345-1--d87543-
To: <sip:2012030238@xxxxxxxxxxxxxxxx>;tag=10.250.20.1+1+2d234c+23cfd1dc
From: <sip:pcm.2012030206@xxxxxxxxxxxxxxxx>;tag=233c563f
Call-ID: ZDQwOGEyZGQ5MjFkNmRkMTg0ODRmZjdjMmQ3ZTZiZjI.
CSeq: 1 SUBSCRIBE
Supported: 100rel,path
WWW-Authenticate: Digest
realm="zte2-ext.abc.com",nonce="9e2ae4164280",stale=false,algorithm=MD5,
qop="auth"
Server: DC-SIP/2.0
Organization:
Content-Length: 0
========================================================================
========
SIP MESSAGE 3 192.168.1.168:28663() ->192.168.1.115:5060()
     UDP Frame 3        8/Jan/07 12:44:56.2902
TimeFromPreviousSipFrame=0.0277 TimeFromStart=0.1906
SUBSCRIBE sip:2012030238@xxxxxxxxxxxxxxxx SIP/2.0
Via: SIP/2.0/UDP
192.168.1.168:28663;branch=z9hG4bK-d87543-12087b7c8d0da718-1--d87543-;rp
ort
Max-Forwards: 70
Contact: <sip:pcm.2012030206@xxxxxxxxxxxxx:28663>
To: <sip:2012030238@xxxxxxxxxxxxxxxx>
From: <sip:pcm.2012030206@xxxxxxxxxxxxxxxx>;tag=233c563f
Call-ID: ZDQwOGEyZGQ5MjFkNmRkMTg0ODRmZjdjMmQ3ZTZiZjI.
CSeq: 2 SUBSCRIBE
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, INVITE, UPDATE, PRACK,NOTIFY,
REFER, SUBSCRIBE, MESSAGE, OPTIONS
Supported: 100rel, path
User-Agent: DA 2.0.0.9
Authorization: Digest
username="pcm.2012030206",realm="zte2-ext.abc.com",nonce="9e2ae4164280",uri="sip:2012030238@zte2-ext.abc.com",response="a6fd9fc903d43ace2718e091
290ab961",cnonce="355fd7387475d660",nc=00000001,qop=auth,algorithm=MD5
Event: dialog
Allow-Events: refer, dialog, message-summary, line-seize,
x-call-service, x-call-history
Content-Length: 0
========================================================================
========
SIP MESSAGE 4 192.168.1.115:5060() ->192.168.1.168:28663()
     UDP Frame 4        8/Jan/07 12:44:56.4557
TimeFromPreviousSipFrame=0.1655 TimeFromStart=0.3561
SIP/2.0 200 OK
Via: SIP/2.0/UDP
192.168.1.168:28663;received=139.142.123.131;rport=5963;branch=z9hG4bK-d
87543-12087b7c8d0da718-1--d87543-
To: <sip:2012030238@xxxxxxxxxxxxxxxx>;tag=10.250.20.1+1+2dc44c+734536e0
From: <sip:pcm.2012030206@xxxxxxxxxxxxxxxx>;tag=233c563f
Call-ID: ZDQwOGEyZGQ5MjFkNmRkMTg0ODRmZjdjMmQ3ZTZiZjI.
CSeq: 2 SUBSCRIBE
Expires: 3600
Contact: <sip:2012030238@xxxxxxxxxxxxxxxx>
Supported: 100rel,path
Server: DC-SIP/2.0
Organization:
Allow-Events: message-summary
Allow-Events: refer
Allow-Events: dialog
Allow-Events: line-seize
Content-Length: 0
========================================================================
========
SIP MESSAGE 5 192.168.1.115:5060() ->192.168.1.168:28663()
     UDP Frame 5        8/Jan/07 12:44:56.4757
TimeFromPreviousSipFrame=0.0200 TimeFromStart=0.3761
NOTIFY sip:pcm.2012030206@xxxxxxxxxxxxxxx:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.115:5060;branch=z9hG4bK604bd23387414d98
Via: SIP/2.0/UDP
10.250.20.1;received=10.250.20.1;rport=5060;branch=z9hG4bK-d83d21de57dc9
059320870bcac49cc7e-10.250.20.1-1
To: <sip:pcm.2012030206@xxxxxxxxxxxxxxxx>;tag=233c563f
From:
<sip:2012030238@xxxxxxxxxxxxxxxx>;tag=10.250.20.1+1+2dc44c+734536e0
Call-ID: ZDQwOGEyZGQ5MjFkNmRkMTg0ODRmZjdjMmQ3ZTZiZjI.
CSeq: 596883405 NOTIFY
Contact: <sip:pcm.2012030206@xxxxxxxxxxxxxxxx;transport=udp>
Supported: 100rel,path
Event: dialog
Allow-Events: message-summary
Allow-Events: refer
Allow-Events: dialog
Allow-Events: line-seize
Max-Forwards: 70
Organization:
Subscription-State: active
Content-Type: application/dialog-info+xml
Content-Length: 156

<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0"
state="full" entity="sip:2012030238@xxxxxxxxxxx"></dialog-info>
========================================================================
========
SIP MESSAGE 6 192.168.1.168:28663() ->192.168.1.115:5060()
     UDP Frame 6        8/Jan/07 12:44:56.5021
TimeFromPreviousSipFrame=0.0264 TimeFromStart=0.4025
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.115:5060;branch=z9hG4bK604bd23387414d98
Via: SIP/2.0/UDP
10.250.20.1;received=10.250.20.1;rport=5060;branch=z9hG4bK-d83d21de57dc9
059320870bcac49cc7e-10.250.20.1-1
Contact: <sip:pcm.2012030206@xxxxxxxxxxxxx:28663>
To: <sip:pcm.2012030206@xxxxxxxxxxxxxxxx>;tag=233c563f
From:
<sip:2012030238@xxxxxxxxxxxxxxxx>;tag=10.250.20.1+1+2dc44c+734536e0
Call-ID: ZDQwOGEyZGQ5MjFkNmRkMTg0ODRmZjdjMmQ3ZTZiZjI.
CSeq: 596883405 NOTIFY
User-Agent: DA 2.0.0.9
Content-Length: 0
========================================================================
========
SIP MESSAGE 7 192.168.1.168:28663() ->192.168.1.115:5060()
     UDP Frame 7        8/Jan/07 12:45:0.7365
TimeFromPreviousSipFrame=4.2344 TimeFromStart=4.6369
SUBSCRIBE sip:pcm.2012030206@xxxxxxxxxxxxxxxx;transport=udp SIP/2.0
Via: SIP/2.0/UDP
192.168.1.168:28663;branch=z9hG4bK-d87543-062b992b8524e41f-1--d87543-;rp
ort
Max-Forwards: 70
Contact: <sip:pcm.2012030206@xxxxxxxxxxxxx:28663>
To: <sip:2012030238@xxxxxxxxxxxxxxxx>;tag=10.250.20.1+1+2dc44c+734536e0
From: <sip:pcm.2012030206@xxxxxxxxxxxxxxxx>;tag=233c563f
Call-ID: ZDQwOGEyZGQ5MjFkNmRkMTg0ODRmZjdjMmQ3ZTZiZjI.
CSeq: 4 SUBSCRIBE
Expires: 0
User-Agent: DA 2.0.0.9
Authorization: Digest
username="pcm.2012030206",realm="zte2-ext.abc.com",nonce="9e2ae4164280",uri="sip:pcm.2012030206@zte2-ext.abc.com;transport=udp",response="79dea63cf248831ebbc380ade06b3d8c",cnonce="2b01e57660489337",nc=00000002,qop=au
th,algorithm=MD5
Event: dialog
Content-Length: 0
========================================================================
========
SIP MESSAGE 8 192.168.1.115:5060() ->192.168.1.168:28663()
     UDP Frame 8        8/Jan/07 12:45:0.9030
TimeFromPreviousSipFrame=0.1666 TimeFromStart=4.8034
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP
192.168.1.168:28663;received=139.142.123.131;rport=5963;branch=z9hG4bK-d
87543-062b992b8524e41f-1--d87543-
To: <sip:2012030238@xxxxxxxxxxxxxxxx>;tag=10.250.20.1+1+2dc44c+734536e0
From: <sip:pcm.2012030206@xxxxxxxxxxxxxxxx>;tag=233c563f
Call-ID: ZDQwOGEyZGQ5MjFkNmRkMTg0ODRmZjdjMmQ3ZTZiZjI.
CSeq: 4 SUBSCRIBE
Contact: <sip:pcm.2012030206@xxxxxxxxxxxxxxxx;transport=udp>
Supported: 100rel,path
WWW-Authenticate: Digest
realm="zte2-ext.abc.com",nonce="9e2ae4174281",stale=true,algorithm=MD5,q
op="auth"
Server: DC-SIP/2.0
Organization:
Content-Length: 0
========================================================================
========
SIP MESSAGE 9 192.168.1.168:28663() ->192.168.1.115:5060()
     UDP Frame 9        8/Jan/07 12:45:0.9316
TimeFromPreviousSipFrame=0.0286 TimeFromStart=4.8320
SUBSCRIBE sip:pcm.2012030206@xxxxxxxxxxxxxxxx;transport=udp SIP/2.0
Via: SIP/2.0/UDP
192.168.1.168:28663;branch=z9hG4bK-d87543-f051dc1ee9128a61-1--d87543-;rp
ort
Max-Forwards: 70
Contact: <sip:pcm.2012030206@xxxxxxxxxxxxx:28663>
To: <sip:2012030238@xxxxxxxxxxxxxxxx>;tag=10.250.20.1+1+2dc44c+734536e0
From: <sip:pcm.2012030206@xxxxxxxxxxxxxxxx>;tag=233c563f
Call-ID: ZDQwOGEyZGQ5MjFkNmRkMTg0ODRmZjdjMmQ3ZTZiZjI.
CSeq: 5 SUBSCRIBE
Expires: 0
User-Agent: DA 2.0.0.9
Authorization: Digest
username="pcm.2012030206",realm="zte2-ext.abc.com",nonce="9e2ae4174281",uri="sip:pcm.2012030206@zte2-ext.abc.com;transport=udp",response="54f4b5cb23243f8d30b3f0b23ea7d095",cnonce="2f1e390ee15e0d18",nc=00000001,qop=au
th,algorithm=MD5
Event: dialog
Content-Length: 0
========================================================================
========
SIP MESSAGE 10 192.168.1.115:5060() ->192.168.1.168:28663()
     UDP Frame 10       8/Jan/07 12:45:1.0920
TimeFromPreviousSipFrame=0.1604 TimeFromStart=4.9924
SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP
192.168.1.168:28663;received=139.142.123.131;rport=5963;branch=z9hG4bK-d
87543-f051dc1ee9128a61-1--d87543-
To: <sip:2012030238@xxxxxxxxxxxxxxxx>;tag=10.250.20.1+1+2dc44c+734536e0
From: <sip:pcm.2012030206@xxxxxxxxxxxxxxxx>;tag=233c563f
Call-ID: ZDQwOGEyZGQ5MjFkNmRkMTg0ODRmZjdjMmQ3ZTZiZjI.
CSeq: 5 SUBSCRIBE
Contact: <sip:pcm.2012030206@xxxxxxxxxxxxxxxx;transport=udp>
Supported: 100rel,path
Server: DC-SIP/2.0
Organization:
Content-Length: 0
========================================================================
========
========================================================================
========


_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

References:
- [reSIProcate] Updated Contact header in NOTIFY changes request uri in SUBSCRIBE dialogs
  - From: Jeremy Geras

Prev by Date: Re: [reSIProcate] question about DNS time to live (TTL)
Next by Date: Re: [reSIProcate] question about DNS time to live (TTL)
Previous by thread: [reSIProcate] Updated Contact header in NOTIFY changes request uri in SUBSCRIBE dialogs
Next by thread: [reSIProcate] getting the auth used for accepting an invite
Index(es):
- Date
- Thread