Intecom E / PointSpan 6880 - Avaya Support
Intecom E / PointSpan 6880 - Avaya Support
Intecom E / PointSpan 6880 - Avaya Support
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Avaya</strong><br />
Modular Messaging<br />
With RS-232 integration, call<br />
information is transmitted over a<br />
digital RS-232 link between the<br />
PBX and the <strong>Avaya</strong> Message<br />
Application Server<br />
Configuration Note 88058 – Rev. A (07/08)<br />
<strong>Intecom</strong> E / <strong>PointSpan</strong> <strong>6880</strong><br />
<strong>Intecom</strong> E / <strong>PointSpan</strong> <strong>6880</strong><br />
TRUNK<br />
CPU<br />
Analog<br />
Station<br />
I/O Port<br />
Minimum Software:<br />
Version 9<br />
Automated Attendant<br />
Return to Operator<br />
RS-232 Circuit<br />
Call ID<br />
Message Waiting<br />
Message<br />
Application<br />
Server<br />
Voice<br />
Boards<br />
Minimum Software<br />
Release 2.0<br />
OVERVIEW<br />
This Configuration Note is intended for <strong>Avaya</strong> certified Modular<br />
Messaging technicians/engineers who are familiar with Modular<br />
Messaging procedures and terminology. It also assumes that you are<br />
<strong>Avaya</strong> certified or very familiar with the features and functionality of the<br />
<strong>Avaya</strong> PBXs supported in this Configuration Note and the QSIG<br />
protocol.<br />
Use this document in conjunction with Modular Messaging Installation<br />
Guide and the <strong>Intecom</strong> PBX Administration Guide.<br />
Please read the entire document before attempting any configuration.<br />
1.0 METHOD OF INTEGRATION<br />
With RS-232 integration, call information is transmitted over a digital RS-<br />
232 link between the PBX and the <strong>Avaya</strong> Message Application Server<br />
(MAS). Voice communications are provided over separate analog lines on<br />
the PBX that connect to the MAS. When an incoming call is received, it is<br />
accompanied by a digital message from the PBX containing call<br />
information. The MAS then answers the call and plays the appropriate<br />
greeting. The RS-232 link also handles on & off message waiting<br />
indication.<br />
Disclaimer: Configuration Notes are designed to be a general guide reflecting AVAYA Inc. experience configuring its systems. These<br />
notes cannot anticipate every configuration possibility given the inherent variations in all hardware and software products. Please<br />
understand that you may experience a problem not detailed in a Configuration Note. If so, please notify the Technical Assistance<br />
Center at (800) 876-2835, and if appropriate we will include it in our next revision. AVAYA Inc. accepts no responsibility for errors or<br />
omissions contained herein.<br />
COM<br />
Port
MAS Requirements<br />
PBX hardware requirements<br />
PBX software requirements<br />
<strong>Support</strong>ed integration features<br />
<strong>Intecom</strong> E 2<br />
2.0 AVAYA MESSAGE APPLICATION SERVER REQUIREMENTS<br />
• Integration cables (PN 057-1580-000 & 003-1081-000)<br />
• Dialogic D/41JCT-LS or D/120JCT-LS cards (4 and 12 port/cards)<br />
• Software Release 2.0<br />
• Dialogic Driver Version: 5.1.1 FP1 SU15<br />
3.0 PBX HARDWARE REQUIREMENTS<br />
• OPX line appearances P/N 300-0325-001(16 ports per card), one port per<br />
MAS port<br />
• One PDI (Programmable Data Interface) per VMP interface-1000S DCE<br />
P/N 520-1000-004<br />
• The customer must provide the necessary hardware.<br />
• Cables:<br />
- RJ11 four-wire telephone cord, one per MAS port<br />
- DB 25 cable, one per RS-232 link<br />
3.1 PBX SOFTWARE REQUIREMENTS<br />
• Minimum Software: Version 9.0<br />
• VMP Interface Software option package, P/N 993-0012-310<br />
- continued on next page -<br />
The above information is provided by AVAYA Inc. as a guideline. See disclaimer on page 1
<strong>Intecom</strong> E 3<br />
4.0 SUPPORTED INTEGRATION FEATURES<br />
[�] Items are supported<br />
System Forward to Personal Greeting<br />
All Calls [ ]<br />
Ring/no answer [�]<br />
Busy [�]<br />
Busy/No Answer [ ]<br />
Station Forward to Personal Greeting<br />
All Calls [�]<br />
Ring/no answer [ ]<br />
Busy [ ]<br />
Busy/No Answer [ ]<br />
Auto Attendant [�]<br />
Call Me [�]<br />
Direct Call [�]<br />
External Call ID (ANI) [�]<br />
Fax [�]<br />
Find Me [ ]<br />
Internal Call ID [�]<br />
Message Waiting [�]<br />
Multiple Greetings [�]<br />
Multiple Call Forward [�]<br />
N+1 [ ]<br />
Outcalling [�]<br />
Return to Operator [�]<br />
- continued on next page -<br />
The above information is provided by AVAYA Inc. as a guideline. See disclaimer on page 1
Configuring the PBX<br />
<strong>Intecom</strong> E 4<br />
5.0 CONFIGURING THE PBX TO INTEGRATE<br />
The following programming is required to successfully integrate with an<br />
InteCom E/Nexspan. Refer to PBX’s System Database Manual for further<br />
information. This programming is intended for certified PBX<br />
technicians/engineers.<br />
� At the PBX man machine terminal, create a bi-directional trunk group for<br />
the MAS voice lines. Set the trunk group type to 'Mail' for the InteCom<br />
E/Nexspan. When prompted for InteMail Interface Number (IIN), enter<br />
'20' for the InteCom E/Nexspan.<br />
� Create a trunk port for each MAS voice line.<br />
� When programming the E, special attention must be paid to assigning<br />
VMP (Voice Message Product) trunks for the MAS ports. The InteCom E<br />
sends a seven-digit trunk port number as part of the Calling Party<br />
Identification (CPID) message. This seven-digit number identifies the<br />
location of the particular VMP trunk, or MAS port, that a call is ringing.<br />
The numbering format is as follows:<br />
AABCCDD<br />
where AA is the two-digit cabinet number;<br />
B is the one-digit shelf number;<br />
CC is the two-digit card slot number;<br />
DD is the two-digit offset of the trunk port.<br />
Each VMP trunk that is used as an MAS port must send a trunk<br />
port number with unique last four digits, i.e., the card slot and<br />
offset must be unique for each trunk used to connect to the MAS.<br />
� Set up a prefix digit table for the trunk group. The table should have<br />
zero (0) significant figures.<br />
� Assign a route guide to the trunk group. When prompted, use the trunk<br />
group and prefix digit table numbers created in the above steps.<br />
� Create the satellite directory group associated with the trunk group.<br />
Enter the route guide number created above. When prompted,<br />
designate the directory group for “direct” call types.<br />
� Assign an extension (pilot) number to the satellite directory group<br />
(SDG).<br />
NOTE: This pilot number is the MAS access number. It is used for two<br />
purposes. First, subscribers’ stations are forwarded to this number.<br />
Second, station users transfer calls to this number when callers wish to be<br />
transferred to the MAS.<br />
The above information is provided by AVAYA Inc. as a guideline. See disclaimer on page 1
Enable Transfer Supervision on<br />
the PBX<br />
Programming the Direct Call<br />
feature<br />
<strong>Intecom</strong> E 5<br />
� Assign a user group for the MAS. When prompted, enter the satellite<br />
directory group number created above. This user group number must be<br />
entered when creating the bi-directional trunk group, the trunk ports, the<br />
satellite directory group, and the satellite directory group extension<br />
number.<br />
� Nail the PDI to the appropriate voice mail link.<br />
� Assign a voice class of service for the MAS subscribers. Enter “Yes”<br />
when prompted to allow voice mail access and voice mail auto sign-on.<br />
In addition, verify the “Pass-thru Option” in the voice class of service is<br />
set to “YES.” If it is not, the subscribers will not have DTMF capability<br />
while accessing the voice module.<br />
� Modify subscriber’s extension profiles to include the MAS user group<br />
number and class of service. Call forward the extension to the satellite<br />
directory group extension number on busy and no answer. Enter the<br />
extension number in the “VID...InteMail ID for VOICE LINE” field.<br />
� Display the voice mail submenu (ITMR). Verify all entries including<br />
InteMail Interface Number (IIN), user group, trunk group, satellite<br />
directory group, and satellite directory group extension number are<br />
correct.<br />
� Enable transfer supervision by answering YES to the following<br />
prompts:<br />
Voice Trunk Transfer enabled?<br />
Does Intermail supervise transfers?<br />
Once you answer YES to the last prompt you will be asked to enter the<br />
'method to cancel transfer?' Two options will appear:<br />
'F' (for Flash) or<br />
'F and feature code'<br />
Select 'F'.<br />
5.1 PROGRAMMING THE DIRECT CALL FEATURE<br />
The PBX has a direct call feature that places subscribers directly into their own<br />
mailbox. Subscribers dial “*5” or depress a special button on their ITE set to<br />
invoke direct call. The MAS will immediately play the subscriber’s name and<br />
ask for their password.<br />
If a subscriber is at another station, he can simply dial the MAS access number<br />
followed by “#”, mailbox number, and password to retrieve messages.<br />
� Configure button templates with a voice mail feature button for direct<br />
call access for ITE phones, if desired.<br />
The above information is provided by AVAYA Inc. as a guideline. See disclaimer on page 1
If you require two hunt groups<br />
supported by one RS232 link on<br />
the InteCom PBX, create the<br />
second hunt group<br />
Configuring the MAS<br />
<strong>Intecom</strong> E 6<br />
5.2 CREATING A SECOND HUNT GROUP<br />
If you require two hunt groups supported by one RS232 link on the InteCom<br />
PBX, create the second hunt group with the following directions. Such set-up<br />
may be desire to support a second hunt group of Fax-enabled ports:<br />
• Create a Satellite Directory Group, and direct it, using the route guide, to<br />
a trunk group containing the second group of MAS ports.<br />
• In the Trunk Group parameters, for “InteMail type,” enter “2 - SMDI<br />
type.” For the “InteMail Interface number” field, set the value to “1.”<br />
• Then, call forward appropriate phones on busy and ring-no-answer<br />
conditions to the Satellite Directory Group.<br />
5.3 MESSAGE WAITING ON THE PBX<br />
Three types of message-waiting indication are available. For ITE sets with<br />
LCD displays, the phrase “voice message” will appear in the display. For<br />
regular ITE sets, the InteMail feature button will light. For analog STE sets<br />
and single line digital ITE4 sets, the phrase “voice message” will be heard<br />
when the phone goes off-hook.<br />
6.0 CONFIGURING THE MESSAGE APPLICATION SERVER<br />
Configuring the MAS platform for proper PBX integration requires<br />
configuring several menus accessed within the Voice Mail System<br />
Configuration application, and a certified MM engineer.<br />
� Access the Voice Mail System Configuration application from the<br />
MAS program group. Expand all fields so all-applicable options are<br />
visible.<br />
1. Select the Voice Mail Domain<br />
2. Expand PBXs<br />
3. Select the newly created <strong>Intecom</strong><br />
4. Access the General PBX Configuration tab<br />
5. Go Off Hook when Port Disabled = Enable by checking the box<br />
6. Pause before Digits (ms) = 500<br />
7. Pause Interval for Comma in Dial String (ms) = 1000<br />
8. DTMF Inter-Digit Delay during Dialing (ms) = 80<br />
9. DTMF Length during Dialing (ms) = 80<br />
10. DTMF Length during Detection (ms) = 50<br />
The above information is provided by AVAYA Inc. as a guideline. See disclaimer on page 1
Call Transfer settings:<br />
With some <strong>Intecom</strong>/<strong>PointSpan</strong><br />
PBXs the settings shown to the<br />
right may need to be modified to<br />
accommodate the PBX’s dial<br />
plan.<br />
<strong>Intecom</strong> E 7<br />
� Next access the Call Transfer tab<br />
1. Transfer Mode = Blind<br />
2. Transfer Prefix Code = &,XN<br />
3. Transfer Complete Code = (leave blank)<br />
4. Transfer Release Code when Busy = &,&<br />
5. Transfer Release Code when No Answer = &,&<br />
6. Transfer Release Code when Reject = &,&,,,<br />
7. Flash Time Interval (ms) = 500<br />
8. Enable Call Progress = Enable by checking the box<br />
9. Start Delay for Call Progress (ms) = 1000<br />
� Next access the Hangup Detection tab<br />
1. Maximum Continuous Tone before Hanging Up (ms) = 6000<br />
2. Hangup String = Leave Blank<br />
3. Hangup String Timeout (ms) = 0<br />
4. Minimum Duration For Drop in Loop Current (ms) = 300<br />
5. Maximum Silence before Hanging Up (ms) = 6000<br />
6. Select OK to save changes<br />
� Next access the Message Waiting Indicator (MWI) tab<br />
1. Enable Message Waiting Indicator (MWI) = Enable by checking<br />
the box<br />
2. MAS MWI Server = Enter the name of the MWI server created<br />
during the installation procedure.<br />
3. Maximum Requests per Minute = 200<br />
4. Message Application Servers that <strong>Support</strong> MWI = This box<br />
should contain a list of MAS servers capable of placing MWI<br />
requests<br />
5. Select OK to save changes<br />
� Next access the Port Groups tab under the MAS name<br />
1. Access the Port Groups General tab and ensure the Default<br />
Group under Port Groups is checked for both Incoming and<br />
Outgoing under Port Group Usage<br />
2. Access the Port Group Usage tab and check all Ports (see port<br />
enabling next)<br />
3. Select OK to save changes<br />
� Next access the Voice Mail System Configuration window<br />
1. Access Message Application Servers<br />
2. Select the General tab under the Telephony Interface<br />
(Dialogic Analog)<br />
The above information is provided by AVAYA Inc. as a guideline. See disclaimer on page 1
<strong>Intecom</strong> E 8<br />
3. Playback Volume = 2 (Default)<br />
4. Number of Ports = Enter the number of ports in your system<br />
- Enable the port(s) by checking the Box field next to the Port field<br />
- Extension = Enter the proper ext # assigned to each port<br />
- Incoming Ring Count = 1<br />
- Primary ID = Enter Logical Terminal Number (LTN) for that port (normally<br />
LTN starts with 0001 for first port, 0002 for second port, 0003)<br />
- Secondary ID = Enter 001 Message Desk (MD) number for all ports.<br />
NOTE: The Secondary ID must be 3 digits in length (standard SMDI protocol),<br />
however the actual value could be different then “001” (i.e. 002, 999, etc.)<br />
� Select OK and Save changes<br />
� Return to the Voice Servers section and access PBX Integration.<br />
1. Access the General tab.<br />
2. Select Serial as the Integration Type.<br />
3. Maximum Time to Wait for Serial and Remote Integration<br />
Data = 6<br />
NOTE: In some cases we have set this value from 4 to 18. Adjusting this value<br />
too high will delay the call integration. Too low if the data is not<br />
present the call will not integrate.<br />
� Access the Serial General tab and set the following values:<br />
- Packet Format = SMDI<br />
- Extension Field Length in Packet = Number of digits in extension<br />
- Maximum Number of Remote Service Sessions = 0<br />
IMPORTANT: This must be the number of MAS’s in system minus MAS #1<br />
- Log Serial Packets = Enable by checking the box<br />
NOTE: If installing multiple MASs, enter the correct value. Example, if you have 2 MASs<br />
then enter 1; if you have 3 MASs then enter 2, etc.. The default is 0 if only 1 MAS.<br />
IMPORTANT: The MAS service must be restarted to allow port enabling<br />
� Next access the Serial Settings button<br />
1. Line Speed (Bits per Second) = 1200 (modem dependant)<br />
2. Data Bits = 7<br />
3. Stop Bits = 1<br />
4. Parity = Even<br />
5. Flow Control = None<br />
6. Connector = COM1<br />
7. Select OK to save changes<br />
After making these changes, return to “Configuring the voicemail system”<br />
within the Message Application Server Installation guide. Ensure you are<br />
prompted to restart the Message Application Server services to apply<br />
these changes.<br />
The above information is provided by AVAYA Inc. as a guideline. See disclaimer on page 1
Installing the integration data<br />
link on the MAS<br />
Important notes regarding this<br />
integration<br />
<strong>Intecom</strong> E 9<br />
7.0 INSTALLING THE INTEGRATION LINK<br />
� The data link connects to the PBX via a PDI I/O port within the CPU<br />
cabinet.<br />
� Find an available port on the PDI board to be used for the VMP I/O port.<br />
Any port can be used. Set the speed of the port at 1200 baud.<br />
� The data link connects from the PBX PDI I/O port within the CPU cabinet<br />
to the COM1 port of the MAS using the cable provided by <strong>Avaya</strong>.<br />
8.0 CONSIDERATIONS/ALTERNATIVES<br />
8.1 In InteCom Version 9 software, integrated ports are able to<br />
perform supervised transfers. However supervised transfers to<br />
stations that ring-no-answer or busy forward to the MAS will forward<br />
to the attendant instead. Enable this feature by answering YES to the<br />
VOICE TRUNK TRANSFER prompt in GRPS command.<br />
Below Version 9 software, integrated ports on the E cannot be used<br />
for supervised transfers. In the E software, the MAS ports are defined<br />
as trunks. Below Version 9 software, the E does not allow a trunk to<br />
reconnect with a ring-no-answer transferred call. Therefore, using<br />
integrated ports for supervised transfer applications will cause call<br />
disconnects, integration errors, and excessive port traffic.<br />
One alternative for systems below Version 9 software is to<br />
configure a separate ACD group of single-line ports (standard STE<br />
or OPX ports) to be used for supervised-transfer applications.<br />
However these ports must be dedicated to the supervised-transfer<br />
application and do not provide integration.<br />
8.2 Centralized MM integration to remote <strong>Intecom</strong>'s is supported if the<br />
remote node is a Survivable Switching Unit (SSU). SSUs uses the CPU<br />
of the main hub, on which the MM must integrate. Centralized MM is<br />
also supported to networked <strong>Intecom</strong>’s as long as these are connected via<br />
IXL/T1/PRI cards. All <strong>Intecom</strong>'s must have VMP Networking software.<br />
All switches should have extension numbers of the same length and no<br />
duplicate extensions in the network.<br />
8.3 MWI and invalid stations may cause integration issues. MWI should<br />
only be sent to valid stations. When a station is deleted on the PBX the<br />
mailbox must also be deleted. With <strong>PointSpan</strong> <strong>6880</strong> server type PBXs we<br />
have found that if an MWI is sent to an invalid station subsequent calls<br />
are sent from the PBX with corrupt information and may not integrate.<br />
The above information is provided by AVAYA Inc. as a guideline. See disclaimer on page 1
<strong>Intecom</strong> E 10<br />
8.4 Inside and Outside dial tone may be different. If it is then a tone file<br />
must be created in order for MM to recognize dial tone in order for<br />
outcalling to function.<br />
C H A N G E H I S T O R Y<br />
Revision Issue Date Reason for Change<br />
A 07/02/08 Initial release<br />
©2008 AVAYA Inc. All rights reserved. All trademarks identified by the ®, SM and TM are registered trademarks,<br />
servicemarks or trademarks respectively. All other trademarks are properties of their respective owners. The above information<br />
is based on knowledge available at the time of publication and is subject to change without notice. Printed in U.S.A.<br />
AVAYA Inc.<br />
1033 McCarthy Blvd<br />
Milpitas, CA 95035<br />
(408) 577- 7000<br />
http://www.avaya.com<br />
The above information is provided by AVAYA Inc. as a guideline. See disclaimer on page 1