Hi All,
Here is an excerpt from the Design Guide for SRSV.
Overview of Cisco Unity Connection SRSV in Connection 9.1(1) and Later
Revised January 16, 2013
Cisco Unity Connection Survivable Remote Site Voicemail (Connection SRSV) is a backup voicemail solution that allows you to receive voice messages during WAN outages. It works in conjunction with Cisco Unified Survivable Remote Site Telephony (SRST) for providing voicemail service to a branch when the connectivity with the central Connection voicemail service is lost.
Connection SRSV is used in the centralized Cisco Unified Communications Manager and Cisco Unity Connection environment with multiple branch offices or small sites. It provides limited voicemail and auto-attendant features that remain in synchronization with the central Connection voicemail service so that when the WAN outage or failure occurs, the Connection SRSV solution can provide voicemail service to the subscribers at the branch. However, as soon as the network is restored, all the voicemails received by the branch subscribers are automatically uploaded to the central Connection voicemail server.
Connection SRSV solution requires the following two components:
•
Cisco Unity Connection: It is deployed at the central site alongside with Cisco Unified CM to deliver powerful integrated messaging and voicemail services.
•Connection SRSV: The SRSV component is natively a part of Connection which is deployed at the branch site alongside with Cisco Unified CM Express or Cisco Unified Survivable Remote Site Telephony (SRST). Connection SRSV is hosted on Cisco Integrated Service Routers Generation 2 (ISR G2) platform by using Services Ready Engine Virtualization.
See the following sections:
Supported SRSV Topologies
Connection SRSV supports several topologies based on the configuration of the router. You can deploy either original SRST or CUCME-as-SRST (also known as SRST Fallback Mode) at branch.
Note If you are running SRST at the branch site, you cannot also deploy the E-SRST feature.
Following figures show three topolgies supported by Connection SRSV:
Figure 14-1: Shows a topology in which SRST is deployed at the branch site. If the WAN occurs or PSTN goes down, Connection SRSV at the branch site provides limited voicemail support in the failover mode.
Figure 14-2: Shows a topology where CUCME-as-SRST (also known as SRST Fallback Mode) is providing call control at the branch site.
Figure 14-3: Shows a topology where multiple CUCME-as-SRST and SRSV devices are paired for load balancing at the survivable branch site. In this scenario, the administrator uses Cisco Unified Communications Manager to divide the branch users between CUCME-SRST-1 and CUCME-SRST-2. The central Connection server detects that and then sends the appropriate configuration to SRSV-1 and SRSV-2 at the branch site. In the event of WAN failure, each SRSV device will handle calls directed to it from the paired CUCME-as-SRST device.
Figure 14-1 Topology 1
Figure 14-2 Topology 2
Figure 14-3 Topology 3
Scalibility
Each Connection SRSV branch will support 200 users per branch with a maximum of 10 branches per centralized Connection server.
Software Requirements
Connection SRSV requires Cisco Unity Connection minimum version 9.1 for both the Central Connection server as well as the SRSV branches.
Bandwidth requirements for synchronization to central Connection server after outage
The synchronization process does not have any bandwidth requirements as it is not a real-time process.
Supported Hardware
Any supported Connection hardware is suitable for Connection SRSV. Please see the current Supported Platforms List for the most up to date list of supported hardware.
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html.
Limitations
•No MWI
•No interaction between existing UMG based SRSV and Unity Connection based SRSV
•No migration from UMG based SRSV
