Corporate Headquarters:
Copyright © 2005 Cisco Systems, Inc. All rights reserved.
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Avaya Definity Gx/PBXLink Integration Guide for
Cisco Unity 3.1
Revised February 10, 2005
This document provides instructions for integrating the phone system with the Cisco Unity voice
messaging system.
Integration Tasks
Before performing the following tasks to integrate Cisco Unity with the Avaya Definity/PBXLink phone
system, confirm that the Cisco Unity server is ready for the integration by completing the appropriate
tasks in 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 on page 2.
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 on page 5.
3. Program the Avaya Definity/PBXLink phone system and extensions. See the “Programming the
Avaya Definity/PBXLink Phone System” section on page 6.
4. Install and configure the PBXLink box. See the “Setting up the PBXLink Box” section on page 15.
5. Configure Cisco Unity for the integration. See the “Configuring Cisco Unity for the Integration”
section on page 19.
6. Test the integration. See the “Testing the Integration” section on page 20.
7. If you have Cisco Unity failover, integrate the secondary server. (Cisco Unity failover is supported
only for release 3.1(2) and later.) See the “Integrating a Secondary Server for Cisco Unity Failover”
section on page 23.
2
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Requirements
Requirements
The Avaya Definity/PBXLink integration supports configurations of the following components:
Phone System
• An Avaya Definity phone system with one or two digital lines connected to the PBX ports on the
PBXLink box. The line or lines must be compatible with the 7434D or 8434D digital phones. If
vectoring will be used and depending on the phone system, the line or lines may require
compatibility with only the 7434D digital phone.
• Bridged mode feature, enabled.
• 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. We recommend that the serial cables have the following construction for the serial
cable:
–
A maximum of 50 feet (15.24 m) in length
–
24 AWG stranded conductors
–
Low capacitance—for example, no more than 12 pF/ft (39.4 pF/m) between conductors
–
At least 65 percent braided shield over aluminized polymer sleeve around conductors
–
UL-recognized overall cable jacket insulation with low dielectric constant
–
Braided shield fully terminated to and enclosed by a metal connector backshell
–
Gold-plated connector contacts
• The phone system ready for the integration as described in the installation guide for the phone
system.
Cisco Unity Server
• The applicable voice cards, installed. For details on supported voice cards, refer to Cisco Unity
System Requirements, and Supported Hardware and Software, available on Cisco.com at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.
• Cisco Unity installed and ready for the integration, as described in 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).
3
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Integration Description
Integration Description
The Avaya Definity/PBXLink integration uses one or more PBXLink boxes, with each box emulating up
to two Avaya 7434D or 8434D 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.
This integration requires that bridged mode be used.
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.
Cisco Unity also activates or deactivates messaging waiting indicators (MWIs) through the analog voice
messaging ports rather than through the serial data link as in other serial integrations. As a result, it is
necessary to set some voice messaging ports for handling MWIs as described in the “Planning How the
Voice Messaging Ports Will Be Used by Cisco Unity” section on page 5, and to enter the MWI on and
off codes as described in the “Configuring Cisco Unity for the Integration” section on page 19.
For more information on the PBXLink box, refer to the PBXLink documentation, which is available
from the manufacturer.
Configuration for 24 or Fewer Ports
Avaya Definity/PBXLink integrations with 24 or fewer ports can use the following configuration (others
are possible):
• (Recommended) A single PBXLink-24 box with Port A set for calls only.
Configuration for 25 to 48 Ports
Avaya Definity/PBXLink integrations with 25 to 48 ports can use the following configuration (others are
possible):
• (Recommended) A single PBXLink-48 box with Ports A and B set for calls only.
• Two PBXLink-24 boxes with Port A of both set for calls only.
Configuration for 49 to 72 Ports
Avaya Definity/PBXLink integrations with 49 to 72 ports can use one of the following configurations
(others are possible):
• (Recommended) One PBXLink-24 box with Port A set for calls only, and a PBXLink-48 box with
Ports A and B of both set for calls only.
• Two PBXLink-48 boxes with Ports A and B of both set for calls only.
• Three PBXLink-24 boxes with Port A of all three set for calls only.
4
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Integration Description
PBXLink Box Connections
A single PBXLink box is connected to the phone system with one or two 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. Figure 1 shows the required
connections.
Figure 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. Figure 2 shows the required connections.
Figure 2 Serial Connections Between Multiple PBXLink Boxes and Cisco Unity
Digital lines
RS-232 serial cable
Analog lines
Phone system
PBXLink box
Cisco Unity serve
r
55419
Digital lines
RS-232 serial cables
Analog lines
Phone system
Cisco Unity serve
r
54394
PBXLink box #1
Add PBXLink
boxes as needed.
PBXLink box #2
PBXLink box #3
5
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Planning How the Voice Messaging Ports Will Be Used by Cisco Unity
Integration Features
The Avaya Definity/PBXLink integration with Cisco Unity provides the following features.
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 set message waiting indicators (MWIs), to make AMIS deliveries, and to make
telephone record and playback (TRAP) connections.
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.
Call forward to personal greeting
When an incoming call is routed to an unanswered 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.
Call forward to busy greeting
When an incoming call is routed to a busy extension, the call is
forwarded to the voice mail of the subscriber. The caller then hears
the busy greeting (if the subscriber enabled it) 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 extension.
6
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Programming the Avaya Definity/PBXLink Phone System
• The number of MWIs that will be activated when call traffic is at its peak.
• The number of AMIS delivery calls.
• The number of Media Master connections needed when call traffic is at its peak. (Media Master
connections are used by Cisco Unity web applications and e-mail clients to play back and record
over the phone.)
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, these voice messaging ports are the busiest. They also have the lowest port
numbers for the phone system. As a general guideline, assign a majority of the voice messaging ports to
answer calls.
You can set voice messaging ports to both answer calls and to dial out (for example, to set MWIs).
The Number of Voice Messaging Ports That Will Only Dial Out, and Not Answer Calls
Ports that will only dial out and will not answer calls can do one or more of the following:
• Notify subscribers by phone, pager, or e-mail of messages that have arrived.
• Turn MWIs on and off for subscriber extensions.
• 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 Media Master connection so that subscribers can use the phone as a recording and playback
device in Cisco Unity web applications and e-mail clients.
Typically, these voice messaging ports are the least busy ports. They also have the highest port numbers
for the phone system. As a general guideline, assign a minority of the voice messaging ports to dial out.
Caution In programming the phone system, do not send calls to voice messaging ports in Cisco Unity that cannot
answer calls (voice messaging ports that are not set to Answer Calls). For example, if a voice messaging
port is set only to Dialout MWI, do not send calls to it.
Preparing for Programming the Phone System
Record your decisions about the voice messaging ports to guide you in programming the phone system.
Programming the Avaya Definity/PBXLink Phone System
If you use programming options other than those supplied in the following procedure, 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: Remapping Extension Numbers” section on page 31.
7
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Programming the Avaya Definity/PBXLink Phone System
Caution In programming the phone system, do not send calls to voice messaging ports in Cisco Unity that cannot
answer calls (voice messaging ports that are not set to Answer Calls). For example, if a voice messaging
port is set only to Dialout MWI, do not send calls to it.
To program the Avaya Definity/PBXLink phone system
Step 1 Use the Add Station <extension number> command (for example, Add Station 2001) to assign an
extension number for each voice messaging port. Set the following options and press Enter.
The options available may vary depending on the software version of your phone system.
Step 2 Use the Add Station <extension number> command (for example, Add Station 2999) to assign an
extension number for each digital line to the PBXLink box. Set the digital line options (Table 2) and
button assignments (Table 3).
Table 1 Voice Messaging Port Options
Option Setting
Extension <the extension number of the voice messaging port>
Type 2500
Port <the physical address of the port>
Lock Messages? n
Test? n
Name VoiceMail 2001
(The extension number must appear within the first 16
characters.)
LWC Reception? n
LWC Activation? y
Redirect Notification? n
Off Premise Station? n
Coverage Msg Retrieval Permission? n
Data Restriction? y
Call Waiting Indication? n
Distinctive Audible Alert? n
Message Waiting Indicator? n
Adjunct Supervision y
Table 2 Digital Line Options for All Lines
Option Setting
Extension <the extension number of the digital line>
Type
• 8434D
• 7434D
8
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Programming the Avaya Definity/PBXLink Phone System
Port <the physical address of the port>
Data Module? n
Expansion Module? n
LWC Reception None
LWC Activation? y
CDR Privacy? n
Redirect Notification? n
Per Button Ring Control? n
Bridged Call Alerting? n
Active Station Ringing Single
Auto Select Any Idle Appearance? n
Coverage Msg Retrieval? y
Auto Answer None
Data Restriction? n
Idle Appearance Preference? n
Restrict Last Appearance? y
Audible Message Waiting? n
Display Client Redirection? n
Select Last Used Appearance? n
Table 3 Button Assignments for All Lines
Button Assignment Setting
1 call-appr
2 call-appr
3 call-appr
4 normal
(Use the Normal setting for programming a 7434D phone. Leave the
setting blank for an 8434D phone.)
5 inspect
6
7
8
9
10 call-appr
Table 2 Digital Line Options for All Lines (continued)
Option Setting
9
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Programming the Avaya Definity/PBXLink Phone System
Step 3 Set the appropriate feature button assignments depending on the number of PBXLink digital ports and
whether load balancing is used.
If there is a single PBXLink digital port and load balancing is not used, set the feature button
assignments as shown in Table 4, then press Enter.
If there are two PBXLink digital ports and load balancing is used, set the feature button assignments as
shown in both Table 5 and Table 6, then press Enter.
If there are three PBXLink digital ports and load balancing is used, set the feature button assignments
as shown in Table 7, Table 8, and Table 9, then press Enter.
Table 4 Feature Button Assignments for a Single PBXLink Digital Port Without Load
Balancing
Feature Button Number Setting
1 abrdg-appr Extn: <1st voice mail extension>
2 abrdg-appr Extn: <2nd voice mail extension>
3 abrdg-appr Extn: <3rd voice mail extension>
.
.
.
<the remaining voice mail extensions>
Table 5 Feature Button Assignments for First of Two PBXLink Digital Ports with Load
Balancing
Feature Button Number Setting
1 abrdg-appr Extn: <1st voice mail extension>
2 abrdg-appr Extn: <3rd voice mail extension>
3 abrdg-appr Extn: <5th voice mail extension>
.
.
.
<the remaining odd-numbered voice mail extensions>
Table 6 Feature Button Assignments for Second of Two PBXLink Digital Ports with Load
Balancing
Feature Button Number Setting
1 abrdg-appr Extn: <2nd voice mail extension>
2 abrdg-appr Extn: <4th voice mail extension>
3 abrdg-appr Extn: <6th voice mail extension>
.
.
.
<the remaining even-numbered voice mail extensions>
10
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Programming the Avaya Definity/PBXLink Phone System
If the phone system has 1 to 8 voice messaging ports or if it does not have vectoring capability, perform
the procedure “To set up coverage paths for one to eight voice messaging ports or for phone systems
without vectoring capability.” Otherwise, perform the procedure “To set up coverage paths for more than
eight voice messaging ports.”
To set up coverage paths for one to eight voice messaging ports or for phone systems without vectoring capability
Refer to Chapter 6 in the PBXLink documentation, which is available from the manufacturer.
Table 7 Feature Button Assignments for First of Three PBXLink Digital Ports with Load
Balancing
Feature Button Number Setting
1 abrdg-appr Extn: <1st voice mail extension>
2 abrdg-appr Extn: <4th voice mail extension>
3 abrdg-appr Extn: <7th voice mail extension>
.
.
.
<every third remaining voice mail extension>
Table 8 Feature Button Assignments for Second of Three PBXLink Digital Ports with Load
Balancing
Feature Button Number Setting
1 abrdg-appr Extn: <2nd voice mail extension>
2 abrdg-appr Extn: <5th voice mail extension>
3 abrdg-appr Extn: <8th voice mail extension>
.
.
.
<every third remaining voice mail extension>
Table 9 Feature Button Assignments for Third of Three PBXLink Digital Ports with Load
Balancing
Feature Button Number Setting
1 abrdg-appr Extn: <3rd voice mail extension>
2 abrdg-appr Extn: <6th voice mail extension>
3 abrdg-appr Extn: <9th voice mail extension>
.
.
.
<every third remaining voice mail extension>
11
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Programming the Avaya Definity/PBXLink Phone System
To set up coverage paths for more than eight voice messaging ports
Step 1 For a phone system with more than eight voice messaging ports, use the Add Vdn <extension number>
command (for example Add Vdn 2000) to set up a vector directory number for the pilot number
(extension 2000 in this example). Set the following options and press Enter.
Step 2 Use the Add Vector 1 or the Change Vector 1 command to define the vector for voice messaging port
extensions that answer calls. Set the options according to one of the following examples Then press
Enter.
For a system with a single PBXLink digital port, use the following example of a system with six lines.
For a system with two PBXLink digital ports, use the following example, which bridges every second
extension to Port A and the remaining extensions to Port B.
Table 10 Vector Direction Number Options
Option Setting
Extension <the pilot number>
Name VoiceMail 2000
Display Override? n
COR 1
Vector Number 1
(must match the Number option in Table 11)
Measured none
Table 11 Vector Definition Options for a Single Digital Port
Option Setting
Number 1
(must match the Vector Number option in Table 10)
Name voicevec
ASAI Routing? n
Basic? y
Prompting? n
01 wait time 0 secs hearing ringback
02 route to number 2001 if unconditionally
(use the first voice messaging port extension)
03 route to number 2002 if unconditionally
04 route to number 2003 if unconditionally
05 route to number 2004 if unconditionally
06 route to number 2005 if unconditionally
07 route to number 2006 if unconditionally
08 busy
12
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Programming the Avaya Definity/PBXLink Phone System
Table 12 Vector Definition Options for Call Vector 1
Option Setting
Number 1
Name voicevec1
ASAI Routing? n
Basic? y
Prompting? n
01 wait time 0 secs hearing ringback
02 route to number 2001 if unconditionally
03 route to number 2002 if unconditionally
04 route to number 2003 if unconditionally
05 route to number 2004 if unconditionally
06 route to number 2005 if unconditionally
07 route to number 2006 if unconditionally
08 route to number 2007 if unconditionally
09 route to number 2008 if unconditionally
10 route to number 2009 if unconditionally
11 route to number 2010 if unconditionally
12 goto vector 2 if unconditionally
Table 13 Vector Definition Options for Call Vector 2
Option Setting
Number 2
Name voicevec2
ASAI Routing? n
Basic? y
Prompting? n
01 route to number 2011 if unconditionally
02 route to number 2012 if unconditionally
03 route to number 2013 if unconditionally
04 route to number 2014 if unconditionally
05 route to number 2015 if unconditionally
06 route to number 2016 if unconditionally
07 route to number 2017 if unconditionally
08 route to number 2018 if unconditionally
09 route to number 2019 if unconditionally
13
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Programming the Avaya Definity/PBXLink Phone System
For a system with three PBXLink digital ports, use the following example, which bridges every third
extension to Port A, another third of the extensions to Port A, and the remaining extensions to Port C.
10 route to number 2020 if unconditionally
11 busy
Table 13 Vector Definition Options for Call Vector 2 (continued)
Option Setting
Table 14 Vector Definition Options for Call Vector 1
Option Setting
Number 1
Name voicevec1
ASAI Routing? n
Basic? y
Prompting? n
01 wait time 0 secs hearing ringback
02 route to number 2001 if unconditionally
03 route to number 2002 if unconditionally
04 route to number 2003 if unconditionally
05 route to number 2004 if unconditionally
06 route to number 2005 if unconditionally
07 route to number 2006 if unconditionally
08 route to number 2007 if unconditionally
09 route to number 2008 if unconditionally
10 route to number 2009 if unconditionally
11 route to number 2010 if unconditionally
12 goto vector 2 if unconditionally
Table 15 Vector Definition Options for Call Vector 2
Option Setting
Number 2
Name voicevec2
ASAI Routing? n
Basic? y
Prompting? n
01 route to number 2011 if unconditionally
02 route to number 2012 if unconditionally
03 route to number 2013 if unconditionally
14
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Programming the Avaya Definity/PBXLink Phone System
After programming the phone system, it is necessary to set up the direct lines for users on the phone
system.
To set up user phones
Step 1 Use the Change Station (extension number) command to display the Station screen for each extension.
04 route to number 2014 if unconditionally
05 route to number 2015 if unconditionally
06 route to number 2016 if unconditionally
07 route to number 2017 if unconditionally
08 route to number 2018 if unconditionally
09 route to number 2019 if unconditionally
10 route to number 2020 if unconditionally
11 goto vector 3 if unconditionally
Table 16 Vector Definition Options for Call Vector 3
Option Setting
Number 3
Name voicevec3
ASAI Routing? n
Basic? y
Prompting? n
01 route to number 2021 if unconditionally
02 route to number 2022 if unconditionally
03 route to number 2023 if unconditionally
04 route to number 2024 if unconditionally
05 route to number 2025 if unconditionally
06 route to number 2026 if unconditionally
07 route to number 2027 if unconditionally
08 route to number 2028 if unconditionally
09 route to number 2029 if unconditionally
10 route to number 2030 if unconditionally
11 busy
Table 15 Vector Definition Options for Call Vector 2 (continued)
Option Setting
15
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Setting up the PBXLink Box
Step 2 In the Name field, enter the user’s name and extension. The PBXLink box can display only the first 16
characters, and the extension must appear in these 16 characters.
Step 3 In the Coverage Path field, enter 1.
Setting up the PBXLink Box
When setting up the PBXLink box, you can access the configuration menus through the display panel
and buttons on the PBXLink box. For details, refer to the PBXLink documentation, which is available
from the manufacturer.
To Update the PBXLink Box Firmware
Step 1 In a web browser on your computer, go to the Cisco Unity Utilities Software Download page at
http://www.cisco.com/cgi-bin/tablebuild.pl/unity-util.
Note To access the software download page, you must be logged on to Cisco.com as a registered user.
Step 2 Click PBXLinkFirmwareUpdate.
Step 3 Follow the instructions to download the PBXLink box firmware update file to your computer.
Step 4 Exit the web browser.
Step 5 Confirm that the PBXLink box is connected to power and turned on.
Step 6 Disconnect the following cables:
• All phone cables connect to the PBXLink box.
• The RS-232 serial cable connected to the Management port
Step 7 Connect one end of am RS-232 serial cable to the Management port of the PBXLink box and the other
end of the serial cable to the serial port of your computer.
Step 8 On your computer, start HyperTerminal or another terminal access application.
Step 9 Set the terminal access application to use the serial connection settings used by the PBXLink box. You
can view the PBXLink serial connection settings by doing the following:
a. On the PBXLink box, press Cancel until the Configuration menu appears.
b. Click OK.
c. Scroll up until Serial Port Options appears, and click OK.
d. Scroll down until Management Port appears, and click OK.
e. Scroll through the serial port settings to verify them.
Step 10 Restart the PBXLink box.
Step 11 In the HyperTerminal window on your computer, press M and press Enter.
Step 12 Press 3 (Reboot/Download), and press Enter.
Step 13 Press 2 (Reboot & Download Code), and press Enter.
16
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Setting up the PBXLink Box
Note Ignore any unusual characters that may appear on the screen.
Step 14 On the Transfer menu, click Send File.
Step 15 In the Send File dialog box, under Filename, click Browse.
Step 16 Browse to the PBXLink box firmware upgrade file that you downloaded to your computer.
Step 17 In the Send File dialog box, under Protocol, click Xmodem.
Step 18 Click Send.
Step 19 When the firmware upgrade is complete, exit HyperTerminal.
Step 20 Repeat Step 5 through Step 19 for all remaining PBXLink boxes.
Step 21 Connect the PBXLink boxes to the phone system and to the Cisco Unity server.
To set up the PBXLink box
Step 1 Select Configuration and press Enter.
Step 2 Select Integration and confirm that Stopped is selected.
Step 3 Select PBX Type, and select either Lucent 2 wire or Lucent 4 wire. If the setting you select is not the
same as the setting that first appeared, the PBXLink box restarts.
Step 4 If the PBXLink box restarts, repeat Step 1, then skip to Step 5. Otherwise, continue with Step 5.
Step 5 Select PBX Options and press Enter. The list of phone systems appears.
Step 6 Select Phone Set and enter either 8434D or 7434D, as you set up the digital port with the Add Station
command.
Step 7 Select Voic e C odi ng and select Mu Law for North America. Otherwise, select A Law.
Step 8 Select Analog Ports on A, enter the number of voice messaging ports that Port A monitors, and then
press Enter.
Step 9 If you are setting up a PBXLink-48 box, select Analog Ports on B, enter the number of voice messaging
ports that Port B monitors, and then press Enter. Otherwise, skip to the next step.
Step 10 Select Configure Port A, select Calls Only, and then press Enter.
Step 11 If you are setting up a PBXLink-48 box, select Configure Port B, select Calls Only, and then press
Enter. Otherwise, skip to the next step.
Step 12 Select Prime Number, enter the pilot number that the phone system uses to call Cisco Unity, and then
press Enter.
Step 13 Select Extension Length and enter the number of digits in the subscriber extensions. If the subscriber
extensions have different lengths, enter the number of digits in the longest extension.
Step 14 Select Integration, select Started, and then press Enter.
If the system has two or more PBXLink digital ports, it is recommended that you balance the load among
the PBXLink boxes by setting up the Port LTNs for random operation. Depending on the number of
PBXLink digital ports your system uses, perform the appropriate procedure that follows.
17
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Setting up the PBXLink Box
To set up the port LTNs for two PBXLink digital ports
This procedure sets up the port LTNs for every second voice messaging port.
Step 1 Select Configuration and press Enter. Then select SMDI Options and press Enter.
Step 2 Select Port A LTNs (or the port that handles calls), select Random, and then press Enter.
Step 3 Select Setup Random LTNs, enter the voice messaging port values (not the extension) as shown in the
following table, and then press Enter.
Step 4 Repeat Step 1 through Step 3 on the interface of the next PBXLink box.
Step 5 Select Setup Random LTNs, enter the voice messaging port values (not the extension) as shown in the
following table, and then press Enter.
Step 6 Select Integration, select Started, and then press Enter.
To set up the port LTNs for three PBXLink digital ports
This procedure sets up the port LTNs for every third voice messaging port.
Step 1 Select Configuration and press Enter. Then select SMDI Options and press Enter.
Step 2 Select Port A LTNs (or the port that handles calls), select Random, and then press Enter.
Step 3 Select Setup Random LTNs, enter the voice messaging port values (not the extension) as shown in the
following table, and then press Enter.
Table 17 Random LTN Settings for Odd-Numbered Ports
LTN Number Voice Messaging Port Value
00001
10003
20005
.
.
.
<the remaining odd-numbered voice messaging ports>
Table 18 Random LTN Settings for Even-Numbered Ports
LTN Number Voice Messaging Port Value
00002
10004
20006
.
.
.
<the remaining even-numbered voice messaging ports>
18
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Setting up the PBXLink Box
Step 4 Repeat Step 1 and Step 2 on the interface of the next PBXLink box.
Step 5 Select Setup Random LTNs, enter the voice messaging port values (not the extension) as shown in the
following table, and then press Enter.
Step 6 Repeat Step 1 and Step 2 on the interface of the next PBXLink box.
Step 7 Select Setup Random LTNs, enter the voice messaging port values (not the extension) as shown in the
following table, and then press Enter.
Step 8 Select Integration, select Started, and then press Enter.
Table 19 Random LTN Settings for the First Set of Ports
LTN Number Voice Messaging Port Value
00001
10004
20007
.
.
.
<the remaining voice messaging ports in the first set>
Table 20 Random LTN Settings for the Second Set of Ports
LTN Number Voice Messaging Port Value
00002
10005
20008
.
.
.
<the remaining voice messaging ports in the second set>
Table 21 Random LTN Settings for the Third Set of Ports
LTN Number Voice Messaging Port Value
00003
10006
20009
.
.
.
<the remaining voice messaging ports in the third set>
19
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Configuring Cisco Unity for the Integration
Configuring Cisco Unity for the Integration
After ensuring that the Cisco Unity server is ready for the integration by completing the appropriate
tasks in 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 field, 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.
Step 6 Enter the codes that turn message waiting indication on and off. The MWI codes are located in the Active
Switch Setting area at the top of the Switch Settings page.
Step 7 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.
For best performance, use the first voice messaging ports for incoming calls and the last ports to dial out.
This helps minimize 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.
Table 22 Switch Settings
Switch Parameter Required Setting
Manufacturer Avaya
Model Definity Gx
Switch PBX Software Version All (Analog MWI)
Integration Serial
20
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
OL-1846-06
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1
Testing the Integration
Caution In programming the phone system, do not send calls to voice messaging ports in Cisco Unity that cannot
answer calls (voice messaging ports that are not set to Answer Calls). For example, if a voice messaging
port is set only to Message Waiting Indication, do not send calls to it.
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.
Testing the Integration
To test whether Cisco Unity and the phone system are integrated correctly, do the procedures in the order
listed.
If any of the steps indicates a failure, refer to the following documentation as applicable:
• The installation guide for the phone system
• Cisco Unity Troubleshooting Guide
• The setup information earlier in this document
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 the Subscribers > Subscribers > Profile page.
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 the Subscribers > Subscribers > Call Transfer page
for Example Subscriber.
For more information on transfer settings, refer to the “Subscriber Template Call Transfer Settings”
section in the online 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 the Subscribers > Subscribers > Messages page for
Example Subscriber.
Step 11 Under Message Waiting Indicators (MWIs), check the Use MWI for Message Notification check box.
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
/
