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

Transcription

1 Avaya Modular Messaging Configuration Note Version D (09/05) This integration is not available for new sales or upgrades. This Config Note is ONLY available for field support of MM 1.1. Contact product management for all other concerns. ROLM CBX 9751 (9005) Set Emulation (RP400) Rolm 9751 TRUNKS Digital Ports Automated Attendant Return to Operator Message Waiting Call ID Message Application Server Dialogic Boards COM Port Minimum Software Release xx Supported Release: 1.1 The Dialogic emulates the ROLMPhone 400 digital sets. 1.0 METHOD OF INTEGRATION The Dialogic D/82JCT-U Card 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 ROLM 9751 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 PBX via a digital port from the PBX, which in turn sets the message lamps on the phones on or off. Message Application Server Requirements 2.0 AVAYA MESSAGE APPLICATION SERVER REQUIREMENTS Dialogic D/82JCT-U PCI Line card (8 port card) Supported Release: 1.1 ONLY PBX Hardware Requirements 3.0 PBX HARDWARE REQUIREMENTS ROLMPhone 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. 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 ROLM Set Emulation 2 PBX Software Requirements 3.1 PBX SOFTWARE REQUIREMENTS Supported Software: Release xx and below 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 4.0 SUPPORTED INTEGRATION FEATURES Items are supported System Forward to Personal Greeting All Calls Ring/no answer Busy [ *] Busy/No Answer [ ] Note: Busy Forward is not supported. 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 Call Forward Multiple Greetings N+1 [ ] Outcalling Queuing [ ] Return to Operator 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.

3 ROLM Set Emulation CONFIGURING THE ROLM 9751 TO INTEGRATE The following PBX programming is intended for certified ROLM technicians/engineers. 5.1 ROLM CBX 9751 ADMINISTRATION The CBX must have the Internal Dial Tone parameter set to HIGH frequency, not LOW frequency. Otherwise, the MAS will not recognize dial tone. LOW frequency is the default value. Define the extension numbers that will connect to the MAS ports using the CR EXT command. Assign a class of service (COS) to each of these extensions. The COS must have the following feature: NOH - No Howler Tone if left off hook The COS must not have the following features: NFL - No Flash Allowed ACB - Automatic Camp-On APV - Always in Privacy TRM - Terminating Only Configuring the digital ports Create a ROLMPhone 400 feature table as shown in Table 2. The button placement must be exactly as specified, or the Dialogic will not function properly. NOTE: Ensure to configure the feature table with the MWCTR key, not the MSGWT key. MWCTR enables the RPI channel to set and cancel message waiting at subscribers' phones. ROLMPhone 400 feature table programming for the MAS:

4 ROLM Set Emulation 4 Rolmphone 400 Feature Table BTN FEAT BTN FEAT BTN FEAT BTN FEAT BTN FEAT *** *** *** 26 7 *** *** *** 27 8 *** *** *** LINE-001 *** *** *** MWCTR 10 HOLD 30 CNCT 38 XFER Table 2. ROLMPhone 400 Feature Table Using the CR RPI/RLI command, configure the ROLMPhone Interface channels connecting to the MAS ports. Note the following: TYPE RP400 TBL NO. The number of the feature table created in the previous step RING Yes MW Yes BI No CLD NAME Yes Configure the remaining ROLMPhone channels to be connected to the MAS ports. Assign all the newly created ROLMPhone interface channels, except for the channel(s) to be used as dedicated message waiting ports, to a Hunt/Distribution Group using the CR HD_G command. The pilot number of this Hunt/Distribution group is the MAS access number subscribers call to access the MAS. This is also the pilot number subscribers will use as the forwarding target for their extensions.

5 ROLM Set Emulation 5 Note1: The ROLM CBX allows up to 48 members in a Hunt/Distribution Group. If the MAS is equipped with more than 48 integrated ports, simply configure a second Hunt/Distribution Group, assigning the remaining ports to it. Then, assign the pilot number of this second Hunt/Distribution Group as the forwarding target for the MAS access hunt group. This is done within the HD_G screen, by configuring the following fields: FWD/BUSY C (condition) B (both internal and external calls) NUMBER Enter the second Hunt/Distribution Group pilot number. Note2: Ensure the subscribers do have other forwarding targets (i.e. hunt groups other than MAS hunt group) when assigning coverage. Save or backup these changes on the PBX 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. 1. Select the Voice Mail Domain 2. Expand PBXs 3. Select the newly created PBX 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) = 50 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,,

6 ROLM Set Emulation 6 7. Drop Call = ^KA 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) = Select OK to save changes NOTE The Max Req per Minute depends on how many MWI Ports are configured. Each MWI request takes 10 seconds. So that s 6 requests per minute per MWI port. (i.e. 4 MWI Ports = 24 MWI Req per Min) 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. Maximum Requests per Minute = (see side NOTE) 4. Message Application Servers that Support MWI = This box should contain a list of MAS servers capable of placing MWI requests. 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 General tab within the PBX Type tab 1. Under PBXs ensure 9005 is selected (highlighted) 2. Select OK to save changes 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.

7 ROLM Set Emulation 7 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. 7. Select OK to save changes 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 = Disable by clearing the box 7. MWI On = ^Kh,%s,^Kh, 8. MWI Off = ^Kh,%s,^Kh, 9. Select OK to save changes After making these changes, return to Configuring the voic system within the S3400 Message 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 following six patches are required on the ROLM 9751 Satellite Operations can be tailored to meet customer needs. The following features are supported for subscribers on the remote CBX: - Forward to personal greeting - Return to operator on the local CBX only - Direct call - Message waiting through outcalling See section 9.0 of this note for further information. 8.2 The ROLM CBX 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 will affect return to operator and unsupervised automated attendant transfers. Ensure any extensions to be used as

8 ROLM Set Emulation 8 attendants or any extensions that can be dialed from an unsupervised automated attendant mailbox have busy forwarding targets programmed. Otherwise, callers might be returned to the MAS when attempting to transfer out of it. 8.3 Avaya recommends using dedicated message-waiting ports. Although this is not an absolute requirement, if dedicated message waiting ports are not used, subscribers may experience long delays with message waiting indication during high-traffic periods. 8.4 Find Me feature is NOT supported. 8.5 Queuing is NOT supported. 8.6 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.

9 ROLM Set Emulation ADDENDUM A - SATELLITE OPERATIONS SOFTWARE One MAS can support two or more ROLM PBX s, provided all switches have Satellite Operations software and all remote systems have Off- Premise Forwarding (Off-system Station Forwarding). The MAS must be integrated and located at the main PBX. Use the following procedure referencing the diagram below. ROLM 9751 CBX with Satellite Operations Software 9751 CBX Remote Tie Trunk Circuits 9751 CBX Main MAS Pilot # 4000 Extn 2000 Hunt Group 1000 Fwd B/RNA to exten 1000 From ATC (or station with Control of Station Features) Dial: # Hunt Group 3000 Mbx 3000 transfers to Mbx 2000 Mbx 2000 One hunt group (with no members) per remote subscriber must be created at both the remote and the main site. At the remote CBX, the hunt-group pilot number must be off-system station forwarded to the hunt-group pilot number at the main site using the Invoke Call Forward command (a Control of Station Features (CSF) command). The hunt-group pilot number at the main site must system forward on a busy condition to the MAS pilot number. A transfer mailbox should be created for each remote subscriber that matches the pilot number of the subscriber s hunt group at the main site. This transfer mailbox should have as its Transfer Mailbox Number the subscriber s mailbox number. With the use of transfer mailboxes, remote subscribers mailbox numbers will match their extension numbers. To forward their stations to personal greeting, subscribers system or station forward their extensions to their own individual hunt group at the remote site. Message Waiting Notification at the remote CBXs will only be possible through outcalling. Return to operator is possible only to the main CBX site. This process prevents callers from being sent back to the MAS (system greeting) when all tie trunks are busy. Additionally, the ROLM CBX does not allow a blind transfer across the tie trunks. NOTE: This procedure uses a large number of hunt groups (for phantom extensions) in the main and remote CBX(s). If a remote CBX

10 ROLM Set Emulation 10 has a large number of extensions, this might not be practical. It might be better to utilize two MAS systems. NOTE: The remote or main CBX may be a CBX II 8000 or CBX II Lexes (logical, or phantom, extensions) should be used on the CBX II 8000 in place of hunt groups. CHANGE HISTORY Revision Issue Date Reason for Change DRAFT /02/03 Initial release for review/validation DRAFT /24/03 Transfer Sequences revised. Updated PBX configuration as per beta site. DRAFT /14/04 Added PBX Type programming in Section 6.0 DRAFT /15/04 Added: Busy Forward is currently not supported under section 4.0 Version A 06/01/04 GA Version B 06/25/04 Added Consideration 8.6 Version C 04/25/05 This Config Note is available for field support only. This is a discontinued integration for new sales or upgrades. Contact product management for other concerns. Version D 09/05/05 Updated the MWI Request per minute 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)