[OpenSER-Devel] Re: [Devel] SF.net SVN: openser: [2190]
trunk/modules/presence
Anca-Maria Vamanu
anca at voice-system.ro
Mon Aug 20 11:05:10 CEST 2007
Hello,
Andy Pyles wrote:
> HI Anca-Maria,
>
> I have a question about this call-flow from a while back. I think
> there is a problem with the initial subscribe sent from openser.
> Specifically with the TO: header.
>
>
> On 5/10/07, *Anca-Maria Vamanu* <anca at voice-system.ro
> <mailto:anca at voice-system.ro>> wrote:
>
> 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
> <http://192.168.2.8:5060> -> 192.168.2.132:5060
> <http://192.168.2.132:5060>
> REGISTER sip:192.168.2.132 <http://192.168.2.132> SIP/2.0.
> Via: SIP/2.0/UDP 192.168.2.8
> <http://192.168.2.8>;branch=z9hG4bK2f049f79E6653CCE.
> From: "phone1" <sip:phone1 at 192.168.2.132
> <mailto:sip:phone1 at 192.168.2.132>>;tag=96978C12-65FCBD9F.
> To: <sip:poly at 192.168.2.132 <mailto:sip:poly at 192.168.2.132>>.
> CSeq: 1 REGISTER.
> Call-ID: 823c247b-b0125bc0-b3a5fddd at 192.168.2.8
> <mailto:823c247b-b0125bc0-b3a5fddd at 192.168.2.8>.
> Contact: <sip:poly at 192.168.2.8
> <mailto:sip:poly at 192.168.2.8>>;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.
> .
>
>
> As you can see the phone registers with From "phone1" or we can say
> "Bob" as in the draft example.
>
>
> U 2007/05/10 19:42:44.891357 192.168.2.132:5060
> <http://192.168.2.132:5060> -> 192.168.2.8:5060
> <http://192.168.2.8:5060>
> SUBSCRIBE sip:poly at 192.168.2.8 <mailto:sip:poly at 192.168.2.8> SIP/2.0.
> Via: SIP/2.0/UDP 192.168.2.132
> <http://192.168.2.132>;branch=z9hG4bKee3b.0d6a9a7.0.
> To: sip:poly at 192.168.2.8 <mailto:sip:poly at 192.168.2.8>.
> From: sip:poly at 192.168.2.132
> <mailto:sip:poly at 192.168.2.132>;tag=616c04edf3c5befd4558c7fc378ac996-514f.
> CSeq: 10 SUBSCRIBE.
> Call-ID: 7c55bd80-14816 at 192.168.2.132
> <mailto:7c55bd80-14816 at 192.168.2.132>.
> Content-Length: 0.
> User-Agent: OpenSER (1.3.0-dev4-notls (i386/linux)).
> Event: dialog;sla.
> Contact: <sip:poly at 192.168.2.132 <mailto:sip:poly at 192.168.2.132>>.
> Expires: 110.
>
>
> I'm assuming this call flow is taken from section 6.1.2 of the draft.
> "Bob Registration and Subscription Flow"
> If you look at packet F9, note the FROM and TO headers.
>
> It looks to me that the from header is right ( from Alice:) , but the
> the TO: header should be
> To: sip:phone1 at 192.168.2.8 <mailto:sip:phone1 at 192.168.2.8> ( to BOB)
When constructing the Subscribe above, sent by OpenSER, the info from
the Register message are used. In the R-URI and the To header, will
contain the value from the Contact header in Register. And, on the other
hand, I can not get sip:phone1 at 192.168.2.8
<mailto:sip:phone1 at 192.168.2.8> from that Register message.
regards,
Anca
>
>
> Regards,
> Andy
>
>
> .
> NOTIFY sip:poly at 192.168.2.132 <mailto:sip:poly at 192.168.2.132> SIP/2.0.
> Via: SIP/2.0/UDP 192.168.2.8
> <http://192.168.2.8>;branch=z9hG4bK8cee88d6657A1843.
> From: <sip:poly at 192.168.2.8
> <mailto:sip:poly at 192.168.2.8>>;tag=42CCFC4-B67A55C1.
> To: < sip:poly at 192.168.2.132
> <mailto:sip:poly at 192.168.2.132>>;tag=616c04edf3c5befd4558c7fc378ac996-514f.
> CSeq: 1 NOTIFY.
> Call-ID: 7c55bd80-14816 at 192.168.2.132
> <mailto:7c55bd80-14816 at 192.168.2.132>.
> Contact: < sip:poly at 192.168.2.8 <mailto:sip:poly at 192.168.2.8>>.
> 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:poly at 192.168.2.132
> <mailto:sip:poly at 192.168.2.132>">.
> </dialog-info>
>
>
> U 2007/05/10 19:42:46.751643 192.168.2.8:5060
> <http://192.168.2.8:5060> -> 192.168.2.132:5060
> <http://192.168.2.132:5060>
> SUBSCRIBE sip:poly at 192.168.2.132 <mailto:sip:poly at 192.168.2.132>
> SIP/2.0.
> Via: SIP/2.0/UDP 192.168.2.8
> <http://192.168.2.8>;branch=z9hG4bK346f7948417AB725.
> From: "phone1" < sip:phone1 at 192.168.2.132
> <mailto:sip:phone1 at 192.168.2.132>>;tag=43D63209-6292CADE.
> To: <sip:poly at 192.168.2.132 <mailto:sip:poly at 192.168.2.132>>.
> CSeq: 1 SUBSCRIBE.
> Call-ID: 42aac31a-6804467-4a55e84c at 192.168.2.8
> <mailto:42aac31a-6804467-4a55e84c at 192.168.2.8>.
> Contact: <sip:poly at 192.168.2.8 <mailto:sip:poly at 192.168.2.8>>.
> 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
> <http://192.168.2.8:5060> -> 192.168.2.132:5060
> <http://192.168.2.132:5060>
> SUBSCRIBE sip:192.168.2.132:5060 <http://192.168.2.132:5060> SIP/2.0.
> Via: SIP/2.0/UDP 192.168.2.8
> <http://192.168.2.8>;branch=z9hG4bKbb45512f3A7A56D4.
> From: "phone1" <sip:phone1 at 192.168.2.132
> <mailto:sip:phone1 at 192.168.2.132>>;tag=43D63209-6292CADE.
> To: <sip:poly at 192.168.2.132
> <mailto:sip:poly at 192.168.2.132>>;tag=10.14816.1178815366.2.
> CSeq: 2 SUBSCRIBE.
> Call-ID: 42aac31a-6804467-4a55e84c at 192.168.2.8
> <mailto:42aac31a-6804467-4a55e84c at 192.168.2.8>.
> Contact: < sip:poly at 192.168.2.8 <mailto:sip:poly at 192.168.2.8>>.
> 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.
>
More information about the Devel
mailing list