Plan requirement
| Subscription | Any plan |
Calling in a browser needs specific connections allowed. On a filtered network this is what to check before anything else.
Who this is for
Most offices need nothing. If your network allows normal outbound web traffic, calling works.
This matters where a firewall blocks by default, where traffic is inspected, or on a guest network that only permits web browsing.
The symptoms
Blocked connections rarely produce a clear error. What you see instead:
- The interface loads and signs in fine, but calls have no audio
- Audio works one way only
- Calls connect and drop after a few seconds
- It works at home and not in the office, or on mobile data and not on Wi-Fi
That last one is the strongest signal. If a phone works on mobile data but not on office Wi-Fi, the network is filtering something.
Test on mobile data before opening a ticket. It takes ten seconds and tells you whether to talk to us or to your network administrator.
Getting the list
Rather than working from generic documentation, ask us for the list that applies to your setup. It differs depending on which products you run and whether you use CLASSOUND.
Send it to whoever manages your firewall. It is a short list.
The ports
This is the general list. Which of it applies depends on what you run, so check with us before opening everything.
| TCP 443, TCP 80 | The web interface and everything that runs over HTTPS. |
| TCP 5060, 5061, 5080 and UDP 5060 | SIP, which is how the desk phones and trunks register and set up calls. |
| UDP 10000 to 59999 | The audio itself. A wide range, and the one that gets missed. |
| TCP 2195 to 2196, 5222 to 5223 | Push notifications for the iOS app only. |
| TCP 5228 to 5230 | Push notifications for the Android app only. |
| TCP 5269 | Group chats only. |
| TCP 5280, TCP 7008 | Supporting services, including text messaging. |
| UDP 9000 to 9001 | Multicast paging only. |
The audio range is where calls break. Signalling on 5060 is a small amount of traffic and usually gets through; the media on the wide UDP range is what carries the voice. Calls that connect and then have no sound in one direction are almost always this.
Your own hostname
Each PBX has its own address, in the form yourcompany.wildixin.com. Where your firewall works on addresses rather than names, ask us for the IP address that belongs to your system.
Deep packet inspection
Firewalls that inspect and re-sign encrypted traffic frequently break real-time audio even when everything is technically allowed. If your network does this, an exception is usually needed rather than a rule change.
Wi-Fi first
Before assuming a firewall problem, rule out the wireless network. Weak signal and roaming between access points cause audio problems that look identical to blocked traffic. Test on a cable if you can.
Comments
0 comments
Article is closed for comments.