This does not make any sense.  It limits outbound connections based on source port?  rport would make us tell the guy the port he DID come from, so the nat mapping is in place and working because we got the packet from that port.

On Apr 14, 2010, at 10:50 AM, Jonas Gauffin wrote:

Most of my customers have forwarded ports in their firewalls/routers. Those ports will not be used if rport is turned on.

I currently got a problem with a customer  who is using an old Windows 2000 server as firewall/router. It wont let packets through when using rport. It would work if rport was turned off and all communication was done using the configured port.

On Wed, Apr 14, 2010 at 3:53 PM, Brian West <brian@freeswitch.org> wrote:
You want rport otherwise NAT HELL will begin.

/b

On Apr 14, 2010, at 8:11 AM, Jonas Gauffin wrote:

> Well, yes. But snom can only turn off rport through provisioning and only in the latest firmware.
>
> It would be great if it could be turned off in FS too, per user account.