El Sábado, 15 de Marzo de 2008, shiebar(a)post.tau.ac.il escribió: 99% you don't need at all to change the "To" header. That's RFC 3261 non complinat. -- Iñaki Baz Castillo _______________________________________________ Users mailing list Users(a)lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users

El Sábado, 15 de Marzo de 2008, shiebar(a)post.tau.ac.il escribió: And why do you assume that it's a fail related to the "To" header? RFC 3261 21.4.19 481 Call/Transaction Does Not Exist This status indicates that the UAS received a request that does not match any existing dialog or transaction. Also read how a UA tries to match an incoming request to an existing transaction: http://tools.ietf.org/html/rfc3261#section-17.2.3 Sincerely, you should read the RFC 3261 to understand that the "To" header is usually not examinated by the UAS, just the Request-Uri. But you cannot asumme something incorrect without reading about it and later ask "then what?". ;) -- Iñaki Baz Castillo _______________________________________________ Users mailing list Users(a)lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users

El Sábado, 15 de Marzo de 2008, shiebar(a)post.tau.ac.il escribió: 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 B@domain1 SIP/2.0 To: B@domain1 From: A@domain1 (note Request-Uri = "To" header) - A sends the INVITE to the proxy responsible for domain1. - The proxy has has a diversion to C@domain2 for B. - Proxy rewrites the request-Uri and sends the INVITE to C: INVITE C@domain2 SIP/2.0 To: B@domain1 From: A@domain1 - 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 C@ip_c SIP/2.0 To: B@domain1 From: A@domain1 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(a)lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users

El Sábado, 15 de Marzo de 2008, Iñaki Baz Castillo escribió: Look at my previous mail (the pure mail headers): From: =?utf-8?q?I=C3=B1aki_Baz_Castillo?= <ibc(a)aliax.net> To: users(a)lists.openser.org But the fact is that the mail arrived to you !!!! XDD This is because during the SMTP protocol, the destination user for that mail was changed in favour of your user, but in the "To" headers remains the *original* destination (just for informative purposes). It's same as in SIP. ;) -- Iñaki Baz Castillo _______________________________________________ Users mailing list Users(a)lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users