Table Of Contents
QSIG/DPNSS Phone System with Cisco EGW 2200 Integration Guide for Cisco Unity Release 8.x
Published February 2, 2010
This document provides instructions for integrating a QSIG/DPNSS phone system with Cisco Unity through a Cisco EGW 2200.
Before doing the following tasks to integrate Cisco Unity with a QSIG/DPNSS phone system through a Cisco EGW 2200, confirm that the Cisco Unity server is ready for the integration by completing the applicable tasks in the applicable Installation Guide for Cisco Unity.
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 a QSIG/DPNSS phone system. If you are installing a new Cisco Unity server by using the applicable Installation Guide for Cisco Unity, 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 QSIG/DPNSS phone system and extensions. See the "Programming the QSIG/DPNSS Phone System" section.
4. Set up the Cisco EGW 2200. See the "Setting Up the Cisco EGW 2200" section.
5. Create the integration. See the "Creating an Integration with the Phone System" section.
6. Test the integration. See the "Testing the Integration" section.
7. 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.
The QSIG/DPNSS integration supports configurations of the following components:
•A QSIG/DPNSS phone system.
•The phone system is ready for the integration as described in the documentation for the phone system and for the Cisco EGW 2200.
•A VoIP gateway configured and connected to the QSIG/DPNSS phone system.
Cisco Unity Server
•Cisco Unity installed and ready for the integration, as described in the applicable Installation Guide for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
•A license that enables the applicable number of voice messaging ports.
•A Cisco EGW 2200 ready for the integration as described in the documentation for the Cisco EGW 2200.
•The Cisco EGW 2200 connected to the LAN and configured for a QSIG/DPNSS backhaul signaling stream from the VoIP gateway.
The QSIG/DPNSS integration uses a Cisco EGW 2200 (which translates QSIG or DPNSS call signaling into SIP), a VoIP gateway, and the LAN to connect Cisco Unity and a QSIG/DPNSS phone system. Figure 1 shows the required connections.
Figure 1 Connections Between a QSIG/DPNSS Phone System and Cisco Unity
The QSIG/DPNSS integration sends the following information with forwarded calls:
•The extension of the called party
•The extension of the calling party (for internal calls) or the phone number of the calling party (if it is an external call and the system uses caller ID)
•The reason for the forward (the extension is busy, does not answer, or is set to forward all 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.
The QSIG/DPNSS integration with Cisco Unity provides the following integration features:
•Call forward to personal greeting
•Call forward to busy greeting
•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 Multiple Phone System Integration Guide for Cisco Unity 8.x at http://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 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 Cisco Unity Administrator.
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 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 Dial Out
Ports that will only dial out can do one or more of the following:
•Notify subscribers by phone, pager, or e-mail of messages that have arrived.
•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.
Preparing for Programming the Phone System
Record your decisions about the voice messaging ports to guide you in programming the phone system.
Programming the QSIG/DPNSS Phone System
For information on provisioning a QSIG or DPNSS phone system to integrate with Cisco Unity, see the documentation for the Cisco EGW 2200 at http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/pbx/interop/notes/427593av.pdf.
Setting Up the Cisco EGW 2200
For information on setting up the Cisco EGW 2200, see the documentation for the Cisco EGW 2200 at http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/pbx/interop/notes/427593av.pdf.
Creating an Integration with the Phone System
After ensuring that the QSIG/DPNSS 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 On the Integration menu of the UTIM window, click New. The Telephony Integration Setup Wizard appears.
Step 3 On the Welcome page, click SIP (including CUCM/CCM) and click Next.
Step 4 On the Name This SIP Integration and Cluster page, enter the following settings, then click Next.
Step 5 On the Enter Primary and Secondary SIP Server page, enter the following settings, then click Next.
You can click Ping Servers to confirm that the IP address is correct.
Step 6 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 Cisco EGW 2200 or the SIP proxy server, then click Next.
Step 7 On the Configure Cisco Unity SIP Settings page, enter the following settings, then click Next.
Step 8 On the Enter SIP Server Authentication page, enter the following settings, then click Next.
Step 9 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 10 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 11.
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.
Step 11 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 12.
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.
Step 12 On the Completing page, verify the settings you entered, then click Finish.
Step 13 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.
Step 14 At the prompt to wait before placing calls to Cisco Unity, click OK.
To Enter the Voice Messaging Port Settings for the Integration
Step 1 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 8 for the voice messaging 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.
•Troubleshooting Guide for Cisco Unity, 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 Cisco Unity Administrator, create a test subscriber to use for testing by doing the following substeps.
a. In 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.
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 Delete the Test Subscriber
Step 1 In 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 Installation Guide for Cisco Unity, available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
For information on failover, refer to the Failover Configuration and Administration Guide for Cisco Unity at http://cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.
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 Installation Guide for Cisco Unity and earlier in this integration guide.
•A license that enables failover.
The QSIG/DPNSS phone system communicates with both the primary and secondary servers through the LAN or WAN. Figure 2 shows the required connections.
Figure 2 Connections Between a QSIG/DPNSS Phone System and the 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 Installation Guide for Cisco Unity.
Step 2 On the Windows Start menu of the secondary server, click Programs > Cisco Unity > Manage Integrations. The UTIM window appears.
Step 3 On the Integration menu of the UTIM window, click New. The Telephony Integration Setup Wizard appears.
Step 4 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 5 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 6 After Cisco Unity restarts, on the Windows Start menu of the Cisco Unity server, click Programs > Cisco Unity > Manage Integrations. UTIM appears.
Step 7 In the left pane of the UTIM window, click the phone system integration that you created in Step 3.
Step 8 In the right pane, click Properties.
Step 9 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 10 If the integration IDs of the phone system on the primary and secondary server are the same, continue to Step 16.
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 11 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 12 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 13 Click Save.
Step 14 At the prompt to restart the Cisco Unity services, click Yes.
Step 15 In the left pane, click the phone system integration that you created in Step 3.
Step 16 In the right pane, click the Ports tab.
Step 17 Enter the port settings to match the port settings on the primary server.
Step 18 Click Save.
Step 19 Exit UTIM.
Appendix: Documentation and Technical Assistance
The QSIG/DPNSS Phone System with Cisco EGW 2200 Integration Guide for Cisco Unity Release 8.x uses the following conventions.
The QSIG/DPNSS Phone System with Cisco EGW 2200 Integration Guide for Cisco Unity Release 8.x 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.
Cisco Unity Documentation
For descriptions and URLs of Cisco Unity documentation on Cisco.com, see the Documentation Guide for Cisco Unity. 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 and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
Cisco Product Security Overview
This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately.
Further information regarding U.S. export regulations can be found at http://www.access.gpo.gov/bis/ear/ear_data.html.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
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.
© 2010 Cisco Systems, Inc. All rights reserved.