Cisco Unity 3.1 User Manual

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

2. Plan how the voice messaging ports will be used by Cisco Unity. See the “Planning How the Voice

3. Program the Avaya Definity/PBXLink phone system and extensions. See the “Programming the

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”

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

server requirements have been met. See the “Requirements” section on page 2.

Messaging Ports Will Be Used by Cisco Unity” section on page 5.

Avaya Definity/PBXLink Phone System” section on page 6.

section on page 19.

only for release 3.1(2) and later.) See the “Integrating a Secondary Server for Cisco Unity Failover”

section on page 23.

Corporate Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

Copyright © 2005 Cisco Systems, Inc. All rights reserved.

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

• Bridged mode feature, enabled.

• For each voice messaging port, one analog port connected to the voice cards in the Cisco Unity

• The SMDI port in the PBXLink box connected to a serial port (COM1 is the default) on the

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

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.

server.

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).

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

2

OL-1846-06

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

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.

Integration Description

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.

OL-1846-06

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

3

Integration Description

r

r

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

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

PBXLink box

Phone system

Digital lines
RS-232 serial cable
Analog lines

Cisco Unity serve

55419

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

Add PBXLink

boxes as needed.

PBXLink box #3

PBXLink box #2

PBXLink box #1

Phone system

Digital lines
RS-232 serial cables
Analog lines

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

4

Cisco Unity serve

54394

OL-1846-06

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

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

Call forward to personal greeting

Call forward to busy greeting

Caller ID

Easy message access

Identified subscriber messaging

Message waiting indication

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.

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.

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.

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.

Cisco Unity automatically identifies a subscriber who leaves a
message during a forwarded internal call, based on the extension
from which the call originated.

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.

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.

OL-1846-06

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

5

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.

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

• 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.

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

6

OL-1846-06

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

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.

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

Tes t ? n

Name VoiceMail 2001

LWC Reception? n

LWC Activa t i o n? 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

Programming the Avaya Definity/PBXLink Phone System

(The extension number must appear within the first 16
characters.)

OL-1846-06

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 (Tab l e 3 ).

Table 2 Digital Line Options for All Lines

Option Setting

Extension <the extension number of the digital line>

Type

• 8434D

• 7434D

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

7

Programming the Avaya Definity/PBXLink Phone System

Table 2 Digital Line Options for All Lines (continued)

Option Setting

Port <the physical address of the port>

Data Module? n

Expansion Module? n

LWC Reception None

LWC Activa t i o n? 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

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

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

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

8

OL-1846-06

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

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 Tab le 4, 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>

.
.
.

If there are two PBXLink digital ports and load balancing is used, set the feature button assignments as
shown in both Table 5 and Tabl e 6, then press Enter.

Programming the Avaya Definity/PBXLink Phone System

<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>

.
.

OL-1846-06

If there are three PBXLink digital ports and load balancing is used, set the feature button assignments
as shown in Tab le 7, Table 8, and Tabl e 9, then press Enter.

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

9

Programming the Avaya Definity/PBXLink Phone System

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>

.
.
.

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>

.
.
.

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

<every third remaining 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>

.
.

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.

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

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.

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

Programming the Avaya Definity/PBXLink Phone System

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.

Table 11 Vector Definition Options for a Single Digital Port

Option Setting

Number 1

(must match the Vector Number option in Tab le 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

OL-1846-06

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.

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

11

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

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

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

12

Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 3.1

OL-1846-06