Router Support
In general we’ve found that our Private Label VoIP services work well with most commercial routers.
However, please consider that most “off-the-shelf” Residential and SOHO routers usually don’t have the processing power needed to manage several VoIP NAT connections as necessary for multiple VoIP phones, 3+ concurrent calls, and or other resource intensive features like Presence, BLF and QoS.
Although these smaller more affordable routers have been deployed, and in some cases perform well, the high variations in hardware/firmware combinations make them unpredictable and not worth the possible issues they could present.
Below are basic recommendations for any router used in a VoIP implementation.
Note: Most DSL/Cable Modems are configured as routers not bridges. This means your router will be assigned a private or NAT’ed IP resulting in double NAT which almost always causes one way audio and or failed inbound calls. Always double check that your Modem is configured as a Bridge and confirm it yourself.
Firewall Support
Please note that firewalls are not officially supported in VoIP implementations, as such limited assistance is available for these deployments.
In most cases, VoIP services behind a firewall result in several calling issues including but not limited to; failed calls, dropped calls, one way or no audio and more.
VoIP Firewall Best Practices.
VoIP CPE Support
Most VoIP devices will perform properly with basic factory default settings. In addition, if you’re using 3NG’s auto provisioning service any non-factory settings that need to be changed will be automatically adjusted for you.
List of basic settings recommended for all VoIP CPE (IP Phone or IP PBX).