configuring endpoints to use a particular port for RTP and then forwarding a range of ports for each endpoint
Guessing this is how you're working around the fact the external RTP port won't be the same as the internal one through most NAT implementations. Seems an awful lot of work to go to when it'd be easier to configure a client correctly (assuming they support NAT correctly). A lot of work for you to setup and maintain, and that won't scale well. If the clients can't support NAT correctly you could try using the SIP ALG on the NAT router (if available) which should rewrite the RTP IP/port automatically. Usually the advice is to disable that and let FS & the client handle the NAT (because generally it just causes more problems if you're handling the NAT twice). But in the bypass_media case it might help. Does mean you can't use TLS though (since the router can't see inside the encrypted packets), and it'll probably only spot SIP on port 5060. -Steve On 21 November 2012 20:11, PhilQ <philq@qsystemsengineering.com> wrote:
configuring endpoints to use a particular port for RTP and then forwarding a range of ports for each endpoint