nexMatrix SIP trunk service will connect to your IP PBX from one or more of these servers. You may need to whitelist these addresses and/or host names to allow unsolicited inbound traffic from them to your PBX on UDP port 5060 and whatever range of RTP ports your PBX is configured for . For outbound traffic from your PBX, our servers are expecting SIP signaling packets on port 5060 UDP and RTP media streams in the range of 10000 to 20000 UDP.
| DNS Hostname |
Primary IP |
Location |
Provider |
| sip10.nexmatrix.net |
66.135.42.81 |
San Antonio |
Cogeco/Peer 1 |
| sip20.nexmatrix.net |
173.234.233.66 |
New York City |
LeaseWeb |
| sip35.nexmatrix.net |
162.218.102.99 |
Billings |
Parsec Data |
| sip40.nexmatrix.net |
64.34.190.68 |
Dulles |
Cogeco/Peer 1 |
| sip50.nexmatrix.net |
138.68.57.55 |
San Francisco |
Digital Ocean |
If you receive Hosted/Cloud PBX service from nexMatrix, your IP Phones will register to one or more of the servers listed here. In most cases, it is not necessary to forward any ports in your router/firewall, but you may need to add the server address(es) to your firewall white list:
| protelity15.nexmatrix.net |
173.234.62.226 |
Chicago |
LeaseWeb |
| protelity25.nexmatrix.net |
174.34.164.106 |
Chicago |
LeaseWeb |
| protelity45.nexmatrix.net |
69.174.246.32 |
San Antonio |
Cogeco/Peer1 |
| protelity55.nexmatrix.net |
162.218.102.28 |
Billings |
Parsec Data |