El Sábado, 15 de Marzo de 2008, [EMAIL PROTECTED] escribió: > Hi Inaki, > > I have already read it but probably missed this important detail. > Thanks for the advice. I will read it again more carefully.
In resume: The real destination is the Request-Uri (except if there is a "Route" header). "To" header jist means the **original** destination. For example: - A calls B so it generates an INVITE like: INVITE [EMAIL PROTECTED] SIP/2.0 To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] (note Request-Uri = "To" header) - A sends the INVITE to the proxy responsible for domain1. - The proxy has has a diversion to [EMAIL PROTECTED] for B. - Proxy rewrites the request-Uri and sends the INVITE to C: INVITE [EMAIL PROTECTED] SIP/2.0 To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] - The INVITE arrives to the inbound proxy of C, who rewrites the Request-Uri with the location of C AoR and sends the INVITE to it: INVITE [EMAIL PROTECTED] SIP/2.0 To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] When the INVITE arrives to C it knows that the original destination was B. In conclusion, the "To" header is just valid for this purpose and no more. It has NOTHING to do with the real destination of the call (except in the original INVITE in which "To" and RURI are the same). Hope it helps ;) Regards. -- Iñaki Baz Castillo _______________________________________________ Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
