|
|
Because the DPA 7630 depends on information from the Cisco CallManager and the Octel systems, you must verify that they are set up properly before configuring the DPA 7630, and you must obtain some information from these systems to set up the DPA 7630.
This guide does not contain details about configuring the Cisco CallManager and Octel systems. Refer to the documentation provided with these 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 as another IP telephony device. So, to add the device to the database, you need some information from the DPA 7630. Additionally, to set up the DPA 7630, you need information from both the Cisco CallManager and Octel systems. Refer to Table 3-1 for an overview of the tasks and information you need from them to configure the DPA 7630.
| Task | For More Information | |
|---|---|---|
| Cisco CallManager Configuration | ||
q | Add the DPA 7630 to the Cisco CallManager database manually or using auto-registration. | |
q | Configure the ports from the DPA 7630 as Cisco IP Phones in the Cisco CallManager database. | |
q | Verify that the options for enabling and disabling MWI on the Cisco IP Phones are configured in Cisco CallManager. | |
q | Verify that the voice mail hunt group is set up properly. | |
| Octel Configuration | ||
q | Set dialing sequence for message waiting indicator. | See the "Setting Dialing Sequence for Message Waiting Indicator" section. |
q | Assign lines to handle incoming calls, outgoing calls, and MWI commands. | See the "Assigning Incoming, Outgoing, and MWI Lines" section. |
The DPA 7630 connects to Cisco CallManager to provide the following capabilities:
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 and Cisco CallManager connect, the ports on the DPA 7630 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 to handle MWI commands to Cisco CallManager.
You can choose to have the DPA 7630 automatically added to Cisco CallManager using auto-registration. If you want to use auto-registration, you must verify that it is enabled in Cisco CallManager. Refer to the Cisco CallManager Administration Guide or online help in the Cisco CallManager application for details.
Cisco CallManager only recognizes these IP phones after the Octel voice mail system is up and running. So, verify that the Octel system and the Cisco DPA 7630 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 is entered in the Description field in the record for the emulated phone in Cisco CallManager. If you do not enter a host name, the following sequence applies for the device description: SEP + the last 10 digits of the MAC address.
1. The first two digits for the MAC address are dropped.
2. The number is shifted two places to the left.
3. The two-digit port number is added to the right.
For example, if the MAC address is000039A44218
the MAC address registered for port 12 in CallManager is0039A4421812
The 25th virtual port is automatically assigned the MAC address of 0039A4421825.
If you want to assign specific directory numbers to the emulated IP phones on the DPA 7630 without using auto-registration, you must manually add each phone to the Cisco CallManager database. Keep in mind several important facts:
From the perspective of the DPA 7630, 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 properly 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.
Outgoing Calls
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.
Incoming Calls
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 Figure 3-1 for an example of the following settings:
The DPA 7630 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 Figure 3-2 for an example of the following settings:
The DPA 7630 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 Figure 3-2 for an example of the following settings:
Although the DPA 7630 does not directly interact with the end-user phones, verify that you configured these phones properly to roll to voice mail. Ensure that you set the forwarding options (Forward Busy and Forward No Answer settings) to the voice mail access number for their assigned hunt group. You might want to divide users into different hunt groups to access the voice mail system. See Figure 3-3 for an example of an end-user phone configuration.
On Cisco CallManager, you must set the option to enable the message waiting light on Cisco IP Phones. Once configured, you can access the values used to enable and disable the message waiting light by following these procedures. These options appear under the Service > Service Parameters menu in Cisco CallManager. You must configure these settings for each Cisco CallManager system in a cluster.
In these examples, the MessageWaitingOffDN value is 1998, and the MessageWaitingOnDN value is 1999. Record these values. You need them to configure the DPA 7630.
You must configure several settings in Cisco CallManager to ensure that the voice mail hunt groups function properly. These options appear under the Service > Service Parameters menu in Cisco CallManager: You must configure these settings for each Cisco CallManager system in a cluster.
The pilot directory number is the number users dial on their Cisco IP Phones to access voice mail. Typically, it is the first directory number in the hunt group. You can configure this number to be easily accessed on Cisco IP Phones, such as with the messages button on a Cisco IP Phone 7960.
To configure the pilot directory number perform the following steps:
Step 2 Click the name of your Cisco CallManager system.
Step 3 Select the VoiceMailDn service parameter.
Step 4 Enter the pilot directory number in the Value field.
Refer to the Cisco CallManager Administration Guide or online help in the Cisco CallManager application if you need additional assistance.
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.
To configure the hop count perform the following steps:
Step 2 Click the name of your Cisco CallManager system.
Step 3 Select the ForwardMaximumHopCount service parameter.
Step 4 Enter the pilot directory number in the Value field.
Refer to the Cisco CallManager Administration Guide or online help in the Cisco CallManager application if you need additional assistance.
You can specify the number of seconds allowed before generating a "no-answer" error. This setting determines how much time is spent contacting a directory number before forwarding to voice mail
The Octel systems have similar settings, which are determined by the number of rings. 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 approximately five seconds (the ring duration on an Octel system) times the number of rings. For example, if you have the Octel system set to four rings, set the setting in Cisco CallManager to at least 20 seconds.
To configure the number of seconds before a no-answer timeout occurs perform the following steps:
Step 2 Click the name of your Cisco CallManager system.
Step 3 Select the ForwardNoAnswerTimeout service parameter.
Step 4 Enter the number of seconds in the Value field.
Refer to the Cisco CallManager Administration Guide or online help in the Cisco CallManager application if you need additional assistance.
You should not need to make any changes to the Octel system. However, you should verify your configuration and obtain information from the Octel system to properly set up the DPA 7630. This information should already be configured if you previously used Octel and Lucent systems together.
On Lucent and Octel systems, you must set the dialing sequence that is used to enable and disable the MWI on phones connected to the Lucent system. After you configure this setting on the Lucent and Octel systems, record the setting. You need it when you configure the DPA 7630.
On the Octel system, you must specify how each line is used, following these guidelines:
However, you have 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 the hybrid integration mode might use the following configuration:
Posted: Thu Dec 14 09:28:22 PST 2000
Copyright 1989-2000©Cisco Systems Inc.
