16
Cisco CallManager 3.0 Confidential
INTUITYTM
AUDIX Message
Server
Configuration Note 9122 - Ver. C 1/03
Cisco CallManager 3.0
1.0 METHOD OF INTEGRATION
Describe how call information is sent from the Cisco CallManager to the INTUITYTM
With RS-232 integration, call information is transmitted over a digital link between the Cisco CallManager and the INTUITYTM ä. Voice communications are provided by a separate path created by a hunt group of single-line stations on the Cisco CallManager that connect to voice port cards within the INTUITYTM. When an incoming call is received by the hunt group, it is accompanied by a digital message in standard SMDI format from the Cisco CallManager which contains call information. The INTUITYTM then answers the call on the specified port and plays the appropriate greeting. To set or cancel message-waiting notification, the INTUITYTM sends a digital message over the RS-232 link to the Cisco CallManager.
2.0 AVAYA Intuity ORDERING INFORMATION
Avaya INTUITYTM Requirements
· Voice Port Cards (IVC6), six analog connections per card
· Multi-Port Serial Card (Provides 8 RJ11 connections)
· INTUITYTM Software Release 5.0 (or later) platform software
· Serial and Inband Integration Software
3.0 CIsco Callmanager HARDWARE REQUIREMENTS
Hardware requirements
· Cisco CallManatger PC with one available serial (com) port
· Analog station ports, one per INTUITYTM port. Analog ports are provided via FXS ports on Cisco Analog Gateways, such as AS-4, AS-8, VG200 Gateways or WS-X6624-FXS Analog Interface Modules
· One analog station for remote service access
· Null Cable DB9-to-DB9 connector
Cisco software requirements
3.1 Cisco callmanager SOFTWARE REQUIREMENTS
· Minimum software level – Version 3.0.X
4.0 SUPPORTED integration FEATURES
Supported integration features
· Station forward to personal greeting
- all calls
· System forward to personal greeting
- busy
- no answer
· Message Waiting Indicator
- stutter dial tone
- lights (IP sets only)
· Automated Attendant
· Outcalling
· Multiple Return-to-operator
· Direct Call
· Personal greeting of original-called party on a multiple-call forward
· Reply to message left by subscriber in internal telephone-answering mode
Configuring the Cisco CallManager for Integration
5.0 CONFIGURING THE CISCO CALLMANAGER FOR INTEGRATION
The Cisco CallManager allows integration to INTUITYTM systems through the Cisco Messaging Interface (CMI). This interface provides an SMDI data stream to the INTUITYTM . Voice connectivity is achieved over analog lines from Cisco Access Analog Station Gateway ports. The following steps are needed to properly configure the Cisco CallManager software to integrate with the INTUITYTM :
o The Cisco CallManager must have Cisco Messaging Interface loaded whenever the Cisco CallManager is installed or upgraded. To verify that CMI is installed, Open CallManager Administration. Select Service. Cisco Messaging Interface should be one of the available services listed.
o Add the Analog ports in CallManager Administration. Open CallManager Administration.
Select Device. Select Add a New Device. Click Next.
Select Device Type. Select Gateway. The Gateway – New screen is displayed. Click Next.
In the Device Type box, select AS-4 Gateway if using AS-4 Gateway(s); select AS-8 Gateway if using AS-8 Gateway(s); select Cisco Catalyst 6000 24 port FXS Gateway if using WS-X6624-FXS Analog Module ports; select Cisco VG200 if using Cisco Voice Gateway 200 ports. For additional information on Cisco VG200 configuration, refer to section 5.1.
Click Next. When adding Analog Access gateways (AS-4, AS-8, Cisco Catalyst 6000 24 Port FXS Gateway), the Device Wizard - MAC Address screen is displayed.
In the MAC Address box, type the gateway's MAC address. The MAC address is the 12-character number on the rear (AS-4, AS-8) or front (Cisco Catalyst 6000 24 Port FXS Gateway) of the gateway. For example, 0010EB001C11. In the Description box, type a description, such as Gateway1 or Voicemail. This is an optional box.
In the Device Pool box, select the device pool you want this gateway assigned to. The device pool determines the Region, Date/Time Group, and CallManager Group the gateway will use.
In the Load Information box, select Default.
In the Country Code box, select the country in which the gateway is located from the drop-down selection box.
Select a valid Location and Calling Search Space, if required, or leave those two fields to <None>.
In the Port Selection Order box, select the order you want the ports to be selected on the gateway. Top Down means the channels are selected in descending order from 1 to 4/8/24; Bottom Up means the channels are selected in ascending order 4/8/24 to 1. If you're not sure which port order to use, choose Top Down.
You can configure the ports on the gateway in this screen. Click on the Add a New Port box. In the Port Type field, select POTS. In the Port Number drop-down box, select the port number you’re adding. In the End Port Number drop-down box, select that same port number. It is important to add one port at a time in this fashion; selecting All Ports from the drop-down box when adding Analog Access gateway ports will result in voicemail integration failure.
Select Insert. A new screen will appear. Leave all parameters at their default setting, except for Call Restart Timer. Enter 1234 as the value for this parameter. This will allow CallManager to provide a positive disconnect signal to the Octel port. Click Update and Close. Repeat these last steps to add all remaining ports on the gateway. Do not configure a DN (Directory Number) for these ports, as they will be configured later into a Route Group and associated with a Route Pattern.
o Add a Route Group comprised of analog ports assigned to voicemail.
After all the required Analog Station Gateway ports have been added, select Route Plan. Click on Route Group.
In the Route Group Name field, enter a descriptive name, such as SJ-voicemail, Vmail, etc.
Click Continue. In Device Name drop-down box, select the newly configured gateway(s). In the Port drop-down box, select port 1. In the Order drop-down box, select 1. Click Insert. To add subsequent ports, click Add Device, and follow the steps above. In the Port and Order drop-down boxes, select 2 for port 2; select 3 for port 3; and so on. Do not select “All” when adding gateway ports to the Route Group, as this will result in voicemail integration failure.
Click Finish.
o Add the Route Group to a Route List.
Although not necessary for proper integration, adding the newly created Route Group to a Route List will make administration simpler, specially when multiple gateways are used for connectivity to the INTUITYTM .
Select Route Plan. Select Route List. The Route List Configuration - New (step 1 of 1) screen is displayed. A Route List organizes a collection of Route Groups. The Order is the priority of each Route Group in the collection. The Order determines the progress of a search for available devices to select for a call. In the Route List Name box, enter a name for this Route List. It is once again recommended using a descriptive name, such as Vmail, Voicemail, SJ-vmail, etc.
Click Insert. Click Add Route Group. A new screen will appear. From the Select Route Group drop-down box, select the newly created Route Group. Click Add. A new screen will appear. Within this screen, you can add Calling/Called Party Transformation Masks, if required, pr leave all fields to their default settings. Click Insert. A feedback screen indicates the Route Group has been added to the Route List. Click Update. The Route Group you added will be displayed under the Route List.
o Add a Route Pattern.
Select Route Plan. Click Route Pattern.
The Route Pattern - New screen is displayed. In the Route Pattern box, type the Route Pattern, including numbers and wildcards (do not use spaces or dashes). In this case, the Route Pattern is the INTUITY Access Number. This is the number subscribers will dial to access the INTUITYTM . This is also the number subscriber phones will be forwarded to for ring-no-answer and busy conditions.
In the Gateway/Route List drop-down box, select the newly created Route List. Uncheck Provide Outside Dial Tone. In the Discard Digits drop-down box, select <None>.
Click Update. The Route Pattern is now added.
o Configure the Cisco Messaging Interface.
Select Service. Select Cisco Messaging Interface.
In the Cisco Messaging Interface Configuration screen, click on a valid CallManager server, if one is already configured for CMI services. If no server has been configured for CMI, in the Select new server: drop-down box, select the CallManager server that will be used to provide the SMDI link to the INTUITYTM .
After a valid CallManager has been selected and entered, several parameters must be configured from proper SMDI link operation.
Select VoiceMailDn. Enter the INTUITYTM Access Number. Click Update.
Select SerialPort. Enter COM1 (default). Click Update. This COM port will connect to the INTUITYTM and a customer-provided DB9-to-DB9 connector.
Select BaudRate. Enter 9600 (default). Click Update.
Select Parity. Enter Even (default). Click Update.
Select DataBits. Enter 7 (default). Click Update.
Select StopBits. Enter 1 (default). Click Update.
The following parameters are optional and in the majority of cases will NOT require any modification:
“OutputDnFormat” – default “%010s”. This parameter allows you to “pad” the output string with a specified digit. In this case the “%” character is a formatting command. The character string “010s” tells CMI to format the SMDI message as a 10-digit string with leading “0”’s. e.g. In order to have CMI output a 7-digit string you would configure “OutputDnFormat” as “%07s”. The “s” simply tells CMI to output the result as a string.
“OutputExternalFormat” – default “%010s”. This parameter is used when you have a Voicemail system that is expecting a string “length” greater than the extension “length” on CallManager e.g. For a Voicemail system expecting a 7-digit string connected to a CallManager configured with 4-digit extensions you would configure “OutputExternalFormat” as “525%4s”. This would result in a string of “5251234” for extension 1234.
“Keep alive DN” This parameter is used when the voice mail system sends a test message waiting command to determine the status of the SDMI link. Upon sending this message waiting command the voice mail system expects a MWI meassage back across the link. Enter the test extension used by the voice mail system, ie 5551212.
“InputDnSignificantDigits” – default “10”. In the case of our Voicemail system that is sending a 7-digit string for MWI commands to a CallManager system configured for 4-digit extensions, we would configure “InputDnSignificantDigits” = “4” e.g. We are keeping the “4” least significant digits.
Configuring the FXS ports on VG200 gateways
5.1 configuring Cisco vg200 ports
o Add the Analog ports in CallManager Administration. Open CallManager Administration.
Select Device. Select Add a New Device. Click Next.
Select Device Type. Select Gateway. Click Next. The Gateway - New screen is displayed. In the Gateway Type drop-down box, select Cisco VG200. Click Next.
In the MGCP Domain Name field, enter the host name as defined on the Cisco VG200 gateway. You must use the same value here that is used to configure the Cisco VG200 gateway at the IOS command line. In the Description field, enter a descriptive name for this device. Click Insert.
In the Module in Slot 1 drop-down box, select the module type installed in the VG200 to be configured. Click Insert.
In the VIC in Sub-Unit 0 drop-down box, select VIC-2FXS. In the VIC in Sub-Unit 1 drop-down box, select VIC-2FXS, if a second VIC module is used on the VG200. Click Update.
The gateway is now configured with 4 analog ports (Endpoint Identifiers). Click on the first port to be configured. In the Port Type drop-down box, select POTS. A new screen will appear. Select a valid Device Pool from the drop-down list. Leave all other parameters to their default settings. Click Insert.
Follow these steps to configure the additional VG200 ports.
o Once the ports have been added and assigned to a Route Group/Route List within CallManager Administration, you need to configure additional VG200 IOS parameters. Below is a sample IOS configuration of a Cisco VG200 gateway:
mgcp
mgcp call-agent 10.1.1.2
! IP Address of CallManager
mgcp dtmf-relay codec all mode out-of-band
mgcp ip-tos precedence 5
! Sets IP “Precedence” of RTP Stream to 5
mgcp default-package hs-package
ccm-manager switchback immediate
ccm-manager redundant-host 10.1.1.253
! Sets Backup CallManager – if applicable
ccm-manager mgcp
!
interface FastEthernet0/0
ip address 10.1.1.3 255.255.255.0
duplex auto
speed auto
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.1.1.1
! Default Route
no ip http server
!
voice-port 1/0/0
!
voice-port 1/0/1
!
voice-port 1/1/0
!
voice-port 1/1/1
!
dial-peer voice 100 pots
application MGCPAPP
port 1/0/0
!
dial-peer voice 101 pots
application MGCPAPP
port 1/0/1
!
dial-peer voice 102 pots
application MGCPAPP
port 1/1/0
!
dial-peer voice 103 pots
application MGCPAPP
port 1/1/1
!
end
6.0 Configuring the Intuity
Configuring the INTUITYTM
The following define the steps required on the INTUITYTM
HINT: When changes to the Switch Interface Administration are completed, a message appears on the screen indicating to restart the INTUITYTM voice system. However, this task is not required after each step. Once ALL changes are completed the system must then be restarted.
Step 1:
Ensure that the Country is properly chosen and Switch is configured as 5ESS. If not then contact your local TSO to have the proper Country, and Switch selected. Systems at Release 5.0 and higher only have the option to view the switch selection page.
Step 2
Serial Interface (port) Configuration Select “Switch Interface Administration” Select “Call Data Interface Administration” Select “Switch Link Administration”. Select “Serial Interface”.
Assign parameter values that match the Cisco CallManager integration serial port:
Data bits: 7 Stop bits: 1 Start bits: 1 Baud rate: 9600 Parity: E Flow control: N
Select the serial port by pressing “Choices” button. Serial ports /dev/tty00 and /dev/tty01 are reserved for INTUITY system use. Select /dev/ttysaa. Press F3 to save the administered values.