Definity Octel 100 Configuration Note

Configuration Note 7022
Octel
100
Messaging Server
Avaya Definity Centralized

VoiceMail - IMC
Revised 05/25/01
ISDN Tie Line

Analog Ports
Avaya ProLogix
Telephone
Avaya Magix
ISDN Tie Line

Telephone
Voice Board(s)
Avaya Legend
Inband signaling is used for

integration
Telephone
Personal Computer
1.0
METHOD OF INTEGRATION
Inband signaling is used for integration. Call forward to personal greeting
is achieved via DTMF signals passed from the Avaya ProLogix / G3 to the
Octel 100 system. Message waiting indicators are set and canceled by
dialing a feature access code followed by the extension number. A hookflash followed by the extension transfers the caller to the operator.
Disclaimer: Configuration Notes are designed to be a general guide reflecting AVAYA Inc.s experience
configuring its systems. These notes cannot anticipate every configuration possibility given the inherent
variations in all hardware and software products. Please understand that you may experience a problem
not detailed in a Configuration Note. If so, please notify the TAC/TSO at (408) 922-1822 and if
appropriate we will include it in our next revision. AVAYA Inc. accepts no responsibility for errors or
omissions contained herein.
Avaya
Communications Applications Group
Supported Voice Processing

Modules
Octel 100 Configuration Note (7022)

Avaya Definity Centralized Voice Mail - IMC
Page 2
1.1
SUPPORTED VOICE PROCESSING MODULES
The Octel 100 is a Year 2000 (Y2K) compliant, PC based, enhanced voice
messaging product release intended to replace the Avaya Inc Messaging
2000, OPC, Signature Performer, CEO, CP, and CP+ product lines. For
installed systems that have port capacities above 16 ports contact your
OMD representative for the proper solution.
1.2
Supported PBX Configurations
Confidential
SUPPORTED PBX CONFIGURATIONS
The Avaya Inc Definity G3 Enterprise Communication Server is a state of

the art digital communication Platform with a modular design that grows
with the customers needs. The ProLogix is based on the Definity/CMC
(Compact Modular Cabinet) hardware.
BCS is an offer that has the competencies of G3 such as reliability,
performance, and security; however, it is designed to meet the basic to
midsize telephony market needs. BCS does not support many of the
advanced features of the ProLogix or the Definity G3. For example, DCS
is not available in the BCS Offering.
Definity BCS Issue 4 is based on the R6 software platform. The main
difference between the ProLogix / G3 and BCS is the feature set and the
station circuit packs.
Note: When the local switch communicates with Octel 100 via mode
codes, remote DCS switches are not supported, CVM - Interswitch
Mode Code is supported.
All reference to ProLogix /G3 will include the Definity BCS
unless otherwise noted.
2.0
Ordering Information
O100 ORDERING INFORMATION
There are many options available for this product, depending on the
application. Voice Boards supported:
<
<
<
Voice Boards supported:

Dialogic DIALOG/4
Optional Fax Boards supported:
Brooktrout TruFax 200
Optional Remote Service
Internal Modem
Please consult with your sales representative.
This integration will support 16

ports
ProLogix / ECS Hardware
Requirements
2.1
VOICEMAIL PORTS SUPPORT
The standard configuration for this integration is 16 ports maximum.
AVAYA ProLogix / ECS HARDWARE REQUIREMENTS
Note: See Sections 7.4 and 7.6. The necessary hardware must be
provided by the customer. Also, verify that the system has enough
DTMF registers for Inband applications.
The information contained in this document is provided by AVAYA Inc. to serve as a guide. See the
disclaimer on page 1
Avaya Inc. PROPRIETARY. Use pursuant to Company instructions.
Avaya

Page 3
One analog port (TN742-8 circuits, TN746B-16 circuits, TN7698 circuits, TN793-24 circuits, and TN2183-16 circuits)
configured as a VMI set for each Octel 100 port.
For Definity BCS analog ports (TN791-16circuits, TN221516cicuits, and TN2793-24 circuits) configured as a VMI set for
each Octel 100 Port.
All line circuits supports LED message waiting indicators
(message waiting indicators are not supported off-premises).
Neon message waiting indicators are support by TN769, TN793,
and TN2793 along with a TN755B Power Unit per carrier or per
Single-Carrier Cabinet.
<
<
<
<
PBX Software Requirements
Confidential
3.1
PBX SOFTWARE REQUIREMENTS
DEFINITY hub (not DEFINITY ONE or GuestWorks). Options are:
<
DEFINITY ECS R8
CVM - Interswitch Mode Code (IMC) RTU for each switch
in the network.
<
<
<
UDP RTU and ISDN RTU software required.
DEFINITY ProLogix R3 (or later)

CVM - Interswitch Mode Code (IMC) RTU for each switch
in the network.
<
<
<
UDP and ISDN RTU software required.
DEFINITY BCS Issue 6 (or later)

CVM and Inter switch Mode Code (IMC) Software on each
switch in the network.
<
<
<
UDP and ISDN software required.
MERLIN MAGIX R1.0 (or later)

UDP, ISDN, and CVM-IMC software required (Standard).
<
<
MERLIN LEGEND R6.1 or R7.0

UDP, ISDN, and CVM-IMC software required (Standard).
<
NorTel Meridian I (Programming not shown)

Need all Option 11C (or larger) for CVM
<
<
NEC (Programming not shown)

Remote Shelf (Remote Carrier) for CVM
<
<
Mitel (Programming not shown)

Remote Shelf (Remote Carrier) for CVM
<
<
Additional Material Requirements
3.2
ADDITIONAL MATERIAL REQUIREMENTS
The board used to interface Octel 100-voice mail is a four-port board.
System configurations may reflect partial use of a board. The board used
to interface Octel 100-fax reception and retrieval is a two-port board.
<
If using the DIALOG/4 you will need:
Avaya

Supported Integration Features
<
<
One RJ-14 jack with 4-conductor line cord for every two
ports
If FaxMail is installed:
One analog line per fax port.
One RJ-11 jack for every Brooktrout TruFax 200 fax port
with 4-conductor modular telephone cords.
SUPPORTED FEATURES
[] Items are supported

System Forward to Personal Greeting
All Calls
Ring/no answer
Busy
Busy/No Answer
Do Not Disturb
Station Forward to Personal Greeting
All Calls
Ring/no answer
Busy
Busy/No Answer
Do Not Disturb
Flexible Forwarding
Forward to No Answer Greeting
Forward to Busy Greeting
Intercom/CO Forwarding
Message Waiting
LCD Display
LED
Lamp
1
Audible / Stutter Dial Tone
1
Page 4
One analog line for remote service access

One RJ-11 jack for above, and a 2-conductor modular
telephone cord
4.0
Confidential
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Multiple Return to Operator

Direct Call
Auto Attendant
Outcalling
Personal Greeting of Original-Called Party
Multiple Call Forward
Double Call Forward
Call Coverage
Intercom Paging
2
Supervised Transfers
Call Screening
Call Queuing
Intercom Paging
Identify Calling Party
System Forward to Personal Greeting
Station Forward to Personal Greeting
Flexible Forwarding (NA with CO)
3
Record Telephone Conversation
2
See Section 7.2

See Section 7.
ProLogix / G3 must have audible MWI activated
4.1
DISCONNECT TYPE
The ProLogix / G3 disconnects by interrupting the loop current (removing
battery) for 900 ms upon receiving disconnect from the central office or an
internal station. Use Adjunct Supervision? y, when configuring the
single-line Octel 100 ports. For proper external disconnect supervision for
the ProLogix / G3, Ground start or Supervised (Reliable Disconnect) Loop
start CO lines are recommended.
Programming Avaya ProLogix /

G3 system parameters
5.0
CONFIGURING THE AVAYA PROLOGIX / G3
Before you begin programming, it is recommended that a hard copy of the
customer database be obtained to verify existing programming.
<
4-digit dial plan in DEFINITY/MERLIN private network
<
4- or 5-digit dial plan in all-DEFINITY (not both at same time)
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Avaya
Entries in bold italic type indicate

where information must be
entered.

Confidential
Page 5
Refer to the Programming section in the appropriate manual for

information on entering, saving, and exiting database programming. The
tasks below must be completed when programming the ProLogix / G3 for
integration. They are as follows:
Enable Mode Code integration
Verify Feature Access codes
Configure the single-line Octel 100 ports
Program a hunt group for call coverage
Using the ADD HUNT-GROUP command, create a hunt group
Create call coverage path(s) that include the hunt group access
number
Change subscriber's station programming to include call
coverage path
In the following example, a four port Voice Mail system is used. Specific
extension numbers are used for the Octel 100 analog lines and subscriber
stations. A sample coverage path is shown.. The example assumes:
<
<
<
<
<
<
<
<
<
<
The Octel 100 analog ports are extensions 5001, 5002, 5003, and
5004
Hunt group number 5000
Extensions 2345, 3001 and 3002 are Voice Mail Subscribers.
Coverage Path number 1 is the example shown.
5.1
ENABLE MODE CODE INTEGRATION
Note: The ProLogix / G3 configuration uses only mode code
integration.
SYSTEM PARAMETERS CUSTOMER-OPTIONS
This screen allows access to features purchased by customers. An
authorized Avaya Inc representative sets these parameters for you.
Use the switchs Customer Options form to enable mode code integration.
Proceed as follows:
1. Enter the command: display system-parameters customer-options
and make sure the G3 Version (on the first line) is set to V6.
2. Change to page 2.
3. Check that Mode Code Interface? field on this screen is set to y.
Note: This field will reflect no on the default translation card that is
shipped with Definity BCS. The technician will need to call the
DDM Dealer Care Center at 800-225-0266 ext. 00234 in order to
have the mode code interface set to y.
Avaya

Confidential
Page 6
display system-parameters customer-options
system-parameters customer-options
Page 2 of 4
The following programming instruction can be used to change the indicated feature
to the proper value:
1 Enter change system-parameters customer-options on the
command line of your system administration screen.
2 on page 3, verify fields as follows:
~ ISDN-PRI field is y.
~ Mode Code for Centralized Voice Mail? Field is y.
~ Mode Code Interface? Field is y.
~ UDP field is y.
5.2
CREATE TIE TRUNK GROUP FOR REMOTE SWITCH
On the hub switch, enter add trunk group xxxx on the command line of
your system administration screen, where xxxx is the number of the ISDNPRI trunk group connecting the hub with the remote switch.
On page 1, verify fields as follows:

Group Type field is ISDN.
Service Type field is TIE.
<
<
On page 2, verify fields as follows:

<
Send Name field is y.
Avaya

<
<
<
Verify Feature Access codes
Confidential
Page 7
Send Calling Number field is y.

Numbering Format field is Private.
Send Connected Number field is y.
5.2
Feature Access Code (FAC) form
Verify the Feature Access codes used for Leave Word Calling Send A
Message and Leave Word Calling Cancel A Message.
1. Enter the command: display feature-access-code.

3. Check Leave Word Calling Send A Message, if this field is
blank, it is
suggested #90 be used.
4. Check Leave Word Calling Cancel A Message, if this field
is blank, it is
suggested #4 be used.
Page 2 of 5
FEATURE ACCESS CODE (FAC)
Group Control Restrict Activation: ____ Deactivation: ____
Hunt Group Busy Activation: ____ Deactivation: ____
ISDN/PRI Access Code: ____
Last Number Dialed Access Code: ____
Leave Word Calling Message Retrieval Lock: ____
Leave Word Calling Message Retrieval Unlock: ____
Leave Word Calling Send a Message: _#90_
Leave Word Calling Cancel a Message: _#4__
Malicious Call Trace Activation: ____ Deactivation: ____
PASTE (Display PBX data on Phone) Access Code: ____
Personal Station Access (PSA) Associate Code:
Dissociate Code:
Print Messages Access Code: ____
Priority Calling Access Code: ____
Program Access Code: ____
Refresh Terminal Parameters Access Code: ____
Send All Calls Activation: ____ Deactivation: ____
Take note of the digits that must be dialed to allow coverage to transfer the
caller to the original call recipients Octel 100 mail box where the caller
Avaya
Entries in bold italic type

indicate where information
must be entered.

Page 8
Confidential
can leave a message. The default is blank. Section 5.4 defines this
number.
2. Check Transfer to AUDIX Access Code:.
Page 3 of 5
FEATURE ACCESS CODE (FAC)
Station Security Code Change Access Code: ____
Terminal Dial-up Test Access Code: ____
Terminal Translation Initialization Merge Code: ____ Separation Code: ____
Transfer to AUDIX Access Code: ____
Trunk Answer Any Station Access Code: ____
User Control Restrict Activation: ____ Deactivation: ____
Voice Coverage Message Retrieval Access Code: ____
Voice Principal Message Retrieval Access Code: ____
5.3 CONFIGURING THE SINGLE LINE AVAYA OCTEL 100

PORTS
Define analog voice ports that will connect to the Octel 100 using the
ADD STATION command. Sequential numbering is recommended.
Repeat for each analog port.
Administer each analog port as station type VMI but exactly as if it were a
model 2500 station. Follow these steps:
Add Station 5001
add station 5001
Page 1 of 3
STATION
BCC: 0
Lock Messages? n
Security Code:
Extension: 5001
Type: VMI
Port: 01A0304
Name: VOICEMAIL
Tests? N
STATION OPTIONS
Off Premise Station? n
TN: 1
COR 2
COS 1
Next
add station 5001
Page 2 of 3
STATION
FEATURE OPTIONS
LWC Reception:
LWC Activation?
CDR Privacy?
Redirect Notification?
Per Button Ring Control?
Bridge Call Alerting?
Switchhook Flash?
Ignore Rotary Digits?
H.320 Conversion?
none
y
n
n
n
n
y
n
n
Coverage Msg Retrieval?

Auto Answer?
Data Restriction?
Call Waiting Indication?
Att. Call Waiting Indication?
Distinctive Audible Alert?
Adjunct Supervision?
n
none
y
n
n
n
y
Audible Message Waiting? n

Avaya

Page 9
Confidential
Next
Entries in bold italic type indicate
where information must be
entered.
add station 5001
Page 3 of 3
STATION
SITE DATA
Room:
Headset? n
Jack:
Speaker? n
Cable:
Mounting: d
Floor:
Cord length: 0
Building:
Set Color:
ABBREVIATED DIALING
List1:
List2:
List3:
HOT LINE DESTINATION
Abbreviated Dialing List Number (From above 1, 2 or 3):
Dial Code:
Line Appearance: call-appr
Enter
Assign the Hunt Group
5.4
ASSIGN THE HUNT GROUP
You must identify each Avaya Octel 100 voice port as a member of a hunt
group. See the appropriate switch documentation for more information
about call distribution groups. Use the following procedure to place the
voice ports into a hunt group starting with port 1:
1. Enter add hunt-group <hunt group number> at the enter command
prompt on the SAT.
You also can enter add hunt-group next to add a hunt group with a
number that is one higher than the previous hunt group.
ADD HUNT-GROUP 11
Add hunt-group 11
Page 1 of 6
HUNT GROUP
Group Name: Avaya Inc Octel 100

Group Number: 11
Group Extension: 5000
Queue? y
Security Code:
ISDN Caller Disp: grp-name1
Group Type: ucd

ACD? n
Vector? n
COR: 1
TN: 1
Queue Length: 4
Calls Warning Threshold:
Time Warning Threshold:
Calls Warning Port:

Time Warning Port:
Enter grp-name (use name specific to site) to specify the hunt group
name be sent to the originating user. This field is required when the
ISDN-PRI option on the switch System-Parameters Customer-Options
screen is enabled.
Avaya

Confidential
Add hunt-group 11
Page 10
Page 2 of 6
HUNT GROUP
Message Center: none
LWC Reception: none

AUDIX Name:
Messaging Server Name:
Next
Add hunt-group 11
Page 3 of 6
HUNT GROUP
Group Number: 11
ucd
Group Extension: 5000
Member Range Allowed: 1 - 999

/4
Group Type:
Administered Members (min/max): 1

Total Administered Members: 4
GROUP MEMBER ASSIGNMENTS

Ext
Name
Ext
Name
1: 5001 VOICEMAIL
14:
2: 5002 VOICEMAIL
15:
3: 5003 VOICEMAIL
16:
4: 5004 VOICEMAIL
17:
5:
18:
6:
19:
7:
20:
8:
21:
9:
22:
10:
23:
11:
24:
12:
25:
13:
26:
Ext
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
Name
At End of Member List
5.5
CONFIGURING THE SUBSCRIBER COVERAGE PATH
Entries in bold italic type indicate where information must be entered.
Avaya

Page 11
Confidential
All extensions that are to use the Octel 100 message server for call
coverage must be assigned a coverage path that includes the Octel 100
message server as a coverage point. This may require the addition of new
coverage paths as well as the modification of existing coverage paths.
Configuring Digital
Subscriber Stations
Add coverage path 1

add coverage path 1
Page 1 of 1
COVERAGE PATH
Coverage Path Number: 1
Next Path Number:

COVERAGE CRITERIA
Station/Group Status
Active?
Busy?
Don't Answer?
All?
DND/SAC/Goto Cover?
Linkage
Inside Call Outside Call
n
n
y
y
y
y Number of Rings:3
n
n
y
y
COVERAGE POINTS
Terminate to Coverage Pts. with Bridged Appearances? n
Point1:
11
Point2:
Point3:
Point4:
Point5:
Point6:
Enter
Note: Refer to Section 7.2 before setting up call coverage.
Configuring Single Line

Subscriber Stations
5.6
CONFIGURING THE SUBSCRIBER STATIONS
This programming is done using the administrator terminal.
3001
STATION
Extension: 3001
Type: 2500
Port: ____
Name: John Smith, 3001
STATION OPTIONS
Off Premise Station? n
Lock Messages? n
Security Code:
Coverage Path: 1
Coverage Path: 2:
Hunt-to Station:
Page 1 of 2
BCC
TN
COR
COS
Tests?
___0
___1
___1
___1
y
Message Waiting Indicator: led
(Page 2 is not shown as no specific programming is required.)

Avaya

Confidential
Page 12
Change Station 3002

Page 1 of 4
STATION
Extension: 3002
Type: 7405D
Port: ____
Name: Stevnsn.HL.3002
Lock Messages? n
Security Code:
Coverage Path 1: 1
TN:
COR:
STATION OPTIONS
Data Module? n
Display Module? y
Message Lamp Ext:

Restrict Last Appearance? y
Feature Module?: n
Coverage Module? N
mm Complex Data Ext:
(Pages 2-4 are not shown as no specific programming is required.)

5.7
SET SYSTEM PARAMETERS
Seven system parameters determine how the system will send mode codes.
These are the four mode codes themselves (in the form of touch-tone
signals) and three time durations associated with their transmissions.
These options must match the transmission qualities of your integrated
voice messaging system. Furthermore, the default entries must match the
Octel 100 defaults. For these reasons, do not change the parameters from
their default settings, unless necessary to meet pre-existing dial plans
settings.
Enter change system-parameters - mode codes
MODE CODE RELATED SYSTEM PARAMETERS
MODE CODES (FROM SWITCH TO VMS)
Direct Inside Access
#00
Direct Dial Access - Trunk
#01
Internal Coverage
#02
External Coverage
#03
OTHER RELATED PARAMETERS
DTMF DURATION ON(msec): 100
OFF(msec): 100
Sending Delay(msec): 100
5.8
AUTOMATED ATTENDANT ADMINISTRATION
Automated attendant provides the caller with a menu of options. The caller
can request a department or extension by pressing a touch-tone key. For
each main attendant, assign a hunt group with a queue equal to the trunks
that feed the attendant, or assign a new hunt group that forwards calls to
the Octel 100-hunt group.
Avaya

Confidential
Page 13
Assign a Station
You can assign a station on the switch for each main attendant. The station
requires a physical port on the switch. A physical voice terminal is not
required. However, if a voice terminal is not attached to the port, the
switch generates a minor alarm. Use the following procedure to assign a
station for a main attendant.
1. Assign a station for the type of available port.
2. Assign the station extension as the incoming destination for the
incoming call trunk groups that will be served by the automated
attendant. If you are not using the automated attendant as an incoming
destination for a trunk group, skip this step and continue with step 3,
and confirm that the Auth Code field is set to n.
3. From the attendant console or administrative voice terminal, activate
Call Forwarding All Calls for the automated attendant extension.
Make the destination the Octel 100 hunt group extension.
Assign a Hunt Group
Assign a new hunt group for the automated attendant if there is not a
physical port available on the switch for a station. The hunt group
forwards calls to the Octel 100 hunt group. Use the following procedure to
assign a hunt group for the automated attendant.
1. Enter add hunt group < hunt group number> on the switch
administration terminal.
2. Set Group Name: to a name that contains the group extension. Use
the group extension as all or part of the group name.
3. Set Group Extension: to the automated attendant extension.
4. Set Group Type: to ucd.
5. Leave the Coverage Path field blank. All calls are forwarded to the
Octel 100 hunt group extension.
6. Set the other fields according to the customer requirements.
7. Set Queue? to y.
8. Assign the numbers of all trunks to the hunt group.
9. Press Enter.
10. Assign the automated attendant group extension as the incoming
destination for incoming call trunk groups served by the automated
attendant.
If you are not using the automated attendant as an incoming
Avaya

Confidential
Page 14
destination for a trunk group, skip this step and continue with Step 11.
Set Auth Code to n.
11. At the attendant console, activate Call Forwarding All Calls for the
automated attendant. Set the destination as the Octel 100 hunt group
extension.
5.9
NIGHT SERVICE TO AUTOMATED ATTENDANT

ADMINISTRATION
You can set up night service to an automated attendant from an incoming
trunk or from a Listed Directory Number (LDN).
From an Incoming Trunk
Use the following procedure to set up night service to an automated
attendant from an incoming trunk.
1. Assign the night automated attendant extension or hunt group number
to the Night Service field on the trunk group form. The nightautomated attendant receives all incoming calls when you activate
night service.
2. Activate Call Forwarding All Calls for the night automated attendant
extension or hunt group number. Set the destination as the Octel 100
hunt group extension.
While the console is in day service mode, calls route as usual according to
the incoming destination on the trunk group form. When the console is
placed in night service mode, calls route according to the night automated
attendant destination identified in the Night Service field.
5.10 FROM A LISTED DIRECTORY NUMBER (LDN)
Use the following procedure to set up night service to an automated
attendant from an LDN.
1. Assign one or more unique extensions on the Listed Directory
Numbers
(LDN) screen. These extensions cannot exist elsewhere in the switch.
For example, assign 1000 as the LDN.
2. For each extension assigned in step 1, assign a name that includes the
night automated attendant extension or hunt group number as part of
the
name. For example, if the night AA number or hunt group number is
1001, use the name night1001.
3. Assign the Octel 100 hunt group extension in the Night Destination
field. From the examples above, this number would be 1001.
Avaya

Confidential
Page 15
When you place the attendant console in day service mode, the LDN acts
as
usual. When you place the attendant console in night service mode, the
system sends calls to the Octel 100 hunt group extension. The Octel 100
system answers calls using the automated attendant that corresponds to the
number in the LDN Name field.
5.11 UNIFORM DIAL PLAN
A unique four- or five-digit number assigned to each station on the
network.
Uniform numbering gives each station a unique number (location code
plus
extension) that can be used at any location in the Electronic Tandem
Network to access that station. DEFINITY ECS enhances the standard
uniform dial plan with the unrestricted 5-digit uniform dial play, which
allows up to five digits to be parsed for call routing.
Enter change dialplan on the command line of your system administration
screen. Usually the hub is considered Node 1.
If the network contains Merlin Legend/Magix systems:
Uniform Dialing Plan field is 4 for each node.
If the network contains only DEFINITY systems:
Uniform Dialing Plan field is 4 or 5.
<
<
In the above example, First digits 1,3,and 5 are used in the Host switch. Digit
2 will be for switch number two and digit 4 will be used in switch number 3.
Avaya
Programming Avaya Merlin

Magix / Legend system
parameters

Confidential
Page 16
5.12 CONFIGURING THE AVAYA MERLIN MAGIX / LEGEND

Before you begin programming, it is recommended that a hard copy of the
customer database be obtained to verify existing programming.
Note: Assignment of extensions has two elements, Send and Receive. As
a Sender, an extension can only be assigned to either an extension or a
group. As a Receiver, an extension can be assigned in multiple groups.
An extension number, once assigned to a Calling Group or Line/Pool, is
committed as a Sender. This extension, however, can be used as a
Receiver in other groups.
5.13
AVAYA MERLIN MAGIX / LEGEND SYSTEM

PROGRAMMING
Refer to the Programming section in the Avaya Merlin Magix / Legend
manual for information on entering, saving, and exiting database
programming.
The Magix / Legend system must be configured as a hybrid/PBX. This
programming must be done when the system is idle. In addition, this
programming will cause the system to restart when you are finished.
Therefore, choose an appropriate time for this procedure.
From the System Programming Menu
Select
System
Select
Mode
Select
Hybrid/PBX
Avaya

Confidential
Page 17
Press <Enter> to save.

At this point, the system will restart as noted above. To continue
programming, re-enter system programming.
Program the Voice Mail System/Automated Attendant Options as follows:
Select
AuxEquip
Select
VMS/AA
From the VMS/AA screen, select TransferRtn. This parameter, Transfer
Return, represents the number of rings before calls transferred by the Octel
100 are sent to a designated backup position. Set it to "0" to disable this
feature. If supervised transfers are used, this parameter should either be
disabled or set higher than the Max rings in the Mailbox Class of Service.
The default value for Transfer Return is 4. To modify this parameter, erase
the current setting, using the Drop key. Enter the desired value and press
Enter.
From the VMS/AA screen, select TT Duration. This parameter should be
set to 75 (milliseconds). If it is not, erase the current setting, using the
Drop key and enter 75. Press Enter to save your entry.
From the VMS/AA screen, select TT Interval. This parameter should be
set to 50 (milliseconds). If it is not, erase the current setting, using the
Drop key and enter 50. Press Enter to save your entry.
Press Exit twice to return to the System Programming menu.
5.14 CONFIGURING THE OCTEL 100 PORTS
Create Calling Group for Octel 100
Select
Extensions
Press More to display second page
Select
Group Calling
Select
Hunt Type
Enter the extension number to be assigned to the Calling Group
Select
Circular
Select
Exit
Return to Group Calling Menu
Select
Members
Enter extension number of Octel 100 group in the Host PBX.
Select Enter
Note: An Overture port can only belong to one calling group. A QCC
cannot be a member of a calling group.
At Enter Group Members Prompt:
Avaya

Confidential
Page 18
Specify first Octel 100 extension number In host PBX.

Select
Exit
Return to Group Calling Menu
Set up Group Type for Octel 100 calling group (this instructs Magix /
Legend to send mailbox ID information)
Select
Group Type
Enter extension number of the Octel 100 calling group in Host PBX
Press Enter
Select
Integ VMI
Press Enter to Save
Press Enter twice to return to Extensions Menu
Program Octel 100 as the Call Coverage target
Select
Group Coverage
Enter a number (1 - 30) as coverage group number for Octel 100

When prompted for extension numbers, enter extension number assigned
to Octel 100 calling group
Press Enter to Save
Press Enter twice to return to System Programming Menu
Program Group Coverage Delay Interval
Select
Options
Select
Group Coverage Delay Interval
Select
Number of Rings (1 - 9
Press Enter to Save
To assign trunks to ring directly to Octel 100
Select
Extensions
Select
Group Calling
Select
Line/Pool
(See Note: Section 7.3)
Enter Octel 100 calling group extension number
Press Enter
At "Enter Line/Pool numbers" prompt identify line or pool of lines you
want Octel 100 to answer
Note: Incoming calls on each line/trunk or pool can be directed to only
one calling group.
Avaya

Confidential
Page 19
5.15 CONFIGURING THE SUBSCRIBER STATIONS

Set up a coverage group for extending call to Octel 100
Select
System Programming
Select
Extensions
Select
Group Cover
Enter Group Number (extension assigned to the Octel 100 Calling Group)
Select
Enter
Dial Extension Number
Select
Enter
Repeat until all subscriber extensions have been added
Press exit twice
Select
System Programming
Select
Options
Select
Cover Delay
Dial number of rings
Select
Enter
Select
Exit
5.16 SWITCH INBAND DIGIT PLAN
The following table shows the digit patterns that could be sent from the
ProLogix / G3.
Example: Calling number = 123 / Called number = 456
Function
AutoLogon
Direct Call from a Trunk
ProLogix / G3 Inband
#00#5678##
#01#5678##
#01#3###03##2811#
Internal Call Coverage
#02#1234#5678#
02#2862#2833#
#02##2465#
Operator handled call
External Call Coverage
#02#0#5678#
#03##5678#
Switch Day
Switch Night
03##8677#
03##2878##
03##293#03##2905#
#11###
#12###
Avaya
Integration for Avaya Octel 100

Avaya Octel 100 Configuration

Page 20
Confidential
6.0
CONFIGURATION OF THE AVAYA OCTEL 100
Sections 6.1 show the integration codes that should already be configured for
your switch. Setup sections may be checked to verify that this is done.
Starting with Octel 100 Version 3.2 build 10, if the Integrator program is run for,
North American Sites select the Avaya Definity with CVM switch. If you are
installing an earlier version of Octel 100 you can contact Technical Support and
they can down load the files required or assist in your retrieving the proper files
form the Support Online Web site.
6.1
INTEGRATION FOR AVAYA OCTEL 100
Switch settings:
Outside Line Access Code
9,
Hook Flash Interval (FLINTVL)
65
DTMF Tone Length (TONELEN)
8
Transfer, Paging and Screening Parameters:
Custom Transfer Code
Intercom Paging Code
B&W5RXDR
&W5RC3799N
These Codes apply to the Transfer Codes and the Init String:
B = Supervisor for Busy tone
W = Wait for Dialtone x seconds
x = 1 - 9 seconds / = 0 wait 60
R = use release Code and treats call as busy
Transfer, Paging and Screening Parameters:
Transfer Release Code when Busy
Transfer Release Code when No Answer
Call Screening Release Code when Busy
Call Screening Release Code when No Answer
Call Screening Release Code when Reject
Call Screening Release Code When Transfer
Release Code for Intercom Paging
Flash Time Interval (FLINTVL)
&,&
&,&
&,&
&,&
&,&
&,&
&,&
65
Message Waiting Parameters
Permit Message Waiting Lights

Message Waiting Light Prefix ON
#90
Message Waiting Light Prefix OFF
#4
Turn message Waiting light on for every Message
Check for new message when exiting VoiceMail

Note: See section 5.2 and verify MWL ON and OFF Codes.
Inband Parameters
Total Number of DID Digits (DIDCOUNT)
DID Terminating Character (DIDTERM)
Seconds to Wait for First Digit (DIDTIME)
Millisecs to Wait for Next Digit
Off Hook Delay (OFFHDLY)
16
*
4
500
15
Avaya

Inband Templates
#00#R##
00#R
00#R##
#02#S#R#
#02#XXX#R#
#02#XXXX#R#
#02#?#R#
#03##R#
#0X##R#
0X##R#
0X##R##
0X#S#R#
0X#XXXX#R#
0X##XXX#0X##R#
#0X#X###0X##R#
#11###
#12###
Page 21
Confidential
Auto Login
Auto Login
Auto Login
Go to Voice Mail
Go To VoiceMail
Go To VoiceMail
Go to Voice Mail
Go to Voice Mail
Go To VoiceMail
Go To VoiceMail
Go To VoiceMail
Go To VoiceMail
Go To VoiceMail
Go To VoiceMail
Go To VoiceMail
Go To VM Get MB
Go To VM Get MB
These Codes apply to the Inband Template:

R = Receiving Mailbox
S = Sending Mailbox
X = Ignore Character
Valid Characters are:
~ $ * # 0-9 A-D F N T
Note: Verify all these dialing sequences for your switch
Avaya ProLogix / G3 unique

consideration
6.2
AVAYA PROLOGIX / G3 UNIQUE CONSIDERATION
Prior to completing the installation and restarting the PC: run the SETUP
program by clicking on the Setup Icon in the Octel folder. The following
parameters should be checked and changed to match the defaults of the
Avaya ProLogix / G3 as required:
Suggested Value-1 Defaults: Octel 100-2 ProLogix / G3 -3
Port Parameters
General Parameters
Number of Digits in a Mailbox
Operator Parameters
Default Operator Mailbox Number
After Hours Operator Mailbox Number
100 1000
100 1000
Subscriber Parameters
Enable Confirmation of Deleted Messages
Consecutive Login Failures before Lock-Out
NO
3
100
100
YES
0
PORT PARAMETERS
Outbound ports are required to be made available to the Octel 100 to
complete internal application such as forwarding of messages form one
mail box to another. Message Indicators will be maintained from the host
to satellite switches. Access to the tie trunks is required. Message
Avaya
Check this section before

completing the installation and
restarting the PC.

Confidential
Page 22
delivery and fax delivery and message networking require external access
for proper functionality. Two examples are shown as a guide for assigning
the outbound usage permitted parameter.
4-port system - Example 1
6-port system - Example 2 Example 1 Example 2
Port Parameters
Port Number 1 2 3 4
1 2 3 4 5 6
Init Node N N N N N N N N N N
Ring Count 1 1 1 1
1 1 1 1 1 1
Inbound
Outbound
Outbound Usage Permitted

Msg Delivery
Msg Indicator
AMIS/OctelNet
Fax
Applications
4-port system Dedicate the last port for external access.

6-port system Dedicate the last two ports for external access.
8-port system Dedicate the last tree ports for external access.
12-and 16- port Dedicate the last four ports for external access.
systems
Note: Use this as a guide when performing the switch administration
function shown in Section 5.3.
Mail Box Class of Service Setup

Do this section before building
mailbox database.
6.3
MAIL BOX CLASS OF SERVICE SETUP
Note: Before Building the Octel 100 mailbox database make the
changes shown in this section.
On the Octel 100 change the value for Max rings from 5 to 0. The Octel
100 will not supervise a call transferred form the Auto Attendant. With
the Octel 100 in the System Manager mode perform the following:
Enter
Alt-O
for Options
Enter
C
Class Of Service
Start with Class of Service 1
Go To
Max Rings
Default is 5, change to 0.
Enter
Alt-N
For next
For the Message Changes have been made. Save Changes?
Enter
YES
to save change and step to next
COS.
Continue for all Class of Services that are used.
Press
Exit
to exit and return to the main
screen.
Avaya

7.0
Confidential
Page 23
CONSIDERATIONS / ALTERNATIVES
The following items should be considered:

Unsupervised Transfers
Supervised Transfers
Leave Word Calling
Hardware Compatibility
Octel 100 compatibility with the DCS Option.
Octel 100 ports should be distributed.
<
<
<
<
<
<
7.1
UNSUPERVISED TRANSFERS
The ProLogix / G3 does not support unsupervised transfers to busy

stations without busy-call coverage programming. The Octel 100 system
has been enhanced to perform this function. The Octel 100 system will
pull a busy call back and return the caller with the busy prompt. For this
to function, Call Coverage Busy should be set to no in section 5.5
configuring the Subscriber Coverage Path.
7.2
Important notes concerning this
integration
SUPERVISED TRANSFERS
When the Octel 100 system is programmed to perform a supervised transfer for
busy calls and blind transfer, subscriber phones should Ring-No-Answer
forward to VoiceMail only. Set the ProLogix / G3 ring timer to allow for more
rings than the Max Rings setting in the Mailbox Class of Service. Internal
calls will encounter a busy signal when the line is busy. Ring No Answer calls
will forward to the personal greeting. For this to function, Call Coverage Busy
should be set to no in Section 5.5 Configuring the Subscriber Coverage
Path. For proper forwarding of DID calls and tie trunks, external Busy Call
coverage should be set to yes.
If the Octel 100 is programmed to execute a supervised transfer, Hands-free
Announce must be disabled.
Mailboxes used for supervised transfers must have the Class of Service Max
Rings setting of 3 or higher. This may be set in the Edit MailBox window by
making the class of service for one mail box number 0 and using a custom
class of service. Supervised transfers will allow a subscriber to use Octel 100
features that are normally reserved for users in the PARTNER. These
features are Intercom Paging, Call Screening, and Call Queuing.
Subscribers utilizing supervised transfer must agree to the following station
considerations:
Analog single line Subscribers:
Do not assign call coverage to the station. Internal calls to the
station should return busy and internal callers will be required to
log-into their Octel 100 mail box and send messages to the
subscriber.
Avaya

Confidential
Page 24
Multiline Subscribers:
May continue to have coverage, calls to these subscribers will rarely
encounter a busy extension. Coverage Delay should be changed so
that the number of rings (Section 5.3) at the station is greater then
the Octel 100 class of service Max Ring value (Section 6.4.)
7.3
LEAVE WORD CALLING
Note: See section 5.2 and verify MWL ON and OFF Codes.
Leave Word Calling (LWC) provides message notification. If the LWC
feature is being used by the Octel 100 system and other sources (that is,
message centers and station users). Then users without display terminals
must contact their designated message retrievers to determine the source of
their message-waiting lights.
The message return feature cannot be used to retrieve messages when
vectoring is in use. For ease of use, create a speed call number to be used to
retrieve messages. Assign this speed call number to a feature button on the
telephone.
We recommend that only the Octel 100 system be allowed LWC
activation. This will prevent single line telephones from having their
message waiting lamps lit when there are no new messages.
CAUTION: Users with display terminals must not delete any Octel 100
messages on their display. This allows the Octel 100 system
to turn off the message-waiting light when voice messages
are reviewed.
7.4
HARDWARE COMPATIBILITY
Check the availability of analog ports in the ProLogix / G3. The TN746
analog card is a -24v circuit card, which is not supported by Avaya Inc
Octel 100. The Octel 100 port requires a -48v circuit. The ProLogix/G3
can use the TN742, TN746B, TN793, and TN2183 analog circuit packs.
The Definity BCS can use the TN791, TN2215 and TN2793 analog circuit
packs in addition to the above ProLogix / G3 packs.
7.5 AVAYA MODE CODE CONSIDERATIONS:
Avaya Mode Code
Considerations:
Definity BCS does not support the DCS feature. When the local switch
communicates with Octel 100 via mode codes, remote DCS switches are
not supported.
CVM - Interswitch Mode Code is supported. A Definity must be used as a
Host for the Octel 100. Remote sites may be Definity, Merlin Legend /
Magix, NorTel Meridian I, NEC, and Mitel.
<
DCS is Avayas PBX networking package. Mode code signaling

is not supported in the DCS environment.
Avaya

Confidential
Page 25
7.6 AVAYA OCTEL 100 PORTS SHOULD BE DISTRIBUTED

integration
It is highly recommended that Octel 100 ports be distributed among

different port cards and shelves in the ProLogix / G3. This reduces the
possibility that a single card or shelf failure will affect a large number of
Octel 100 ports. Depending on the ProLogix / G3 architecture,
performance could also be an issue on some ProLogix / G3 systems during
high traffic if a large number of calls are being processed on the same card
or shelf. The TN746B / TN791 is an interface between analog voice
terminal lines and the TDM packet bus. The TN746B / TN791 consists of
a ringing application circuit and port input/output circuits. A TN746B /
TN791 supports 16 ports. The TN746B / TN791 allows ringing on 4 ports
of each half of the circuit pack for a maximum of eight simultaneous ports
ringing. In addition, the TN793 and TN2793 are 24 port boards, are divide
into thirds 4 ports of each section ringing for a maximum of twelve
simultaneous ports ringing. A user attempting to ring one section of the
circuit pack when all four ports are busy receives a busy tone from the
ProLogix / G3. Therefore, when assigning analog ports to be used as
appearances for integration, always distribute the voicemail ports across
multiple TN746B / TN791 / TN793 / TN2793 cards.
7.7 RECORD TELEPHONE CONVERSATION CAN BE
SUPPORTED.

integration
In the Host Switch, a Coverage path can be created for Record Telephone
Conversation. The following inband templates must be added:
#02#123#R#
#03#123#R#
GO to Immediate Record
GO to Immediate Record
Digits 123 are example of a coverage group 123. The called party would
interrupt their conversions, perform a hook-flash, and dial 123. The Octel
100 would answer the call and return a beep indicating that recording had
started. The called party would then hook-flash to complete, or complete
the three-way conference. The time for Silence detection may have to be
adjusted to avoid premature voicing of recording menu options.
It will also be necessary to adjust the Recording time in the COS of the
called party to avoid premature voicing of recording menu options.
Avaya

Confidential
Page 26
2000-2001 Avaya Inc. All rights reserved. All trademarks identified by the , SM and TM are registered
trademarks, servicemarks or trademarks respectively. All other trademarks are properties of their respective
owners. The above information is based on knowledge available at the time of publication and is subject to
change without notice.
MERLIN Legend, Merlin Magix , Definity are registered trademarks of Avaya Inc.
DIALOG/4 is a registered trademark of Dialogic Corporation
Brooktrout TR114 Series Universal Port registered trademark of Brooktrout Technology A
BROOKTROUT COMPANY
Meridian I Optional 11 are registered trademarks of NorTel Inc.
Printed in the United States
AVAYA Inc.
1001 Murphy Ranch Road
Milpitas, CA 95035-7912
(408) 577-7000
http://www.avaya.com
(CFN 7022)

Definity Octel 100 Configuration Note

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Definity Octel 100 Configuration Note

Uploaded by

Copyright:

Available Formats

Configuration Note 7022

Avaya Definity Centralized

ISDN Tie Line

ISDN Tie Line

Inband signaling is used for

Supported Voice Processing

Octel 100 Configuration Note (7022)

Supported PBX Configurations

SUPPORTED PBX CONFIGURATIONS

The Avaya Inc Definity G3 Enterprise Communication Server is a state of

O100 ORDERING INFORMATION

Voice Boards supported:

Please consult with your sales representative.

This integration will support 16

Avaya Inc. PROPRIETARY. Use pursuant to Company instructions.

Octel 100 Configuration Note (7022)

PBX Software Requirements

UDP RTU and ISDN RTU software required.

DEFINITY ProLogix R3 (or later)

UDP and ISDN RTU software required.

DEFINITY BCS Issue 6 (or later)

UDP and ISDN software required.

MERLIN MAGIX R1.0 (or later)

MERLIN LEGEND R6.1 or R7.0

NorTel Meridian I (Programming not shown)

NEC (Programming not shown)

Mitel (Programming not shown)

Additional Material Requirements

If using the DIALOG/4 you will need:

Avaya Inc. PROPRIETARY. Use pursuant to Company instructions.

Octel 100 Configuration Note (7022)

Supported Integration Features

[] Items are supported

One analog line for remote service access

Multiple Return to Operator

See Section 7.2

ProLogix / G3 must have audible MWI activated

Programming Avaya ProLogix /

4-digit dial plan in DEFINITY/MERLIN private network

4- or 5-digit dial plan in all-DEFINITY (not both at same time)

Avaya Inc. PROPRIETARY. Use pursuant to Company instructions.

Entries in bold italic type indicate

Octel 100 Configuration Note (7022)

Refer to the Programming section in the appropriate manual for

Avaya Inc. PROPRIETARY. Use pursuant to Company instructions.

Octel 100 Configuration Note (7022)

display system-parameters customer-options

On page 1, verify fields as follows:

On page 2, verify fields as follows:

Send Name field is y.

Avaya Inc. PROPRIETARY. Use pursuant to Company instructions.

Octel 100 Configuration Note (7022)

Verify Feature Access codes

Send Calling Number field is y.

1. Enter the command: display feature-access-code.

Avaya Inc. PROPRIETARY. Use pursuant to Company instructions.

Entries in bold italic type

Octel 100 Configuration Note (7022)

5.3 CONFIGURING THE SINGLE LINE AVAYA OCTEL 100

Coverage Msg Retrieval?

Audible Message Waiting? n

Avaya Inc. PROPRIETARY. Use pursuant to Company instructions.

Octel 100 Configuration Note (7022)

add station 5001