The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The term device refers to a configurable application or platform. More than one device can reside on a server. For example, one physical server can contain a Call Server and a Reporting Server. In this case, each device is configured with the same IP address.
The network map is a collection of Unified CVP solution components and their configuration data. When you add a device to the Operations Console, that device becomes visible in the network map and its configuration data is stored in the Operations Console database.
The Operations Console provides two views of the properties of the devices in the network map:
For more information, see Viewing Device Information
In the Offline view, the Operations Server operates without a running Unified CVP solution, allowing you to build the network map even if the devices do not exist. The configurations are stored locally in the Operations Console database. The Operations Console displays the property values stored in the local database. When you modify a property value in the Offline view and click Save, the configuration is stored locally in the Operations Console database only. Configurations that are saved while a device is Offline can be applied when the device is ready and available.
By default, Unified CVP devices are displayed in the Offline view. To display the Online device view, select online from the View drop down menu.
The Online view provides a snapshot of properties used by the running Unified CVP server at the moment. When you modify a property value in the Online view and click Save, the configuration is stored locally in the Operations Console database only. Clicking Save & Deploy saves the change in the Operations Console database and also applies the change to the device. If you change a device property, click Save, but do not click Save & Deploy, you see the changed value in the Online view, but see the current value in the Offline view.
By default, Unified CVP devices are displayed in the Offline view. To display the Online device view, select online from the View drop-down menu.
When you select a device type from the Device Management menu, information appears about the device that has been added to the Operations Console.
The following table describes the server window fields.
See also Display Device Statistics.
To find a device:
Step 1 | From the Device Management menu, select the menu
option for the type of device to find from the Device menu. The Find, Add, Delete, Edit window lists the available devices of the type you selected, sorted by name, 10 per screen. | ||
Step 2 | If the list is long, you can click the first page, previous page, next page, and last page icons on the bottom right of the screen to page through the list. Or, you can enter a page number in the Page field and press enter to go directly to the numbered page. | ||
Step 3 | You can also filter the list by selecting an attribute such as
Hostname; then selecting a modifier, such as
begins with; entering your search term; and then
clicking Find.
|
Step 1 | Choose the device from the Device Management menu: For example, if
you want to view statistics for the Unified CVP Reporting Server, choose
.
The Find, Add, Delete, Edit window opens. |
Step 2 | Click Edit. |
Step 3 | Find the device by using the procedure inFind Device. |
Step 4 | From the list of matching records, choose the device that you want to get statistics for. |
Step 5 | Select
Statistics from the Configuration menu bar.
The Statistics window opens. |
Step 6 | If there are multiple statistics options to choose, select the desired option from the Statistics drop-down menu. |
To get device statistics:
Step 1 | Choose the device from the Device Management menu: For example, if
you want to view statistics for the Unified CVP Reporting Server, choose
.
The Find, Add, Delete, Edit window opens. |
Step 2 | Click Edit. |
Step 3 | Find the device using the procedure shown in Find Device. |
Step 4 | From the list of matching records, choose the device that you want to get statistics for. |
Step 5 | Select
Statistics from the Configuration menu bar.
The Statistics window opens. |
Step 6 | If there are multiple statistics options to choose, select the desired option from the Statistics drop-down menu. |
The Operations Server displays the statistics in the window.
The following Unified CVP licenses are enforced by the software on a per-instance basis:
Unified CVP licenses:
Call Server - The SIP Service and the IVR Service check at startup time to ensure that it is running on a system with a valid Call Server license.
Unified CVP VXML Server - The Unified CVP VXML Server checks at startup time to ensure that it is running on a system with a valid Unified CVP VXML Server license.
Reporting Server - The Reporting Server checks at startup time to ensure that it is running on a system with a valid Reporting Server license.
The Operations Server runs without requiring a license.
In addition, each Call Server and each Unified CVP VXML Server enforce licenses for a particular number of simultaneous calls. The software does not distinguish between Call Director calls, VRU-only calls, or VRU calls with ASR/TTS or VXML.
Port licensing is enforced as follows:
The Call Server is licensed for a certain number of ports; SIP and IVR Services share this port pool.
The SIP Service attempts to allocate one of its licenses whenever it receives an incoming call. Once the last license has been allocated, the SIP Service changes its status and that of its host Call Server (the Call Server on which the SIP Service is running) to Partial status, preventing further calls from being accepted. When a call terminates, the SIP Service releases a license, and if it had been in Partial status due to license depletion, it resumes Up status.
![]() Note | You can view the devices in a particular device pool by selecting Control Center from the System menu, selecting the Device Pool tab, and then selecting a device pool. You can also view a particular type of device by selecting the Device Type tab and selecting a device type. |
The IVR Service can receive calls transferred from SIP Service or from some other source. The IVR Service can handle both the VRU leg and the switch leg of the same call. The IVR Service keeps a list of active Call IDs, and uses that list to determine whether a particular incoming call has already been counted. Therefore, the IVR Service always accepts an incoming call if its host Call Server (the Call Server on which the IVR Service is running) is in the Up state, and then checks whether the call has been seen before. If the call has not been seen before, the IVR Service allocates a license for that call. If doing so exhausts the available licenses, the IVR Service changes its state and that of its host Call Server to Partial. When a call terminates, the IVR Service releases a license and if it had been in Partial state due to license depletion, it resumes Up status.
Note that this licensing scheme might change in future releases, and should customers order an insufficient number of licenses, they will be impacted in future releases when licensing tracks the number of ports actually ordered.
For more information on licensing, see the Design Guide for Cisco Unified Customer Voice Portal.
For more information on licensing, see the Solution Design Guide for Cisco Unified Contact Center Enterprise.
From the Call Server option on the Device Management menu, you can configure one or more Call Servers. The Unified CVP Call Server provides call control capabilities, using Session Initiation Protocol (SIP) signaling.
The Call Server can be configured to provide the following call control services, which are installed with the Call Server:
SIP Service - Session Initiation Protocol (SIP), RFC 3261, is the primary call control protocol in Unified CVP. The SIP Service uses SIP to communicate with other Unified CVP solution components, such as the SIP Proxy Server, the VXML and Ingress Gateways, and Cisco Unified Communications Manager SIP trunks and SIP phones.
IVR Service - Creates the VXML pages that implement the Unified CVP Micro-applications, based on Run Script instructions received from an ICM server. The IVR service functions as the Voice Response Unit (VRU) leg, and calls must be transferred to it from the SIP Service in order to execute micro-applications. The VXML pages created by this module are sent to the VXML Gateway to be executed. The IVR Service routes requests from the SIP Service to the ICM Service.
ICM Service - Enables communication between Unified CVP components and the ICM Server. It sends and receives messages on behalf of the SIP Service, the IVR Service, and the VXML Service.
You can perform the following tasks:
To add a Call Server:
Step 1 | Select
.
Any Call Servers that have been added to the Operations Console are listed.
| ||
Step 2 | Click
Add New from the Menu bar or at the bottom of
the screen.
The Call Server Configuration window opens to the General tab. | ||
Step 3 | Fill in the IP Address and Hostname fields and other Call Server configuration settings, as needed. | ||
Step 4 | Optionally, click Enable secure communications with the Ops Console to secure communications between the Operations Console and the Call Server. | ||
Step 5 | Turn on the Call Services required for the Call Flow you are using
by checking the appropriate check boxes, and then click
Next. See Call Services.
The CVP Call Server Configuration page opens to the General tab. Additional tabs for configuring the selected services are displayed. | ||
Step 6 | Optionally, click Change Type and change your selections of services. | ||
Step 7 | Select each tab and verify that the default values are correct or
change the values if desired:
Configuration Tabs: | ||
Step 8 | When you have filled in the configuration settings for all
selected Call Services, click
Save to save the settings in the Operations
Console database. Click
Save & Deploy to save the changes and
apply them to the Call Server.
You must apply a license to the Call Server before using it. See Apply License to Call Server. | ||
Step 9 | Shut down and start the Call Server to start the newly added services. |
Services Needed for CVP Call Flow Models
Choose the desired call flow model, and then select the required call services in the Call Server Configuration window:
Call Flow Model | Required Call Services |
---|---|
Comprehensive Call Flow Using SIP | ICM, IVR, SIP |
VRU-Only | ICM, IVR |
Call Director Using SIP | ICM, IVR |
Unified CVP VXML Server with ICM Lookup | ICM |
Unified CVP VXML Server Standalone Call Flow | No Service |
Basic Video Call Flow | ICM, IVR, SIP |
The Comprehensive call flow model combines the Call Director and the VRU-Only scenarios. It provides initial prompt and collect, self-service IVR, queuing, and VoIP routing among all types of UCCE and TDM agents. This scenario is supported at two port licensing levels: Basic and Advanced. The Basic level supports the playing of .wav files and input using DTMF. The Advanced level adds support for ASR, TTS, and Unified CVP VXML Server applications.
Unified CVP provides ICM with VRU services for calls which are routed in some other manner, such as by a carrier switched network through an ICM NIC interface. VRU services could be for initial prompt and collect, for integrated self service applications, for queuing, or for any combination thereof. This scenario does not use SIP, and requires no Ingress Gateway. It does use VXML Gateways, but the Unified CVP VXML Server is optional, as are ASR and TTS Servers.
Depending on which kind of routing client is in charge of call routing, ICM may transfer the call to the VRU-Only Call Server either by a Translation Route to VRU node, or by a Send To VRU node. In the first case, the Call Server will determine that the arriving call is a VRU leg call by matching the arriving DNIS with its configured list of arriving DNIS numbers. In the second case, it will determine that it is a VRU leg call because the DNIS length is greater than its configured maximum DNIS length. Digits beyond the maximum DNIS length are taken as the Correlation ID.
In Call Director using SIP, Unified CVP provides ICME with VoIP call routing capabilities only. Use your own Service Control VRU if you are using an ICM Server to queue calls, or queue calls directly on an ACD. Calls can be transferred multiple times, from Ingress, to customer-provided VRU, to either UCCE or customer-provided ACD or agent, and back again. When calls are connected to customer-provided equipment, their voice paths must go to an Egress gateway which is connected by TDM to that equipment. If the signaling is SIP, then Unified CVP will work with customer-provided SIP endpoints which have been tested and certified to interoperate with Unified CVP. Neither Unified CVP VXML Server nor any VXML Gateways are used in this model.
In this call flow model, the call server with the ICM Service enabled is required to route calls. The Reporting server is optional. Use a Reporting server if you want to generate reports that include Unified CVP VXML Server events. You can also use the ICM request label from the Unified CVP VXML Server to an ICM Server, if the ICM service is enabled on the Call Server. The Reporting server can be installed on the same physical machine as the Call Server. After you configure the Call Server, you must configure the Unified CVP VXML Server. See Unified CVP VXML Server Setup.
The RequestICMLabel is a feature that allows you to make back-end requests to an ICM Server without relinquishing control of the call. The application generally acts on its own, but includes a special step to send a query to the ICM Server and receive a response. The query and the response may contain full call context information, as can the response.
Following are the features of the IVR application :
In this call flow model, the Call Server is used to route messages between the components. Calls arrive through a VXML gateway, and interact directly with a Unified CVP VXML Server to execute VXML applications. The gateway performs both ingress and VXML functions. This call flow model provides a sophisticated VXML-based VRU, for applications which in many cases do not need to interact with an ICM Server.
For a Unified CVP VXML Server (standalone) with no connection to an ICM Server and no Reporting Server, configure the Call Server with no services enabled. If you need to make requests to an ICM server, without relinquishing control of the call or use Unified CVP reporting, you must configure the VXML Server to use a Call Server with at least the ICM Service enabled. See Unified CVP VXML Server Setup.
After you configure the Call Server, you must configure the Unified CVP VXML Server as a Unified CVP VXML Server (standalone). See Unified CVP VXML Server (Standalone) Setup.
The Basic Video call flow model combines the Call Director and the VRU-Only call flow models, along with video capabilities that are only enabled during the caller-agent conversation. It provides initial prompt and collect, self-service IVR, queuing, and VoIP routing among UCCE and TDM agents.
![]() Note | This call flow model is almost identical to the Unified CVP Comprehensive SIP call flow model. The only change between the two call flow models is the addition of video-enabled endpoints for the calling and called parties (Cisco Unified Video Advantage (CUVA), Cisco Unified Personal Communicator (CUPC), and Cisco TelePresence). See the Configuration Guide for Cisco Unified Customer Voice Portal for additional information about CUVA and Cisco Telepresence. |
When you are adding a Call Server, you must configure the call services required for the call flow model you are using.
You must configure the ICM service if you are adding or editing a Call Server and you are using any of these call flow models:
Call Director
VRU-Only
Comprehensive
You must also configure the ICM service if you use a Unified CVP VXML Server (standalone) that makes requests to an ICM server without relinquishing control of the call (Request ICM Label).
To configure the ICM Service:
Step 1 | If you are adding a new Call Server, refer to Add Call Server. If you want to change an existing Call Server, refer to Edit Call Server. |
Step 2 | Fill in the appropriate configuration settings as described in ICM Service Settings |
Step 3 | When you finish configuring all desired Call Server services, click Save to save the settings in the Operations Console database. Click Save & Deploy to apply the changes to the Call Server. |
The following table describes the property settings that you can change to configure the ICM Service. The first time you configure the ICM Service on a Call Server, you must restart the Call Server. You must also restart the server if you change a configuration setting that has been marked yes in the restart required column in the table below.
Property |
Description |
Default |
Range |
Restart Required |
||||
---|---|---|---|---|---|---|---|---|
General Configuration |
||||||||
VRU Connection Port |
The Port Number on which the ICM Service listens for a TCP connection from the ICM PIM. |
5000 |
Any valid TCP/IP connection port |
Yes |
||||
Maximum Length of DNIS |
The maximum length of an incoming Dialed Number Identification Service (DNIS). Valid input for this field is 1 - 99999 characters. Look for this information in your network dial plan. For example, if the Gateway dial pattern is 1800******, the value of Maximum Length of DNIS should be 10. The number of DNIS digits from the PSTN must be less than or equal to the maximum length of DNIS field.
|
10 |
Integer |
No |
||||
DNIS |
||||||||
Add |
Enter a single DNIS number for translation routed calls. DNIS is a phone service that identifies which number the caller dialed. DNIS can be up to 32 characters in length. Validations for DNIS fields are as follows: |
None |
Integer |
No |
||||
Add a Range |
List of DNIS numbers for translation routed calls. Add a range of DNIS numbers, select Add a Range, enter the first DNIS number in the range, and then enter the last DNIS number in the range in the to field. Click Add DNIS to add the entered DNIS or DNIS range to the list of Configured DNIS numbers. Select a DNIS or DNIS range in the Configured DNIS box and click Delete DNIS to remove it from the list of Configured DNIS numbers. DNIS can be up to 32 characters in length. Valid input for DNIS range requires the first and last DNIS numbers in the range to be the same length. For example, a range from 100 to 900 is valid because each number is three characters in length. |
None |
Integer |
No |
||||
Advanced Configuration |
||||||||
New Call Service ID |
Identifies calls to be presented to ICM software as a new call. New Call Service ID calls result in a NEW CALL message being sent to ICM software and the call being treated as a new call, even if it had been pre-routed by ICM software. |
1 |
Integer |
Yes |
||||
Pre-routed Service ID |
Identifies calls pre-routed with a translation route or correlation ID. Pre-routed Service ID calls result in a REQUEST_INSTRUCTION message being sent to ICM software, which continues to run the script for the call. |
2 |
Integer |
Yes |
||||
New Call Trunk Group ID |
Calls presented to ICM as new calls are sent with this Trunk Group ID as part of the NEW_CALL message to ICM. |
100 |
Integer |
Yes |
||||
Pre-routed Call Trunk Group ID |
Calls pre-routed with a Translation Route or correlation ID are sent with this Trunk Group ID as part of the REQUEST_INSTRUCTION message to ICM. |
200 |
Integer |
Yes |
||||
Select QoS Level |
Select the Quality of Service level between the ICM Service and the ICM VRU PIM.
|
cs3 |
The drop-down list has the following values: af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs1, cs2, cs3, cs4, cs5, cs6, cs7,default, ef
|
Yes |
||||
Trunk Utilization |
||||||||
Enable Gateway Trunk Reporting |
Check the check box to enable gateway trunk reporting.
|
None |
Not applicable |
No |
||||
Maximum Gateway Ports |
The value used for setting the maximum number of ports that a gateway supports in a CVP deployment. This will be used to calculate the number of ports to report to the Unified ICM Server for each gateway. |
700 |
1-1500 |
Yes |
||||
Available |
The list of gateways available for trunk reporting. |
None |
Not applicable |
No |
||||
Selected |
The list of gateways selected for trunk reporting. |
All Gateways Selected |
Not applicable |
No |
The first time you configure the service on a Call Server, you must restart the Call Server.
You must configure the IVR service if you add a new Call Server (adding a new Call Server) or edit a Call Server (editing a Call Server) and you any of these call flow models (call flow models):
Audio call flow models:
The IVR Service creates VXML documents that implement the Micro-Applications based on Run Script instructions received by the ICM. The VXML pages are sent to the VXML Gateway to be executed. The IVR Service can also generate external VXML through the Micro-Applications to engage the Unified CVP VXML Server to generate the VXML documents.
The IVR Service plays a significant role in implementing a failover mechanism: those capabilities that can be achieved without ASR/TTS Servers, and VXML Servers. Up to two of each such server are supported, and the IVR Service orchestrates retries and failover between them.
Before You Begin
Configure the following servers before configuring the IVR Service:
The IVR Service is one of the services that can be configured when creating a new Call Server.
Step 1 | If you are adding a new Call Server, refer to Add Call Server. If you want to change an existing Call Server, refer to Edit Call Server. |
Step 2 | Fill in the appropriate configuration settings as described in IVR Service Settings |
Step 3 | When you finish configuring all desired Call Server services, click Save to save the settings in the Operations Console database. Click Save & Deploy to apply the changes to the Call Server. |
The following table describes the property settings that you can change to configure the IVR Service.
Property |
Description |
Default |
Range |
Restart Required |
||
---|---|---|---|---|---|---|
IOS Voice Browser Configuration |
||||||
Last Access Timeout (seconds) |
The number of seconds the IVR Service waits for a call request from a non-Unified CVP Voice Browser before removing that Voice Browser from its current client list. This value must be greater than or equal to the call timeout. |
7320 |
0 -2147483647 |
No |
||
Media Server Timeout |
The number of seconds the Gateway should wait to connect to the HTTP Media Server before timing out. |
4 |
0 -2147483647 |
No |
||
Media Server Retry Attempts |
Maximum number of times the non-Unified CVP Voice Browser (IOS Voice Browser) or Unified CVP VXML Server attempts to connect to an HTTP Media Server to retrieve a single prompt. If the Voice Browser or Unified CVP VXML Server fails after the specified number of times, it will try the same number of times to retrieve the media from a backup media server before failing and reporting an error. The backup media server is defined on the gateway as <mediaserver>-backup. |
0 |
0 -2147483647 |
No |
||
ASR/TTS Server Retry Attempts |
Maximum number of times the Gateway tries to connect to an ASR/TTS server. If the Gateway fails to connect this many attempts, it will try the same number of times to connect to a backup ASR/TTS server before failing and reporting an error. (The backup ASR and TTS servers are defined on the gateway as asr-<locale>-backup and tts-<locale>-backup.) |
0 |
0 -2147483647 |
No |
||
IVR Service Timeout |
The number of seconds the Gateway should wait to connect to the IVR Service before timing out. This setting controls call results only. The initial NEW_CALL timeout from the Gateway to the IVR Service is controlled through the fetchtimeout property within the bootstrap VXML in flash memory on the Gateway. |
7 |
0 -2147483647 |
No |
||
IVR Service Retry Attempts |
Maximum number of times the Gateway tries to connect to the IVR Service before failing and reporting an error. This setting controls call results only. The initial NEW_CALL retry count from the Gateway to the IVR Service is controlled from within the bootstrap VXML in flash memory on the Gateway. |
0 |
0 -2147483647 |
No |
||
Use Backup ASR/TTS Servers |
If you select Yes (default) and an ASR/TTS Server is unavailable, the Gateway attempts to connect to the backup ASR/TTS server. |
Yes |
Yes or No |
No |
||
Use Backup Media Servers |
If you select Yes (default) and a media server is unavailable, the Gateway attempts to connect to the backup Media Server. |
Yes |
Yes or No |
No |
||
Use hostnames for default Media/VXML servers |
If you select No (default), the IP address is used for the XML Server and Media Server. If you select Yes, the hostnames are used rather than IP addresses. | No |
Yes or No |
No |
||
Use Security For Media Fetches |
If you select No (default), HTTP URLs are generated to media servers.
Select Yes to generate HTTPS URLs to media servers. |
No |
Yes or No |
No |
||
Advanced |
||||||
Call timeout |
The number of seconds the IVR Service waits for a response from the SIP Service before timing out. This setting should be longer than the longest prompt, transfer or digit collection at a Voice Browser. If the timeout is reached, the call is cancelled but no other calls are affected. The only downside to making the number arbitrarily large is that if calls are being stranded, they will not be removed from the IVR Service until this timeout is reached. |
7200 |
Must be 6 seconds or greater |
No |
||
ASR/TTS Use the Same MRCP Server |
Select this option if your ASR and TTS servers are on the same machine. Using this option helps to minimize the number of MRCP connections on the ASR/TTS server. |
No |
Yes or No |
No |
Session Initiation Protocol (SIP), RFC 3261, is the primary call control protocol in Unified CVP. The SIP Service uses SIP to communicate with other Unified CVP solution components, such as the SIP Proxy Server, the VXML and Ingress Gateways, and Cisco Unified Communications Manager SIP trunks and SIP phones.
The SIP Service is one of the services that can be configured when creating a new Call Server.
Step 1 | If you are adding a new Call Server, refer to Add Call Server. If you want to change an existing Call Server, see Edit Call Server. |
Step 2 | Fill in the appropriate configuration settings. For more information, see section SIP Service Settings in the Managing Devices chapter. |
Step 3 | When you finish configuring all desired Call Server services, click Save to save the settings in the Operations Console database. Click Save & Deploy to apply the changes to the Call Server. |
The following table describes the properties that you can set to configure the SIP Service. The first time you configure the SIP service on a Call Server, you must restart the Call Server.
Enable Outbound Proxy
Default | Range | Restart Required |
---|---|---|
No | Yes and No | Yes |
Use DNS SRV type query
![]() Note | If you enable Resolve SRV records locally, you must select Yes to ensure the feature works properly. |
Default | Range | Restart Required |
---|---|---|
No | Yes and No | Yes |
Resolve SRV records locally
![]() Note | If you enable Resolve SRV records locally, you must select Yes to use DNS SRV type query. Otherwise, this feature will not work. |
Default | Range | Restart Required |
---|---|---|
None | Enabled or Disabled No | Yes |
Outbound Proxy Host
Default | Range | Restart Required |
---|---|---|
No | Valid IP Address | Yes |
Outbound SRV domain name/Server group name (FQDN)
If you use a hostname that is an SRV type record instead of a standard DNS type record, this field contains a fully qualified domain name that is configured on the DNS server. Otherwise, the field contains an SRV configuration file.
Default | Range | Restart Required |
---|---|---|
None |
Follows the same validation rules as hostname, which includes uppercase and lowercase letters in the alphabet, the numbers 0 through 9, and a dash. 0 - 256 character length. |
Yes |
DN on the Gateway to Play the Ringtone
Dialed Number (DN) configured on the gateway to play ringtone (dedicated VoIP dial peer).
Default | Range | Restart Required |
---|---|---|
9191 | Any valid label | No |
DN on the Gateway to Play the Error Tone
Dialed Number (DN) configured on the gateway to play the error.wav file (dedicated VoIP dial peer).
Default | Range | Restart Required |
---|---|---|
9292 | Any valid label | No |
Override System Dialed Number Pattern Configuration
Default | Range | Restart Required |
---|---|---|
Unchecked |
|
No |
Select QoS Level
![]() Note | For more information, see the Enterprise QoS Solution Reference Network Design Guide. |
Default | Range | Restart Required |
---|---|---|
cs3 | The drop-down list has the following values: af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs1, cs2, cs3, cs4, cs5, cs6, cs7,default, ef | Yes |
Incoming Call Dialed Number (DN)
Default | Range | Restart Required |
---|---|---|
None | Dialed Number pattern, destination (must be in the form of NNN.NNN.NNN.NNN or a hostname). See Valid Formats for Dialed Numbers for more information. | No |
Survey Dialed Number (DN)
Default | Range | Restart Required |
---|---|---|
None | Accepts only alphanumeric characters | No |
Static Routes for Local Routing Without an Outbound Proxy (see View SIP Server Groups) .
Dialed Number (DN)
Creates a Static Proxy Route Configuration Table. You must create static routes if you do not use a SIP Proxy Server. Before adding a local static route, you must enter a value into both the Dialed Number (DN) and IP Address fields so that the local static route is complete.
Click Add to create a proxy route using the Dialed Number (DN) and the IP address/Hostname entered above the Add button. The newly created proxy route is added to the list of proxy routes displayed in the box below the Add button.
Default | Range | Restart Required |
---|---|---|
None | Dialed number pattern, destination (must be format of NNN.NNN.NNN.NNN or a hostname). See Valid Formats for Dialed Numbers for more information. | No |
IP Address/Hostname/Server Group Name
![]() Note | If you use Server Group Name, you must select Yes to use DNS SRV type query and you must enable Resolve SRV records locally to ensure the feature works properly. |
Default | Range | Restart Required |
---|---|---|
None | Valid IP address, hostname, or SRV domain name | No |
Patterns for sending calls to the originator :
Dialed Number (DN)
Creates a SIP Send Back to Originator Lookup Table. Specify the DN patterns to match for sending the call back to the originating gateway for VXML treatment. For the Unified CVP branch model, use this field to automatically route incoming calls to the Call Server from the gateway back to the originating gateway at the branch. For information on the Unified CVP branch model, see Planning Guide for Cisco Unified Customer Voice Portal.
This setting overrides sending the call to the outbound proxy or to any locally configured static routes. It is also limited to calls from the IOS gateway SIP "User Agent" because it checks the incoming invite's User Agent header value to verify this information. If the label returned from ICM for the transfer matches one of the patterns specified in this field, the call is routed to sip:<label>@<host portion of from header of incoming invite>.
Three types of DNs work with Send To Originator: VRU label returned from ICM, Agent label returned from ICM, and Ringtone label.
![]() Note | For Send To Originator to work properly, the call must be TDM originated and have survivability configured on the pots dial peer. |
Default | Range | Restart Required |
---|---|---|
None | See Valid Formats for Dialed Numbers for more information. | No |
Patterns for RNA timeout on outbound SIP calls:
- Dialed Number (DN)
Creates a Dialed Number (DN) pattern outbound invite timeout using the DN and Timeout entered above the Add button. Click Add to add the newly created DN pattern outbound invite timeout to the list displayed in the box below the Add button.
Default | Range | Restart Required |
---|---|---|
None | See Valid Formats for Dialed Numbers for more information. | No |
Timeout (Seconds)
The number of seconds the SIP Service waits for transferee to answer the phone or accept the call.
Default | Range | Restart Required |
---|---|---|
60 seconds | 5 - 60 | No |
Custom ringtone patterns:
Dialed Number (DN)
Specify a custom Dialed Number (DN) pattern. Click Add to add the newly created DN pattern to the list displayed in the box below the Add button.
Default | Range | Restart Required |
---|---|---|
None | See Valid Formats for Dialed Numbers | No |
Ringtone Media file name
The file name of the ringtone to be played for the respective dialed number.
Default | Range | Restart Required |
---|---|---|
None |
0 - 256 characters. Spaces are not permitted. Provide the URL for the stream name in the following form: rtsp://<streaming server IP address> /<port>/<foldername>/ <filename>.rm |
No |
Header Name
Default | Range | Restart Required |
---|---|---|
None | Maximum length of 255 characters. | No |
Parameter
Default | Range | Restart Required |
---|---|---|
None | Maximum length of 255 characters. | No |
Default | Range | Restart Required |
---|---|---|
None | See Valid Formats for Dialed Numbers for more information. | No |
Incoming Call Dialed Number (DN)
Survey Dialed Number (DN)
Default | Range | Restart Required |
---|---|---|
None | See Valid Formats for Dialed Numbers for more information. | No |
UDP is the default transport in high availability SIP deployments. One of the drawbacks of TCP is the slow response times encountered in transmission failures due to network outages. The slow response times for TCP are caused by slowness in detecting a connection reset in applications running on other SIP devices in the network. This slowness is due to the buffering window of the TCP connection. Higher call loads fill the buffer faster and thus the notification of a connection down with an I/O exception arrives more quickly. Lower call loads or a test with a single call can be affected by as much as a 30-second delay or more. Invite Retry Counts and Retry Timeout settings are not effective when using TCP transport on SIP calls because of the persistent nature of the TCP connection.
For SIP RFC, use TCP transport in deployments in which packet sizes exceed 1300 bytes, the size of a Maximum Transmission Unit (MTU). Using UDP, if a SIP message exceeds 1300 bytes, then it might fragment and cause problems with delivery and message ordering. See Section 18.1.1 Sending Requests in RFC 3261. A SIP packet can exceed 1 MTU for various reasons; for example, if there are many Via headers, or the media portion is very large in bytes.
While the SIP Request For Comments (RFC) mandates the support of both TCP and UDP, not all SIP User Agents support TCP. However, the Unified CVP SIP Service, IOS Gateway, and Cisco Unified Communications Manager use both transport protocols.
SIP calls can be load balanced across destinations in several different ways:
Valid dialed number patterns are the same as for the ICM label sizes and limitations, including:
To verify the dialed number configured on the gateway to play ringtone, execute the sh run command on the gateway and look for the dial peer that matches the incoming dialed number. For example:
sh run
paramspace english index 0
paramspace english language en
paramspace english location flash
service ringtone flash:ringtone.tcl
paramspace english prefix en
service ringtone
voice-class codec 1
voice-class sip rel1xx disable
incoming called-number 9191T
dtmf-relay rtp-nte h245-signal h245-alphanumeric
no vad
Step 1 | If you are adding a new Call Server, refer to Add Call Server. If you want to change infrastructure settings for an existing Call Server, refer to Edit Call Server. |
Step 2 | Fill in the appropriate configuration settings as described in Infrastructure Settings. |
Step 3 | When you finish configuring Call Server services, click Save to save the settings in the Operations Console database, or click Save & Deploy to save the changes to the Operations Console database and apply them to the Call Server. |
The following table describes the infrastructure configuration settings.
Property |
Description |
Default |
Range |
Restart Required |
||
---|---|---|---|---|---|---|
Configuration: Thread Management |
||||||
Maximum Threads |
Maximum number of threads allocated in the thread pool, that can be shared by all services running as part of a CVP Web Application. |
300 |
100 to 1,000 |
No |
||
Statistics |
||||||
Statistics Aggregation Interval |
Length of time (in minutes) during which system and service statistics are published to the log file and SNMP events are sent. Once published, the counters will reset and aggregate data for the next interval. Note that this is different than the real time snapshot statistics (for the number of concurrent calls). Realtime statistics are on-demand and have no intervals. Statistics Publishing Interval will be used for attributes like the number of calls in last interval, the number of transfers in last interval, and the number of HTTP sessions in last interval. |
30 minutes |
10 - 1,440 minutes |
No |
||
Log File Properties |
||||||
Max Log File Size |
Maximum size of a log file in Megabytes before a new log file is created. |
10 MB |
1 through 100 MB |
No |
||
Max Log Directory Size |
Maximum number of Megabytes to allocate for disk storage for log files.
|
20,000 MB |
500 - 500000 The log folder size divided by the log file size must be less than 5,000. |
No |
||
Configuration: Primary Syslog Settings |
||||||
Primary Syslog Server |
Hostname or IP address of Primary Syslog Server to send syslog events from a CVP Application. |
None |
Valid IP address or hostname. |
No |
||
Primary Syslog Server Port Number |
Port number of Primary Syslog Server. |
None |
Any available port number. Valid port numbers are integers between 1 and 65535. |
No |
||
Primary Backup Syslog Server |
Hostname or IP address of the Primary Backup Syslog Server to send syslog events from a CVP Application when the Syslog Server cannot be reached. |
None |
Valid IP address or host name. |
No |
||
Primary Backup Syslog Server Port Number |
Port number of Primary Backup Syslog Server. |
None |
Any available port number. Valid port numbers are integers between 1 and 65535. |
No |
||
Configuration: Secondary Syslog Settings |
||||||
Secondary Syslog Server |
Hostname or IP address of Secondary Syslog Server to send syslog events from a CVP Application. |
None |
Valid IP address or hostname. |
No |
||
Secondary Syslog Server Port Number |
Port number of Secondary Syslog Server. |
None |
Any available port number. Valid port numbers are integers between 1 and 65535. |
No |
||
Secondary Backup Syslog Server |
Hostname or IP address of the Secondary Backup Syslog Server to send syslog events from a CVP Application when the Syslog Server cannot be reached. |
None |
Valid IP address or hostname. |
No |
||
Secondary Backup Syslog Server Port Number |
Port number of Secondary Backup Syslog Server. |
None |
Any available port number. Valid port numbers are integers between 1 and 65535. |
No |
||
License Thresholds |
||||||
Critical Threshold |
Percentage of licenses in use required to reach critical licensing state. See About License Thresholds. |
97% |
Positive integer less than or equal to 100 and greater than the warning threshold. |
No |
||
Warning Threshold |
Percentage of licenses in use required to reach warning licensing state. See About License Thresholds. |
94% |
Positive integer less than the critical threshold and greater than the safe threshold. |
No |
||
Safe Threshold |
Percentage of licenses in use required to reach safe licensing state. See About License Thresholds. |
90% |
Positive integer less than the warning threshold and greater than 0. |
No |
Three thresholds (safe, warning, and critical) describe the percentage of licenses in use required to reach their respective licensing state. If using a license or releasing a license causes the number of licenses currently in use to cross a threshold (in either direction), the state of licensing will be that of the threshold.
This does not always mean the state will change. For example, if there are 100 total licenses and the Safe, Warning, and Critical license thresholds are set to the defaults of 90%, 94%, and 97%, and there are 89 licenses in use, licenses are at a Safe level. When the licenses in use reach 94, license state changes from Safe to Warning level. If one more license is used (95), the license state remains at the Warning level. If three licenses are released (no longer in use), 92 licenses remain in use and the license state remains at the Warning level. Once the licenses in use reach the previous threshold (90), the state changes from Warning to Safe.
To edit a Call Server:
Step 1 | select
.
The Find, Add, Delete, Edit Call Servers window opens. |
Step 2 | Select a Call Server by clicking on the link in its Hostname
column or by clicking the radio button preceding it and then clicking
Edit.
The Edit CVP Call Server Configuration window opens with the current settings displayed. |
Step 3 | If you have not already applied a license to the Call Server,
select
File Transfer in the toolbar and then click
Licensing.
The Licensing page opens. See Applying a License to a Call Server. |
Step 4 | Change the desired configuration settings on the General tab as
described in
Call Server Settings.
You cannot change the IP Address. |
Step 5 | Optionally, click the Change Type button to change the services that are turned on for this Call Server. |
Step 6 | Select the appropriate tab and change the desired settings:
Configuration Tabs: |
Step 7 | When you finish configuring the Call Server, click Save to save the settings, or click Save & Deploy to save the changes and apply them to the Call Server. |
Step 8 | If you changed a configuration setting that requires a restart,
shut down and start the Call Server.
Configuration settings that require a restart of the Call Server are identified in Call Server Settings. |
To delete a Call Server:
To find a Call Server:
Step 1 | Select
from the Main menu.
The Find, Add, Delete, Edit Call Servers window lists the available Call Servers sorted by name, 10 at a time. | ||
Step 2 | If the list is long, you can click the first page, previous page, next page, and last page icons on the bottom right of the screen to page through the list. Or, you can enter a page number in the Page field and press enter to go directly to the numbered page. | ||
Step 3 | You can also filter the list by selecting an attribute such as
Hostname, selecting a modifier such as
begins with, entering your search term, and
then clicking
Find.
|
To view device statistics:
Step 1 | Select
.
The Find, Add, Delete, Edit Call Servers window opens. |
Step 2 | Find the Call Server by using the procedure in Find Call Server. |
Step 3 | From the list of matching records, select the Call Server that you want to edit. |
Step 4 | Click
Edit.
The Edit Call Server Configuration window opens with the current settings displayed. |
Step 5 | Click the
Statistics icon in the toolbar.
Statistics are reported for the selected device. |
If you are adding a Call Server (adding a Call Server) or editing a Call Server (editing a Call Server), you can configure the Call Server by filling in or changing values for one or more of these settings.
Property |
Description |
Default |
Range |
Restart Required |
---|---|---|---|---|
General |
||||
IP Address |
The IP address of the Call Server |
None |
Valid IP address |
No |
Hostname |
The hostname of the Call Server |
None |
A valid DNS name, which includes uppercase and lowercase letters in the alphabet, the numbers 0 through 9,and a dash |
No |
Description |
The description of the Call Server |
None |
0 - 1024 characters |
No |
Enable Secure Communication with the Ops Console |
Select to enable secure communications between the Operations Console and the Call Server. The device is accessed using SSH and files are transferred using HTTPS. You must configure secure communications before you enable this option. For more information, see the Configuration Guide for Cisco Unified Customer Voice Portal. |
None |
Enabled or Disabled |
Yes |
Device Version |
Lists the Release and Build Number for this device. |
Read Only |
Read Only |
Read Only |
Turn On Services |
||||
ICM |
Enables the Call Server to communicate with an ICM Server. The ICM Server must be configured in the Operations Console. |
None |
Not applicable |
Yes |
IVR |
The IVR Service creates VXML pages that implement the Micro-Applications, based on Run Script instructions received from the ICM Server. The VXML pages are sent to the VXML Gateway to be executed. |
None |
Not applicable |
Yes |
SIP |
Session Initiation Protocol (SIP), RFC 3261, is the primary call control protocol in Unified CVP. The SIP Service uses SIP to communicate with other Unified CVP solution components, such as the SIP Proxy Server, the VXML and Ingress Gateways, and Cisco Unified Communications Manager SIP trunks and SIP phones. Configure the SIP service if you are adding a new Call Server or editing a Call Server and you are using the Call Director or Comprehensive call flow models. |
None |
Not applicable |
Yes |
To apply a license file:
Step 1 | Select
.
The Find, Add, Delete, Edit Call Servers window lists any Call Servers that have been added to the Operations Console. |
Step 2 | Select a Call Server by clicking on the link in its Hostname field
or by clicking the radio button preceding it and then clicking
Edit.
The Edit Call Server Configuration window opens. |
Step 3 | Select
File Transfer in the toolbar and then click
Licensing.
The File Transfer page opens. |
Step 4 | If the license file is not listed in the Select From Available License Files text box: |
Step 5 | If the license is listed in the Select From Available License Files text box, select the license file. |
Step 6 | Click Transfer to transfer the selected license file to the Call Server. |
Step 7 | Shut down and start the Call Server. |
The Operations console renames the license file to cvp.license under the folder on the machine to which the file is transferred. If the file cvp.license already exists in the folder, the old cvp.license file will be deleted first, and then replaced with the new cvp.license file.
Reporting provides historical reporting to a distributed self-service deployment in a call center. The Reporting Server receives reporting data from one or more Call Servers and Unified CVP VXML Servers, and stores that data in an Informix database. Call data is stored in a relational database, on which you can write custom reports. Administrators can use the Operations Console to schedule data removal (delete) and database backups. Multiple Call Servers can send data to a single Reporting Server.
You can use third-party reporting tools such as Crystal Reports to generate and view reports on call data. Unified CVP provides four sample Crystal report templates. One of the included templates provides an example of joining Unified CVP and ICM data to create a comprehensive report.
You can perform the following tasks:Before You Begin
You must configure the Call Server to associate with the Reporting Server before configuring the Reporting Server.
Collect the following information about the Reporting Server and Reporting Database during the installation of Unified CVP software:
Host name of the Call Servers associated with the Reporting Server
![]() Note | A Call Server can only be associated with one Reporting Server. |
Hostname and IP address of the server on which the Reporting Database resides
Password for the Reporting Database user
To add a Reporting Server:
Step 1 | Select
.
A window listing Reporting Servers opens.
| ||
Step 2 | Click
Add New.
The Reporting Server Configuration window opens to the General Tab. | ||
Step 3 | Fill in the IP Address and Hostname for the Reporting server and fill in any other desired information. | ||
Step 4 | Associate one or more Call Servers to the Reporting server by selecting a Call Server listed in the Available pane and clicking the right arrow to add it to the Selected pane. | ||
Step 5 | Select the Reporting Properties tab and configure reporting properties. | ||
Step 6 | Optionally, select the Device Pool tab and add the Reporting Server to a device pool. | ||
Step 7 | Optionally, select the Infrastructure tab and configure log file and syslog settings. | ||
Step 8 | When you finish configuring the Reporting Server, click Save to save the settings in the Operations Server database. Click Save & Deploy to deploy the changes to the Reporting Server page. |
You can configure settings that identify the Reporting server, associate it with one or more Call Servers, and enable or disable security on the General Tab.
Field |
Description |
Default |
Range |
Restart Required |
---|---|---|---|---|
General |
||||
IP Address |
The IP address of the Reporting server |
None |
Valid IP address |
Yes |
Hostname |
The host name of the Reporting server machine |
None |
Valid DNS name, which can include letters in the alphabet, the numbers 0 through 9 |
Yes |
Description |
An optional text description for the Reporting server |
None |
Up to 1,024 characters |
No |
Enable Secure Communication with the Operations Console |
Select to enable secure communications between the Operations Server and this component. The Reporting Server is accessed using SSH and files are transferred using HTTPS. You must configure secure communications before you enable this option. For more information, see the Configuration Guide for Cisco Unified Customer Voice Portal. |
Off |
On or Off |
No |
Device Version |
Lists the Release and Build Number for this device. |
Read Only |
Read Only |
Read Only |
Associate Call Servers |
Select one or more Call Servers to associate with the Reporting Server. You must select at least one Call Server. Call data for all SIP, and VXML calls handled by this Call Server are stored in the Reporting Database. Click the right arrow to add a Call Server to the Selected pane. Click the left arrow to remove a Call Server from the Selected pane. |
None |
A given Call Server can only be associated with one Reporting Server. |
No |
You can configure Reporting Server settings on the Reporting Properties Tab.
Field |
Description |
Default |
Range |
Restart Required |
||
---|---|---|---|---|---|---|
Configuration |
||||||
Enable Reporting |
Enables the Reporting Server to receive call data from the associated Call Server(s). |
Yes |
Yes or No |
Yes |
||
Max. File Size (MB): |
Defines the maximum size of the file used to record the data feed messages during a database failover. This can be limited by the amount of free disk space. |
100 |
1 through 250 MB |
No |
||
QoS |
||||||
Select QoS Level |
Enables Quality of Service (QoS) between the Reporting Server and the Call Server.
|
default |
af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs1, cs2, cs3, cs4, cs5, cs6, cs7,default, ef |
Yes |
The Reporting Server publishes statistics on the number of reporting events received from the Unified CVP VXML Server, the SIP Service, and the IVR Service. It also publishes the number of times the Reporting Server writes data to the Reporting database. You can configure the interval at which the Reporting Server publishes these statistics, the maximum log file and directory size, and the details for recording syslog messages on the Reporting Server Infrastructure tab.
Field |
Description |
Default |
Range |
Restart Required |
||
---|---|---|---|---|---|---|
Configuration: Thread Management |
||||||
Maximum Threads |
(Required) The maximum thread pool size in the Reporting Server Java Virtual Machine. |
300 |
100 - 1000 |
Yes |
||
Advanced |
||||||
Statistics Aggregation Interval |
The Reporting Server publishes statistics at this interval. |
30 minutes |
10 - 1440 |
Yes |
||
Log File Properties |
||||||
Max Log File Size |
(Required) Maximum size of the log file in Megabytes. The log file name follows this format: CVP.DateStamp.SeqNum.log example: For example: CVP.2006-07-04.00.log After midnight each day, a new log file is automatically created with a new date stamp. When a log file exceeds the max log file size, a new one with the next sequence number is created, for example, when CVP.2006-07-04.00.log reaches 5 Mb, CVP.2006-07-04.01.log is automatically created. |
10 MB |
1 through 100 MB |
Yes |
||
Max Log Directory Size |
(Required) Maximum size of the directory containing Reporting Server log files.
|
20,000 MB |
500 - 500000 MB Max Log File size < Max Log Directory Size Max Log File size > 1 Max Log Dir Size / Max Log File Size cannot be greater than 5.000 |
Yes |
||
Configuration: Primary Syslog Settings |
||||||
Primary Syslog Server |
Hostname or IP address of Primary Syslog Server to send syslog events from a CVP Application. |
None |
Valid IP address or hostname. |
No |
||
Primary Syslog Server Port Number |
Port number of Primary Syslog Server. |
None |
Any available port number. Valid port numbers are integers between 1 and 65535. |
No |
||
Primary Backup Syslog Server |
Hostname or IP address of the Primary Backup Syslog Server to send syslog events from a CVP Application when the Syslog Server cannot be reached. |
None |
Valid IP address or hostname. |
No |
||
Primary Backup Syslog Server Port Number |
Port number of Primary Backup Syslog Server. |
None |
Any available port number. Valid port numbers are integers between 1 and 65535. |
No |
||
Configuration: Secondary Syslog Settings |
||||||
Secondary Syslog Server |
Hostname or IP address of Secondary Syslog Server to send syslog events from a CVP Application. |
None |
Valid IP address or hostname. |
No |
||
Secondary Syslog Server Port Number |
Port number of Secondary Syslog Server. |
None |
Any available port number. Valid port numbers are integers between 1 and 65535. |
No |
||
Secondary Backup Syslog Server |
Hostname or IP address of the Secondary Backup Syslog Server to send syslog events from a CVP Application when the Syslog Server cannot be reached. |
None |
Valid IP address or hostname. |
No |
||
Secondary Backup Syslog Server Port Number |
Port number of Secondary Backup Syslog Server. |
None |
Any available port number. Valid port numbers are integers between 1 and 65535. |
No |
To edit a Reporting Server:
Step 1 | Choose
.
The Find, Add, Delete, Edit Reporting Servers window opens. |
Step 2 | Select a Reporting Server by clicking on the link in its name
field or by clicking the radio button preceding it, and then clicking
Edit.
The Edit Reporting Server Configuration window opens. |
Step 3 | If you have not already applied a license, select
File Transfer in the toolbar and then click
Licensing.
The File Transfer page opens. |
Step 4 | On the General tab, change the desired general information. You cannot change the IP address of the Reporting Server. |
Step 5 | Select the Reporting Properties tab, then edit reporting properties. |
Step 6 | Optionally, you can select the Device Pool tab and add or remove the Reporting Server from a device pool. |
Step 7 | Optionally, you can select the Infrastructure tab and change log file and syslog settings. |
Step 8 | When you finish configuring the Reporting Server, click Save to save the settings in the Operations Console database. Click Save & Deploy to deploy the changes to the Reporting Server. |
Unified CVP Database Administrator - Uses the Operations Console to run backups, check database used space, and add and remove Reporting users.
Unified CVP Database User - Connects, inserts, and updates records in the Informix database. This user cannot modify the Reporting schema.
To change a reporting database user password:
Step 1 | Choose
.
The Find, Add, Delete, Edit Reporting Servers window opens. | ||
Step 2 | Select a Reporting Server by clicking on the link in its Hostname
field or by clicking the radio button preceding it and then clicking
Edit.
The Edit Reporting Server Configuration window opens with the current settings displayed. | ||
Step 3 | Select the
Database Administration menu in the toolbar,
then select
Change User Passwords.
The Reporting Server: Change User Passwords page opens, displaying the IP address and host name for the currently selected Reporting Server. | ||
Step 4 | In the User field, use the drop-down menu to select the user whose password you want to change. | ||
Step 5 | In Old Password field, enter the existing password for that user. | ||
Step 6 | In the
New Password field, enter the new password.
| ||
Step 7 | In the Reconfirm Password field, retype the new password. | ||
Step 8 | Click Save & Deploy to save the changes to the Operations Console database and deploy them to the Reporting Server. |
The cvp_dbadmin should create reporting users to run reports against the Reporting database. Reporting users should have read-only access to the Reporting database, so they cannot accidentally modify the database schema or data.
To add a new reporting user to the Reporting Server:
Step 1 | Choose
.
The Find, Add, Delete, Edit Reporting Servers window opens. |
Step 2 | Select a Reporting Server by clicking on the link in its name
field or by clicking the radio button preceding it, and then clicking
Edit.
You can also search for a Reporting Server. The Edit Reporting Server Configuration window opens. |
Step 3 | Select the
Database Administration menu in the toolbar,
then select
Manage Reporting Users.
The Reporting Server: Manage Users windows opens, listing the IP address and host name for the selected Reporting Server. |
Step 4 | In the Manage Users pane, click Add User. |
Step 5 | Enter the name for the user in the Username field. |
Step 6 | Enter a password for the new user in the Password field. |
Step 7 | Retype the password in the Reconfirm Password field. |
Step 8 | Click Add to add the user. |
To change a reporting user's password:
Step 1 | Choose
.
The Find, Add, Delete, Edit Reporting Servers window opens. |
Step 2 | Select a Reporting Server by clicking on the link in its name
field or by clicking the radio button preceding it and then clicking
Edit.
You can also search for a Reporting Server. The Edit Reporting Server Configuration window opens. |
Step 3 | Select the
Database Administration menu in the toolbar,
then select
Manage Reporting Users.
The Reporting Server: Manage Users window opens, listing the IP address and host name for the currently selected Reporting Server. |
Step 4 | In the Manage Users pane, click Change Password. |
Step 5 | From the Available users list, select the user whose password you want to change and click the left arrow. The user name is displayed in Username field. |
Step 6 | Type the user's original password in Old Password field. |
Step 7 | In the New Password field, type the new password. |
Step 8 | In the Reconfirm Password field, retype the new password. |
Step 9 | Click Change to make the change. |
To remove a reporting user from the Reporting Server:
Step 1 | Choose
.
The Find, Add, Delete, Edit Reporting Server window opens. |
Step 2 | Select a Reporting Server by clicking on the link in its name
field or by clicking the radio button preceding it and then clicking
Edit.
You can also search for a Reporting Server. The Edit Reporting Server Configuration window opens. |
Step 3 | Select
Database Administration in the toolbar, then
select
Manage Reporting Users.
The Reporting Server: Manage Users window opens, listing the IP address and host name for the currently selected Reporting Server. |
Step 4 | From the Available users list, select the user to remove and click the left arrow. The user will be displayed in Username field. |
Step 5 | Enter the Database Administrator password in Database Administrator Password field. |
Step 6 | Click Delete to delete the selected user. |
To run a reporting database backup:
Step 1 | Choose
.
The Find, Add, Delete, Edit Reporting Servers window opens. |
Step 2 | Select the Reporting Server to edit by clicking the link to its name under the Hostname column. |
Step 3 | Click
Edit.
The Reporting Server Configuration window opens with the current settings displayed. |
Step 4 | Select the
Database Administration menu in the toolbar,
then select
Reporting Database Backups.
The Reporting Server - Database Backup Activities page opens. The IP address and host name for the currently selected Reporting Server are listed. |
Step 5 | To launch a backup immediately, click Backup Now. To schedule a time for daily backups, select Schedule Daily Backups and then select the hour and minute of the start time. |
Step 6 | Enter your cvp_dbadmin password and click Save & Deploy. |
To cancel a reporting database backup:
Step 1 | Choose
.
The Find, Add, Delete, Edit Reporting Servers window opens. |
Step 2 | Select a Reporting Server by clicking on the link in its name
field or by clicking the radio button preceding it, and then clicking
Edit.
The Edit Reporting Server Configuration window opens with the current settings displayed. |
Step 3 | Select the
Database Administration menu in the toolbar,
then select
Reporting Database Backups.
The Reporting Server - Database Backup Activities page displays. The IP address and host name for the currently selected Reporting Server are listed. |
Step 4 | Click Cancel Daily Backups. |
Step 5 | Enter your cvp_dbadmin Password and Save & Deploy. |
To configure Reporting Database Delete settings:
Step 1 | Choose
.
The Find, Add, Delete, Edit Reporting Servers window opens. |
Step 2 | Select a Reporting Server by clicking on the link in its name
field or by clicking the radio button preceding it and then clicking
Edit.
The Edit Reporting Server Configuration window opens with the current settings displayed. |
Step 3 | Select the
Database Administration menu in the toolbar,
then select
Data Delete.
The Reporting Server - Database Delete Settings page opens, displaying the IP address and host name for the currently selected Reporting Server. |
Step 4 | In the Data Delete section of the page, you can change the data retention time for each category of data. |
Step 5 | Select the hours and minutes to run the delete each day. |
Step 6 | Enter your cvp_dbadmin Password and click Save & Deploy. |
Using the Operations Console, you can select the time of day to run database delete, and set the number of days that the data is retained by data category. The following table describes each category of data that you can delete from the Reporting Database and lists the default number of days that this data is kept before purging. A high level category, such as Call, cannot have a lower retention time than a dependent category, such as Call Event.
Choosing how much data is to be retained is a sensitive matter. If a database space fills up, then the database is able to continue processing until data is deleted. This is complicated by the fact that when Informix increases its extents for a table within the data file, due to data growth, extension remains even after the data is deleted. This causes space within the file to be reserved even if the actual space is no longer needed. The only way to regain the space is to rebuild the table.
Emergency delete is, a critical safety mechanism. If used space has grown past the system's threshold, the Reporting Server creates an SNMP trap, and data is deleted. The SNMP notification alerts the user to the loss of data, and data is deleted.
Data Category |
Description |
Default |
---|---|---|
Call |
Detailed information about calls received by Unified CVP. |
30 |
Call Event |
Call state change event messages published by the Call Server and Unified CVP VXML Server. SIP and IVR services publish call state change event messages when a SIP call changes its state. These states include call initiated, transferred, terminated, aborted, or an error state. |
30 |
VXML Session |
VXML session data includes application names, session ID, and session variables. Session variables are global to the call session on the Unified CVP VXML Server. Unlike element data, session data can be created and modified by all components (except the global error handler, hotevents, and XML decisions). |
30 |
VXML Element |
A VXML element is a distinct component of a voice application call flow whose actions affect the experience of the caller. A VXML element contains detailed script activity to the element level, such as, Call Identifiers, activity time stamp, VXML script name, name and type of the VXML element, and event type. |
15 |
VXML ECC Variable |
Expanded Call Context (ECC) variables that are included in VXML data. Unified CVP uses ECC variables to exchange information with Unified ICME. |
15 |
VXML Voice Interact Detail |
Application detailed data at the script element level from the Unified CVP VXML Server call services. This data includes input mode, utterance, interpretation, and confidence. |
15 |
VXML Session Variable |
VXML session variables are global to the call session on the Unified CVP VXML Server. |
15 |
VXML Element Detail |
The names and values of element variables. |
15 |
Callback |
Retention days for Courtesy Callback reporting data |
15 |
Trunk Utilization Usage |
Retention days for Gateway Trunk Utilization reporting data |
15 |
The data categories are hierarchical. For example. Call data includes Call Event and VXML Session data.
VXML Session Data Categories:
![]() Note | A high level category, such as Call, cannot have a lower retention time than a dependent category, such as CallEvent. |
To view database details:
Step 1 | Choose
.
The Find, Add, Delete, Edit Reporting Servers window opens. | ||
Step 2 | Select a Reporting Server by clicking on the link in its name
field or by clicking the radio button preceding it, and then clicking
Edit.
The Edit Reporting Server Configuration window opens with the current settings displayed. | ||
Step 3 | Select the
Database Administration menu in the toolbar,
and then select
Database Details.
The Reporting Server - Disk Drives: Housing Database Files page opens, displaying the IP address and host name for the currently selected Reporting Server along with the following database information: Reporting Database Details:
|
To get Reporting Server statistics:
Step 1 | Choose
.
The Find, Add, Delete, Edit Reporting Servers window opens. |
Step 2 | Select a Reporting Server by clicking on the link in its name
field or by clicking the radio button preceding it, and then clicking
Edit.
The Edit Reporting Server Configuration window opens with the current settings displayed. |
Step 3 | Select
Statistics in the toolbar.
The Reporting Server Statistics are listed in the Reporting tab. |
To delete a reporting server:
Step 1 | Choose
.
The Find, Add, Delete, Edit Reporting Servers window displays. |
Step 2 | Find the Reporting Server to delete by using the procedure in Find Reporting Server. |
Step 3 | From the list of matching records, choose the Reporting Server that you want to delete. |
Step 4 | Click Delete. |
Step 5 | When prompted to confirm the delete operation, click OK to delete or click Cancel to cancel the delete operation. |
To apply a license file:
Step 1 | Choose
.
The Find, Add, Delete, Edit Reporting Server window lists any Reporting Servers that have been added to the Operations Console. |
Step 2 | Select a server by clicking on the link in its Hostname field or by clicking the radio button preceding it and then clicking Edit. |
Step 3 | Select
File Transfer in the toolbar and then click
Licensing.
The File Transfer page displays, listing the Hostname and IP Address for the currently selected Reporting Server. |
Step 4 | If the license file is not listed in the Select From Available License Files text box: |
Step 5 | If the license is listed in the Select From Available License Files text box, select the license file. |
Step 6 | Click
Transfer to transfer the selected license file
to the selected device.
The license is applied to the selected server. |
The Operations Console renames the license file to cvp.license under the directory on the machine to which the file is transferred. If the file cvp.license already exists in the directory, the old cvp.license file will be deleted first, and then replaced with the new cvp.license file.
To find a Reporting Server:
Step 1 | Choose
.
A list of the available Reporting Servers appears, 10 devices per screen, sorted by name. | ||
Step 2 | If the list is long, click the first page, previous page, next page, and last page icons on the bottom right of the window to page through the list. Or, you can enter a page number in the Page field and press enter to go directly to the numbered page. | ||
Step 3 | You can also filter the list by selecting an attribute such as
Hostname. Then select a modifier, such as
begins with, enter your search term, and then click
Find.
|
The Unified CVP VXML Server is an optional J2EE-compliant application server that provides a solution for rapidly creating and deploying dynamic VXML applications. If you installed a Unified CVP VXML Server, you must configure it before using it to deploy VXML applications or licenses.
If you are using a VXML gateway to route calls from the Unified CVP VXML Server, but want to use the Unified CVP reporting feature, install the Call Server and Reporting Server on the same physical machine. Configure the Call Server with no call services enabled, then configure the Reporting Server and select the Call Server that is installed on the same machine (same IP address) as the primary call server for the Reporting Server.
To make requests to an ICM server, without relinquishing control of the call or use Unified CVP reporting, you must configure the Unified CVP VXML Server to use a Call Server with at least the ICM Service enabled.
You can perform the following tasks:
Before adding a VXML Server to the Operations Console, ensure that you have done the following:
Collect the hostname or IP address of the Unified CVP VXML Server during the installation of Unified CVP software.
Install and configure at least one Call Server before configuring the Unified CVP VXML Server.
![]() Note | You do not need to install a Call Server if you are adding a Unified CVP VXML Server (standalone). |
Review Call Studio scripts, noting any of the following items you want to include or exclude from Unified CVP VXML Server reporting data:
To add a Unified CVP VXML Server:
Step 1 | Choose
.
The Find, Add, Delete, Edit Unified CVP VXML Servers window opens.
| ||
Step 2 | Click
Add New.
The Unified CVP VXML Server Configuration window opens to the General Tab. | ||
Step 3 | Fill in the IP Address and Hostname fields and a primary Call Server. | ||
Step 4 | Select each tab and verify that the default values are correct or
change the values if desired:
Configuration tabs: | ||
Step 5 | When you finish configuring the Unified CVP VXML Server, click Save to save the settings in the Operations Console database. Click Save & Deploy to apply the changes to the Unified CVP VXML Server. | ||
Step 6 | Shut down and then start the Unified CVP VXML Server and the primary and backup Call Servers. |
To edit a Unified CVP VXML Server configuration:
Step 1 | Choose
.
The Find, Add, Delete, Edit Unified CVP VXML Servers window opens. |
Step 2 | You can search for a VXML Server by using the procedure in the Finding a Unified CVP VXML Server topic. |
Step 3 | From the list of matching records, choose the Unified CVP VXML Server that you want to edit. |
Step 4 | Click
Edit.
The Unified CVP VXML Server Configuration window opens to the General Tab. |
Step 5 | Change any general server information. You cannot change the IP address of the VXML Server. |
Step 6 | Select the Configuration Tab, then edit Unified CVP VXML Server properties. |
Step 7 | Optionally, you can select the Device Pool tab and add or remove the Unified CVP VXML Server from a device pool. |
Step 8 | Optionally, you can select the Infrastructure tab and configure log file and syslog settings. |
Step 9 | When you finish configuring the Unified CVP VXML Server, click Save to save the settings in the Operations Server database. Click Save & Deploy to apply the changes to the Unified CVP VXML Server. |
Step 10 | If instructed, shut down and then start the Unified CVP VXML Server and the primary and backup Call Servers. |
To delete a Unified CVP VXML Server from the Control Center:
Step 1 | Choose
.
The Find, Add, Delete, Edit Unified CVP VXML Servers window opens. |
Step 2 | From the list of matching records, select the Unified CVP VXML Server that you want to delete by clicking the radio button preceding it. |
Step 3 | Click Delete. |
Step 4 | When prompted to confirm the delete operation, click OK to delete or click Cancel to cancel the delete operation. |
Step 5 | Shut down and start the Unified CVP VXML Server and the primary and backup Call Servers. |
You can configure settings that identify the Unified CVP VXML Server and choose a primary, and optionally, a backup Call Server to communicate with the Reporting Server. You can also enable secure communications between the Operations Console and the Unified CVP VXML Server.
Field |
Description |
Default |
Range |
Restart/Reboot Needed |
---|---|---|---|---|
General |
||||
IP Address |
The IP address of the Unified CVP VXML Server |
None |
A valid IP address |
No |
Hostname |
The host name of the Unified CVP VXML Server. Host names must be valid DNS names, which can include letters in the alphabet, the numbers 0 through 9, and a dash. |
None |
A valid DNS name, which includes uppercase and lowercase letters in the alphabet, the numbers 0 through 9, and a dash. |
No |
Description |
The Unified CVP VXML Server description |
None |
Up to 1,024 characters |
No |
Enable secure communication with the Ops console |
Select to enable secure communications between the Operations Server and this component. The device is accessed using SSH and files are transferred using HTTPS. Configure secure communications before you enable this option. For more information, see the Configuration Guide for Cisco Unified Customer Voice Portal. |
None |
On or Off |
Yes - reboot |
Device Version |
Lists the Release and Build Number for this device. |
Read Only |
Read Only |
Read Only |
Call Servers |
||||
Primary Unified CVP Call Server |
The Unified CVP VXML Server uses the message service on this Call Server to communicate with the Reporting Server and to perform an ICM lookup. Select a primary Call Server from the drop-down list. The drop-down list includes all Call Servers added to the Operations Console. |
None |
Not applicable |
Yes - Restart Call Server and Unified CVP VXML Server |
Backup Unified CVP Call Server |
The Unified CVP VXML Server uses the message service on this Call Server to communicate with the Reporting Server and perform an ICM lookup if the primary Call Server is unreachable. Select a backup Call Server from the drop-down list. The drop-down list includes all Call Servers added to the Operations Console. |
None |
Not applicable |
Yes - Restart Call Server and VXML Server |
When the primary Call Server is unreachable, the Unified CVP VXML Sever uses the backup Call Server to communicate with the Reporting Server and to perform an ICM lookup. But the VXML Server does not continuously try to re-establish a connection with the primary Call Server. The VXML Server continues to use the backup Call Server until you restart either the Unified CVP VXML Server or the backup Call Server.
From the Unified CVP VXML Server Configuration tab, you can enable the reporting of Unified CVP VXML Server and call activities to the Reporting Server. When enabled, the Unified CVP VXML Server reports on call and application session summary data. Call summary data includes call identifier, start and end timestamp of calls, ANI, and DNIS. Application session data includes application names, session ID, and session timestamps.
If you choose detailed reporting, Unified CVP VXML Server application details are reported, including element access history, activities within the element, element variables and element exit state. Customized values added in the Add to Log element configuration area in Call Studio applications are also included in reporting data. You can also create report filters that define which data are included and excluded from being reported.
Field |
Description |
Default |
Range |
Restart/Reboot Needed |
||||
---|---|---|---|---|---|---|---|---|
Configuration |
||||||||
Enable Reporting for this Unified CVP VXML Server |
Indicates whether or not the Unified CVP VXML Server sends data to the Reporting Server. If disabled, no data is sent to the Reporting Server, and reports do not contain any VXML application data. |
Enabled |
Enabled (the default) or Disabled. |
No |
||||
Enable Reporting for VXML Application Details |
Indicates whether VXML application details are reported. |
Disabled |
Enabled or Disabled (the default). |
No |
||||
Max. Number of Messages |
Define the maximum number of reporting messages that will be saved in a file if failover occurs. (Limited by amount of free disk space.) |
100,000 |
Not applicable |
Not applicable |
||||
QoS |
||||||||
Select QoS Level |
The level of transmission quality and service availability for the Unified CVP VXML Server.
|
cs3 |
The drop-down list has the following values: af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs1, cs2, cs3, cs4, cs5, cs6, cs7,default, and ef
|
Yes - Restart VXML Server |
||||
VXML Applications Details: Filters |
||||||||
Inclusive Filters |
List of applications, element types, element names, and element fields, and ECC variables to include in reporting data. |
None |
A semicolon-separated list of text strings. A wildcard character (*) is allowed within each element in the list.
|
Yes - Restart VXML Server |
||||
Exclusive Filters |
List of applications, element types, element names, and element fields, and ECC variables to exclude from reporting data. |
None |
A semicolon-separated list of text strings. A wildcard character (*) is allowed within each element in the list.
|
Yes - Restart VXML Server |
Field |
Description |
Default |
Range |
Restart Required |
||
---|---|---|---|---|---|---|
Configuration: Thread Management |
||||||
Maximum Threads |
(Required) The maximum thread pool size in the VXML Server Java Virtual Machine. |
300 |
100 - 1000 |
Yes |
||
Advanced |
||||||
Statistics Aggregation Interval |
The VXML Server publishes statistics at this interval. |
30 minutes |
10 - 1440 |
Yes |
||
Log File Properties |
||||||
Max Log File Size |
(Required) Maximum size of the log file in Megabytes. The log file name follows this format: CVP.DateStamp.SeqNum.log example: For example: CVP.2006-07-04.00.log After midnight each day, a new log file is automatically created with a new date stamp. Also, when a log file exceeds the max log file size, a new one with the next sequence number is created, for example, when CVP.2006-07-04.00.log reaches 5 Mb, CVP.2006-07-04.01.log is automatically created. |
10 MB |
1 through 100 MB |
Yes |
||
Max Log Directory Size |
(Required) Maximum size of the directory containing VXML Server log files.
|
20,000 MB |
500 - 500000 MB Max Log File size < Max Log Directory Size Max Log File size > 1 Max Log Dir Size / Max Log File Size cannot be greater than 5.000 |
Yes |
||
Configuration: Primary Syslog Settings |
||||||
Primary Syslog Server |
Hostname or IP address of Primary Syslog Server to send syslog events from a CVP Application. |
None |
Valid IP address or hostname. |
No |
||
Primary Syslog Server Port Number |
Port number of Primary Syslog Server. |
None |
Any available port number. Valid port numbers are integers between 1 and 65535. |
No |
||
Primary Backup Syslog Server |
Hostname or IP address of the Primary Backup Syslog Server to send syslog events from a CVP Application when the Syslog Server cannot be reached. |
None |
Valid IP address or hostname. |
No |
||
Primary Backup Syslog Server Port Number |
Port number of Primary Backup Syslog Server. |
None |
Any available port number. Valid port numbers are integers between 1 and 65535. |
No |
||
Configuration: Secondary Syslog Settings |
||||||
Secondary Syslog Server |
Hostname or IP address of Secondary Syslog Server to send syslog events from a CVP Application. |
None |
Valid IP address or hostname. |
No |
||
Secondary Syslog Server Port Number |
Port number of Secondary Syslog Server. |
None |
Any available port number. Valid port numbers are integers between 1 and 65535. |
No |
||
Secondary Backup Syslog Server |
Hostname or IP address of the Secondary Backup Syslog Server to send syslog events from a CVP Application when the Syslog Server cannot be reached. |
None |
Valid IP address or hostname. |
No |
||
Secondary Backup Syslog Server Port Number |
Port number of Secondary Backup Syslog Server. |
None |
Any available port number. Valid port numbers are integers between 1 and 65535. |
No |
You use Inclusive and Exclusive VXML filters to control the data that the Unified CVP VXML Server feeds to the Reporting Server.
Data feed control is crucial for:
To configure inclusive and exclusive filters for a Reporting Server:
Step 1 | Choose
.
The Find, Add, Delete, Edit Unified CVP VXML Servers window opens. |
Step 2 | You can search for a Unified CVP VXML Server by using the procedure in the Finding a Unified CVP VXML Server topic. |
Step 3 | From the list of matching records, choose the Unified CVP VXML Server that you want to edit. |
Step 4 | Click
Edit.
The Unified CVP VXML Server Configuration window opens to the General Tab. |
Step 5 | Select the Configuration Tab, then configure Unified CVP VXML Server properties. |
Step 6 | In the VXML Applications Details: Filters pane, enter an inclusive filter that defines the VXML elements to include in data sent to the Reporting Server. |
Step 7 | Optionally, enter an exclusive filter that excludes some of the data specified by the inclusive filter. |
Step 8 | When you finish configuring filters, click Save to save the settings in the Operations Console database or click Save & Deploy to save and apply the changes to the Unified CVP VXML Server. |
Step 9 | Shut down and then start the Unified CVP VXML Server and the primary and backup Call Servers. |
Inclusive and exclusive filters operate using the following rules:
Filters are case sensitive.
By default, all items except the Start, End, Subdialog_Start and Subdialog_End elements are filtered from reporting data unless they are added to an Inclusive Filter. The Subdialog_Start and Subdialog_End elements are never filtered from reporting data unless Reporting is disabled on the Unified CVP VXML Server.
The Exclusive Filter takes precedence over the Inclusive Filter. For example, if an application name is in the Exclusive Filter, then the items of that applications are excluded from reporting data even if a particular field or element is listed in the Inclusive filter.
The syntax for Inclusive/Exclusive filters is:
Appname.ElementType.ElementName.FieldName
or
AppName.*.*.SESSION:Varname
![]() Note | This syntax indicates session variables. |
Use a semicolon (;) to separate each item in a filter. For example, ElementA ; ElementB is valid.
Use a single wildcard (*) anywhere within the application name, element type, element name, or field name.
Element types, element names, and field names can contain alphanumeric characters, underscores, and a space character.
An application name can contain alphanumeric characters and underscores, but the space character is not allowed. For example, A_aa.B_bb.*C_cc_DD.E_ee_F* is valid.
The table below provides examples of VXML filter wildcard matching.
Filter |
What It Matches |
---|---|
MyApplication.voice.*.* |
Matches all voice elements in MyApplication |
*.voice.*.* |
Matches all Voice elements in all applications |
MyApplication.*.*.var* |
Matches all fields in MyApplication that start with the string var |
MyApplication.*.*.*3 |
Matches all fields in MyApplication that end with 3 |
MyApplication.*.*.SESSION:Company |
Matches the Company session variable in MyApplication |
The table below provides examples of some different combinations of Inclusive and Exclusive filters and the resulting data that the Unified CVP VXML Server feeds to the Reporting Server.
Inclusive Filter |
Exclusive Filter |
Data the Unified CVP VXML Server Feeds To the Reporting Server |
---|---|---|
Application1.*.*.* |
None |
All Application1 data |
Application1.*.*.* |
*.*.Element1.*; *.*.Element2.* |
All Application1 data, except Element1 and Element2 |
Application1.*.*.* |
*.*.Element1.*; *.*.Element2.*; *.*.*.Field1 |
All Application1 data, except Element1, Element2, and Field1 |
Application1.*.*.* |
*.voice.*.* which matches Element3 and Element4 |
All Application1 data, except Element3 and Element4 |
*.*.Element1.*; *.*.Element2.*; *.*.*.Field1 |
Application1.*.*.* |
No data for Application1. Other Data for other applications, such as Application2, which contain Element1, Element2 and Field1, will be fed. |
*.voice.*.* which matches Element1, Element2, Element3, and Element4 |
*.*.Element3.*; *.*.Element4.* |
Only Element1 and Element2 and all applications. |
*.voice.*.* which matches Element1 and Element2 |
*.*.*.Field1 |
Element1 and Element2, except for Field1, if it exists in those elements |
*.*.Element1.* |
None |
Element1 |
*.*.Element1.* |
*.*.*.Field1 |
Element1, except for Field1 if it exists in Element1 |
*.*.*.Field1 |
*.*.Element3.*; *.*.Element4.* |
Field1 in any elements except Element3 and Element4 |
A good strategy for using filters is to create an Inclusive filter that includes the data you want to save in the Reporting database and then create an Exclusive filter to exclude portions of the data, for example, sensitive security information such as Social Security Numbers. For example, you
Applications transferred to a Unified CVP VXML Server or Unified CVP VXML Server (standalone) must be stored in the .zip archive format, otherwise the Operations Console returns an invalid format error message and the file is not transferred. Use the Call Studio archive feature to create .zip application files to be transferred to a Unified CVP VXML Server or Unified CVP VXML Server (standalone).
To create an Archive file using Call Studio:
Right-click on a project in the Navigator view, and choose Deploy.
Under Deploy Destination, choose Archive File.
Enter the location and filename of the destination file in the Archive File text field.
![]() Note | The filename must end with a ".zip" extension. |
Click Finish.
Transferring a file is a two-step process:
Upload the file to the Operations Console.
Select one or more servers to transfer the uploaded file to.
To transfer VXML application files to the Unified CVP VXML Server (standalone):
The Find, Add, Delete, Edit window lists any servers that have been added to the Operations Console.
The VXML Application File Transfer page opens, listing the host name and IP address for the selected device. VXML applications currently stored in the Operations Server database are listed in the Select From available VXML applications box.
The VXML application is transferred to the selected server.
To download a Log Messages XML file from the Operations Console to a Unified CVP Server:
Step 1 | From the Device Management menu, choose the type of server from
which you want to download a syslog XML file. For example, to download a file
to a Unified CVP VXML Server, choose
.
The Find, Add, Delete, Edit window lists any servers that have been added to the control panel. |
Step 2 | Select a server by clicking on the link in its Hostname field or by clicking the radio button preceding it and then clicking Edit. |
Step 3 | Select
File Transfer in the toolbar and then click
Log Messages XML File Download.
The Log Messages XML Download dialog box opens. |
Step 4 | Click
Download to transfer the XML file to the
server.
A message indicates that this operation takes time. Click OK to continue with the download or click Cancel. |
Each Unified CVP Call Server, Unified CVP VXML Server, and Reporting Server has a log messages XML file and log message file. You can edit the CVPLogMessages.xml file on a particular Unified CVP server to customize the severity, destination and possible resolution for each event that the server generates. You can also edit the CVPLogMessagesRes.properties file to change the text of the message that is generated when an event occurs on that server.
Use any plain-text editor (one that does not create any markup) or XML editor to edit the CVPLogMessages.xml file. Use a resource file editor, to edit the CVPLogMessagesRes.properties file. If a resource file editor is not available, use a text editor.
Message Element |
Possible Values |
What it Means |
---|---|---|
Name |
Resource="identifier" |
Identifies the event type described in the CVPLogMessagesRes.properties file. |
Body |
Resource="identifier" |
Identifies the message text described in the CVPLogMessagesRes.properties file. |
Severity |
0 to 6 |
Identifies the severity level of the event. See Unified CVP Event Severity Levels. |
SendToSNMP |
True or false |
Set to true, to send this message, when logged, to an SNMP manager, if one is configured. |
SendToSyslog |
True or false |
Set to true to send this message, when logged, to a Syslog server, if one is configured. |
SNMPRaise |
True or false |
Set to true to identify this message, when logged, as an SNMP raise event, which the SNMP management station can use to initiate a task or automatically take an action. Set to false to identify this message as an SNMP clear when sent to an SNMP management station. An SNMP clear event usually corresponds to an SNMP raise event, indicating that the problem causing the raise has been corrected. An administrator on an SNMP management station can correlate SNMP raise events with SNMP clear events. |
The following table describes the available severity levels for Unified CVP events. You can set the severity level for an event by editing the log messages XML file, CVPLogMessages.xml, on the server that generates events. For instructions on editing this file, see Edit Log Messages XML File.
Level |
Severity |
Purpose |
---|---|---|
EMERGENCY |
0 |
System or service is unusable |
ALERT |
1 |
Action must be taken immediately |
CRITICAL |
2 |
Critical condition, similar to ALERT, but not necessarily requiring an immediate action |
ERROR |
3 |
An error condition that does not necessarily impact the ability of the service to continue to function |
WARN |
4 |
A warning about a bad condition, which is not necessarily an error |
NOTICE |
5 |
Notification about interesting system-level conditions, which are not errors |
INFO |
6 |
Information about internal flows or application or per-request information, not system-wide information |
To upload a Log Messages XML file from a Unified CVP Server to the Operations Console:
Step 1 | From the Device Management menu, select the type of server to
which you want to upload a syslog XML file. For example, to upload a file to a
Unified CVP VXML Server, select
.
The Find, Add, Delete, Edit window lists any servers that have been added to the control panel. |
Step 2 | Select a server by clicking on the link in its Hostname field or by clicking the radio button preceding it and then clicking Edit. |
Step 3 | Select
File Transfer in the toolbar and then click
Log Messages XML File Upload.
The Log Messages XML Upload page opens. |
Step 4 | In the Select a Log Messages XML file from your local PC text box, enter a file name or click Browse and search for the file on your local system. |
Step 5 | Click Upload to transfer the selected file to the Unified CVP VXML Server. |
Step 6 | Shut down and then start the corresponding Unified CVP VXML Server. |
To apply a license file:
Step 1 | Select
.
The Find, Add, Delete, Edit Unified CVP VXML Server window lists any servers that have been added to the Operations Console. |
Step 2 | Select a server by clicking on the link in its Hostname field or by clicking the radio button preceding it and then clicking Edit. |
Step 3 | Select
File Transfer in the toolbar and then click
Licensing.
The File Transfer page displays, listing the Hostname and IP Address for the currently selected Unified CVP VXML Server. |
Step 4 | If the license file is not listed in the Select From Available License Files text box: |
Step 5 | If the license is listed in the Select From Available License Files text box, select the license file. |
Step 6 | Click
Transfer to transfer the selected license file
to the selected device.
The license is applied to the selected server. |
To find a Unified CVP VXML Server:
Step 1 | Select
.
The Find, Add, Delete, Edit Unified CVP VXML Servers window lists the available Unified CVP VXML Servers, 10 at a time, sorted by name. | ||
Step 2 | If the list is long, click the first page, previous page, next page, and last page icons on the bottom right of the widow to page through the list. Or, you can enter a page number in the Page field and press enter to go to the page. | ||
Step 3 | You can also filter the list by selecting an attribute such as
Hostname. Then select a modifier, such as
begins with, enter your search term, and then click
Find.
|
In the Unified CVP VXML Server (standalone) call flow model, the Call Server routes messages between the components. Calls arrive through a VXML gateway and interact directly with a Unified CVP VXML Server to execute VXML applications. The gateway performs both ingress and VXML functions. This call flow model provides a sophisticated VXML-based VRU, for applications which in many cases do not need to interact with an ICM Server.
You can perform the following tasks:
To add a Unified CVP VXML Server (standalone):
Step 1 | Choose
.
The Find, Add, Delete, Edit Unified CVP VXML Server (standalone) window opens.
| |||||||||||||||||||||||||||||||||||
Step 2 | Click
Add
New.
The Unified VXML Server (standalone) Configuration window opens to the General Tab. | |||||||||||||||||||||||||||||||||||
Step 3 | Fill in the IP
address and hostname and an optional description for the Unified CVP VXML
Server.
| |||||||||||||||||||||||||||||||||||
Step 4 | Optionally, you can select the Device Pool Tab and add the server to an additional device pool. | |||||||||||||||||||||||||||||||||||
Step 5 | When you finish configuring Unified CVP VXML Server (standalone), click Save to save the settings in the Operations Console database. Click Save & Deploy to save and apply the changes to the Unified CVP VXML Server (standalone). |
To delete a Unified CVP VXML Server (standalone):
Step 1 | Select
.
The Find, Add, Delete, Edit Unified CVP VXML Servers (standalone) window opens. |
Step 2 | Select the Unified CVP VXML Server (standalone) by clicking the radio button preceding it and then clicking Delete. To narrow the list of servers see Find Standalone Unified VXML Server. |
Step 3 | Click Delete. |
Step 4 | When prompted to confirm the delete operation, click OK to delete or click Cancel to cancel the delete operation. |
To edit a Unified CVP VXML Server (standalone):
Step 1 | Choose
.
The Find, Add, Delete, Edit Unified CVP VXML Servers (standalone) window opens. | |||||||||||||||||||||||||||||||||||||
Step 2 | Select a server
by clicking on the link in its Hostname field or by clicking the radio button
preceding it and then clicking
Edit.
the Unified CVP VXML Server (standalone) Configuration window opens to the General Tab. | |||||||||||||||||||||||||||||||||||||
Step 3 | Make the desired
changes to the settings. You cannot change the IP address.
| |||||||||||||||||||||||||||||||||||||
Step 4 | When you finish editing Unified CVP VXML Server (standalone), click Save to save the settings in the Operations Console database. Click Save & Deploy to save and apply the changes to the Unified CVP VXML Server (standalone). |
To find a Unified CVP VXML Server (standalone):
Step 1 | Select
.
The Find, Add, Delete, Edit Unified CVP VXML Server (standalone) window lists the available Unified CVP VXML Server (standalone) sorted by name, 10 at a time. | ||
Step 2 | If the list is long, click the first page, previous page, next page, and last page icons on the bottom right of the window to page through the list. Or, enter a page number in the Page field and press enter to go directly to the numbered page. | ||
Step 3 | You can also filter the list by selecting an attribute such as
Hostname. Then select a modifier, such as
begins with, enter your search term, and then click
Find.
|
To apply a license file:
Step 1 | Select
.
The Find, Add, Delete, Edit Unified CVP VXML Servers (standalone) window lists any servers that have been added to the Operations Console. |
Step 2 | Select a server by clicking on the link in its Hostname field or by clicking the radio button preceding it and then clicking Edit. |
Step 3 | Select
File Transfer in the toolbar and then click
Licensing.
The File Transfer page displays, listing the Hostname and IP Address for the currently selected Unified VXML Server (Standalone). |
Step 4 | If the license file is not listed in the Select From Available License Files text box: |
Step 5 | If the license is listed in the Select From Available License Files text box, select the license file. |
Step 6 | Click
Transfer to transfer the selected license file
to the selected device.
The license is applied to the selected server. |
From the Device Management menu, Gateway option, you can add an IOS Gateway to the Operations Console. Once added, you can execute a subset of IOS Gateway commands on the Gateway from the Operations Console.
The Ingress Gateway is the point at which an incoming call enters the Unified CVP solution. It terminates TDM phone lines on one side and implements VoIP on the other side. It also provides for sophisticated call routing capabilities at the command of other Unified solution components. It works with SIP protocols, and also supports MGCP for use with Unified CM.
The VXML Gateway hosts the IOS voice browser, the component which interprets VXML pages from either the Unified CVP IVR service or the VXML Server, plays .wav files and Text-to-Speech (TTS), inputs voice and DTMF, and sends results back to the VXML requestor. It also mediates between Media Servers, Unified CVP VXML Servers, ASR and TTS Servers, and the IVR service.
The Ingress Gateway may be deployed separately from the VXML Gateway, but in most implementations they are the same: one Gateway performs both functions. Gateways are often deployed in farms, for centralized deployment models. In Branch deployment models, one combined Gateway is usually located at each branch office.
An Egress Gateway is typically used in Call Director Model to provide access to a call center ACD or third-party IVR.
See Also:
In Unified CVP there are fields for Trunk Group ID. If the Call Server associated with this Gateway has Enable Gateway Trunk Reporting checked on the ICM tab, then the Trunk Group ID is used for Gateway trunk reporting. The default value is 300, however the value can be from 1 to 65535.
To add a Gateway:
Step 1 | Select
.
The Find, Add, Delete, Edit Gateways window opens. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Click
Add
New.
The Gateway Configuration window opens.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Fill in the IP
address, hostname, Trunk Group ID, user password, and enable password for the
Gateway:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | Optionally, you can select the Device Pool tab and add the Gateway to a device pool. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | When you finish configuring the Gateway, click Save to save the configuration. |
To delete a Gateway:
Step 1 | Select
.
The Find, Add, Delete, Edit Gateways window opens. |
Step 2 | Find the Gateway using the procedure in Find Gateway. |
Step 3 | Select the radio button next to the Gateway that you want to
delete and click
Delete.
If this Gateway is assigned to a system-level configuration location or trunk utilization, then the association must be removed prior to deleting this Gateway. |
To edit a Gateway:
Step 1 | Select
.
The Find, Add, Delete, Edit Gateways window opens. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Find the Gateway using the procedure in Find Gateway. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | From the list of matching records, select the Gateway that you want to edit. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | Click on the
Gateway name to edit it.
The Gateway Configuration window opens with the current settings displayed on the General tab. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | Change the
appropriate configuration settings.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 6 | Optionally, you can select the Device Pool tab and add edit the device pool setting. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 7 | When you finish editing the Gateway configuration, click Save. |
To find a Gateway:
Step 1 | Select
.
The Find, Add, Delete, Edit Window lists the available Gateways, 10 at a time, sorted by name. | ||
Step 2 | If the list is long, you can click the first page, previous page, next page, and last page icons on the bottom right of the screen to page through the list. Or, you can enter a page number in the Page field and press enter to go directly to the numbered page. | ||
Step 3 | You can also filter the list by selecting an attribute such as
Hostname. Then select a modifier, such as
begins with, enter your search term, and then click
Find.
|
To transfer scripts between the Operations Console and a Gateway:
Step 1 | Select
.
The Find, Add, Delete, Edit Gateway window lists any Gateways that have been added to the Operations Console. |
Step 2 | Select a Gateway by clicking on the link in its name field or by
clicking the radio button preceding it, and then clicking
Edit.
The Edit Gateway Configuration window opens. |
Step 3 | Select
from the Gateway configuration toolbar.
The File Transfer window opens. |
Step 4 | Select a script and media file to transfer to the Gateway.
|
Step 5 | When you have selected the script and media file to transfer, click Transfer to copy the selected script and media file to the Operations Console and the Gateway. |
To get Gateway statistics:
Step 1 | Choose
.
The Find, Add, Delete, Edit Gateways window opens. |
Step 2 | Select a Gateway by clicking on the link in the Hostname field or
by clicking the radio button preceding it and then clicking
Edit.
The Edit Gateway Configuration window opens to the General tab. |
Step 3 | Click
Statistics in the toolbar and then select the
type of statistics to view from the drop-down menu.
The Gateway Statistics Results window opens, displaying the selected statistics. If the statistics fill the display area, use the scroll bar to move forward and backward or up and down in the display. See View Gateway Statistics. |
To execute a Gateway commands:
Step 1 | Select
.
The Find, Add, Delete, Edit Gateways window opens. | ||||||||
Step 2 | If you are editing an existing Gateway configuration, click Edit. | ||||||||
Step 3 | Select IOS Commands from the Gateway Configuration toolbar. | ||||||||
Step 4 | From the IOS Commands drop-down menu, select an IOS command to
execute on the Gateway.
You can execute the following IOS Gateway commands from the IOS Commands drop-down menu on the Gateway Configuration window.
If the command fails, the error will be displayed in an error web page. |
A Speech Server provides speech recognition and synthesis services. You can add a pre-configured Speech Server to the Operations Console. Once added to the Operations Console, you can add a Speech Server to one or more device pools.
A Speech Server provides speech recognition services and text-to-speech services for a VXML Gateway.
![]() Note | The Operations Console can only manage Speech Servers installed on Microsoft Windows. |
You can perform the following tasks:
Install the Remote Operations in the Speech Server before you add the Speech Server to the Operations console.
Step 1 | Select . The Find, Add, Delete, Edit Speech Server window opens.
| |||||||||||||||||||||||||||||||||||||
Step 2 | Click Add New. The Speech Server Configuration window opens. | |||||||||||||||||||||||||||||||||||||
Step 3 | Fill in the appropriate configuration settings on the General tab as described in Speech Server Configuration Settings. You can change the settings described in the following table to configure a Speech Server.
| |||||||||||||||||||||||||||||||||||||
Step 4 | Select the Device Pool tab to optionally add the Speech Server to additional device pools. | |||||||||||||||||||||||||||||||||||||
Step 5 | Click Save to save the settings in the Operations Console database. Click Save & Deploy to deploy the changes to the Speech Server. |
To delete a Speech Server:
Step 1 | Select
.
The Find, Add, Delete, Edit Speech Server window opens. |
Step 2 | Select the Speech Server by clicking the radio button preceding it and then clicking Delete. To narrow the list of servers see Find Speech Server. |
Step 3 | When prompted to confirm the delete operation, click OK to delete or click Cancel to cancel the delete operation. |
To edit a Speech Server:
Step 1 | Select . The Find, Add, Delete, Edit Speech Server window opens. | |||||||||||||||||||||||||||||||||||||
Step 2 | Select the radio button next to the Speech Server that you want to edit, and click Edit. | |||||||||||||||||||||||||||||||||||||
Step 3 | Change the appropriate configuration settings on the General tab. You can change the settings described in the following table to configure a Speech Server.
| |||||||||||||||||||||||||||||||||||||
Step 4 | Select the Device Pool tab to optionally add or remove the Speech Server to or from device pools. | |||||||||||||||||||||||||||||||||||||
Step 5 | When you finish configuring the Speech Server, click Save to save the settings in the Operations Console database. Click Save & Deploy to deploy the changes to the Speech Server. |
To find a Speech Server:
Step 1 | Select
.
The Find, Add, Delete, Edit Speech Servers window lists the available Call Servers sorted by name, 10 at a time. | ||
Step 2 | If the list is long, you can click the first page, previous page, next page, and last page icons on the bottom right of the window to page through the list. Or, you can enter a page number in the Page field and press enter to go directly to the numbered page. | ||
Step 3 | You can also filter the list by selecting an attribute such as
Hostname. Then select a modifier, such as
begins with, enter your search term, and then click
Find.
|
To apply a license file:
Step 1 | Select
.
The Find, Add, Delete, Edit Speech Server window opens. |
Step 2 | Select the radio button next to the Speech Server that you want to edit and click Edit. |
Step 3 | Make sure the License File Location lists the correct path of the license file on the Speech Server. The Operations Console transfers the license file to this location. |
Step 4 | Select
File Transfer in the toolbar and then click
Licenses.
The License File Transfer page displays, listing the host name and IP address for the currently selected Speech Server. |
Step 5 | If the license is listed in the Select From Available License Files text box, select the license file. |
Step 6 | If the license file is not listed in the Select From Available License Files text box: |
Step 7 | Click
Transfer to transfer the selected license file
to the selected device.
The license is applied to the selected server. |
When you add and deploy a Media Server(s) to the Operations Console, that information gets pushed to all the Callservers. It is similar to how WebServices information gets added to the CVP devices. This automatically populates the media servers in the FTP element of the Studio application. You can designate a default media server.
The Media Server is a simple web server/FTP server (if FTP enabled) with the sole purpose within Unified CVP to store and serve .wav files to the VXML gateway, as required in order to render VXML pages. The VXML gateway caches the .wav files it retrieves from the Media Server. In most deployments, the Media Server encounters extremely low traffic from Unified CVP.
The Media Server must be an IIS web server on a separate machine, with FTP enabled. The Agent Greeting recording script requires the Media Server to have FTP enabled. This is done automatically with Unified CVP as long as the Media Server is configured with Add Media Server. Using Tomcat on the Unified CVP VXML server is not a supported configuration as a Media Server, and the FTP element in the recording application fails if the FTP operation fails.
You can perform the following tasks:To add a Media Server:
![]() Note | Whenever you add, edit, or delete a Media Server, you must click the Deploy button to make the change effective. |
Step 1 | Select
.
The Find, Add, Delete, Edit Media Server window opens.
| |||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Click
Add New.
The Media Server Configuration window opens. | |||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Fill in the appropriate configuration settings on the General tab.
The following table describes the fields that can be configured for a Media Server:
| |||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | Optionally, you can select the Device Pool tab and add the Media Server to a device pool. See Add and Remove Media Server From Device Pool. | |||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | When you finish configuring the Media Server, click Save. |
To delete a Media Server:
![]() Warning | You will receive a special prompt if you attempt to delete the default Media Server. |
![]() Note | Whenever you add, edit, or delete a Media Server, click the Deploy button to make the change effective. |
Step 1 | Select
.
The Find, Add, Delete, Edit Media Server window opens. |
Step 2 | Select the Media Server by clicking the radio button preceding it and then clicking Delete. To narrow the list of servers see Find Media Server. |
Step 3 | When prompted to confirm the delete operation, click OK to delete or click Cancel to cancel the delete operation. |
A default media server device may be specified in the Operations Console. If specified, micro-applications use that default media server if the ECC variable for the media server is not defined in the UCCE ICM script.
To deploy a Media Server to all Call Servers:
Step 1 | Select
.
The Find, Add, Delete, Edit Media Server window opens. | ||
Step 2 | From the Default Media Server drop-down menu, select the default Media Server. | ||
Step 3 | Click the Set button next to the Media Server you want to set as the default Media Server. | ||
Step 4 | Click the
Deploy button to have the default Media Server sent
to the Call Servers and VXML Servers.
You must select the Deploy button to have the Media Server sent to the Call Servers and VXML Servers.
|
To edit a Media Server:
![]() Note | Whenever you add, edit, or delete a Media Server, click the Deploy button to make the change effective. |
Step 1 | Select
.
The Find, Add, Delete, Edit Media Server window opens. | |||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | From the list of matching records, select the Media Server that you want to edit. | |||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Select the radio button next to the Media Server you want to Edit, and then click Edit. | |||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | Change appropriate configuration settings on the General tab. You
cannot change the IP address of the Media Server.
The following table describes the fields that can be configured for a Media Server:
| |||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | Optionally, you can select the Device Pool tab and edit the Media Server's association with a device pool. See Add and Remove Media Server From Device Pool. | |||||||||||||||||||||||||||||||||||||||||||||||||
Step 6 | When you finish configuring the Media Server, click Save. |
To find a Media Server:
Step 1 | Select
.
The Find, Add, Delete, Edit Call Servers window lists the available Media Servers sorted by name, 10 at a time. | ||
Step 2 | If the list is long, click the first page, previous page, next page, and last page icons on the bottom right of the window to page through the list. Or, you can enter a page number in the Page field and press enter to go to the numbered page. | ||
Step 3 | You can filter the list by selecting an attribute such as
Hostname. Then select a modifier, such as
begins with, enter your search term, and then click
Find.
|
To add or remove a Media Server from a device pool:
Step 1 | Select
.
The Find, Add, Delete, Edit Media Server window opens. |
Step 2 | From the list of matching records, select the Media Server that you want to edit. |
Step 3 | Click Edit. |
Step 4 | Select the Device Pool tab. |
Step 5 | To add a device to a device pool, select the device pool from the Available pane, and then click the right arrow to move the pool to the Selected pane. |
Step 6 | To remove a device from a device pool, select the device pool from the Selected pane, and then click the left arrow to move the device pool to the Available pane. |
Step 7 | Click Save. |
To view the status of the Media Server device list:
From the Device Management menu, Communications Manager option, you can add a Unified CM Server to the Operations Console. Once added, you can add the Unified CM Server to a device pool and access a Unified CM administration web page, from which you can configure the Unified CM Server.
Unified CM manages and switches VoIP calls among IP phones. Unified CVP interacts with Unified CM to send PSTN-originated calls to UCCE agents.
![]() Note | If the Unified CM was synchronized for its configured locations, and the Unified CM synchronization is disabled or the Unified CM device is deleted, then the previously configured synchronization locations are marked as invalid. |
You can perform the following tasks:
Use this procedure to add a Unified CM Server. See the following table for the Unified CM field descriptions.
Field |
Description |
Default |
Range |
Restart Required |
---|---|---|---|---|
General |
||||
IP Address |
The IP address of the Unified CM Server. |
None |
Valid IP address |
No |
Hostname |
The name of the Unified CM Server |
None |
Valid DNS names, includes letters in the alphabet, the numbers 0 through 9, and a dash. |
No |
Description |
The description of the Unified CM Server |
None |
Any text |
No |
Device Admin URL |
The Administration URL for the Unified CM Server |
None |
A valid URL. The Operations Console validates the URL for syntax errors but does not check that the site exists. |
No |
Enable Synchronization (See Synchronize Location Information for more information.) |
||||
Enable synchronization |
Select to enable synchronization for location. If enabled, the Operations Console extracts (synchronizes) the Unified CM location information from the Unified CM server. |
Disabled When you enable this service, the Port field defaults to 8443. |
Enabled or Disabled |
No |
Username |
User name to access the Unified CM AXL interface. |
None |
Valid Unified CM AXL username. |
No |
Password |
Password to access the Unified CM AXL interface |
None |
Valid Unified CM AXL password. |
No |
Confirm Password |
Retype the password to verify that you typed the password correctly |
None |
Text must match the text entered in the Password field |
No |
Port |
The port to which the Unified CM server connects when establishing initial contact |
8443 |
1 through 65535 |
No |
Step 1 | Select
.
The Find, Add, Delete, Edit Unified ICM Servers window opens. | ||
Step 2 | Click
Add New.
The Unified ICM Server Configuration window opens to the General tab. | ||
Step 3 | Fill in the appropriate configuration settings.
See the Unified CM configuration settings field descriptions table for details.
To enable Cisco AXL Web Service on the Unified CM, perform the following steps: | ||
Step 4 | (Optional)Select the Device Pool tab and add the Unified CM Server to a device pool. | ||
Step 5 | When you finish configuring the Unified CM, click Save. |
Use this procedure to edit a Unified CM Server.
See the following table for the Unified CM field descriptions
Field |
Description |
Default |
Range |
Restart Required |
||
---|---|---|---|---|---|---|
General |
||||||
IP Address |
The IP address of the Unified CM Server.
|
None |
Valid IP address |
No |
||
Hostname |
The name of the Unified CM Server |
None |
Valid DNS names, includes letters in the alphabet, the numbers 0 through 9, and a dash. |
No |
||
Description |
The description of the Unified CM Server |
None |
Any text |
No |
||
Device Admin URL |
The Administration URL for the Unified CM Server |
None |
A valid URL. The Operations Console validates the URL for syntax errors, but does not check that the site exists. |
No |
||
Enable Synchronization for Location (See Synchronize Location Information for more information.) |
||||||
Enable synchronization |
Select to enable synchronization for location. If enabled, the Operations Console extracts (synchronizes) the Unified CM location information from the Unified CM server. |
Disabled When you enable this service, the Port field defaults to 8443. |
Enabled or Disabled |
No |
||
Username |
User name to access the Unified CM AXL interface. |
None |
Valid names include uppercase and lowercase alphabetical letters, the numbers 0 through 9, a dash, and an underscore. |
No |
||
Password |
Password to access the Unified CM AXL interface |
None |
Any text that follows the requirements for choosing secuire passwords. See General User Information Settings. |
No |
||
Confirm Password |
Retype the password to verify that you typed the password correctly |
None |
Text must match the text entered in the Password field |
No |
||
Port |
The port to which the Unified CM server connects when establishing initial contact |
8443 |
1 through 65535 |
No |
Step 1 | Select
.
The Find, Add, Delete, Edit Unified ICM Servers window opens. | ||
Step 2 | Select the Unified CM Server that you want to edit. To narrow down the list of servers see Find Unified CM Server. | ||
Step 3 | Click
Edit.
The Edit Unified CM Server Configuration window opens to the General tab with the current settings displayed. | ||
Step 4 | Update the configuration settings as required. See the Unified CM configuration settings field descriptions table for details.
To enable Cisco AXL Web Service on the Unified CM, perform the following steps: | ||
Step 5 | (Optional)Select the Device Pool tab and add the server to a device pool. | ||
Step 6 | When you finish configuring the server, click Save to save the configuration. |
To delete a Unified CM Server:
Step 1 | Select
.
The Find, Add, Delete, Edit Unified ICM Servers window opens. |
Step 2 | Select the Unified CM Server that you want to delete. To narrow down the list of servers, see Find Unified CM Server. |
Step 3 | Click Delete. |
Step 4 | When prompted to confirm the delete operation, click OK or click Cancel. |
To find a Unified CM Server:
Step 1 | Select
.
The Find, Add, Delete, Edit Unified ICM Servers window lists the available Unified ICM Servers, sorted by name, 10 at a time. | ||
Step 2 | If the list is long, click the first page, previous page, next page, and last page icons on the bottom right of the window to page through the list. Or, you can enter a page number in the Page field and press enter to go to the numbered page. | ||
Step 3 | You can also filter the list by selecting an attribute such as
Hostname. Then select a modifier, such as
begins with, enter your search term, and then clickFind.
|
Unified CVP provides VoIP routing services for the Unified CCE and Unified CCX products. Unified ICM provides the services to determine where calls should be routed, whether to ACDs, specific agents, or to VRUs, but the routing services themselves must be provided by an external routing client.
A Unified ICM Server is required in Unified CVP Comprehensive, Call Director, and VRU-Only call flow models.
You can perform the following tasks:
To add an ICM Server:
Step 1 | Select
.
The Find, Add, Delete, Edit ICM Server window opens.
| ||||||||||||||||||||||||||||||
Step 2 | Click
Add New.
The Unified ICM Server Configuration window opens. | ||||||||||||||||||||||||||||||
Step 3 | Fill in the appropriate Unified ICM configuration settings on the
General tab.
| ||||||||||||||||||||||||||||||
Step 4 | In the Unified ICM server, enter the information in the
Enable Serviceability panel so that
Serviceability information for this Unified ICM server is distributed using the
web services manager feature of Unified CVP.
| ||||||||||||||||||||||||||||||
Step 5 | (Optional)Select the Device Pool tab and add the Unified ICM Server to a device pool. | ||||||||||||||||||||||||||||||
Step 6 | When you finish configuring the Unified ICM Server, click Save. |
To delete an Unified ICM Server:
Step 1 | Select
.
The Find, Add, Delete, Edit Unified ICM Server window opens. |
Step 2 | Select the Unified ICM Server that you want to delete. To narrow the list of servers see Find Unified ICM Server. |
Step 3 | Click Delete. |
Step 4 | When prompted to confirm the delete operation, click OK or click Cancel. |
To edit a Unified ICM Server:
Step 1 | Select
.
The Find, Add, Delete, Edit Unified ICM Server window opens. | ||||||||||||||||||||||||||||||||
Step 2 | Select the Unified ICM Server that you want to edit. To narrow the list of servers see Find Unified ICM Server. | ||||||||||||||||||||||||||||||||
Step 3 | Click
Edit.
The Unified ICM Server Configuration window opens and displays the current settings. | ||||||||||||||||||||||||||||||||
Step 4 | Change the appropriate Unified ICM Server configuration settings
on the General tab as required.
| ||||||||||||||||||||||||||||||||
Step 5 | In the Unified ICM server, you
can change the information in
Enable Serviceability panel.
| ||||||||||||||||||||||||||||||||
Step 6 | Update the Device Pool tab settings. | ||||||||||||||||||||||||||||||||
Step 7 | When you are finished configuring the Unified ICM Server, click Save. |
To find a Unified ICM Server:
Step 1 | Select
.
The Find, Add, Delete, Edit Unified ICM Servers window lists the available Unified ICM Servers. | ||
Step 2 | If the list is long, click the first page, previous page, next page, and last page icons on the bottom right of the window to page through the list. Or, you can enter a page number in the Page field and press enter to go to the numbered page. | ||
Step 3 | You can also filter the list by selecting an attribute such as
Hostname. Then select a modifier, such as
begins with, enter your search term, and then click
Find.
|
From
, add a SIP Proxy Server to the Operations Console. Once added, you can add the SIP Proxy Server to a device pool. You can also configure a link to the administration web page for the SIP Proxy Server so that you can access that page from the Operations Console.A SIP Proxy Server is a device that routes individual SIP transport messages among SIP endpoints. It plays a key role in high availability in a Unified CVP deployment for call switching. It is designed to support multiple SIP endpoints of various types, and implements load balancing and failover among those endpoints. SIP Proxy Servers are deployed alone or as a pair. Also, smaller Unified CVP deployments run without a SIP Proxy Server. In such cases, the Unified CVP SIP service assumes some of those functions because it configures a static table to look up destinations.
Unified CVP works with RFC-3261-compliant SIP Proxy Servers and has been qualified with the following:
You can perform the following tasks:
To add a SIP Proxy Server:
Step 1 | Select
.
The Find, Add, Delete, Edit SIP Servers window opens.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Click
Add New.
The SIP Server Configuration window opens. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Fill in the appropriate SIP Proxy Server configuration settings on
the
General tab.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | Optionally, select the Device Pool tab and add the SIP Proxy Server to a device pool. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | When you finish configuring the SIP Proxy Server, click Save. |
To edit SIP Proxy Server:
Step 1 | Select
.
The Find, Add, Delete, Edit SIP Servers window opens. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Select the SIP Proxy Server that you want to edit. If the list is too long, see Find SIP Proxy Server. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Click
Edit.
The SIP Proxy Server Configuration window opens and displays the current settings. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | Fill in the appropriate configuration settings on the General tab.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | (Optional)Select the Device Pool tab and update the device pool settings. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 6 | When you finish configuring the SIP Proxy Server, click Save. |
To delete a SIP Proxy Server:
Step 1 | Select
.
The Find, Add, Delete, Edit SIP Proxy Server window opens. |
Step 2 | Select the radio button next to the SIP Proxy Server that you want to delete. If the list is too long, see Find SIP Proxy Server. |
Step 3 | Click Delete. |
Step 4 | When prompted to confirm the delete operation, click OK or click Cancel. |
To find a SIP Proxy Server:
Step 1 | Select
.
The Find, Add, Delete, Edit SIP Proxy Servers window lists the available proxy servers of the type you selected, sorted by name, 10 at a time. | ||
Step 2 | If the list is long, click the first page, previous page, next page, and last page icons on the bottom right of the window to page through the list. Or, you can enter a page number in the Page field and press enter to go directly to the numbered page. | ||
Step 3 | You can also filter the list by selecting an attribute such as
Hostname. Then select a modifier, such as
begins with, enter your search term, and then click
Find.
|
The Unified Intelligence Center (Unified IC) Server is a device type in Operations Console for Unified CVP.
To support a Unified CVP reporting solution, install and configure a Unified IC Server with the Unified CVP Reporting Server.
![]() Note | To use an existing Unified IC Server as a template for creating the new Unified IC Server, select the Unified IC Server by clicking the radio button preceding it, and then click Use As Template. |
You can perform the following tasks:
Configured Unified IC Servers are listed in the Device Past Configurations table listing. Unified IC Server devices are only saved to the Operations Console database--they are not saved and deployed. Consequently, each Unified IC Server is listed as one past configuration entry.
The Unified IC Server is a standalone device and is not integrated with Unified CVP. Therefore, the Unified IC Server is not displayed in the Device Versions table.
A Unified IC Server device is not included as a selectable device in the SNMP menu option windows.
If you select a Unified CVP Reporting Server for deletion and this server has a Unified IC Server association, a warning message prompts you to remove the association.
To add a Unified IC Server to the Operations Console database and associate it with a Unified CVP Reporting Server:
Step 1 | Select
.
All Unified IC Servers that have been added to the Operations Console are listed in the Find, Add, Delete, Edit Unified IC Servers list. | |||||||||||||||||||||||||
Step 2 | Click
Add New.
The Unified IC Server Configuration window opens to the General tab. | |||||||||||||||||||||||||
Step 3 | Enter the IP Address and Hostname of the Unified IC Server. | |||||||||||||||||||||||||
Step 4 | (Optional)Provide a description. | |||||||||||||||||||||||||
Step 5 | (Optional)Enter the Device Admin URL. If you do not provide one, a default URL is automatically inserted when you save. | |||||||||||||||||||||||||
Step 6 | (Optional)Provide the serviceability information for this
server:
| |||||||||||||||||||||||||
Step 7 | Assigning Unified CVP Reporting Servers is optional. One Unified CVP Reporting Server can be assigned to multiple Unified IC Server devices. By associating a Reporting Server, you are tracking that this Reporting Server is being set up as a data source for Unified IC. | |||||||||||||||||||||||||
Step 8 | Click
Device Pool to associate the Unified IC Server
to a device pool.
The default device pool is automatically assigned to the newly-configured Unified IC Server. You can specifically assign the Unified IC Server to required device pool. | |||||||||||||||||||||||||
Step 9 | When you finish configuring the Unified IC Server click Save to save the settings in the Operations Console database. |
To edit an existing Unified IC Server:
Step 1 | Select
.
The Find, Add, Delete, Edit Unified IC Server window opens. |
Step 2 | Select a Unified IC Server by clicking on the link in its name
field or by clicking the radio button preceding it, and then clicking
Edit. To narrow the list of servers see
Find Unified IC Server.
All fields are pre-populated with existing configuration information if available: IP Address (read-only, required), Hostname (required), Description, Device Admin URL, and Reporting Server Assignment. Serviceability information is also present if configured. See Add Unified IC Server for details on the fields. |
Step 3 | (Optional)Select the Device Pool tab to add/remove devices the device pool. |
Step 4 | When you finish configuring the Unified IC Server, click Save to save the settings in the Operations Console database. |
One Unified CVP Reporting Server can be assigned to several Unified IC Servers. Before the assigned Unified CVP Reporting Server can be deleted, these associated references in the Unified IC devices must also be removed. When you select a Unified CVP Reporting Server for deletion and that server has a Unified IC Server association, you receive a warning message prompting you to delete all Unified IC Server associations.
You can delete existing Unified IC Servers using the procedure specified in this section.
To delete a Unified IC Server:
Step 1 | Select
.
The Find, Add, Delete, Edit Unified IC Server window opens. |
Step 2 | Select the required Unified IC Server by clicking the radio button preceding it, and then clicking Delete. To narrow the list of servers see Find Unified IC Server. |
Step 3 | When prompted to confirm the delete operation, click OK or click Cancel. |
To find a Unified IC Server:
Step 1 | Select
.
The Find, Add, Delete, Edit Unified IC Servers window lists the available Unified IC Servers, sorted by name. | ||
Step 2 | If the list is long, you can click the first page, previous page, next page, and last page icons on the bottom right of the window to page through the list. Or, you can enter a page number in the Page field and press enter to go to the numbered page. | ||
Step 3 | You can also filter the list by selecting an attribute such as
Hostname. Then select a modifier, such as
begins with, enter your search term, and then click Find.
|
You can view the past 10 saved configurations of a selected device that are currently stored in the Operations Console database.
You can perform the following tasks:
To find a past configuration for a device:
Step 1 | Select . | ||
Step 2 | If the list is long, click the first page, previous page, next page, and last page icons on the bottom right of the window to page through the list. Or, you can enter a page number in the Page field and press enter to go to the numbered page. | ||
Step 3 | You can also filter the list by selecting an attribute such as
Hostname. Then select a modifier, such as
begins with, enter your search term, and then click
Find.
|
To view the details of a past configuration for a device:
Step 1 | Select . |
Step 2 | Select the device configuration by clicking the radio button
preceding it and then clicking
Past Configurations.
The List of Past Configurations window lists the configurations that have been saved for the selected device. |
Step 3 | Select a device past configuration to view by clicking the link in
the description field or by clicking the radio button preceding it, and then
clicking
View.
Configuration details for the selected past configuration are displayed. |
To apply a past configuration to a device:
Step 1 | Select from the Main menu. | ||
Step 2 | Select the device configuration by clicking the radio button
preceding it, and then clicking
Past Configurations.
The List of Past Configurations window lists the configurations that have been saved for the selected device. | ||
Step 3 | Select a device past configuration to view by clicking the link in
the description field or by clicking the radio button preceding it, and then
clicking
View.
Configuration details for the selected past configuration are displayed. | ||
Step 4 | Click
Save to save the selected configuration to the
database.
|
From the Device Management menu, Device Version option, you can view version information for the Call Server, Reporting Server, Unified CVP VXML Server, and Unified CVP VXML Server (standalone). Device version information is available for CVP specific devices only.
To view version information for CVP device types: