Implementing and Supporting Cisco Unified Contact Center Enterprise Free Sample Questions

Must have SIP Proxy server to pass messages between the gateways and the Cisco Unified CVP servers.

Must have voice gateway TCL scripts to handle conditions where the gateways cannot contact the Cisco Unified CVP Call Server to direct the call correctly.

Add load balancers to load balance .wav file requests across multiple Cisco Unified CVP Media Servers.

Dedicate duplexed VRU peripheral gateways for each Cisco Unified CVP call server.

For a single data center with centralized deployment, deploy Cisco Unified CVP with N:N redundancy.

Cluster Manager

System Application Agent

Cisco DB

Cisco Tomcat

Cisco Dirsync

dbagent

opcs

ccagent

mds

100 ms, 3 heartbeats

100 ms, 5 heartbeats

400 ms, 3 heartbeats

400 ms, 5 heartbeats

The heartbeat interval and maximum missed heartbeats settings can be customized by a system administrator

Implement a centralized SIP Proxy Server that load balances SIP INVITE messages to both CVP Call Servers using a round-robin algorithm with options ping enabled.

Configure the Voice Gateways to use H.323 alternate gatekeepers to direct calls to the Side B CVP Call Server immediately upon Side A failure.

Deploy the CVP Call Servers in a simplex mode and use VMware High Availability (HA) to restart the virtual machine on a host in the secondary data center.

Configure the ICM Router to bypass the VRU leg and route calls directly to agents using the default label if the CVP Peripheral Gateway detects a failure.

It is a registry key used to define the specific IP address of the peer Router for heartbeat communication.

It is a specialized license file that must be uploaded to the Router to enable high-capacity call processing.

It defines the ordering of the Peripheral Gateways and determines which PG is active for a specific peripheral.

It is a unique alphanumeric string configured during setup that identifies the router instance and ensures that only valid components with the matching key can participate in the system.

Both Routers go active immediately to ensure no calls are dropped, relying on the PGs to deduplicate data.

The system utilizes the Test-Other-Side mechanism over the visible network; if they can communicate, the router with the higher capacity or uptime remains active while the other goes idle.

The Router with the lower latency to the Peripheral Gateways will assert mastership and the other will shut down its services.

Side B automatically yields to Side A, and Side A enters a simplex mode operation regardless of its current state.

The Finesse client automatically detects the failure of the primary server and redirects the agent browser to the secondary server URL without user intervention.

Agents must manually refresh their browser and select the 'Secondary Server' link from the bookmark bar to resume operations.

The Finesse server uses a Virtual IP (VIP) address that automatically floats to the active server, making the failover transparent to the client.

Failover is handled by the CTI Server; Finesse servers are stateless and do not require specific failover logic.