Thanks, Iñaki. But It is not what I really need.<br><br>I need to send to an UAS a SIP Request, like OPTIONS, and tell it to send the reply to a different transport address (IP Addr + Port) than the source address of the request.<br>
<br>This is, basically, in order to perform NAT discovering and typing from the server.<br><br>Thanks in advance,<br><br>Víctor<br><br><br><br><br><div><span class="gmail_quote">2008/4/7, Iñaki Baz Castillo <<a href="mailto:ibc@in.ilimit.es">ibc@in.ilimit.es</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
El Monday 07 April 2008 14:03:39 Victor Cartes escribió:<br> <br>> Hello to all,<br> ><br> > About SIP/UDP: Is there any way to specify the IP address for SIP<br> > responses, in a similar fashion as port specified on top most Via HF?<br>
<br> <br>RFC 3261:<br> <a href="http://tools.ietf.org/html/rfc3261#section-18.2.1">http://tools.ietf.org/html/rfc3261#section-18.2.1</a><br> <br> <br> 18.2.1 Receiving Requests<br> <br> When the server transport receives a request over any transport, it<br>
MUST examine the value of the "sent-by" parameter in the top Via<br> header field value. If the host portion of the "sent-by" parameter<br> contains a domain name, or if it contains an IP address that differs<br>
from the packet source address, the server MUST add a "received"<br> parameter to that Via header field value. This parameter MUST<br> contain the source address from which the packet was received.<br> This is to assist the server transport layer in sending the response,<br>
since it must be sent to the source IP address from which the request<br> came.<br> <br> Consider a request received by the server transport which looks like,<br> in part:<br> <br> INVITE sip:bob@Biloxi.com SIP/2.0<br>
Via: SIP/2.0/UDP <a href="http://bobspc.biloxi.com:5060">bobspc.biloxi.com:5060</a><br> <br> The request is received with a source IP address of <a href="http://192.0.2.4">192.0.2.4</a>.<br> Before passing the request up, the transport adds a "received"<br>
parameter, so that the request would look like, in part:<br> <br> INVITE sip:bob@Biloxi.com SIP/2.0<br> Via: SIP/2.0/UDP bobspc.biloxi.com:5060;received=<a href="http://192.0.2.4">192.0.2.4</a><br> <br> <br> This means that ANY UAS or proxy (as OpenSer) must add "received" parameter to<br>
the top mos VIA header in case the source IP is not the same as the indicated<br> in sent-by field fo top Via header. This is in UPD or TCP. And this is<br> already done by OpenSer (automatically).<br> <br> Regards.<br> <br>
<br> --<br> Iñaki Baz Castillo<br> <a href="mailto:ibc@in.ilimit.es">ibc@in.ilimit.es</a><br> <br><br> _______________________________________________<br> Users mailing list<br> <a href="mailto:Users@lists.openser.org">Users@lists.openser.org</a><br>
<a href="http://lists.openser.org/cgi-bin/mailman/listinfo/users">http://lists.openser.org/cgi-bin/mailman/listinfo/users</a><br> </blockquote></div><br>