Business SIP trunking built around your calls.

A SIP trunk is a connection between your phone system and a carrier that carries voice calls over the internet instead of over physical phone lines. It handles both inbound calls to your business numbers and outbound calls from your extensions.

Your numbers sit with a carrier. The carrier sends calls for those numbers over the internet to your PBX using the SIP protocol, and the PBX routes each call to the right extension, ring group or queue. Outbound calls follow the same path in reverse.

It depends on your destinations, call volume, how many concurrent calls you need, how many inbound numbers you hold and whether you want a second carrier for failover. We price it against your own call records rather than quoting a per minute figure that may have nothing to do with your traffic.

You need a carrier to reach the public telephone network. What you do not need is to accept whichever provider is put in front of you. We compare providers against your traffic and configure the trunk, whoever you end up buying it from.

Yes. FreePBX is one of the most common systems we configure trunks on, including trunk authentication, inbound and outbound routes, dial patterns, codecs and failover. Our FreePBX integration page covers that work in more detail.

Yes. On plain Asterisk the trunk is defined in configuration and routed through your existing dialplan contexts. Everything a FreePBX setup does through its interface can be done directly, which suits systems where call handling has been written rather than configured.

In most cases yes, through number porting. We pull the customer service record, prepare the documentation and schedule the port with the existing service still running. Portability is not guaranteed for every number or every country, so we check before committing to a date.

That is a configured limit rather than a physical one. It depends on the channel limit agreed with the carrier, the bandwidth available on your circuit and the codec in use. Capacity can normally be increased without changing the phone system behind it.

Yes, and for most businesses that matters more than the rate. Two carriers on the same PBX give you a path to fall back to, and let you send different destinations down whichever trunk prices them better.

With a single trunk, calls stop until the carrier recovers. With a secondary carrier and routing rules in place, outbound calls move to the second trunk and inbound numbers can be redirected, usually without anyone having to intervene.

Yes. In practice that means a second carrier, outbound routes in priority order, inbound failover configured at the carrier, and monitoring of trunk state so a failure is detected rather than reported to you by a customer.

They often do, particularly when replacing ISDN or when the current carrier does not suit the destinations you call. Whether they will in your case depends on your call mix, which is why we start from your call records rather than from a promise.

A framework used in the United States to sign outbound calls with an attestation level, indicating how confident the originating carrier is that the caller is entitled to use that number. Terminating networks use it, among other signals, when deciding how to treat a call.

Usually a combination of low attestation, no CNAM registration, and calling patterns that look like a campaign to the analytics engines the mobile networks use. It can be improved, but no provider can guarantee that a network will never label a call.

Not if it speaks SIP. FreePBX, Asterisk and most modern IP PBX platforms accept SIP trunks directly. Replacement is only worth discussing when the system is out of support or cannot do what the business now needs.