Avaya S87 0 Series Quick start guide

Configuration Note 88502 – Version AH (7/09)
Avaya™
Modular Messaging AVAYA Definity G3, Prologix &
S87x0/S8xx0 - EMEA
E1/QSIG
Supported Versions:
See section 2.0
Message
Application Server
Automated Attendant
Return to Operator
Message Waiting
Call ID
Minimum Software:
Refer to Section 3.1
PSTN
Avaya PBX
Supported Versions:
See section 2.0
Message
Application Server
Automated Attendant
Return to Operator
Message Waiting
Call ID
Minimum Software:
Refer to Section 3.1
PSTN
Avaya PBX
The PBX and MM are
assumed to be collocated.
For other configurations
please consult with the
Switch Integrations group.
Overview
This Configuration Note is intended for Avaya certified Modular Messaging
technicians/engineers who are familiar with Modular Messaging
procedures and terminology. It also assumes that you are Avaya certified
or very familiar with the features and functionality of the Avaya PBXs
supported in this Configuration Note and the QSIG protocol.
Use this document in conjunction with Modular Messaging Installation Guide and
the Avaya PBX Administration Guide.
Please read the entire document before attempting any configuration.
1.0 METHOD OF INTEGRATION
With E1 QSIG, one digital
pathway between the PBX and
the Avaya Message Application
Server transmits both call
information and voice
communications
With E1 QSIG integration, one digital pathway between the Avaya™PBX
and the Avaya Message Application Server (MAS) transmits both call
information and voice communications. The pathway is provided by an
ISDN digital link (QSIG), which provides channels that connect to the
Dialogic E1 card. Within the D-Channel, routing information is sent to the
MAS containing information regarding the source of the call with reason
codes. The MAS processes call information from the supplementary code
in the D-Channel, which routes call reasons directly to mailboxes.
Message-Waiting indication is set and canceled using the supplementary
code service. Voice is carried through the system in digital format.
Disclaimer: Configuration Notes are designed to be a general guide reflecting AVAYA Inc. 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 Technical Assistance Center
at [phone], and if appropriate we will include it in our next revision. AVAYA Inc. accepts no responsibility for errors or omissions
contained herein.

AVAYA E1/QSIG 2
2.0 AVAYA MESSAGE APPLICATION SERVER REQUIREMENTS
•Dialogic D/600JCT-1E1 or D/300JCT-E1
MAS Requirements
•CT Bus cable (only required for multiple card installation)
•Supported Releases: 1.1, 2.0, 3.0, 3.1, 4.0, 5.0, 5.1
3.0 PBX HARDWARE REQUIREMENTS
PBX hardware requirements
•TN464 or MM710 circuits one per each Dialogic E1 Interface Card
•Cables:
-RJ45 on the Dialogic (cable depends on PBX connection)
3.1 PBX SOFTWARE REQUIREMENTS
PBX software requirements • Minimum Supported Software:
Definity G3 & Prologix: G3V10.1 Load 43
S8300/S8xx0: MV1.1, CM2.0 / 3.1.x / 4.x / 5.x
Important: Before ordering account teams should check with Avaya
Services to determine if there are any applicable patches for customer
specific configuration. Specifically if DCS+ or QSIG Networking is used.
•ISDN PRI
•Private Networking
•Basic Call Setup
•Basic Supplementary Services
•Supplementary Services with Rerouting
●DCS+ for Multiple PBX Support (Refer to Section 9.0)
(This option is only required for networking (multiple PBXs)
Note: Either DCS+ or QSIG Networks are necessary to support multiple
PBXs (Centralized Voice Mail). No other networks are supported.
Refer to Section 8.0 (Considerations) for additional info.
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 3
4.0 SUPPORTED INTEGRATION FEATURES
Supported integration features [9] Items are supported
System Forward to Personal Greeting
All Calls [9]
Ring/no answer [9]
Busy [9]
Station Forward to Personal Greeting
All Calls [9]
Ring/no answer [9]
Busy [9]
Auto Attendant [9]
Call Me [9]
Direct Call [9]
External Call ID (ANI) [9]
Fax [9]
Find Me [9]
Internal Call ID [9]
Message Waiting [9]
Multiple Call Forward [9]
Multiple Greetings [9]
N+1 [9]
Outcalling [9]
Queuing [ ]
Return to Operator [9]
IMPORTANT: PBX options or features not described in this Configuration
Note are not supported with this integration. To implement
options/features not described in this document, please contact the Avaya
Switch Integration product manager.
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 4
5.0 CONFIGURING THE PBX TO INTEGRATE
The following programming is intended for certified PBX technicians/engineers.
The screens shown in this section are taken from an Avaya PBX administration
terminal. Some parameters may not appear on all software releases.
Ensure all required software features are enabled on the PBX. Access the System
Parameters Customer Options form. Below is an example of the forms required for
QSIG integration, with the required features in boldface.
IMPORTANT: Only change the recommended fields. (see note on left)
display system-parameters customer-options Page 2 of 9
OPTIONAL FEATURES
Abbreviated Dialing Enhanced List? y Attendant Vectoring? y
Access Security Gateway (ASG)? n Audible Message Waiting? y
Analog Trunk Incoming Call ID? y Authorization Codes? y
A/D Grp/Sys List Dialing Start at 01? n CAS Branch? n
Answer Supervision by Call Classifier? y CAS Main? n
ARS? y Change COR by FAC? n
ARS/AAR Partitioning? y Cvg Of Calls Redirected Off-net? y**
ARS/AAR Dialing without FAC? n DCS (Basic)? y*
ASAI Interface? y DCS Call Coverage? y*
ASAI Proprietary Adjunct Links? y DCS with Rerouting? y*
Async. Transfer Mode (ATM) PNC? n DEFINITY Network Admin? n
Async. Transfer Mode (ATM) Trunking? n Digital Loss Plan Modification? n
ATM WAN Spare Processor? n DS1 MSP? y
ATMS? y DS1 Echo Cancellation? y
display system-parameters customer-options Page 3 of 9
OPTIONAL FEATURES
Emergency Access to Attendant? y ISDN-BRI Trunks? n
Enhanced EC500? y ISDN-PRI? y
Extended Cvg/Fwd Admin? y Malicious Call Trace? y
External Device Alarm Admin? n Mode Code for Centralized Voice Mail? n
Flexible Billing? n
Forced Entry of Account Codes? n Multifrequency Signaling? y
Global Call Classification? n Multimedia Appl. Server Interface (MASI)? n
Hospitality (Basic)? y Multimedia Call Handling (Basic)? y
Hospitality (G3V3 Enhancements)? n Multimedia Call Handling (Enhanced)? y
H.323 Trunks? y Multiple Locations? n
Personal Station Access (PSA)? n
IP Stations? y
ISDN Network Call Redirection? n
ISDN Feature Plus? y
NOTICE:
The screens in this
Config Note are only for
illustration purposes.
It is recommended that
a qualified technician
review the customer’s
CM QSig programming
for accuracy.
*NOTE:
DCS is only required for
networking.
Stand-alone/single PBX do
not require DCS, so those
options may be set to “N”
**NOTE:
Cvg of Calls Redirected Off-
Net (CCRON) must be set to
“y” if you are using Find Me.
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 5
display system-parameters customer-options Page 4 of 9
OPTIONAL FEATURES
PNC Duplication? n Tenant Partitioning? y
Terminal Trans. Init. (TTI)? y
Processor and System MSP? y Time of Day Routing? y
Private Networking? y Uniform Dialing Plan? y
Usage Allocation Enhancements? y
R9.5 Capabilities? y VAL Full 1-Hour Capacity? y
Remote Office? y
Restrict Call Forward Off Net? y Wideband Switching? y
Secondary Data Module? y Wireless? y
Station and Trunk MSP? y
Station as Virtual Extension? y
(NOTE: You must logoff & login to effect the permission changes.)
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1
*Note:This parameter would be set to “y” if you are using DCS to network Avaya PBXs.
display system-parameters customer-options Page 7 of 9
QSIG OPTIONAL FEATURES
Basic Call Setup? y
Basic Supplementary Services? y
Centralized Attendant? y
Interworking with DCS? n*
Supplementary Services with Rerouting? y
Transfer into QSIG Voice Mail? y
Value-Added (VALU)? y
Define the QSIG TSC Extension and MWI Number of Digits per Voice Mail Subscriber.
The following is an example of the form, with the required features in boldface.
change system-parameters features Page 7 of 12
FEATURE-RELATED SYSTEM PARAMETERS
ISDN PARAMETERS
Send Non-ISDN Trunk Group Name as Connected Name? n
Display Connected Name/Number for ISDN DCS Calls? y
Send ISDN Trunk Group Name on Tandem Calls? n
Send Custom Messages Through QSIG? y
QSIG TSC Extension: 2998
MWI - Number of Digits Per Voice Mail Subscriber: 4 (*see note below)
Feature Plus Ext:
National CPN Prefix:
International CPN Prefix:
Pass Prefixed CPN to ASAI? n
Unknown Numbers Considered Internal for AUDIX? n
USNI Calling Name for Outgoing Calls? y
Path Replacement with Measurements? y
QSIG Path Replacement Extension: 2798 (vacant extension)
Path Replace While in Queue/Vectoring? n
NOTE: This parameter must match the number of digits used for
mailbox/extension length. For multiple length extensions leave this field blank.
Important: The option to leave this field blank requires Avaya CM 2.1 and later.

AVAYA E1/QSIG 6
Also access the System Parameter Coverage-Forwarding and change or ensure the
following parameters are set appropriately:
Maintain SBA At Principal? n* (see note on left)
Coverage Of Calls Redirected Off-Net Enabled? n** (see note on left)
Change features and assign your private network access code, in this example we
assigned 107
display system-parameters coverage-forwarding Page 2 of 2
SYSTEM PARAMETERS CALL COVERAGE / CALL FORWARDING
COVERAGE OF CALLS REDIRECTED OFF-NET (CCRON)
Coverage Of Calls Redirected Off-Net Enabled? n**
Activate Answer Detection (Preserves SBA) On Final CCRON Cvg Point? n
Ignore Network Answer Supervision? n
Disable call classifier for CCRON over ISDN trunks? n
display system-parameters coverage-forwarding Page 1 of 2
SYSTEM PARAMETERS CALL COVERAGE / CALL FORWARDING
CALL COVERAGE/FORWARDING PARAMETERS
Local Cvg Subsequent Redirection/CFWD No Ans Interval (rings): 2
Off-Net Cvg Subsequent Redirection/CFWD No Ans Interval (rings): 2
Coverage - Caller Response Interval (seconds): 2
Threshold for Blocking Off-Net Redirection of Incoming Trunk Calls: 3
COVERAGE
Keep Held SBA at Coverage Point? y
External Coverage Treatment for Transferred Incoming Trunk Calls? n
Immediate Redirection on Receipt of PROGRESS Inband Information? n
Maintain SBA At Principal? n*
QSIG VALU Coverage Overrides QSIG Diversion with Rerouting? n
Station Hunt Before Coverage? n
FORWARDING
Call Forward Override? n
Coverage After Forwarding? n
change feature-access-codes Page 1 of 6
FEATURE ACCESS CODE (FAC)
Abbreviated Dialing List1 Access Code: 101
Abbreviated Dialing List2 Access Code: 102
Abbreviated Dialing List3 Access Code: 103
Abbreviated Dial - Prgm Group List Access Code:
Announcement Access Code: 104
Answer Back Access Code:
Auto Alternate Routing (AAR) Access Code: 107
Auto Route Selection (ARS) - Access Code 1: 9 Access Code 2:
Automatic Callback Activation: Deactivation:
Call Forwarding Activation Busy/DA: 190 All: *9 Deactivation: #9
Call Park Access Code: *6
Call Pickup Access Code:
CAS Remote Hold/Answer Hold-Unhold Access Code:
CDR Account Code Access Code: 188
Change COR Access Code:
Change Coverage Access Code:
Data Origination Access Code:
Data Privacy Access Code:
Directed Call Pickup Access Code:
**NOTE:
Coverage of Calls
Redirected Off-Net
(CCRON) must be set to “y”
if you are using Find Me.
*NOTE:
Maintain SBA at principal set
to “n” ensures that when the
call covers to voice messaging
the appearance on the station is
removed to ensure privacy.
Doing this prevents someone
from listening to the call as it is
being recorded by the voice
messaging system.
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 7
Install the E1 circuit pack, making sure they are “strapped” for 30-channel
operation (E-1). Configure the DS1 circuits as follows:
Configure a Signaling Group that will be assigned to the DS1 channels. The
Signaling Group should be configured as follows:
Important: The Max number of NCA TSC (Non-Carrier Associated Temporary
Signaling Channels) should be 1 or higher. This allows a path (1 or more) for
MWI to operate.
display ds1 01b17
DS1 CIRCUIT PACK
Location: 01B17 Name: E1 QSIG
Bit Rate: 2.048 Line Coding: hdb3
Signaling Mode: isdn-pri
Connect: pbx Interface: peer-master
CentreVu Long Timers? n Peer Protocol: Q-SIG
Interworking Message: PROGress Side: a
Interface Companding: alaw CRC? n
Idle Code: 11111111 Channel Numbering: timeslot
DCP/Analog Bearer Capability: 3.1kHz
Slip Detection? nNear-end CSU Type: other
display signaling-group 1 Page 1 of 5
SIGNALING GROUP
Group Number: 9 Group Type: isdn-pri
Associated Signaling? y Max number of NCA TSC: 10
Primary D-Channel: 01b1716 Max number of CA TSC: 10
Trunk Group for NCA TSC: 1
Trunk Group for Channel Selection: 1 X-Mobility/Wireless Type: NONE
Supplementary Service Protocol: b
NCA-TSCs are used for QSIG.
CA-TSCs are used with DCS+
-----------------
Trunk Group for NCA TSC
should have a value to indicate
trunk group only if using MWI
Interrogation.
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 8
Create a trunk group, and assign the newly created DS1 channels to it. If the
MAS will be configured to perform outcalls, ensure that the COR (Class of
Restriction) assigned to this trunk group allows for outside trunk access. The trunk
group must be configured as follows:
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1
display trunk-group 1 Page 1 of 22
TRUNK GROUP
Group Number: 1 Group Type: isdn CDR Reports: y
Group Name: QSIG - E1 COR: 1 TN: 1 TAC: 21
Direction: two-way Outgoing Display? y Carrier Medium: PRI/BRI
Dial Access? n Busy Threshold: 99 Night Service:
Queue Length: 0
Service Type: tie Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4
TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: bDigit Handling (in/out): enbloc/enbloc
Trunk Hunt: cyclical QSIG Value-Added? n
Digital Loss Group: 13
Calling Number - Delete: Insert: Numbering Format: unk-unk
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Su
p
ervision Timeout: 0
display trunk-group 1 Page 2 of 22
TRUNK FEATURES
ACA Assignment? nMeasured: none Wideband Support? n
Internal Alert? n Maintenance Tests? y
Data Restriction? n NCA-TSC Trunk Member: 29 (Note1)
Send Name: ySend Calling Number: y
Used for DCS? Hop Dgt?n n
Suppress # Outpulsing? nNumbering Format: unk-pvt (see Tip & NOTE2 below)
Outgoing Channel ID Encoding: exclusive UUI IE Treatment: service-provider
Replace Restricted Numbers? n
Replace Unavailable Numbers? n
Send Called/Busy/Connected Number: y
Send UCID? n
Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? n
Modify Reroute Number? y
Path Replacement with Retention? n
Path Replacement Method: always
Network (Japan) Needs Connect Before Disconnect? n
Tip:If the numbering format is set to unk-pvt
then the PBX looks to the Private-Numbering
Table to build the number. The Network Level
must not be left blank (in most cases this is set
to 0) or NO number will be sent.
This is where the PBX builds the called party
number for the integration. If it is set to
unknown, the PBX looks at the Public-
Unknown table where an entry is required to
build to the number. If there is no entry in this
table to build the number, NO number is sent.
For Avaya CM 4.0 and later see related
note below
NOTE 1: NCA-TSC Trunk Member should have the highest timeslot from the
upper E1 span in the trunk group. For example, if there is one E1 span in the
MAS then it should be 29, and if there are 2 spans then its should be 59.
NOTE 2: The Numbering Format fields could be set according to the customer’s
environment. There are many variations plus other tables associated with these
fields that must be considered also. Consult with a Software Specialists for proper
programming.

AVAYA E1/QSIG 9
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1
display trunk-group 1 Page 6 of 22
TRUNK GROUP
Administered Members (min/max): 1/29
GROUP MEMBER ASSIGNMENTS Total Administered Members: 29
Port Code Sfx Name Night Sig Grp
1: 01B1701 TN464 F 1
2: 01B1702 TN464 F 1
3: 01B1703 TN464 F 1
4: 01B1704 TN464 F 1
5: 01B1705 TN464 F 1
6: 01B1706 TN464 F 1
7: 01B1707 TN464 F 1
8: 01B1708 TN464 F 1
9: 01B1709 TN464 F 1
10: 01B1710 TN464 F 1
11: 01B1711 TN464 F 1
12: 01B1712 TN464 F 1
13: 01B1713 TN464 F 1
14: 01B1714 TN464 F 1
15: 01B1715 TN464 F 1
display trunk-group 1 Page 7 of 22
TRUNK GROUP
Administered Members (min/max): 1/29
GROUP MEMBER ASSIGNMENTS Total Administered Members: 29
Port Code Sfx Name Night Sig Grp
16: 01B1717 TN464 F 1
17: 01B1718 TN464 F 1
18: 01B1719 TN464 F 1
19: 01B1720 TN464 F 1
20: 01B1721 TN464 F 1
21: 01B1722 TN464 F 1
22: 01B1723 TN464 F 1
23: 01B1724 TN464 F 1
24: 01B1725 TN464 F 1
25: 01B1726 TN464 F 1
26: 01B1727 TN464 F 1
27: 01B1728 TN464 F 1
28: 01B1729 TN464 F 1
29: 01B1730 TN464 F 1
See side NOTE
There should be 29 total ports for a
single E1 span per MAS.
There should be 59 total ports if
two E1 spans per MAS.
Do not administer (add) the highest
order timeslot/port as a member in
the trunk group.
•For an MAS with a single E1 card
Do Not add port 30. Only 29 ports
should be in the trunk group.
•For an MAS equipped with two E1
cards Do Not add Port 60. Only 59
ports should be in the trunk group.
The reason for this is due to a limitation with
the Dialogic drivers it requires that we leave
out the highest order timeslot to enable MWI,
even though MWI is sent on the D-Channel.
Therefore, only 29 ports are available on an
MAS with one E1 card, or 59 ports on an MAS
with two E1 cards.
Note: For full N+1 support in your MM environment you should set aside a
number of ports from each MAS in your environment to be allocated for each of
the different port types. When planning trunk group configuration for your
multiple MAS environment care should be taken to ensure the same number of
ports are allocated to the incoming trunk group for each MAS in your
environment. For example, if MAS1 has 16-ports allocated to the incoming trunk
group, MAS2 should also have 16-ports allocated to the incoming trunk group.
When running in a multiple MAS environment with N+1 support, you should
setup the trunks groups as follows:

AVAYA E1/QSIG 10
Incoming Trunk group: should be configured containing all of the required
incoming ports from each MAS in your environment, the ports should be entered
into the trunk group so Trunk group port-1 is the first port on MAS1, Trunk group
port-2 is the first port on MAS2, Trunk group port-3 is the second port on MAS1,
etc..
Outgoing Trunk group: should be configured with all of the required outgoing
ports from each MAS in your environment, used for MM client outcalls and TUI
transfers.’
Refer to Consideration 8.10 for additional N+1 programming.
Change the ISDN Numbering - Private Network form to configure and ensure
the PBX for the proper Network Level to be used. Below is a copy of the ISDN
Numbering - Private Network form with the required field in boldface.
display isdn private-numbering
ISDN NUMBERING - PRIVATE FORMAT
Network Level: 0PBX Identifier:
Level 2 Code: Deleted Digits: 0
Level 1 Code:
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 11
NOTE: This parameter must match the number of digits used for mailbox/extension length.
For multiple length extensions leave this field blank (this requires Avaya CM 2.1
or later). However, please note MM supports only one mailbox length.
In Avaya CM 4.0 the Private Numbering Form is now used to define the number
format for specific trunk groups. In our example screen below, we have a 4-digit
extension length that includes extensions from 2000 thru 5999. The 4-digit
number will be part of the QSIG number information that will be passed to the
MM for call integration.
If you set numbering format to "unk-pvt" on page 2 of the trunk group form (see
earlier in this section), which is for the MM Trunk Group, this form must be
completed so the CM knows how to build the private format number. For that
reason, do not leave the form blank or the MM call integration will fail.
NOTES for Avaya CM 4.0 and later
Network Levels and Level codes are now
found in system-parameters features under
Parameters for Creating QSIG Selection
Numbers
Note: If the numbering format is set to unk-
pvt then the PBX looks to the Private-
Numbering Table to build the number.
Network Level must not be left blank (in
most cases this is set to 0) or NO number
will be sent. This is where the PBX builds
the proper number (i.e., user’s station
number) for the integration to open the
proper mailbox.
display system-parameters features Page 8 of 17
FEATURE-RELATED SYSTEM PARAMETERS
ISDN PARAMETERS
PARAMETERS FOR CREATING
Send Non-ISDN Trunk Group Name as Connected Name? n QSIG SELECTION NUMBERS
Display Connected Name/Number for ISDN DCS Calls? y Network Level: 0
Send ISDN Trunk Group Name on Tandem Calls? n Level 2 Code:
Send Custom Messages Through QSIG? y Level 1 Code:
QSIG/ETSI TSC Extension: 2998
MWI - Number of Digits Per Voice Mail Subscriber: 4 (see note below)
Feature Plus Ext:
National CPN Prefix:
International CPN Prefix:
Pass Prefixed CPN to ASAI? n
Unknown Numbers Considered Internal for AUDIX? n
USNI Calling Name for Outgoing Calls? y
Path Replacement with Measurements? y
QSIG Path Replacement Extension: 2798
Path Replace While in Queue/Vectoring? n
change private-numbering 3 Page 1 of 2
NUMBERING - PRIVATE FORMAT
Ext Ext Trk Private Total
Len Code Grp(s) Prefix Len
4 2 99 4 al Administered: 4Tot
4 3 99 4 Maximum Entries: 540
4 4 99 4
4 5 99 4
IMPORTANT
This screen supports Private Numbering
Plans (PNP) allowing you to specify the
digits to be put in the Calling Number
information element (IE), the Connected
Number IE, and the QSIG Party Number
for extensions in the Private Numbering
Plan.
Avaya CM supports private-network
numbers up to 15 digits in length. If the
total number — including the level 1 and
2 prefixes, the Private Prefix (formerly
known as PBX identifier), and the
extension — is more than 15 digits long,
neither QSIG Party Numbers nor the
information elements are created or sent.
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 12
Create a Route Pattern for the trunk group that was previously created for the
DS1 channels. The Route Pattern must be configured as follows:
display route-pattern 1 Page 1 of 3
Pattern Number: 12
Grp. FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC
No. Mrk Lmt List Del Digits QSIG
Dgts Intw
1: 1 03yuser
2: 203(this is an example, yuser
3: see note below) n user
4: n user
5: n user
6: n user
BCC VALUE TSC CA-TSC ITC BCIE Service/Feature BAND No. Numbering LAR
0 1 2 3 4 W Request Dgts Format
Subaddress
1: y y y y y n yas needed rest unk-unk rehu
2: y y y y y n n rest none
3: y y y y y n n rest none
4: y y y y y n n rest none
5: y y y y y n n rest none
6: y y y y y n n rest none
Note: If adding additional MAS servers, ensure their Trunk Groups are added to this
Route Pattern and follow the same programming as the 1st Trunk Group.
Within the AAR Digit Analysis Table, create a dialed string that will map calls
to the newly created Route Pattern. The dialed string created in the AAR Digit
Analysis Table will be used later in the Hunt Group form that will define the MAS
Hunt Group. Below is an example of an AAR dialed string in boldface.
display aar analysis 15 Page 1 of 2
Percent Full: 3
Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
4573000 7 7 1 aar n
NOTE: Avaya IP phones may experience DTMF failure when dialing the Hunt
Group. They can dial the UDP number or the AAR # above to bypass the Hunt
Group and use DTMF capability.
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 13
Configure a Hunt Group to be used as the Call Coverage Point for the Call
Coverage Path assigned to the MAS subscribers. This hunt group’s extension
number is going to be used as the MAS Access Number. Enter the dialed string
created previously in the AAR Digit Analysis Table in the “Voice Mail Number”
field on page 2 of the Hunt Group form. Also, in the “Routing Digit (e.g.
AAR/ARS Access Code)” field of this form, enter your PBX’s AAR Access Code
as defined on page 1 of the Feature Access Codes form. This hunt group is
configured with no members assigned to it, and should be configured as follows:
Note: Queue? should be set to “n” as recommended. Refer to
Consideration 8.9 for further information.
display hunt-group 1 Page 1 of 60
HUNT GROUP
Group Number: ACD?1 n
Group Name: QSIG E1 Queue? n (see note below)
Group Extension: 3000 Vector? n
Group Type: ucd-mia Coverage Path:
TN: 1 Night Service Destination:
COR: 1 MM Early Answer? n
Security Code:
ISDN Caller Display: grp-name
display hunt-group 1 Page 2 of 60
HUNT GROUP
Message Center: qsig-mwi
Voice Mail Number: 4573000
Routing Digits (e.g. AAR /ARS Access Code): 107
Send Reroute Request: n
LWC Reception: none
NOTE: The “Voice Mail Number” entered here must be administered in the “Voice
Mail System Configuration->PBX->OutgoingCall” tab of the MAS. The number
that is entered in the “Outgoing Call” tab is the Voice Mail Number.
- continued on next page -
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 14
Create a Call Coverage Path that will be assigned to the subscribers’ stations.
This Call Coverage Path will have the MAS Hunt Group as the Call Coverage Point.
Below is an example of a Call Coverage Path.
display coverage path 10
COVERAGE PATH
Coverage Path Number: 1
Hunt after Coverage? n
Next Path Number: Linkage
COVERAGE CRITERIA
Station/Group Status Inside Call Outside Call
Active? n n
Busy? y y
Don't Answer? y y Number of Rings: 4
All? n n
DND/SAC/Goto Cover? y y
COVERAGE POINTS
Terminate to Coverage Pts. with Bridged Appearances? n
Point1:h1 Point2: Point3:
Point4: Point5: Point6:
Configure the subscriber stations, assigning the newly created Call Coverage
Path (i.e. 10) to them. Also, ensure the following setting for subscribers:
display station 3002 Page 1 of 4
STATION
Extension: 3002 Lock Messages? n BCC: 0
Type: 8410D Security Code: TN: 1
Port: 01A0102 Coverage Path 1: 10 COR: 1
Name: Smith John Coverage Path 2: COS: 1
Hunt-to Station:
STATION OPTIONS
Loss Group: 2 Personalized :Ringing Pattern 1
Data Module? n Message Lamp Ext: 3002
Display Module? y
Speakerphone: 2-way Mute Button Enable? y
Display Language: english
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 15
display station 3002 Page 2 of 4
STATION
FEATURE OPTIONS
LWC Reception: none Auto Select Any Idle Appearance? n
LWC Activation? n Coverage Msg Retrieval? y
LWC Log External Calls? n Auto Answer? none
CDR Privacy? n Data Restriction? n
Redirect Notification? y Idle Appearance Preference? n
Per Button Ring Control? n
Bridged Call Alerting? n Restrict Last Appearance? y
Active Station Ringing: single
H.320 Conversion? n Per Station CPN – Send Calling Number? y
MWI Served User Type: qsig-mwi Display Client Redirection? n
Select Last Used Appearance? n
Coverage After Forwarding? s
Per Station CPN – Send Calling Number
must be set to “y” for the integration to
work properly.
Note: With QSIG integration the following fields are required for Message
Waiting:
LWC Reception: none
MWI Served User Type: qsig-mwi
Single Line sets should have field “Message Waiting Indicator” set to “led” or
“neon,” depending on the type of telephone set used. Also, the “Number of
Rings” field should be set to a minimum of 4 rings, to allow Personal Assistance
to work properly.
Save these PBX changes.
Please refer to the Consideration section at the end of this document for special
PBX programming considerations.
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 16
6.0 CONFIGURING THE MESSAGE APPLICATION SERVER
Configuring the MAS Configuring the MAS platform for proper PBX integration requires configuring
several menus accessed within the Voice Mail System Configuration application, and
a certified MM engineer.
Access the Voice Mail System Configuration application from the
MAS program group.
The example number shown above in blue is incorrect. Change this from 000F 01 to 000F 00.
Save then file and then reboot the MAS.
Special Note: Verify the CRC value in the QTE.PRM is set correctly. If left uncorrected the Dialogic E1 boards
will not initialize properly. The file is found in:
C:\Program Files\Dialogic\data\qte.prm
Open the qte.prm file. About 23 lines into the file text you will see a setting under the line as show in bold below.
;---
;--- CRC ENABLE SWITCH (Parameter type 0FH - E1 only)
;--- Turns the transmission of the CRC4 pattern on or off and searches
;--- for such a pattern in the received signal.
;--- Possible values for the data are as follows:
;--- 00H = Turn CRC off.
;--- 01H = Turn CRC on.
;--- The default data value is 00H (Turn CRC off).
000F 01
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 17
Expand all fields so all-applicable options are visible:
Note: Starting with MM 5.0
additional Fields such as
Sites and PBX
Integration will appear
on the VMSC screen.
Ensure the new PBX is added as instructed by the Modular Messaging
Installation guide. The new PBX should be:
Avaya G3 (QSIG)
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 18
1. Select the Voice Mail Domain
2. Expand PBXs
3. Select the newly created Avaya G3 (Dialogic QSIG)
4. Access the General (QSIG) PBX Configuration tab
5. DTMF Inter-Digit Delay during Dialing (ms) = 80
6. DTMF Length during Dialing (ms) = 80
7. DTMF Length during Detection (ms) = 50
Next access the Transfer/Outcall tab
Transfer Mode = Blind
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 19
Next access the Tone Detection tab
Maximum Silence before Hanging Up (ms) = 6000
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1

AVAYA E1/QSIG 20
Next access the Outgoing Call tab
1. Layer Protocol = G.711 A-Law
2. BC Transfer Cap = Speech
3. Number Type = Unknown
4. Number Plan = Unknown
5. Origin Number = 4573000 (The number entered here should be the
number entered in the “Voice Mail Number” field on page 2 of the Hunt
Group form)
Note: Layer protocol fields should match the Interface Companding setting
selected on Page1 of the DS1 Circuit Pack configuration screen on Page 7
of this configuration note.
The above information is provided by AVAYA Inc. as a guide. See disclaimer on page 1