Introduction
Before Pilot Voice can get up and running, it’s important to have your business’s firewalls and ports provisioned correctly. We'll need to ensure everything is setup prior to Voice activation so you can place and receive phone calls right away.
Some routers/firewalls use a legacy setting called Session Initiation Protocol Application Layer Gateway or SIP ALG for short. This needs to be turned off for Pilot Voice to work optimally.
To get started, make sure Voice traffic is allowed from these IP addresses:
IP addresses for Voice services
IP address |
SIP feature servers for region |
162.217.10.0/24 |
ATL cluster |
70.42.220.0/24 |
NYJ cluster |
70.42.142.0/24 |
SJE cluster |
IP addresses for additional features
IP address |
Feature and cluster region |
162.217.10.21 |
Primary web portal ATL |
162.217.10.24 |
Primary provisioning server ATL |
TCP and UDP ports
Ports |
Use |
TCP ports 80 and 443 |
Web UIs and provisioning servers |
TCP & UDP port 5060 |
SIP signaling |
UDP port 8889 |
Web Meetings and Video Conferences |
UDP ports 20000-37999 |
RTP |
Required Ports and Trusted IP Addresses and Hosts for Poly Phones
This table lists the open ports on the PDMS-SP. The ports are required by Polycom OBi devices.
Protocol |
Port |
Direction |
TCP |
6800 |
out |
TCP |
5222 |
out |
TCP |
5223 |
out |
UDP |
5060 |
out |
UDP |
5061 |
out |
UDP |
10000 to 11000 |
out |
UDP |
16600 to 16998 |
out |
UDP |
19305 |
out |
UDP |
10000 |
in |
PDMS-SP Trusted IP Addresses
This section lists the PDMS-SP IP addresses and hosts you should trust, which include on the on-site ACL. These IP addresses are the pieces that connects the devices to the PDMS-SP cloud in its peer-to-peer (P2P) fashion. Fundamentally, the P2P network is responsible for sending and receiving messages and commands to and from the device. Functions are listed as follows:
- OBi-to-OBi calling (for OBi Edition only)
- Media loopback calls to another OBi (for OBi Edition only)
- Online/Offline Status
- Registration Status
- Firmware Version
- Reboot
- Local Factory Reset
- Interactive Local Webpage
- Voice Echo Test
- Activation Codes
- Everything else that is used to check phone status and update instances on the device.
Trusted IP Address |
UDP/TCP |
TLS |
13.52.69.0 |
10000 to 20000 |
443 |
13.56.185.145 |
10000 to 20000 |
443 |
13.57.121.193 |
10000 to 20000 |
443 |
54.241.91.173 |
10000 to 20000 |
443 |
54.241.160.4 |
10000 to 20000 TCP: 6800 |
443 |
54.241.163.234 |
10000 to 20000 |
443 |
54.67.107.54 |
10000 to 20000 |
443 |
54.67.113.163 |
10000 to 20000 |
443 |
54.219.101.213 |
10000 to 20000 |
443 |
52.52.249.241 |
10000 to 20000 |
443 |
52.53.96.55 |
10000 to 20000 |
443 |
52.9.223.41 |
10000 to 20000 |
443 |
52.9.225.203 |
10000 to 20000 |
443 |
PDMS-SP Provisioning Trusted Hosts
These set of FQDNs enable the phone does a combination of essential cloud-management pieces (applicable for OBi Edition only):
Trusted Host |
Description |
www.obitalk.com www1.obitalk.com |
HTTP/HTTPS Required Essential pieces in cloud troubleshooting and general connectivity features, including performing remote syslogs, and PCAPs. |
prov.obitalk.com |
HTTP/HTTPS Required Allow Zero-Touch customization responsible for phone onboarding. |
devpfs.obitalk.com |
HTTP/HTTPS Required For Device Profiles, part of ZT customization to match phone ID with the cloud. |
api.obitalk.com |
HTTP/HTTPS Optional To access the APIs from your PC or app that manages PDMS-SP. No need to whitelist on the device’s network. |
fw.obitalk.com |
HTTP Optional Download firmware from the website. This is optional but future-proof. |
