Cisco Cisco Customer Voice Portal 8.0(1) Design Guide
4-8
Cisco Unified Customer Voice Portal (CVP) 8.x Solution Reference Network Design (SRND)
OL-15989-06
Chapter 4 Designing Unified CVP for High Availability
SIP Proxy
Deployment Option B - Redundant SIP Proxy Servers (Double Capacity)
This method:
•
Consists of 2 gateways for redundancy, 2 proxy modules in each chassis. All 4 proxy servers are in
active mode with calls being balanced between them.
active mode with calls being balanced between them.
•
Uses SRV to load balance across proxies with priority.
•
The ISR is dedicated to the proxy blade function and is not co-located as a VXML gateway, nor as
a TDM gateway, due to platform validation restrictions on CUSP.
a TDM gateway, due to platform validation restrictions on CUSP.
•
TDM gateways are set with SRV or with Dial Peer Preferences to use the primary and secondary
CUSP proxies.
CUSP proxies.
•
CUSP is set with Server Groups to find primary and back up Unified CVP, Unified CM and VXML
gateways.
gateways.
•
Unified CVP is set up with Server Group to use the primary and secondary CUSP proxies.
•
Cisco Unified CM is set up with Route Group with multiple SIP Trunks, to use the primary and
secondary CUSP proxies.
secondary CUSP proxies.
Example of Option B
With this example ISR1 is on the east coast and ISR2 is on the west coast. The TDM gateways will use
the closest ISR, and only cross the WAN when needing to failover to the secondary priority blades. The
SRV records look like this:
the closest ISR, and only cross the WAN when needing to failover to the secondary priority blades. The
SRV records look like this:
east-coast.proxy.atmycompany.com
blade 10.10.10.10 priority 1 weight 10 (this blade is in ISR1 on east coast)
blade 10.10.10.20 priority 1 weight 10 (this blade is in ISR1 on east coast)
blade 10.10.10.30 priority 2 weight 10 (this blade is in ISR2 on west coast)
blade 10.10.10.40 priority 2 weight 10 (this blade is in ISR2 on west coast)
west-coast.proxy.atmycompany.com
blade 10.10.10.30 priority 1 weight 10 (this blade is in ISR2 on west coast)
blade 10.10.10.40 priority 1 weight 10 (this blade is in ISR2 on west coast)
blade 10.10.10.10 priority 2 weight 10 (this blade is in ISR1 on east coast)
blade 10.10.10.20 priority 2 weight 10 (this blade is in ISR1 on east coast)
Performance Matrix for CUSP Deployment
Table #2 in the
“Performance Measured in the Number of New Call Attempts
per Second" shows performance data for the CUSP server.
CUSP baseline tests were done in isolation on the proxy, and capacity numbers (450 TCP, 500 UDP
transactions per second) should be used as the highest benchmark, and most stressed condition
allowable.
transactions per second) should be used as the highest benchmark, and most stressed condition
allowable.
A CVP call, from the proxy server perspective, entails on average, 4 separate SIP calls:
•
Caller inbound leg
•
VXML outbound leg
•
Ringtone outbound leg
•
Agent outbound leg
When a consult with CVP queuing occurs, an additional 4 SIP transactions will be incurred for the
session, effectively doubling the number of calls.
session, effectively doubling the number of calls.