Table Of Contents
Mitel SX-200 ONS DTMF Integration
Integration Overview
Integration Steps
Requirements
Integration Description
Integration Features
Programming the Phone System
Configuring Cisco Unity for the Integration
Testing the Integration
Integrating a Cisco Unity Failover (Secondary) Server
Requirements
Integration Description
Setting Up a Failover (Secondary) Server
Mitel SX-200 ONS DTMF Integration
Integration Overview
Before performing the following integration steps, confirm that the Cisco Unity server is ready for the integration by completing the appropriate tasks in the Cisco Unity Installation Guide.
Integration Steps
Follow these steps to set up this integration.
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. Program the phone system and extensions. See the "Programming the Phone System" section.
3. Configure Cisco Unity for the integration. See the "Configuring Cisco Unity for the Integration" section.
4. Test the integration. See the "Testing the Integration" section.
5. If you have a Cisco Unity failover (secondary) server, integrate the secondary server. See the "Integrating a Cisco Unity Failover (Secondary) Server" section.
Requirements
The Mitel SX-200 integration supports configurations of the following components:
Phone System
•Mitel SX-200
•Software level Lightware 18 release 2.0 or later
•The ONS ports (on premise line 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 installation guide for the phone system
Cisco Unity Server
•The Dialogic D/41EPCI, D/120JCT-LS, or D/120JCT-Euro voice cards, installed
•Cisco Unity installed and ready for the integration as described in the Cisco Unity Installation Guide
•A system key that enables the integration and the appropriate number of voice messaging ports
Integration Description
The Mitel SX-200 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-1 shows the required connections.
Figure 1-1 Connections Between the Phone System and Cisco Unity
There are two levels of integration based on the Switch PBX Software Version setting (see Table 1-3), basic ("Lightware 18") and enhanced ("Lightware 18 w/Enhanced InBand").
For the basic integration, the phone system sends the following information with the forwarded calls:
•The extension of the called party
For the enhanced integration, the phone system sends the following information with the forwarded calls:
•The extension of the called party
•The reason for the forward (the extension is busy, does not answer, or is set to forward all calls)
•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 Features
The Mitel SX-200 integration with Cisco Unity provides the following features:
Call forward to personal greeting
|
When an incoming call is routed to an unanswered or busy extension, the call is forwarded to the voice mail of the subscriber. The caller then hears the personal greeting of the subscriber and can leave a message.
|
Caller ID
(enhanced integration only)
|
Cisco Unity receives caller ID information from the phone system (if available). This information appears in the subject line of the message in the desktop messaging application.
|
Easy message access
|
A subscriber can retrieve messages without entering an ID. Cisco Unity identifies a subscriber based on the extension from which the call originated. A password may be required.
|
Identified subscriber messaging
(enhanced integration only)
|
Cisco Unity automatically identifies a subscriber who leaves a message during a forwarded internal call, based on the extension from which the call originated.
|
Message waiting indication
|
When a message is waiting for a subscriber, Cisco Unity notifies the phone system to activate the message waiting indicator (MWI) on the subscriber's extension (a lamp or a stutter dial tone).
|
Programming the Phone System
If you use programming options other than those supplied in the following procedure, the performance of the integration may be affected.
To program the phone system
Step 1 Go to Form 01 - System Configuration, and program the ONS/CLASS line card.
Step 2 Go to Form 02 - Feature Access Codes and assign the feature access codes as indicated in Table 1-1.
Table 1-1 Feature Access Code Settings
Feature
|
Setting Explanation
|
Feature 24 - Abbreviated Dial Access
|
The access code for voice mail.
|
Feature 41 - Send Message
|
The access code for MWIs.
This code must match the beginning portion of the setting of the MWI On Code and MWI Off Code fields on the System > Switch page in the Cisco Unity Administrator.
|
Feature 3 - Call forwarding - All Calls
|
The access code forwarding all calls.
|
Feature 4 - Call forwarding - Internal Only
|
The access code forwarding internal calls only.
|
Feature 5 - Call forwarding - External Only
|
The access code forwarding external calls only.
|
Step 3 Go to Form 03 - COS Define, create a class of service for the ONS ports that will be used to answer calls, and enable the following class of service options:
•COS Option 208 - Call Forwarding - External
•COS Option 212 - Can Flash if Talking to an Incoming Trunk
•COS Option 213 - Can Flash if Talking to an Outgoing Trunk
•COS Option 216 - Data Security
•COS Option 238 - Override Security
•COS Option 261 - ONS Voice Mail Port
•COS Option 301 - Camp-On
Step 4 In Form 03 - COS Define, create a class of service for the ONS ports that will be used for MWIs, and enable the following class of service options:
•COS Option 216 - Data Security
•COS Option 220 - Do Not Disturb
•COS Option 235 - Originate Only
•COS Option 238 - Override Security
•COS Option 259 - Message Sending
Step 5 In the class of service for subscribers, enable one of the following:
•COS Option 231 - Message Waiting Setup - Bell
•COS Option 232 - Message Waiting Setup - Lamp
Step 6 In the class of service for subscribers, it is recommended that you disable the following:
•COS Option 220 - Do Not Disturb
Caution When a subscriber extension has the Do Not Disturb (DND) mode turned on, callers may be incorrectly identified in, for example, voice messages left for the subscriber.
Step 7 Go to Form 04 - System Options/System Timers, and enable the following:
•System Option 21 - Incoming to Outgoing Call Forwarding
•System Option 22 - Last Party Clear Dial Tone
Step 8 Go to Form 09 - Desktop Device Assignments, program the ONS ports that will be used to answer calls and assign them to the appropriate class of service.
Step 9 In Form 09 - Desktop Device Assignments, program the ONS ports that will be used for MWIs and assign them to the appropriate class of service.
Step 10 Go to Form 17 - Hunt Groups, and set up a hunt group for the ONS ports that will be used to answer calls.
Step 11 For the basic integration, skip to the "Testing the Integration" section. For the enhanced integration, continue to the next step.
Step 12 Go to Form 31 - System Abbreviated Dial Entry, and create an abbreviated dial index for voice mail access.
Step 13 In the Digit String field, enter the hunt group pilot number followed by *9*4#*6#*8#.
Step 14 Go to class of service for the ONS ports that will be used for MWIs, locate option 265 - Voice Mail System Speed Dial Index, and enter the abbreviated dial index created in Step 12.
Step 15 Go to Form 19 - Call Rerouting Table, and in the DND Intercept Routing option, enter the abbreviated dial index created in Step 12.
Step 16 Program each phone to forward calls to the abbreviated dial index assigned to the voice messaging ports, based on one of the following Cisco Unity call transfer types.
Table 1-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.
|
Configuring Cisco Unity for the Integration
After ensuring that the Cisco Unity server is ready for the integration by completing the appropriate tasks in the Cisco Unity Installation Guide, perform the following procedures to confirm that the integration is enabled and to enter the port settings.
To confirm that the integration is enabled
Step 1 On the Cisco Unity server, go to the Cisco Unity Administrator by doing one of the following:
•In Internet Explorer, go to http://<server name>/web/sa.
•Double-click the desktop shortcut to the Cisco Unity Administrator.
Step 2 Go to System > Licensing > Licensed Features.
Step 3 In the Integration field, confirm that the setting is Analog for a single phone system integration or Multiple Integrations for a dual phone system integration.
Step 4 If the setting is not Analog or Multiple Integrations, contact your sales representative for the necessary system key.
Step 5 Go to System > Switch. Confirm that the settings match those in the following table. If the settings are incorrect, integration features may not be enabled.
Table 1-3 Switch Settings
Switch Parameter
|
Required Setting
|
Manufacturer
|
Mitel
|
Model
|
SX-200 ELX
|
Switch PBX Software Version
|
•Lightware 18
•Lightware 18 w/Enhanced InBand
|
Integration
|
Analog
|
Step 6 If necessary, edit the codes that turn message waiting indication on and off. The MWI codes are located in the Active Switch Setting area at the top of the Switch Settings page.
Step 7 Click the Save icon.
To enter port settings
Step 1 In the Cisco Unity Administrator, go to System > Ports.
Step 2 Select a port in the table.
Step 3 Indicate the settings for the port. For ports that will be used to answer calls, leave unchecked the Message Waiting Indication check box. For ports that will be used for MWIs, leave unchecked the Answer Calls check box.
For a hunt group, 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.
Step 4 Type the extension for the port.
Step 5 Repeat Steps 2 through 4 for the remaining ports.
Step 6 Click the Save icon.
Step 7 For the settings to take effect, exit and restart the Cisco Unity software. For more information, see Appendix A, "Exiting and Starting the Cisco Unity Software and Server."
Testing the Integration
To test whether Cisco Unity and the phone system are integrated correctly, perform the procedures in the order listed.
If any of the steps indicates a failure, see the following documentation as appropriate:
•The installation guide for the phone system
•Cisco Unity Troubleshooting Guide
•This integration 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.
Step 3 In the Cisco Unity Administrator, go to Subscribers > Subscribers > Profile.
If Example Subscriber is not displayed, click the Find icon (the magnifying glass) in the title bar, then click Find, and select Example Subscriber in the list that appears.
Step 4 In the Extension field, enter the extension of Phone 1.
Step 5 Click the Save icon.
Step 6 In the navigation bar, click Call Transfer to go to Subscribers > Subscribers > Call Transfer for Example Subscriber.
For more information on transfer settings, refer to the "Subscriber Template Call Transfer Settings" section in the Help for the Cisco Unity Administrator.
Step 7 Under Transfer Incoming Calls, click Yes, Ring Subscriber's Extension, and confirm that the extension number is for Phone 1.
Step 8 Under Transfer Type, click Release to Switch.
Step 9 Click the Save icon.
Step 10 In the navigation bar, click Messages to go to Subscribers > Subscribers > Messages for Example Subscriber.
Step 11 Under Message Waiting Indicators (MWIs), check Use MWI for Message Notification.
Step 12 In the Extension field, enter x.
Step 13 Click the Save icon.
Step 14 Open the Status Monitor by doing one of the following:
•In Internet Explorer, go to http://<server name>/web/sm.
•Double-click the desktop shortcut to the Status Monitor.
•In the Windows systray, right-click the Cisco Unity 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 the port that 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 released the call and transferred it to Phone 1.
Step 5 Do not answer Phone 1, and confirm that the state of the port handling the call changes to "Idle." This state means that release transfer succeeds.
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 Example 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 the port that handles this call.
Step 8 Leave a message for Example 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 an internal call with release transfer
Step 1 From Phone 1, enter the internal pilot number for Cisco Unity.
Step 2 When asked for your password, enter 12345. 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 Example Subscriber. 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 messages, 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 Subscribers > Subscribers > Call Transfer.
If Example Subscriber is not displayed, click the Find icon (the magnifying glass) in the title bar, then click Find, and select Example Subscriber in the list that appears.
For more information on transfer settings, refer to the "Subscriber Template Call Transfer Settings" section in the Help for the Cisco Unity Administrator.
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 the port that 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 Do not answer Phone 1, and 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 Example 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 return Example Subscriber to the default settings
Step 1 In the Cisco Unity Administrator, go to Subscribers > Subscribers > Call Transfer.
If Example Subscriber is not displayed, click the Find icon (the magnifying glass) in the title bar, then click Find, and select Example Subscriber in the list that appears.
Step 2 Under Transfer Incoming Calls, click No (Send Directly to Subscriber's Greeting).
Step 3 In the navigation bar, click Profile to go to Subscribers > Subscribers > Profile.
Step 4 In the Extension field, enter 99990.
Step 5 Click the Save icon.
Step 6 In the navigation bar, click Messages to go to Subscribers > Subscribers > Messages for Example Subscriber.
Step 7 Under Message Waiting Indicators (MWIs), uncheck Use MWI for Message Notification.
Step 8 Click the Save icon.
Integrating a Cisco Unity Failover (Secondary) Server
A Cisco Unity failover server is a secondary (or backup) server that provides voice messaging services if the primary Cisco Unity server becomes inactive. For information on installing a secondary server, refer to the Cisco Unity Installation Guide.
Requirements
The following components are required to integrate a Cisco Unity secondary server:
•One secondary Cisco Unity server for each primary server installed and ready for the integration, as described in the Cisco Unity Installation Guide and earlier in this integration guide.
•The appropriate 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 system key that enables the integration, the appropriate number of voice messaging ports, and the secondary server.
Integration Description
The phone system communicates with both the primary and secondary servers through the connecting cables. Figure 1-2 shows the required connections.
Figure 1-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 a Failover (Secondary) Server
Do the following procedure to integrate a Cisco Unity secondary server.
To set up a failover (secondary) server
Step 1 Install a secondary server with the same configuration as the primary server. For installation instructions, refer to the 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 In the Cisco Unity Administrator of the secondary server, enter the settings on the System > Ports page to match the port settings on the primary server.
No changes to the hunt group programming on the phone system are necessary.
Feedback
