Network Configuration for CTS Hosted VoIP on a Customer-Managed Network
If you are going to manage your own network switches to support CTS Hosted VoIP Phones, there are specific settings that are required to make sure things run smoothly. Advanced assistance in programming your network could be potentially billable, so please take care to understand these configuration options and apply them as necessary.
- POE available
- Router/Firewall: turn off all SIP ALG functions as our equipment will negotiate SDP over NAT.
- Bandwidth Considerations: Upload and download speeds must be adequate to support payload for uncompressed (G711) traffic based on best practices.
- Polycom endpoints must be on the same network segment to support Intercom and Paging as these features require multicast.
- We need to know what VLAN to use when provisioning your phones. Endpoints need to be configured on VLAN 0 if VLAN2 is not supported by your organization. It is preferred to have VoIP devices on a separate “Voice” VLAN to protect from unnecessary broadcast traffic. Public NTP server addresses should also be set on the Business group.
- Customer DNS servers need to resolve sip-p6320.ctsvoice.net correctly.
- DHCP server should be configured for Option 66 to direct the endpoint to our Software Provisioning server. If this is not done, then a factory defaulted endpoint will not be able to download its initial configuration and a technician will have to be dispatched.
- Aastra Phones use https://www.ctsportal.net/sip-ps/
- Polycom VVX use http://www.ctsportal.net/sip-ps/
- Customer-provided SIP endpoints will be accepted on a case-by-case basis and will need technical clearing from the CTS Voice team before registering to our services.
- Customers who have their IT services managed by an outside vendor should ensure that their vendor is available to test and troubleshoot at implementation and should be the first line of support before contacting CTS for device replacements.