Cisco Cisco Customer Voice Portal Downloads

Configuring Unified CM Service Configuration Settings

Set the following configuration parameters to make Unified CM use the Ingress gateway instead
of Unified CVP as the originating location of the call.

•

Set "Accept Unknown TCP connection" in Unified CM Service parameters.

•

Set the Unified CM Service parameter "GK controlled trunk that will listen to 1720" to
“None”.

•

Do not define Unified CVP as a gateway device in Cisco Unified Communications Manager.

•

Define the Ingress gateway(s) as gateway devices in Unified CM. Assign the correct location
to the device(s).

These settings will ensure that CAC can be properly adjusted based on the locations of the
calling endpoint and the phone.

Configuring Ingress Gateway H.323 Settings

To help the Unified CVP H.323 Service identify the Unified CM cluster the Ingress gateway
is registered to, a translation rule on the Ingress gateway is used. The rule will prefix a digit to
the called number prior to initiating the call set-up to Unified CVP. The prefixed digits represent
the tech-prefix number used by the Unified CM Cluster gatekeeper controlled trunk when
registering with the gatekeeper.

Note: This technique is a special application of the tech-prefix call routing described in Chapter
14, " 

."

In the example below:

•

The Unified CM cluster registers with tech-prefix 7#.

•

The Ingress gateway prepends the digit 7 to the DNIS.

•

The VBAdmin command setSigDigits 1 strips off the first digit before passing the DNIS to
Unified ICME.

•

When the Unified ICME transfers the call to the agent, Unified CVP prepends 7# to the
transfer DNIS before initiating the transfer.

•

The gatekeeper sees that the Unified CM cluster is registered with 7#Unified CM cluster;
CAC is adjusted correctly.

translation-rule 99

    Rule 1 ^6951000 76951000

dial-peer voice 99 voip

Configuration and Administration Guide for Cisco Unified Customer Voice Portal Release 4.1(1)