On Wed, 2008-11-26 at 11:21 -0500, Arjun Nair wrote: > Hi, > > 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. > > Comments?
Does the standard allow for non-standard elements? Even if it does, we will need to test for backward compatibility. It might be best to control this with an extension to the subscription - add a proprietary option tag (sipxecs-regpath) to a Supported header on the SUBSCRIBE, and provide the path element only if that is present - the sipXrls would send it, but any other reginfo subscriber would not and would then receive only the standard reginfo. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
