Hi!

On 05/18/2007 05:12 PM, Andreas Granig wrote:

Alexander Bergolth wrote:

...

I've noticed that (at least on my boxes) x-lite uses a different source-port for the sip-connection than the one that is announced in the Via-header. (See the example below.)

Are you sure there isn't any NAT or ALG in between?

I've done the packet dump on both ends, on a box running x-lite (with the windows-firewall disabled) and on the proxy-host. Both show the same source/destination ip-adresses and ports, so I assume there cannot be any kind of ALG.

However, there is some packet filter (not doing NAT) between the box and the proxy, maybe x-lite does some firewall-detection on startup and uses the wrong port-number in the via header intentionally to enforce the use of an rtp-proxy?

I'll do some tests on a box that isn't protected by a packet filter on Monday.

By default, x-lite binds to local port 5060, but you've some non-standard ports in there. So my guess is either a non-standard port setting in x-lite and NAT, or a faulty ALG on the NAT device.

I don't have any special settings in X-Lite, ICE is disabled, "Use local IP address" is enabled.

I've noticed that your version of x-lite uses UDP, mine seems to use TCP by default.

Cheers, --leo

Here's a trace using x-lite 2.0 r1105d (Linux):

U 192.168.123.129:5060 -> <public IP>:5060 REGISTER sip:<some domain> SIP/2.0. Via: SIP/2.0/UDP 192.168.123.129:5060;rport;branch=z9hG4<snip>

Cheers, Andreas