Plan requirement
| Subscription | Any plan |
| Access | WMS administrator |
Your system comes with our own multi-carrier connections. Calls route over whichever premium carrier is performing best at that moment, and inbound numbers registered with us sit on premium carriers only. That is the arrangement most customers should keep, and it is why a carrier having a bad hour usually goes unnoticed.
When your own trunk makes sense
- You have an existing contract you cannot or will not exit yet.
- A country or number type we do not carry.
- A group arrangement that already covers telephony.
Outside those, bringing your own carrier costs you the automatic routing and gains you little.
Your carrier may already be tested
Wildix keeps a list of VoIP operators it has tested, covering the United States, Canada, Italy, Germany, France, Switzerland, the Netherlands, Austria, Spain and the United Kingdom. If yours is on that list the groundwork is done and the settings are known. If it is not, it has to be tested first, and that is work rather than a formality: skipping it means finding the gaps during a customer call.
Tell us which carrier you are considering and we will check the list for you.
What to get from your carrier
Whether or not it is on the list, the same details are needed, and asking for them early is the quickest way to find out whether the carrier can deliver what you want.
| What to ask for | Why it matters |
| Auth login and password | How the trunk authenticates. Without both, nothing registers. |
| SIP proxy address or host name | Where calls are sent. Ask whether it is a fixed address or whether the carrier registers towards you. |
| From user and from domain | What goes in the SIP headers. Often the same as the auth login, but not always, and a mismatch is a common cause of rejected calls. |
| Whether outbound registration is used | Decides how the trunk is set up on our side. |
| The country the trunk is used in | The country code drives number normalisation. Wrong here and numbers arrive in a format nothing matches. |
What changes about support
This is the part to be clear-eyed about. On your own trunk, the carrier relationship is yours. We monitor trunks that register with us and we will tell you when one goes unavailable, but resolving it is between you and your carrier. A fault that we would normally route around becomes an outage you have to chase.
Where quality problems come from
Robotic audio, one-way sound and dropped calls on a customer trunk usually come from the same short list: the connection between your network and the carrier, a firewall interfering with the media, or capacity on the trunk itself.
Our network requirements apply just as much here. A trunk that is fine in isolation still fails behind a firewall that inspects voice traffic.
Comments
0 comments
Article is closed for comments.