VoIP NAT: Difference between revisions

From AAISP Support Site
mNo edit summary
mNo edit summary
Line 9: Line 9:
*Disable Stun settings on the VoIP phone (or try enabling it. stun.aa.net.uk can be used)
*Disable Stun settings on the VoIP phone (or try enabling it. stun.aa.net.uk can be used)


If NAT works, then well done, but if not we cannot guarantee to be able to make it work. We can provide broadband lines and public IPs that can be used for VoIP - even multiple lines through different back-haul suppliers for extra resilience. -do speak to us.
If NAT works, then well done, but if not we cannot guarantee to be able to make it work. We can provide broadband lines with constant quality monitoring and public IPs that can be used for VoIP - even multiple lines through different back-haul suppliers for extra resilience. -do speak to us.





Revision as of 16:04, 29 May 2014

NAT on our Voiceless platform does work in many cases. However, due to the nature of NAT, and the numerous implementation and 'fixes' and 'bodges' in routers, it can be tricky to get working. Lots of the phones that we've tested do just work without the need for an ALG, stun, port forwarding etc), but other network equipment (ie the router) may get in the way.

We'd always suggest using public IP addresses for VoIP devices.

If you do want to use NAT, then here are some tips if you are struggling:

  • Disable upnp on routers
  • Disable SIP ALG on the router (Or try enabling)
  • Disable Stun settings on the VoIP phone (or try enabling it. stun.aa.net.uk can be used)

If NAT works, then well done, but if not we cannot guarantee to be able to make it work. We can provide broadband lines with constant quality monitoring and public IPs that can be used for VoIP - even multiple lines through different back-haul suppliers for extra resilience. -do speak to us.