Cisco Cisco Customer Voice Portal 8.0(1) Design Guide

For TrunkGroupChannelNum, look for :DS0 in x-ds0num field 

 If found, TrunkGroupChannelNum = <value before the :DS0> 

Using the above example: TrunkGroupChannelNum = 1 

 else, TrunkGroupChannelNum = <max int value> to indicate we didn't find the DS0 value 

Using the above example: TrunkGroupChannelNum = Integer.MAX_VALUE (2^31 - 1) 

The Trunk Utilization feature enables the gateways to push the status of memory, DS0, DSP and the CPU 
to Unified CVP, not only for real time routing, but also for Unified ICM reporting and scripting purposes, 
as well as Unified CVP reporting.

Because this feature uses a push method to send resource data to Unified CVP, resources are monitored 
more closely and failover can occur faster when a device goes down or is out of resources.

Some of the characteristics of this feature include:

Each gateway can publish an SIP OPTIONS message with CPU, Memory, DS0 and DSP info to 
Unified CVP every 3 minutes when operation conditions are normal on the gateway.

The push interval is configurable via IOS CLI on the Gateway. 

If a high water mark level is reached, the gateway will send the SIP OPTIONS message immediately 
with an Out-Of-Service = true indication and will not send another OPTIONS message until the low 
water mark level is reached with an Out-Of-Service = false indication.

Up to 5 Resource Availability Indication (RAI) targets can be configured on the gateway. 

Trunk Utilization Routing could also be used to update trunk group status in the Unified CCE router. 
Then a PSTN call (through the ICM script) can query the router with a pre-route from an SS7 NIC to see 
the most available ingress gateway to use for the post route to Unified CVP. 

DS0 is the data line that provides utilization information about the number of trunks free on a gateway.

When combining the Server Group element polling feature with the IOS Gateway trunk utilization 
feature, your solution will have faster failover for high availability call signaling. This combination is 
recommended.

Configuration and Deployment Considerations

For Proxy Server Deployment with CUSP:

Configure TDM originating gateways for rai-targets to provide status in OPTIONS message to 
primary and secondary Unified CVP Call Servers, for reporting purposes only. The data is only used 
for reporting, not routing, so the data only needs to be sent to Call Servers that have reporting turned 
on. 

Configure primary and secondary CUSP proxy servers with Server Groups pinging to Unified CVP, 
VXML gateways, and CUCM elements.