Contact Center Pro network recommendations and setup

Overview

Explore the recommended network options for Contact Center Pro and learn how to choose the best setup for optimal performance. You'll find a list of required ports, protocols, and FQDNs to help you properly configure your network for Contact Center Pro.

Things to know

• Contact Center Pro does not work on satellite internet. Voice over Internet Protocol (VoIP) calls need a fast, steady internet connection. Satellite internet has a long delay because the signal has to travel to space and back, and it's more likely to fluctuate due to weather or congestion. As a result, calls can have long pauses, sound choppy/robotic, or drop. This limitation applies to any VoIP platform, not just Contact Center Pro.

• Contact Center Pro does not support virtual private networks (VPNs). If your company uses a VPN, set up a split tunnel and direct ServiceTitan traffic outside of the VPN.

• You can use a virtual LAN (VLAN) to manage security and routing policies. You can also use a voice VLAN for security purposes.        

  Note: You are required to set up a voice VLAN when workstations are linked together through IP phones.

• For better voice quality, we recommend using a high-speed DSL, cable, or fiber-optic connection with dedicated upload and download bandwidth for the voice of at least 100 kilobits/second for each voice line you plan to run.

• Be aware that remote agents may experience different network behaviors than agents at the main office. Ensure that all locations — including remote workstations — meet the network requirements described in this article.

Set wired connections

Wired connections provide the best quality experience. Your network should use cabling that meets the network speed specifications.

Set wireless connections

If you use a wireless connection, be aware of the following issues:

• Physical obstructions

• Channel congestion

• Electromagnetic interference

• Multiple Wi-Fi bandwidth frequencies

• Type of frequency for wifi connection

Router options

Contact Center Pro supports network routers, switches, and firewalls. Make sure your network hardware supports the following features:

• Quality of service (QoS)

• Bandwidth limiting

• Simple Network Management Protocol (SNMP)

We recommend turning off the following features:

• Session Initiation Protocol Application Layer Gateway (SIP-ALG)

• Deep Packet Inspection (DPI)

• Stateful Packet Inspection (SPI)

Enable QoS

For supported routers, you can configure QoS settings based on:

• Application (RTP/SIP)

• Application and port (RTP over UDP)

• Destination port

• Combination of the options listed above

Fully Qualified Domain Name (FQDN) Whitelisting

Routing to a Fully Qualified Domain Name (FQDN) allows modern Cloud Networks flexibility for Routing, Security, System Maintenance, and remote Device management.

Contact Center Pro uses FQDNs for:

• Registration

• Exchanging SIP to set up a call

• Managing Device Firmware

• Managing Device Configurations

• Managing Devices remotely

Caution: If your organization has complex network configuration, enterprise-grade VPN system, or strict outbound firewall rules, you must ensure that you whitelist the Contact Center Pro IP addresses before onboarding or infrastructure migrations. Failure to do so will cause your local network to result in call set up failures and/or media timeouts on your inbound and outbound calls.

Key things to know about whitelisting:

• Whitelisting IP changes must be made entirely on your side. ServiceTitan cannot make these changes on your behalf.

• If the person performing the migration is not the same person who manages your network, coordinate with your network IT administrator before proceeding.

• If your business has remote agents, each remote location may require its own whitelisting configuration. Work with your local IT administrator to ensure everyone is set up properly prior to onboarding or migrations.

How to tell if you need whitelisting:

If you experience media timeouts (unable to hear the caller, unable to dial out and be heard) on inbound or outbound calls after onboarding or infrastructure migrations, your firewall may be blocking Contact Center Pro traffic. Contact your network administrator to verify firewall rules and whitelist the FQDNs listed in the FQDNs section of this article.

Tip: We recommend verifying your network configuration after onboarding and migrations by attempting a test call from your environment. If the media does not connect, work with your network administrator to update firewall rules to prevent intermittent call issues.

Contact Center Pro recommended FQDNs

Caution: Contact Center Pro is migrating from Azure to OCI (Oracle Cloud Infrastructure). The OCI FQDNs below are new and must be whitelisted before your migration date. We recommend keeping both your existing Azure FQDNs and the new OCI FQDNs active until your migration is fully complete.

New: OCI FQDNs

App servers

• app01.aza.phones.servicetitan.com [132.226.156.160]

• app02.aza.phones.servicetitan.com [152.70.137.240]

• app01.mdw.phones.servicetitan.com [170.9.244.181]

• app02.mdw.phones.servicetitan.com [64.181.214.64]

• app01.dca.phones.servicetitan.com [157.151.156.32]

• app02.dca.phones.servicetitan.com [129.80.46.195]

Kamailio servers

• kam01-aza.phones.servicetitan.com [152.70.134.161]

• kam02-aza.phones.servicetitan.com [132.226.118.57]

• kam03-aza.phones.servicetitan.com [129.153.100.191]

• kam04-aza.phones.servicetitan.com [144.24.30.87]

• kam01-mdw.phones.servicetitan.com [170.9.231.15]

• kam02-mdw.phones.servicetitan.com [163.192.212.9]

• kam03-mdw.phones.servicetitan.com [64.181.194.33]

• kam04-mdw.phones.servicetitan.com [170.9.246.2]

• kam01-dca.phones.servicetitan.com [129.153.234.28]

• kam02-dca.phones.servicetitan.com [152.70.197.111]

• kam03-dca.phones.servicetitan.com [150.230.162.118]

• kam04-dca.phones.servicetitan.com [129.153.141.146]

Freeswitch servers

• fs01.aza.phones.servicetitan.com [158.101.34.13]

• fs02.aza.phones.servicetitan.com [161.153.43.240]

• fs03.aza.phones.servicetitan.com [141.148.177.187]

• fs04.aza.phones.servicetitan.com [152.70.157.220]

• fs01.mdw.phones.servicetitan.com [163.192.120.116]

• fs02.mdw.phones.servicetitan.com [163.192.124.27]

• fs03.mdw.phones.servicetitan.com [163.192.219.199]

• fs04.mdw.phones.servicetitan.com [163.192.101.44]

• fs01.dca.phones.servicetitan.com [129.80.207.15]

• fs02.dca.phones.servicetitan.com [129.80.102.233]

• fs03.dca.phones.servicetitan.com [129.80.148.26]

• fs04.dca.phones.servicetitan.com [143.47.119.245]

Database servers

• db01.aza.phones.servicetitan.com [161.153.50.209]

• db02.aza.phones.servicetitan.com [137.131.59.168]

• db03.aza.phones.servicetitan.com [141.148.157.229]

• db04.aza.phones.servicetitan.com [141.148.177.127]

• db05.aza.phones.servicetitan.com [161.153.23.142]

• db01.mdw.phones.servicetitan.com [64.181.211.196]

• db02.mdw.phones.servicetitan.com [64.181.200.183]

• db03.mdw.phones.servicetitan.com [64.181.211.90]

• db04.mdw.phones.servicetitan.com [64.181.194.41]

• db05.mdw.phones.servicetitan.com [207.211.172.228]

• db01.dca.phones.servicetitan.com [129.153.40.121]

• db02.dca.phones.servicetitan.com [129.153.176.4]

• db03.dca.phones.servicetitan.com [129.153.19.177]

• db04.dca.phones.servicetitan.com [129.80.127.13]

• db05.dca.phones.servicetitan.com [129.158.237.172]

Push servers

• push01.aza.phones.servicetitan.com [161.153.61.89]

• push01.mdw.phones.servicetitan.com [163.192.106.153]

• push01.dca.phones.servicetitan.com [129.158.217.244]

Push DB servers

• pushdb01.aza.phones.servicetitan.com [161.153.29.24]

• pushdb01.mdw.phones.servicetitan.com [170.9.247.166]

• pushdb01.dca.phones.servicetitan.com [157.151.161.214]

RabbitMQ servers

• rabbit01.aza.phones.servicetitan.com [129.153.67.89]

• rabbit02.aza.phones.servicetitan.com [137.131.57.12]

• rabbit01.mdw.phones.servicetitan.com [170.9.235.204]

• rabbit02.mdw.phones.servicetitan.com [207.211.175.99]

• rabbit01.dca.phones.servicetitan.com [129.80.200.118]

• rabbit02.dca.phones.servicetitan.com [157.151.195.21]

Rsyslog servers

• rsyslog01.aza.phones.servicetitan.com [137.131.55.220]

• rsyslog01.mdw.phones.servicetitan.com [163.192.209.5]

• rsyslog01.dca.phones.servicetitan.com [129.80.146.211]

Old: Azure FQDNs

App servers

• app01.eat.phones.servicetitan.com [52.143.127.217]

• app02.eat.phones.servicetitan.com [52.247.244.50]

• app01.sfo.phones.servicetitan.com [52.160.86.147]

• app02.sfo.phones.servicetitan.com [52.160.86.227]

• app01.phx.phones.servicetitan.com [4.242.235.8]

• app02.phx.phones.servicetitan.com [4.242.235.86]

Kamailio servers

• kam01.eat.phones.servicetitan.com [52.148.139.234]

• kam02.eat.phones.servicetitan.com [52.148.138.74]

• kam03.eat.phones.servicetitan.com [52.148.138.233]

• kam04.eat.phones.servicetitan.com [52.148.140.1]

• kam01.sfo.phones.servicetitan.com [13.91.126.130]

• kam02.sfo.phones.servicetitan.com [13.91.125.143]

• kam03.sfo.phones.servicetitan.com [13.91.131.64]

• kam04.sfo.phones.servicetitan.com [13.93.165.12]

• kam01.phx.phones.servicetitan.com [4.236.125.44]

• kam02.phx.phones.servicetitan.com [4.236.124.235]

• kam03.phx.phones.servicetitan.com [4.236.125.110]

• kam04.phx.phones.servicetitan.com [4.236.121.150]

Freeswitch servers

• fs01.eat.phones.servicetitan.com [20.190.32.67]

• fs02.eat.phones.servicetitan.com [20.190.35.108]

• fs03.eat.phones.servicetitan.com [20.190.36.73]

• fs04.eat.phones.servicetitan.com [52.247.254.199]

• fs01.sfo.phones.servicetitan.com [52.160.87.12]

• fs02.sfo.phones.servicetitan.com [52.160.80.23]

• fs03.sfo.phones.servicetitan.com [52.160.80.16]

• fs04.sfo.phones.servicetitan.com [52.160.85.189]

• fs01.phx.phones.servicetitan.com [4.242.235.228]

• fs02.phx.phones.servicetitan.com [4.242.235.239]

• fs03.phx.phones.servicetitan.com [4.242.235.153]

• fs04.phx.phones.servicetitan.com [4.242.235.123]

Note: Contact Center Pro traffic is flagged with Differentiated Services Code Point (DSCP) markings (DSCP 46 = RTP Traffic, DSCP 26 = SIP Traffic).

Ports and protocols

See the table below for recommended ports and protocols:

Note: If you have outbound port restrictions, make sure you have Port 10000 to 20000 open under Protocol UDP/TCP.

Want to learn more?

• See Contact Center Pro

• See Disable SIP ALG to improve ServiceTitan call quality

• See Best practices for optimal VoIP experience and reliability

• See Set call routing rules in Contact Center Pro