Avaya Definity Gx/PBXLink Integration Guide for
Cisco Unity 4.0
Revised March 31, 2006
This document provides instructions for integrating the phone system with Cisco Unity.
Integration Tasks
Before doing 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 applicable
tasks in the applicable Cisco Unity installation guide.
The following task lists describe the process for creating, changing, and deleting integrations.
Task List to Create the Integration
Use the following task list to set up a new integration with the Avaya Definity/PBXLink phone system.
If you are installing a new Cisco Unity server by using th e applicable Cisco Unity installation guide, you
may have already completed some of the following tasks.
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 6 .
3. Program the Avaya Definity/PBXLink phone system and extensions. See the “Programming the
Avaya Definity/PBXLink Phone System” section on page 8.
4. Install and configure the PBXLink box. See the “Setting Up the PBXLink Box” section on page 17.
5. Create the integration. See the “Creating a New Integration with the A vaya Def inity/PBXLink Phone
System” section on page 29.
6. Test the integration. See the “Testing the Integration” section on page 33.
7. If you have a secondary server for Cisco Unity failover, integrate the secondary server. See the
“Integrating a Secondary Server for Cisco Unity Failover” section on page 37.
Corporate Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Use the following task list to make changes to an integration after it has been created.
1. Start the Cisco Unity Tele phony Integration M anager (UTIM). Se e the “Changing the Settings for
an Existing Integration” section on page 40.
2. Make the changes you want to the existing integration. See the “Changing the Settings for an
Existing Integration” section on page 40.
Task List to Delete an Existing Integration
Use the following task list to remove an existing integration.
1. Start the Cisco Unity Tele phony Integration M anager (UTIM). Se e the “Deleting an Existing
Integration” section on page 41.
2. Delete the existing integration. See the “Deleting an Existing Integration” section on page 41.
Avaya Definity Gx/PBXLink Integration Guide for CiscoUnity 4.0
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
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 ca ble. If multi ple PBXLink box es are in stalled, 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 v alues as
the SMDI port.
We recommend that the serial cable have the following construction:
–
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
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity4.0
2
OL-3105-15
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
• 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, refer to the “Supported C ircuit-Switched Phone
System Integrations” section in your version of Cisco Unity System Requirements at
• A license that enables the applicable number of voice messaging ports.
• An available serial port (COM1 is the default).
Integration Description
The A vaya Def inity/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:
Integration Description
• The extension of the called party
• 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 reason for the forward (the extension is busy, does not answer, or is set to forward all calls)
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 indicato rs (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 6, and to ente r the MWI on and
off codes as described in the “Creating a New Integration with the Avaya Definity/PBXLink Phone
System” section on page 29.
For additional information on the PBXLink box, refer to the PBXLink documentation, which is av ailable
from the manufacturer.
Configuration for 24 or Fewer Ports
A vay a Defi nity/PBXLink inte grations with 2 4 or fe wer ports can use the follo wing conf iguration ( others
are possible):
OL-3105-15
• (Recommended) A single PBXLink-24 box with Port A set for calls only.
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
3
Integration Description
Analog lines
P
PBXLink box
er
Avaya Definity Gx/PBXLink Integration Guide for CiscoUnity 4.0
Configuration for 25 to 48 Ports
Avaya Definity/PBXLink integrations with 25 to 48 ports can use one of the following configurations
(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 one PBXLink-48 box with
Ports A and B set for calls only.
• Two PBXLink-48 boxes with Ports A and Port B of both set for calls only.
• Three PBXLink-24 boxes with Port A of all three set for calls only.
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 1Serial Connections Between a Single PBXLink Box and Cisco Unity
hone system
Digital lines
RS-232 serial cable
Cisco Unity serv
5419
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.
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
4
OL-3105-15
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
Analog lines
P
er
Figure 2Serial Connections Between Multiple PBXLink Boxes and Cisco Unity
Add PBXLink
boxes as needed.
PBXLink box #3
PBXLink box #2
PBXLink box #1
hone systemCisco Unity serv
Digital lines
RS-232 serial cables
Integration Description
Integration Functionality
The Avaya Definity/PBXLink integration with Cisco Unity provides the following integration features:
• Call forward to personal greeting
• Call for ward to busy greeting
• Caller ID
• Easy message acc ess (a subscriber can retrieve messages without entering an ID because
Cisco Unity identifies the subscriber based on the extension from which the call originated; a
password may be required)
• Identified subscriber messaging (Cisco Unity identifies the subscriber who lea ves a message during
a forwarded internal call, based on the extension from which the call originated)
• Message waiting indication (MWI)
Integrations with Multiple Phone Systems
Depending on the version, Cisco Unity can be integrated with two or more phone systems:
• Cisco Unity 4.0 and 4.1 can be integrated with a maximum of two phone systems at one time. For
information on and instructions for integrating Cisco Unity with two phone systems, refer to the
Dual Phone System Integration Guide at
• Cisco Unity 4.2 and later can be integrated with two or more phone systems at one time. For
information on the maximum supported combinations and instructions for integrating Cisco Unity
with multiple phone systems, refer to the Multiple Phone System Integration Guide at
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
5
Avaya Definity Gx/PBXLink Integration Guide for CiscoUnity 4.0
Planning How the Voice Messaging Ports Will Be Used by Cisco Unity
Planning How the Voice Messaging Ports Will Be Used by
Cisco Unity
Before programming the phone system, you ne ed t o pl an how the voice messaging ports will be used b y
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 following table describes the voice messaging port settings in Cisco Unity that can be set in UTIM,
and that are displayed as read-only text on the System > Ports page of the Cisco Unity Administrator.
Table 1Settings for the Voice Messaging Ports
FieldConsiderations
ExtensionEnter the extension for the port as assigned on the phone system.
EnabledCheck this check box to enable the port. The port is enabled during normal operation.
Uncheck this check box to disable the port. When the port is disabled, calls to the port get a
ringing tone but are not answered. Typically, the port is disabled only by t he installer during
testing.
Answer CallsCheck this check box to designate the port for answering calls. These calls can be incoming
calls from unidentified callers or from subscribers.
Message NotificationCheck this check box to designate the port for notifying subscribers of messages. Assign
Message Notification to the least busy ports.
Dialout MWI
(not used by serial or SMDI
integrations)
AMIS Delivery
(available with the AMIS
licensed feature only)
TRAP ConnectionCheck this check box so that subscribers can use the phone as a recording and playback
Check this check box to designate t he port for turning MWIs on and of f. Assign Dialout MWI
to the least busy ports.
Check this check box to designate the port for making outbound AMIS calls to deliver voice
messages from Cisco Unity subscribers to users on another voice messaging system.
Cisco Unity supports the Audio Messaging Interchange Specification (AMIS) protocol,
which provides an analog mechanism for transferring voice messages between different
voice messaging systems.
This setting affects outbound AMIS calls only. All ports are used for incoming AMIS calls.
Because the transmission of outgoing AMIS messages may tie up voice ports for long
periods of time, you may want to adjust the schedule on the Network > AMIS > Schedule
page so that outgoing AMIS calls are placed during closed hours or at times when
Cisco Unity is not processing many calls.
device in Cisco Unity web applications and e-mail clients. Assign TRAP Connection to the
least busy ports.
The Number of Voice Messaging Ports to Install
The number of voice messaging ports to install depends on numerous factors, including:
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
6
OL-3105-15
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
• 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.
• The number of MWIs that will be activated when call traffic is at its peak.
• The number of AMIS delivery calls.
• The number of TRAP connections ne eded when call traffic is at its peak. (TRAP connections are
used by Cisco Unity web applications and e-mail clients to play back and record over the phone.)
• The number of calls that will use the automated attendant and call handlers when call traffic is at its
peak.
It is best to install only the number of voice messag ing ports that are need ed 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 inco ming cal ls from unidenti fied callers or from
subscribers. Typically, the voice messaging ports that answer calls are the busiest.
Planning How the Voice Messaging Ports Will Be Used by Cisco Unity
You can set voice messaging ports to both answer calls and to dial out (for example, to send message
notifications). However, when the voice messaging ports perform more than one function and are very
active (for example, answering man y calls), the other functions may be delayed until the v oice messaging
port is free (for example, message notif icat ions canno t be sent until there are fewer calls to answer). For
best performance, dedicate certain voice messaging ports for only answering incoming calls, and
dedicate other ports for only dialing out. Separating these port functions eliminates 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.
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 outbou nd AMIS cal ls to de liver 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 TRAP 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.
CautionIn programming the phone system, do not send calls to v oice messaging ports in Cisco Unity that cannot
answer calls (voice messaging ports that are not set to Answer Calls). For e xample, if a v o ice mess aging
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 p orts to guid e you in pro gra mmi ng the ph one sy stem .
OL-3105-15
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
7
Avaya Definity Gx/PBXLink Integration Guide for CiscoUnity 4.0
Programming the Avaya Definity/PBXLink 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.
CautionIn programming the phone system, do not send calls to v oice messaging ports in Cisco Unity that cannot
answer calls (voice messaging ports that are not set to Answer Calls). For e xample, if a v o ice mess aging
port is set only to Message Notification, do not send calls to it.
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 can n o t b e a n s w e r e d by C i s c o U n i t y and may cause other problems.
Do the following procedures as applicable.
To Program the Phone System
Step 1Us e 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 2Voice Messaging Port Options
OptionSetting
Extension<the extension number of the voice messaging port>
Type2500
Port<the physical address of the port>
Lock Messages?n
Test?n
NameVoiceMail 2001
(The extension number must appear within the first 16
characters.)
LWC Reception?n
LW C A ct ivation?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 Supervisiony
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
8
OL-3105-15
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
Step 2Us e 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 3) and
button assignments (Table 4).
Table 3Digital Line Options for All Lines
OptionSetting
Extension<the extension number of the d igital l ine>
Type
Port<the physical address of the port>
Data Module?n
Expansion Module?n
LWC ReceptionNone
LW C A ct ivation?y
CDR Privacy?n
Redirect Notification?n
Per Button Ring Control?n
Bridged Call Alerting?n
Active Station RingingSingle
Auto Select Any Idle Appearance? n
Coverage Msg Retrieval?y
Auto AnswerNone
Data Restriction?n
Idle Appearance Preference?n
Restrict Last Appearance?y
Audible Message Waiting?n
Display Client Redirection?n
Select Last Used Appearance?n
Programming the Avaya Definity/PBXLink Phone System
• 8434D
• 7434D
OL-3105-15
Table 4Button Assignments for All Lines
Button AssignmentSetting
1call-appr
2call-appr
3call-appr
4normal
(Use the Normal setting for programming a 7434D phone. Leave the
setting blank for an 8434D phone.)
5inspect
6
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
9
Programming the Avaya Definity/PBXLink Phone System
Table 4Button Assignments for All Lines (continued)
Button AssignmentSetting
7
8
9
10call-appr
Step 3Set the applicable 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 5, then press Enter.
Table 5Feature Button Assignments for a Single PBXLink Digital Port Without Load
Balancing
Feature Button NumberSetting
1abrdg-appr Extn: <1st voice mail extension>
2abrdg-appr Extn: <2nd voice mail extension>
3abrdg-appr Extn: <3rd voice mail extension>
.
.
.
Avaya Definity Gx/PBXLink Integration Guide for CiscoUnity 4.0
<the remaining voice mail extensions>
If there are two PBXLink digital ports and load balancing is used, set the feature button assignments as
shown in both Table 6 and Table 7, then press Enter.
Table 6Feature Button Assignments for First of Two PBXLink Digital Ports with Load
Balancing
Feature Button NumberSetting
1abrdg-appr Extn: <1st voice mail extension>
2abrdg-appr Extn: <3rd voice mail extension>
3abrdg-appr Extn: <5th voice mail extension>
.
<the remaining odd-numbered voice mail extensions>
.
.
Table 7Feature Button Assignments for Second of Two PBXLink Digital Ports with Load
Balancing
Feature Button NumberSetting
1abrdg-appr Extn: <2nd voice mail extension>
2abrdg-appr Extn: <4th voice mail extension>
10
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
OL-3105-15
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
Table 7Feature Button Assignments for Second of Two PBXLink Digital Ports with Load
Balancing (continued)
Feature Button NumberSetting
3abrdg-appr Extn: <6th voice mail extension>
.
.
.
If there are three PBXLink digital ports and load balancing is used, set the feature button assignments
as shown in Table 8, Table 9, and Table 10, then press Enter.
Table 8Feature Button Assignments for First of Three PBXLink Digital Ports with Load
Balancing
Feature Button NumberSetting
1abrdg-appr Extn: <1st voice mail extension>
2abrdg-appr Extn: <4th voice mail extension>
3abrdg-appr Extn: <7th voice mail extension>
.
.
.
Programming the Avaya Definity/PBXLink Phone System
<the remaining even-numbered voice mail extensions>
<every third remaining voice mail extension>
Table 9Feature Button Assignments for Second of Three PBXLink Digital Ports with Load
Balancing
Feature Button NumberSetting
1abrdg-appr Extn: <2nd voice mail extension>
2abrdg-appr Extn: <5th voice mail extension>
3abrdg-appr Extn: <8th voice mail extension>
.
<every third remaining voice mail extension>
.
.
OL-3105-15
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
11
Programming the Avaya Definity/PBXLink Phone System
Table 10Feature Button Assignments for Third of Three PBXLink Digital Ports with Load
Balancing
Feature Button NumberSetting
1abrdg-appr Extn: <3rd voice mail extension>
2abrdg-appr Extn: <6th voice mail extension>
3abrdg-appr Extn: <9th voice mail extension>
.
.
.
If the phone system has 1 to 8 voice messaging ports or if it does not have vectoring capability, do the
procedure “To Set Up Coverage Paths for One to Eight Voice Messaging Ports or for Phone Systems
Without Vectoring Capability.” Otherwise, do the procedure “To Set up Coverage Paths for More Than
Eight Voice M essaging Ports .”
Avaya Definity Gx/PBXLink Integration Guide for CiscoUnity 4.0
<every third remaining voice mail extension>
To Set Up Coverage Paths for One to Eight Voice Messaging Ports or for Phone Systems Without Vectoring
Capability
Step 1Refer to Chapter 6 in the PBXLink documentation, which is available from the manufacturer.
To Set up Coverage Paths for More Than Eight Voice Messaging Ports
Step 1For a phone system with more than eight voice messaging ports, use th e 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 11Vector Direction Number Options
OptionSetting
Extension<the pilot number>
NameVoiceMail 2000
Display Override?n
COR1
Ve ctor Number1
(must match the Number option in Table 12)
Measurednone
12
Step 2Us e 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.
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
OL-3105-15
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
Table 12Vector Definition Options for a Single Digital Port
OptionSetting
Number1
(must match the Vector Number option in Table 11)
Namevoicevec
ASAI Routing?n
Basic?y
Prompting?n
01wait time 0 secs hearing ringback
02route to number 2001 if unconditionally
(use the first voice messaging port extension)
03route to number 2002 if unconditionally
04route to number 2003 if unconditionally
05route to number 2004 if unconditionally
06route to number 2005 if unconditionally
07route to number 2006 if unconditionally
08busy
Programming the Avaya Definity/PBXLink Phone System
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 13Vector Definition Options for Call Vector 1
OptionSetting
Number1
Namevoicevec1
ASAI Routing?n
Basic?y
Prompting?n
01wait time 0 secs hearing ringback
02route to number 2001 if unconditionally
03route to number 2002 if unconditionally
04route to number 2003 if unconditionally
05route to number 2004 if unconditionally
06route to number 2005 if unconditionally
07route to number 2006 if unconditionally
08route to number 2007 if unconditionally
09route to number 2008 if unconditionally
10route to number 2009 if unconditionally
OL-3105-15
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
13
Programming the Avaya Definity/PBXLink Phone System
Table 13Vector Definition Options for Call Vector 1 (continued)
OptionSetting
11route to number 2010 if unconditionally
12goto vector 2 if unconditionally
Table 14Vector Definition Options for Call Vector 2
OptionSetting
Number2
Namevoicevec2
ASAI Routing?n
Basic?y
Prompting?n
01route to number 2011 if unconditionally
02route to number 2012 if unconditionally
03route to number 2013 if unconditionally
04route to number 2014 if unconditionally
05route to number 2015 if unconditionally
06route to number 2016 if unconditionally
07route to number 2017 if unconditionally
08route to number 2018 if unconditionally
09route to number 2019 if unconditionally
10route to number 2020 if unconditionally
11busy
Avaya Definity Gx/PBXLink Integration Guide for CiscoUnity 4.0
14
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 B, and the remaining extensions to Port C.
Table 15Vector Definition Options for Call Vector 1
OptionSetting
Number1
Namevoicevec1
ASAI Routing?n
Basic?y
Prompting?n
01wait time 0 secs hearing ringback
02route to number 2001 if unconditionally
03route to number 2002 if unconditionally
04route to number 2003 if unconditionally
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
OL-3105-15
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
Table 15Vector Definition Options for Call Vector 1 (continued)
OptionSetting
05route to number 2004 if unconditionally
06route to number 2005 if unconditionally
07route to number 2006 if unconditionally
08route to number 2007 if unconditionally
09route to number 2008 if unconditionally
10route to number 2009 if unconditionally
11route to number 2010 if unconditionally
12goto vector 2 if unconditionally
Table 16Vector Definition Options for Call Vector 2
OptionSetting
Number2
Namevoicevec2
ASAI Routing?n
Basic?y
Prompting?n
01route to number 2011 if unconditionally
02route to number 2012 if unconditionally
03route to number 2013 if unconditionally
04route to number 2014 if unconditionally
05route to number 2015 if unconditionally
06route to number 2016 if unconditionally
07route to number 2017 if unconditionally
08route to number 2018 if unconditionally
09route to number 2019 if unconditionally
10route to number 2020 if unconditionally
11goto vector 3 if unconditionally
Programming the Avaya Definity/PBXLink Phone System
OL-3105-15
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
15
Programming the Avaya Definity/PBXLink Phone System
Table 17Vector Definition Options for Call Vector 3
OptionSetting
Number3
Namevoicevec3
ASAI Routing?n
Basic?y
Prompting?n
01route to number 2021 if unconditionally
02route to number 2022 if unconditionally
03route to number 2023 if unconditionally
04route to number 2024 if unconditionally
05route to number 2025 if unconditionally
06route to number 2026 if unconditionally
07route to number 2027 if unconditionally
08route to number 2028 if unconditionally
09route to number 2029 if unconditionally
10route to number 2030 if unconditionally
11busy
Avaya Definity Gx/PBXLink Integration Guide for CiscoUnity 4.0
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 1Use the Change Station (extension number) command to display the Station screen fo r each extensio n.
Step 2In 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 3In the Coverage Path field, enter 1.
NoteYou can use alternate extensions to create multiple line appearances, enable easy message access from
cell phones, and simplify addressing messages to subscribers at different locations in Cisco Unity.
Enabling alternate MWIs lets Cisco Unity turn MWIs on at more than one extension. For details, see the
“Appendix: Using Alternate Extensions and MWIs” section on page 41.
16
Avaya Definity Gx/PBXLink Integration Guide for Cisco Unity 4.0
OL-3105-15
Loading...
+ 36 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.