Cisco Cisco Customer Voice Portal 8.0(1) Design Guide
9-2
Cisco Unified Customer Voice Portal (CVP) 8.x Solution Reference Network Design (SRND)
OL-15989-06
Chapter 9 Network Infrastructure Considerations
Bandwidth Provisioning and QoS Considerations
Bandwidth Provisioning and QoS Considerations
In many Unified CVP deployments, all components are centralized; therefore, there is no WAN network
traffic to consider. In general, there are only two scenarios when WAN network structure must be
considered in a Unified CVP environment:
traffic to consider. In general, there are only two scenarios when WAN network structure must be
considered in a Unified CVP environment:
•
In a distributed Unified CVP deployment, when the ingress gateways are separated from the Unified
CVP servers by a WAN.
CVP servers by a WAN.
•
In Unified CVP deployments where the ingress gateway and the agent are separated over a WAN.
The agent can be a TDM ACD agent or a Unified CCE agent.
The agent can be a TDM ACD agent or a Unified CCE agent.
Unlike Unified ICM, Unified CVP has a very simple view of QoS:
•
Unified CVP has no concept of a private WAN network structure. All WAN activity, when required,
is conducted on a converged WAN network structure.
is conducted on a converged WAN network structure.
•
Unified CVP does not use separate IP addresses for high and low priority traffic.
•
Unified CVP does mark the QoS DSCP of SIP packets. H.323 traffic must be marked by routers or
switches in the network using access control lists (ACLs).
switches in the network using access control lists (ACLs).
Adequate bandwidth provisioning is an important component in the success of Unified CVP
deployments. Bandwidth guidelines and examples are provided in this chapter to help with provisioning
the required bandwidth.
deployments. Bandwidth guidelines and examples are provided in this chapter to help with provisioning
the required bandwidth.
Note
RSVP. Cisco Unified CM 5.0 introduced support for Resource Reservation Protocol (RSVP) between
endpoints within a cluster, and 8.0 Unified CM introduces RSVP over the SIP Trunk. RSVP is a protocol
used for call admission control, and it is used by the routers in the network to reserve bandwidth for calls.
RSVP is not qualified for call control signaling via the Unified CVP Call Server in SIP or H.323 in the
8.0(1) release. The recommended solution for Call Admission Control is to employ Locations
configuration on CVP and in UCM. Refer to
endpoints within a cluster, and 8.0 Unified CM introduces RSVP over the SIP Trunk. RSVP is a protocol
used for call admission control, and it is used by the routers in the network to reserve bandwidth for calls.
RSVP is not qualified for call control signaling via the Unified CVP Call Server in SIP or H.323 in the
8.0(1) release. The recommended solution for Call Admission Control is to employ Locations
configuration on CVP and in UCM. Refer to
.
Unified CVP Network Architecture Overview
In a Unified CVP environment, WAN and LAN traffic can be grouped into the following categories:
•
•
•
Voice Traffic
Voice calls consist of Real-Time Transport Protocol (RTP) packets that contain actual voice samples.
RTP packets are transmitted in the following cases:
RTP packets are transmitted in the following cases:
•
Between the ingress PSTN gateway or originating IP phone and one of the following:
–
Another IP phone, such as an agent
The destination phone might or might not be co-located with the ingress gateway or calling IP
phone, and the connection can be over a WAN or LAN.
phone, and the connection can be over a WAN or LAN.
–
An egress gateway front-ending a TDM ACD (for legacy ACDs or IVRs)