[Serusers] Ser2.0 wrong behaviour of the sl_reply() function?

Weiter Leiter bp4mls at googlemail.com
Fri Apr 27 08:55:20 CEST 2007


Replies take the same path as requests, no matter what kind of proxy there
were on the way.
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't even look at
that Via.

WL.

On 4/25/07, tzieleniewski <tzieleniewski at o2.pl> wrote:
>
> Hi,
>
> I am using SER rel 2_0_0 from CVS.
> I encountered the following situation.
> My scenario was the following:
>
> UA -> Application Serwer -> SER -> UA
>
> 1. UA sent an INVITE message to the application server.
> 2. Application Server changed the Request URI and forwarded statelessly
> the INVITE message to SER.
> 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.
> Shouldn't SER sent the response according to the VIA header value??
> I kindly ask for Your help.
>
> Below is the ngrep:
> 192.168.0.112:5060 - this is application server
> 192.168.0.112:5061 - this is calling UA
>
> U 2007/04/25 16:17:05.652934 192.168.0.112:5060 -> 192.168.0.165:5060
> INVITE sip:sen at voip.rd.touk.pl SIP/2.0.
> Via: SIP/2.0/UDP 192.168.0.112:5061
> ;rport=5061;branch=z9hG4bKhnrxbtgp;received=127.0.0.1.
> Max-Forwards: 70.
> To: <sip:sen at voip.rd.touk.pl>.
> From: <sip:pz at voip.rd.touk.pl>;tag=jlegd.
> Call-ID: pfnqwekjwtuxbfv at 192.168.0.112.
> CSeq: 87 INVITE.
> Contact: <sip:pz at 192.168.0.112:5061>.
> Content-Type: application/sdp.
> Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO.
> Supported: 100rel.
> User-Agent: Twinkle/0.9.
> Content-Length: 304.
> .
> v=0.
> o=pz 86411392 1733597180 IN IP4 192.168.0.112.
> s=-.
> c=IN IP4 192.168.0.112.
> t=0 0.
> m=audio 8000 RTP/AVP 98 97 8 0 3 101.
> a=rtpmap:98 speex/16000.
> a=rtpmap:97 speex/8000.
> a=rtpmap:8 PCMA/8000.
> a=rtpmap:0 PCMU/8000.
> a=rtpmap:3 GSM/8000.
> a=rtpmap:101 telephone-event/8000.
> a=fmtp:101 0-15.
> a=ptime:20.
>
> #
> U 2007/04/25 16:17:05.699923 192.168.0.165:5060 -> 192.168.0.112:5060
> SIP/2.0 407 Proxy Authentication Required.
> Via: SIP/2.0/UDP 192.168.0.112:5061
> ;rport=5060;branch=z9hG4bKhnrxbtgp;received=127.0.0.1;received=
> 192.168.0.112.
> To: <sip:sen at voip.rd.touk.pl>;tag=b27e1a1d33761e85846fc98f5f3a7e58.6a45.
> From: <sip:pz at voip.rd.touk.pl>;tag=jlegd.
> Call-ID: pfnqwekjwtuxbfv at 192.168.0.112.
> CSeq: 87 INVITE.
> Proxy-Authenticate: Digest realm="voip.rd.touk.pl",
> nonce="462f640d527dfc442d53379e1f0167c8a12a583d", qop="auth".
> Server: Sip EXpress router (2.0.0-rc1 (x86_64/linux)).
> Content-Length: 0.
> Warning: 392 192.168.0.165:5060 "Noisy feedback tells:  pid=20441
> req_src_ip=192.168.0.112 req_src_port=5060 in_uri=sip:sen at voip.rd.touk.plout_uri=
> sip:sen at voip.rd.touk.pl via_cnt==1".
> .
>
> Cheers Tomasz
> _______________________________________________
> Serusers mailing list
> Serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>



-- 
"C is a language that combines all the elegance and power of assembly
language with all the readability and maintainability of assembly language."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20070427/5c2a769a/attachment.htm>


More information about the sr-users mailing list