[SIPForum-techwg] Quetion about how registration mode works

[Sanjay Sinha (sanjsinh)]

Inline pls...

>-----Original Message-----
>From: techwg-bounces at sipforum.org 
>[mailto:techwg-bounces at sipforum.org] On Behalf Of Hadriel Kaplan
>Sent: Saturday, February 14, 2009 4:51 AM
>To: Elwell, John; Spencer Dawkins; Francois Audet; Cullen 
>Jennings (fluffy); techwg at sipforum.org
>Subject: Re: [SIPForum-techwg] Quetion about how registration 
>mode works
>
>
>There is, BTW, a solution to this which avoids option tags I 
>think: insert a ";lr" loose-route parameter in the Contact-URI 
>of the REGISTER.  When a Registrar gets that contact, it knows 
>the UA does this new spec.  When the Registrar routes a new 
>request to the PBX, it sees that param and inserts it as a 
>Route header instead of replacing the contact.

This is essentially what was proposed with he tua-loose-route draft, but
for some reason did not make that far. I like the solution proposed in
ua-loose-route compared to what is in target-uri-delivery.

One question, don't you need some indication back to the PBX that the
SP-SSE also understands the ;lr param in Contact?

Thanks

>
>
>> -----Original Message-----
>> From: Elwell, John [mailto:john.elwell at siemens.com]
>> Sent: Friday, February 13, 2009 12:57 PM
>>
>> I would prefer not to add anything to the protocol, since it would 
>> introduce a long delay getting any new option tag or 
>whatever assigned.
>
>Then that's a pretty sad statement for the value of option 
>tags.  In 2543-days anyone could mint their own tag, and 
>that's still commonly done TODAY by most if not all of the 
>vendors on this list (including mine).  I think that 3261 
>experiment^H^Hchange failed.  We need to rethink the rules for 
>it.  There's no reason we shouldn't be able to create an 
>org.sipforum.scon.reg tag if we wanted to.
>
>-hadriel
>
>_______________________________________________
>techwg mailing list
>Send mail to: techwg at sipforum.org
>Unsubscribe or edit options at:  
>http://sipforum.org/mailman/listinfo/techwg
>