Peace of mind when porting
toll free to us
Before you port-in your numbers to DID Logic, our Provisioning team works directly with your IT and Engineering teams to create a highly available, completely reliable SIP setup. You can rest easy knowing that your inbound DID trunk is just as reliable as the traditional telephone service.
Three delivery options available
1. Directly to your static IP address via SIP URI. For example, email@example.com The instant the number ports, your PBX answers the calls just like it did on the loosing carrier (as long as you have inbound rules created). When configured correctly, this setup is practically indestructible.
SIP INVITE example:
184.108.40.206 SIP.LAX 2016/06/12
INVITE sip:firstname.lastname@example.org SIP/2.0
From: "James M." sip:+email@example.com;tag=as3bf610bb
CSeq: 102 INVITE
Many customers with 24/7 ops (finance, medical or travel) use two independent systems with DNS SRV. This feature allows you to use two separate redundant PBX systems and instantly reroute voice traffic. DNS SRV entries can return several IPs, by order of priority, on a specific port. For example, sip.domain.com SIP 5060 can have DNS SRV entries of: 220.127.116.11 and 18.104.22.168, two independent systems at different IPs. If you point your DID to a DNS SRV based hostname, our system will instantly detect failure on primary IP and will replace that entry with 2nd entry from your DNS SRV.
You can have more than 2 entries of course and more than 2 IPs associated with the hostname. Failure detection is nearly instant and our proxy will keep distributing calls to IPs that are live and respond. You only need to point to 1 hostname on our end. By managing DNS SRV on your end, you can have health checks and call distribution required.
2. To your SIP endpoint actively registered to DID Logic. Any IP PBX capable of SIP registration can be used to route your DID number. The SIP REGISTER method can be used on 3CX, FreeSwitch, Asterisk and many other office PBXes.
Registration string example:
3. Forwarded to PSTN. You can forward your DIDs to domestic or international phone numbers. This option can be used for backup, DR, and mobility purposes.
Redundancy built in
There is no single point of failure in our telco core. Every single element of the network is protected on every level: physical, link layer, routing, and application.
We use memory-synced, carrier-grade SBCs that exist on multiple physical chassis simultaneously. On top of the logical SBC redundancy, we run the same PoP in two physically separated locations. For example, in the UK, we rely on London Telehouse North and BT Cardiff. Both facilities contain four sets of identical gear and can operate independently or in tandem.
We buy from multiple Tier1 IP transit providers in each location. Our team of Cisco-certified engineers builds, operates and supervises redundant switch clusters connected to several IP providers, such as TeliaSonera, NTT or GTT. Presence of multiple Tier1 carriers in route protects the IP leg of the VoIP service from network outages.
Our equipment sits right next to the underlying carrier suites in the same carrier hotels they use. We use a minimum of two fiber strands per each partner cross connect to completely rule out incidents of physical link disruption.
Redundant data centers
In most of our locations, the facility that hosts our PoPs offers 100% uptime SLA and six nines (99.9999%) uptime track record. We only use Tier III and Tier IV data centers that host critical segments of the global telecommunication infrastructure.