Emergency Standalone Proxy

Service survivability for SIP-based voice networks

Emergency Standalone Proxy

Service survivability for SIP-based voice networks


Features




      • Complete support for any access technology – POTS, xDSL, HFC, FTTx


      • Keep subscribers connected - local and trunk calling, and emergency calling complete with caller-ID


      • Highly scalable – up to 500,000 subscribers per instance


      • Collocation or standalone deployment options


      • Seamlessly integrated into MetaView network management system

Features




      • Complete support for any access technology – POTS, xDSL, HFC, FTTx


      • Keep subscribers connected - local and trunk calling, and emergency calling complete with caller-ID


      • Highly scalable – up to 500,000 subscribers per instance


      • Collocation or standalone deployment options


      • Seamlessly integrated into MetaView network management system

ESA protection for modern SIP-based networks

Industry trends are pushing the transition to SIP telephony deeper into the network, including to the vital links between the switching core and the access network that delivers local service to subscribers.

  • SIP based BLCs and MSANs are now increasingly the access technology of choice for fixed-line telephony, whether over traditional copper lines delivering POTS + DSL or over fiber as part of HFC or FTTx networks.
  • Traditional TDM-based access equipment such as DLCs and their northbound media gateways are often now controlled by AGCF devices, with onward connection to the core over SIP, particularly as networks move to IMS.
  • SIP-based CPE such as desk phones, and soft-clients on PCs and mobile devices,, are now being deployed in homes and businesses.

Meanwhile, the regulatory requirement for Emergency Standalone service remains. Protecting that SIP traffic from the impact of losing connectivity to the core network is a key part of ensuring continuous voice service and particularly emergency calling.

How it works

Metaswitch ESA Proxy protects a remote site in any network architecture in which the link between the remote site and the core is SIP.

Acting as their primary SIP registrar, the Metaswitch ESA Proxy monitors the core network’s registrations of SIP phones, BLCs and other network endpoints, and builds a database of these connections.

If the link to the core network goes down or the central switch becomes unresponsive, even temporarily, ESA Proxy swings into action using the learned registration information to maintain local calling functionality. ESA Proxy can also use a fall-back trunk to attempt to complete non-local calls.

Once the central switch is back online, the ESA Proxy reverts to its normal mode of monitoring registrations, and call handling is once again handled by the central switch.

Emergency calling

The ability to reach emergency first responders is the critical feature of ESA requirements in most jurisdictions. ESA Proxy supports this using a trunk to the Public Safety Answering Point (PSAP) or diversion to a local emergency number (e.g. the police station).

Deployment options

Internally fault-tolerant, ESA Proxy can be deployed on dedicated virtual machines using VMware and OpenStack/KVM, or on ATCA hardware, either on its own or collocated with related Metaswitch products.


Contact us

Ask us how ESA Proxy can protect your subscribers’ vital voice services when they need it most

Contact us

Ask us how ESA Proxy can protect your subscribers’ vital voice services when they need it most