Table Of Contents
Nortel Meridian 1/PBXLink Integration
Integration Overview
Integration Steps
Requirements
Integration Description
Integration Features
Configuring Cisco Unity for the Integration
Programming the Phone System
Setting up the PBXLink Box
Testing the Integration
Nortel Meridian 1/PBXLink 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 Chapters 1 through 3 of 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. Configure Cisco Unity for the integration. See the "Configuring Cisco Unity for the Integration" section.
3. Program the phone system and extensions. See the "Programming the Phone System" section.
4. Install and configure the Connected Systems™ PBXLink™ box. See the "Setting up the PBXLink Box" section.
5. Test the integration. See the "Testing the Integration" section.
Requirements
The Nortel Meridian/PBXLink integration supports configurations of the following components:
Phone System
•Nortel Meridian 1 with the following software option packages installed:
Table 1-1 Required Option Packages
Option Package
|
Package Number
|
EES
|
10
|
MSB
|
17
|
DDSP
|
19
|
MWC
|
46
|
DSET
|
88
|
CPND
|
95
|
ARIE
|
170
|
•One or more digital lines that are compatible with the M2616 digital phone connected to the PBX ports on the PBXLink box.
•For each voice messaging port, one analog port connected to the voice cards in the Cisco Unity server.
•The SMDI port in the PBXLink box connected to a serial port (COM1 is the default) on the Cisco Unity server with an RS-232 serial cable. If multiple PBXLink boxes are installed, the SMDI port of the last PBXLink box is connected to the Management port of the first PBXLink box with an RS-232 serial cable. The SMDI port of the first PBXLink box is connected to a serial port (COM1 is the default) on the Cisco Unity server with another RS-232 serial cable. Make sure that the serial protocol parameters for the Management port of the first PBXLink box are set to the same values as the SMDI port.
•The phone system ready for the integration as described in the installation guide for the phone system.
•If you use ACD hunt groups, packages ACD-A and ACD-B.
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.
Caution To prevent Windows from mistaking the serial connection for a serial mouse when rebooting the Cisco Unity server, confirm that the Boot.ini file is set according to instructions. Otherwise, the integration will not work properly. For details on setting up the Boot.ini file, refer to "Installing Windows 2000 Server" in Chapter 3 of the
Cisco Unity Installation Guide.
•A system key that enables the integration and the appropriate number of voice messaging ports.
•An available serial port (COM1 is the default).
Integration Description
The Nortel Meridian/PBXLink integration uses one or more PBXLink boxes that each emulate up to two Nortel M2616 digital phones. The PBXLink is connected to the phone system with digital phone lines and connected to the Cisco Unity server with an RS-232 serial cable. The voice messaging lines from the phone system connect to the analog voice cards in the Cisco Unity server.
The PBXLink box receives the following call information from the phone system:
•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) or the phone number of the calling party (if it is an external call and the system uses caller ID)
The PBXLink box formats this information as a Simplified Message Desk Interface (SMDI) packet and sends the packet to Cisco Unity through the RS-232 serial cable.
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 PBXLink box also activates or deactivates message waiting indicators (MWIs) after receiving a command from Cisco Unity.
For more information, refer to Chapter 1 of the PBXLink User Guide, which is available at the following website:
http://www.connectedsystems.com/pbx/48/pbxlink48.html
Configuration for 24 or Fewer Ports
Nortel integrations with 24 or fewer ports can use one the following configurations (others that are possible):
•(Recommended) A single PBXLink-48 box with Port A set for MWIs only and Port B set for calls only.
•Two PBXLink-24 boxes with Port A of one box set for MWIs only and Port A of the second box set for calls only.
•A single PBXLink-24 box with Port A set for both calls and MWIs.
Configuration for 25 to 48 Ports
Nortel integrations with 25 to 48 ports can use one of the following configurations (others that are possible):
•(Recommended) A single PBXLink-48 box with Port A set for MWIs only and Port B set for calls only, and a single PBXLink-24 box with Port A set for calls only.
•Two PBXLink-24 boxes with Port A of one box set for both calls and MWIs and Port A of the second box set for calls only.
It is not possible to use a single PBXLink-48 box with Port A set to both calls and MWIs and Port B set for calls only. In this configuration, Port B is disabled.
PBXLink Box Connections
A single PBXLink box is connected to the phone system with a digital phone line and connected to the Cisco Unity server with an RS-232 serial cable. The voice messaging lines from the phone system connect to the analog voice cards in the Cisco Unity server. The following illustration shows the required connections.
Figure 1-1 Serial Connection Between a Single PBXLink Box and Cisco Unity
Multiple PBXLink boxes are connected to the Cisco Unity server by using an RS-232 cable to connect the SMDI port from the last PBXLink box to the Management port of the first PBXLink box. Another RS-232 cable is then used to connect the SMDI port of the first PBXLink box to the Cisco Unity server. The voice messaging lines from the phone system connect to the analog voice cards in the Cisco Unity server. The following illustration shows the required connections.
Figure 1-2 Serial Connections Between Multiple PBXLink Boxes and Cisco Unity
Integration Features
The Nortel Meridian/PBXLink 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
|
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
|
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).
|
Configuring Cisco Unity for the Integration
After ensuring that the Cisco Unity server is ready for the integration by completing the appropriate tasks in Chapters 1 through 3 of 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 box, confirm that the setting is Serial for a single phone system integration or Multiple Integrations for a dual phone system integration.
Step 4 If the setting is not Serial 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-2 Switch Settings
Switch Parameter
|
Required Setting
|
Manufacturer
|
Nortel
|
Model
|
Meridian-1
|
Switch PBX Software Version
|
All
|
Integration
|
Serial
|
Step 6 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.
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."
Programming the Phone System
If you use programming options other than those supplied in the following procedures, the performance of the integration may be affected.
If you want to remap extension numbers (for example, when multiple subscribers use a single phone, or when multiple extension numbers on a single phone should go to a single subscriber greeting), see Appendix B, "Remapping Extension Numbers."
Make sure that the phone system sends calls only to Cisco Unity voice ports that are set to Answer Calls on the System > Ports page in the Cisco Unity Administrator. Calls sent to a voice port not set to Answer Calls cannot be answered by Cisco Unity. And, if certain voice cards are installed, the call will not be dropped, but the port remains unavailable for use until the Cisco Unity server is restarted.
To program the phone system
Step 1 Assign extensions for the voice messaging ports.
Step 2 Confirm that the software on the phone system is current by using overlay 22 to display options EES, MSB, DDSP, MWC, DSET, CPND, and ARIE. If any of these options is missing, contact your sales representative.
Step 3 On overlay 15, set the following customer data block options.
Table 1-3 Customer Data Block Options
Option
|
Setting
|
REQ
|
CHG
|
TYPE
|
CDB
|
CUST
|
<customer data block>
|
NITE
|
<the pilot number if night calls go to voice mail>
|
OPT
|
CFO
MCI
IDP
|
FNAD
|
FDN
|
FNAN
|
FDN
|
FNAT
|
FDN
|
FNAL
|
FDN
|
CFNA
|
6
|
DFNA
|
6
|
AODN
|
<the pilot number for the automated attendant>
|
MDID
|
YES
|
NDID
|
YES
|
MWFB
|
YES
|
LDTT
|
6
|
EEST
|
NO
|
Step 4 On overlay 95, set the following options to enable display of a four-letter code why the call was forwarded.
Table 1-4 Calling Party Display Options
Option
|
Setting
|
REQ
|
CHG
|
TYPE
|
CPND
|
CUST
|
<customer data block>
|
RESN
|
YES
|
CFWD
|
CFWD
|
CFNA
|
CFNA
|
HUNT
|
HUNT
|
XFER
|
T
|
AAA
|
A
|
Step 5 On overlay 10, set the following options to enable the analog voice messaging lines.
Table 1-5 Analog Voice Messaging Line Options
Option
|
Setting
|
CDEN
|
SD (if QPC60)
DD (if QPC452)
4D (if QPC594)
|
CUST
|
<customer data block>
|
DN
|
<the extension number for the port being set>
|
HUNT
|
<the next line after the port being set>
|
CLS
|
HTA FBD DTN XFA FND MWD LDTA
|
Step 6 On overlay 11, set the following options to enable the digital lines for the PBXLink box.
If you set up more than 24 voice messaging ports, it is recommended that you balance the load among the PBXLink boxes. You can balance the load by enabling digital line keys for one PBXLink box to monitor odd-numbered ports (1, 3, 5, and so on), while enabling digital line keys on the other PBXLink box to monitor even-numbered ports (2, 4, 6, and so on). For details, see the "To set up the port LTNs" section.
Table 1-6 Digital Line Options
Option
|
Setting
|
AOM
|
1
|
CLS
|
ADD HFD CNDA DNDA
|
HUNT
|
000
|
KEY 00 SCR
|
<the primary number for the digital line; any valid unused number>
|
KEY 16 SCN
|
<the pilot number; or for an ACD hunt group, the first analog line number in the hunt group>
|
KEY 17 SCN
|
<the second analog line number after the extension for KEY 16>
|
.
.
.
|
<additional analog line numbers>
|
KEY 37 SCN
|
<the 22nd analog line number>
|
KEY 5 SCN
|
<the 23rd analog line number>
|
KEY 6 SCN
|
<the 24th analog line number>
|
Step 7 Program each phone to forward calls to the pilot number assigned to the voice messaging ports, based on one of the following Cisco Unity call transfer types.
Table 1-7 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.
|
Perform one of the following procedures, depending on the number of voice messaging ports in the Cisco Unity server. If Cisco Unity has more than 30 voice messaging ports, it is recommended that you set up an ACD hunt group as described in the "To set up an ACD hunt group for more than 30 ports" section.
To set up a hunt group for up to 30 ports
Step 1 Set up the first voice messaging port as the pilot number of the hunt group.
Step 2 Set the first voice messaging port to hunt to the second voice messaging port.
Step 3 Set the second voice messaging port to hunt to the third, then continue up to the 30th.
Step 4 Set the 30th voice messaging port to hunt to the first voice messaging port.
Table 1-8 Example of 30-Port Hunt Group
Device
|
Setting
|
Destination
|
Port 1
|
HUNT
|
Port 2
|
Port 2
|
HUNT
|
Port 3
|
Port 3
|
HUNT
|
Port 4
|
.
.
.
|
|
<additional ports>
|
Port 29
|
HUNT
|
Port 30
|
Port 30
|
HUNT
|
Port 1
|
To set up an ACD hunt group for more than 30 ports
Step 1 Set up ACD 1 as the pilot number of the hunt group.
Step 2 With the Night Call Forward Destination (NCFW) command, set ACD 1 to forward to the first voice messaging port.
Step 3 Set the first voice messaging port to hunt to the second, then continue up to the 30th.
Step 4 Set the 30th voice messaging port to hunt to ACD 2.
Step 5 With the NCFW command, set ACD 2 to forward to the 31st voice messaging port.
Step 6 Set the 31st voice messaging port to hunt to the 32nd, then continue up to the last voice messaging port.
Step 7 Set the last voice messaging port to hunt to ACD 1.
Table 1-9 Example of 48-Port ACD Hunt Group
Device
|
Setting
|
Destination
|
ACD 1 (pilot number)
|
NCFW
|
Port 1
|
Port 1
|
HUNT
|
Port 2
|
Port 2
|
HUNT
|
Port 3
|
.
.
.
|
|
<additional ports>
|
Port 29
|
HUNT
|
Port 30
|
Port 30
|
HUNT
|
ACD 2
|
ACD 2
|
NCFW
|
Port 31
|
Port 31
|
HUNT
|
Port 32
|
.
.
.
|
|
<additional ports>
|
Port 46
|
HUNT
|
Port 47
|
Port 47
|
HUNT
|
Port 48
|
Port 48
|
HUNT
|
ACD1
|
Setting up the PBXLink Box
To set up the PBXLink box, you can access the configuration menus through:
•A terminal access application such as HyperTerminal. Set the application to 1200 baud, even parity, 7 data bits, and 1 stop bit.
•The display panel and buttons on top of the PBXLink box. For details, refer to the PBXLink User Guide, which is available at the following website:
http://www.connectedsystems.com/pbx/48/pbxlink48.html
To set up the PBXLink box
Step 1 If you are using HyperTerminal, enter M and press Enter. The Main menu appears.
If you are not using HyperTerminal, skip to Step 2.
Step 2 Select Configuration and press Enter.
Step 3 Select PBX Options and press Enter. The list of phone systems appears.
Step 4 Select Nortel M1 and press Enter. The interface leaves the menu system.
Step 5 If you are using HyperTerminal, enter M and press Enter. Then enter 1 and press Enter.
If you are not using HyperTerminal, skip to Step 6.
Step 6 Select PBX Options and press Enter.
Step 7 Select Analog Ports on A, and enter the number of voice messaging ports that Port A monitors, then press Enter.
Step 8 If you are setting up a PBXLink-48 box, select Analog Ports on B, and enter the number of voice messaging ports that Port B monitors, then press Enter. Otherwise, skip to the next step.
Step 9 Select Configure Port A, select one of the following settings for Port A, then press Enter.
Table 1-10 Port Configuration Settings
Setting
|
Meaning
|
Calls Only
|
The port handles only calls.
|
MWI Only
|
The port handles only MWIs.
|
Calls + MWI
|
The port handles both calls and MWIs.
|
Step 10 If you are setting up a PBXLink-48 box, select Configure Port B, select one of the preceding settings for Port B, then press Enter. Otherwise, skip to the next step.
Step 11 Select Prime Number, enter the pilot number for Cisco Unity, then press Enter.
Step 12 Select Call Forward Display, enter the option settings as shown in the following table, then press Enter.
Table 1-11 Call Forward Display Options
Option
|
Setting
|
CFWD
|
•CFWD (only if you do not use ACD hunt groups)
•DIR (only if you use ACD groups)
|
CFNA
|
CFNA
|
HUNT
|
HUNT
|
If the system has more than 24 voice messaging ports, it is recommended that you balance the load among the PBXLink boxes by setting up the Port LTNs for random operation.
To set up the port LTNs
Step 1 If you are using HyperTerminal, enter M and press Enter. The Main menu appears.
If you are not using HyperTerminal, skip to Step 2.
Step 2 Select Configuration and press Enter. Then select SMDI Options and press Enter.
Step 3 Select Port A LTNs (or the port that handles calls), then select Random and press Enter.
Step 4 Select Setup Random LTNs, enter the voice messaging port values (not the extension) as shown in the following table, then press Enter.
Table 1-12 Random LTN Settings for Odd-Numbered Ports
LTN Number
|
Voice Messaging Port Value
|
0
|
0001
|
1
|
0003
|
2
|
0005
|
.
.
.
|
<the remaining odd-numbered voice messaging ports>
|
Step 5 Repeat Steps 1 through 3 on the interface of the next PBXLink box.
Step 6 Select Setup Random LTNs, enter the voice messaging port values (not the extension) as shown in the following table, then press Enter.
Table 1-13 Random LTN Settings for Even-Numbered Ports
LTN Number
|
Voice Messaging Port Value
|
0
|
0002
|
1
|
0004
|
2
|
0006
|
.
.
.
|
<the remaining even-numbered voice messaging ports>
|
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.
Feedback
