CTS implements failover services for voice lines through our Disaster Recovery SIP Server. This allows us to become the immediate backup for all clients in the event of a disaster.
You might be wondering...what exactly prompted us to create a failover site? New York, the city that never sleeps, was experiencing way too many fiber cuts & power outages. Unfortunately, our clients were losing most, if not all of their service, obviously not only creating an inconvenience for them, but for us as well. In order to continue honoring our commitment to carry out quality telecommunications and stand by our customers, we knew it was time for a change.
Disaster Recovery Sip Server Will Keep You Connected
Our Disaster Recovery SIP Server offers custom Automated Attendant routing as well, which will replicate the clients' Automated Attendant giving us even more flexibility in call routing and matching of the digits dialed. This will allow the client to stay connected with the outside world and give the ability to be reached under any circumstances, such as carrier outages and/or power failures, and still manage to provide a greeting and route. This makes it look like the client is open for business no matter what.
Since Hurricane Sandy, we have successfully run our Disaster Recovery SIP Server without any issues. We have successfully provided our clients with communication both ways by utilizing any means possible to connect through the internet and our server at their location. Cable Modems and 4G LTE wireless was our only way of routing calls for several weeks following the storm. This type of technology allows us to route calls over any internet, making it a perfect backup that can be implemented almost instantly. If a cable connection was not available, then 4G LTE signal was used to route the calls. With our SIP technology, we are able to route up to 23 calls on 4G-LTE signal and up to 92 calls on cable modems.
This type of backup is a must for today’s businesses, providing them with off-site call routing at a minimal cost. The best part about it? The backup server call routing can be implemented in as little as 4 hours.