I’m asked this doubt a lot, so we suspicion it’d be a good blog topic.
I don’t consider we are as endangered with this as a amber lights in a server room… But if we are creation any changes to your company’s phone system, I’m presumption this doubt is on your mind.
The elementary answer is… no. SIP trunks are not as reliable. They are more arguable than a Primary Rate Interface (PRI). But it has zero to do with a open Internet.
When we consider of SIP trunking, we might consider it refers to promulgation phone calls over your company’s open Internet connection. Which is one approach of delivering SIP calls to your phone system. And you’re right, this process is about as arguable as your child, revelation we their room is clean.
The other approach we can broach SIP calls to your phone complement is over a Dedicated Circuit. When we have SIP trunks delivered this way, trustworthiness and call peculiarity are a exact same as an ISDN PRI T1.
So because do we contend SIP is more reliable? Four reasons.
More failover routes
With SIP, your association can have dual or some-more pre-determined IP addresses or phone numbers to failover incoming calls to, if a primary end is down. More failover routes means a aloft odds of uptime.
With PRI, your association can customarily have one pre-determined phone number to failover incoming calls.
For example, we can pre-program your company’s incoming calls to track to: (1) your company’s dedicated SIP circuit; Then (2) your company’s primary Internet connection; Then (3) your company’s backup Internet connection; And afterwards (4) another association site or phone number.
You’ll have so many routes, your dedicated circuit could be down for years though we even noticing! Ahhhh, yes… a telecom broker’s dream.
More failover call capacity
If your company’s PRI provider allows we to auto-failover incoming calls, we are always singular (by cost), on a volume of coexisting calls you’re means to forward, during a failover situation. This is because:
- Your association contingency compensate your PRI provider a monthly repeated cost (every month), for failover call paths (for any coexisting call), we need forwarded, regardless either your association ever uses a failover.
- Your association contingency compensate for a fill-in analog POTS lines (your PRI will brazen calls to), any singular month, regardless of either they’re used.
As a result, many companies typically customarily have 4 POTS lines and 4 call failover paths, per PRI T1. This means if your PRI goes down, customarily 4 calls can be perceived and a 5th will accept a bustling signal.
With SIP Trunking (since calls are typically forwarding to a open Internet connection), there isn’t a extent on a series of coexisting calls your association is means to forward. Depending on a SIP provider’s codec, any call customarily uses 32k to 100k of bandwidth from your Internet connection. More ability means no business job in, removing bustling signals.
Assuming your association is in a U.S., with SIP trunking, your pre-determined failover end can be anywhere in a country. With PRI, a pre-determined failover phone series contingency be internal to a area where your PRI is installed.
This SIP capability is good if we wish to send calls to another partial of a U.S., while your side of a nation deals with some complicated drama.
DID routing forwards with calls
In a eventuality of an outage, with PRI, (when forwarding incoming calls), all DID routing is lost. All calls only strike a singular phone series we gave a provider (usually one of a backup analog POTS lines), and your callers are wondering because their call went to a accepting table instead of to Sharon.
Side benefit: This is a discerning approach to see how many personal calls people are taking. [maniacal laughter]
When SIP calls are forwarded, however, a calls can keep their DID routing. This is a good underline if we have a lot of employees with DID’s and incoming call routing is vicious to your business (i.e. lots of salespeople, etc.).
See what we mean? ISDN PRI still works excellent though it simply can't contest with a DR capability of SIP trunking. There is no denying SIP calls will accept reduction bustling signals if configured correctly.
Another Service Provider Secret revealed. Don’t be shy. Hit me adult with your thoughts or questions.
This essay is published as partial of a IDG Contributor Network. Want to Join?