Intecom E / PointSpan 6880

Similar documents
Cisco CallManager w/vg-248

Nortel DMS-100, SL-100 & DMS-250, DMS-500

Mitel SX200D / SX200 Light

AVAYA Merlin Legend/Magix

Toshiba DK280/424 with SMDI

Sopho-S/iS3000 Series

Cisco Call Manager T-1 / QSIG. Configuration Note Rev. K (07/08)

Cisco Call Manager T-1 / QSIG. Configuration Note Rev. M (7/09)

Cisco Call Manager T-1 / QSIG. Configuration Note Rev. O (1/10)

ROLM CBX 9751 (9005) Set Emulation (RP400) Configuration Note Version D (09/05)

Cisco Call Manager E1/QSIG - EMEA. Configuration Note Version M (1/10)

Cisco CallManager & VG-248 Gateway

Siemens Hicom 300/ 9006

Configuration Note Iwatsu ADIX * / ADIX M *

Mitel 200 Light. Voice Board(s) Analog Ports. Personal Computer. Configuration Note Mitel SX200 Light * ONS. Revised 6/2/99

Lucent 5ESS. with 3A Translator. Configuration Note Ver. D 6/06

Smooth Operator Configuration Note

Inter-Tel IMX 1224/2448/2460*

Smooth Operator Configuration Note

Mitel SX-2000/SX-2000 LIGHT

Smooth Operator Configuration Note

Smooth Operator Configuration Note

Mitel SX-200D*/SX-200 Light*

Smooth Operator Configuration Note

Smooth Operator Configuration Note

AVAYA MultiVantage S8700/S Set Emulation

Panasonic KX-T30810/T61610 *

AVAYA IP600 - Set Emulation

Lucent Merlin Legend. Configuration Note Lucent Merlin Legend. Revised 1/24/00

Smooth Operator Configuration Note

Setting Up a Serial (SMDI, MCI, or MD-110) PIMG Integration with Cisco Unity Connection

Serial and Inband Switch Integration

8 Digital Station Lines

DuVoice Voice Mail provides hospitality and business messaging for the Avaya IP Office, as well as unified messaging and fax capabilities.

Nortel M1 -- Set Emulation

Chapter TIMG BOILERPLATE

Integration Note. Title: Panasonic KX-TD Integration. Overview. Theory of Operation. PBX Requirements and Programming. Programming

Voice Mail System User s Guide

Setting Up an Avaya Definity ProLogix Digital PIMG Integration with Cisco Unity Connection

NEC SV8300 SIP Integration

2018/06/14 00:32 1/2 KX-TDA TAPI

VME-Pro. Application Notes VERSION 1 JUNE, 2005

Panasonic KX-TDA TAPI

Configuration Note 6102 Rev. D (12/03) GPT isdx - DPNSS (UK & Ireland)

Application Notes for Objectworld UC Server with Avaya IP Office Using TAPI Analog Integration Issue 1.0

Atlas AVM JR. Installation and Programming Manual

Abstract. Avaya Solution & Interoperability Test Lab

A Sample Configuration for Computer Instruments e-ivr Automated Attendant and Voic 3.0 with Avaya IP Office System Issue 1.

Unified Messaging Voice Mail System Installation and Programming Manual. Version 1.3 August 2003 Proprietary

Application Notes for DuVoice DV2000 with Avaya Communication Manager Using Digital Station Interface Issue 0.2

Setting Up a Mitel SX-2000 Digital PIMG Integration with Cisco Unity Connection

Configuring the Telephony Settings on the VG248

Avaya Unified Messenger Client User Guide

Avaya Aura Messaging Web Interface

NVM-2e Installation Instructions and Release Notes for Versions 1.08, , and 1.20

Using Avaya one-x Agent

Win Series Integration Note ... Mitel DNIC Set Emulation w/vbpc

Setting up Alcatel 4400 Digital PIMG Integration

East-Central Vermont Community Fiber-Optic Network

Digital Telephone User Guide

Internet Phone. User Guide

Setting Up an Alcatel 4400 Digital PIMG Integration with Cisco Unity Connection

Application Notes for DuVoice DV2000 with Avaya Communication Manager Using Analog Mode Code Integration Issue 1.0

Application Notes for MultiTech CallFinder CF220 with Avaya IP Office - Issue 0.1

TABLE OF CONTENTS Introduction: Default Operation and Remote Programming Programming Receptionist Extensions Installing CallExtend

Nortel Networks Integrated Call Director

Installing And Programming The Digital Voice Announce Equipment On The DXP, DXP Plus, And FX Series Systems

COMPLEX SYSTEMS ONE SOLUTION

IVX X-Class Installer worksheets

Application Notes for Configuring Objectworld CallAttendant Office Analog Integration with Avaya IP Office - Issue 1.0

TC-308, TC-616 TC-308-VM, TC-616-VM TC-616-NHR, TC-616-NHR-VM

Caller dialled digit during recording. Fax routing Config? Yes. Route to Fax Extensions

SoLink-Lite IP-PBX. Administrator Guide. (Version 1.0)

Administration. Overview

TELUS Voice Mail User Guide

PARTNER Messaging User Guide

VME Office Installation and Programming Manual. Version 1 Release 1.2 December 2002 Proprietary

EAR Installation and Programming Manual

A Sample Configuration for Computer Instruments e-ivr Automated Attendant and Voic 3.0 with Avaya MERLIN Magix Issue 1.

Integration Guide 1 ONLINE DOCUMENT. To print this book. a b

Axxess Phone Instructions (NOT ALL PHONES HAVE ALL FEATURES)

TELEVANTAGE CTM SUITE USER S GUIDE

CommPortal User Guide

ORIGINAL ADMINISTRATOR MANUAL

Integration Notes-Switch # 925

Managing your PBX- Administrator

Enterprise Edge 2.0 Voice Messaging Set Up and Operation Guide

Digital Voice Services Residential User Guide

DX-80 TM Hard Drive Voice Mail Installation and Supervisor Guide

Custom Calling Services

Application Notes for Configuring the ADTRAN NetVanta UC Server with Avaya IP Office 6.1 Issue 1.0

XN120 PC Pro with Quick Installer Guide Rev 1.2 (September 2005)

APPLICATION NOTE No

KX-HTS824 KX-HTS32. Feature Manual. Hybrid IP-PBX. Model No.

Application Notes for BBX Technologies Vuesion Multimedia Contact Center with Avaya IP Office 8.0 Issue 1.0

How to Configure an Avaya TM IP600 Server With MultiTECH Systems MVP200 Gateway - Issue 1.0

XN120 PC Pro Guide Getting Started Rev 1.2 (January 2007)

PARTNER Messaging System User s Guide

Administration for the Nortel Norstar Switch

VMS User s Guide: PMM Utility

Transcription:

Avaya Modular Messaging Configuration Note 88058 Version B (2/09) Intecom E / PointSpan 6880 Intecom E / PointSpan 6880 TRUNK Analog Station Automated Attendant Return to Operator Message Application Server Voice Board CPU I/O Port Minimum Software: Version 9 RS-232 Circuit Call Message Waiting CO Port See Section 2.0 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 Intecom PBX Administration Guide. Please read the entire document before attempting any configuration. With RS-232 integration, call information is transmitted over a digital RS-232 link between the PBX and the Avaya Message Application Server 1.0 METHOD OF INTEGRATION With RS232 integration, call information is transmitted over a digital RS-232 link between the PBX and the Avaya Message Application Server (MAS). Voice communications are provided over separate analog lines on the PBX that connect to the MAS. When an incoming call is received, it is accompanied by a digital message from the PBX containing call information. The MAS then answers the call and plays the appropriate 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 (800) 876-2835, and if appropriate we will include it in our next revision. AVAYA Inc. accepts no responsibility for errors or omissions contained herein.

Intecom E 2 greeting. The RS-232 link also handles on & off message waiting indication. MAS Requirements 2.0 AVAYA MESSAGE APPLICATION SERVER REQUIREMENTS Integration cables (PN 057-1580-000 & 003-1081-000) Dialogic D/41JCT-LS or D/120JCT-LS cards (4 and 12 port/cards) Software Release MM 2.0, 3.x, 4.0, 5.0 Dialogic Driver Version: 5.1.1 FP1 SU15 PBX hardware requirements 3.0 PBX HARDWARE REQUIREMENTS OPX line appearances P/N 300-0325-001(16 ports per card), one port per MAS port One PDI (Programmable Data Interface) per VMP interface-1000s DCE P/N 520-1000-004 The customer must provide the necessary hardware. Cables: - RJ11 four-wire telephone cord, one per MAS port - DB 25 cable, one per RS-232 link PBX software requirements 3.1 PBX SOFTWARE REQUIREMENTS Minimum Software: Version 9.0 VMP Interface Software option package, P/N 993-0012-310 - continued on next page - Supported integration features

Intecom E 3 4.0 SUPPORTED INTEGRATION FEATURES [] Items are supported System Forward to Personal Greeting All Calls [ ] Ring/no answer [] Busy [] Busy/No Answer [ ] Station Forward to Personal Greeting All Calls [] Ring/no answer [ ] Busy [ ] Busy/No Answer [ ] Auto Attendant [] Call Me [] Direct Call [] External Call ID (ANI) [] Fax [] Find Me [ ] Internal Call ID [] Message Waiting [] Multiple Greetings [] Multiple Call Forward [] N+1 [ ] Outcalling [] Return to Operator [] - continued on next page -

Intecom E 4 Configuring the PBX 5.0 CONFIGURING THE PBX TO INTEGRATE The following programming is required to successfully integrate with an InteCom E/Nexspan. Refer to PBX s System Database Manual for further information. This programming is intended for certified PBX technicians/engineers. At the PBX man machine terminal, create a bi-directional trunk group for the MAS voice lines. Set the trunk group type to 'Mail' for the InteCom E/Nexspan. When prompted for InteMail Interface Number (IIN), enter '20' for the InteCom E/Nexspan. Create a trunk port for each MAS voice line. When programming the E, special attention must be paid to assigning VMP (Voice Message Product) trunks for the MAS ports. The InteCom E sends a seven-digit trunk port number as part of the Calling Party Identification (CPID) message. This seven-digit number identifies the location of the particular VMP trunk, or MAS port, that a call is ringing. The numbering format is as follows: AABCCDD where AA is the two-digit cabinet number; B is the one-digit shelf number; CC is the two-digit card slot number; DD is the two-digit offset of the trunk port. Each VMP trunk that is used as an MAS port must send a trunk port number with unique last four digits, i.e., the card slot and offset must be unique for each trunk used to connect to the MAS. Set up a prefix digit table for the trunk group. The table should have zero (0) significant figures. Assign a route guide to the trunk group. When prompted, use the trunk group and prefix digit table numbers created in the above steps. Create the satellite directory group associated with the trunk group. Enter the route guide number created above. When prompted, designate the directory group for direct call types. Assign an extension (pilot) number to the satellite directory group (SDG). NOTE: This pilot number is the MAS access number. It is used for two purposes. First, subscribers stations are forwarded to this number. Second, station users transfer calls to this number when callers wish to be transferred to the MAS.

Intecom E 5 Enable Transfer Supervision on the PBX Assign a user group for the MAS. When prompted, enter the satellite directory group number created above. This user group number must be entered when creating the bi-directional trunk group, the trunk ports, the satellite directory group, and the satellite directory group extension number. Nail the PDI to the appropriate voice mail link. Assign a voice class of service for the MAS subscribers. Enter Yes when prompted to allow voice mail access and voice mail auto sign-on. In addition, verify the Pass-thru Option in the voice class of service is set to YES. If it is not, the subscribers will not have DTMF capability while accessing the voice module. Modify subscriber s extension profiles to include the MAS user group number and class of service. Call forward the extension to the satellite directory group extension number on busy and no answer. Enter the extension number in the VID...InteMail ID for VOICE LINE field. Display the voice mail submenu (ITMR). Verify all entries including InteMail Interface Number (IIN), user group, trunk group, satellite directory group, and satellite directory group extension number are correct. Enable transfer supervision by answering YES to the following prompts: Voice Trunk Transfer enabled? Does Intermail supervise transfers? Once you answer YES to the last prompt you will be asked to enter the 'method to cancel transfer?' Two options will appear: 'F' (for Flash) or 'F and feature code' Select 'F'. Programming the Direct Call feature 5.1 PROGRAMMING THE DIRECT CALL FEATURE The PBX has a direct call feature that places subscribers directly into their own mailbox. Subscribers dial *5 or depress a special button on their ITE set to invoke direct call. The MAS will immediately play the subscriber s name and ask for their password. If a subscriber is at another station, he can simply dial the MAS access number followed by #, mailbox number, and password to retrieve messages. Configure button templates with a voice mail feature button for direct call access for ITE phones, if desired.

Intecom E 6 If you require two hunt groups supported by one RS232 link on the InteCom PBX, create the second hunt group 5.2 CREATING A SECOND HUNT GROUP If you require two hunt groups supported by one RS232 link on the InteCom PBX, create the second hunt group with the following directions. Such set-up may be desire to support a second hunt group of Fax-enabled ports: Create a Satellite Directory Group, and direct it, using the route guide, to a trunk group containing the second group of MAS ports. In the Trunk Group parameters, for InteMail type, enter 2 - SMDI type. For the InteMail Interface number field, set the value to 1. Then, call forward appropriate phones on busy and ring-no-answer conditions to the Satellite Directory Group. 5.3 MESSAGE WAITING ON THE PBX Three types of message-waiting indication are available. For ITE sets with LCD displays, the phrase voice message will appear in the display. For regular ITE sets, the InteMail feature button will light. For analog STE sets and single line digital ITE4 sets, the phrase voice message will be heard when the phone goes off-hook. Configuring the MAS 6.0 CONFIGURING THE MESSAGE APPLICATION SERVER 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. Expand all fields so all-applicable options are visible. 1. Select the Voice Mail Domain 2. Expand PBXs 3. Select the newly created Intecom 4. Access the General PBX Configuration tab 5. Go Off Hook when Port Disabled = Enable by checking the box 6. Pause before Digits (ms) = 500 7. Pause Interval for Comma in Dial String (ms) = 1000 8. DTMF Inter-Digit Delay during Dialing (ms) = 80 9. DTMF Length during Dialing (ms) = 80 10. DTMF Length during Detection (ms) = 50

Intecom E 7 Call Transfer settings: With some Intecom/PointSpan PBXs the settings shown to the right may need to be modified to accommodate the PBX s dial plan. Next access the Call Transfer tab 1. Transfer Mode = Blind 2. Transfer Prefix Code = &,XN 3. Transfer Complete Code = (leave blank) 4. Transfer Release Code when Busy = &,& 5. Transfer Release Code when No Answer = &,& 6. Transfer Release Code when Reject = &,&,,, 7. Flash Time Interval (ms) = 500 8. Enable Call Progress = Enable by checking the box 9. Start Delay for Call Progress (ms) = 1000 Next access the Hangup Detection tab 1. Maximum Continuous Tone before Hanging Up (ms) = 6000 2. Hangup String = Leave Blank 3. Hangup String Timeout (ms) = 0 4. Minimum Duration For Drop in Loop Current (ms) = 300 5. Maximum Silence before Hanging Up (ms) = 6000 6. Select OK to save changes Support NOTE for MM 1.1 & 2.0 only: Limit Requests should be checked. Maximum Requests per Minute should be set for 200. Next access the Message Waiting Indicator (MWI) tab 1. Enable Message Waiting Indicator (MWI) = Enable by checking the box 2. MAS MWI Server = Enter the name of the MWI server created during the installation procedure. 3. Limit requests = Leave Unchecked 4. Maximum Requests per Minute = <grayed out> 5. Message Application Servers that Support MWI = This box should contain a list of MAS servers capable of placing MWI requests 6. Select OK to save changes Next access the Port Groups tab under the MAS name 1. Access the Port Groups General tab and ensure the Default Group under Port Groups is checked for both Incoming and Outgoing under Port Group Usage 2. Access the Port Group Usage tab and check all Ports (see port enabling next) 3. Select OK to save changes

Intecom E 8 Next access the Voice Mail System Configuration window 1. Access Message Application Servers 2. Select the General tab under the Telephony Interface (Dialogic Analog) 3. Playback Volume = 2 (Default) 4. Number of Ports = Enter the number of ports in your system - Enable the port(s) by checking the Box field next to the Port field - Extension = Enter the proper ext # assigned to each port - Incoming Ring Count = 1 - Primary ID = Enter Logical Terminal Number (LTN) for that port (normally LTN starts with 0001 for first port, 0002 for second port, 0003) - Secondary ID = Enter 001 Message Desk (MD) number for all ports. NOTE: The Secondary ID must be 3 digits in length (standard SMDI protocol), however the actual value could be different then 001 (i.e. 002, 999, etc.) Select OK and Save changes Return to the Voice Servers section and access PBX Integration. 1. Access the General tab. 2. Select Serial as the Integration Type. 3. Maximum Time to Wait for Serial and Remote Integration Data = 6 NOTE: In some cases we have set this value from 4 to 18. Adjusting this value too high will delay the call integration. Too low if the data is not present the call will not integrate. Access the Serial General tab and set the following values: - Packet Format = SMDI - Extension Field Length in Packet = Number of digits in extension - Maximum Number of Remote Service Sessions = 0 IMPORTANT: This must be the number of MAS s in system minus MAS #1 - Log Serial Packets = Enable by checking the box NOTE: If installing multiple MASs, enter the correct value. Example, if you have 2 MASs then enter 1; if you have 3 MASs then enter 2, etc.. The default is 0 if only 1 MAS. IMPORTANT: The MAS service must be restarted to allow port enabling Next access the Serial Settings button 1. Line Speed (Bits per Second) = 1200 (modem dependant) 2. Data Bits = 7 3. Stop Bits = 1 4. Parity = Even

Intecom E 9 5. Flow Control = None 6. Connector = COM1 7. Select OK to save changes After making these changes, return to Configuring the voicemail system within the Message Application Server Installation guide. Ensure you are prompted to restart the Message Application Server services to apply these changes. Installing the integration data link on the MAS 7.0 INSTALLING THE INTEGRATION LINK The data link connects to the PBX via a PDI I/O port within the CPU cabinet. Find an available port on the PDI board to be used for the VMP I/O port. Any port can be used. Set the speed of the port at 1200 baud. The data link connects from the PBX PDI I/O port within the CPU cabinet to the COM1 port of the MAS using the cable provided by Avaya. Important notes regarding this integration 8.0 CONSIDERATIONS/ALTERNATIVES 8.1 In InteCom Version 9 software, integrated ports are able to perform supervised transfers. However supervised transfers to stations that ring-no-answer or busy forward to the MAS will forward to the attendant instead. Enable this feature by answering YES to the VOICE TRUNK TRANSFER prompt in GRPS command. Below Version 9 software, integrated ports on the E cannot be used for supervised transfers. In the E software, the MAS ports are defined as trunks. Below Version 9 software, the E does not allow a trunk to reconnect with a ring-no-answer transferred call. Therefore, using integrated ports for supervised transfer applications will cause call disconnects, integration errors, and excessive port traffic. One alternative for systems below Version 9 software is to configure a separate ACD group of single-line ports (standard STE or OPX ports) to be used for supervised-transfer applications. However these ports must be dedicated to the supervised-transfer application and do not provide integration. 8.2 Centralized MM integration to remote Intecom's is supported if the remote node is a Survivable Switching Unit (SSU). SSUs uses the CPU of the main hub, on which the MM must integrate. Centralized MM is also supported to networked Intecom s as long as these are connected via IXL/T1/PRI cards. All Intecom's must have VMP Networking software.

Intecom E 10 All switches should have extension numbers of the same length and no duplicate extensions in the network. 8.3 MWI and invalid stations may cause integration issues. MWI should only be sent to valid stations. When a station is deleted on the PBX the mailbox must also be deleted. With PointSpan 6880 server type PBXs we have found that if an MWI is sent to an invalid station subsequent calls are sent from the PBX with corrupt information and may not integrate. 8.4 Inside and Outside dial tone may be different. If it is then a tone file must be created in order for MM to recognize dial tone in order for outcalling to function. C H A N G E H I S T O R Y Version Issue Date Reason for Change Version A 07/02/08 Initial release Version B 02/02/09 Updated to support MM 5.0; Changed Limit Requests for MWI in Section 6.0 2009 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. Printed in U.S.A. AVAYA Inc. 1033 McCarthy Blvd Milpitas, CA 95035 (408) 577-7000 http://www.avaya.com