Here is a message sequence from a Polycom phone.
It seems that when updating, the phone uses the uri in Contact header as
Request-URI - and it did not worked.
Now I am not sure xlite does not do the same. I have to study more this
issue.
U 2007/05/10 19:42:44.870449 192.168.2.8:5060 -> 192.168.2.132:5060
REGISTER sip:192.168.2.132 SIP/2.0.
Via: SIP/2.0/UDP 192.168.2.8;branch=z9hG4bK2f049f79E6653CCE.
From: "phone1" <sip:[EMAIL PROTECTED]>;tag=96978C12-65FCBD9F.
To: <sip:[EMAIL PROTECTED]>.
CSeq: 1 REGISTER.
Call-ID: [EMAIL PROTECTED]
Contact: <sip:[EMAIL PROTECTED]>;methods="INVITE, ACK, BYE, CANCEL,
OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER".
User-Agent: PolycomSoundPointIP-SPIP_430-UA/2.0.3.0127.
Max-Forwards: 70.
Expires: 3600.
Content-Length: 0.
.
U 2007/05/10 19:42:44.891357 192.168.2.132:5060 -> 192.168.2.8:5060
SUBSCRIBE sip:[EMAIL PROTECTED] SIP/2.0.
Via: SIP/2.0/UDP 192.168.2.132;branch=z9hG4bKee3b.0d6a9a7.0.
To: sip:[EMAIL PROTECTED]
From: sip:[EMAIL PROTECTED];tag=616c04edf3c5befd4558c7fc378ac996-514f.
CSeq: 10 SUBSCRIBE.
Call-ID: [EMAIL PROTECTED]
Content-Length: 0.
User-Agent: OpenSER (1.3.0-dev4-notls (i386/linux)).
Event: dialog;sla.
Contact: <sip:[EMAIL PROTECTED]>.
Expires: 110.
.
NOTIFY sip:[EMAIL PROTECTED] SIP/2.0.
Via: SIP/2.0/UDP 192.168.2.8;branch=z9hG4bK8cee88d6657A1843.
From: <sip:[EMAIL PROTECTED]>;tag=42CCFC4-B67A55C1.
To: <sip:[EMAIL PROTECTED]>;tag=616c04edf3c5befd4558c7fc378ac996-514f.
CSeq: 1 NOTIFY.
Call-ID: [EMAIL PROTECTED]
Contact: <sip:[EMAIL PROTECTED]>.
Event: dialog;sla.
User-Agent: PolycomSoundPointIP-SPIP_430-UA/2.0.3.0127.
Subscription-State: active;expires=109.
Max-Forwards: 70.
Content-Type: application/dialog-info+xml.
Content-Length: 152.
.
<?xml version="1.0"?>.
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0"
state="full" entity="sip:[EMAIL PROTECTED]">.
</dialog-info>
U 2007/05/10 19:42:46.751643 192.168.2.8:5060 -> 192.168.2.132:5060
SUBSCRIBE sip:[EMAIL PROTECTED] SIP/2.0.
Via: SIP/2.0/UDP 192.168.2.8;branch=z9hG4bK346f7948417AB725.
From: "phone1" <sip:[EMAIL PROTECTED]>;tag=43D63209-6292CADE.
To: <sip:[EMAIL PROTECTED]>.
CSeq: 1 SUBSCRIBE.
Call-ID: [EMAIL PROTECTED]
Contact: <sip:[EMAIL PROTECTED]>.
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE,
NOTIFY, PRACK, UPDATE, REFER.
Event: dialog;sla.
User-Agent: PolycomSoundPointIP-SPIP_430-UA/2.0.3.0127.
Accept: application/dialog-info+xml.
Max-Forwards: 70.
Expires: 110.
Content-Length: 0.
U 2007/05/10 19:43:36.753299 192.168.2.8:5060 -> 192.168.2.132:5060
SUBSCRIBE sip:192.168.2.132:5060 SIP/2.0.
Via: SIP/2.0/UDP 192.168.2.8;branch=z9hG4bKbb45512f3A7A56D4.
From: "phone1" <sip:[EMAIL PROTECTED]>;tag=43D63209-6292CADE.
To: <sip:[EMAIL PROTECTED]>;tag=10.14816.1178815366.2.
CSeq: 2 SUBSCRIBE.
Call-ID: [EMAIL PROTECTED]
Contact: <sip:[EMAIL PROTECTED]>.
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE,
NOTIFY, PRACK, UPDATE, REFER.
Event: dialog;sla.
User-Agent: PolycomSoundPointIP-SPIP_430-UA/2.0.3.0127.
Accept: application/dialog-info+xml.
Max-Forwards: 70.
Expires: 110.
Content-Length: 0.
Juha Heinanen wrote:
Anca Vamanu writes:
> Log Message:
> -----------
> - introduced the possiblity to choose where to take presentity uri
> - from, specific for event (needed for pua_bla)
why is it needed for bla?
i tried to study the example call flows in draft-anil-sipping-bla-03.txt
and didn't find any reason to use to header for anything. phones
subscribe to state agent:
SUBSCRIBE sip:[EMAIL PROTECTED] SIP/2.0
and state agent subscribes to phones' contacts:
SUBSCRIBE sip:[EMAIL PROTECTED] SIP/2.0
SUBSCRIBE sip:[EMAIL PROTECTED] SIP/2.0
-- juha
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
