Table Of Contents
Teltronics 20-20 LX DTMF Integration Guide for Cisco Unity 5.0
Integration Tasks
Task List to Create the Integration
Requirements
Integration Description
Call Information
Integration Functionality
Integrations with Multiple Phone Systems
Planning How the Voice Messaging Ports Will Be Used by Cisco Unity
Programming the Teltronics 20-20 LX Phone System
Creating a New Integration with the Teltronics 20-20 LX Phone System
Testing the Integration
Integrating a Secondary Server for Cisco Unity Failover
Requirements
Integration Description
Setting Up the Secondary Server for Failover
Appendix: Documentation and Technical Assistance
Conventions
Obtaining Documentation, Obtaining Support, and Security Guidelines
Teltronics 20-20 LX DTMF Integration Guide for Cisco Unity 5.0
Revised November 26, 2007
This document provides instructions for integrating the Teltronics 20-20 LX phone system (formerly the Harris 20-20 LX) with Cisco Unity.
Integration Tasks
Before doing the following tasks to integrate Cisco Unity with the Teltronics 20-20 LX phone system, confirm that the Cisco Unity server is ready for the integration by completing the applicable tasks in the applicable Cisco Unity installation guide.
The following task list describes the process for creating the integration.
Task List to Create the Integration
Use the following task list to set up a new integration with the Teltronics 20-20 LX phone system. If you are installing a new Cisco Unity server by using the applicable Cisco Unity installation guide, you may have already completed some of the following tasks.
1. 
Review the system and equipment requirements to confirm that all phone system and Cisco Unity server requirements have been met. See the "Requirements" section.
2. Plan how the voice messaging ports will be used by Cisco Unity. See the "Planning How the Voice Messaging Ports Will Be Used by Cisco Unity" section.
3. Program the Teltronics 20-20 LX phone system and extensions. See the "Programming the Teltronics 20-20 LX Phone System" section.
4. Create the integration. See the "Creating a New Integration with the Teltronics 20-20 LX Phone System" section.
5. Test the integration. See the "Testing the Integration" section.
6. If you have a secondary server for Cisco Unity failover, integrate the secondary server. See the "Integrating a Secondary Server for Cisco Unity Failover" section.
Requirements
The Teltronics 20-20 LX integration supports configurations of the following components:
Phone System
•Teltronics 20-20 LX.
•Software version 3.2.3.0072c or later.
•The voice messaging ports in the phone system connected to the voice cards in the Cisco Unity server.
•The phone system ready for the integration, as described in the documentation for the phone system.
Cisco Unity Server
•The applicable voice cards, installed. For details, refer to the "Supported Circuit-Switched Phone System Integrations" section in the applicable Supported Hardware and Software, and Support Policies at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
•Cisco Unity installed and ready for the integration, as described in the applicable Cisco Unity installation guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
•A license that enables the appropriate number of voice messaging ports.
Integration Description
The Teltronics 20-20 LX phone system communicates with the Cisco Unity server by using DTMF sequences. The voice messaging lines from the phone system connect to the analog voice cards in the Cisco Unity server. Figure 1 shows the required connections for analog connections.
Figure 1 Connections Between the Phone System and Cisco Unity
Call Information
The phone system sends the following information with forwarded calls:
•The extension of the called party
•The extension of the calling party (for internal calls)
Cisco Unity uses this information to answer the call appropriately. For example, a call forwarded to Cisco Unity is answered with the personal greeting of the subscriber. If the phone system routes the call to Cisco Unity without this information, Cisco Unity answers with the Opening Greeting.
Integration Functionality
The Teltronics 20-20 LX integration with Cisco Unity provides the following features:
•Call forward to personal greeting
•Caller ID
•Easy message access (a subscriber can retrieve messages without entering an ID because Cisco Unity identifies the subscriber based on the extension from which the call originated; a password may be required)
•Identified subscriber messaging (Cisco Unity identifies the subscriber who leaves a message during a forwarded internal call, based on the extension from which the call originated)
•Message waiting indication (MWI)
Integrations with Multiple Phone Systems
Cisco Unity can be integrated with multiple phone systems at one time. For information on the maximum supported combinations and instructions for integrating Cisco Unity with multiple phone systems, refer to the applicable Multiple Phone System Integration Guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.
Planning How the Voice Messaging Ports Will Be Used by Cisco Unity
Before programming the phone system, you need to plan how the voice messaging ports will be used by Cisco Unity. The following considerations will affect the programming for the phone system (for example, setting up the hunt group or call forwarding for the voice messaging ports):
•The number of voice messaging ports installed.
•The number of voice messaging ports that will answer calls.
•The number of voice messaging ports that will only dial out, for example, to send message notification, to set message waiting indicators (MWIs), to make AMIS deliveries, and to make telephone record and playback (TRAP) connections.
The following table describes the voice messaging port settings in Cisco Unity that can be set in UTIM, and that are displayed as read-only text on the System > Ports page of the Cisco Unity Administrator.
Table 1 Settings for the Voice Messaging Ports
Field
|
Considerations
|
Extension
|
Enter the extension for the port as assigned on the phone system.
|
Enabled
|
Check this check box to enable the port. The port is enabled during normal operation.
Uncheck this check box to disable the port. When the port is disabled, calls to the port get a ringing tone but are not answered. Typically, the port is disabled only by the installer during testing.
|
Answer Calls
|
Check this check box to designate the port for answering calls. These calls can be incoming calls from unidentified callers or from subscribers.
|
Message Notification
|
Check this check box to designate the port for notifying subscribers of messages. Assign Message Notification to the least busy ports.
|
Dialout MWI
(not used by serial or SMDI integrations)
|
Check this check box to designate the port for turning MWIs on and off. Assign Dialout MWI to the least busy ports.
|
AMIS Delivery
(available with the AMIS licensed feature only)
|
Check this check box to designate the port for making outbound AMIS calls to deliver voice messages from Cisco Unity subscribers to users on another voice messaging system. Cisco Unity supports the Audio Messaging Interchange Specification (AMIS) protocol, which provides an analog mechanism for transferring voice messages between different voice messaging systems.
This setting affects outbound AMIS calls only. All ports are used for incoming AMIS calls.
Because the transmission of outgoing AMIS messages may tie up voice ports for long periods of time, you may want to adjust the schedule on the Network > AMIS > Schedule page so that outgoing AMIS calls are placed during closed hours or at times when Cisco Unity is not processing many calls.
|
TRAP Connection
|
Check this check box so that subscribers can use the phone as a recording and playback device in Cisco Unity web applications and e-mail clients. Assign TRAP Connection to the least busy ports.
|
The Number of Voice Messaging Ports to Install
The number of voice messaging ports to install depends on numerous factors, including:
•The number of calls Cisco Unity will answer when call traffic is at its peak.
•The expected length of each message that callers will record and that subscribers will listen to.
•The number of subscribers.
•The number of ports that will be set to dial out only.
•The number of calls made for message notification.
•The number of MWIs that will be activated when call traffic is at its peak.
•The number of AMIS delivery calls.
•The number of TRAP connections needed when call traffic is at its peak. (TRAP connections are used by Cisco Unity web applications to play back and record over the phone.)
•The number of calls that will use the automated attendant and call handlers when call traffic is at its peak.
It is best to install only the number of voice messaging ports that are needed so that system resources are not allocated to unused ports.
The Number of Voice Messaging Ports That Will Answer Calls
The calls that the voice messaging ports answer can be incoming calls from unidentified callers or from subscribers. Typically, the voice messaging ports that answer calls are the busiest.
You can set voice messaging ports to both answer calls and to dial out (for example, to send message notifications). However, when the voice messaging ports perform more than one function and are very active (for example, answering many calls), the other functions may be delayed until the voice messaging port is free (for example, message notifications cannot be sent until there are fewer calls to answer). For best performance, dedicate certain voice messaging ports for only answering incoming calls, and dedicate other ports for only dialing out. Separating these port functions eliminates the possibility of a collision, in which an incoming call arrives on a port at the same time that Cisco Unity takes the port off-hook to dial out.
The Number of Voice Messaging Ports That Will Only Dial Out, and Not Answer Calls
Ports that will only dial out and will not answer calls can do one or more of the following:
•Notify subscribers by phone, pager, or e-mail of messages that have arrived.
•Turn MWIs on and off for subscriber extensions.
•Make outbound AMIS calls to deliver voice messages from Cisco Unity subscribers to users on another voice messaging system. (This action is available only with the AMIS licensed feature.)
•Make a TRAP connection so that subscribers can use the phone as a recording and playback device in Cisco Unity web applications.
Typically, these voice messaging ports are the least busy ports.
Caution In programming the phone system, do not send calls to voice messaging ports in Cisco Unity that cannot answer calls (voice messaging ports that are not set to Answer Calls). For example, if a voice messaging port is set only to Dialout MWI, do not send calls to it.
Preparing for Programming the Phone System
Record your decisions about the voice messaging ports to guide you in programming the phone system.
Programming the Teltronics 20-20 LX Phone System
If you use programming options other than those supplied in the following procedures, the performance of the integration may be affected.
Caution In programming the phone system, do not send calls to voice messaging ports in Cisco Unity that cannot answer calls (voice messaging ports that are not set to Answer Calls). For example, if a voice messaging port is set only to Dialout MWI, do not send calls to it.
Do the following procedures in the order given.
To Program the Collect and Route for Setting MWIs
Step 1 Log on to the phone system maintenance terminal.
Step 2 At the system prompt, enter EDT and press Enter.
Step 3 Select the applicable active database by entering either A or B.
Step 4 At the database prompt, enter COLLECT and press Enter. The Collect & Route prompt appears.
Note Adding or modifying Collect & Route settings requires restarting the phone system. If you are using redundant common control, the phone system will switch over to the standby shelf.
Step 5 Enter ADD <name of the group of Collect & Route settings> and press Enter.
For example, enter "ADD CR-UNITY" and press Enter.
Step 6 Enter *1 /REM 1,2 = VMS-NO-MSGS and press Enter to set the code for turning off MWIs.
Step 7 Enter #1 /REM 1,2 = VMS-MSGS and press Enter to set the code for turning on MWIs.
Step 8 Enter XXXX = STA and press Enter to enable dialing stations.
Step 9 Enter a comment to conclude the Collect & Route settings and press Enter.
For example, enter "VOICEMAIL DIALING" and press Enter.
To Program the Classes of Service
Step 1 Enter ROU and press Enter. The Routing Class prompt appears.
Step 2 Enter LIST and press Enter to display a list of the existing routing classes.
Step 3 Enter ADD <the routing class that you are adding to the class of service> and press Enter.
For example, enter "ADD 2" and press Enter.
Step 4 Enter the name for the class of service and press Enter.
For example, enter "UNRESTRICTED FOR LONG DISTANCE" and press Enter.
Step 5 Repeat Step 3 and Step 4 for each additional routing class that you want to create.
Step 6 Enter DIA and press Enter. The Dial Control Class prompt appears.
Step 7 To create the facility dial control class of service, do the following substeps:
a. Accept the default Dial Control Class setting and press Enter.
b. Select a type of dial for the Dial Control Class setting and press Enter.
c. Select a destination for the Collect & Route settings (which you created in Step 4 through Step 9 of the "To Program the Collect and Route for Setting MWIs" procedure), and press Enter.
For example, select "CR-UNITY" and press Enter.
d. Press Enter to accept the default values for Tone settings.
e. In the Comment field, enter a label for the facility dial control class of service and press Enter.
For example, enter "UNITY FACILITY" and press Enter.
Step 8 To create the trunk group dial control class of service, do the following substeps:
a. Enter LIST 1-63 /FREE and press Enter to display a list of unused numbers that can be used as a trunk group pilot number.
b. Enter ADD <the trunk group pilot number> and press Enter.
For example, enter "ADD 15" and press Enter.
c. Select a type of dial for the Dial Control Class setting and press Enter.
d. Select a destination for the Collect & Route settings (which you created in Step 4 through Step 9 of the "To Program the Collect and Route for Setting MWIs" procedure), and press Enter.
For example, select "CR-UNITY" and press Enter.
e. Press Enter to accept the default values for Tone settings.
f. In the Comment field, enter a label for the trunk group dial control class of service and press Enter.
For example, enter "UNITY TRUNK GROUP" and press Enter.
Step 9 Enter FEA and press Enter. The Feature Class prompt appear.
Step 10 Enter LIST 1-63 /FREE and press Enter to display a list of unused feature class numbers.
Step 11 To create a feature class for the facility dial control class of service, do the following substeps:
a. Enter ADD <an unused feature class number> and press Enter.
For example, enter "ADD 28" and press Enter.
b. In the Type field, enter FAC and press Enter.
c. For the remaining fields, do the applicable action:
•To accept the defaults, press Enter.
•To apply other values, enter the values you want and press Enter.
Step 12 To create a feature class for the trunk group dial control class of service, do the following substeps:
a. Enter ADD <an unused feature class number> and press Enter.
For example, enter "ADD 25" and press Enter.
b. In the Type field, enter VMS-Line and press Enter.
c. For the remaining fields, do the applicable action:
•To accept the defaults, press Enter.
•To apply other values, enter the values you want and press Enter.
Step 13 Enter COS and press Enter. The Class of Service prompt appears.
Step 14 Enter LIST 1-255 /FREE and press Enter to display a list of unused class of service numbers.
Step 15 To create a class of service for the facility, do the following substeps:
a. Enter ADD <an unused class of service number> and press Enter.
For example, enter "ADD 35" and press Enter.
b. In the Dial Control Class field, enter 1 and press Enter.
c. In the Feature Class field, enter the feature class that you created in Step 11 and press Enter.
For example, enter "28" and press Enter.
d. In the Routing Class field, enter the routing class that you created in Step 3 and press Enter.
For example, enter "2" and press Enter.
e. In the Bearer Capability Class field, press Enter to accept the default value of 0.
f. In the Reliable Disconnect field, press Enter to accept the default value of Y.
g. Enter a label for the class of service for the facility and press Enter.
Step 16 To create a class of service for the trunk group, do the following substeps:
a. Enter ADD <an unused class of service number> and press Enter.
For example, enter "ADD 20" and press Enter.
b. In the Dial Control Class field, enter the dial control class that you created in Step 8 and press Enter.
For example, enter "15" and press Enter.
c. In the Feature Class field, enter the feature class (for the trunk group dial control class of service) that you created in Step 12 and press Enter.
For example, enter "25" and press Enter.
d. In the Routing Class field, enter the routing class that you created in Step 3 and press Enter.
For example, enter "2" and press Enter.
e. In the Bearer Capability Class field, press Enter to accept the default value of 0.
f. In the Reliable Disconnect field, press Enter to accept the default value of Y.
g. Enter a label for the class of service for the trunk group and press Enter.
To Program the Trunk Group
Step 1 Enter TRUNK and press Enter. The Trunk Group prompt appears.
Step 2 Enter LIST 1-45 /FREE and press Enter to display a list of unused trunk group numbers.
Step 3 Enter ADD <the trunk group number that you are adding> and press Enter.
For example, enter "ADD 44" and press Enter.
Step 4 In the Trunk Group Type field, enter LINE and press Enter.
Step 5 In the DSP Trunk Group field, press Enter to accept the default value of N.
Step 6 In the Incoming Class of Service field, enter the class of service that you created in Step 16 of the "To Program the Classes of Service" procedure and press Enter.
For example, enter "20" and press Enter.
Step 7 In the Trunk ID Digits field, press Enter to accept the default value of NONE.
Step 8 In the Outgoing Calls Allowed field, press Enter to accept the default value of YES.
Step 9 In the Search Type field, press Enter to accept the default value of HF (homing forward).
Step 10 In the Number of Circuits field, enter the number of circuits (or ports) that will connect with Cisco Unity and press Enter.
Step 11 In the Circuit Locations field, enter the location of the first circuit and press Enter.
Step 12 Repeat Step 11 for all remaining circuits.
Step 13 When END appears after the locations of all circuits have been entered, press Enter.
Step 14 In the AW Display Name field, enter Unity and press Enter.
Step 15 In the Teleset Display Name field, enter VMS and press Enter.
Note This field is limited to a maximum of four letters.
Step 16 In the Comment field, enter an applicable comment and press Enter.
For example, enter "UNITY VOICE MAIL SERVER" and press Enter.
Note Adding trunk groups requires restarting the phone system to save the changes. If you are using redundant common control, the phone system will switch over to the standby shelf.
To Program the Facilities
Step 1 Enter FAC and press Enter. The Facility prompt appears.
Step 2 Enter LIST 1-625 /FREE and press Enter to display a list of unused facility numbers.
Step 3 To create the facility that is used when calls are sent to the Opening Greeting, do the following substeps:
a. Enter ADD <the facility number that you are adding> and press Enter.
For example, enter "ADD 86" and press Enter.
b. In the Enable DSP Control field, press Enter to accept the default value of N.
c. In the Trunk Group field, enter the trunk group you created in Step 3 of the "To Program the Trunk Group" procedure and press Enter.
For example, enter "44" and press Enter.
d. In the Class of Service field, enter the class of service you created in Step 15 of the "To Program the Classes of Service" procedure and press Enter.
For example, enter "35" and press Enter.
e. In the Outpulse Command field, enter PANSWER 1 and press Enter.
f. Press Enter to leave the remaining Outpulse Command values empty.
Note This facility will send calls to the Opening Greeting, so no digit sequences are necessary.
g. In the Comment field, enter an applicable comment and press Enter.
Step 4 To create the facility that is used when calls are forwarded to a subscriber personal greeting, do the following substeps:
a. Enter ADD <the unused facility number that you are adding> and press Enter.
For example, enter "ADD 184" and press Enter.
b. In the Enable DSP Control field, press Enter to accept the default value of N.
c. In the Trunk Group field, enter the trunk group you created in Step 3 of the "To Program the Trunk Group" procedure and press Enter.
For example, enter "44" and press Enter.
d. In the Class of Service field, enter the class of service you created in Step 15 of the "To Program the Classes of Service" procedure and press Enter.
For example, enter "35" and press Enter.
e. In the Outpulse Command field, enter PAUSE .5 and press Enter.
f. Enter SDIGITS 4 and press Enter.
g. Enter SEND # and press Enter.
h. Enter SANI 4 and press Enter.
i. Enter SEND # and press Enter.
j. Enter SAUTH 10 and press Enter.
k. Enter Send # and press Enter.
l. Enter PANSWER 10 and press Enter.
m. Press Enter to leave the remaining Outpulse Command values empty.
n. In the Comment field, enter an applicable comment and press Enter.
Step 5 To create the facility that is used when subscribers retrieve messages from their phone, do the following substeps:
a. Enter ADD <the unused facility number that you are adding> and press Enter.
For example, enter "ADD 10" and press Enter.
b. In the Enable DSP Control field, press Enter to accept the default value of N.
c. In the Trunk Group field, enter the trunk group you created in Step 3 of the "To Program the Trunk Group" procedure and press Enter.
For example, enter "44" and press Enter.
d. In the Class of Service field, enter the class of service you created in Step 15 of the "To Program the Classes of Service" procedure and press Enter.
For example, enter "35" and press Enter.
e. Enter SEND * and press Enter.
f. Enter SANI 4 and press Enter.
g. Enter PANSWER 5 and press Enter.
h. Press Enter to leave the remaining Outpulse Command values empty.
i. In the Comment field, enter an applicable comment and press Enter.
To Program the Route Patterns
Step 1 Determine unused extension numbers for the following purposes:
•Accessing the Opening Greeting
•Destination for forwarded calls
These extension numbers will be used for the route patterns that are added in the following steps.
Step 2 Enter PAT and press Enter. The Route Pattern prompt appears.
Step 3 Enter ADD RP-VMS-UNITY and press Enter.
Step 4 Enter AUTO-ANS and press Enter.
Step 5 Enter a route pattern that will access the Opening Greeting, and press Enter.
For example, enter "5433" and press Enter.
Step 6 In the Name field, enter UNITY and press Enter.
Step 7 Press Enter.
Step 8 Press Enter.
Step 9 Enter a name for the office location and press Enter.
For example, enter "BASM" and press Enter.
Note This field is limited to a maximum of four letters.
Step 10 Enter a name for the department and press Enter.
For example, enter "TCOM" and press Enter.
Note This field is limited to a maximum of four letters.
Step 11 Do one of the following, as applicable:
•If you publish extension numbers, enter Y and press Enter.
•If you do not publish extension numbers, enter N and press Enter.
Step 12 Enter ROUTE and press Enter.
Step 13 Enter ALL and press Enter.
Step 14 Press Enter.
Step 15 Enter ALL and press Enter.
Step 16 Press Enter.
Step 17 Enter ALL and press Enter.
Step 18 Press Enter.
Step 19 Enter the facility that you created in Step 3 of the "To Program the Facilities" procedure and press Enter.
For example, enter "86" and press Enter.
Step 20 Enter ALL and press Enter.
Step 21 Press Enter.
Step 22 Press Enter.
Step 23 Enter Y and press Enter.
Step 24 Enter QUEUE and press Enter.
Step 25 Enter ALL and press Enter.
Step 26 Press Enter.
Step 27 Enter ALL and press Enter.
Step 28 Press Enter.
Step 29 Enter ALL and press Enter.
Step 30 Press Enter.
Step 31 Enter BOTH and press Enter.
Step 32 Enter the number of seconds that calls are queued when all circuits are busy, and press Enter.
For example, enter "30" and press Enter.
Step 33 Enter END and press Enter.
Step 34 In the Comment field, enter an applicable comment and press Enter.
For example, enter "ROUTE PATTERN ACCESSING OPENING GREETING" and press Enter.
Step 35 Enter ADD and press Enter.
Step 36 Enter RP-UNITY-FORWARD and press Enter.
Step 37 Enter AUTO-ANS and press Enter.
Step 38 Enter a route pattern that will be used for calls that are forwarded to Cisco Unity, and press Enter.
For example, enter "5572" and press Enter.
Step 39 In the Name field, enter UNITY and press Enter.
Step 40 Press Enter.
Step 41 Press Enter.
Step 42 Enter a name for the office location and press Enter.
For example, enter "BASM" and press Enter.
Note This field is limited to a maximum of four letters.
Step 43 Enter a name for the department and press Enter.
For example, enter "TCOM" and press Enter.
Note This field is limited to a maximum of four letters.
Step 44 Do one of the following, as applicable:
•If you publish extension numbers, enter Y and press Enter.
•If you do not publish extension numbers, enter N and press Enter.
Step 45 Enter ROUTE and press Enter.
Step 46 Enter ALL and press Enter.
Step 47 Press Enter.
Step 48 Enter ALL and press Enter.
Step 49 Press Enter.
Step 50 Enter ALL and press Enter.
Step 51 Press Enter.
Step 52 Enter the facility that you created in Step 4 of the "To Program the Facilities" procedure and press Enter.
For example, enter "184" and press Enter.
Step 53 Enter ALL and press Enter.
Step 54 Press Enter.
Step 55 Press Enter.
Step 56 Enter Y and press Enter.
Step 57 Enter QUEUE and press Enter.
Step 58 Enter ALL and press Enter.
Step 59 Press Enter.
Step 60 Enter ALL and press Enter.
Step 61 Press Enter.
Step 62 Enter ALL and press Enter.
Step 63 Press Enter.
Step 64 Enter BOTH and press Enter.
Step 65 Enter the number of seconds that calls are queued when all circuits are busy, and press Enter.
For example, enter "30" and press Enter.
Step 66 Enter END and press Enter.
Step 67 In the Comment field, enter an applicable comment and press Enter.
For example, enter "ROUTE PATTERN FOR CALLS FORWARDED TO UNITY" and press Enter.
Step 68 Enter ADD RP-VMS and press Enter.
Step 69 Enter GENERAL and press Enter.
Step 70 Enter ROUTE and press Enter.
Step 71 Enter ALL and press Enter.
Step 72 Press Enter.
Step 73 Enter ALL and press Enter.
Step 74 Press Enter.
Step 75 Enter ALL and press Enter.
Step 76 Press Enter.
Step 77 Enter the facility that you created in Step 5 of the "To Program the Facilities" procedure and press Enter.
For example, enter "10" and press Enter.
Step 78 Enter ALL and press Enter.
Step 79 Press Enter.
Step 80 Press Enter.
Step 81 Enter Y and press Enter.
Step 82 Enter QUEUE and press Enter.
Step 83 Enter ALL and press Enter.
Step 84 Press Enter.
Step 85 Enter ALL and press Enter.
Step 86 Press Enter.
Step 87 Enter ALL and press Enter.
Step 88 Press Enter.
Step 89 Enter BOTH and press Enter.
Step 90 Enter the number of seconds that calls are queued when all circuits are busy, and press Enter.
For example, enter "30" and press Enter.
Step 91 Enter END and press Enter.
Step 92 Press Enter.
Step 93 In the Comment field, enter an applicable comment and press Enter.
For example, enter "ROUTE PATTERN FOR CALLS FORWARDED TO UNITY" and press Enter.
Step 94 Program each subscriber phone to forward calls to the pilot number that is assigned to the voice messaging ports, based on one of the Cisco Unity call transfer types shown in Table 2.
Table 2 Call Transfer Types
Transfer Type
|
Usage
|
Release transfer
(blind transfer)
|
Program the phone to forward calls to the pilot number when:
•The extension is busy
•The call is not answered
|
Supervised transfer
|
Program the phone to forward calls to the pilot number only when the call is not answered. Confirm that call forwarding is disabled when the extension is busy.
|
Creating a New Integration with the Teltronics 20-20 LX Phone System
After ensuring that the Teltronics 20-20 LX phone system and the Cisco Unity server are ready for the integration, do the following procedures to set up the integration and to enter the port settings.
To Create an Integration
Step 1 If UTIM is not already open, on the Windows Start menu of the Cisco Unity server, click Programs > Cisco Unity > Manage Integrations. UTIM appears.
Step 2 In the left pane of the UTIM window, click Cisco Unity Server.
Step 3 On the Integration menu of the UTIM window, click New. The Telephony Integration Setup Wizard appears.
Step 4 On the Welcome page, click Circuit-Switched via Voice Card and click Next.
Step 5 On the Name the Phone System Integration page, accept the default name or enter another name to identify this integration, then click Next.
Step 6 On the Select Integration Method page, click Analog, then click Next.
Step 7 On the Select Phone System Manufacturer page, click the following settings, then click Next.
Table 3 Settings for the Select Phone System Manufacturer Page
Field
|
Setting
|
Manufacturer
|
Harris
|
Model
|
20/20
|
Software Version
|
7
|
Configuration File
|
<if you have made copies of the .ini configuration file, the name of the configuration file that you want to use>
|
Step 8 On the Enter MWI Codes page, enter the following settings, then click Next.
Table 4 Settings for the Enter MWI Codes Page
Field
|
Setting
|
MWI On Code
|
<the code you specified in the phone system for turning MWIs on>
|
MWI Off Code
|
<the code you specified in the phone system for turning MWIs off>
|
Step 9 On the Set Number of Voice Messaging Ports page, enter the number of voice messaging ports on Cisco Unity that you want to connect to the phone system, then click Next.
This number cannot be more than the number of ports on the installed voice cards or the number of ports set up on the phone system.
Step 10 If other integrations already exist, the Enter Trunk Access Code page appears. Enter the extra digits that Cisco Unity must use to transfer calls through the gateway to extensions on the other phone systems with which it is integrated. Then click Next.
Step 11 On the Reassign Subscribers page, any subscribers whose phone system integration has been deleted and who are not currently assigned to a phone system integration will appear in the list.
If no subscribers appear in the list, click Next and continue to Step 12.
Otherwise, select the subscribers that you want to assign to this phone system integration and click Next. You can use the following selection controls for selecting subscribers.
Table 5 Selection Controls for the Reassign Subscribers Page
Selection Control
|
Effect
|
Check All
|
Checks the check boxes for all subscribers in the list.
|
Uncheck All
|
Unchecks the check boxes for all subscribers in the list.
|
Toggle Selected
|
For the subscribers highlighted in the list, toggles between checking and unchecking the check boxes.
If some highlighted subscriber check boxes are checked and others are unchecked, clicking this button will check all the check boxes. Clicking again will uncheck all the check boxes.
|
Step 12 On the Reassign Call Handlers page, any call handlers whose phone system integration has been deleted and that are not currently assigned to a phone system integration will appear in the list.
If no call handlers appear in the list, click Next and continue to Step 13.
Otherwise, select the call handlers that you want to assign to this phone system integration and click Next. You can use the following selection controls for selecting call handlers.
Table 6 Selection Controls for the Reassign Call Handlers Page
Selection Control
|
Effect
|
Check All
|
Checks the check boxes for all call handlers in the list.
|
Uncheck All
|
Unchecks the check boxes for all call handlers in the list.
|
Toggle Selected
|
For the call handlers highlighted in the list, toggles between checking and unchecking the check boxes.
If some highlighted call handler check boxes are checked and others are unchecked, clicking this button will check all the check boxes. Clicking again will uncheck all the check boxes.
|
Step 13 On the Completing page, verify the settings you entered, then click Finish.
Step 14 At the prompt to restart the Cisco Unity services, click Yes. The Cisco Unity services restart.
Alternatively, you can restart the Cisco Unity services in UTIM on the Tools menu by clicking Restart Cisco Unity.
To Enter the Voice Messaging Port Settings for the Integration
Step 1 After the Cisco Unity services restart, on the View menu, click Refresh.
Step 2 In the left pane of the UTIM window, expand the phone system integration that you are creating.
Step 3 In the left pane, click the name of the phone system.
Step 4 In the right pane, click the Ports tab.
Step 5 Enter the settings shown in Table 7 for the voice messaging ports.
For best performance, use the first voice messaging ports for incoming calls and the last ports to dial out. This helps minimize the possibility of a collision, in which an incoming call arrives on a port at the same time that Cisco Unity takes the port off-hook to dial out.
Caution In programming the phone system, do not send calls to voice messaging ports in Cisco Unity that cannot answer calls (voice messaging ports that are not set to Answer Calls). For example, if a voice messaging port is set only to Message Notification, do not send calls to it.
Table 7 Settings for the Voice Messaging Ports
Field
|
Considerations
|
Extension
|
Enter the extension for the port as assigned on the phone system.
|
Enabled
|
Check this check box to enable the port. The port is enabled during normal operation.
Uncheck this check box to disable the port. When the port is disabled, calls to the port get a ringing tone but are not answered. Typically, the port is disabled only by the installer during testing.
|
Answer Calls
|
Check this check box to designate the port for answering calls. These calls can be incoming calls from unidentified callers or from subscribers.
|
Message Notification
|
Check this check box to designate the port for notifying subscribers of messages. Assign Message Notification to the least busy ports.
|
Dialout MWI
(not used by serial or SMDI integrations)
|
Check this check box to designate the port for turning MWIs on and off. Assign Dialout MWI to the least busy ports.
|
AMIS Delivery
(available with the AMIS licensed feature only)
|
Check this check box to designate the port for making outbound AMIS calls to deliver voice messages from Cisco Unity subscribers to users on another voice messaging system. Cisco Unity supports the Audio Messaging Interchange Specification (AMIS) protocol, which provides an analog mechanism for transferring voice messages between different voice messaging systems.
This setting affects outbound AMIS calls only. All ports are used for incoming AMIS calls.
Because the transmission of outgoing AMIS messages may tie up voice ports for long periods of time, you may want to adjust the schedule on the Network > AMIS > Schedule page so that outgoing AMIS calls are placed during closed hours or at times when Cisco Unity is not processing many calls.
|
TRAP Connection
|
Check this check box so that subscribers can use the phone as a recording and playback device in Cisco Unity web applications and e-mail clients. Assign TRAP Connection to the least busy ports.
|
Step 6 Click Save.
Step 7 Exit UTIM.
Testing the Integration
To test whether Cisco Unity and the phone system are integrated correctly, do the following procedures in the order listed.
If any of the steps indicate a failure, refer to the following documentation as applicable:
•The installation guide for the phone system.
•Cisco Unity Troubleshooting Guide, available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_troubleshooting_guides_list.html.
•The setup information earlier in this guide.
To Set Up the Test Configuration
Step 1 Set up two test extensions (Phone 1 and Phone 2) on the same phone system that Cisco Unity is connected to.
Step 2 Set Phone 1 to forward calls to the Cisco Unity pilot number when calls are not answered.
Caution The phone system must forward calls to the Cisco Unity pilot number in no fewer than four rings. Otherwise, the test may fail.
Step 3 In the Cisco Unity Administrator, create a test subscriber to use for testing by doing the applicable substeps below.
If your message store is Microsoft Exchange, do the following:
a. In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Profile page.
b. Click the Add icon.
c. In the New subscriber field, click Exchange.
d. On the Add Subscriber page, enter the applicable information.
e. Click Add.
If your message store is IBM Lotus Domino, do the following:
a. In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Profile page.
b. Click the Add icon.
c. In the New Subscriber field, click Notes.
d. In the Address Book list, confirm that the address book listed is the one that contains the user data that you want to import.
If the address book that you want to use is not listed, go to the System > Configuration > Subscriber Address Books page and add a different address book.
e. In the Find Domino Person By list, indicate whether to search by short name, first name, or last name.
f. Enter the applicable short name or name. You also can enter * to display a list of all users, or enter one or more characters followed by * to narrow your search.
g. Click Find.
h. On the list of matches, click the name of the user to import.
i. On the Add Subscriber page, enter the applicable information.
j. Click Add.
Step 4 In the Extension field, enter the extension of Phone 1.
Step 5 In the Active Schedule field, click All Hours - All Days.
Step 6 Click the Save icon.
Step 7 In the navigation bar, click Call Transfer to go to the Subscribers > Subscribers > Call Transfer page for the test subscriber.
For more information on transfer settings, refer to the "Subscriber Template Call Transfer Settings" section in the Cisco Unity Administrator Help.
Step 8 In the Transfer Rule Applies To field, click Standard.
Step 9 Under Transfer Incoming Calls, click Yes, Ring Subscriber's Extension, and confirm that the extension number is for Phone 1.
Step 10 Under Transfer Type, click Release to Switch.
Step 11 Click the Save icon.
Step 12 In the navigation bar, click Messages to go to the Subscribers > Subscribers > Messages page for the test subscriber.
Step 13 Under Message Waiting Indicators (MWIs), check Use MWI for Message Notification.
Step 14 In the Extension field, enter x.
Step 15 Click the Save icon.
Step 16 Open the Status Monitor by doing one of the following:
•In Internet Explorer, go to http://<Cisco Unity server name>/web/sm.
•Double-click the desktop shortcut to the Status Monitor.
•In the status bar next to the clock, right-click the Cisco Unity tray icon and click Status Monitor.
To Test an External Call with Release Transfer
Step 1 From Phone 2, enter the access code necessary to get an outside line, then enter the number outside callers use to dial directly to Cisco Unity.
Step 2 On the Status Monitor, note which port handles this call.
Step 3 When you hear the opening greeting, enter the extension for Phone 1. Hearing the opening greeting means that the port is configured correctly.
Step 4 Confirm that Phone 1 rings and that you hear a ringback tone on Phone 2. Hearing a ringback tone means that Cisco Unity correctly released the call and transferred it to Phone 1.
Step 5 Leaving Phone 1 unanswered, confirm that the state of the port handling the call changes to "Idle." This state means that release transfer is successful.
Step 6 Confirm that, after the number of rings that the phone system is set to wait, the call is forwarded to Cisco Unity and that you hear the greeting for the test subscriber. Hearing the greeting means that the phone system forwarded the unanswered call and the call-forward information to Cisco Unity, which correctly interpreted the information.
Step 7 On the Status Monitor, note which port handles this call.
Step 8 Leave a message for the test subscriber and hang up Phone 2.
Step 9 On the Status Monitor, confirm that the state of the port handling the call changes to "Idle." This state means that the port was successfully released when the call ended.
Step 10 Confirm that the MWI on Phone 1 is activated. The activated MWI means that the phone system and Cisco Unity are successfully integrated for turning on MWIs.
To Test Listening to Messages
Step 1 From Phone 1, enter the internal pilot number for Cisco Unity.
Step 2 When asked for your password, enter the default password. Hearing the request for your password means that the phone system sent the necessary call information to Cisco Unity, which correctly interpreted the information.
Step 3 Confirm that you hear the recorded voice name for the test subscriber (if you did not record a voice name for the test subscriber, you will hear the extension number for Phone 1). Hearing the voice name means that Cisco Unity correctly identified the subscriber by the extension.
Step 4 When asked whether you want to listen to your message, press 1.
Step 5 After listening to the message, press 3 to delete the message.
Step 6 Confirm that the MWI on Phone 1 is deactivated. The deactivated MWI means that the phone system and Cisco Unity are successfully integrated for turning off MWIs.
Step 7 Hang up Phone 1.
Step 8 On the Status Monitor, confirm that the state of the port handling the call changes to "Idle." This state means that the port was successfully released when the call ended.
To Set Up Supervised Transfer on Cisco Unity
Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Call Transfer page.
If the name of the test subscriber is not displayed, click the Find icon (the magnifying glass) in the title bar, then click Find, and select the name of the test subscriber in the list that appears.
For more information on transfer settings, refer to the "Subscriber Template Call Transfer Settings" section in the Cisco Unity Administrator Help.
Step 2 Under Transfer Type, click Supervise Transfer.
Step 3 Set the Rings to Wait For field to 3.
Step 4 Click the Save icon.
To Test Supervised Transfer
Step 1 From Phone 2, enter the access code necessary to get an outside line, then enter the number outside callers use to dial directly to Cisco Unity.
Step 2 On the Status Monitor, note which port handles this call.
Step 3 When you hear the opening greeting, enter the extension for Phone 1. Hearing the opening greeting means that the port is configured correctly.
Step 4 Confirm that Phone 1 rings and that you do not hear a ringback tone on Phone 2. Instead, you should hear the indication your phone system uses to mean that the call is on hold (for example, music or beeps).
Step 5 Leaving Phone 1 unanswered, confirm that the state of the port handling the call remains "Busy." This state and hearing an indication that you are on hold mean that Cisco Unity is supervising the transfer.
Step 6 Confirm that, after three rings, you hear the greeting for the test subscriber. Hearing the greeting means that Cisco Unity successfully recalled the supervised-transfer call.
Step 7 During the greeting, hang up Phone 2.
Step 8 On the Status Monitor, confirm that the state of the port handling the call changes to "Idle." This state means that the port was successfully released when the call ended.
To Delete the Test Subscriber
Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Profile page.
If the name of the test subscriber is not displayed, click the Find icon (the magnifying glass) in the title bar, then click Find, and select the name of the test subscriber in the list that appears.
Step 2 In the title bar, click the Delete Subscriber icon (the X).
Step 3 Click Delete.
Step 4 When prompted to confirm deleting the subscriber, click OK.
Integrating a Secondary Server for Cisco Unity Failover
The Cisco Unity failover feature enables a secondary server to provide voice messaging services when the primary server becomes inactive. For information on installing a secondary server for failover, refer to the applicable Cisco Unity installation guide, available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
For information on failover, refer to the applicable Cisco Unity Failover Configuration and Administration Guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.
Requirements
The following components are required to integrate a secondary server:
•One secondary server for each primary server installed and ready for the integration, as described in the applicable Cisco Unity installation guide and earlier in this integration guide.
•The applicable cable configuration for each analog voice messaging port to simultaneously connect the phone system to the corresponding ports on both the primary and the secondary servers. For example, connect port 1 on the phone system with both port 1 on the primary server and port 1 on the secondary server.
•A license that enables failover.
Integration Description
The phone system communicates with both the primary and secondary servers through the connecting cables. Figure 2 shows the required connections.
Figure 2 Connections Between the Phone System and Cisco Unity Servers
The primary and secondary servers act in the following manner:
•When the primary server is operating normally, the secondary server is inactive.
•When the primary server becomes inactive, the secondary server becomes active.
•When the primary server becomes active again, the secondary server becomes inactive.
Setting Up the Secondary Server for Failover
Do the following procedure to integrate the secondary server.
To Set Up the Secondary Server for Failover
Step 1 Install a secondary server with the same configuration as the primary server. For installation instructions, refer to the applicable Cisco Unity installation guide.
Step 2 Make all voice connections from the phone system to the corresponding ports on both the primary server and the secondary server. For example, connect port 1 from the phone system with port 1 on both the primary and the secondary servers.
Step 3 On the Windows Start menu of the secondary server, click Programs > Cisco Unity > Manage Integrations. The UTIM window appears.
Step 4 On the Integration menu of the UTIM window, click New. The Telephony Integration Setup Wizard appears.
Step 5 Enter the settings to match the integration settings on the primary server.
Note We recommend not reassigning any unassigned subscribers and call handlers to the new integration, if you are asked by the wizard. Failover replication will automatically assign the correct integration.
Step 6 At the prompt to restart the Cisco Unity services, click Yes.
Note When restarting the Cisco Unity services, use the UTIM prompt instead of the Cisco Unity icon in the Windows taskbar. The taskbar icon does not restart all of the Cisco Unity services.
Step 7 After Cisco Unity restarts, on the Windows Start menu of the Cisco Unity server, click Programs > Cisco Unity > Manage Integrations. UTIM appears.
Step 8 In the left pane of the UTIM window, click the phone system integration that you created in Step 4.
Step 9 In the right pane, click Properties.
Step 10 On the Integration tab, compare the setting of the Integration ID field for the secondary server to the setting of the Integration ID field for the primary server.
Step 11 If the integration IDs of the phone system on the primary and secondary server are the same, continue to Step 17.
If the integration IDs of the phone system on the primary and secondary servers are different, on the secondary server, click Modify Integration ID.
Step 12 When cautioned that subscribers associated with the current Integration ID setting will not be automatically associated with the new Integration ID setting, click OK.
Step 13 In the Modify Integration ID dialog box, in the Enter New Integration ID field, enter the Integration ID setting for the phone system on the primary server and click OK.
Step 14 Click Save.
Step 15 At the prompt to restart the Cisco Unity services, click No.
Step 16 In the left pane, click the phone system integration that you created in Step 4.
Step 17 In the right pane, click the Ports tab.
Step 18 Enter the port settings to match the port settings on the primary server.
Caution In programming the phone system, do not send calls to voice messaging ports in Cisco Unity that cannot answer calls (voice messaging ports that are not set to Answer Calls). For example, if a voice messaging port is set only to Dialout MWI, do not send calls to it.
Step 19 Click Save.
Step 20 Exit UTIM.
Step 21 On the Windows Start menu of the server, click Programs > Cisco Unity > Edit Switch Utility.
Step 22 In the Switch Configuration Editor window, in the Manufacturer field, click Harris.
Step 23 In the Model field, click 20/20.
Step 24 Click Edit.
Step 25 In the Switch Configuration dialog box, click the Incoming Calls tab.
Step 26 In the Call Rings field, enter 3 and click OK.
Step 27 In the Switch Configuration Editor dialog box, click Exit.
Step 28 On the Windows Start menu, click Run.
Step 29 Enter Regedit and click OK.
Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) If you have any questions about changing registry key settings, contact Cisco TAC.
Step 30 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.
Step 31 Expand the key HKEY_LOCAL_MACHINE\Software\Active Voice\Miu\1.0\Initialization.
Step 32 Double-click New Call Delay on Inactive Backup Server.
Step 33 In the Edit DWORD Value dialog box, in the Value Data field, enter 0, and click OK.
Step 34 Close the Registry Editor.
Step 35 Restart the Cisco Unity server.
No changes to the hunt group programming on the phone system are necessary.
Appendix: Documentation and Technical Assistance
Conventions
The Teltronics 20-20 LX DTMF Integration Guide for Cisco Unity 5.0 uses the following conventions.
Table 8 Teltronics 20-20 LX DTMF Integration Guide for Cisco Unity 5.0 Conventions
Convention
|
Description
|
boldfaced text
|
Boldfaced text is used for:
•Key and button names. (Example: Click OK.)
•Information that you enter. (Example: Enter Administrator in the User Name box.)
|
< >
(angle brackets)
|
Angle brackets are used around parameters for which you supply a value. (Example: In the Command Prompt window, enter ping <IP address>.)
|
-
(hyphen)
|
Hyphens separate keys that must be pressed simultaneously. (Example: Press Ctrl-Alt-Delete.)
|
>
(right angle
bracket)
|
A right angle bracket is used to separate selections that you make:
•On menus. (Example: On the Windows Start menu, click Settings > Control Panel > Phone and Modem Options.)
•In the navigation bar of the Cisco Unity Administrator. (Example: Go to the System > Configuration > Settings page.)
|
[x]
(square brackets)
|
Square brackets enclose an optional element (keyword or argument). (Example: [reg-e164])
|
[x | y]
(vertical line)
|
Square brackets enclosing keywords or arguments separated by a vertical line indicate an optional choice. (Example: [transport tcp | transport udp])
|
{x | y}
(braces)
|
Braces enclosing keywords or arguments separated by a vertical line indicate a required choice. (Example: {tcp | udp})
|
The Teltronics 20-20 LX DTMF Integration Guide for Cisco Unity 5.0 also uses the following conventions:
Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the document.
Caution Means
reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.
For descriptions and URLs of Cisco Unity documentation on Cisco.com, see the About Cisco Unity Documentation. The document is shipped with Cisco Unity and is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_documentation_roadmaps_list.html.
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
