[Devel] t_uac_dlg with nated SIP user agent
Bogdan-Andrei Iancu
bogdan at voice-system.ro
Mon Oct 17 20:27:23 CEST 2005
Hi Juha,
there was a problem in RR module - the info from the second Route (when
doing double routing) was not use to select the proper outgoing socket.
I did a fast and simple fixup - it's on CVS; please let me know if it works.
regards,
bogdan
Juha Heinanen wrote:
>proxy is listening on two
>ports 5060 and 5062 at the same ip address. mhomed is 0,
>because the proxy host has only one ip interface. packet numbers refer
>to the enclosed ethereal dump.
>
>- invite comes into the proxy (packet 17)
>
>- proxy forks it to two sip UAs (packets 20 and 21), but forking is
> irrelevant regarding the problem at hand. lets thus only look at
> packet 21, where proxy correctly forwards the invite a nated callee
> using source port 5062 (because the ua registered to that port).
>
>- callee replies with 200 ok, which proxy forwards to the caller
> (packets 27 and 28).
>
>- caller correctly sends ack to proxy (packet 29).
>
>- after receiving the ack, proxy sends ack to the callee, but source
> port is 5060, when it should be 5062 (packet 30).
>
>- nat is symmetric will not forward ack to the callee, because of wrong
> source port resulting in retransmissions of 200 ok from the callee
> (packet 35 and others).
>
>there exists two route headers in the ack from the caller, which look ok
>to me (packet 29). any ideas why proxy is using wrong source port or is
>it a bug?
>
>-- juha
>
>
More information about the Devel
mailing list