Replies take the same path as requests, no matter what kind of proxy there were on the way.<br>SER replies to the address it detected in the transport layer (UDP/IP) of the request; the Via in your request will be used by the application server to send the reply back to the UA and not by SER; SER doesn&#39;t even look at that Via.
<br><br>WL.<br><br><div><span class="gmail_quote">On 4/25/07, <b class="gmail_sendername">tzieleniewski</b> &lt;<a href="mailto:tzieleniewski@o2.pl">tzieleniewski@o2.pl</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>I am using SER rel 2_0_0 from CVS.<br>I encountered the following situation.<br>My scenario was the following:<br><br>UA -&gt; Application Serwer -&gt; SER -&gt; UA<br><br>1. UA sent an INVITE message to the application server.
<br>2. Application Server changed the Request URI and forwarded statelessly the INVITE message to SER.<br>3. Everything would be ok but SER replied to the Application server instead of the client. Application server changed only the Request URI and nothing else.
<br>Shouldn&#39;t SER sent the response according to the VIA header value??<br>I kindly ask for Your help.<br><br>Below is the ngrep:<br><a href="http://192.168.0.112:5060">192.168.0.112:5060</a> - this is application server
<br><a href="http://192.168.0.112:5061">192.168.0.112:5061</a> - this is calling UA<br><br>U 2007/04/25 16:17:05.652934 <a href="http://192.168.0.112:5060">192.168.0.112:5060</a> -&gt; <a href="http://192.168.0.165:5060">
192.168.0.165:5060</a><br>INVITE <a href="mailto:sip:sen@voip.rd.touk.pl">sip:sen@voip.rd.touk.pl</a> SIP/2.0.<br>Via: SIP/2.0/UDP <a href="http://192.168.0.112:5061">192.168.0.112:5061</a>;rport=5061;branch=z9hG4bKhnrxbtgp;received=
<a href="http://127.0.0.1">127.0.0.1</a>.<br>Max-Forwards: 70.<br>To: &lt;<a href="mailto:sip:sen@voip.rd.touk.pl">sip:sen@voip.rd.touk.pl</a>&gt;.<br>From: &lt;<a href="mailto:sip:pz@voip.rd.touk.pl">sip:pz@voip.rd.touk.pl
</a>&gt;;tag=jlegd.<br>Call-ID: <a href="mailto:pfnqwekjwtuxbfv@192.168.0.112">pfnqwekjwtuxbfv@192.168.0.112</a>.<br>CSeq: 87 INVITE.<br>Contact: &lt;sip:pz@192.168.0.112:5061&gt;.<br>Content-Type: application/sdp.<br>Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO.
<br>Supported: 100rel.<br>User-Agent: Twinkle/0.9.<br>Content-Length: 304.<br>.<br>v=0.<br>o=pz 86411392 1733597180 IN IP4 <a href="http://192.168.0.112">192.168.0.112</a>.<br>s=-.<br>c=IN IP4 <a href="http://192.168.0.112">
192.168.0.112</a>.<br>t=0 0.<br>m=audio 8000 RTP/AVP 98 97 8 0 3 101.<br>a=rtpmap:98 speex/16000.<br>a=rtpmap:97 speex/8000.<br>a=rtpmap:8 PCMA/8000.<br>a=rtpmap:0 PCMU/8000.<br>a=rtpmap:3 GSM/8000.<br>a=rtpmap:101 telephone-event/8000.
<br>a=fmtp:101 0-15.<br>a=ptime:20.<br><br>#<br>U 2007/04/25 16:17:05.699923 <a href="http://192.168.0.165:5060">192.168.0.165:5060</a> -&gt; <a href="http://192.168.0.112:5060">192.168.0.112:5060</a><br>SIP/2.0 407 Proxy Authentication Required.
<br>Via: SIP/2.0/UDP <a href="http://192.168.0.112:5061">192.168.0.112:5061</a>;rport=5060;branch=z9hG4bKhnrxbtgp;received=<a href="http://127.0.0.1">127.0.0.1</a>;received=<a href="http://192.168.0.112">192.168.0.112</a>
.<br>To: &lt;<a href="mailto:sip:sen@voip.rd.touk.pl">sip:sen@voip.rd.touk.pl</a>&gt;;tag=b27e1a1d33761e85846fc98f5f3a7e58.6a45.<br>From: &lt;<a href="mailto:sip:pz@voip.rd.touk.pl">sip:pz@voip.rd.touk.pl</a>&gt;;tag=jlegd.
<br>Call-ID: <a href="mailto:pfnqwekjwtuxbfv@192.168.0.112">pfnqwekjwtuxbfv@192.168.0.112</a>.<br>CSeq: 87 INVITE.<br>Proxy-Authenticate: Digest realm=&quot;<a href="http://voip.rd.touk.pl">voip.rd.touk.pl</a>&quot;, nonce=&quot;462f640d527dfc442d53379e1f0167c8a12a583d&quot;, qop=&quot;auth&quot;.
<br>Server: Sip EXpress router (2.0.0-rc1 (x86_64/linux)).<br>Content-Length: 0.<br>Warning: 392 <a href="http://192.168.0.165:5060">192.168.0.165:5060</a> &quot;Noisy feedback tells:&nbsp;&nbsp;pid=20441 req_src_ip=<a href="http://192.168.0.112">
192.168.0.112</a> req_src_port=5060 in_uri=<a href="mailto:sip:sen@voip.rd.touk.pl">sip:sen@voip.rd.touk.pl</a> out_uri=<a href="mailto:sip:sen@voip.rd.touk.pl">sip:sen@voip.rd.touk.pl</a> via_cnt==1&quot;.<br>.<br><br>Cheers Tomasz
<br>_______________________________________________<br>Serusers mailing list<br><a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a><br><a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers
</a><br></blockquote></div><br><br clear="all"><br>-- <br>&quot;C is a language that combines all the elegance and power of assembly language with all the readability and maintainability of assembly language.&quot;