Siemens Hicom 300/ 9006

Transcription

1 Avaya Modular Messaging Configuration Note Version K (02/08) This integration is not available for new sales or upgrades. This Config Note is ONLY available for MM field support. Contact product management for all other concerns. Siemens Hicom 300/ 9006 Digital Set Emulation (RP400) HiCom 300 E TRUNKS Digital Ports Automated Attendant Return to Operator Message Waiting Call ID Message Application Server Dialogic Boards COM Port Minimum Software Version 6.4 Supported Software Releases 1.1, 2.0, 3.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 Siemens certified or very familiar with the features and functionality of the Siemens 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. Important: Please read MM Product Support Note #612u found on to understand limitations using this integration. The Dialogic emulates the ROLMPhone 400 digital sets. 1.0 METHOD OF INTEGRATION The Dialogic emulates the ROLMPhone 400 digital display telephones. When a call arrives at the Dialogic, it passes a packet containing the call information provided by the Siemens Hicom 300 E PBX to the Avaya Message Application Server (MAS), which then answers with the proper greeting. The Dialogic then sends MWI on or off information to the Siemens PBX via a digital port from the PBX, which in turn sets the message lamps on the phones on or off. 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 Service Organization at (800) , and if appropriate we will include it in our next revision. AVAYA Inc. accepts no responsibility for errors or omissions contained herein.

2 Siemens Hicom 300 E - Set Emulation 2 Message Application Server Requirements 2.0 AVAYA MESSAGE APPLICATION SERVER REQUIREMENTS Dialogic D/82JCT-U PCI Line card (8 port card) Supported Releases: 1.1, 2.0, 3.0 PBX Hardware Requirements PBX Software Requirements 3.0 PBX HARDWARE REQUIREMENTS ROLMPhone 400 Interface channels, one per MAS port Cables: -One RJ11 cable per Dialogic port to connect the PBX digital ports to the 4-wire Cluster box. 3.1 PBX SOFTWARE REQUIREMENTS Supported Software: Version 6.4, 6.5 Dialogic requirements Supported integration features 3.2 DIALOGIC REQUIREMENTS Dialogic D/82JCT-U Set Emulation Card Dialogic D/82JCT-U Cable one per D/82JCT U card Dialogic CT-Bus drop down cable this is only required if you will have more than one D/82JCT-U card in your MAS 4-Wire RJ11 Cluster box/panel one per D/82JCT-U card, minimum of 8 ports per patch box/panel, not available from Dialogic Driver Version: FP1 SU 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 [ ] Auto Attendant Call Me Direct Call External Call ID (ANI) Fax

3 Siemens Hicom 300 E - Set Emulation 3 Find Me Internal Call ID Message Waiting Multiple Call Forward Multiple Greetings N+1 [ ] Outcalling Return to Operator IMPORTANT: PBX options or features not described in this Configuration Note are not supported with this integration. 5.0 CONFIGURING THE SIEMENS HICOM 300 E CS PBX Change the system Dial Plan and ADD the new station numbers (STNO) for the ROLMPhone 400, and extensions as well as the Hunt Group pilot number. Create a COS for the MAS ports. Create a ROLMPhone 400 Key layout Create one ROLMPhone 400 (SLMR) channel per MAS port and assign the Key layout (created in the previous step) Add the Prime line to ROLMPhone 400 Add an EVMS Index Add to the system dial plan 5.1 ADD TO THE SYSTEM DIAL PLAN Use the AMO "ADD-DPLN" to ADD new Station numbers with the following parameters: ADD-DPLN: DGTS: (first station no.)&&(last station no.) or Hunt No. DPLN: 0 CPS: Blank DAR: This will be either STN or HUNT CHECK N Allow all other fields to default. 5.2 CREATE A CLASS OF SERVICE FOR THE MAS PORTS Use the AMO "ADD-COS" ADD-COS: COPY-COS: Blank

4 Siemens Hicom 300 E - Set Emulation 4 NEW-COS: Assign a new COS number AVCE: MSGWCAP&INDTMF Allow all other fields to default. Create a key standard table for the ROLMphone 400 ports 5.3 CREATE A KEY STANDARD TABLE FOR THE ROLMPHONE 400 (SLMR) PORTS Use the AMO "CHA-KEPRO" CHA-KEPRO: STNO: Prime number of the ROLMPhone 400 STD: Assign a free "Key Standard Table" number KEYM1STD: (DEFAULT VALUE) KEYM2STD: (DEFAULT VALUE) KEYM3STD: (DEFAULT VALUE) KEYM4STD: (DEFAULT VALUE) DIGTYPE: RP400 KY01-KY08: VACANT KY09: LINE (PRIME) KY10: HOLDM KY11-KY29: VACANT KY30: CLEAR KY31-KY37: VACANT KY38: XFER KY39: VOLUP KY40: VOLDN KY41: VACANT Note: Execute the CHA-KEPRO command a second time. This will allow the database to update and assigns the PRIME LINE extension from KCSU (see step 5.5 for KCSU).

5 Siemens Hicom 300 E - Set Emulation 5 Vacant (1) Vacant (2) Vacant (3) Vacant(4) Vacant (5) ROLMPhone 400 Feature Table Vacant (11) Vacant (12) Vacant (13) Vacant (14) Vacant (15) Vacant (16) Vacant (17) Vacant (18) Vacant (19) Vacant (20) Vacant (21) Vacant (22) Vacant (23) Vacant (24) Vacant (25) Vacant (31) Vacant (32) Vacant (33) Vacant (34) Vacant (35) Vacant (6) Vacant (7) Vacant (8) Prime (9) Hold (10) Vacant (26) Vacant (27) Vacant (28) Vacant(29) Clear (30) Volume (39) Volume (40) Vacant (36) Vacant (37) Xfer (38) Key Numbers are shown in parenthesis (xx) Table 2 ROLMPhone 400 Features Create the ROLMPhone 400 (SLMR) features 5.4 CREATE THE ROLMPHONE 400 (SLMR) CHANNELS Use the AMO "ADD-SCSU" ADD-SCSU: STNO: Station Number LOCODE: Blank PEN: Port Equipment Number DPLN: 0 ITR: 0 COS1: (see step 5.2) COS2: As above COSX: Leave blank PUBSCR: C.O. Prefix + station no. NYTPE: NAT ACTCDE: Blank DCFWBUSY: N HTLNIDX: Blank EVMSIDX: 0 DEVFUNC: RPHONE EVMS: Y RPTYPE: RP400 SPDC1: Blank SPDC2: Blank SPDI: Blank LCRCOSD1: Blank LCRCOSD2: Blank LCRCOSV1: To be assigned

6 Siemens Hicom 300 E - Set Emulation 6 LCRCOSV2: VCP: DSSALERT: DTS: HDSTYPE: COMGRP: DNIDSP: TA: SPKALERT: To be assigned ON N N NONE Blank N This will allow forward-to-personal greeting for DNIS calls. N N Add the prime line to the ROLMPhone ADD THE PRIME LINE TO THE ROLMPHONE 400 Use the AMO "ADD-KCSU" ADD-KCSU: STNO: Prime Number TYPE: KEY PRIMEKEY: 9 RIOP: Y ORLNPF: PRIM TMLNPF: RING SGLBMOD: Y ROLRING: (DEFAULT) APRIVAT: N INS: Y AICS: N Create the hunt group 5.6 CREATE THE HUNT GROUP Use the AMO "ADD-HUNT" ADD-HUNT: TYPE: VCE (Voice) AC: Pilot Number DPLN: 0 STNO: See step 5.5 NAME: VOIC CQMAX: This is the maximum number of calls that are allowed to queue when all ports are busy FNA: N STYPE: CIR (Type of Hunting is Circular) 5.7 ADD THE EVMS INDEX Use the AMO "ADD-DEST"

7 Siemens Hicom 300 E - Set Emulation 7 ADD-DEST: TYPE: IDX: EVMSDEST: EVMS To be assigned See step 5.6 Pilot Number Please refer to the Consideration section at the end of this document for special PBX programming and considerations.

8 Siemens Hicom 300 E - Set Emulation 8 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. Access the Voice Mail System Configuration application from the MAS program group. Expand all fields so all-applicable options are visible. The following programming is a continuation from the Message Application Server Installation Guide: 1. Select the Voice Mail Domain 2. Expand PBXs 3. Select the newly created Siemens 9006 (Set Emulation) 4. Access the General (Set Emulation) PBX Configuration tab 5. DTMF Inter-Digit Delay during Dialing (ms) = DTMF Length during Dialing (ms) = DTMF Length during Detection (ms) = Port Disable Key = Leave Blank Next access the Transfer/Outcall tab 1. Transfer Mode = Blind 2. Start Delay for Call Progress = Initiate Transfer = ^Kn,L%s, 4. Initiate Blind Transfer = %s 5. Complete Transfer =, 6. Retrieve Call = ^Km,,, 7. Drop Call =, 8. Make Call Prefix = Leave Blank Next access the Tone Detection tab 1. Maximum Silence before Hanging Up (ms) = Maximum Tone before Hanging Up (ms) = Record Trim Length = 10, Select OK to save changes

9 Siemens Hicom 300 E - Set Emulation 9 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. Scheduled MWI updates: Active or Inactive = Configure as per customer requirements.* 4. Maximum Requests per Minute = 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 *Note: The Scheduled MWI updates parameter is only available on MM 3.x Return to the Voice Mail System Configuration window 1. Access Voice Servers 2. Select the General tab under the Telephony Interface (QSIG or Set Emulation) 3. Playback Volume = 2 4. Concurrent Calls = Enter the number of ports connected to the PBX Note: The MAS service must be restarted to allow port enabling 5. Port = Enable ports by checking the checkbox next to the ports 6. Select OK to save changes NOTE: We recommend at least 2 ports dedicated for Message Waiting by removing the highest 2 ports from the default port group and placing them in a port group of their own called e.g. MWI port group. Next access the Port Groups tab under the MAS name 1. Click Add Group Radio Button 2. Name Group MWI (or something you can remember) 3. Uncheck Incoming under Port Group Usage 4. Access the Port Group Usage tab and uncheck all Ports, except the port(s) you will be using for MWI. 5. Return to the Port Groups General tab and ensure the Default Group under Port Groups is checked for both Incoming and Outgoing under Port Group Usage. 6. Access the Port Group Usage tab and check all Ports, except the port(s) you will be using for MWI (see port enabling next). 7. Select OK to save changes

10 Siemens Hicom 300 E - Set Emulation 10 Return to the Voice Mail System Configuration window 1. Access the General tab within the PBX Integration tab 2. Set Emulation = Enable by checking the box 3. Access the QSIG/SE tab 4. Port Group Name = Enter the MWI Group defined for your system 5. Max MWI Session = 2 6. Indicator On/Off signals must use the same port = Enable by checking the box 7. MWI On = #*1,%s 8. MWI Off = #*8%s 9. Select OK to save changes After making these changes, return to Configuring the voic system within the Message Application Server Installation guide. Ensure you are prompted to restart the Message Application Server services to apply these changes. Important notes regarding this integration 8.0 CONSIDERATIONS/ALTERNATIVES 8.1 The Hicom 300 E CS does not allow a call to be transferred unsupervised to an extension that is busy and not busy forwarded. This is to prevent a caller from being transferred to a busy signal. Instead, the call will be sent back to the extension of the person attempting to transfer the call. This affects return-tooperator and unsupervised automated attendant transfers. Any station that can be reached through such applications must have busy forwarding targets programmed. Otherwise, callers might be returned to the MAS when attempting to transfer out of it. 8.2 Supervised transfers to busy subscribers are not supported. If supervised transfers are attempted failure of integration can result. 8.3 Supervised transfers to the attendant are NOT supported. 8.4 Stutter dial tone has a different cadence and overrides the message waiting broken dial tone. Subscribers may mistake this stutter tone for message-waiting indication. 8.5 This Integration requires the use of "Dedicated Message- Waiting Port(s)". 8.6 CorNet is an Inter-PBX ISDN Signaling System that provides feature transparency across a PBX network. All locally supported integration features are available over CorNet (when operating within a Hicom 300 E CS environment). In addition:

11 Siemens Hicom 300 E - Set Emulation 11 There are no additional MAS requirements necessary in order to work with CorNet. Mailboxes that have extensions on remote PBXs require those extensions to be in the Local PBX DialPLN. The remote extensions will require MB in their Class of Service (as do local extensions). Remote extensions will need to forward calls to the MAS hunt pilot number (as do local extensions). NOTE: Only CorNet is supported for networking. Other PBX networks are not supported. 8.7 Hicom 300 E CS at Release 6.4 may experience messagewaiting problems under high traffic. This is a PBX buffer issue, and requires patch PS10E65. The buffer, located in the DIMEN table, of the PBX is 3,816. Once the number of message-waiting commands nearly reaches that number, the MAS ports start getting busy or fast busy signals. 8.8 Transfers to off-premise locations are NOT supported. Locations connected via CorNet are not considered offpremise. 8.9 Avaya HIGHLY recommends the distribution of MAS ports within the PBX in order to help eliminate/minimize potential problems that may be experienced during periods of high traffic Avaya HIGHLY recommends the inclusion of the letter T at the beginning of the name field (AMO TGACC parameter NAME ) for ANY incoming trunk group in order to eliminate integration problems. Attendant consoles do not generate DTMF tones. Because of this PBX limitation, console operators can transfer callers into Open Trees, however, once the transfer is complete, callers must re-enter the mailbox number they are trying to access. Siemens Hicom 300 E CS switches do not provide a way for the MAS to detect turning on/off message waiting indicators for invalid extensions. Because of this, the MAS status log will not log errors even when failures occur while trying to operate message-waiting indicators. The MAS requires PBX subscribers to be configured as EVMS users with a Phon (PHML) key. When the MAS is

12 Siemens Hicom 300 E - Set Emulation 12 configured with dedicated multiple message waiting ports, the PBX must allow any of those ports to turn off message waiting indicators at the subscribers' station. The Siemens Hicom 300 ECS normally allows only the station that turned on the messagewaiting indicator at a subscriber's station to turn that same station's message waiting indicator off. Assigning the MAS HUNT GROUP an EVMS Index, and configuring the subscribers stations as EVMS users and a Phon (PHML) key eliminate this limitation. Queuing is NOT supported. The TSFFiles and the Disconnect values need to be set to "Yes" from the misc tab. To change these values the Dialogic cards need to be stopped and restarted. The Rolm-9751.tsf file needs to be selected from the files tab. To get the Rolm 9751 file go to: "look in" select local C: Drive, Avaya support, Tone files then Rolm-9751.tsf. You need to choose Rolm 9005 support when loading SP3.

13 Siemens Hicom 300 E - Set Emulation 13 CHANGE HISTORY Revision Issue Date Reason for Change DRAFT /03/03 Initial release for review/validation DRAFT /25/03 Added consideration 8.14 Find Me is not supported. DRAFT /05/03 Removed Extension & Incoming Ring Count fields, as these are not used. Also, Consideration 8.15 was added. DRAFT /04/04 Updates to meet MM R1.1, and make it clear that only CorNet is supported for PBX networking. Version A 06/01/2004 GA Version B 06/25/04 Added Consideration 8.16 Version C 07/21/04 Changed Transfer sequences and MWI On/Off codes as per development s input. Version D 09/17/04 Updated to meet MM R.2.0 Version E 10/05/04 Updated MWI Requests Per Minute to 12 Version F 11/19/04 Clarify the PBX brand name to Siemens 9006 as requested. Version G 12/06/04 Changed MWI On/Off codes to include s after each sequence as per product support input. Version H 07/01/05 Corrected Avaya PBX versus Siemens PBX verbiage. Version I 03/15/06 Added Important statement on page 1 referring to PSN612u found on website. Version J 04/11/06 Added: MM 3.0 to support release section 2.0 New bullet for Scheduled MWI updates parameter added in Section 6.0 and noted for MM3.0 Version K 02/15/08 This CN made Support Only. Added red note on page 1 to indicate this 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 McCarthy Blvd Milpitas, CA (408)