|
|
Because the DPA 7630/7610 depends on information from the Cisco CallManager system and the Octel voice messaging system, you must verify that these systems are set up properly before configuring the DPA 7630/7610. You must also obtain some information from these systems to set up the DPA 7630/7610.
This guide does not contain details about configuring the Cisco CallManager and Octel systems. Refer to the documentation provided with those systems for installation and configuration instructions.
These sections provide details about the configuration requirements on the Cisco CallManager and Octel systems:
Cisco CallManager recognizes the DPA 7630/7610 as another IP telephony device. So, to add the device to the database, you need some information from the DPA 7630/7610. Additionally, to set up the DPA 7630/7610, you need information from both the Cisco CallManager and Octel systems. Refer to Table 4-1 for an overview of the tasks and information you need from them to configure the DPA 7630/7610.
| Task | For More Information | |
|---|---|---|
| Cisco CallManager Configuration | ||
See "Adding the DPA 7630/7610 to Cisco CallManager" section. |
||
Configure the ports from the DPA 7630/7610 as Cisco IP Phones in Cisco CallManager. |
||
Verify that the options for enabling and disabling MWI on the Cisco IP Phones are configured in Cisco CallManager. |
||
| Octel Configuration | ||
See the "Setting Dialing Sequence for Message Waiting Indicator" section. |
||
Assign lines to handle incoming calls, outgoing calls, and MWI commands. |
See the "Assigning Incoming, Outgoing, and MWI Lines" section. |
|
The DPA requires minor changes to Cisco CallManager because when you add the DPA 7630/7610 to the IP network, Cisco CallManager recognizes the ports as Cisco IP Phones. Therefore, you need to add these ports to the Cisco CallManager database. Additionally, because of the close interaction of the DPA 7630/7610 with the voice mail system, you must ensure that some key voice mail settings on the Cisco CallManager system are properly configured.
The DPA 7630/7610 connects to Cisco CallManager to provide the following capabilities:
The DPA 7630/7610 provides connection to the Octel voice messaging system by emulating IP phones. These emulated phones appear in the Cisco CallManager database.
Some ports on the DPA 7630/7610 handle MWI commands from the Octel system. An additional "virtual" IP phone sends these messages to the Cisco CallManager system. Cisco CallManager then sets the MWI on the Cisco IP Phones.
When reviewing the following tasks, if you need additional instructions, refer to the Cisco CallManager Administration Guide or the online help in the Cisco CallManager application:
When the DPA 7630/7610 and Cisco CallManager connect, the ports on the DPA 7630/7610 appear as IP phones in the Cisco CallManager database. An additional "virtual" port also appears as an IP phone to Cisco CallManager, but it does not have any correspondence to a physical port. It is created by the DPA 7630/7610 to handle MWI commands to Cisco CallManager.
You can choose to have the DPA 7630/7610 automatically added to Cisco CallManager using auto-registration. To do this, you must verify that auto-registration is enabled in Cisco CallManager. Refer to the documentation or online help included with the Cisco CallManager application for details.
When the DPA 7630/7610 connects to Cisco CallManager through auto-registration, the ports connected between the DPA 7630/7610 and the Octel system are registered as Cisco IP Phones. These ports are actually emulated IP phones used to access the voice mail system and to process MWI commands.
Cisco CallManager only recognizes these IP phones after the Octel voice mail system is up and running. Therefore, verify that the Octel system and the Cisco DPA 7630/7610 systems are up before completing these tasks in Cisco CallManager.
Auto-registration automatically assigns phones a directory number. The directory number assigned is the next one available in sequential order within the device pool assigned to this phone type in Cisco CallManager. However, if you need to, you can modify this directory number for each emulated phone (see the "Configuring the DPA Ports and Phones" section).
During auto registration, the host name assigned to the DPA 7630/7610 is used to populate the MAC address field in the record for the emulated phone in Cisco CallManager. The default host name is: SEP + the last 10 digits of the MAC address of the DPA 7630/7610. Typically, you should not change the default host name, but to do so, see the "Setting the Host Name" section
Cisco CallManager requires unique MAC addresses for all devices, but all 24 ports on the DPA 7630/7610 share the same MAC address. Therefore, auto-registration includes a process that converts the host name into unique MAC addresses for each port:
1. The SEP portion of the host name is removed.
2. The two-digit port number is appended to the right.
The virtual port is assigned 25 as its port number.
If you want to assign specific directory numbers to the emulated IP phones on the DPA 7630/7610 without using auto-registration, you must manually add each phone to the Cisco CallManager database. Keep in mind several important facts:
You must configure several settings in Cisco CallManager to ensure that the voice mail hunt group is set up properly for the DPA 7630/7610. You must configure these settings for each Cisco CallManager system in a cluster, and you must stop and restart Cisco CallManager after making these changes.
Refer to the instructions specific to the version of Cisco CallManager that you are using with the DPA 7630/7610.
Follow these steps to set up the voice mail hunt group on Cisco CallManager 3.1:
Step 2 From the Server drop-down list box, choose a server.
Step 3 From the Services list, choose Cisco CallManager.
Step 4 Enter the settings described in Table 4-2.
Step 5 Click Update.
| Field | Description |
|---|---|
You can specify the number of times Cisco CallManager forwards a call before generating an error tone. The default setting is 12, but you should set it to a number larger than the number of extensions in the largest hunt group. |
|
The no-answer timeout setting determines how much time is spent contacting a directory number before forwarding to voice mail. You can specify the number of seconds allowed before the system determines that a call to an extension forwarded to the voice mail system. When performing supervised transfers, the Octel system expects a certain number of rings before the call forwards to voice mail. If the call forwards to voice mail prematurely, the Octel system assumes the phone was busy. To ensure that the Cisco CallManager system allows enough time for the number of expected rings on the Octel system, you must set the no-answer timeout. In Cisco CallManager, you should set this setting to be 6 seconds times the number of rings. (Six seconds is slightly longer than the ring duration of a Lucent Definity PBX system.) For example, if you have the Octel system set to four rings, set the setting in Cisco CallManager to 24 seconds. |
|
Set this flag to True, if you want Cisco CallManager to use translation patterns to convert voice message box numbers into directory numbers when your voice mail system issues a command to set a message waiting indicator. |
|
Enter the number used to access their voice mail messages. This number should correspond to the directory number of the first voice mail port (see the "Configuring Call Ports" section) and the pilot directory number entered on the DPA 7630/7610 (see the "Entering Cisco CallManager Pilot Directory Number" section) You can have multiple voice mail hunt groups, but these hunt groups require different voice mail access numbers. For efficiency, enter the directory number of the largest hunt group as the VoiceMail parameter and ensure that the AdvancedCallForwardHopFlag parameter is set to true. |
|
Set this value to be at least as high as the total number of ports in use across all DPA devices. |
On Cisco CallManager 3.2, you must configure some service parameters, but you must also configure the voice mail port and voice mail profile. These sections provide an overview of these steps:
Follow these steps to configure the voice mail service parameters on Cisco CallManager 3.2:
Step 2 From the Server drop-down list box, choose a server.
Step 3 From the Services list, choose Cisco CallManager.
Step 4 Enter the settings described in Table 4-3.
Step 5 Click Update.
You need to create the voice mail pilot number, which is the number users enter to access their voice mail messages. This number should correspond to the directory number of the first voice mail port (see the "Configuring Call Ports" section) and the pilot directory number entered on the DPA 7630/7610 (see "Entering Cisco CallManager Pilot Directory Number" section).
Follow these steps to create the voice mail pilot port:
Step 2 Enter the number of the first port on the DPA 7630/7610 in the Voice Mail Pilot Number field.
 |
Note This number should correspond to the directory number of the first voice mail port (see the "Configuring Call Ports" section) and the pilot directory number entered on the DPA 7630/7610 (see "Entering Cisco CallManager Pilot Directory Number" section) |
Step 3 Enter any other optional fields.
Step 4 Click Insert.
The voice mail profile enables you to assign a user a different mail box number than their extension number. So, if users have an extension that is a different number than their voicemail box on the Octel system, they can still access their voice mail using the pilot directory number.
Step 2 Click Add a New Voice Mail Profile.
Step 3 Enter the minimum information:
Step 4 Click Insert.
From the perspective of the DPA 7630/7610, several types of ports exist:
To Cisco CallManager, these ports on the DPA appear as IP phones, but the PBX MWI ports do not appear in Cisco CallManager. The Cisco CallManager database also contains records of all the end-user phones. You must configure each of these phones in Cisco CallManager to ensure that calls are processed properly. You access the phones using the Devices > Phone menu in Cisco CallManager.
These sections provide details about the required settings in Cisco CallManager for the different ports:
Use call ports to connect lines from the Octel system that handle incoming messages, such as voice mail access, and outgoing calls such as fax calls, outgoing calls to pagers, and so on. However, a particular line from the Octel system must support either incoming or outgoing calls; it cannot support both.
Do not include the call ports supporting outgoing calls in the voice mail hunt groups. Otherwise, configure these lines in Cisco CallManager as you normally would, assigning directory numbers to them.
The call ports supporting incoming calls require additional configuration in Cisco CallManager. In these cases, these lines and their corresponding call ports compose the voice mail hunt groups. See Table 4-4 for an overview of the required settings for both Cisco CallManager 3.1 and 3.2.
The DPA 7630/7610 uses the Octel MWI ports to handle MWI messages from the Octel system. You can also enable these lines to support outgoing call processing. However, you must not configure these ports to handle any incoming call processing. See Table 4-5 for an overview of the required settings for both Cisco CallManager 3.1 and 3.2.
The DPA 7630/7610 automatically creates and uses the virtual port to send MWI messages to Cisco CallManager. One virtual port is created regardless of the number of Octel MWI ports you have. The virtual phone settings are similar to the Octel MWI port. See Table 4-6 for an overview of the required settings for both Cisco CallManager 3.1 and 3.2.
Although the DPA 7630/7610 does not directly interact with the end-user phones, verify that you configured these phones properly to forward to voice mail. You might want to divide users into different hunt groups to access the voice mail system. See Table 4-7 for an overview of the required settings for either Cisco CallManager 3.1 or 3.2.
| Field | Description |
|---|---|
| Cisco CallManager 3.1 | |
| Cisco CallManager 3.2 | |
In Cisco CallManager, you must set the option to enable the message waiting light on Cisco IP Phones. After you configure these settings, you must record the values and enter them on the DPA 7630/7610 (see the "Entering MWI for Cisco CallManager" section).
Refer to the section appropriate for the version of Cisco CallManager that you are using in your network:
You must configure these settings for each Cisco CallManager system in a cluster, and you must stop and restart Cisco CallManager after making these changes.
Step 2 From the Server drop-down list box, choose a server.
Step 3 From the Services list, choose Cisco CallManager.
Step 4 Enter these settings:
Step 5 Click Update.
Step 6 Record these values and use them to update the DPA 7630/7610. See the "Entering MWI for Cisco CallManager" section).
Follow these steps to configure Message Waiting Indicators for Cisco CallManager 3.2:
Step 2 To enable MWI, enter the following fields:
Step 3 Click Insert
Step 4 To disable MWI, enter the following fields:
Step 5 Record these values and use them to update the DPA 7630/7610. See the "Entering MWI for Cisco CallManager" section).
You should not need to make any changes to your Octel system. However, you should verify your configuration and obtain information from the Octel system to properly set up the DPA 7630/7610. This information should already be configured if you previously used Octel and Definity or Meridian 1 systems together.
On Definity and Octel systems, you must set the dialing sequence that is used to enable and disable the MWI on phones connected to the Definity system. After you configure this setting on the Definity and Octel systems, record the setting. You need it when you configure the DPA 7630. Meridian 1 PBX systems set MWI differently so you do not need to set this for the DPA 7610.
The Octel system has two methods of receiving incoming calls on a Meridian 1 system, using Hunt or Automatic Call Distribution (ACD). The Hunt method involves groups of forwarded phones, which is similar to the method used in Cisco CallManager. However, the Meridian 1 system has a restriction on the number of hops in a forwarding chain (similar to the ForwardMaxHopCount setting in Cisco CallManager). This setting is fixed between 18 and 30 hops (depending on the PBX version), and you cannot modify it. This restriction limits both the number of phones available to the hunt group and the number of Octel ports that can be part of the group.
To avoid this restriction, you can use ACD groups, which can be much larger than the hunt groups.
Regardless of the method you use, you must verify the method in use so you can set the proper setting on the DPA 7610. To quickly verify this method, on the Meridian 1 system, check the configuration of key 0 on the phones connected to the Octel system:
On the Octel system, you must specify how each line is used, following these guidelines:
You can assign a single line to process outgoing calls and MWI commands. However, you must not have a single line supporting both incoming call processing and MWI commands.
You have some flexibility in determining the number of lines used for each of these tasks. For example, a company with a 144-port Octel voice mail system using a DPA 7630 in hybrid integration mode might use the following configuration:
Posted: Sun Jan 19 12:37:27 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.