|
|
Because of its close interaction with Cisco CallManager, Octel, Definity, and Meridian 1 systems, the DPA 7630/7610 has several critical settings that you must properly configure. You typically do not need to make any changes on the other systems to add the DPA 7630/7610 to your network. However, you need information from these systems to configure these DPA 7630/7610 settings, and you should verify that they are set up properly. Be sure to review "Preparing the Cisco CallManager and Octel Systems" to ensure you have the information you need.
These sections provide details about the settings you need to configure on the DPA 7630/7610:
If you are using the DPA 7630, you must configure settings specific to the Definity PBX system. The DPA 7630 is designed to integrate into your network without requiring any changes to the current Definity and Octel settings. However, you must obtain information from these systems to enable the DPA 7630 to function properly.
You must choose the mode of integration by which you are implementing the DPA 7630:
Selecting the integration mode automatically forces the 24 ports on DPA 7630 to support particular settings. To understand these settings, review "Choosing an Integration Mode" before selecting an integration method.
To set the integration mode, perform these steps:
Step 1 From the main menu, choose Configure.
Step 2 Choose Octel/Definity integration.
Step 3 Choose Mode.
Step 4 Choose the appropriate configuration type:
Step 5 Restart the DPA 7630.
On Definity and Octel systems, you must set the dialing sequence used to enable and disable the MWI on phones connected to the Definity system. Verify and obtain the dialing sequences set on the Octel and Definity systems (see the "Setting Dialing Sequence for Message Waiting Indicator" section for details).
To enter the dialing sequences, perform these steps:
Step 1 From the main menu, choose Configure.
Step 2 Choose Octel/Definity integration.
Step 3 Choose the appropriate settings:
Step 4 Enter the appropriate values obtained from the Octel and Definity systems.
The dialing sequence can also optionally include a comma (,) to indicate a pause of 200 milliseconds (ms). These are additive, so a series of four commas (,,,,) is an 800 ms pause. Each pause causes the DPA 7630 to wait an additional 200 ms while receiving MWI commands from the Octel system, and it also creates a 200 ms delay while sending the command on to the PBX.
For example, if you enter #40,,,,, as the dialing sequence, the DPA 7630 waits an additional second for MWI commands. The DPA 7630 also inserts a 1 second pause when dialing the command to the PBX (after dialing #40 and before dialing the extension number).
Step 5 Restart the DPA 7630.
The disable policy is designed to prevent the Octel system from assuming a port is up when there is not an active Cisco CallManager or PBX connection. Changing this policy can prevent the Octel system from attempting outgoing calls or setting MWIs. This might be useful if you have configured your system for redundancy. For example, if the Octel MWI lines are distributed between two DPA 7630 systems and the first DPA 7630 loses its connection to Cisco CallManager, the ports connecting to the first DPA 7630 are disabled, and the Octel system only sends MWIs to the second DPA.
 |
Note The Cisco CallManager connection is considered lost if the DPA 7630 recognizes that it is down and has been down for 60 seconds. |
Step 1 From the main menu, choose Configure.
Step 2 Choose Octel/Definity integration.
Step 3 Choose Octel connection disable policy.
Step 4 Choose one of the following:
Step 5 Restart the DPA 7630.
You must configure the encoding algorithm, A-law or mu-law, used by the Definity and Octel systems. The settings on the DPA 7630 must match the settings on the Definity and Octel systems. Typically, North American systems use mu-law, and European systems use a-law.
To set the companding law, perform these steps:
Step 1 From the main menu, choose Configure.
Step 2 Choose Octel/Definity integration.
Step 3 Choose Companding law.
Step 4 Choose the appropriate option so that it corresponds to the setting on the Octel system:
Step 5 Restart the DPA 7630.
The Octel system sends all MWI messages to the Definity system through the DPA 7630. The same DPA 7630 port that sends a message to the Definity system to enable an MWI must also send the message to disable it. However, if the DPA 7630 is turned off or restarted after the Octel system has sent a MWI message, the message might be lost.
Although the setting on the Octel system is correct, if DPA 7630 was turned off before sending the message to the Definity system, some user phones might have MWI lights constantly enabled. If this happens, you need to clear the Definity MWI messages.
To clear Definity MWIs, perform these steps:
Step 1 From the main menu, choose Configure.
Step 2 Choose Octel/Definity integration.
Step 3 Choose Clear Definity MWIs.
Step 4 Enter the directory numbers or range of directory numbers to clear, using this format: 4419, 4420, 4440-4450.
If you are using the DPA 7610, you must configure settings specific to the Meridian 1 PBX system. The DPA 7610 is designed to integrate into your network without requiring any changes to the current Meridian 1 and Octel settings. However, you must obtain information from these systems to enable the DPA 7610 to function properly.
You must choose the mode of integration by which you are implementing the DPA 7610:
Selecting the integration mode automatically forces the 24 ports on DPA 7610 to support particular settings. To understand these settings, review "Choosing an Integration Mode" before selecting an integration method.
To set the integration mode, perform these steps:
Step 1 From the main menu, choose Configure.
Step 2 Choose Octel/Meridian 1 integration.
Step 3 Choose Mode.
Step 4 Choose the appropriate configuration type:
Step 5 Restart the DPA 7610.
You can configure the Octel system to handle incoming calls using hunt or ACD groups, and you must set the DPA 7610 to use the same mode. See "Determining Incoming Call Mode" section to verify the mode used.
To set the incoming call mode on the DPA 7610, perform these steps:
Step 1 From the main menu, choose Configure.
Step 2 Choose Octel incoming call mode.
Step 3 Choose the appropriate incoming call mode:
Step 4 Restart the DPA 7610.
The disable policy is designed to prevent the Octel system from assuming a port is up when there is not an active Cisco CallManager or PBX connection. Changing this policy can prevent the Octel system from attempting outgoing calls or setting MWIs. This might be useful if you have configured your system for redundancy. For example, if the Octel MWI lines are distributed between two DPA 7610 systems and the first DPA 7610 loses its connection to Cisco CallManager, the ports connecting to the first DPA 7610 are disabled, and the Octel system only sends MWIs to the second DPA.
|
Note The Cisco CallManager connection is considered lost if the DPA 7610 recognizes that it is down and has been down for 60 seconds. |
Step 1 From the main menu, choose Configure.
Step 2 Choose Octel/Meridian 1integration.
Step 3 Choose Octel connection disable policy.
Step 4 Choose one of the following:
Step 5 Restart the DPA 7630.
You must configure the encoding algorithm, A-law or mu-law, used by the Meridian 1 and Octel systems. The settings on the DPA 7610 must match the settings on the Meridian 1 and Octel systems. Typically, North American systems use mu-law, and European systems use a-law.
To set the companding law, perform these steps:
Step 1 From the main menu, choose Configure.
Step 2 Choose Octel/Meridian 1 integration.
Step 3 Choose Companding law.
Step 4 Choose the appropriate option corresponding to the setting on the Octel system.
Step 5 Restart the DPA 7610.
The Octel system sends all MWI messages to the Meridian 1 system through the DPA 7610. If the DPA 7610 is turned off or restarted after the Octel system has sent a MWI message, the message might be lost. The result is that some user phones might have MWI lights disabled erroneously or constantly enabled. If this happens, you need to clear the Meridian 1 MWI messages.
To clear Meridian MWIs, perform these steps:
Step 1 From the main menu, choose Configure.
Step 2 Choose Octel/Meridian 1 integration.
Step 3 Choose Clear M1 MWIs.
Step 4 Enter the directory numbers or range of directory numbers to clear, using this format: 4419, 4420, 4440-4450.
You must configure the DPA 7630/7610 with specific settings based on your Cisco CallManager configuration.
After configuring these Cisco CallManager settings, you must restart the DPA 7630/7610. See "Restarting the DPA 7630/7610" section.
The DPA 7630/7610 uses the TFTP server to identify the correct Cisco CallManager system. If you are not using DHCP to get the TFTP server, you must identify the address of the TFTP server.
|
Note If you use DHCP to get the TFTP server, the DPA 7630 uses option 66, option 150, or si-addr in that order of precedence. |
To assign a TFTP server, perform these steps:
Step 1 From the main menu, choose Configure.
Step 2 Choose CallManager.
Step 3 Choose TFTP server address.
Step 4 Enter the IP address or domain name of the TFTP server.
To enter multiple TFTP servers, separate them using a comma (,) or semicolon (;). You can enter a maximum of five (5) TFTP servers.
Step 5 Restart the DPA 7630/7610.
On Cisco CallManager, you must set the dialing sequence used to enable and disable the MWI on phones connected to Cisco CallManager. These settings must match those entered in Cisco CallManager (see the "Configuring the Message Waiting Light" section).
To enter the MWI settings, perform these steps:
Step 1 From the main menu, choose Configure.
Step 2 Choose CallManager.
Step 3 Choose the appropriate settings:
Step 4 Enter the appropriate values obtained from the Cisco CallManager system.
Step 5 Restart the DPA 7630/7610.
When Cisco CallManager is configured, one port on the DPA 7630/7610 serves as the primary or "pilot" directory number for a voice mail hunt group. Typically, you only need to specify this number if
For example, DPA 7630/7610 A has extensions 1000-1010, and DPA 7630/7610 B has extensions 1011-1020. These extensions form one large voice mail hunt group, with all the end-user phones forwarding to extension 1000.
You would not need to enter a pilot directory number for DPA 7630/7610 A because extension 1000 is one of its own voice mail ports. However, you would need to enter 1000 as the pilot directory number on DPA 7630/7610 B.
This pilot directory number should match the one defined in Cisco CallManager (see the "Setting Up the Voice Mail Hunt Group" section).
To enter a pilot directory number, perform these steps:
Step 1 From the main menu, choose Configure.
Step 2 Choose CallManager.
Step 3 Choose CallManager "Pilot" directory number.
Step 4 Enter the directory number for the primary number in the voice mail hunt group. You can enter multiple numbers separated by a comma.
Step 5 Restart the DPA 7630/7610.
The DPA 7630/7610 supports Cisco fax relay. Cisco fax relay provides a more reliable method of transporting fax data over the IP network rather than sending the fax information as a voice call. However, the terminating device must also support Cisco fax relay.
When fax relay is enabled, the DPA 7630/7610 attempts to negotiate fax relay first on the incoming voice over IP (VoIP) call. If this fails, then the DPA 7630/7610 automatically tries to negotiate the fax call in fax pass through mode.
By default, Cisco fax relay is enabled on the DPA 7630/7610. Follow these steps to disable it:
Step 1 From the main menu, choose Configure.
Step 2 Choose CallManager.
Step 3 Choose Fax Relay.
Step 4 Choose one of the following:
Step 5 Restart the DPA 7630/7610.
If the TFTP server is down, you can configure the DPA 7630/7610 to rely on its last known good configuration setting to access Cisco CallManager using cached TFTP responses.
To use cached TFTP responses, follow these steps:
Step 1 From the main menu, choose Configure.
Step 2 Choose CallManager.
Step 3 Choose Use cached TFTP responses.
Step 4 Choose one of the following:
Step 5 Restart the DPA 7630/7610.
Posted: Wed Aug 14 10:12:29 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.