[Freeswitch-users] nat problem!

[Brian West]

On May 27, 2010, at 11:39 AM, babak yakhchali wrote:

> finally I found out what the scenario is:
> I captured packets on registration and I found out when registering, freeswitch uses port 5060 as destination even if incoming udp packets are from ports other than 5060.
> but during the call freeswitch uses the source port of the incoming packet and the problem arises.

That is why the client needs to enable rport.  because when they register I suspect the contact said 5060 in it.  We tend to do exactly what you tell us in the contact field unless rport is on.

> Is there anyway that I can force freeswitch to always use the port specified in via header?

NDLB-force-rport on the profile but that can break some devices.

> thanx