Survivable remote site telephony

Survivable remote site telephony

In Cisco's Architecture for Voice Video and Integrated Data (AVVID), there is a feature known as Survivable Remote Site Telephony, which gives you the ability to have SRST-enabled IP phones to register with a router in the event that they lose network connectivity to the Call Manager. Generally the way this is deployed is for remote sites that are small enough that you can't justify a local Call Manager server for them, but that are still important enough to require a fault-tolerant telephony solution.

Unfortunately, SRST had a pretty major limitation, which is that the router that takes over call processing for the site had to be the default gateway for the site. This is fine in many smaller remote offices, where you might have just a few users and a single subnet, but for many organizations, remote offices are often factory floors or warehouses, which have few telephone handsets, but are very large physically, or have other wiring issues that make designers prefer routing instead of switching. Other organizations have remote offices with hundreds of users, but may still prefer to use a centralized Call Manager farm. So with the massive popularity of layer-3 switching, it's not unusual to find many "remote" offices that have users scattered around on many subnets. Further, popular designs for redundancy, and even Cisco's own "Core-Distribution-Access" layered architecture model conflict with the basic restriction of SRST that all the users at a site share the

    Requires Free Membership to View

    Login

    SearchUnifiedCommunications.com members gain immediate and unlimited access breaking industry news, expert advice on UC, technical guides, and more -- all at no cost. Join me on SearchUnifiedCommunications.com today!

    Kate Gerwig, Editorial Director

    By submitting your registration information to SearchUnifiedCommunications.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchUnifiedCommunications.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

same physical default gateway.

Fortunately, the more recent versions of Call Manager do not have this requirement. As of version 3.3, you can make the decision as to which router processes calls in the event of a WAN failure on a device-pool basis, and you can specify a device that is not the default gateway.

Thomas Alexander Lancaster IV is a consultant and author with over ten years experience in the networking industry, focused on Internet infrastructure.


This was first published in July 2003

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

Back to top