On Mon, Feb 9, 2009 at 12:22 PM, Dale Worley <[email protected]> wrote: > On Mon, 2009-02-09 at 11:55 -0500, M. Ranganathan wrote: >> Problem I have is that I need some indication that the call being made >> is to an emergency service so I know how to find the ITSP in >> sipxbridge to route the request to. The Request URI should also be >> formatted as >> >> sip:911;[email protected];user=phone >> >> (at least this is what I understand - please correct if mistaken). >> >> Usually, I would get a RequestURI like this : >> sip:[email protected]. Will the R-URI look like the above when >> sipxbridge sees it or will it look like sip:[email protected] ? >> >> My question is how will the request look when it is sent to sipxbridge >> by sipx proxy when an emergency call is made via a specific ITSP? How >> can I recognize that it is an emergency call and possibly re-write the >> request URI to be as required? > > I may not be understanding the problem, but I would think that the thing > to do is place the burden on the proxy, and have it write the request > URI as SIPconnect specifies. Then the bridge doesn't need to rewrite > the request URI, and the "@serviceprovider.net" part of the request URI > should be sufficient to tell the bridge how to route the call. But > maybe there is a complexity that I do not understand. > > Dale
No complication -- just a matter of convention. I just want to establish that it will be so (or not). Thanks Ranga > > > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
