...
| Info |
|---|
Due to the dynamic nature of Sharpen infrastructure, whitelisting is not recommended. The following items may be changed without advance notice. |
...
Domain
...
Protocol/Port
...
Purpose
...
*.sharpencx.com
...
TCP: 80,443,8089,8090
...
Main app
...
*.sharpen.cx
...
TCP: 443
...
Supplemental main app
...
*.cx.shpn.co
...
TCP: 443
...
CX and VCX
...
*.sipvbx.com
...
UDP: 5060
...
SIP registration
...
*.fathomvoice.com
...
TCP: 443,9002
UDP: 10000-20000
...
Legacy api domain, webRTC registration
RTP media
...
Universal Domains
Access to these domains need to be open regardless of which isolation zone (IZ0,IZ1) your account is built in.
| Expand |
|---|
|
Domain | Protocol/Port | Purpose |
|---|
*.s3.amazonaws.com | TCP: 443 | Long-term audio and image file storage | stun.l.google.com | UDP: 19302 | WebRTC STUN server | stun1.l.google.com | UDP: 19302 | WebRTC STUN server | stun2.l.google.com | UDP: 19302 | WebRTC STUN server | stun3.l.google.com | UDP: 19302 | WebRTC STUN server | stun4.l.google.com | UDP: 19302 | WebRTC STUN server | *.yealink.com | TCP: 443 | Yealink auto-provisioning | *.ckeditor.com | TCP: 443 | Visual editor/UI library | *.loggly.com | TCP: 443 | Logging | *.pendo.io | TCP: 443 | Analytics and logging | *.ingest.io | TCP: 443 | Client logging | *.gstatic.com | TCP: 443 | Font library | *.googleapis.com | TCP: 443 | Font library | *. |
|
...
fortawesome.com | TCP: 443 | Font library |
|
Isolation Zone Domains
Access to these domains should be open with respect to which isolation zone your account is built in.
Isolation Zone 0 | Your users login to app.sharpencx.com
| Expand |
|---|
| title | IZ0 (app.sharpencx.com) Domain Details |
|---|
|
Domain | Protocol/Port | Purpose |
|---|
*.sharpencx.com | TCP: 443,8089,8090 | App | *.sharpen.cx | TCP: 443 | Supplemental app domain | *.cx.shpn.co | TCP: 443 | CX and VCX | *.sipvbx.com | UDP: 5060 | SIP registration and signaling | *.fathomvoice.com | TCP: 80,443,9002
UDP: 10000-20000 | Provisioning, API, webRTC registration
RTP media |
|
Isolation Zone 1 | Your users login to app.iz1.sharpen.cx
| Expand |
|---|
| title | IZ1 (app.iz1.sharpen.cx) Domain Details |
|---|
|
Domain | Protocol/Port | Purpose |
|---|
*.iz1.sharpen.cx | TCP: 80,443,8089,8090,9002
UDP: 5060 | Provisioning, app, webRTC registration
SIP registration and signaling | *.cx-iz1.shpn.co | TCP: 443 | CX and VCX |
|
If whitelisting by IP is necessary, the following ranges/addresses apply. *IPs subject to change.
| Expand |
|---|
|
54.148.191.0/24 | 18.214.5.180 | 35.158.26.231 | 52.15.147.167 | 52.20.148.224 | 52.77.254.206 | 54.206.39.164 | 54.209.81.22 | 54.77.58.54 | 54.91.211.210 | 54.173.127.0/24 | 18.215.76.125 | 50.112.144.88 | 52.15.76.70 | 52.66.64.126 | 52.91.230.27 | 54.208.177.217 | 54.65.54.117 | 54.77.95.125 | 54.93.180.13 | 107.20.84.56 | 35.154.184.39 | 52.14.157.193 | 52.15.86.252 | 52.66.66.61 | 54.165.169.174 | 54.208.217.176 | 54.76.26.255 | 54.84.172.227 | 54.94.245.133 | 107.23.101.107 | 35.154.209.148 | 52.14.253.217 | 52.16.3.217 | 52.74.101.155 | 54.169.184.3 | 54.208.88.191 | 54.76.35.133 | 54.85.33.54 | 13.54.48.191 | 107.23.40.94 | 35.156.15.138 | 52.14.30.147 | 52.17.4.111 | 52.74.73.150 | 54.187.125.18 | 54.209.197.93 | 54.77.168.19 | 54.85.60.149 | 52.62.8.34 | 13.236.115.208 | 3.104.84.131 | 52.62.30.18 | 52.17.219.38 | 52.17.29.105 | 23.21.26.240 | 3.212.89.84 | 3.82.182.42 | 34.196.245.252 | 35.172.172.112 | 52.200.241.100 | 52.7.126.239 | 3.219.165.98 | 35.153.197.62 | 52.7.61.33 | 52.203.75.253 | 54.225.184.101 | 34.193.241.162 | 34.205.49.94 | 54.87.30.176 | 107.22.254.243 | 52.5.76.81 | 54.235.189.62 | 23.21.193.93 | 54.146.138.47 | 3.82.140.190 | 18.204.61.135 | 184.73.214.192 | 54.157.9.182 | 35.174.79.112 | 18.215.195.239 | 23.23.74.83 | 18.205.175.46 | 3.91.123.104 | 3.228.252.37 | 54.158.183.188 | 3.210.20.3 | 35.173.79.56 | | |
Yealink Provisioning | 52.71.103.102, 35.156.148.166, 106.15.89.161, 47.75.58.202, 47.89.187.0 |
|
Prioritization
Use Quality of Service to maintain prioritization
Many devices support Quality of Service (QoS) tags to maintain traffic priority across the network. It is beneficial to tag your voice traffic with the appropriate tags, so it can be prioritized anywhere in the network in the event of a saturated link. This will help to prevent any audio issues caused by voice and data competing for the same bandwidth over your internet connection.
...
Protocol | Port Range | Priority |
|---|
UDP | 10000-20000 | DSCP 46 - EF
DSCP 56 - CS7 (for webRTC) |
UDP | 5060-5081 | DSCP 46 - EF | TCP | 5060-5081 | DSCP 46 - EF |
Protocols
...