Scott Lawrence wrote: > On Thu, 2008-09-11 at 17:26 -0400, Arjun Nair wrote: >> Scott Lawrence wrote: >>> I'm not sure this approach will work (for either the paging server or >>> RLS, actually) if the phone is remote. >>> >>> The problem is that the registration event will give you the Contact for >>> the phone, but not the associated route set. If the phone is remote, >>> and needs to go through a particular proxy, then using only the Contact >>> address will sometimes not work. >>> >>> Unless the Contact value is a gruu (is globally routable), using it as >>> the target for an out-of-dialog request is not a reliable thing to do. >>> >>> >> Hi Scott, >> >> I am a bit confused here. It is the paging server that initiates the >> dialog. How would a dialog initiating entity get the associated route >> set for a far-end phone? > > If the phone is addresses using the AOR that it registered (the To > address from the REGISTER), then the proxy/registrar will route it to > the service route that ensures it goes through the correct proxy, but > the Contact alone from that REGISTER might not. >
OK, I see. I was also pointed to the use of path headers in Registrations - http://www.ietf.org/rfc/rfc3327.txt - for this purpose. Thanks, Arjun _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
