On Wed, 2008-11-26 at 11:21 -0500, Arjun Nair wrote:
> I am proposing to add path attribute to the reg-info, i.e.
>
> <?xml version="1.0"?>
> <reginfo xmlns="urn:ietf:params:xml:ns:reginfo"
> version="1" state="partial">
> <registration aor="sip:[EMAIL PROTECTED]" id="a7" state="active">
> <contact id="76" state="active" event="registered"
> duration-registered="0">
> <uri>sip:[EMAIL PROTECTED]</uri>
> <path>my.path.com</path>
> </contact>
> </registration>
> </reginfo>
>
> The RLS will then use this path header to create a route set in the
> outgoing dialog-forming Request.
>
> As for phones with GRUU addresses, we can pass the GRUU address as the
> Contact URI, and not bother with the Path headers.
If the registration has a GRUU, it is carried in a <pub-gruu> element
within the <registration> element. See
draft-ietf-sipping-gruu-reg-event-09, soon to be an RFC.
A typical example is:
<?xml version="1.0"?>
<reginfo xmlns="urn:ietf:params:xml:ns:reginfo"
xmlns:gr="urn:ietf:params:xml:ns:gruuinfo"
version="0" state="full">
<registration aor="sip:[EMAIL PROTECTED]" id="as9"
state="active">
<contact id="76" state="active" event="registered"
duration-registered="36001" expires="3599"
callid="[EMAIL PROTECTED]" cseq="54321"
q="0.8">
<uri>sip:[EMAIL PROTECTED]</uri>
<unknown-param
name="+sip.instance">"<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>"</unknown-param>
<gr:pub-gruu uri="sip:[EMAIL PROTECTED];gr=hha9s8d-999a"/>
</contact>
</registration>
</reginfo>
(Because the UA provided an instance ID, there is an <unknown-param
name="+sip.instance"> element as well.)
(Oddly, a registrar can construct a GRUU for a registration even if the
UA doesn't support GRUU. Because the registrar/proxy converts the GRUU
to the contact of the UA, the UA can receive requests directed to the
GRUU.)
Summarizing this discussion, if a UA registers with a Path and is issued
a GRUU, the <reginfo> will look like this:
<?xml version="1.0"?>
<reginfo xmlns="urn:ietf:params:xml:ns:reginfo"
xmlns:gr="urn:ietf:params:xml:ns:gruuinfo"
version="1" state="partial">
<registration aor="sip:[EMAIL PROTECTED]" id="a7" state="active">
<contact id="76" state="active" event="registered"
duration-registered="100">
<uri>sip:[EMAIL PROTECTED]</uri>
<unknown-param name=path>sip:my.path.com</unknown-param>
<gr:pub-gruu uri="sip:[EMAIL PROTECTED];gr=hha9s8d-999a"/>
</contact>
</registration>
</reginfo>
(Note that values of the Path header are name-addr's (see RFC 3327
section 4, and so the "sip:" at the beginning of the value may not be
omitted, as has been done in several examples in this thread.)
The recipient of this document can access this UA via
"sip:[EMAIL PROTECTED];gr=hha9s8d-999a", or
"sip:[EMAIL PROTECTED]:my.path.com", or
"sip:[EMAIL PROTECTED]", depending on which components of reginfo it
understands. The first is preferable to the second, and the third may
not work.
Dale
_______________________________________________
sipx-dev mailing list
sipx-dev@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
