Page 1 Integration Octel 200 and Octel 300 Message Servers Installation and Maintenance Manual S.4.1 March 2001 Avaya Inc. Communication Applications Group 1001 Murphy Ranch Road Milpitas, CA 95035-7912 USA...
Page 2 Intellectual property related to this product (including trademarks) and registered to Lucent Technologies Inc. has been transferred or licensed Avaya Inc. does not warrant that this product or any of its networked to Avaya Inc. equipment is either immune from or will prevent either unauthorized or Any reference within the text to Lucent Technologies Inc.
Page 3: Table Of Contents
..............Octel 200/300 PBX Interaction in Standard DTMF Integration .
Page 4 7.2.4 Octel 200/300 System Configuration ............
Page 5 ..............The Octel 200/300 Configuration for Millennium Integration .
Page 6 11.4 Octel 200/300 Configuration ..............
Page 7 15.2 Octel 200/300 Message Server Configuration ..........
Page 8 ............Octel 200/PBX Interaction — Standard DTMF Integration, Secondary Answering Only .
Page 9 7.2-7 Station Data Entry Screen for an Octel 200/300 Port Extension ....... . .
Page 10 Message Server and ND110 Connections for Voice Mail Integration ....... 14-1 Octel 200/300 S.4.1 PB60019-01...
Page 11 5-16 The Octel 200/300 Configuration Changes for MWI ..........
Page 12 8.1-5 Octel 200/300 Configuration Changes to MWI ..........
Page 13 10.1-4 Octel 200/300 Configuration Changes for MWI and CPI ........
Page 14 ........... 17−12 Octel 200/300 S.4.1...
Page 15 INTRODUCTION The Octel 200/300 Installation and Maintenance Manual, Integration volume, contains information about how Octel 200/300 integrates with specific telephone systems. The following is a brief summary of each chapter within this volume. Chapter 1 This chapter discusses Octel 200/300 integration without the use of Standard DTMF special Serenade software.
Page 16 Chapter 8 This chapter discusses the Adaptive Integration connection between ROLM CBX, ROLM 9751, Octel 200/300 message servers and the ROLM CBX and the ROLM Models 30/80 9751, Model 30 and Model 80. This connection is provided by Octel’s ROLM Interface Card (RIC).
Page 17: Chapter 1 Standard Dtmf Integration
............Octel 200/PBX Interaction — Standard DTMF Integration, Secondary Answering Only .
Page 19: Standard Dtmf Integration Vs. Adaptive Integration
Standard DTMF Integration uses Octel 200/300 standard features only. Adaptive Integration may also require additional hardware, consisting of additional cabling. Message Waiting Indication. In a standard Octel 200/300, when the first new message is left in a mailbox, ringing message waiting notification (MWN) is provided. The Octel 200/300 calls the extension of the mailbox with a new message and, if the call is answered, plays a prompt indicating that there are messages in the mailbox.
Page 20: Standard Dtmf Integration
Octel 200/300. When this information is provided in DTMF tones preceding the forwarded call, the Octel 200/300 can process the call as if a caller had entered the called extension. A standard integrated Octel 200/300 can be configured to accept these forwarded calls in CX or MX mode.
Page 21: Octel 200/300 Pbx Interaction In Standard Dtmf Integration
OCTEL 200/300 PBX INTERACTION IN STANDARD DTMF INTEGRATION This section explains how the phone system and the Octel 200/300 interact when switching calls from the Octel 200/300 port to a called station in standard DTMF integrated environments. Primary and Secondary Answering. Figure 1-1 illustrates the interaction between the Octel 200/300 and the PBX in a standard DTMF integration installation, where both Primary and Secondary Answering modes are used.
Page 22: Octel 200/Pbx Interaction - Standard Dtmf Integration, Secondary Answering Only
On a busy or no answer, the extension is programmed to automatically forward calls to the Octel 200/300 pilot number (e.g., 2500) for Secondary Answering. When the call is forwarded, the PBX tells the Octel 200/300 which extension the call was forwarded from. There is no need for the caller to reenter the extension number.
Page 23: Chapter 2 Adaptive Integration
........2-11 Figures Octel 200/300/PBX Interaction in Enhanced DTMF In-band Integration Environment ....Octel 200/300/PBX Interaction in RS-232C Data Link Integration Environment .
Page 25: Adaptive Integration
DTMF mailbox digits prefixed to a call. Depending on the method a particular PBX uses to send call records and control indicators, the Octel 200/300 may be equipped with proprietary integration cards or an RS-232C data link, in addition to Adaptive Integration software.
Page 26: Ai Features
Integration Volume AI Features AI introduces additional features. These features offer shortcuts for high-use Octel 200/300 functions. Quick Logon. Allows a mailbox holder to press to immediately log on to the mailbox identified by the calling extension number. After pressing , the caller is prompted for their security code.
Page 27: Types Of Adaptive Integration
The call record is sent over the ports in the form of DTMF tones. MWI commands are sent by the Octel 200/300 over the ports as well. All ports can be placed in a single hunt group because the information in the call record determines how the call will be answered.
Page 28: Octel 200/300/Pbx Interaction In Rs-232C Data Link Integration Environment
Depending on the information in the call record (called party ID, called party status, calling party ID), the Octel 200/300 can customize how the call is answered, letting the caller know that the person was busy or didn’t answer, as well as provide identification of an internal caller in the message.
Page 29: Octel 200/300 System Proprietary Card Integrations
For MWI, Octel 200/300 sends a call record over the data link to the PE or PBX, telling it which station’s lamp (or stutter dial tone) to turn ON or OFF.
Page 30: Octel 200/300/Pbx Interaction In Octel 200/300 Proprietary Card Integration Environment
(trunk group ID, called party ID/status, calling party ID). For MWI, the Octel 200/300 sends a call record over the digital line to the PBX, telling it which station’s lamp (or stutter dial tone) to turn ON or OFF.
Page 31 Number of OFF commands in the longest round trip. commands Current msg waiting time Start time for the current round trip. Current user number This is a hexadecimal mailbox number for the current mailbox being (hex) looked at. PB60019-01 Octel 200/300 S.4.1...
Page 32 Because the longest round trip time listed is only changed if a longer round trip time is logged, the time listed might not reflect current activity. The round trip log must be cleared to review recent activity. Use the C RT command to clear the round trip log. Octel 200/300 S.4.1 PB60019-01...
Page 33: Octel 200/300 Responses For Integrated Calls
The exact prompt varies according to how the Octel 200/300 is configured. When an extension is busy and the mailbox has a name recorded, the prompt can be either “(name) is busy” or “(name) is on the phone.” System Parameter 115 must be set to YES for the prompt “is on the phone”...
Page 34: Called Party Identification
Network Name Confirmation feature must be installed for the calling party ID to be recognized. When the calling party ID is not found in the USER Table, the Octel 200/300 searches the Network Names Table for the calling mailbox ID. If the calling party ID is found in the Network Names Table, the network mailbox and recorded name, if any, are associated with the call.
Page 35: Mailbox Features Available With Adaptive Integration
Quick Logon to Mailbox, Quick Greeting Activation, and Auto Logon allow shortcuts for mailbox logon and mailbox greeting by accessing the mailbox identified by the calling extension immediately, without requiring the standard logon procedure. PB60019-01 Octel 200/300 S.4.1...
Page 37 3-11 Octel 200/300 Configuration ..............
Page 39: Chapter 3 Enhanced Dtmf In-Band Integration
DTMF call records from the PBX are received directly on the Octel 200/300 line card (LIC), just prior to the call they describe. No special Octel 200/300 hardware or data connection is required to implement Enhanced DTMF In-band Integration.
Page 40: Enhanced Dtmf In-Band Integration Capabilities
Record Call-in-Progress. For PBXs that support the feature, record call-in-progress allows the Octel 200/300 to be conferenced into an existing call and begin recording a message to be placed in the called party’s mailbox. The Octel 200/300 plays beep tones to inform all parties that the call is being recorded.
Page 41: In-Band Integration Operation
When the Octel 200/300 answers a call on a port configured for Enhanced DTMF In-band Integration, it expects to receive a DTMF call record. If the Octel 200/300 receives either an invalid call record or no call record before a specified timeout, the port reverts to a non-integrated status and plays the default company greeting.
Page 42: Call Record Type Actions
None Mailbox Does Not Exist Re- None Link Supervision Requests None Link Supervision Reply None * Not pegged by any single traffic peg, but included in Peg 1. Specific to enhanced in-band integration with MATRA PBX. Octel 200/300 S.4.1 PB60019-01...
Page 43: Pbx Considerations For Enhanced Dtmf In-Band Integration
DTMF call records. If a PBX provides for two separate internal call records, the Octel 200/300 can be configured with Call Type 2 for direct internal calls and Call Type 12 for automatic logon. If a PBX provides one kind of internal call record, Call Type 2 can be configured, and COS Attribute 110 —...
Page 44: The Dtmfint Table
The key to understanding the DTMFINT Table is to recognize that the order of elements in a call record format specified by the PBX manufacturer is the pattern that the DTMFINT Table must reproduce. The string of DTMF digits sent by the PBX to the Octel 200/300 contains some or all of the following items: Call type code...
Page 45 Defines miscellaneous or other digits. These digits correspond to information that the PBX generates in its call record, but is not used by the Octel 200/300. These elements may be defined as MISC or may identify the specific digits to be received.
Page 46 Specifies the DTMF digit(s) used to delimit a fixed length definition. Acceptable values are 0−9, A−E, *, or #. The delimiter DTMF digit also defines the DTMF digit the Octel 200/300 expects the PBX to use to pad an element that would otherwise not contain enough digits.
Page 47 Table 3-2 summarizes call record types and their required and optional fields. Beginning with Serenade Release 3.0, call record types 13 through 19 have been added to support enhanced DTMF in−band integration with MATRA PBX. PB60019-01 Octel 200/300 S.4.1...
Page 48: Required And Optional Fields For Call Record Types
18 — Link Supervision Optional Request 19 — Link Supervision Reply Optional * Not applicable. Element types marked with an asterisk are not allowed and will be rejected during configuration. Specific to enhanced in-band integration with MATRA PBX. Octel 200/300 S.4.1 PB60019-01...
Page 49: How To Configure The Dtmfint Table
Use the MODIFY command to establish default values for the DTMFINT Table according to the PBX connected to the Octel 200/300. The Octel 200/300 automatically loads the default values corresponding to the PBX selected from the list in System Parameter 3.
Page 50: Octel 200/300 Configuration
SLOTS Table In the Octel 200/300, the DTMF In-band port should be configured as an AX mode port. COS Table Configure COS Attribute 68 — THIS PORT IS DTMF INTEGRATED, for all ports receiving DTMF In-band calls.
Page 51: Trace Capabilities
9 — Record Call in progress REC CALL FOR (Extension) 10 — Forced Forward FWDED FORCED (Extension) ==>(Extension) 11 — PBX Restart PBX RESTART 12 — Auto Log On AUTO LOG ON CALL (Extension) * Included in Traffic Peg 1. PB60019-01 Octel 200/300 S.4.1...
Page 52: List Trace Entries For Enhanced Dtmf In-Band Integration Errors
UNKNOWN CALL FORMAT No match to first element DIGITS DO NOT MATCH FORMAT Bad format after first element (number) ELEMENT (number) BAD FIRST DIGIT TABLE (number) DTMF digits do not match able ELEMENT (number) FIRSTDIGIT T Octel 200/300 S.4.1 PB60019-01...
Page 53 ........4-12 Message Waiting (Response to Command the Octel 200/300 Sent to SMDI) ....
Page 55: Chapter 4 Centrex Smdi/Smsi Adaptive Integration
Centrex systems. They provide a connection between Centrex and the Octel 200/300t message server on the customer’s premises. This connection is in the form of a 1200 baud serial data link. Calls to unanswered or busy Centrex lines are forwarded via Centrex call forwarding to the Octel 200/300 multiline hunt group.
Page 56: The Octel 200/300 Message Server, Smdi, And Centrex Connection
(CPI) operation. Message Waiting Indication. SMDI tells the Centrex to provide a message waiting indicator in the form of a stutter tone that can be activated by the Octel 200/300 (for mailboxes with a COS containing Attribute 9). When the first new message is received in a mailbox, the Octel 200/300 sends information to the PE to activate the MWI.
Page 57 When the mailbox is accessed, the Octel 200/300 sends information back to the PE to turn OFF the MWI, even if the messages are not listened to and erased.
Page 58: Centrex Smdi Limitations
CENTREX SMDI LIMITATIONS The Octel 200/300’s interface with Centrex is restricted. The following limitations should be considered when configuring the interface. All extensions should not be forwarded to the Octel 200/300, depending on who typically calls the extension. Sequential forwarding should be avoided!
Page 59 Centrex SMDI/SMSI Adaptive Integration that use of this feature stops the recording of reorder tone on abandoned calls to the Octel 200/300. If the NOH feature is not available, this problem can be avoided by utilizing ground start trunks. With ground start trunks, the system...
Page 60: Centrex Configuration
Centrex station lines for the Octel 200/300 ports must be provided and programmed as a multiline hunt group (MLHG) with SMDI. All stations to be call forwarded to the Octel 200/300 /SMDI ports require each of the following to be programmed at the PE. The Adaptive Integration option, which includes both Called Party Identification (CPI) and Message Waiting Indication (MWI) features, is required.
Page 61: Octel 200/300 Configuration For Centrex Smdi
System Parameter 117 — RINGBACKS BEFORE ANSWERING AX PORT In most cases, the Octel 200/300 receives the call record within the first ring of the forwarded call. The Octel 200/300 answers the call as soon as the call record is received. If after “n” rings (defined in System Parameters the call record has still not been received, the caller hears the company greeting instead of the called party’s station/name or...
Page 62 If this parameter is modified, the message server must be restarted before the baud rate is changed. Configure all ports that answer calls forwarded to the Octel 200/300 for AX mode. Configure the SLOTS Table as follows: In the extension number field for each port answering the Centrex lines, the extension number must be the exact Message Desk Number plus the Message Desk Terminal Number assigned by the PE.
Page 63 When the Octel 200/300 sends a MWI command over the SMDI link to turn ON or OFF the MWI for a mailbox, the Public Exchange (PE) expects a seven- or ten-digit Centric number corresponding to that extension.
Page 64 Greetings provide different company greetings, different intercept numbers, call blocking, etc., the Octel 200/300 can be configured by splitting incoming calls into different groups or by assigning unique Centrex station numbers for each type of incoming call that should receive different treatment.
Page 65: Octel 200/300/Centrex Installation
4-11 OCTEL 200/300/CENTREX INSTALLATION The Octel 200/300 is connected to the Centrex data link from the PE via a modem connected to Octel 200/300 RS-232C interface port, One data link must be configured for each cabinet. Every port/station associated with the data link must be in the same Octel 200/300 hunt group.
Page 66: Smdi Call Records
MD0010002D_ This is a direct call into the Octel 200/300 (the message desk) from outside of the Centrex. It came into the Octel 200/300 port having 0010002 defined as the station number in the SLOTS Table. In this type of call, the caller hears the company greeting.
Page 67: Message Waiting (Response To Command The Octel 200/300 Sent To Smdi)
The phone system has a hardware problem. The call is not programmed within SMDI to send call information to the Octel 200/300 multiline hunt group.
Page 69: Chapter 5 Neax-2400 Adaptive Integration
................Octel 200/300 Configuration for NEAX-2400 MCI .
Page 70: Neax-2400 Requirements
Figures The Octel 200/300, MCI, and NEAX-2400 Connection ..........
Page 71: Chapter 5 Neax-2400 Adaptive Integration
For full functionality of the integration, software release level 5200 is required. Message Waiting Indication. MCI tells the NEAX-2400 to provide message waiting indication (MWI) in the form of a lamp or MW display that can be activated by the Octel 200/300 (for mailboxes with a COS containing Attribute 9).
Page 72 Called Party Identification. When a call comes in to a NEAX-2400 line that is forwarded* to the Octel 200/300, the MCI sends the call record over the data link to the Octel 200/300. In most cases, the Octel 200/300 receives the call record within the first ring of the forwarded call. The Octel 200/300 answers the call as soon as it receives the call record.
Page 73: Neax-2400 Mci Limitations
The Octel 200/300 can wait up to the amount of rings defined in System Parameter 99, 100 or 117 for information sent from the PE. If it is not sent, the Octel 200/300 answers with the company greeting, not the called party’s mailbox information. Refer to the Octel 200/300 Configuration for NEAX-2400 MCI in this chapter.
Page 74: Neax-2400 Configuration
NEAX-2400 station lines for the ports must be provided and programmed as a UCD group with MCI. Extension Requirements All extensions to be call forwarded to the Octel 200/300 /MCI ports require each of the following to be programmed on the NEAX-2400. The Adaptive Integration option, which includes both called party identification (CPI) and message waiting indication (MWI) features, is required.
Page 75 NEC vendor may require an ODD parity if the MCI port is sharing a card with the NEAX-2400’s proprietary CDR (Call Detail Recording) package. If so, try to assign a port on a separate card for the MCI link. PB60019-01 Octel 200/300 S.4.1...
Page 76: Octel 200/300 Configuration For Neax-2400 Mci
For MWI, the Octel 200/300 activates and deactivates the MWI for the extension number associated with the mailbox. For CPI, the Octel 200/300 uses the extension number in the MCI call record to identify the calling and called mailbox numbers.
Page 77: Configuration Requirements For Cpi
System Parameter 117 — RINGBACKS BEFORE ANSWERING AX PORT In most cases the Octel 200/300 receives the call record within the first ring of the forwarded call. The Octel 200/300 answers the call as soon as the call record is received. If after “n” rings (defined in System Parameter 99, 100 and 117) the call record has not been received, the caller hears the company greeting instead of the called party’s...
Page 78: After All Changes Have Been Made For Mwi And Cpi
COS of the trunk group they came in on instead of the COS of the port the Octel 200/300 answered the call with. This means ports do not have to be split. For example, the company greeting may be customized depending upon the trunk group the call came in on;...
Page 79: Octel 200/300/Neax-2400 Installation
One data link must be configured for each Octel 200/300 cabinet. Every port/extension associated with the data link must be in the same Octel 200/300 hunt group. In a collocated Octel 200/300 installation, each cabinet must have a dedicated data link.
Page 80: Custom Cable Pin Pattern
Digital Ground 6−20* * Pin 6 and pin 20 (on the PBX side) should be tied together. Figure 5-4 Custom Cable Pin Pattern Octel 200/300 To PBX Figure 5-5 Octel 200/300 to PBX, RS-232C Male Connectors Octel 200/300 S.4.1 PB60019-01...
Page 81: Mci Call Records
If the extension is less than six digits long, the field is filled with trailing spaces. The Octel 200/300 supports the expanded MCI call records format. This format allows eight digits to identify the port extension and for calling and called party information. The expanded MCI format introduces a new field currently referred to as “spare.”...
Page 82: Mci Call Record Samples
<STX>0!J0012001 __430018395__001______<ETX> This is also a call direct to the Octel 200/300 but from a station on the NEAX-2400. The call originated from extension 8395. If the calling number does not have a mailbox, the caller hears the company greeting. If the calling number has a mailbox, the caller hears “To enter your mailbox, press pound...”...
Page 83: If A Call Record Is Not Received
The phone system has a hardware problem. The call is not programmed within MCI to send call information to the Octel 200/300 multi-line hunt group.
Page 84: Installation Checklist
Integration Volume INSTALLATION CHECKLIST This section offers a checklist of issues relating to the Octel 200/300 and NEAX-2400. The list is presented in the order that the installation process should be followed. For details regarding any topic, refer to the sections of this chapter pertaining to the issue.
Page 85 MCI link. The NEAX-2400 lines must also be programmed to forward to the Octel 200/300 UCD group on the desired conditions: RNA Forwarding to the MCI Group (CPI) FWD Busy Forwarding to the MCI Group (CPI) Set up message waiting lamp indication on mailboxes/extensions in the NEAX 2400 for MWI.
Page 86: Actual Installation
Item Description Complete Connect the NEAX-2400 data link via the special cables to the Octel 200/300 upper RS-232C port B. One data link must be configured for each Octel 200/300 cabinet. Refer to the Octel 200/300/NEAX-2400 Installation section in this chapter for cable specifications for the configuration for the Octel 200/300 NEC 2400 MCI.
Page 87 NEAX-2400 Adaptive Integration 5-17 Table 5-6 The Octel 200/300 Configuration Changes for CPI Item Description Command Complete Modify System Parameter 51 — .M SYS 51 RS-232 INTEGRATION WITH PBX, to YES. Modify System Parameter 99 — .M SYS 99 RINGBACKS BEFORE ANSWERING CX PORT, to 5.
Page 89 ..............Octel 200/300 Port Extensions .
Page 90: Digit Display Set Keyboard Layout - 16 To 32 Ports, Odd # Ports
6-36 Octel 200/300 Configuration Changes to MWI ..........
Page 91: Chapter 6 Northern Telecom Sl-1 Adaptive Integration
Message waiting indication (MWI) — control of message waiting lamps on PBX stations. Called party identification (CPI) — identification of the source and original destination of calls forwarded to the Octel 200/300. The Octel 200/300 can process the call and provide call coverage based on the type of call and desired coverage.
Page 92 Direct Calls from External Trunks If the call comes in on a trunk, the SL-1 provides the Octel 200/300 with the trunk access code as the source of the call. Trunks may be directed to Octel 200/300 ports for answering via the SL-1 auto-terminate feature determines how to process each call based on this trunk group number.
Page 93 Customizing Mailbox Features chapter, for more information. Direct Internal Call A person can call the Octel 200/300 directly to enter a mailbox, send a Quick Message, or make a network call. The Octel 200/300 recognizes these calls as internal and not forwarded since the display shows the calling extension.
Page 94: Sl-1 Pbx Requirements
SL-1 links (digit display extensions) connected to the Octel 200/300. Calls on incoming trunks to be handled by the Octel 200/300 are directed to this hunt group by using the SL-1 auto-terminate feature. The primary directory numbers (PDN) of the SL-1 links are configured as separate numbers, not as part of the Octel 200/300 hunt group.
Page 95: Software Requirements
19 — Digit Display (DDSP) This option allows call information to appear on the SL-1 digital display telephones. 46 — Message Center (MC) This option allows the SLIC to turn telephone message waiting indicators ON and OFF. PB60019-01 Octel 200/300 S.4.1...
Page 96: Sl-1 Configuration
This number is configured into the SL-1 and assigned to a group of incoming CO, WATS, DID, or TIE trunks. There is no need to split the Octel 200/300 ports to achieve different greetings as long as the trunks themselves belong to different trunk groups. Therefore, to configure Octel 200/300 to play different greetings to external callers, the specific trunk group numbers must be known.
Page 97 Occasionally, a third delay, FDDDE, can be helpful. The Octel 200/300 hunt group must be configured with a ring-no-answer fail-safe extension (FDN-FNA) for no-answer conditions. If the Octel 200/300 cannot answer a call due to a system failure, the call forwards to the fail-safe extension.
Page 98: Slic Link Digit Display Telephone Extensions
The SL-1 digit display set must be configured to have two extra rows of buttons (the 20 key add on module) for Octel 200/300 port appearances. Each SL-1 digit display set link into the Octel 200/300 SLIC must be specifically configured for its Octel 200/300 SLIC link extension and must have the following capabilities.
Page 99 Northern Telecom SL-1 Adaptive Integration For example, Integration Unit #1 Analog Port # Integration Unit #2 Analog Port # Line Appearance Line Appearance PB60019-01 Octel 200/300 S.4.1...
Page 100 Note: T he key numbers are in parenthesis. Only keys with key numbers are configurable. NC = Null Configuration. L/A = Line Appearance Figure 6-1 SL-1 Digit Display Set Keyboard Layout — 16 to 32 Ports, Odd# Ports PB60019-01 Octel 200/300 S.4.1...
Page 101: Customer Telephones
(05-08) Not configured. Release key. 10-17 scn XXXX Single call non-ring. This is the Octel 200/300 1-8 appearance. Line 1 must be configured at key 10 with successive ports configured on successive keys. XXXX = extension of port appearance. 18-19 Not configured.
Page 102 6-12 Integration Volume then use the camp-on feature, but will not have call coverage by the Octel 200/300 when busy. In addition, primary answer calls that reach a busy extension do not get call status (“is on the phone”). The prompt says “is unavailable.”...
Page 103: Octel 200/300 Configuration
Northern Telecom SL-1 Adaptive Integration 6-13 OCTEL 200/300 CONFIGURATION This section describes the changes that must be made to the Octel 200/300 configuration for message waiting indication and called party identification. Changes for Message Waiting Indication To configure the Octel 200/300 with message waiting indication on an SL-1, the following configuration changes must be made through the UPDATE program.
Page 104 Octel 200/300 ports. CONFIGURATION OF PORTS FOR OUTCALL — To maximize system performance and port usage, all Octel 200/300 ports should be configured for outcall. If this is not possible, the higher numbered ports should be configured for outcall. For example, in an eight-port system, ports 3−8 should be configured for outcall.
Page 105 Calls can be processed according to the COS of the trunk group they came in on instead of the COS of the port the Octel 200/300 answered the call with. This means ports do not have to be split. For example; the company greeting may be customized depending upon the trunk group the call came in on;...
Page 106: Test Equipment
If the CO is equipped with a DMS-100, ground start circuitry will need to be ordered. Refer to your PBX manual. In addition to the system test, there are some tests that should be made before the Octel 200/300 is connected. These tests are described in this section.
Page 107: Testing Procedures
Determine the cause and correct the problem before continuing. 2. EXTENSION NUMBER CHECK This test verifies that PBX extension numbers match the Octel 200/300 SLOT Table Before continuing with this test, obtain a hardcopy of the SLOTS Table for reference.
Page 108 Does the LED corresponding to port light steady? Hang up the phone. Does the LED turn OFF on both SL-1 sets that correspond to the Octel 200/300 port being called? Continue the procedure until all ports are tested. Determine the cause and correct the problem before continuing.
Page 109 Northern Telecom SL-1 Adaptive Integration 6-19 4. PBX BUSY FORWARD TEST This test verifies that a call to a busy extension forwards to the Octel 200/300 hunt group Connect telephone B to the modular adapter position associated with port 1 of the Octel 200/300.
Page 110 Unit 1, Link 1 on the SLIC board. b. Connect telephone B to the jack position of the modular adapter associated with Port 1 of the Octel 200/300 From telephone C, call the extension number associated with telephone B. d. Press the Display Number Key on the SL-1 digit display set. Does the corresponding LED turn ON? Determine the cause and correct the problem before continuing.
Page 111 - Before continuing with step 9 - When all Octel 200/300 port extensions pass steps 1−8, connect the 25-pair cables to the Octel 200/300 ports and integration cards and test the system for standard opera- tion. Verify that the yellow LEDs on the integration board are ON.
Page 112 On the terminal, at the @ prompt, enter the command PS. The port number in the IDL2 state is the port that the Octel 200/300 thinks was called. If that is not the port you intended to call, the lines should be changed so that the correct line is connected to the correct port.
Page 113 Determine the cause and correct the problem before continuing. d. While still connected to the Octel 200/300, enter mailbox number XXXX. Did the Octel 200/300 respond with the prompt, “Thank you. Just a moment” and did phone C start to ring again? Continue.
Page 114 6-24 Integration Volume h. Did the Octel 200/300 respond with the prompt, “Thank you. Just a moment,” and did phone C start to ring again? Continue. Determine the cause and correct the problem before continuing. After a predetermined interval (defined by the entry in the INFORMATION Table for Ringbacks Before No Answer) does respond with, “Extension YYY doesn’t answer.
Page 115 12. HUNT GROUP OPERATION TEST (For new install) Verifying the hunting sequence The terminal command PS displays the current status of each Octel 200/300 port. A three character abbreviation denotes the state of each port. Refer to the Installation and Maintenance volume, Maintenance Commands, for more information on using the PS command and the meaning of the states.
Page 116 Does the call overflow to the correct answering extension as determined for fail-safe operation? Determine the cause and correct the problem before continuing. Remove the busy condition from all the Octel 200/300 port PBX extensions by entering at the @ prompt TE C 2 x Enter where x is the port number.
Page 117 From telephone A, call out and back in on a trunk dedicated to the hunt group. o. Does the call overflow to the correct destination? Determine the cause and correct the problem before continuing. p. Remove the busy condition from all the Octel 200/300 port extensions by entering at the @ prompt TE C 2 Enter q.
Page 118 Determine the cause and correct the problem before continuing. 17. MESSAGE WAITING From telephone A, call out and back in on a trunk dedicated to the Octel 200/300. b. Does the Octel 200/300 answer properly? Determine the cause and correct the problem before continuing.
Page 119 Answer telephone C (or call the Octel 200/300 and enter the mailbox if the indicator is lit.) The Octel 200/300 should respond with “... has X messages. Ready,” or might also ask for a security code.
Page 120: Installation Of The Slic Board
All cross-connections to the PBX must be completed before proceeding. Changes to connections should only be made while the integration card is not installed in the Octel 200/300. Cross connecting Caution! integration links when the integration card is installed may result in damage to the integration card.
Page 121 YELLOW Unit 2, Link 1 YELLOW Unit 1, Link 1 YELLOW Unit 2, Link 1 Code Download Complete GREEN YELLOW Unit 1, Link 1 YELLOW Unit 2, Link 1 YELLOW Unit 1, Link 1 YELLOW Unit 2, Link 1 PB60019-01 Octel 200/300 S.4.1...
Page 122: Sl-1 Adaptive Integration Maintenance
L INT where x is the slot number CLEAR INTEGRATION This command clears the SLIC board pegs. The form of the command is (C INT x y) C INT x y where x is the slot number PB60019-01 Octel 200/300 S.4.1...
Page 123 There are two types of pegs for integrated systems. These pegs are independent of traffic pegs and can only be listed by using the L INT command. LINK-INDEPENDENT PEGS. Independent pegs refer to overall card operation. They do not indicate an error condition. PEGS 1−5 Not used. PB60019-01 Octel 200/300 S.4.1...
Page 124 LED did not come ON. PEGS 8−10 Not used. For information on hardware errors regarding integrated systems, refer to the Installation and Maintenance volume, System Errors and Traffic Pegs chapter, for more information. PB60019-01 Octel 200/300 S.4.1...
Page 125: Installation Checklist
6-35 INSTALLATION CHECKLIST This section contains checklists of issues relating to the Octel 200/300 and to the SL-1. The list is presented in the order in which the installation process should be followed. For details regarding any topic, refer to the sections of this chapter pertaining to the issue.
Page 126 Provide 2 SL-1 digit display phones with 20 button add-on modules that will include two terminal numbers and two unique primary directory numbers. (Used for testing only.) A complete hardcopy of Directory Number Block (DNB) and Terminal Num- ber Block (TNB) of all stations requiring a change. PB60019-01 Octel 200/300 S.4.1...
Page 127: Octel 200/300 Configuration Changes To Cpi
Northern Telecom SL-1 Adaptive Integration 6-37 Actual Installation Table 6-6 Octel 200/300 Configuration Changes to MWI Item Description Command Complete Modify System Parameter 9 to be 700 (increase flash .M SYS 9 time). Modify System Parameter 85 to be NONE (reconnect .M SYS 85...
Page 128 Forward RNA non-DID calls (FNAD command) Optional by Customer Forward DID calls (FNAD command) Optional by Customer System Ring Cycle — Regular (CFNA command) Optional by Customer System Ring Cycle — Distinctive (DFNA command) Optional by Customer PB60019-01 Octel 200/300 S.4.1...
Page 129 Table 6-9 SL-1 Configuration (continued) Item Description Complete Octel 200/300 port extensions: Configure the ports in a terminal hunt group with the last extension in the hunt group specified as the overflow extension Program the COS (Class of Service) with the following...
Page 130 MWA (message waiting allowed) Key XX = MWK XXXX (Assign a key that will go to the pilot number of the Octel 200/300 when the key is pressed.) SL-1 sets without a message waiting key will still get stutter dial tone:...
Page 131: Test Equipment
Extensions for testing, in addition to the port extension. One extension must have message waiting allowed and be busy and RNA forwarded into the Octel 200/300 hunt group. SL-1 digit display phones with 20-button add-on module. Hardcopy of Testing Operation procedures.
Page 133: Chapter 7.1 Definity G3 Adaptive Integration
..........7.3-1 PB60019-01 Octel 200/300 S.4.1...
Page 135 These chapters explain the PBX and Octelt 200/300 configuration requirements for correct operation of Adaptive Integration, including Message Waiting Indication and Called Party Identification. When planning, configuring, installing and testing DEFINITY, AT&T System 75 or System 85 Adaptive Integration, be sure to use the correct chapter in this manual. PB60019-01 Octel 200/300 S.4.1...
Page 137 7.1-14 Octel 200/300 Port Extensions ..........
Page 138: Station Data Entry Screen For Link
7.1-2 COR Data for the Octel 200/300 Ports ..........
Page 139: 7.1.1 Operation Of Definity G3 Adaptive Integration
Any information that the DEFINITY G3i provides to an AT&T display phone station (either on the display itself or by the display set LEDs) is available to the Octel 200/300. This information includes the following: The trunk group number of external calls that have been directed to for primary answering.
Page 140: Definity G3 Call Coverage
The source extension or trunk group, the called extension, and the status of forwarded calls. With this information, the Octel 200/300 can process the various types of calls appropriately. The Octel 200/300 receives the necessary call information from the DEFINITY G3i through the digital links of the ATTIC.
Page 141: Called Party Identification Call Processing
Instead, it forwards to the next coverage point in the original called extension’s coverage path. The Octel 200/300 uses the following prompts to describe the reason a call has been sent to coverage: Reason for Coverage Octel 200/300 Prompt “(name) doesn’t answer”...
Page 142 R is a code indicating the reason the call was forwarded. Upon receiving the forwarded call, the Octel 200/300 plays the extension’s greeting if it is ON, or if the greeting is OFF, the Octel 200/300 prompts the caller with the status of the extension, followed by the prompt “Please leave a message at the tone, enter another extension number, or press zero for personal...
Page 143 DEFINITY G3i sends this type of call record: a = XXX Name to YYY XXX is the number of the calling extension and YYY is the access extension number. The Octel 200/300 uses the call record information to identify the calling extension.
Page 144: How Incoming Call Ports Are Selected With The Definity G3
Trunk Group 0. If Trunk Group 0 is set up in the TRUNK GROUP Table, the Octel 200/300 will answer with the greeting for Trunk Group 0. If Trunk Group 0 is not configured, Octel 200/300 will answer with the main company greeting.
Page 145: 7.1.2 Definity G3 Requirements
Digital Voice Terminal Extensions. The DEFINITY G3i must provide a digital voice terminal port for each ATTIC link in the Octel 200/300. If two or more AT&T digital line cards (part number TN754B) are available, having each digital link on a different digital line card in the DEFINITY G3i provides greater reliability.
Page 146: 7.1.3 Definity G3 Configuration
7.1.3 DEFINITY G3 CONFIGURATION Several changes must be made to the DEFINITY G3i configuration to use Adaptive Integration features. The DEFINITY G3i configuration used for the Octel 200/300 with Adaptive Integration is substantially different from the configuration used for a non-integrated Octel 200/300.
Page 147: Cor
All CORs should have access to the digital link’s COR. This is because all calls handled by the Octel 200/300 are received by the Octel 200/300 and then transferred to an available Octel 200/300 port for call processing. COR must be the only COR that has access to the COR of the 200/300 ports (except for the operator and trunks, see below).
Page 148 7.1-10 Integration Volume The COR for the operator and the trunks must allow access to the Octel 200/300 ports. All other CORs should be denied access to the Octel 200/300 ports. If other extensions have the same COR as the operator or the trunks, they must be issued a new COR.
Page 149: Cor Data For Links. "Lk" Should Be The Number Of An Available Cor
Figure 7.1-1 COR data for LINKS. “LK” should be the number of an available COR LEGEND for Figure 7.1-1 bold Entry which must be made exactly as shown Entry which must be made but which is specific to the particular DEFINITY G3i installation PB60019-01 Octel 200/300 S.4.1...
Page 150: Cor Data For The Octel 200/300 Ports
31? y 39? y 47? y 55? y 63? y Figure 7.1-2 COR Data for the Octel 200/300 Ports “DP” should be the number of an available COR. LEGEND for Figure 7.1-2 bold Entry which must be made exactly as shown...
Page 151: Cor Data For Another System Cor
55? _ Figure 7.1-3 COR Data for Another System COR In this example, COR 62 is used for the links and COR 63 is used for Octel 200/300 ports. No CALLING PERMISSION entries should be changed except for 62 and 63.
Page 152: Attic Link Digital Phone Extensions
A digital telephone station must be allocated for each ATTIC link. These stations must be properly configured as 7405D sets in the DEFINITY G3i to interface with the Octel 200/300. Each system port may be assigned to more than one integration unit to the maximum for the Octel 200/300.
Page 153 LEGEND for Figure 7.1-4 italics Entry described in the instructions bold Entry which must be made exactly as shown ____(blank) Must be left blank Entry which must be made but which is specific to the particular DEFINITY G3i installation. PB60019-01 Octel 200/300 S.4.1...
Page 154: Station Data Entry Screen For The Links
23: __________ 12: __________ 24: __________ Figure 7.1-6 STATION Data Entry Screen for the Links LEGEND for Figure 7.1-5 and Figure 7.1-6 bold Entry which must be made exactly as shown ____(blank) Must be left blank Octel 200/300 S.4.1 PB60019-01...
Page 155: Octel 200/300 Port Extensions
2. Use the CHANGE command to modify one of the Octel 200/300 port extensions to be integrated. Figure 7.1-8 shows an example of the Station data entry screen for an Octel 200/300 port (2500 type single-line analog extension).
Page 156 5. Repeat steps 2 through 4 above for each integrated Octel 200/300 port. 6. The integrated Octel 200/300 ports are not placed in a hunt group. To determine if any port extensions appear as part of a hunt group, enter LI GR STATION XXX where XXX is the port extension number.
Page 157: Hunt Group Data Entry Screen
3. Assign the hunt group a coverage path (CPX) which has the attendant as its first coverage point. This coverage path ensures that if it isn’t working, calls to the Octel 200/300 will default to the attendant. Refer to the Coverage Path Configuration section, step 6.
Page 158: Hunt Group Data Entry Screen
Figure 7.1-10 Hunt Group Data Entry Screen, Page 2 Coverage Paths All extensions that are to use the Octel 200/300 for call coverage must be assigned a coverage path that includes as a coverage point. This may require addition of new coverage paths as well as modification of existing coverage paths.
Page 159: Coverage Path Example Data Screen
The coverage path is set up as follows: The first coverage point is the Octel 200/300 hunt group. The second coverage point (in the event the Octel 200/300 fails to answer the call) is the attendant (extension 0). No third point is specified.
Page 160: Trunk Groups
XXX is the trunk group’s TAC (trunk access number). 4. If the trunk group is to be answered directly by the Octel 200/300 enter EXTNH for the Incoming Destination. Also write down the Group Number and the TAC. These numbers are needed for the Octel 200/300 configuration.
Page 161: Trunk Group Data Entry Screen
3. Change the station’s Name entry to fit this format as described in the Naming Conventions section in this chapter. Example, First XXX Last First is the station owner’s first name, XXX is the 3- to 8-digit station extension, and Last is the station owner’s last name. PB60019-01 Octel 200/300 S.4.1...
Page 162: Example Station Data Entry Screen For A Station Extension
Enclosing the station extension within the station owner’s name in the Name entry preserves the functionality of the DEFINITY G3i’s directory feature. Extension numbers are typically the same as the Octel 200/300 mailbox numbers associated with them. 4. (Message waiting indication only) If the station has a message waiting indicator, enable “Leave Word Calling Reception”...
Page 163: 7.1.4 Octel 200/300 Configuration
External Call Configuration. The DEFINITY G3i provides the Octel 200/300 with the Trunk Group number of an external call. The TRUNK GROUP Table enables the Octel 200/300 to process the call according to the trunk group on which the call was received instead of which port answered the call on.
Page 164: Changes For Called Party Identification
SLOTS Table. Changes for Called Party Identification To configure the Octel 200/300 with called party identification on a System 75, the following configuration changes must be made through the UPDATE program. Mailbox and extension numbers must match for message waiting indication to operate correctly.
Page 165 Port COS COS Attribute 58 — DO NOT USE THIS PORT FOR INTEGRATION Assign this COS attribute to those Octel 200/300 ports used in special applications that do not require integration. SLOTS Table The SLOTS Table is used to configure both Line Interface Cards (LICs) and Integration Cards.
Page 166 System Parameter 133 — INTEGRATION CARD EXTENSION Modify this system parameter to be the Octel 200/300 hunt group access number. This parameter is required only for the system ring-through test TE L 2. Refer to the Installation and Maintenance volume, Maintenance Commands chapter, Line Interface Card Diagnostics section, for more information.
Page 167: Test Equipment
Modular adapter for digital sets. Recommend AT&T 356A adapter. Modular adapter for the 2500. Recommended Armiger AA2560A or equivalent. These tests assume no other calls are being made into the Octel 200/300. If the Octel 200/300 receives other calls, the test results may be invalid.
Page 168: Configuration Of Test Extensions
EXT-B is replaced with the extension number. In the tests that follow, the number of this extension is referred to as EXT-B. Assign this station the same COR assigned to the Octel 200/300 ports and a coverage path in which the Octel 200/300 hunt group is the first coverage point. The coverage path must specify forwarding on RNA and busy.
Page 169: Function Key Layout For 7407D Display Telephone
Line 2 Line 7 Line 3 Line 8 Line 4 Line 9 Line 5 Line 10 lwc-cancel lwc-store Oper inspect normal Display Select Ring Speaker Microphone Message Figure 7.1-14 Function Key Layout for 7407D Display Telephone PB60019-01 Octel 200/300 S.4.1...
Page 170: Testing Procedure
This test verifies that dial tone is present on each of the single line analog extensions used for the Octel 200/300 ports. Disconnect the 25-pair cables from the back of the Octel 200/300 b. Connect the modular adapter to the 25-pair cable associated with slot 1.
Page 171 4. DIGITAL LINE EXTENSION NUMBER VERIFICATION This test verifies that the PBX extension numbers assigned to the Octel 200/300 match the corresponding extensions. Obtain a hard copy of the SLOTS Table information pertaining to those slots configured for ATTIC integration.
Page 172 Repeat steps c. through g. to test the other integration units. 6. PBX BUSY FORWARD TEST This test verifies that a call to a busy extension forwards to the Octel 200/300 access number. Connect the 356A adapter to the 25-pair cable associated with the configured slot.
Page 173 DEFINITY G3 Adaptive Integration 7.1-35 7. PBX RING-NO-ANSWER FORWARD TEST This test verifies that a call to a ring-no-answer extension forwards to the Octel 200/300 access number. Re-enable Ring-no-answer coverage for this test. Connect the 356A adapter to the 25-pair cable associated with the configured slot.
Page 174 Hang up phone A. Using phone A, call into the ATTIC hunt group directly. g. Look at the display of the digital phone. The second line of the display should contain this information: Test AXXX Octel 200/300 S.4.1 PB60019-01...
Page 175 Hang up phone A and phone B. Call forwarded on RNA g. Using phone A, call phone B. Let phone B ring until the call forwards to the Octel 200/300 hunt group. h. Press the Inspect Mode key to look at the displays of the ringing line on the digital phone. The second line of the display should contain this information: a = Test A EXT−A to Test B EXT−B...
Page 176: Installation Of The Attic Board
Determine the cause and correct the problem before continuing. Connect phone B to the jack position of the modular adapter of the next Octel 200/300 port extension. Repeat steps b. through d. until every Octel 200/300 port has successfully transferred a call to the attendant.
Page 177: Testing Of Adaptive Integration Features
Testing of Adaptive Integration Features This section describes the procedures for testing Adaptive Integration features, once the ATTIC board is installed and operational and the PBX 25-pair cable is re-connected to the correct Octel 200/300 ports, proceed as follows: PB60019-01 Octel 200/300 S.4.1...
Page 178 This shows the port the call came in on. b. From phone A, call the extension of Octel 200/300 port 1. Phone A must have the same COR as the digital links to call the Octel 200/300 ports directly. Does Octel 200/300 answer with the company greeting? Go to step d.
Page 179 3. DIRECT INTERNAL CALL TO THE OCTEL 200/300 This test verifies that the Octel 200/300 processes a direct internal call correctly. From phone B, call the extension number for Octel 200/300 access (). Does the Octel 200/300 answer with “To enter your mailbox press pound...” ? Determine the cause and correct the problem before continuing.
Page 180 200/300 port that answered the call. Use the command TE C 1 x, in which x is the port number. d. Repeat steps a. through c. for each Octel 200/300 port until all of the ports are busied out. This is to confirm that calls can be placed to the Octel 200/300 on each port.
Page 181 Does the call overflow to the correct destination? Determine the cause and correct the problem before continuing. From the Octel 200/300 terminal, use the command TE C 2 to release all Octel 200/300 ports from the FWD condition. 9. EXTERNAL CALL TO A RING-NO-ANSWER EXTENSION This test verifies that the Octel 200/300 correctly processes an external call that reaches a ring-no-answer (RNA) extension.
Page 182 Determine the cause and correct the problem before continuing. From phone A, call out and back in on a trunk auto-terminated to the Octel 200/300. When the Octel 200/300 answers, let the system time out (do not enter any digits).
Page 183 ON.) Determine the cause and correct the problem before continuing. g. From phone B, call the Octel 200/300 and on to mailbox B. The Octel 200/300 should respond with “you have one message. Ready.”...
Page 184 In the PBX, configure the name for phone B to be TEST B. Do not include the extension number in the name field. Take phone B off-hook to make it appear busy. b. From phone A, call phone B. Does the Octel 200/300 answer with the greeting for Trunk Group 0 (zero)? Press to exit from the Octel 200/300.
Page 185: 7.1.6 Definity G3 Maintenance
The following are definitions of the fields displayed when listing the state of the ATTIC board. Card ID The CARD ID states the type of equipped integration card. The Octel 200/300 reads this register and reports that this is an ATTIC integration card. PB60019-01 Octel 200/300 S.4.1...
Page 186 The ATTIC is down and not responding to the CARD DOWN software. Code is downloading to the ATTIC. DOWN LOAD INITIALIZATION The Octel 200/300 software is downloading code to the card and setting up operation parameters. The ATTIC is operational. CARD UP Diagnostic The diagnostic code is read from the ATTIC card.
Page 187 PBX that did not have a valid CRC. The packet was ignored and not acknowledged. NO DISPLAY Number of times that the ATTIC called the Octel 200/300 and the display was blank. INTERNAL ERROR The ATTIC incremented one of its internal error pegs.
Page 188 HOLD ERROR Number of times the ATTIC pressed the CONFERENCE button and it did not put the call to the Octel 200/300 on hold. DIAL ERROR Number of times the ATTIC did not get a port from the message server.
Page 189: Octel 200/300 Requirements
7.1-51 7.1.7 INSTALLATION CHECKLIST This section offers a checklist of issues relating to the Octel 200/300 and to the DEFINITY G3i. The list is presented in the order in which the installation process should be followed. For details regarding any topic, refer to the sections of this chapter pertaining to the issue.
Page 190: Class Of Restriction Checklist
Description Complete Allocate a Hunt Group pilot number to be used for access to the Octel 200/300. Add the digital stations configured for the ATTIC Set up page 1 of the Link 1 Station Data. Type should be 7405D. See Figure 7.1-4 and Figure 7.1-5.
Page 191: Coverage Path Configuration Checklist
Change the Group Name to fit this format: T-XXX. XXX is the trunk group TAC. If the trunk group is to be answered by the Octel 200/300 enter the number for the Incoming Destination. Repeat steps 2 through 4 for each trunk group listed in step 1.
Page 192: Installing The Attic Board
Table 7.1-10 Installing the ATTIC Board Item Description Command Complete Forward the Octel 200/300 ports. CD x y z Plug the ATTIC board(s) into the configured slot(s). Refer to the power-on routine and monitor the LEDs. Plug the 25-pair cable into the ATTIC slot.
Page 193: Configuration Changes To Cpi
Add Attribute 15 to the COS of all mailboxes associated .A COS with extensions that forward to the Octel 200/300 All ports should be configured in AX mode. .M SLOT Add a COS with Attribute 58 to those ports that do not .A COS...
Page 194: Test Equipment
Quantity Description 2500-type (single-line touchtone) phones, one with a message waiting indicator. Terminal/teleprinter directly connected to the Octel 200/300 via RS-232C cable. Hard copy of the Octel 200/300 configuration database. Hard copy of the DEFINITY G3i configuration Single-line analog extensions (connected to RJ11 jacks) for testing. These extensions are in addition to the ATTIC link extensions.
Page 195 7.2-14 Octel 200/300 Port Extensions ..........
Page 196: Station Data Entry Screen For The Links, Page 1
........7.2-16 7.2-7 STATION Data Entry Screen for an Octel 200/300 Port Extension ......7.2-18 7.2-8...
Page 197: 7.2.1 Operation Of At&T System 75 Adaptive Integration
LEDs) is available to the Octel 200/300.This information includes the following: The trunk group number of external calls that have been directed to the Octel 200/300 for primary answering. The trunk group number and the original called extension of external calls that have been forwarded to the Octel 200/300.
Page 198: System 75 Call Coverage
The source extension or trunk group, the called extension, and the status of forwarded calls. With this information, the Octel 200/300 can process the various types of calls appropriately. the Octel 200/300 receives the necessary call information from the System 75 through the digital links of the ATTIC.
Page 199: Called Party Identification Call Processing
Send All Calls “(name) is unavailable” * If System Parameter 115 is set to Y, the Octel 200/300 uses “(name) is on the phone” instead of “(name) is busy.” Refer to the Feature Description volume, Customizing Mailbox Features. Called Party Identification Call Processing...
Page 200 R is a code indicating the reason the call was forwarded. Upon receiving the forwarded call, the Octel 200/300 plays the extension’s greeting if it is ON, or if the greeting is OFF, the Octel 200/300 prompts the caller with the status of the extension, followed by the prompt “Please leave a message at the tone, enter another extension number, or press zero for personal...
Page 201 = T−XXX to OPERATOR Direct Internal Calls A caller can access the Octel 200/300 directly to enter a mailbox, send a Quick Message, or make a network call. For these direct internal calls, the System 75 sends this type of call record: a = XXX Name to YYY XXX is the number of the calling extension and YYY is the Octel 200/300 access extension number.
Page 202: How Incoming Call Ports Are Selected With The At&T System 75
Trunk Group 0. If Trunk Group 0 is set up in the TRUNK GROUP Table, the Octel 200/300 will answer with the greeting for Trunk Group 0. If Trunk Group 0 is not configured, the Octel 200/300 will answer with the main company greeting.
Page 203: 7.2.2 At&T System 75 Requirements
Digital Voice Terminal Extensions. The System 75 must provide a digital voice terminal port for each ATTIC link in the Octel 200/300 If two or more AT&T digital line cards (part no. TN754B) are available, having each digital link on a different digital line card in the DEFINITY G3i provides greater reliability.
Page 204: 7.2.3 At&T System 75 Configuration
Integration Volume 7.2.3 AT&T SYSTEM 75 CONFIGURATION Several changes must be made to the System 75 configuration to use the Octel 200/300’s Adaptive Integration features. The System 75 configuration used for the Octel 200/300 with Adaptive Integration is substantially different from the configuration used for a non-integrated the Octel 200/300 The changes to the configuration of the System 75 are divided into seven sections.
Page 205: Cor
200/300 are received by the Octel 200/300 and then transferred to an available Octel 200/300 port for call processing. The link’s COR must be the only COR that has access to the COR of the Octel 200/300 ports (except for the operator and trunks, see below). This is to prevent other extensions from directly accessing the Octel 200/300 ports.
Page 206 4. Set up COR LK according to Figure 7.2-1. Under CALLING PERMISSION, enter a Y for all other CORs on the system. 5. Add the COR for the Octel 200/300 ports. This COR is referred to as COR DP. 6. Set up COR DP according to Figure 7.2-2. Under CALLING PERMISSION, enter a Y for all other CORs on the system.
Page 207 AT&T System 75/Definity G1 Adaptive Integration 7.2-11 Page 1 of 1 CLASS OF RESTRICTION COR Number: Octel 200/300 FRL: * APLT? n Calling Party Restriction: none Called Party Restriction: none Forced Entry of Account Codes? n CALLING PERMISSION (Enter “y” to grant permission to call specified COR)
Page 208 31? y 39? y 47? y 55? y 63? y Figure 7.2-2 COR Data for the Octel 200/300 Ports “DP” should be the number of an available COR. LEGEND for Figure 7.2-2 bold Entry which must be made exactly as shown...
Page 209 55? _ Figure 7.2-3 COR Data for Another System COR In this example, COR 62 is used for the links and COR 63 is used for Octel 200/300 ports. No CALLING PERMISSION entries should be changed except for 62 and 63.
Page 210: Attic Link Digital Phone Extensions
Include an A- before the extension number. For example, A-382. Assign Link 1 a coverage path (CPX) which has the attendant as its first coverage point. This coverage path ensures that if Octel 200/300 isn’t working, calls to Octel 200/300 default to the attendant.
Page 211 AT&T System 75/Definity G1 Adaptive Integration 7.2-15 Page 1 of 3 STATION Octel 200/300 Extension: EXTL Type: 7405D Lock Messages: n COR: Octel 200/300 ROOM: Port: **** Security Code: ____ COS: Jack: Coverage Path: CPX Octel 200/300 Name: A-EXTL Cable:...
Page 212 6: __________ 7: __________ Figure 7.2-6 STATION Data Entry Screen for the Links, Page 3 LEGEND for Figure 7.2-5 and Figure 7.2-6 bold Entry which must be made exactly as shown blank Must be left blank PB60019-01 Octel 200/300 S.4.1...
Page 213: Octel 200/300 Port Extensions
5. Repeat steps 2 through 4 above for each integrated the Octel 200/300 port. 6. The integrated the Octel 200/300 ports are not placed in a hunt group. To determine if any the Octel 200/300 port extensions appear as part of a hunt group, enter LI GR STATION XXX where XXX is the port extension number.
Page 214: Hunt Group
3. Assign the hunt group a coverage path (CPX) which has the attendant as its first coverage point. This coverage path ensures that if the Octel 200/300 isn’t working, calls to the Octel 200/300 will default to the attendant. Refer to Coverage Path, Configuration, number 6.
Page 215 Page 2 of 6 Hunt Group Group Number: HX Group Extension: EXTNH Group Type: UCD Group Member Assignments Name Name Name EXS5U1L1 EXS5U1L2 EXS5U2L1 EXS5U2L2 EXS6U1L1 EXS6U1L2 EXS6U2L1 Figure 7.2-9 Hunt Group Data Entry Screen, Page 2 PB60019-01 Octel 200/300 S.4.1...
Page 216: Coverage Paths
Integration Volume Coverage Paths All extensions that are to use the Octel 200/300 for call coverage must be assigned a coverage path that includes the Octel 200/300 as a coverage point. This may require addition of new coverage paths as well as modification of existing coverage paths.
Page 217: Trunk Groups
200/300. Create a coverage path that has the attendant as its first coverage point and the extension of the last the Octel 200/300 port as the second coverage point. This is the coverage path (referred to as CPX) that should be specified for the Octel 200/300 access extension (EXTL1) Octel 200/300.
Page 218: Trunk Group Data Entry Screen
XXX is the trunk group’s TAC (trunk access number). 4. If the trunk group is to be answered directly by the Octel 200/300 enter Octel 200/300 for the Incoming Destination. Also write down the Group Number and the TAC. These numbers are needed for the Octel 200/300 configuration.
Page 219: Station Extensions
Enclosing the station extension within the station owner’s name in the Name entry preserves the functionality of the System 75’s directory feature. Extension numbers are typically the same as the Octel 200/300 mailbox numbers associated with them. 4. (Message waiting indication only) If the station has a message waiting indicator, enable “Leave Word Calling Reception”...
Page 220 Abbreviated Dialing List Number (From above 1, 2 or 3): Dial Code: Figure 7.2-12 Example STATION Data Entry Screen for a Station Extension LEGEND for Figure 7.2-12 italics Entry described in the instructions blank Leave unchanged PB60019-01 Octel 200/300 S.4.1...
Page 221: 7.2.4 Octel 200/300 System Configuration
The TRUNK GROUP Table enables the Octel 200/300 to process the call according to the trunk group on which the call was received instead of which port the Octel 200/300 answered the call on. This means integrated ports do not need to be split. Examples of how this can be applied include A different company greeting may be used for each trunk group.
Page 222: Changes For Called Party Identification
Refer to the Configuration volume, Slots Table chapter, for more information on configuring the SLOTS Table. Changes for Called Party Identification To configure the Octel 200/300 with called party identification on a System 75, the following configuration changes must be made through the UPDATE program. Mailbox COS COS Attribute 15 —...
Page 223 Port COS COS Attribute 58 — DO NOT USE THIS PORT FOR INTEGRATION Assign this COS attribute to those the Octel 200/300 ports used in special applications that do not require integration. SLOTS Table The SLOTS Table is used to configure both Line Interface Cards (LICs) and Integration Cards.
Page 224 System Parameter 117 — RINGBACKS BEFORE ANSWERING AX PORT Modify System Parameter 117 to be 5. This gives the Octel 200/300 extra time to receive the call records from the PBX. The Octel 200/300 normally answers the call immediately within one ring upon receiving a call record from the ATTIC.
Page 225: 7.2.5 At&T System 75 Testing And Installation
Modular adapter for digital sets. Recommend AT&T 356A adapter. Modular adapter for the 2500. Recommended Armiger AA2560A or equivalent. These tests assume no other calls are being made into the Octel 200/300. If the Octel 200/300 receives other calls, the test results may be invalid.
Page 226: Configuration Of Test Extensions
EXT-B is replaced with the extension number. In the tests that follow, the number of this extension is referred to as EXT-B. Assign this station the same COR assigned to the Octel 200/300 ports and a coverage path in which the Octel 200/300 hunt group is the first coverage point. The coverage path must specify forwarding on RNA and busy.
Page 227: 13 Function Key Layout For 7407D Display Telephone
Line 2 Line 7 Line 3 Line 8 Line 4 Line 9 Line 5 Line 10 lwc-cancel lwc-store Oper inspect normal Display Select Ring Speaker Microphone Message Figure 7.2-13 Function Key Layout for 7407D Display Telephone PB60019-01 Octel 200/300 S.4.1...
Page 228: Testing Procedure
This test verifies that dial tone is present on each of the single line analog extensions used for the Octel 200/300 ports. Disconnect the 25-pair cables from the back of Octel 200/300. b. Connect the modular adapter to the 25-pair cable associated with slot 1.
Page 229 Check that the name on the digital display is the name programmed for phone A. h. Hang up phone A. Connect phone A to the RJ11 jack position of the modular adapter of the next Octel 200/300 port extension and repeat steps f. through i. until every Octel 200/300 port extension has been tested.
Page 230 Repeat steps c. through g. to test the other integration units. 6. PBX BUSY FORWARD TEST This test verifies that a call to a busy extension forwards to the Octel 200/300 access number. Connect the 356A adapter to the 25-pair cable associated with the configured slot.
Page 231 Integration Unit 1, Link 2. Set phone C to send all calls to coverage. d. Using phone A, call the extension of phone B. Does the Octel 200/300 start to ring? Determine the cause and correct the problem before continuing.
Page 232 T-XXX is the group name of the trunk group the call came in on. A-YYY is the extension of the ATTIC hunt group. If the display does not contain this information, determine the cause and correct the problem before continuing. PB60019-01 Octel 200/300 S.4.1...
Page 233 Hang up phone A and phone B. Call forwarded on RNA g. Using phone A, call phone B. Let phone B ring until the call forwards to the Octel 200/300 hunt group. h. Press the Inspect Mode key to look at the displays of the ringing line on the digital phone. The second line of the display should contain this information: a = Test A EXT−A to Test B EXT−B...
Page 234 NO ' Determine the cause and correct the problem before continuing. Connect phone B to the jack position of the modular adapter of the next Octel 200/300 port extension. Repeat steps b. through d. until every Octel 200/300 port has successfully transferred a call to the attendant.
Page 235: Installation Of The Attic Board
Installation of the ATTIC Board This section describes the procedure for installing the ATTIC board. Before proceeding with installation, note that there are Octel 200/300 These are used to indicate card status and are, from top to bottom, LED Name...
Page 236: Testing Of Adaptive Integration Features
Testing of Adaptive Integration Features This section describes the procedures for testing Adaptive Integration features, once the ATTIC board is installed and operational and the PBX 25-pair cable for the Octel 200/300 is re-connected to the correct the Octel 200/300 ports, proceed as follows: 1.
Page 237 This shows the port the call came in on. b. From phone A, call the extension of the Octel 200/300 port 1. Phone A must have the same COR as the digital links to call the Octel 200/300 ports directly.
Page 238 Take phone B off-hook to make it appear busy. b. From phone A, call phone B. Does the Octel 200/300 answer with the prompt, “Extension EXT-B is in use. Please leave a message at the tone”? Determine the cause and correct the problem before continuing.
Page 239 200/300 port that answered the call. Use the command TE C 1 x, in which x is the port number. d. Repeat steps a. through c. for each Octel 200/300 port until all of the ports are busied out. This is to confirm that calls can be placed to the Octel 200/300 on each port.
Page 240 Take phone B off-hook to make it appear busy. b. From phone A, call outside of the PBX and back in on a trunk that terminates Octel 200/300. Does the Octel 200/300 answer properly? Determine the cause and correct the problem before continuing.
Page 241 Message feature to leave a message for phone B instead of following the instructions of step d. d. Enter the extension number of phone B. Does Octel 200/300 respond with “Thank you, just a moment...”? the Octel 200/300 should respond with “Extension EXT-B is busy/unavailable.
Page 242 13. FORWARDED INTERNAL CALL TO AN EXTENSION THAT DOES NOT HAVE THE EXTENSION NUMBER IN THE NAME FIELD This test verifies that the Octel 200/300 correctly processes a call to an extension that does not have the extension number in the name field.
Page 243: 7.2.6 At&T System 75 Maintenance
The following are definitions of the fields displayed when listing the state of the ATTIC board. Card ID The CARD ID states the type of equipped integration card. The Octel 200/300 reads this register and reports that this is an ATTIC integration card. PB60019-01 Octel 200/300 S.4.1...
Page 244 The ATTIC is down and not responding to the CARD DOWN software. Code is downloading to the ATTIC. DOWN LOAD INITIALIZATION The Octel 200/300 software is downloading code to the card and setting up operation parameters. The ATTIC is operational. CARD UP Diagnostic The diagnostic code is read from the ATTIC card.
Page 245 PBX that did not have a valid CRC. The packet was ignored and not acknowledged. NO DISPLAY Number of times that the ATTIC called Octel 200/300 and the display was blank. INTERNAL ERROR The ATTIC incremented one of its internal error pegs.
Page 246 HOLD ERROR Number of times the ATTIC pressed the CONFERENCE button and it did not put the call to the Octel 200/300 on hold. DIAL ERROR Number of times the ATTIC did not get a port from the Octel 200/300...
Page 247: 7.2.7 Installation Checklist
7.2-51 7.2.7 INSTALLATION CHECKLIST This section offers a checklist of issues relating to the Octel 200/300 and to the System 75. The list is presented in the order in which the installation process should be followed. For details regarding any topic, refer to the sections of this chapter pertaining to the issue.
Page 248 Description Complete List CORs currently in use on the System 75. Designate two new CORs to be exclusively for the Octel 200/300 (COR DP & COR LK). Designate a COR to be used for the operator. Designate a COR to be used for the trunks terminating at the Octel 200/300 Change the COR (referred to as COR LK).
Page 249 Change the Group Name to fit this format: T-XXX. XXX is the trunk group TAC. If the trunk group is to be answered by the Octel 200/300 enter the Hunt Group pilot number for the incoming destination. Repeat steps 2 through 4 for each trunk group listed in step 1.
Page 250: Station Configuration Checklist
Table 7.2-10 Installing the ATTIC Board Item Description Command Complete Forward the Octel 200/300 ports. CD x y z Plug the ATTIC board(s) into the configured slot(s). Refer to the power-on routine and monitor the LEDs. Plug the 25-pair cable into the ATTIC slot.
Page 251: 11 Configuration Changes To Cpi
For mailboxes requiring Quick Greeting Activation, modify .M INFO INFORMATION Table Index 25 to be YES. Index # 25 Configure all Octel 200/300 ports to be YES for outcall. .M INFO Index # 25 For collocated system, modify System Parameter 130 to .M SYS 130...
Page 252 Table 7.2-12 Test Equipment Quantity Description 2500-type (single-line touchtone) phones, one with a message waiting indicator. Terminal/teleprinter directly connected to the Octel 200/300 via RS-232C cable. Hard copy of the Octel 200/300 configuration database. Hard copy of the System 75 configuration Single-line analog extensions (connected to RJ11 jacks) for testing.
Page 253 7.3-8 ATTIC Link Digital Phone and Octel 200/300 Port Extensions ....... .
Page 254: Test Equipment
................7.3-49 Octel 200/300 S.4.1...
Page 255: 7.3.1 Operation Of At&T System 85 Adaptive Integration
Message waiting indication (MWI) — Control of message waiting lamps on PBX stations. Called party identification — Identification of the source and original destination of calls forwarded to the Octel 200/300. The Octel 200/300 can process the call and provide call coverage based upon the type of call and desired coverage.
Page 256: System 85 Call Coverage
The covering extension is specified when the feature is activated. When the Octel 200/300 receives a call forwarded from an extension that is Call Forwarding All Calls, it describes the status of the call with the prompt “(name) is unavailable.”...
Page 257: Called Party Identification Call Processing
Forward All Calls “(name) is unavailable” * If System Parameter 115 is set to Y, Octel 200/300 uses “(name) is busy” instead of “(name) is on the phone.” Refer to Feature Description volume, Customizing Mailbox Features chapter, for more information.
Page 258 Direct Internal Calls A caller can access the Octel 200/300 directly to enter a mailbox, send a quick message, or make a network call. For these direct internal calls, the System 85 sends this type of call record: a = XXX Name to YYY XXX is the number of the calling extension and YYY is the Octel 200/300 access extension number.
Page 259 Octel 200/300 knows which caller left the message. When the person receiving the message listens to it, the Octel 200/300 is able to play the name of the caller who left the message before playing the message itself. The person receiving the message may automatically reply to the message.
Page 260: 7.3.2 At&T System 85 Requirements
Digital Voice Terminal Extensions. The System 85 must provide digital voice terminal ports per ATTIC board for the four ATTIC links in Octel 200/300. If two or more AT&T digital line cards (part no. SN270B) are available, spreading the digital links on different digital line cards in the System 85 provides greater reliability.
Page 261: 7.3.3 At&T System 85 Configuration
7.3-7 7.3.3 AT&T SYSTEM 85 CONFIGURATION Several changes must be made to the System 85 configuration to utilize Octel 200/300’s AI features. The System 85 configuration used for Octel 200/300 with AI is slightly different from the configuration used for a non-integrated Octel 200/300.
Page 262: Naming Conventions
40 characters long. If an extension is given a name, Adaptive Integration requires that it meet certain restrictions. The Octel 200/300 port extensions, the link extensions, trunk groups, and the pilot number of the UCD/EUCD/ACD group must be given names.
Page 263 The configuration of the digital links and the Octel 200/300 ports are closely related. Each extension used for a Octel 200/300 port must also appear on one of the digital sets. The digital phone that supports the link is limited to eight appearances. Each port is configured on only one of the two digital phones associated with integration links.
Page 264 7.3-10 Integration Volume 1. Start by selecting extension numbers for each Octel 200/300 port and an extension number for each link. Allocate two Classes of Service (COS): One for the port extensions One for the extensions dedicated to each of the links.
Page 265 AT&T System 85/Definity G2 Adaptive Integration 7.3-11 The other attributes can be enabled/disabled as required at the particular installation. 3. Define the System 85 COS attributes for Octel 200/300 extensions. The COS should have these attributes: Automatic Callback - Disabled...
Page 266 Configure Links according to Figure 7.3-1 and Figure 7.3-5. If the figure specifies an extension for a Octel 200/300 port that does not exist in your system (e.g., Port 7 in a 4 port system), leave the specified key unconfigured. Assign the following:...
Page 267 7. Repeat step 5 and 6 for all Links. 8. Create the terminal ACD (UCD) hunt group containing the extensions of the Octel 200/300 ports. Assign the extension for Octel 200/300 Port 1 as the supervisor’s extension. Create a pilot number for the ACD (UCD) hunt group.
Page 268: Integration Unit 1, Link 1 And Integration Unit 1, Link 2 (Four Ports Or Less)
TRANSFER (19) (31) DROP HOLD (20) (32) (21) (33) (22) (34) (23) (35) (24) (36) Oper RECALL DISCONNECT MESSAGE Figure 7.3-1 Integration Unit 1, Link 1 and Integration Unit 1, Link 2 (Four Ports or less) Octel 200/300 S.4.1 PB60019-01...
Page 269: Integration Unit 1, Link 1 (Five Or More Ports)
LEXT (29) (DPEXT#9) (18) (30) CONFERENCE TRANSFER (19) (31) DROP HOLD (20) (32) (21) (33) (22) (34) (23) (35) (24) (36) Oper RECALL DISCONNECT MESSAGE Figure 7.3-2 Integration Unit 1, Link 1 (Five or More Ports) PB60019-01 Octel 200/300 S.4.1...
Page 270: Integration Unit 1, Link 2 (Five Or More Ports)
(LEXT) (29) (DPEXT#10) (18) (30) CONFERENCE TRANSFER (19) (31) DROP HOLD (20) (32) (21) (33) (22) (34) (23) (35) (24) (36) Oper RECALL DISCONNECT MESSAGE Figure 7.3-3 Integration Unit 1, Link 2 (Five or More Ports) Octel 200/300 S.4.1 PB60019-01...
Page 271: Integration Unit 2, Link 1 (Five Or More Ports)
(12) (29) (DPEXT#25) (18) (30) CONFERENCE TRANSFER (19) (31) DROP HOLD (20) (32) (21) (33) (22) (34) (23) (35) (24) (36) Oper RECALL DISCONNECT MESSAGE Figure 7.3-4 Integration Unit 2, Link 1 (Five or More Ports) PB60019-01 Octel 200/300 S.4.1...
Page 272: Integration Unit 2, Link 2 (Five Or More Ports)
(LEXT) (29) (DPEXT#26) (18) (30) CONFERENCE TRANSFER (19) (31) DROP HOLD (20) (32) (21) (33) (22) (34) (23) (35) (24) (36) Oper RECALL DISCONNECT MESSAGE Figure 7.3-5 Integration Unit 2, Link 2 (Five or More Ports) Octel 200/300 S.4.1 PB60019-01...
Page 273: Call Coverage
7.3-19 Call Coverage All extensions that are to use Octel 200/300 for call coverage must be assigned Call Coverage Group that includes Octel 200/300 as a coverage point. This may require addition of new Call Coverage Groups as well as modification of existing groups.
Page 274: Station Extensions
7.3-20 Integration Volume The trunk group configuration is as follows: 1. List the System 85 trunk groups. Note those that are answered directly by Octel 200/300 2. Change the trunk group’s name to fit this format: T-XXX XXX is the trunk group’s TAC (Trunk Access Code).
Page 275: 7.3.4 Octel 200/300 Configuration
7.3-21 7.3.4 OCTEL 200/300 CONFIGURATION This section describes the changes that must be made to the Octel 200/300 configuration for Message waiting indication and called party identification. The ATTIC integration card can be configured in any slot. Refer to the Configuration volume, Slots Table chapter, for instructions on configuring the card and message waiting.
Page 276: Changes For Called Party Identification
Refer to the Configuration volume, SLOTS Table, How to Configure the Slots Table section, for more information. Changes for Called Party Identification To configure the Octel 200/300 with Called Party Identification on a System 85, the following configuration changes must be made through the UPDATE program. Mailbox COS COS Attribute 15 —...
Page 277 If 9 to 32 ports are configured, the Octel 200/300 makes outcalls when at least three ports are idle. If more than 32 ports are configured, the Octel 200/300 makes outcalls when at least four ports are idle.
Page 278 ATTIC. This system parameter provides a fail-safe mode of operation. The ports answer calls in AX mode in the event that Octel 200/300 does not receive call information from the digit display links.
Page 279: 7.3.5 At&T System 85 Testing And Installation
This section describes the procedures for testing and installation of System 85 Adaptive Integration. The System 85 and the Octel 200/300 should always be checked for proper operation after any changes are made to the system configuration. In addition to the system test, there are some tests that should be made before Octel 200/300 is connected.
Page 280: Configuration Of Test Extensions
EXT-C is replaced with the extension number. In the tests that follow, the number of this extension is referred to as EXT-C. Assign this a coverage group in which Octel 200/300 is the first coverage point. The coverage group must specify forwarding on RNA and busy.
Page 281: Function Key Layout For 7407D Display Telephone
Line 2 Line 7 Line 3 Line 8 Line 4 Line 9 Line 5 Line 10 lwc-store lwc-cancel Oper inspect normal Display Select Ring Speaker Microphone Message Figure 7.3-6 Function Key Layout for 7407D Display Telephone PB60019-01 Octel 200/300 S.4.1...
Page 282: Testing Procedure
This test verifies that dial tone is present on each of the single line analog extensions used for the Octel 200/300 ports. Disconnect the 25-pair cables from the back of the Octel 200/300. b. Connect the analog modular adapter to the 25-pair cable associated with slot 1.
Page 283 Hang up phone B. Connect phone B to the RJ11 jack of the next Octel 200/300 port extension and repeat steps e. though g. until every Octel 200/300 port extension has been tested. 4. DIGITAL LINE EXTENSION NUMBER VERIFICATION This test verifies that the PBX extension numbers assigned to digital links used for AI match the corresponding extension numbers in the Octel 200/300 SLOTS Table.
Page 284 Repeat steps a. through d. for all units and links configured for call processing. 5. PBX BUSY FORWARD TEST This test verifies that a call to a busy extension forwards to the Octel 200/300 access number. Connect the 356A adapter to the 25-pair cable associated with the configured slot.
Page 285 Connect one digital phone to the jack position of the adapter that corresponds to Integration Unit 1, Link 1 and connect the second digital phone to the jack position that corresponds to Integration Unit 1, Link 2. PB60019-01 Octel 200/300 S.4.1...
Page 286 If the display does not contain this information, determine the cause and correct the problem before continuing. Hang up phone A and phone C. Call forwarded on RNA g. Using phone A, call phone C. Let phone C ring until the call forwards to the Octel 200/300 hunt group. Octel 200/300 S.4.1...
Page 287 Determine the cause and correct the problem before continuing. Connect phone B to the jack position of the modular adapter of the next Octel 200/300 port extension. Repeat steps b. through d. until every Octel 200/300 port has successfully transferred a call to the attendant.
Page 288: Installation Of The Attic Board
All cross-connections to the PBX must be completed before proceeding. Changes to connections should only be made while the integration card is not installed in the Octel 200/300. Cross connecting Caution! integration links when the integration card is installed may result in damage to the integration card.
Page 289: Testing Of Adaptive Integration Features
System 85 coverage groups for forwarding on RNA. 2. TESTING PORTS This test verifies that all System 85 port extensions are connected to the correct Octel 200/300 ports. Modify System Parameter 117 to be 0. When testing is complete, modify System Parameter 117 back to 5 rings.
Page 290 This test verifies that the Octel 200/300 processes a direct internal call correctly. From phone C, call the extension number for Octel 200/300 access (the pilot number of the hunt group). Does Octel 200/300 answer with “To enter your mailbox press pound...” ? Determine the cause and correct the problem before continuing.
Page 291 200/300. Does the Octel 200/300 answer properly? Determine the cause and correct the problem before continuing. b. Enter the extension of phone C. The Octel 200/300 should respond with “Thank you, just a moment. . .” Does phone C start ringing? Correct the problem before continuing.
Page 292 Determine the cause and correct the problem before continuing. From phone A, call out and back in on a trunk auto-terminated to the Octel 200/300 When the Octel 200/300 answers, listen to the complete company greeting; let the system time out (do not enter any digits).
Page 293 You may prefer to use the Quick Message feature to leave a message for phone C instead of following the instructions in step d. and step e. d. Enter the extension number of phone C. Does the Octel 200/300 respond with “Thank you, just a moment...”? The Octel 200/300 should respond with “Extension EXT-C is busy/unavailable.
Page 294 Take phone C off-hook to make it appear busy. b. From phone A, call phone C. Does the Octel 200/300 answer with the greeting for Trunk Group 0 (zero)? Determine the cause and correct the problem before continuing.
Page 295 12. TESTING THE HUNT GROUP This test verifies that each member of the Hunt Group can receive calls. From phone A, call the Octel 200/300 hunt group. b. Determine which port answered the call by entering at the @ prompt...
Page 296: 7.3.6 At&T System 85 Maintenance
(1 or 2) The following are definitions of the fields displayed when listing the state of the ATTIC board. Card ID The CARD ID states the type of equipped integration card. Octel 200/300 S.4.1 PB60019-01...
Page 297 LINK-INDEPENDENT PEGS. The following independent pegs are listed by the LIST INTEGRATION command. PEG NAME DESCRIPTION IC ERROR Number of times the ATTIC timed out waiting for Octel 200/300 to process a reply. WRONG CNT Number of times the ATTIC processor received an invalid interrupt.
Page 298 LED did not light. INIT CNT Number of times the link has be initialized. For information on hardware errors regarding integrated systems, refer to the Installation and Maintenance volume, System Errors and Traffic Pegs chapter, for more information. Octel 200/300 S.4.1 PB60019-01...
Page 299: 7.3.7 Installation Checklist
7.3-45 7.3.7 INSTALLATION CHECKLIST This section offers a checklist of issues relating to the Octel 200/300 and to the System 85. The list is presented in the order in which the installation process should be followed. For details regarding any topic, refer to the sections of this chapter pertaining to the issue.
Page 300 Create a new Call Coverage Group or modify an existing Call Coverage Group to include Octel 200/300 as a coverage point. Assign all extensions that are to forward to the Octel 200/300 to that Call Coverage Group. Check Coverage Criteria. Make sure the number of rings for don’t answer is one greater than the number of rings specified for RNA in the Octel 200/300.
Page 301: Station Configuration Checklist
List the existing System 85’s trunk groups. Note those that are to be directed to the Octel 200/300. Change Trunk Groups Name field to be answered by the Octel 200/300 to read T-XXX (XXX = Trunk Group Access Code in the PBX).
Page 302 Add Attribute 15 to the COS of all mailboxes associated .A COS with extensions that forward to the Octel 200/300. All ports should be configured in AX mode. .M SLOT Add a COS with Attribute 58 to those ports that do not .A COS...
Page 303 Quantity Description 2500-type (single line touchtone) phones, one with a message waiting indicator. Terminal/teleprinter directly connected to Octel 200/300 J1 or SP1 via RS-232C cable. Hard copy of the Octel 200/300 Configuration Database. Hard copy of the System 85 Configuration.
Page 305: Configuration
7.3A-4 To Assign a COS to an Extension for the Octel 200/300 Ports and Links 1 and 2 ......
Page 306 7.3A-2 Integration Volume PB60019-01 Octel 200/300 S.4.1...
Page 307 ACD Agent Override Disabled Send All Calls Disabled PROC 010, word 2 Field Name Set To Meaning COS number COS for the Octel 200/300 ports Originate LWC (Enabled) Receive LWC (Disabled) Off net Fwding (Disabled) SMDR Acct code (Account code not...
Page 308: To Define The Cos For The Octel 200/300 Ports
Term. Restrict (Not restricted) Toll/Code Restrict (Not restricted) Auto route selection Site dependant FRL Level Site dependant To Define the COS for the Octel 200/300 Ports PROC 010,word 1 Field Name Set To Meaning Not Used Not used Automatic Callback...
Page 309: To Assign A Cos To An Extension For The Octel 200/300 Ports And Links 1 And
(Not restricted) Toll/Code Restrict (Not restricted) Auto route selection Site dependant FRL Level Site dependant To Assign a COS to an Extension for the Octel 200/300 Ports and Links 1 and 2 PROC 000, word 1 Field Name Set To Meaning...
Page 310: To Assign The Equipment Location For The Digital Links
Type of Ringing (Rings) Home Terminal (Home Terminal) Originating Only (Not Originating Only) To Assign the Octel 200/300 Ports as an Appearance on a Link PROC 052, word 1 Field Name Set To Meaning Eqpt. Location Location of the link...
Page 311 (Display Module) Button number (1st Display Button) Button encode (Inspect) PROC 054, word 4 Field Name Set To Meaning Location Location of Link Type of equipment (Display Module) Button number (2nd Display Button) Button encode (Normal) PB60019-01 Octel 200/300 S.4.1...
Page 312 Originating Only (Not originating only) PROC 052, word 2 Field Name Set To Meaning Extn Number Extension of an Octel 200/300 port Line Appearance # Type of transfer Ringing Transfer (No Ringing Transfer) PROC 054, word 1 Field Name Set To...
Page 313: To Busy Out Cms
Regular ACD split PROC 026,word 2 Field Name Set To Meaning Group number ACD group for the Octel 200/300 ports Supervisor Extension of Octel 200/300 port 1 Extension of Pilot number Priority Extn. Number − (Not used) PB60019-01 Octel 200/300 S.4.1...
Page 314: To Add The Octel 200/300 Port Extensions To The Acd (Ucd) Group
Short Display Start Outgoing Display − Not applicable Copy Mode Not a copy Copy Name Not used PROC 12, word 2 Specify the name as ”D-XXXX”, where XXXX is the number associated with the Octel 200/300 port extensions. PB60019-01 Octel 200/300 S.4.1...
Page 315 7.3B-4 To Assign A Cos for the Octel 200/300 Ports .............
Page 316 7.3B-2 Integration Volume Octel 200/300 S.4.1 PB60019-01...
Page 317 Refers to the extension number associated with a Octel 200/300 port. DPECT #X DPEXT is used when configuring a Octel 200/300 port and refers to the extension number of the port currently being configured. DPEXT#x refers to the extension number of Port x.
Page 318 Call Forward-Off Net Send All Calls Call Hold SMDR Account Code Required Calling Number Display Stop Hunt Call Waiting Timed Recall Exempt Touchtone Data Protection Transfer/Con-Three Way Ring Ping Immediate ACD Queue Status Display Page 1 of 2 Octel 200/300 S.4.1 PB60019-01...
Page 319 Misc. Trunk Restriction Grp. 6 Outward Misc. Trunk Restriction Grp. 7 Terminal to Terminal Misc. Trunk Restriction Grp. 8 Termination Toll Restriction Code Restriction Level: Facility Restriction Level: Bearer Capability: ISDN Routing: Page 2 of 2 <endmask> PB60019-01 Octel 200/300 S.4.1...
Page 320: To Assign A Cos For The Octel 200/300 Ports
Stop Hunt Call Waiting Timed Recall Exempt Touchtone Data Protection Transfer/Conf-Three Way Ring Ping Immediate ACD Queue Status Display Page 1 of 2 Note that for the Octel 200/300, the “ACD (UCD) member” must be defined. Octel 200/300 S.4.1 PB60019-01...
Page 321 Misc. Trunk Restriction Grp. 6 Outward Misc. Trunk Restriction Grp. 7 Terminal to Terminal Misc. Trunk Restriction Grp. 8 Termination Toll Restriction Code Restriction Level: Facility Restriction Level: Bearer Capability: ISDN Routing: Page 2 of 2 <endmask> PB60019-01 Octel 200/300 S.4.1...
Page 322: Physical Equipment Location Assignment
Price Element 2: Headset? Price Element 3: Price Element 4: Abbreviated Dialing- A List Type: B List Type: System list access? Page 1 of 1 <endmask> Build a straight line set for each Octel 200/300 port. Octel 200/300 S.4.1 PB60019-01...
Page 323 AT&T System 85/Definity G2 CSM Configuration Descriptions 7.3B-9 4. TO DEFINE ACTUAL OCTEL 200/300 EXTENSIONS CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add Last Service Request Number: Date: State: W Extension No: (DPEXT) Analog? n Set Type: 2500 Class of Service: DPCOS...
Page 324 7.3B-10 Integration Volume CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add User Name: D-(DPEXT) Octel 200/300 Location: Room: Electronic Mail Address: Supervisor’s Name: Organization No.: Auth Code: Page 3 of 4 CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add User Name: D-(DPEXT) Octel 200/300 Definable Fields Page 4 of 4 <endmask>...
Page 325: To Program Digital Link 1 On Integration Unit
For Link 2, the Set ID will be the actual dedicated extension number associated with Link 2. When first adding a 36-button phone, button assignments 1 and 2 are reversed. Make sure button assignments 01 and 02 are exactly as shown above. Delete button assignments 03 through 07. PB60019-01 Octel 200/300 S.4.1...
Page 326 Button assignments must be programmed as shown above. For specific button assignments, refer to Section 7.3.3, AT&T System 85 Configuration, ATTIC Link Digital Phone and Octel 200/300 Port Extension. and to Figures 7.3-1 and 7.3-2 or Figures 7.3-3 and 7.3-4.
Page 327: To Assign Extension For Link 1 On Integration Unit
Extn is in Call Coverage group with extn #: OR Call Cov. Grp.: Controlled Restriction Group: Is Message retrieval allowed? Page 1 of 4 CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add NPA−NXX Designator: Page 2 of 4 PB60019-01 Octel 200/300 S.4.1...
Page 328 7.3B-14 Integration Volume CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add User Name: A−(IU1L1EXT) Octel 200/300 Location: Room: Electronic Mail Address: Supervisor’s Name: Organization No.: Auth Code: Page 3 of 4 CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add User Name: A−(IU1L1EXT) Octel 200/300 Definable Fields Page 4 of 4 <endmask>...
Page 329: To Program Digital Link 2 On Integration Unit 1
For Link 2, the Set ID will be the actual dedicated extension number associated with Link 2. When first adding a 36-button phone, button assignments 1 and 2 are reversed. Make sure button assignments 01 and 02 are exactly as shown above. Delete button assignments 03 through 07. PB60019-01 Octel 200/300 S.4.1...
Page 330 Button assignments must be programmed as shown above. For specific button assignments, refer to Section 7.3.3, AT&T System 85 Configuration, ATTIC Link Digital Phone and Octel 200/300 Port Extensions and to Figures 7.3-1 and 7.3-2 or Figures 7.3-3 and 7.3-4.
Page 331: To Assign Extension For Link 2 On Integration Unit
Extn is in Call Coverage group with extn #: OR Call Cov. Grp.: Controlled Restriction Group: Is Message retrieval allowed? Page 1 of 4 CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add NPA−NXX Designator: Page 2 of 4 PB60019-01 Octel 200/300 S.4.1...
Page 332 7.3B-18 Integration Volume CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add User Name: A−(IU1L2EXT) Octel 200/300 Location: Room: Electronic Mail Address: Supervisor’s Name: Organization No.: Auth Code: Page 3 of 4 CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add User Name: A−(IU1L2EXT) Octel 200/300 Definable Fields Page 4 of 4 <endmask>...
Page 333: To Program Digital Link 1 On Integration Unit
For Link 2, the Set ID will be the actual dedicated extension number associated with Link 2. When first adding a 36-button phone, button assignments 1 and 2 are reversed. Make sure button assignments 01 and 02 are exactly as shown above. Delete button assignments 03 through 07. PB60019-01 Octel 200/300 S.4.1...
Page 334 Button assignments must be programmed as shown above. For specific button assignments, refer to Section 7.3.3, AT&T System 85 Configuration, ATTIC Link Digital Phone and Octel 200/300 Port Extensions and to Figures 7.3-1 and 7.3-2 or Figures 7.3-3 and 7.3-4.
Page 335: To Assign Extension For Link 1 On Integration Unit
Extn is in Call Coverage group with extn #: OR Call Cov. Grp.: Controlled Restriction Group: Is Message retrieval allowed? Page 1 of 4 CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add NPA−NXX Designator: Page 2 of 4 PB60019-01 Octel 200/300 S.4.1...
Page 336 7.3B-22 Integration Volume CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add User Name: A−(IU2L1EXT) Octel 200/300 Location: Room: Electronic Mail Address: Supervisor’s Name: Organization No.: Auth Code: Page 3 of 4 CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add User Name: A−(IU2L1EXT) Octel 200/300 Definable Fields Page 4 of 4 <endmask>...
Page 337: To Program Digital Link 2 On Integration Unit
For Link 2, the Set ID will be the actual dedicated extension number associated with Link 2. When first adding a 36-button phone, button assignments 1 and 2 are reversed. Make sure button assignments 01 and 02 are exactly as shown above. Delete button assignments 03 through 07. PB60019-01 Octel 200/300 S.4.1...
Page 338 Button assignments must be programmed as shown above. For specific button assignments, refer to Section 7.3.3, AT&T System 85 Configuration, ATTIC Link Digital Phone and Octel 200/300 Port Extensions and to Figures 5.2-1 and 5.2-2 or Figures 5.2-3 and 5.2-4.
Page 339: To Assign Extension For Link 2 On Integration Unit
Extn is in Call Coverage group with extn #: OR Call Cov. Grp.: Controlled Restriction Group: Is Message retrieval allowed? Page 1 of 4 CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add NPA−NXX Designator: Page 2 of 4 PB60019-01 Octel 200/300 S.4.1...
Page 340 7.3B-26 Integration Volume CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add User Name: A−(IU2L2EXT) Octel 200/300 Location: Room: Electronic Mail Address: Supervisor’s Name: Organization No.: Auth Code: Page 3 of 4 CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add User Name: A−(IU2L2EXT) Octel 200/300 Definable Fields Page 4 of 4 <endmask>...
Page 341 14. TO DEFINE A DUMMY TRUNK GROUP CSM Release V4 Sys85:R2L4 CON: PATH:fm:admin:trk-grp:add (TGRP) Trunk Group No.: Dial Access Code: Trunk Type: Signaling Type: Page 1 of 3 The trunk type must be 6 (Special Queueing). PB60019-01 Octel 200/300 S.4.1...
Page 342: 15. To Define An Acd (Ucd) Group
Under the field “Queuing Trunk Group”, only 1 trunk group can be defined per ACD (UCD) group. When you define an ACD (UCD) group “Supervisor Extension No.”, the System 85 automatically assigns that extension number as a Member 0 of the ACD split. Octel 200/300 S.4.1 PB60019-01...
Page 343: 16. To Define The Members Of The Acd (Ucd) Group
No. Extn Extn No. Extn 0 (DPEXT#1) 1 (DPEXT#2) 2 (DPEXT#3) 3 (DPEXT#4) Page 1 of 1 <endmask> Add ACD (UCD) members to assign the balance of the Octel 200/300 ports to the ACD (UCD) hunt group. PB60019-01 Octel 200/300 S.4.1...
Page 344: 17. To Define The Vector Directory Number
CSM Release V4 Sys85:R2L4 CON: PATH: tcm:admin:vdn-add Vector Directory Number:(ACDVDN) Class of Service:DPCOS Name:A-(ACDVDN) Octel 200/300 Vector Number:ACDVEC Page 1 of 1 <endmask> The Vector Directory Number must be a valid unused extension in the System 85. Octel 200/300 S.4.1...
Page 345: 18. To Set Up Vector Features For Overflow
Page 1 of 2 The Vector features shown above perform an unconditional queuing to the Octel 200/300 hunt group. Call Vectoring has many features and may allow the customer many different ways of handling the ACD (UCD) hunt group. See System 85 documentation for more information on Call Vectoring.
Page 346: 19. To Assign The Call Vector To The Vectoring Directory Number
19. TO ASSIGN THE CALL VECTOR TO THE VECTORING DIRECTORY NUMBER CSM Release V4 Sys85:R2L4 CON: PATH: tcm:admin:call-vectoring:add Vector Number: (ACDVEC) Vector Measured Console Return Call Directory No. Message Char. Indicator -−−−−−−−−−−−− −−−−−−−− −−−−−−−−−−−− −−−−−−−−−−−− (ACDVDN) / / / Page 1 of 1 <endmask> Octel 200/300 S.4.1 PB60019-01...
Page 347: Chapter 8.1 Rolm Cbx Adaptive Integration
..........8.2-1 PB60019-01 Octel 200/300 S.4.1...
Page 349 Adaptive Integration, including Message Waiting Indication and Called Party Identification. When planning, configuring, installing and testing ROLM CBX or ROLM 9751, Model 30 or Model 80, be sure to use the correct chapter in this manual. PB60019-01 Octel 200/300 S.4.1...
Page 351 8.1-5 Octel 200/300 Port Extensions ............
Page 352: Test Equipment
8.1-1 Display Phone Keyboard Layout Octel 200/300 ..........
Page 353: Chapter 8.1 Rolm Cbx Adaptive Integration
The trunk access code and member number of external calls that have been directed to the Octel 200/300 for primary answering. The status of the called party (busy vs. no answer) when calls are forwarded to the Octel 200/300. Personal assistance operates in conjunction with called party identification in integrated systems. For many applications, Personal Assistance and Auto-Transfer to Assistance are required.
Page 354 Direct Calls from External Trunks If the call comes in on a trunk, the CBX provides the Octel 200/300 with the trunk access code as the source of the call. Trunks may be directed to the Octel 200/300 ports for answering via the CBX dedicated trunk feature (DED).
Page 355 Forwarded Internal Calls When one extension calls another and the call is forwarded to the Octel 200/300, the CBX sends the calling and called extension numbers. The Octel 200/300 answers the call and informs the caller that the extension is unavailable or busy and offers options.
Page 356: 8.1.2 Rolm Cbx Requirements
All Octel 200/300 ports are configured to be in a single terminal hunt group. The extension number of each port also has appearances on the display phones. Calls on incoming trunks to be handled by Octel 200/300 are directed to this hunt group using the ROLM DED (dedicated trunk) feature.
Page 357: 8.1.3 Rolm Specific Configuration
The Octel 200/300 ports must be configured into a hunt group. The Octel 200/300 hunt group must be configured with a fail-safe extension for no-answer and busy conditions. If the Octel 200/300 cannot answer a call due to a system failure, or if all the Octel 200/300 ports are busy, the call forwards to the fail-safe extension.
Page 358 There are two parts to the display phone configuration. The first part is the feature table configuration and the second part is the Octel 200/300 port appearance configuration. Feature Table Configuration. The following are the key configurations for the ROLM display phone.
Page 359 8000 series software. Commands and responses may vary in further releases of ROLM software. What is critical, regardless of ROLM software release, is that button appearances of Octel 200/300 ports are set for “No Ring.” Only the primary line (Line-001) should be set for ring.
Page 360: Display Phone Keyboard Layout Octel
LINE-001 dp-0 dp-# dp-* hold connect transfer NOTE: L/A = Line Appearance. n.c. = not configured Figure 8.1-1 Display Phone Keyboard Layout Octel 200/300 PB60019-01 Octel 200/300 S.4.1...
Page 361: Display Phone Keyboard Layout - With 16 To 32 Ports (Odd Ports)
LINE-001 dp-0 dp-# dp-* hold connect transfer NOTE: L/A = Line Appearance. n.c. = not configured Figure 8.1-2 Display Phone Keyboard Layout — With 16 to 32 Ports (Odd ports) PB60019-01 Octel 200/300 S.4.1...
Page 362: Display Phone Keyboard Layout - With 16 To 32 Ports (Even Ports)
LINE-001 dp-0 dp-# dp-* hold connect transfer NOTE: L/A = Line Appearance. n.c. = not configured Figure 8.1-3 Display Phone Keyboard Layout — With 16 to 32 Ports (Even ports) PB60019-01 Octel 200/300 S.4.1...
Page 363: Customer Telephones
Telephones with assigned mailboxes for secondary answering should be forwarded to the pilot number of the Octel 200/300 hunt group. This allows complete integration of both internal and external calls. However, if internal callers want the ability to use the Camp-on feature on a busy extension, the CBX should be programmed not to forward internal calls on a busy condition.
Page 364: 8.1.4 Octel 200/300 Configuration
The system can be configured with message waiting indication and called party identification. The sections below detail the configuration changes that must be made. Changes for Message Waiting Indication To configure the Octel 200/300 with message waiting indication on a CBX, the following configuration changes must be made through the program.
Page 365 Modify System Parameter 116 to be YES. System Parameter 117 — RINGBACKS BEFORE ANSWERING AX PORT Modify System Parameter 117 to be 5. This gives Octel 200/300 extra time to receive the call records from the CBX. The Octel 200/300 normally answers the call immediately within one ring upon receiving a call record from the RIC.
Page 366 8.1-14 Integration Volume parameter provides a fail-safe mode of operation. The ports answer calls in AX mode in the event that the Octel 200/300 does not receive call information from the digit display links. System Parameter 130 — SEND DTMF A FOR FORWARDED...
Page 367: 8.1.5 Rolm Testing
ROLM board. In addition to the system test, there are some tests that should be made before the Octel 200/300 is connected. Refer to Table 8.1-1 for the items required for testing. Table 8.1-1 Test Equipment Quantity Description 2500-type (single line touchtone) phones, one with a message waiting indicator.
Page 368 From phone A enter the extension number associated with phone B. g. Does phone B ring? ' Does the LED flash on both display phones that correspond to the Octel 200/300 port called? ' Answer the call using phone B and verify the circuit quality.
Page 369 Repeat for all ports and units until all have been tested. 3. PBX FUNCTIONAL TEST (FOR NEW INSTALL) This test verifies that each Octel 200/300 port extension can initiate a transfer by doing a hookswitch flash and a transfer code (or just a hookswitch flash), before entering an extension number.
Page 370 RIC link so that the Octel 200/300 port is configured as No Ring. d. Continue the test by calling from phone C to the next Octel 200/300 port extension number and perform step c. again.
Page 371 Connect the display phone to the jack position of the modular adapter associated with Unit 1, Link 2 on the RIC board and repeat the tests. g. Repeat the sequence for any other integration links configured for MWI. PB60019-01 Octel 200/300 S.4.1...
Page 372 Does the display on the display phone look like this? YYYY XXXX phone C XXXX phone A YYYY Determine the cause and correct the problem before continuing. Repeat the sequence for all Octel 200/300 links configured for call processing. PB60019-01 Octel 200/300 S.4.1...
Page 373 On the terminal, at the @ prompt, enter The port number in the IDL2 state is the port that the Octel 200/300 thinks was called. If that is not the port you intended to call, the lines should be changed so that the correct line is connected to the correct port.
Page 374 11. CALLING A RING-NO-ANSWER EXTENSION This test verifies that the Octel 200/300 properly handles RNA calls. Three different types of calls to an RNA extension may be sent to the Octel 200/300 for secondary answering. A call from an internal extension to an RNA extension. This call should forward into the Octel 200/300 through the PBX forwarding mechanism and play the “unavailable”...
Page 375 Rolm CBX Adaptive Integration 8.1-23 d. While still connected to the Octel 200/300, enter MBX number XXXX. Did the Octel 200/300 respond with the prompt, “Thank you. Just a moment . . .,” and did phone C start to ring again? Continue.
Page 376 Determine the cause and correct before continuing. g. While still connected to the Octel 200/300, enter MBX number YYYY. h. Did the Octel 200/300 respond with the prompt, “Thank you. Just a moment. . .” ? Continue. Determine the cause and correct the problem before continuing.
Page 377 Does the call overflow to the correct answering extension as determined for fail-safe operation? Determine the cause and correct the problem before continuing. Remove the busy condition from all Octel 200/300 port PBX extensions by entering at the @ prompt...
Page 378 Does the port that answered show WFD state? Determine the cause and correct the problem before continuing. g. From phone A, enter the extension number associated with phone C. The Octel 200/300 should respond with, “Thank you. Just a moment.”...
Page 379 This test verifies that the Octel 200/300 can transfer a call to the intercept position (attendant) when the caller does nothing or presses From phone A, call outside of the PBX and back in on a trunk dedicated to the Octel 200/300. b. Does the Octel 200/300 answer correctly? Listen to the complete company greeting.
Page 380 Answer phone C, or call Octel 200/300, and enter the mailbox if the indicator is lit. The Octel 200/300 should respond with “...(Name) has X messages. Ready,” If set, the security code is requested.
Page 381 All cross-connections to the PBX must be completed before proceeding. Changes to connections should only be made while the integration card is not installed in the Octel 200/300. Cross connecting Caution! integration links when the integration card is installed may result in damage to the integration card.
Page 382: Led Operation For Power-Up Routine
YELLOW Unit 2, Link 1 YELLOW Unit 1, Link 1 YELLOW Unit 2, Link 1 Code Download complete GREEN YELLOW Unit 1, Link 1 YELLOW Unit 2, Link 1 YELLOW Unit 1, Link 1 YELLOW Unit 2, Link 1 PB60019-01 Octel 200/300 S.4.1...
Page 383 The following are definitions of the fields displayed when listing the state of the RIC board. Card ID The CARD ID states the type of integration card. Card Status There are four possible states for the card: The RIC is down and not responding to the CARD DOWN software. PB60019-01 Octel 200/300 S.4.1...
Page 384 The number of times uplink transmissions had to be unlocked. PEG 3 The number of times the trace reply buffer overflowed. PEG 4 Not used. PEG 5 The number of times the LED event reply buffer overflowed. PB60019-01 Octel 200/300 S.4.1...
Page 385 PEG10 (0−1) The number of times KEY.LOOP.TEST failed per link. For information on hardware errors regarding integrated systems, refer to the Installation and Maintenance volume, System Errors and Traffic Pegs chapter, for more information. PB60019-01 Octel 200/300 S.4.1...
Page 386: Octel 200/300 Requirements
8.1-34 Integration Volume 8.1.8 INSTALLATION CHECKLIST This section offers a checklist of issues relating to the Octel 200/300 and to the CBX. The list is presented in the order in which the installation process should be followed. For details regarding any topic, refer to the sections of this chapter.
Page 387: Octel 200/300 Configuration Changes To Cpi
Rolm CBX Adaptive Integration 8.1-35 Actual Installation Table 8.1-5 Octel 200/300 Configuration Changes to MWI Item Description Complete Command Modify System Parameter 9 to be 700 (increase flash .M SYS 9 time). Modify System Parameter 116 to be YES. .M SYS 116 Add Attribute 9 to the COS of all mailboxes requiring .A COS...
Page 388: Installing The Ric Board
Configure the MSG CTR feature on both display phones on designated button. See Figure 8.1-1 through Figure 8.1-3. Configure Octel 200/300 ports into a hunt group with a RNA and busy fail-safe. Configure user phones that want Adaptive Integration features to RNA and busy forward into Octel 200/300 hunt group.
Page 389 8.2.4 Octel 200/300 Configuration ............. . .
Page 390: Rolm Requirements
8.2-4 Octel 200/300 Configuration Changes to MWI ..........
Page 391 Message waiting indication (MWI) — control of message waiting lamps on PBX stations. Any information that can be provided to a display phone (either on the display itself or by the LEDs associated with the keys on the phone) is available to the Octel 200/300. This information includes the following: The extension number of an internal station calling the Octel 200/300 directly.
Page 392 Direct Calls from External Trunks If the call comes in on a trunk, the ROLM Model 30/80 CBX provides the Octel 200/300 with the trunk access code as the source of the call. Trunks may be directed to the Octel 200/300 ports for answering via the ROLM Model 30/80 CBX dedicated trunk feature (DIT).
Page 393 Customizing Mailbox Features chapter, for more information. Direct Internal Call A person can call the Octel 200/300 directly either to enter a mailbox, send a quick message, or make a network call. The Octel 200/300 recognizes these calls as internal, and not forwarded, since the display shows only the calling extension.
Page 394 The ROLM Model 30/80 CBX is configured differently for an integrated application than it is for a non-integrated Octel 200/300 installation. Neither the Octel 200/300 Links or the analog ports are configured in a hunt group. Instead, a group of phantom numbers is configured to appear on links that are used for call processing. These phantom numbers are configured in a hunt group, and the pilot number of that hunt group is used as the station forwarding target.
Page 395 8.2-5 Display Phone. The digital portion consists of four ROLMphone 400 telephone lines for the RIC board in the Octel 200/300. Connect the configured links to the RIC board. These ROLMphone 400 lines should be configured as described below. For the Octel 200, the RIC can be installed in slots A1 − A6.
Page 396 This section describes the changes that must be made to the ROLM 9751 so that the PBX can use the Octel 200/300’s Adaptive Integration features. To configure the switch, Change the system Dial Plan and add the new station numbers (STNO) for the ROLMphone 400s,...
Page 397 Line 7 Vacant Vacant Vacant Line 3 Line 8 Vacant Vacant Vacant Line 4 Vacant Vacant Vacant Vacant Line 5 Vacant Vacant Vacant Vacant Vacant Volume Vacant Volume Vacant Clear Vacant Prime Prog Vacant Hold Vacant Xfer PB60019-01 Octel 200/300 S.4.1...
Page 398 Field Set To CHAKEPRO: STNO: Prime number of the ROLMphone 400 Same Assign a free Key Standard Table number STD: Same DIGTYPE: Same RP400 KY01−KY05: Vacant LINE KY06−KY08: Vacant Vacant KY09: PRIME PRIME KY11−KY13: Vacant LINE Octel 200/300 S.4.1 PB60019-01...
Page 399 If the ports are not answered during the first attempt, the 9006i tries a second time before placing them out of service. If the ports are placed out of service, they remain out of service until enabled by a technician. PB60019-01 Octel 200/300 S.4.1...
Page 400 COSXCD: ORG: RSTRCPIN: Add Prime Line Add the prime line to the ROLMphone 400. Use the AMO, ADDKCSU. Field Set To ADDKASU: STNO: Prime number TYPE: PRIMEKEY: RIOP: ORLNPF: LAST TMLNPF: RING SGLBMOD: ABRING: APRIVAT: INS: Octel 200/300 S.4.1 PB60019-01...
Page 401 Translation Table chapter, for more information. Telephones with assigned mailboxes for secondary answering should be forwarded to the pilot number of hunt group of the phantom lines. This allows complete integration of both internal and external calls. PB60019-01 Octel 200/300 S.4.1...
Page 402 200/300 when the called station is busy. In order to have a visible message waiting indicator, digital phones must be configured to have a message waiting key (MW), and analog phones must be connected to a ROLM message waiting line card. Octel 200/300 S.4.1 PB60019-01...
Page 403 Changes for Message Waiting Indication To configure the Octel 200/300 with message waiting indication on a ROLM Model 30/80 CBX, the following configuration changes must be made through the program.
Page 404 8.2-14 Integration Volume Changes for Called Party Identification To configure the Octel 200/300 with called party identification on a ROLM Model 30/80 CBX, the following configuration changes must be made through the program. UPDATE Mailbox COS COS Attribute 15 — TRANSFER TO A RINGING EXTENSION Assign a COS with Attribute 15 to mailboxes of extensions that the ROLM Model 30/80 CBX forwards to Octel 200/300.
Page 405 System Parameter 130 — SEND DTMF A FOR FORWARDED CALLS For a collocated system, modify the value of this system parameter to be YES. This allows the Octel 200/300 to detect that a call has forwarded from one cabinet to another. System Parameter 243 —INTEGRATION: ROLM 9006 PICKUP CODE Modify System Parameter 243 to be *3.
Page 406 Refer to the ROLM Board Installation section in this chapter for the procedure for installing the ROLM board. In addition to the system test, there are some tests that should be made before the Octel 200/300 is connected. Refer to Table 8.2-1 for the items required for testing.
Page 407 If only one ROLMphone 400 is available, connect the phone to Link 1, perform all the tests and then connect the phone to Link 2 and repeat the tests. h. Repeat for all ports Octel 200/300 until all have been tested. PB60019-01 Octel 200/300 S.4.1...
Page 408 USER T 4. PBX BUSY FORWARD TEST This test verifies that a call to a busy extension forwards to the Octel 200/300 hunt group Connect phone B to the modular adapter position associated with port 1 of the Octel 200/300.
Page 409 ROLM 9751 Model 30/80 Adaptive Integration 8.2-19 5. PBX RING-NO-ANSWER FORWARD TEST This test verifies that a call to a ring-no-answer extension forwards to the Octel 200/300 hunt group Connect phone B to the modular adapter position associated with port 1 of the Octel 200/300.
Page 410 Link 1 on the RIC board. (The link programmed for call processing on the RIC board.) b. From phone C, call the pilot number for VMLINK (the pilot number for the Octel 200/300). Does the ROLMphone 400 look like this?
Page 411 Continue tests for each CPI Link configured. 8. CALLS TO THE INTERCEPT EXTENSION (ATTENDANT) (FOR NEW INSTALL) This test verifies that each Octel 200/300 port extension can transfer a call to the intercept extension (attendant). Connect phone B to the modular adapter position associated with port 1 of the Octel 200/300.
Page 412 10. CALLING A RING-NO-ANSWER EXTENSION This test verifies that the Octel 200/300 properly handles RNA calls. Three different types of calls to an RNA extension may be sent to the Octel 200/300 for secondary answering. A call from an internal extension to an RNA extension. This call should forward into Octel 200/300 through the PBX forwarding mechanism and play the “unavailable”...
Page 413 Determine the cause and correct the problem before continuing. d. While still connected to the Octel 200/300, enter MBX number CCCC. Did the Octel 200/300 respond with the prompt, “Thank you. Just a moment . . .” and did phone C start to ring again? Continue.
Page 414 8.2-24 Integration Volume 11. CALLING A BUSY EXTENSION This test verifies that the Octel 200/300 properly handles a call directed to a busy extension. (Use the same configuration as step 10 Take phone C off-hook. b. From phone A, call phone C.
Page 415 Does the port that answered show WFD state? Continue. Determine the cause and correct the problem before continuing. g. From phone A, enter the extension number associated with phone C. The Octel 200/300 should respond with, “Thank you. Just a moment.” h. Does phone C ring? Continue.
Page 416 This test verifies that the Octel 200/300 can transfer a call to the intercept position (attendant) when the caller does nothing or presses From phone A, call outside of the PBX and back in on a trunk dedicated to the Octel 200/300 b. Does the Octel 200/300 answer correctly? Listen to the complete company greeting.
Page 417 Determine the cause and correct the problem before continuing. h. Call the Octel 200/300, and enter the mailbox if the indicator is lit. The Octel 200/300 should respond with “...(Name) has X messages. Ready,” If set, the security code is requested.
Page 418: 8.2.6 Rolm Board Installation
All cross-connections to the PBX must be completed before proceeding. Changes to connections should only be made while the integration card is not installed in the Octel 200/300. Cross connecting Caution! integration links when the integration card is installed may result in damage to the integration card.
Page 419 If there are two units, both units would have to be initialized. Repeat this step for unit 2. 7. Test the system for proper operation. Once the down LED is OFF, the good LED is ON, and the yellow LEDs are ON, the card is working properly. PB60019-01 Octel 200/300 S.4.1...
Page 420: 8.2.7 Rolm Adaptive Integration Maintenance
(1 or 2). Clear Integration This command clears the RIC board pegs. The command is C INT C INT x y where x is the slot number. where y is the integration unit number (1 or 2). Octel 200/300 S.4.1 PB60019-01...
Page 421 The link is probably disconnected, or the polarity of the tip and ring wiring is reversed. Only states DOWN and DEAD are error conditions. If either of these states are found, check the PBX and the wiring. PB60019-01 Octel 200/300 S.4.1...
Page 422 The number of times the phantom extension display could not be decoded during initialization. For information on hardware errors regarding integrated systems, refer to the Installation and Maintenance volume, System Errors and Traffic Pegs chapter, for more information. Octel 200/300 S.4.1 PB60019-01...
Page 423 8.2-33 8.2.8 INSTALLATION CHECKLIST This section offers a checklist of issues relating to Octel 200/300 and to the ROLM Model 30/80 CBX. The list is presented in the order in which the installation process should be followed. For details regarding any topic, refer to the sections of this chapter.
Page 424: Octel 200/300 Configuration Changes To Mwi
8.2-34 Integration Volume Actual Installation Table 8.2-4 Octel 200/300 Configuration Changes to MWI Item Description Command Complete Modify System Parameter 9 to be 500 (increase flash .M SYS 9 time). Modify System Parameter 116 to be YES. .M SYS 116 Add Attribute 9 to the COS of all mailboxes requiring .A COS...
Page 425: Installing The Ric Board
ROLM 9751 Model 30/80 Adaptive Integration 8.2-35 Table 8.2-5 Octel 200/300 Configuration Changes to CPI Item Description Command Complete Mailbox and extension numbers must match. Modify System Parameter 9 to be 500 (increase flash .M SYS 9 time). Modify System Parameter 116 to be YES.
Page 427 ............The Octel 200/300 Configuration for Millennium Integration .
Page 428: Dce Pinouts For J2 To Pbx Integration Cable
9-17 The Octel 200/300 Configuration Changes for MWI ..........
Page 429: Chapter 9 Cortelco Millennium Adaptive Integration
Called Party Identification. When a call comes to a Millennium line that is forwarded to the Octel 200/300 the call record is sent over the data link to the message server. In most cases, the Octel 200/300 receives the call record within the first ring of the forwarded call and answers the call as soon as the call record is received.
Page 430 Direct Call. For a direct internal call, the Millennium provides calling party identification, allowing quick logon. For a direct external call, the Millennium does not provide trunk identification. The Octel 200/300 plays the company greeting specified at the port level.
Page 431: Chapter 9 Cortelco Millennium Adaptive Integration
Link Performance (Specification for the link) Note that the Millennium does not send calls to the Octel 200/300 ports if the data link is not in operation. Because of strapping requirements on the RS-232C IDEA PBA (printed board assembly), the Millennium cannot immediately detect that the integration data link has been disconnected.
Page 432 The Millennium verifies connection to the Octel 200/300 by sending an inquiry data packet. If the Octel 200/300 responds, calls are processed. If the Octel 200/300 does not respond, no calls are sent, and the Millennium polls the link periodically until a connection is established.
Page 433: Millennium Requirements
Millennium vendor must strap the IDEA board accordingly to provide a permanent DSR (Data Set Ready) signal on the data port configured for the Octel 200/300. Figure 9-2 is provided for reference. The PBX vendor should test the data registers to ensure that they all work properly. If any of these are not working, the data link could have problems initializing properly after restarts and power failures.
Page 434: Strapping Diagram For Rs-232C Idea Ii Pba
Extensions must be in a class of service that allows access to voice mail. They should also be allowed the various levels of forwarding available on the Millennium. Refer to the Octel 200/300 Configuration for Millennium Integration, COS attributes for Integrated Mailboxes section in this chapter for the class of service attributes required.
Page 435 VMPORT must be set to a sequential designation to allow the Millennium to hunt past a busy port. Note that these are not extension numbers for the ports; they are internal reference numbers for the PBX only. The sequence starts with the first line connected to the Octel 200/300, then the second, etc., as follows: Port 1...
Page 436 Message receive button MSGR (multibutton electronic sets only) — provides MWI: When MSGR is lit, there are new messages. Press MSGR for direct access to the Octel 200/300 with quick logon. If access is through this key, the LAMP OFF command is sent by the Octel 200/300, but the lamp goes out only when a call is released.
Page 437 FLASH TIME (MSEC) In the Octel 200/300, the value of System Parameter 9 is the actual length of the flash. In the Millennium , the flash time value sets the level at which a flash becomes a disconnect. For example, if the PBX is set for a flash time of 500 ms, then an on-hook condition of 500 ms or longer is seen as a disconnect, and anything less than 500 ms is seen as a flash.
Page 438 THE OCTEL 200/300 CONFIGURATION FOR MILLENNIUM INTEGRATION The Octel 200/300 configuration is divided into six categories: system parameters for the data link, system parameters for message waiting indication, COS attributes for integrated mailboxes, COS attributes for integrated ports, trunk groups, and after all changes have been made.
Page 439 After All Changes Have Been Made After configuration is complete, exit the UPDATE program, save to the configuration backup diskette, and restart the Octel 200/300. When the system is booted and running, test all integration, call processing, and messaging functions.
Page 440: Wiring Of Data Link
9-12 Integration Volume OCTEL 200/300 TO MILLENNIUM INSTALLATION The Octel 200/300 to Millennium installation is divided into two categories: data link cable connection and data cable pinouts. Data Link Cable Connection An eight-pin modular jack is wired to the Millennium MDF in accordance with Cortelco practice. The Millennium XXX-011 data cable consists of an eight-pin modular plug on one end and a DB-25 male connector on the other.
Page 441: Data Cable Configuration
Data Cable Pinouts The Millennium data cable pinouts are shown in Figure 9-4. The matching pinouts for the J2 on the Octel 200/300 are shown in Table 9-1. PBX (DTE) Octel 200/300 (DCE) 8-pin modular DB-25 (male) Brown Light Blue...
Page 442 24 = the “140” internal access with the company greeting (no mailbox) gg Port (Refer to Table 9-2 for a complete list of corresponding Octel 200/300 port numbers, Millennium VM port numbers, and packet port ID numbers.) 20 = port 1...
Page 443 (disconnected) or some other fault prevents transmission of call records. If a mailbox is not configured for an extension, the PBX sends a call record, but the Octel 200/300 does not answer the call. Table 9-2 Port Number and Packet Port ID Number Correspondence...
Page 444: Installation Checklist
Integration Volume INSTALLATION CHECKLIST This section offers a checklist of issues relating to the Octel 200/300 and the Millennium PBX. The list is presented in the order that the installation process should be followed. For details regarding any topic, refer to the sections of this chapter pertaining to the issue.
Page 445: Actual Installation
Verify the Millennium software level: Generic 6.1, version BAD4 or later software, or Generic 6.2 version AAD4 or later. Users who want to forward to the Octel 200/300 must know MSGS and MSGR codes and must have call forwarding on their phones.
Page 446: The Octel 200/300 Configuration Changes For Mwi
9-18 Integration Volume Table 9-7 The Octel 200/300 Configuration Changes for MWI Item Description Command Complete Modify System Parameter 3 — , to 01, the PBX PBX TYPE M SYS 3 type for the Millennium. Modify System Parameter 51 —...
Page 447: The Octel 200/300 Configuration Changes For Cpi
Cortelco Millennium Adaptive Integration 9-19 Table 9-8 The Octel 200/300 Configuration Changes for CPI Item Description Command Complete Modify System Parameter 3 — , to 01, the PBX .M SYS 3 PBX TYPE type for the Millennium. Modify System Parameter 51 —...
Page 449: Chapter 10.1 Mitel Sx-200 Digital Adaptive Integration
........... . 10.3A-1 PB60019-01 Octel 200/300 S.4.1...
Page 451 Adaptive Integration, including Message Waiting Indication and Called Party Identification, for Mitel SX-200 Digital, Mitel SX-100/SX-200 Analog, and Mitel SX-2000. When planning, configuring, installing and testing Mitel SX-200 Digital, Mitel SX-100/SX-200 Analog, or Mitel 2000 Adaptive Integration, be sure to use the correct section in this manual. PB60019-01 Octel 200/300 S.4.1...
Page 453: Chapter 10.1 Mitel Sx-200 Digital Adaptive Integration
10.1.5 Octel 200/300 System Configuration ............
Page 454: Test Equipment
10.1-4 Octel 200/300 Configuration Changes for MWI and CPI ........
Page 455 Octel 200/300. The Octel 200/300 can process the call and provide call coverage based on the type of call and desired coverage. In fact, any information that the Mitel SX-200 Digital provides to a Mitel Superset 4 telephone is available to the Octel 200/300.
Page 456 The Mitel SX-200 Digital does not provide the Octel 200/300 with the reason a call was forwarded, so the Octel 200/300 reports the status of all forwarded calls as “Extension XXX is unavailable. . .”...
Page 457 Direct Internal Calls A person can call the Octel 200/300 directly either to enter a mailbox, send a Quick Message, or make a network call. For these direct internal calls, the Mitel SX-200 Digital sends a display containing the...
Page 458 Octel 200/300 knows what caller left the message. When the person receiving the message listens to it, the Octel 200/300 is able to play the name of the caller who left the message before playing the message itself. The person receiving the message may automatically reply to the message or immediately call the sender.
Page 459: 10.1.2 Mitel Sx-200 Digital Requirements
Software, and Configuration. Hardware Requirements The Mitel SX-200 Digital hardware interface for the Octel 200/300 with Adaptive Integration requires Superset 4 telephone lines to interface to the MIC ports. MIC Port Extensions. The Mitel SX-200 Digital must provide a Superset 4 line for each MIC port in the Octel 200/300.
Page 460 Additional ports can be configured for MWI. Message waiting indication for a Superset 4 display telephone appears as a callback message. The Octel 200/300 cannot be called back from a Superset 4 because the MIC message waiting port cannot answer calls.
Page 461 10.1-7 The following information applies only to sub-attendant message waiting indication. The Octel 200/300 must call a phone to control its message waiting indicator. A phone may ring briefly while the Octel 200/300 turns its indicator ON or OFF. The Octel 200/300 cannot control a phone’s message waiting indicator while that phone is set for Do Not Disturb, or when that phone forwards on Busy-Forward or All-Forward.
Page 462 This is a requirement for each Superset 4 that will have full CPI functionality. When all Octel 200/300 ports are busy, a call can forward on ring-no-answer to busy tone. This is because these PBX software releases do not have a hunt group overflow or permit hunt group queuing for internal calls.
Page 463 Each trunk group that is to be identified by the Octel 200/300 must be configured with either no name or with a name that includes the string TXXX.
Page 464 Call coverage is set up at each phone only. This requires that each phone user set up their extension to forward to the Octel 200/300 so that the Octel 200/300 can provide secondary answering. If mailbox holders forward their phones to destinations other than the Octel 200/300, CPI may not work properly.
Page 465 Example. A customer service group has five lines in a hunt group, and each line appears on a phone. If agents in the group forward their phones to the Octel 200/300, their extensions are taken out of the hunt group, even if the forwarding is only on ring-no-answer.
Page 466: 10.1.4 Mitel Sx-200 Digital Configuration
This section describes the changes that must be made to the Mitel SX-200 Digital configuration so that the PBX can use the Octel 200/300 Adaptive Integration features. The configuration requirements may differ slightly for different Mitel software releases. The configuration instructions note any of these differences.
Page 467 In the SX-200 Digital, both analog Superset line cards and digital COV line cards may be available. Superset lines from the analog cards are recommended, but are not mandatory. The analog Superset line card sends display information more quickly, allowing the Octel 200/300 to process calls faster.
Page 468 MIC call processing ports, and not to any other extensions. Assign the options according to the Option Names given below; the Option Numbers for some options differ among the various Generics. The option numbers given below are for Generic 1003. Some of these options are not available on earlier Generics. Octel 200/300 S.4.1 PB60019-01...
Page 469 TEN — The tenant number should be the same as the tenant number for all extensions using the Octel 200/300. If multiple tenants will be calling the Octel 200/300, use a tenant number to which each of the tenants has access. Tenant interconnections are configured in CDE form 05, TENANT INTERCONNECTION Table.
Page 470 10.1-16 Integration Volume EXTN — Assign any available extension numbers. Make a note of the extension numbers; they will be needed for defining the MIC port hunt group, SLOTS Table in the Octel 200/300, and also for the Installation and Testing procedures.
Page 471 Octel 200/300. 2. Note the trunk number so that this number may be entered in the Octel 200/300 TRUNK GROUP Table. For Generic 1003 only, the trunk Name entry must be left blank.
Page 472 10.1-18 Integration Volume Stations that are to have message waiting indicators controlled by the Octel 200/300 must be connected to line cards in the Mitel SX-200 Digital that support message waiting lamps. For Generic 1003 only, stations that have been assigned a name in CDE form 09, STATION/SUPERSET TELEPHONES, must have the station extension number included in the name according to the format described in Naming Conventions at the beginning of this section.
Page 473 The TRUNK GROUP Table enables the Octel 200/300 to process the call according to which trunk group the call came in on instead of which port the Octel 200/300 answered the call on. This means integrated ports do not need to be split. Examples of how this can be applied include the following: A different company greeting may be recorded for each trunk group.
Page 474 COS Attribute 58 — DO NOT USE THIS PORT FOR INTEGRATION If there are any line cards in the Octel 200/300 that are not MICs, or if some special application requires that a MIC port operate in a non-integrated mode, use this COS attribute to distinguish these ports from the integrated MIC ports.
Page 475 System Parameter 81 — LAMP MW: “OFF” PRE-EXTENSION DIGITS If the Octel 200/300 is using COV Voice Mail port message waiting indication, modify both System Parameter 79 and System Parameter 81 to be 00. These parameter values tell the integration software to perform message waiting indication using the COV Voice Mail feature instead of the sub-attendant feature.
Page 476 Generic 1003, release E96.7 or later is used because of the COS option, COV Voice Mail Port. The Octel 200/300 identifies calls from the attendant as coming from Trunk Group 00, since a call from the attendant cannot be identified by extension number.
Page 477 Octel 200/300. These tests verify that Mitel Adaptive Integration works properly with the PBX. Some of the tests are made before the Octel 200/300 is connected to the PBX. Always check the PBX for proper operation after any changes are made to the system. The following items are required for testing: Table 10.1-1 Test Equipment...
Page 478 4. Allocate one trunk line into the PBX that can be individually called. This will be used to test external calls into the Octel 200/300. Configure this trunk to ring directly into the first port of the MIC port hunt group. During the testing, the trunk is reconfigured to ring directly into one of the analog test extensions.
Page 479: Diagram Of The Superset 4 Telephone
Prime hold Line key 3:08 9-JAN-95 PROGRAM display select features Softkeys (numbered speaker on/off 1 to 6, starting from the left) mic. on/off Figure 10.1-1 Diagram of the Superset 4 Telephone PB60019-01 Octel 200/300 S.4.1...
Page 480 EXT-B and EXT-A, respectively. b. Connect a Superset 4 to the extension assigned to the first MIC port of the Octel 200/300 used for answering calls. Do not use the MIC extension that is used for Message Waiting Indication.
Page 481 Determine the cause and correct the problem before continuing. Hang up phone A and the Superset 4. Connect the Superset 4 to the next Octel 200/300 MIC port extension and repeat steps d. through h. until every MIC port extension has been tested.
Page 482 4. PBX BUSY FORWARD TEST AND SUPERSET DISPLAY TEST This test verifies that an extension can forward to the Octel 200/300 on a busy condition and verifies that the Superset 4 display contains the correct information for a forwarded call.
Page 483 6. PBX FORWARD ALL CALLS TEST This test verifies that an extension can forward all calls to the Octel 200/300 access number. Set phone B to forward all calls to the Superset 4 by entering the feature access code for Call Forwarding −...
Page 484 Press the selected feature button on the Superset 4. The display should read as follows: DIAL FEATURE NO. Determine the cause and correct the problem before continuing. Press on the keypad. Does the display clear? Determine the cause and correct the problem before continuing. Octel 200/300 S.4.1 PB60019-01...
Page 485 Hang up phone A. 8. CALLS TO THE INTERCEPT EXTENSION (ATTENDANT) (For new installation only) This test verifies that each Octel 200/300 port extension can transfer a call to the intercept extension (attendant). Connect the Superset 4 phone to the PBX extension used for the first MIC port.
Page 486 All cross-connections to the PBX must be completed before proceeding. Changes to connections should only be made while the integration card is not installed in the Octel 200/300. Cross connecting Caution! integration links when the integration card is installed may result in damage to the integration card.
Page 487 1. ALL ACTIVITIES. and C for continuous display. b. From phone A, call the extension of the Octel 200/300 port 1. Does the Octel 200/300 answer with “To enter your mailbox, press pound”? Correct the problem before continuing.
Page 488 This test verifies that the Octel 200/300 processes a direct internal call correctly. From phone A, call the extension number for the Octel 200/300 access, that is, the access number of the MIC ports’ hunt group. Does the Octel 200/300 answer with, “To enter your mailbox press pound.
Page 489 Put the Octel 200/300 ports in FWD state by entering at the @ prompt TE C 1 b. Using phone A, call the extension of the Octel 200/300 hunt group. Be sure that you reach the position specified for overflow in the Octel 200/300 hunt group. If not, correct the problem before continuing.
Page 490 TE C 1 x where x is the port number. d. Repeat steps a. through c. for each Octel 200/300 port until all the ports are busied out. This is to confirm that each Octel 200/300 port can answer a trunk call.
Page 491 Determine the cause and correct the problem before continuing. From phone A, call out and back in on a trunk that auto-terminates to the Octel 200/300. When the Octel 200/300 answers, let the system time out; do not enter any digits.
Page 492 Call Forwarding − Busy followed by the Octel 200/300 access number. After setting forwarding for phone B, leave phone B off-hook so that it appears busy. b. From phone A, call out and back in on a trunk that auto-terminates to the Octel 200/300. Does the Octel 200/300 answer properly? Determine the cause and correct the problem before continuing.
Page 493 Octel 200/300 call the extension associated with phone B? Determine the cause and correct the problem before continuing. g. From phone B, call the Octel 200/300 and enter the mailbox number of mailbox B. The Octel 200/300 should respond with “ EXT-B has one message. Ready. . .”...
Page 494 LINK 4 = 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 CLEAR INTEGRATION This command clears the MIC pegs. The form of the command is C INT x 1 C INT x 1 where x is the slot number. Octel 200/300 S.4.1 PB60019-01...
Page 495 The MIC is operational. CARD UP Diagnostic The MIC firmware reports the diagnostic code to the Octel 200/300 CPU. If there are no errors, the DIAGNOSTIC = OK. If an error is found, the DIAGNOSTIC = ERROR DETECTED, CODE = XX.
Page 496 LIST INTEGRATION command. PEG NAME DESCRIPTION REPLY ERROR Number of times the MIC timed out waiting for the Octel 200/300 to pro- cess a reply. REQUEST ERROR Number of times the MIC firmware received an invalid request.
Page 497 INT ERROR Miscellaneous firmware error has occurred. For information on hardware errors regarding integrated systems, refer to the Installation and Maintenance volume, System Errors and Traffic Pegs chapter, for more information. PB60019-01 Octel 200/300 S.4.1...
Page 498 10.1-44 Integration Volume 10.1.8 INSTALLATION CHECKLIST This section offers a checklist of issues relating to the Octel 200/300 and the Mitel SX-200 Digital. The list is presented in the order that the installation process should be followed. For details regarding any topic, refer to the sections in this chapter pertaining to the issue.
Page 499: Octel 200/300 Configuration Changes For Mwi And Cpi
Mitel SX-200 Digital Adaptive Integration 10.1-45 Actual Installation Table 10.1-4 Octel 200/300 Configuration Changes for MWI and CPI Item Description Command Complete Assign COS Attribute 9 only to mailboxes that will use MWI to acti- .A COS vate message waiting lamps.
Page 500: After All Changes Have Been Made For Mwi And Cpi
Description Complete Configure the required test extensions. Perform pre-installation testing. Install the MIC boards in the Octel 200/300 and connect the cables. Perform Adaptive Integration operational tests. Table 10.1-7 Test Equipment Quantity Description 2500-type, single line touchtone phones, one with a message waiting indicator.
Page 501: Chapter 10.2 Mitel Sx-100/Sx-200 Analog Adaptive Integration
10.2.5 Octel 200/300 Configuration ............. .
Page 502: Test Equipment
10.2-4 Octel 200/300 Configuration Changes for MWI and CPI ........
Page 503 Octel 200/300. The Octel 200/300 can process the call and provide call coverage based on the type of call and desired coverage. In fact, any information that the Mitel SX-100/SX-200 Analog provides to a Mitel Superset 4 telephone is available to the Octel 200/300.
Page 504 10.2-2 Integration Volume waiting indicator is ON will not know whether the lamp is for the Octel 200/300 message waiting indication or for another message waiting condition and will have to check for the source of the message. Called Party Identification. Called party identification allows the Octel 200/300 to identify the source (extension or external trunk number) of direct calls and the source and the original called extension of forwarded calls.
Page 505 Direct Internal Calls A person can call the Octel 200/300 directly either to enter a mailbox, send a Quick Message, or make a network call. For these direct internal calls, the Mitel SX-100/SX-200 Analog sends a display containing...
Page 506 Octel 200/300 knows what caller left the message. When the person receiving the message listens to it, the Octel 200/300 is able to play the name of the caller who left the message before playing the message itself. The person receiving the message may automatically reply to the message or immediately call the sender.
Page 507: 10.2.2 Mitel Sx-100/Sx-200 Analog Requirements
Software, and Configuration. Hardware Requirements The Mitel SX-100/SX-200 Analog hardware interface for the Octel 200/300 with Adaptive Integration requires Superset 4 telephone lines to interface to the MIC ports. MIC Port Extensions. The Mitel SX-100/SX-200 Analog must provide a Superset 4 line for each MIC port in the Octel 200/300.
Page 508 Additional ports can be configured for MWI. Message waiting indication for a Superset 4 display telephone appears as a callback message. The Octel 200/300 cannot be called back from a Superset 4 because the MIC message waiting port cannot answer calls.
Page 509: Chapter 10.2 Mitel Sx-100/Sx-200 Analog Adaptive Integration
This requires an additional port in the PBX. When all Octel 200/300 ports are busy, a call can forward on ring-no-answer or busy tone. This is because the Mitel SX-100/SX-200 Analog does not have a hunt group overflow or permit hunt group queuing for internal calls.
Page 510 Example. A customer service group has five lines in a hunt group, and each line appears on a phone. If agents in the group forward their phones to the Octel 200/300, their extensions are taken out of the hunt group, even if the forwarding is only on ring-no-answer.
Page 511: 10.2.4 Mitel Sx-100/Sx-200 Analog Configuration
This section describes the changes that must be made to the Mitel SX-100/SX-200 Analog configuration so that the PBX can use the Octel 200/300 Adaptive Integration features. The configuration requirements may differ slightly for different Mitel software releases. The configuration instructions note any of these differences.
Page 512 The Call Forwarding Don’t Answer Time-Out (System Option 255, 256, or 257), must be set longer than the length of time corresponding to the Octel 200/300 system INFORMATION Table Index 7 — RINGS BEFORE NO ANSWER. This ensures that the Octel 200/300 system can still perform screened transfers to a ringing extension that has been forwarded on ring-no-answer.
Page 513 MIC call processing ports, and not to any other extensions. Using the console in program mode, assign the COS options listed below. Also assign any options the Octel 200/300 requires for use of external trunks, such a Trunk Group Access options or ARS options.
Page 514 1. Set the answer points for DAY, NIGHT 1, and NIGHT 2 service to the MIC port hunt group number according to when the trunk is to be answered by the Octel 200/300. 2. Note the trunk number so that this number may be entered in the Octel 200/300 TRUNK GROUP Table.
Page 515 The TRUNK GROUP Table enables the Octel 200/300 to process the call according to which trunk group the call came in on instead of which port the Octel 200/300 answered the call on. This means integrated ports do not need to be split. Examples of how this can be applied include the following: A different company greeting may be recorded for each trunk group.
Page 516 COS Attribute 58 — DO NOT USE THIS PORT FOR INTEGRATION If there are any line cards in the Octel 200/300 that are not MICs, or if some special application requires that a MIC port operate in a non-integrated mode, use this COS attribute to distinguish these ports from the integrated MIC ports.
Page 517 Superset 4 telephones cannot use DTMF feature access codes to set and cancel forwarding, so set System Parameters 45 and 46 to NONE. This causes the Octel 200/300 to take a port off-hook when the port is forwarded, removing the port from the hunt group. When forwarding is cancelled, the Octel 200/300 puts the port back on-hook so that it can answer calls.
Page 518 The Octel 200/300 identifies calls from the attendant as coming from Trunk Group 00, since a call from the attendant cannot be identified by extension number. Refer to Direct Internal Calls in this section.
Page 519 Octel 200/300. These tests verify that Mitel Adaptive Integration works properly with the PBX. Some of the tests are made before the Octel 200/300 is connected to the PBX. Always check the PBX for proper operation after any changes are made to the system. The following items are required for testing: Table 10.2-1 Test Equipment...
Page 520 4. Allocate one trunk line into the PBX that can be individually called. This will be used to test external calls into the Octel 200/300. Configure this trunk to ring directly into the first port of the MIC port hunt group. During the testing, the trunk is reconfigured to ring directly into one of the analog test extensions.
Page 521: Diagram Of The Superset 4 Telephone
Prime hold Line key 3:08 9-JAN-95 PROGRAM display select features Softkeys (numbered speaker on/off 1 to 6, starting from the left) mic. on/off Figure 10.2-1 Diagram of the Superset 4 Telephone PB60019-01 Octel 200/300 S.4.1...
Page 522 EXT-B and EXT-A, respectively. b. Connect a Superset 4 to the extension assigned to the first MIC port of the Octel 200/300 used for answering calls. Do not use the MIC extension that is used for message waiting indication.
Page 523 Determine the cause and correct the problem before continuing. Hang up phone A and the Superset 4. Connect the Superset 4 to the next Octel 200/300 MIC port extension and repeat steps d. through h. until every MIC port extension has been tested.
Page 524 4. PBX BUSY FORWARD TEST AND SUPERSET DISPLAY TEST This test verifies that an extension can forward to the Octel 200/300 on a busy condition and verifies that the Superset 4 display contains the correct information for a forwarded call.
Page 525 Hang up phone A. 5. PBX RING-NO-ANSWER FORWARD TEST This test verifies that an extension can forward to the Octel 200/300 on a ring-no-answer condition. Set phone B to forward to the Superset 4 on a ring-no-answer condition by entering the feature access code for Call Forwarding −...
Page 526 6. PBX FORWARD ALL CALLS TEST This test verifies that an extension can forward all calls to the Octel 200/300 access number. Set phone B to forward all calls to the Superset 4 by entering the feature access code for Call Forwarding −...
Page 527 10.2-25 8. CALLS TO THE INTERCEPT EXTENSION (ATTENDANT) (For new installation only) This test verifies that each Octel 200/300 port extension can transfer a call to the intercept extension (attendant). Connect the Superset 4 phone to the PBX extension used for the first MIC port.
Page 528 Repeat this step for unit 2. 7. Test the system for proper operation. Once the down LED is OFF, the good LED is ON (green), and the yellow LEDs are ON, the card and links are working properly. Octel 200/300 S.4.1 PB60019-01...
Page 529 1. ALL ACTIVITIES. and C for continuous display. b. From phone A, call the extension of the Octel 200/300 port 1. Does the Octel 200/300 answer with “To enter your mailbox, press pound”? Correct the problem before continuing.
Page 530 This test verifies that the Octel 200/300 correctly processes a call forwarded from a busy extension. Set phone B to forward to the Octel 200/300 on a busy condition by entering the feature access code for Call Forwarding − Busy followed by the Octel 200/300 access number. After setting forwarding for phone B, leave phone B off-hook so that it appears busy.
Page 531 TE C 1 x where x is the port number. d. Repeat steps a. through c. for each Octel 200/300 port until all the ports are busied out. This is to confirm that each Octel 200/300 port can answer a trunk call.
Page 532 Determine the cause and correct the problem before continuing. From phone A, call out and back in on a trunk that auto-terminates to the Octel 200/300. When the Octel 200/300 answers, let the system time out; do not enter any digits.
Page 533 This test verifies correct operation of message waiting indication. Set phone B to forward to the Octel 200/300 on a busy condition by entering the feature access code for Call Forwarding - Busy followed by the Octel 200/300 access number. After setting forwarding for phone B, leave phone B off-hook so that it appears busy.
Page 534 This test verifies correct operation of message waiting notification for systems not using Message Waiting Indication. Set phone B to forward to the Octel 200/300 on a busy condition by entering the feature access code for Call Forwarding − Busy followed by the Octel 200/300 access number. After setting forwarding for phone B, leave phone B off-hook so that it appears busy.
Page 535 11. FORWARDED INTERNAL CALL FROM AN EXTENSION THAT DOES NOT HAVE THE EXTENSION NUMBER IN THE NAME FIELD This test verifies that the Octel 200/300 correctly processes a call to an extension number in the name field. With the Superset 4 on-hook, press the PROGRAM softkey, followed by the NAME softkey. The...
Page 536 LINK 4 = 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 CLEAR INTEGRATION This command clears the MIC pegs. The form of the command is C INT x 1 C INT x 1 where x is the slot number. Octel 200/300 S.4.1 PB60019-01...
Page 537 The MIC is operational. CARD UP Diagnostic The MIC firmware reports the diagnostic code to the Octel 200/300 CPU. If there are no errors, the DIAGNOSTIC = OK. If an error is found, the DIAGNOSTIC = ERROR DETECTED, CODE = XX.
Page 538 LIST INTEGRATION command. PEG NAME DESCRIPTION REPLY ERROR Number of times the MIC timed out waiting for the Octel 200/300 to pro- cess a reply. REQUEST ERROR Number of times the MIC firmware received an invalid request.
Page 539 Maintenance volume, System Errors and Traffic Pegs chapter, for more information. This section offers a checklist of issues relating to the Octel 200/300 and the Mitel SX-100/SX-200 Analog. The list is presented in the order that the installation process should be followed. For details regarding any topic, refer to the sections in this chapter pertaining to the issue.
Page 540 Configure the MIC Superset extension used for MWI. Configure the MIC Superset extensions used for CPI. Configure trunks that will be answered by the Octel 200/300. Configure individual station extensions for Adaptive Integration. Make sure individual station extensions are forwarded to the Octel 200/300 hunt group for call coverage.
Page 541 Mitel SX-100/SX-200 Analog Adaptive Integration 10.2-39 Actual Installation Table 10.2-4 Octel 200/300 Configuration Changes for MWI and CPI Item Description Command Complete Assign COS Attribute 9 only to mailboxes that will use MWI .A COS to activate message waiting lamps.
Page 542: After All Changes Have Been Made For Mwi And Cpi
Description Complete Configure the required test extensions. Perform pre-installation testing. Install the MIC boards in the Octel 200/300 and connect the cables. Perform Adaptive Integration operational tests. Table 10.2-7 Test Equipment Quantity Description 2500-type, single line touchtone phones, one with a message waiting indicator.
Page 543: Chapter 10.3 Mitel Sx-2000 S & Sx-2000 Sg Adaptive Integration
10.3-48 Octel 200/300 Configuration Changes ..........
Page 544: Test Equipment
10.3-4 Octel 200/300 Configuration Changes for MWI and CPI ........
Page 545 Octel 200/300 — Called Party Identification (CPI). The Octel 200/300 can process the call and provide call coverage based upon the type of call and desired coverage. In fact, any information that the Mitel SX-2000 provides to a Mitel Superset 4 telephone is available to the Octel 200/300.
Page 546 MWI on a single dedicated port. At any SX-2000 software level, the Octel 200/300 can perform MWI using a single dedicated Octel 200/300 port. This port must be isolated so that it does not receive calls. The port need not be an MIC port. This configuration does not require Adaptive Integration.
Page 547 A Call Rerouting Always Alternative specifies as an alternate answer point that all calls are to be rerouted. Rerouting can be enabled or disabled for different types of call sources (DID trunk, TIE trunk, CO trunk, or internal). Octel 200/300 S.4.1 PB60019-01...
Page 548 Reroute internal calls and TIE trunk calls to coverage if station is RNA. Reroute CO and DID trunk calls to coverage if station is busy or RNA. Reroute all CO and DID trunk calls to the Octel 200/300 during Night 1 service, and all calls to the attendant during Night 2 service.
Page 549: Call Rerouting First Alternative Assignment Example
TIE trunk calls are rerouted to the message server only if the station is unanswered, while CO and DID trunk calls are rerouted to the Octel 200/300 if the station is either Busy/DND or unanswered. In either case, the number of rings for “Unanswered” is defined by the Call Forward No Answer Timer in the station’s PBX COS.
Page 550: Call Rerouting Assignment Example Entries
Forward All Calls “(name) is unavailable” * If System Parameter 115 is set to Y, the Octel 200/300 uses “(name) is on the phone” instead of “(name) is busy.” Refer to the Feature Description volume —Customizing Mailbox Features, Recording Names for Mailboxes, for further details.
Page 551 TRUNK XXX is the trunk number that the Octel 200/300 uses to identify trunks. If the MIC Superset ports do not have the COS option COV Voice Mail port enabled, and the trunk has a Trunk Service Label, this label will appear in the display instead of TRUNK XXX.
Page 552 Direct Internal Calls A person can call the Octel 200/300 directly either to enter a mailbox, send a Quick Message, or make a network call. For these direct internal calls, the Mitel SX-2000 sends a display containing the following information: XXX is the extension number of the calling party.
Page 553 Octel 200/300 knows which caller left the message. When the person receiving the message listens to it, the Octel 200/300 is able to play the name of the caller who left the message before playing the message itself. The person receiving the message may automatically reply to it or immediately call the sender (IntraMessaging feature).
Page 554 Configuration Requirements The Mitel SX-2000 configuration must have one unassigned COS available for use with Adaptive Integration’s CPI feature. An additional unassigned COS is required if the Octel 200/300 is using DTMF feature access codes to control message waiting indicators.
Page 555 PBX Functional Limitations that Affect Message Waiting Indicator Control The following are limitations that affect the Octel 200/300’s use of DTMF feature access codes to control message waiting indicators. SX-2000 attendants and other stations can control message waiting indicators. This may interfere with proper operation of message waiting indicator control.
Page 556 The COV Voice Mail Port class of service option should not be used for the Octel 200/300 ports in a multinode SX-2000 installation unless the SX-2000 PBX has software level H10.15 or later.
Page 557 This section describes the changes that must be made to the Mitel SX-2000 configuration so that the PBX can utilize the Octel 200/300’s Adaptive Integration features. The configuration requirements may differ slightly for different Mitel software releases. The configuration instructions note any of these differences.
Page 558 Trunk names, if assigned, must follow the guidelines below unless the MIC ports are assigned the COV Voice Mail Port class of service option. The Octel 200/300 always identifies forwarded external calls by individual trunk number. Therefore, if the Octel 200/300 is to process forwarded calls according to their trunks, the individual trunk numbers must be included in Octel 200/300 TRUNK GROUP Table.
Page 559 30 seconds No Answer Recall Timer 30 seconds Ringing Timer 180 seconds Set the following COS options according to the requirements of the particular the Octel 200/300 installation. COS Option. Public Network to Public Network Connection Allowed Non-verified Account Code...
Page 560 Configuration for Message Waiting Indication Ports If the PBX class of service option COV Voice Mail Port is available, any Octel 200/300 outcall port can perform MWI. If the COV Voice Mail Port Option is not available, SX-2000 ports must be dedicated for MWI.
Page 561 Trunks and Trunk Groups Trunks that are to be answered by the Octel 200/300 must be configured to terminate at the MIC hunt group. If the Octel 200/300 is to identify a group of incoming trunks for special applications, trunks in that group must be assigned the same trunk service number.
Page 562 Integration Volume Call Rerouting All extensions that are to use the Octel 200/300 for call coverage must be assigned a Call Rerouting table entry that includes the Octel 200/300 as an answer point. This may require addition of new Call Rerouting table entries as well as modification of existing Call Rerouting table entries.
Page 563 Rings Before No Answer and Message Waiting Rings. Configuration for Message Waiting Indication To ensure that the Octel 200/300 can control message waiting indicators on single line stations, be sure that those stations with lamps are assigned an appropriate ONS/OPS Circuit Descriptor number. Stations without indicators, as well as those with indicators, can receive message waiting notification by a special message waiting tone after going off-hook.
Page 564 The Mitel PBX provides the Octel 200/300 with the trunk number of an external call. The TRUNK GROUP Table enables the Octel 200/300 to process the call according to the trunk on which the call came in instead of the port on which the Octel 200/300 answered the call. Integrated ports, therefore, do not need to be split.
Page 565 COS Attribute 58 — DO NOT USE THIS PORT FOR INTEGRATION If there are any line cards in the Octel 200/300 that are not MICs, or if some special application requires that a MIC port operate in a non-integrated mode, use this COS attribute to distinguish these ports from the integrated MIC ports.
Page 566 Modify the value of System Parameter 85 to be F. System Parameter 106 — PORT FOR LAMP MESSAGE WAITING If a single Octel 200/300 port is to be dedicated for MWI, enter the port number in System Parameter 106. Otherwise, modify System Parameter 106 to 0.
Page 567 Octel 200/300 ports so that any port can control message waiting indicators. If this class of service option is not available or cannot be used, one or more Octel 200/300 ports must be dedicated for message waiting control and cannot answer calls.
Page 568 System Parameter 80 — LAMP MW: “ON” POST-EXTENSION DIGITS Use the character E, expect dial tone, to ensure that the Octel 200/300 checks for dial tone after attempting to activate a message waiting indicator. If the PBX does not provide dial tone, the message waiting activation was not successful.
Page 569 Octel 200/300. These tests verify that Mitel Adaptive Integration works properly with the PBX. Some of the tests are made before the Octel 200/300 is connected to the PBX. Always check the PBX for proper operation after any changes are made to the system.
Page 570 Set up a Call Rerouting Always Alternative that reroutes to the first MIC port in the Octel 200/300 hunt group for all types of calling devices, but do not assign this Always Alternative to either analog extension yet. Instead, assign an Always Alternative number that results in No Reroute for Day, Night 1, and Night 2 operation.
Page 571: Diagram Of The Superset 4 Telephone
Volume controls for speaker and ringer Prime Line hold 3:08 9-JAN-95 PROGRAM display select features Softkeys (numbered speaker on/off 1 to 6, starting from the left) mic. on/off Figure 10.3-5 Diagram of the Superset 4 Telephone Octel 200/300 S.4.1 PB60019-01...
Page 572 This test verifies that dial tone is present on each of the Superset extensions used for the MIC links. Disconnect the 25-pair cables from the back of the Octel 200/300. b. Connect the modular adapter to the 25-pair cable associated with slot 1.
Page 573 Label the single line telephone with a message waiting indicator as phone B. Label the other single line telephone as phone A. b. Connect a Superset 4 to the 25-pair cable assigned to the first MIC port of the Octel 200/300 hunt group.
Page 574 5. PBX FORWARD ALL CALLS TEST This test verifies that an extension can forward all calls to the Octel 200/300 access number. Set phone B to forward all calls to the Superset 4 by assigning to phone B’s extension the Call Rerouting Always Alternative that reroutes to the first MIC port in Day, Night 1, and Night 2 operation.
Page 575 After the duration specified by the phone B’s Call Forward No Answer timer, does the call forward to the Superset 4? Correct the problem before continuing. d. Look at the display of the Superset 4. The display should contain this information: CFNA: XXX is the extension of phone B. Octel 200/300 S.4.1 PB60019-01...
Page 576 TXXX XXX is the trunk number. If the display does not contain this information, determine the cause and correct the problem before continuing. n. Press the EXIT softkey on the Superset 4. Hang up phone A. Octel 200/300 S.4.1 PB60019-01...
Page 577 Determine the cause and correct the problem before continuing. Look at the Superset 4 display. The display should contain this information: CFB: XXX is the extension of phone B. Determine the cause and correct the problem before continuing. Octel 200/300 S.4.1 PB60019-01...
Page 578 10. DISPLAY TEST FOR CALLS FORWARDED ON ALWAYS REROUTE This test verifies that the MIC ports receive the proper display information from the PBX for calls that always reroute to the Octel 200/300. Internal Call Forwarded on Always Reroute Access the SX-2000 Call Rerouting Assignment form and assign to phone B the Call rerouting Always Alternative that reroutes all calls to the first MIC port.
Page 579 Always Alternative back to No Reroute for all types of calling devices. 11. CALLS TO THE INTERCEPT EXTENSION (ATTENDANT) (For new installation only) This test verifies that each Octel 200/300 port extension can transfer a call to the intercept extension (attendant).
Page 580 This section describes the procedure for installing the MIC board. Reconnect the 25-pair cable to the Octel 200/300. Before proceeding with installation, note that there are six LEDs on the front edge of the MIC, near the top of the card. These are used to indicate card status and are, from top to bottom,...
Page 581 On the Octel 200/300 terminal, enter and select 1. ALL ACTIVITIES. b. From phone A, call the extension of the Octel 200/300 port 1. Does the Octel 200/300 answer with “To enter your mailbox, press pound”? Correct the problem before continuing.
Page 582 This test verifies that the Octel 200/300 processes a direct internal call correctly. From phone A, call the extension number for the Octel 200/300 access, that is, the access number of the MIC ports’ hunt group. Does the Octel 200/300 answer with, “To enter your mailbox press pound.
Page 583 TE C 1 x where x is the port number. d. Repeat steps a. through c. for each Octel 200/300 port until all of the ports are busied out. This is to confirm that each Octel 200/300 port can answer a trunk call.
Page 584 200/300. Does the Octel 200/300 answer with the greeting configured for the trunk? Determine the cause and correct the problem before continuing. Call the extension of phone B. Does the Octel 200/300 respond with, “Thank you, just a moment. . .” after which phone B starts ringing? Determine the cause and correct the problem before continuing.
Page 585 While still connected to the Octel 200/300, enter the mailbox number of mailbox B. Note that this should be the same as the extension number of phone B. Does the Octel 200/300 respond with the prompt, “Thank you. Just a moment. . . ?”...
Page 586 Determine the cause and correct the problem before continuing. From phone A, call out and back in on a trunk that auto-terminates to the Octel 200/300. When the Octel 200/300 answers, let the system time out; do not enter any digits.
Page 587 SX-2000 feature access codes to control message waiting indicators. Set phone B to forward to the Octel 200/300 on a busy condition by entering the feature access code for Call Forwarding - Busy followed by the Octel 200/300 access number. After setting forwarding for phone B, leave phone B off-hook so that it appears busy.
Page 588 EXTENSION NUMBER IN THE NAME FIELD This test verifies that the Octel 200/300 correctly processes a call to an extension that does not have the extension number in the name field. Perform this test only for SX-2000 PBXs that do not have the COV Voice Mail Port class of service option.
Page 589 LINK 4 = 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 CLEAR INTEGRATION This command clears the MIC board pegs. The form of the command is C INT x 1 C INT x 1 where x is the slot number. Octel 200/300 S.4.1 PB60019-01...
Page 590 The MIC is operational. CARD UP Diagnostic The MIC firmware reports the diagnostic code to the Octel 200/300 CPU. If there are no errors, the DIAGNOSTIC = OK. If an error is found, the DIAGNOSTIC = ERROR DETECTED, CODE = XX.
Page 591 Number of times the MIC link’s call processing routine saw an unexpected VCU control event. GLARE COUNT Number of times that the Octel 200/300 went off-hook on this port to make an outcall and the MIC firmware saw a call come in at the same time.
Page 592 Integration Volume 10.3.8 INSTALLATION CHECKLIST This section offers a checklist of issues relating to the Octel 200/300 and the Mitel SX-2000. The list is presented in the order that the installation process should be followed. For details regarding any topic, refer to the sections in this chapter pertaining to the issue.
Page 593 Mitel SX-2000 Adaptive Integration 10.3-49 Octel 200/300 Configuration Changes Table 10.3-4 Octel 200/300 Configuration Changes for MWI and CPI Item Description Command Complete Assign COS Attribute 9 only to mailboxes that will use MWI .A COS to activate message waiting lamps or message waiting dial tone.
Page 594: Installation And Testing
Restart the system. Table 10.3-6 Installation and Testing Item Description Complete Configure the required test extensions. Perform pre-installation testing. Install the MIC boards in the Octel 200/300 and connect the Superset lines. Perform Adaptive Integration operational tests. Octel 200/300 S.4.1 PB60019-01...
Page 595 Table 10.3-7 Test Equipment Quantity Description 2500-type, single line touchtone phones, one with a message waiting indicator. Terminal/teleprinter directly connected to Octel 200/300 PORT A via RS-232C cable. Hard copy of the Octel 200/300 configuration database. Hard copy of the PBX configuration.
Page 597 10.3A-1 Appendix A Mitel SX2000 Integration (DPNSS)* With DPNSS, one digital pathway between the PBX and the Octel 200/300 transmits both call information and voice communications Method of Integration With DPNSS integration, one digital pathway between the Octel 200/300 and the PBX transmits both call information and voice communications.
Page 598 10.3A-2 Integration Volume Requirements Octel 200/300 S3.0 (or higher) Software Requirements COD DSP ports Software Features Packages X0031 (Adaptive Integration) Octel 200/300 DTIC−E1 (1 per 30 ports ) Hardware Requirements Earthing Bracket Amphenol to BNC converter (1 per DTIC−E1 card)
Page 599 (A/B) Integrated Digital Access DPNSS Link Descriptor Assignment Form (Digital Link Forms) Digital Link Assignment Cabinet Shelf Slot Link Card Digital Text Descrip- Type Link Number CEPT For- matter Digital Link Assignment Form (Digital Link Form) PB60019-01 Octel 200/300 S.4.1...
Page 600 Leading Digits: 3000 (Pilot Number for Message Server) Selection Assignment Second Dial Tone (Yes/No/Alternate): COR Group Number: Digits Number of Termination Number Dialed Digits to Type Follow Route Automatic Route Selection Assignment Form (Automatic Route Selection Forms) Octel 200/300 S.4.1 PB60019-01...
Page 601 Shelf Slot Hybrid Slip Rate −5 First Clock Source Second Clock Source Third Clock Source Fourth Clock Source Fifth Clock Source Sixth Clock Source Seventh Clock Source Eighth Clock Source Network Synchronization Form (Digital Link Forms) PB60019-01 Octel 200/300 S.4.1...
Page 602 10.3A-6 Integration Volume Configuring the Octel 200/300 This section shows how to configure the Octel 200/300 system tables for Mitel SX2000 DPNSS Integration. For questions about the Mitel switch, refer to the Mitel documentation, Configuring the Mitel SX2000 Light to Integrate section, Link Descriptor Assignment.
Page 603 Parameter DPNSS: Voice Mail Destination Address = Set value to be at least 3 digits long. Note: The Octel 200/300 ID number (System Parameter 313) MUST be the same as the Mitel PBX ARS number used to access the Octel 200/300.
Page 604 If that setting is “Outgoing” set the parameter to Y Example: n,254,AX,Y,N,X Slot Card Type This is an example of how a list of the Slot Table appears. LSP table: DPN_MITA PRIMARY SYNC RECEIVER OF CLOCK Port Extension Mode Outcall DTC17− Number Test DPNSS Octel 200/300 S.4.1 PB60019-01...
Page 605 Application Delay Table The Application Delay Table contains the timing values the Octel 200/300 uses. The Applications Delay Table for Mitel should be correct if the PBX type “Mitel SX2000” is selected in System Parameter 3, with the exception that the following delays must be changed.
Page 606 Translation Table If the Mitel DPNSS switch is part of a larger switch network and the call records sent to the Octel 200/300 reflect a Node ID as well as the actual extension numbers, the Node ID must be stripped off by using the Translation Table. This is an example...
Page 607 The DTIC card can be installed in any of the slots that would normally house an analogue or FAX card, (i.e. slots 1−6 on an Octel 200, slots 1−11 on an Octel 300). As with all other line cards the DTIC card can be hot plugged.
Page 608 6. Leave a message. Verify that the message waiting indicator turns on. 7. Verify that transfer to attendant works properly. 8. Call the Octel 200/300 from a test extension. Log onto the mailbox. 9. Review the message in the mailbox.
Page 609 If this routine is used, set System Parameter 191 to specify the hour that the message server should reactivate indicators. The Octel 200/300 ID number (System Parameter 306 and 313) MUST be the same as the Mitel PBX ARS number used to access the Octel server.
Page 611 11-7 Octel 200/300 Port Extensions ............
Page 612: Test Equipment
11-7 Octel 200/300 Configuration Changes to MWI ..........
Page 613: Chapter 11 Meridian 1 Adaptive Integration
Meridian 1 (M1) Adaptive Integration that includes message waiting indication and called party identification. M1 Adaptive Integration uses an intelligent connection between the Octel 200/300 and the M1 PBX. This intelligent connection is provided by the SIC8 Interface Card. The SIC8 connects to eight M2616 modular telephone sets.
Page 614 Direct Calls From External Trunks If the call comes in on a trunk, the M1 provides the Octel 200/300 with the trunk access code as the source of the call. Trunks may be directed to Octel 200/300 ports for answering via the M1 auto-terminate feature.
Page 615 11-3 Direct Internal Calls A person can call the Octel 200/300 directly either to enter a mailbox, send a Quick Message, or make a network call. The Octel 200/300 recognizes these calls as internal and not forwarded since the display shows the calling extension.
Page 616 M1 links (modular telephone extensions) connected to the Octel 200/300. Calls on incoming trunks to be handled by the Octel 200/300 are directed to this hunt group by using the M1 auto-terminate feature. The primary directory numbers (PDN) of the M1 links are configured as separate numbers, not as part of the Octel 200/300 hunt group.
Page 617 This option allows M1 digital telephones to send DTMF digits. 18 — Special Services for 2500 Set Features (SS25) This option allows touchtone forwarding of Octel 200/300 ports (2500 sets). 19 — Digit Display (DDSP) This option allows call information to appear on the M1 digital display telephones.
Page 618: 11.3 M1 Configuration
This number is configured into the M1 and assigned to a group of incoming CO, WATS, DID, or TIE trunks. There is no need to split the Octel 200/300 ports to achieve different greetings as long as the trunks themselves belong to different trunk groups. Therefore, to configure Octel 200/300 to play different greetings to external callers, the specific trunk group numbers must be known.
Page 619 Below is an example of a four-port Octel 200/300 hunt group where 300 through 303 are port extensions and 600 is the attendant’s extension — the overflow. The pilot number of this hunt group is 300.
Page 620 Caution! Step 2, EXTENSION NUMBER CHECK, in this chapter. Each Octel 200/300 port extension must have the following capabilities. For some M1 installations, these capabilities must be specifically configured for each Octel 200/300 port extension by COS (Class of Service).
Page 621 11-9 Configuring SIC8 and M2616 Modular Telephone Sets During INSTALL or UPDATE, the Octel 200/300 prompts whether to use a link for call processing, lamp message waiting, or both. For optimal performance, it is recommended that links not be configured to perform both call processing and message waiting.
Page 622 7 required for MWI link 8 Options for Octel 200/300 message servers with over 32 ports Two options for programming two SIC8 boards with over 32 ports are Option1 − Sequential configuration On the first SIC8 board, program ports 1 to 32 on links 1 to 4 and message waiting on links 5 to 8. On the Second SIC8 board, program ports 33 to 64 on links 1 to 4 and message waiting on links 5 to 8.
Page 623 2 to 64 link 4 2 to 64 (All even) link 5 link 6 No line appearances link 7 required for MWI link 8 These are example configurations; link configuration is dependent upon the type of application. PB60019-01 Octel 200/300 S.4.1...
Page 624: M1 (2616) Keyboard Layout
11-12 Integration Volume Figure 11-1 M1 (2616) Keyboard Layout Octel 200/300 S.4.1 PB60019-01...
Page 625 Not configured 08−14 scn XXXX Single call non-ring. This is Octel 200/300 line 1−10 appearance. Line 1 must be configured at key 8 with successive ports configured on successive keys. For example, key 9 = line 2. XXXX = extension of port appearance.
Page 626 M1 should be programmed not to forward internal calls on a busy condition. Internal callers may then use the camp-on feature, but will not have call coverage by the Octel 200/300 when busy. In addition, primary answer calls that reach a busy extension do not get call status (“is on the phone”). The prompt says “is unavailable.”...
Page 627 Meridian 1 Adaptive Integration 11-15 11.4 OCTEL 200/300 CONFIGURATION This section describes the changes that must be made to the Octel 200/300 configuration for message waiting indication and called party identification. Changes for Message Waiting Indication To configure the Octel 200/300 with message waiting indication on an M1, the following configuration changes must be made through the UPDATE program.
Page 628 Calls can be processed according to the COS of the trunk group they came in on instead of the COS of the port the Octel 200/300 answered the call with. This means ports do not have to be split among different hunt groups.
Page 629: Typical Meridian 1 Adaptive Integration Installation
The SIC8 installation involves connecting RS-232C cables from the SIC8 I/O panel mounted on the rear of the Octel 200/300 to a 2616 modular telephone set that is mounted on a shelf or rack. Each RS-232C cable supports one link on the Octel 200/300. A 25-pair cable connects the SIC8 I/O panel to the physical slot the SIC8 board resides in.
Page 630: Sic8 I/O Panel Designations
The SIC8 I/O panel connects eight external M2616 modular telephones to the SIC8 board via RS-232C cables. This assembly mounts at the rear lower panel of the Octel 200/300 cabinet. The M2616 modular telephone designated for link 1 is connected to IJ1, link 2 in IJ2, link 3 in IJ3, etc. Refer to Figure 11-3 for I/O panel designations.
Page 631: First Example Of Meridian Modular Telephone Cross-Connections
Transformer Figure 11-5 First Example of Meridian Modular Telephone Cross-connections 66M Connector Block (or equivalent) Telephone Connecting Meridian Block (or Connector) For Power M2616 Supply Leads phone Figure 11-6 Second Example of Meridian Modular Telephone Cross-connections PB60019-01 Octel 200/300 S.4.1...
Page 632 The system should always be checked for proper operation after the configuration database is installed or changes are made. In addition to the system test, there are some tests that should be made before the Octel 200/300 is connected. These tests are described in this section.
Page 633 Determine the cause and correct the problem before continuing. 2. EXTENSION NUMBER CHECK This test verifies that PBX extension numbers match the Octel 200/300 SLOTS Table Before continuing with this test, obtain a hardcopy of the SLOTS Table for reference.
Page 634 USER Table. 4. PBX BUSY FORWARD TEST This test verifies that a call to a busy extension forwards to the Octel 200/300 hunt group Connect telephone B to the modular adapter position associated with port 1 of the Octel 200/300.
Page 635 Answer telephone B. Verify talk path and voice quality. Hang up. 5. PBX RING-NO-ANSWER FORWARD TEST This test verifies that a call to a ring-no-answer extension forwards to the Octel 200/300 hunt group Connect telephone B to the modular adapter position associated with port 1 of the Octel 200/300.
Page 636 Connect telephone B to the jack position of the modular adapter associated with Port 1 of the Octel 200/300. b. From telephone C, call the extension number associated with telephone B.
Page 637 Determine the cause and correct the problem before continuing. o. Hang up telephone A. p. Cause telephone C to be in the Forward All Calls state to the Octel 200/300 hunt group. q. From telephone A, call telephone C. Press the Display Number Key on the M1 modular telephone set. Does the corresponding LCD turn ON? Determine the cause and correct the problem before continuing.
Page 638 On the terminal, at the @ prompt, enter the command P S. The port number in the IDL2 state is the port that Octel 200/300 thinks was called. If that is not the port you intended to call, the lines should be changed so that the correct line is connected to the correct port.
Page 639 This call should be pulled back by the transferring port and play the “doesn’t answer” prompt. Octel 200/300 Transfer to Ringing to an RNA extension. This call should forward to the Octel 200/300 through the PBX forwarding mechanism and play the “doesn’t answer” prompt.
Page 640 Determine the cause and correct before continuing. g. While still connected to the Octel 200/300, enter mailbox number YYY. h. Did the Octel 200/300 respond with the prompt, “Thank you. Just a moment,” and did phone C start to ring again? Continue.
Page 641 Did the Octel 200/300 respond with the prompt, “Thank you. Just a moment”? Continue. Determine the cause and correct the problem before continuing. After a short interval, does the Octel 200/300 respond with, “Extension XXX busy/on the phone. Please leave a message at the tone”? Continue.
Page 642 13. HUNT GROUP OPERATION TEST (FOR NEW INSTALL) Verifying the hunting sequence The terminal command P S displays the current status of each Octel 200/300 port. A three character abbreviation denotes the state of each port. Refer to the Installation and Maintenance volume, Maintenance Commands chapter, for more information on using the P S command and the meaning of the states.
Page 643 Does the call overflow to the correct answering extension as determined for fail-safe operation? Determine the cause and correct the problem before continuing. Remove the busy condition from all Octel 200/300 port PBX extensions by entering at the @ prompt...
Page 644 From telephone A, call out and back in on a trunk dedicated to the hunt group. o. Does the call overflow to the correct destination? Determine the cause and correct the problem before continuing. p. Remove the busy condition from all Octel 200/300 port extensions by entering at the @ prompt TE C 2 Enter q.
Page 645 11-33 17. CALLS TO THE INTERCEPT EXTENSION (For new install) This test verifies that the Octel 200/300 can transfer a call to the intercept position (attendant) when the caller does nothing or presses From telephone A, call outside of the PBX and back in on a trunk dedicated to the Octel 200/300.
Page 646 Answer telephone C (or call the Octel 200/300 and enter the mailbox if the indicator is lit). The Octel 200/300 should respond with “... has X messages. Ready,” or Octel 200/300 might also ask for a security code.
Page 647 Link 1 through 8 Yellow Installation Procedure The SIC8 board is installed in the Octel 200/300 cabinet as follows: 1.. Forward the Octel 200/300 ports (TE C 1). 2.. Turn the power to the Octel 200/300 cabinet OFF. The SIC8 goes through a short power-on routine. The cycle during the power-on routine is as...
Page 648 CLEAR INTEGRATION This command clears the SIC8 board pegs. The form of the command is C INT x y C INT x y where x is the slot number where y is the integration unit number (1) Octel 200/300 S.4.1 PB60019-01...
Page 649 Only the states DOWN and DEAD are error conditions. The link is probably disconnected. Integration Pegs There are two types of pegs for integrated systems. These pegs are independent of the Octel 200/300 traffic pegs and can only be listed by using the L INT command. PB60019-01 Octel 200/300...
Page 650 Number of times the Display LCD was in the wrong state when attempting to press it. PEG 10 Not used. For information on hardware errors regarding integrated systems, refer to the Installation and Maintenance volume, System Errors and Traffic Pegs chapter, for more information. Octel 200/300 S.4.1 PB60019-01...
Page 651 11-39 11.9 INSTALLATION CHECKLIST This section contains checklists of issues relating to the Octel 200/300 and to the M1. The list is presented in the order in which the installation process should be followed. For details regarding any topic, refer to the sections of this chapter pertaining to the issue.
Page 652 Complete Incoming trunks that auto-terminate to the Octel 200/300: If new trunk groups are to be answered by the Octel 200/300 and are not programmed to auto-terminate, do that now. Answer YES to the auto prompt of the route Data Block (RDB) Enter the main number of the hunt group to the ATDN prompt of the Trunk Data Block.
Page 653 Hotline (off) AUT=OFF Auto answer (off) BAUD=ON Baud rate (9600) DCD=ON Dynamic CD (on) PRM KBD=ON No prompt (Host mode) VLL=OFF Virtual leased line (off) MOD=YES Yes = Network INT=OFF SL-1/100 Interworking (off) CLK=OFF Clock (off) PB60019-01 Octel 200/300 S.4.1...
Page 654 Phones that require secondary answering must be programmed to for- ward on a no-answer and hunt on busy conditions to the main “pilot number” of the Octel 200/300 hunt group. Set the prompts as follows: HUNT XXXX (main pilot number of the Octel 200/300 hunt group)
Page 655: Octel 200/300 Requirements
Table. Obtain Access Code numbers from M1 vendor. Set the ring cycle to be one less than the ring cycle in .M INFO the M1. Index #7 Table 11-7 Octel 200/300 Configuration Changes to MWI Item Description Command Complete Modify System Parameter 9 to be 700 (increase flash .M SYS 9...
Page 656 .M SYS 117 before answering). Add Attribute 15 to the COS of all mailboxes asso- .A COS ciated with extensions that forward to Octel 200/300. All ports should be configured in AX mode. .M SLOT Configure the TRUNK GROUP Table if different .A TRUNK...
Page 657 2500 type telephone sets, one with message waiting allowed. Terminal/teleprinter connected to J1 or SP1 connector via RS-232C. Hardcopy of the Octel 200/300 and M1 database. 1 each Extensions for testing, in addition to the port exten- sion. One extension must have message waiting al- lowed and be busy and RNA forwarded into the Octel 200/300 hunt group.
Page 659 ........12.3-1 PB60019-01 Octel 200/300 S.4.1...
Page 661 ..........12.1-23 Configuring Adaptive Integration on the Octel 200/300 ......
Page 662 ..............12.1-28 Octel 200/300 S.4.1...
Page 663 When the APIC card is installed, no analog ports are required. The Octel 200/300 can process the call and provide call coverage based upon the type of call and desired coverage. Any information that the DEFINITY G3 provides to an AT&T display phone station (either on the display itself or by the display set LEDs) is available to the Octel 200/300.
Page 664 The source extension or trunk group, the called extension, and the status of forwarded calls With this information, the Octel 200/300 can process the various types of calls appropriately. The Octel 200/300 receives the necessary call information from the DEFINITY G3 through the digital ports of the APIC.
Page 665 Send All Calls “(name) is unavailable” If System Parameter 115 is set to Y, the Octel 200/300 uses “(name) is on the phone” instead of “(name) is busy.” Refer to the Feature Description volume, Customizing Mailbox Features, for further details.
Page 666 Upon receiving the forwarded call, the Octel 200/300 plays the mailbox’s greeting for that extension, if the greeting is ON. If the greeting is OFF, the Octel 200/300 prompts the caller with the status of the extension, followed by the prompt “Please leave a message at the tone, enter another extension number, or press zero for personal assistance.”...
Page 667 = T−XXX to OPERATOR Direct Internal Calls A caller can access the Octel 200/300 directly to enter a mailbox, send a Quick Message or fax, or make a network call. For these direct internal calls, the DEFINITY G3 sends this type of display: a = XXXX to A-YYYY XXXX is the number of the calling extension and YYYY is access extension number.
Page 668 When the person receiving the message listens to it, the Octel 200/300 is able to play the name associated with the extension from which the message was left before playing the message itself. The person receiving the message may automatically reply to the message.
Page 669 Any release of DEFINITY G3 software can be used for the installation with Adaptive Integration. Configuration Requirements The DEFINITY G3 configuration must have one unassigned Class of Restriction (COR) available to configure for the APIC ports. * TN754B, Vintage 2 or later versions only. Octel 200/300 S.4.1 PB60019-01...
Page 670 The DEFINITY G3 allows each extension, pilot number, and trunk group to have an alphanumeric name. The information needed by the Octel 200/300 message server must be contained within the first 16 characters. If an extension is given a name, Adaptive Integration requires that it meet certain restrictions.
Page 671: Chapter 12.1 Definity G3 Adaptive Integration With Apic
COR Configuration Changes A new COR (Classes of Restriction) for the Octel 200/300 ports (port COR) must be defined in the DEFINITY G3 for use with Adaptive Integration. This COR is assigned to the digital stations configured as the message server ports.
Page 672: Cor Data For Apic Ports
1. Obtain a list of CORs currently in use on the DEFINITY G3. ____ 2. Select a new port COR that is used exclusively for the Octel 200/300. This port COR is used for all Octel 200/300 APIC ports. ____ 3.
Page 673: Cor Data Showing Port Cor Marked Y
Figure 12.1-2 COR Data Showing Port COR Marked Y In Figure 12.1-2, XX is any COR in the PBX, except COR 62. COR 62 is used for the APIC ports. The other CALLING PERMISSION entries are not changed. Octel 200/300 S.4.1 PB60019-01...
Page 674 A digital telephone station must be allocated for each APIC port. These stations must be properly configured as 7405D sets in the DEFINITY G3 to interface with the Octel 200/300. For proper functionality, each port must be set up to do either call processing or message waiting.
Page 675 Feature Module? n Display? Coverage Module? n Disp Clint Redir? n Figure 12.1-3 STATION Data Entry Screen − Page 1 Feature Option, LWC Reception choice, msa or spe, is site specific; consult your AT&T technical contact. Octel 200/300 S.4.1 PB60019-01...
Page 676: Apic Port Data Entry Screen − Display Button Assignments
Figure 12.1-4 STATION Data Entry Screen − Page 2 Page x of x STATION DISPLAY BUTTON ASSIGNMENTS 1: normal 2: __________ 3: __________ 4: __________ 5: __________ 6: __________ 7: __________ Figure 12.1-5 APIC Port Data Entry Screen − Display Button Assignments Octel 200/300 S.4.1 PB60019-01...
Page 677: Hunt Group Data Entry Screen
4. Assign the hunt group a coverage path (CPX) that has the attendant as its first coverage point. This coverage path ensures that if the Octel 200/300 is not working, calls default to the attendant. Refer to the Coverage Path Configuration section, step 6.
Page 678: Hunt Group Data Entry Screen − Group Member Assignments
12.1-16 Integration Volume The example in the Name column of the screen below refers to APIC port position. The Octel 200/300 does not use the information in the Name column to process calls. Page HUNT GROUP Message Center: LWC Reception:...
Page 679 Any incoming CO trunk group answered by the Octel 200/300 must have its incoming destination defined to be the Octel 200/300 hunt group. All incoming trunk groups carrying calls that could be directed or re-directed to the Octel 200/300 must be named using the format required for identification by the Octel 200/300.
Page 680 Enclosing the station extension within the station owner’s name in the Name entry preserves the functionality of the DEFINITY G3’s directory feature. Extension numbers typically are the same as the Octel 200/300 mailbox numbers associated with them. 3. Message waiting indication only — If the station has a message waiting indicator, enable “Leave Word Calling Reception”...
Page 681 Coverage Path Configuration All extensions that are to use the Octel 200/300 for call coverage must be assigned a coverage path that includes the Octel 200/300 as a coverage point. This may require the addition of new coverage paths as well as the modification of existing coverage paths.
Page 682 The coverage path is set up as follows: The first coverage point is the Octel 200/300 hunt group. The second coverage point (in the event the Octel 200/300 fails to answer the call) is the attendant (extension 0). No third point is specified.
Page 683 Point, defaults to YES and allows the transfer of a call from one digital set to another digital set without going to coverage. This may cause calls to the Octel 200/300 to be bridged. Set this feature parameter to NO if this should occur.
Page 684 TRUNK GROUP Table enables the Octel 200/300 to process the call according to the trunk group on which the call was received, instead of according to which port the Octel 200/300 answered the call on. This means integrated ports do not have to be split to answer calls from different trunk sources differently.
Page 685 200/300. Configuring Adaptive Integration on the Octel 200/300 To configure the Octel 200/300 Adaptive Integration to work with DEFINITY G3, changes to the COS, INFORMATION Table, System Parameter Table and SLOTS Table must be made in UPDATE. The following explains the type of changes that may be required.
Page 686 COS Attribute 58 — DO NOT USE THIS PORT FOR INTEGRATION Assign this COS attribute to those Octel 200/300 ports used in special applications that do not require integration. These ports would be supported by standard line cards rather than the APIC cards.
Page 687 Type 24, Data 1−7 errors in the Hardware Error Table. With the PIC integration, analog ports cannot be used for MWI. If analog ports are installed, use them for other outcalls, such as network and offsite message waiting. Octel 200/300 S.4.1 PB60019-01...
Page 688 The ports answer calls with the port-level company greeting in the event that the Octel 200/300 does not receive call information from the digit display links. System Parameter 170 — INTEGRATION LAMP ON/OFF LINK MUST MATCH Modify System Parameter 170 to be YES.
Page 689 Definity G3 Adaptive Integration with APIC 12.1-27 Octel 200/300 Configuration Checklist Below is a checklist for configuring the Octel 200/300 message server. The message server command is listed. Configuration Step Command Assign COS Attribute 9 only to mailboxes that will use MWI .A COS...
Page 690 Octel 200/300. These tests verify that APIC Adaptive Integration works properly with the PBX. Some of the tests are made before the Octel 200/300 is connected to the PBX. Always check the PBX for proper operation after any changes are made to the system.
Page 691 The extension numbers of these extensions must be consistent with the format of the mailbox numbers in the Octel 200/300 USER Table. For example, the first digit and the number of digits in the extensions must correspond to the mailbox numbering scheme.
Page 692 This ensures that the cables can be reconnected correctly after the APIC card is installed. If the Octel 200/300 ports are not connected to their assigned DEFINITY G3 extensions, the Octel 200/300 may not handle calls properly.
Page 693 This test verifies that dial tone is present on each of the extensions used for the APIC ports. The 25-pair cables should be disconnected from the back of the Octel 200/300. Connect the modular adapter to the 25-pair cable associated with the configured slot.
Page 694 Answer the call on phone C. Verify the talk path. Hang up phone A and phone C. 3. PBX RING-NO-ANSWER FORWARD TEST This test verifies that a call to a ring-no-answer (RNA) extension forwards to the Octel 200/300 access number.
Page 695 Answer phone C. Hang up phone A and phone C. 5. MESSAGE WAITING INDICATOR TEST (For installations using the Octel 200/300 to control message waiting indicators) This test verifies that a message waiting indicator can be set and cleared using the LWC feature codes programmed.
Page 696 Determine the cause, and correct the problem before continuing. d. Connect phone C to the jack position of the modular adapter of the next Octel 200/300 port extension. Repeat steps b. through d. until every Octel 200/300 port has successfully transferred a call to the attendant.
Page 697: Installing The Sic8 Board
This section describes the procedure for installing the APIC board. Reconnect the 25-pair cable to the Octel 200/300. Before proceeding with installation, note that there are 18 LEDs on the front edge of the APIC, near the top of the card. The first through fourteenth LEDs are used to indicate card status and are,...
Page 698 Testing Adaptive Integration This section describes the procedures for testing Adaptive Integration features. Once the APIC card is installed and operational and the PBX cable is re-connected to the correct Octel 200/300 ports, proceed with the following tests. 1. CONFIGURING THE OCTEL 200/300 FOR TEST Before proceeding, make the following changes to the Octel 200/300 configuration.
Page 699 This shows the port the call came in on. b. From phone A, call the extension of the Octel 200/300 port 1. Phone A must have the same COR as the digital links to call the Octel 200/300 ports directly.
Page 700 Take phone B off-hook so that it appears busy. b. From phone A, call phone B. Does the Octel 200/300 answer with the prompt, “Extension EXTB is unavailable. Please leave a message at the tone. . . ”? Determine the cause and correct the problem before continuing.
Page 701 TE C 1 x where x is the port number. Repeat steps a. through d. for each Octel 200/300 port until all of the ports are busied out. This is to confirm that each Octel 200/300 port can answer a trunk call.
Page 702 Determine the cause, and correct the problem before continuing. From phone A, call out and back in on a trunk that auto-terminates to the Octel 200/300. When the Octel 200/300 answers, let the system time out; do not enter any digits.
Page 703 This test verifies correct operation of message waiting indication for systems using MWI. Take phone B off-hook so that it appears busy. b. From phone A, call out and back in on a trunk auto-terminated to the Octel 200/300. Does the Octel 200/300 answer properly? Determine the cause, and correct the problem before continuing.
Page 704 A message is not delivered to a mailbox unless it is at least 4.5 seconds in length. Leave a test message approximately 15−20 seconds in length to ensure a valid message. The mailbox for phone B must be entered in the Octel 200/300 USER Table or the Octel 200/300 does not offer to take a message.
Page 705 Take phone B off-hook to make it appear busy. b. From phone A, call phone B. Does the Octel 200/300 answer with the greeting for Trunk Group 0? Determine the cause, and correct the problem before continuing.
Page 707 ..........12.2-23 Configuring Adaptive Integration on the Octel 200/300 ......
Page 708: Test Equipment
..............12.2-28 Octel 200/300 S.4.1...
Page 709 When the APIC card is installed, no analog ports are required. The Octel 200/300 can process the call and provide call coverage based upon the type of call and desired coverage. Any information that the System 75 provides to an AT&T display phone station (either on the display itself or by the display set LEDs) is available to the Octel 200/300.
Page 710 The source extension or trunk group, the called extension, and the status of forwarded calls With this information, the Octel 200/300 can process the various types of calls appropriately. The Octel 200/300 receives the necessary call information from the System 75 through the digital ports of the APIC.
Page 711 Send All Calls “(name) is unavailable” If System Parameter 115 is set to Y, the Octel 200/300 uses “(name) is on the phone” instead of “(name) is busy.” Refer to the Feature Description volume, Customizing Mailbox Features, for further details.
Page 712 Upon receiving the forwarded call, the Octel 200/300 plays the mailbox’s greeting for that extension, if the greeting is ON. If the greeting is OFF, the Octel 200/300 prompts the caller with the status of the extension, followed by the prompt “Please leave a message at the tone, enter another extension number, or press zero for personal assistance.”...
Page 713 = T−XXX to OPERATOR Direct Internal Calls A caller can access the Octel 200/300 directly to enter a mailbox, send a Quick Message or fax, or make a network call. For these direct internal calls, the System 75 sends this type of display: a = XXXX to A-YYYY XXXX is the number of the calling extension and YYYY is access extension number.
Page 714 When the person receiving the message listens to it, the Octel 200/300 is able to play the name associated with the extension from which the message was left before playing the message itself. The person receiving the message may automatically reply to the message.
Page 715 All software releases for Definity G1 are acceptable. Configuration Requirements The System 75 configuration must have one unassigned Class of Restriction (COR) available to configure for the APIC ports. * TN754B, Vintage 2 or later versions only. Octel 200/300 S.4.1 PB60019-01...
Page 716 The System 75 allows each extension, pilot number, and trunk group to have an alphanumeric name. The information needed by the Octel 200/300 message server must be contained within the first 16 characters. If an extension is given a name, Adaptive Integration requires that it meet certain restrictions. The port extensions and trunk groups must have names.
Page 717: Chapter 12.2 At&T System 75/Definity G1 Adaptive Integration With Apic
COR Configuration Changes A new COR (Classes of Restriction) for the Octel 200/300 ports (port COR) must be defined in the System 75 for use with Adaptive Integration. This COR is assigned to the digital stations configured as the message server ports.
Page 718: Cor Data Showing Port Cor Marked Y
1. Obtain a list of CORs currently in use on the System 75. ____ 2. Select a new port COR that is used exclusively for the Octel 200/300. This port COR is used for all Octel 200/300 APIC ports. ____ 3.
Page 719: Cor Data For Another System Cor − Showing Port Cor Marked Y
Figure 12.2-2 COR Data for Another System COR − Showing Port COR Marked Y In Figure 12.2-2, XX is any COR in the PBX, except COR 62. COR 62 is used for the APIC ports the other CALLING PERMISSION entries are not changed. Octel 200/300 S.4.1 PB60019-01...
Page 720 A digital telephone station must be allocated for each APIC port. These stations must be properly configured as 7405D sets in the System 75 to interface with the Octel 200/300. For proper functionality, each port must be set up to do either call processing or message waiting.
Page 721 701A Data Module? n F401A Feature Module? n C401A Coverage Module? n D401A Display Module? ABBREVIATED DIALING List1: ________ List2: ________ List3: ________ BUTTON ASSIGNMENTS 1: call-appr 2: call-appr Figure 12.2-3 APIC Port Data Entry Screen − Page 1 Octel 200/300 S.4.1 PB60019-01...
Page 722: Apic Port Data Entry Screen − Display Button Assignments
4. Assign the hunt group a coverage path (CPX) that has the attendant as its first coverage point. This coverage path ensures that if the Octel 200/300 is not working, calls default to the attendant. Refer to the Coverage Path Configuration section, step 6.
Page 723: Hunt Group Data Entry Screen − Group Member Assignments
Group Number: HX Group Extension: EXTNH Group Type: UCD Group Member Assignments Name Name Name D-PORT1 D-PORT2 D-PORT3 D-PORT4 D-PORT5 D-PORT6 D-PORT7 D-PORT8 D-PORT9 D-PORT10 Figure 12.2-6 Hunt Group Data Entry Screen − Group Member Assignments Octel 200/300 S.4.1 PB60019-01...
Page 724 Any incoming CO trunk group answered by the Octel 200/300 must have its incoming destination defined to be the Octel 200/300 hunt group. All incoming trunk groups carrying calls that could be directed or re-directed to the Octel 200/300 must be named using the format required for identification by the Octel 200/300.
Page 725 Disconnect Timing(msec): ____ ACA Assignment? _ Long Holding Time(hours): ___ Short Holding Time(secs.): ____ Short Holding Threshold: ___ Maintenance Test? ___ Answer Supervision Timeout: ______ Suppress # Outpulsing? ____ Figure 12.2-7 Trunk Group Data Entry Screen Octel 200/300 S.4.1 PB60019-01...
Page 726 Enclosing the station extension within the station owner’s name in the Name entry preserves the functionality of the System 75’s directory feature. Extension numbers typically are the same as the Octel 200/300 mailbox numbers associated with them. 3. Message waiting indication only — If the station has a message waiting indicator, enable “Leave Word Calling Reception”...
Page 727 Coverage Path Configuration All extensions that are to use the Octel 200/300 for call coverage must be assigned a coverage path that includes the Octel 200/300 as a coverage point. This may require the addition of new coverage paths as well as the modification of existing coverage paths.
Page 728 The coverage path is set up as follows: The first coverage point is the Octel 200/300 hunt group. The second coverage point (in the event the Octel 200/300 fails to answer the call) is the attendant (extension 0). No third point is specified.
Page 729 Point, defaults to YES and allows the transfer of a call from one digital set to another digital set without going to coverage. This may cause calls to the Octel 200/300 to be bridged. Set this feature parameter to NO if this should occur.
Page 730 TRUNK GROUP Table enables the Octel 200/300 to process the call according to the trunk group on which the call was received, instead of according to which port the Octel 200/300 answered the call on. This means integrated ports do not have to be split to answer calls from different trunk sources differently.
Page 731 Proceed with configuring adaptive integration on the Octel 200/300. Configuring Adaptive Integration on the Octel 200/300 To configure the Octel 200/300 Adaptive Integration to work with System 75, changes to the COS, SLOTS T INFORMATION Table, System Parameter Table and able must be made in UPDATE.
Page 732 COS Attribute 58 — DO NOT USE THIS PORT FOR INTEGRATION Assign this COS attribute to those Octel 200/300 ports used in special applications that do not require integration. These ports would be supported by standard line cards rather than the APIC cards.
Page 733 Type 24, Data 1−7 errors in the Hardware Error Table. With the PIC integration, analog ports cannot be used for MWI. If analog ports are installed, use them for other outcalls, such as network and offsite message waiting. Octel 200/300 S.4.1 PB60019-01...
Page 734 The ports answer calls with the port-level company greeting in the event that the Octel 200/300 does not receive call information from the digit display links. System Parameter 170 — INTEGRATION LAMP ON/OFF LINK MUST MATCH Modify System Parameter 170 to be YES.
Page 735 AT&T System 75/Definity G1 Adaptive Integration with APIC 12.2-27 Octel 200/300 Configuration Checklist Below is a checklist for configuring the Octel 200/300 message server. The message server command is listed. Configuration Step Command Assign COS Attribute 9 only to mailboxes that will use MWI .A COS...
Page 736 Octel 200/300. These tests verify that APIC Adaptive Integration works properly with the PBX. Some of the tests are made before the Octel 200/300 is connected to the PBX. Always check the PBX for proper operation after any changes are made to the system.
Page 737 The extension numbers of these extensions must be consistent with the format of the mailbox numbers in the Octel 200/300 USER Table. For example, the first digit and the number of digits in the extensions must correspond to the mailbox numbering scheme.
Page 738 Octel 200/300, the 25-pair cable connecting the Octel 200/300 ports to the System 75. Before disconnecting the Octel 200/300 25-pair cable, mark each one with the slot number to which it is connected. This ensures that the cables can be reconnected correctly after the APIC card is installed.
Page 739 This test verifies that dial tone is present on each of the extensions used for the APIC ports. The 25-pair cables should be disconnected from the back of the Octel 200/300. Connect the modular adapter to the 25-pair cable associated with the configured slot.
Page 740 Answer the call on phone C. Verify the talk path. Hang up phone A and phone C. 3. PBX RING-NO-ANSWER FORWARD TEST This test verifies that a call to a ring-no-answer (RNA) extension forwards to the Octel 200/300 access number.
Page 741 Answer phone C. Hang up phone A and phone C. 5. MESSAGE WAITING INDICATOR TEST (For installations using the Octel 200/300 to control message waiting indicators) This test verifies that a message waiting indicator can be set and cleared using the LWC feature codes programmed.
Page 742 Determine the cause, and correct the problem before continuing. d. Connect phone C to the jack position of the modular adapter of the next Octel 200/300 port extension. Repeat steps b. through d. until every Octel 200/300 port has successfully transferred a call to the attendant.
Page 743 All cross-connections to the PBX must be completed before proceeding. Changes to connections should only be made while the integration card is not installed in the Octel 200/300. Cross-connecting Caution! integration links when the integration card is installed may result in damage to the integration card.
Page 744 From phone A, call the extension of the Octel 200/300 port 1. Phone A must have the same COR as the digital links to call the Octel 200/300 ports directly. Does the Octel 200/300 answer with the company greeting? Correct the problem before continuing.
Page 745 Take phone B off-hook so that it appears busy. b. From phone A, call phone B. Does the Octel 200/300 answer with the prompt, “Extension EXTB is unavailable. Please leave a message at the tone. . . ”? Determine the cause and correct the problem before continuing.
Page 746 TE C 1 x where x is the port number. Repeat steps a. through d. for each Octel 200/300 port until all of the ports are busied out. This is to confirm that each Octel 200/300 port can answer a trunk call.
Page 747 200/300. Does the Octel 200/300 answer with the greeting configured for the trunk? Determine the cause, and correct the problem before continuing. b. Call the extension of phone B. Does the Octel 200/300 respond with, “Thank you, just a moment. . .” Does phone B start ringing? Determine the cause, and correct the problem before continuing.
Page 748 Determine the cause, and correct the problem before continuing. From phone A, call out and back in on a trunk that auto-terminates to the Octel 200/300. When the Octel 200/300 answers, let the system time out; do not enter any digits.
Page 749 Call the extension number of phone B. The Octel 200/300 should respond, “Extension EXTB is busy. Please leave a message at the tone, enter another extension number, or press zero for assistance.
Page 750 Take phone B off-hook to make it appear busy. b. From phone A, call phone B. Does the Octel 200/300 answer with the greeting for Trunk Group 0? Determine the cause, and correct the problem before continuing.
Page 751: Test Equipment
12.3-16 Configuring Adaptive Integration on the Octel 200/300 ........
Page 753 When the APIC card is installed, no analog ports are required. The Octel 200/300 can process the call and provide call coverage based upon the type of call and desired coverage. Any information that the System 85 provides to an AT&T display phone station (either on the display itself or by the display set LEDs) is available to the Octel 200/300.
Page 754 The source extension or trunk group, the called extension, and the status of forwarded calls With this information, the Octel 200/300 can process the various types of calls appropriately. The Octel 200/300 receives the necessary call information from the System 85 through the digital ports of the APIC.
Page 755 Send All Calls “(name) is unavailable” If System Parameter 115 is set to Y, the Octel 200/300 uses “(name) is on the phone” instead of “(name) is busy.” Refer to the Feature Description volume, Customizing Mailbox Features chapter, for further details.
Page 756 Upon receiving the forwarded call, the Octel 200/300 plays the mailbox’s greeting for that extension, if the greeting is ON. If the greeting is OFF, the Octel 200/300 prompts the caller with the status of the extension, followed by the prompt “Please leave a message at the tone, enter another extension number, or press zero for personal assistance.”...
Page 757 AT&T System 85/Definity G2 Adaptive Integration 12.3-5 Direct Internal Calls A caller can access the Octel 200/300 directly to enter a mailbox, send a Quick Message or fax, or make a network call. For these direct internal calls, the System 85 displays the following: a = XXXX to A−YYYY...
Page 758 When the person receiving the message listens to it, the Octel 200/300 is able to play the name associated with the extension from which the message was left before playing the message itself. The person receiving the message may automatically reply to the message.
Page 759 APIC message server port. For greater reliability, ports should be provided from multiple cards in the switch. One 25-pair cable per APIC slot is required, from the Octel 200/300 to the location for connecting the ports. When using 2500-type telephone sets with message waiting lamps other than AT&T 3178-SYSI or equivalent, special PBX hardware may be required in order to allow the System 85 to control the message waiting lamp.
Page 760 Integration Volume 12.3.3 CONFIGURING AT&T SYSTEM 85 Several changes must be made to the System 85 configuration to utilize Octel 200/300’s AI features. The System 85 configuration used for Octel 200/300 with AI is slightly different from the configuration used for a non-integrated Octel 200/300.
Page 761 Octel 200/300 Port The name must contain the string D-XXXX, Extensions where XXXX is the extension number of the Octel 200/300 port. The D should be in upper case in order for the call record to be recognized. ACD/UCD Hunt Group...
Page 762 A digital telephone station must be allocated for each APIC port. These stations must be properly configured as 7405D sets in the System 85 to interface with the Octel 200/300. For proper functionality, each port must be set up to do either call processing or message waiting.
Page 763 Term to Term Only Disabled Inward Restrict Disabled Man. Term. Restrict Disabled Orig. Restrict Disabled Outward Restrict Disabled Term. Restrict Disabled Toll/Code Restrict Disabled The other attributes can be enabled/disabled as required at the particular installation. Octel 200/300 S.4.1 PB60019-01...
Page 764 All of the APIC ports to be used for call processing are to be configured into a hunt group. 1. Create the terminal ACD (UCD) hunt group containing the extensions of the Octel 200/300 ports. 2. Assign the extension for Octel 200/300 Port 1 as the supervisor’s extension.
Page 765 AT&T System 85/Definity G2 Adaptive Integration 12.3-13 Call Coverage All extensions that are to use Octel 200/300 for call coverage must be assigned Call Coverage Group that includes Octel 200/300 as a coverage point. This may require addition of new Call Coverage Groups as well as modification of existing groups.
Page 766 3. Message waiting indication only — If the station has a message waiting indicator, be sure that “Leave Word Calling Reception” is enabled in that stations COS. 4. Assign the station to be forwarded to the Octel 200/300 to an appropriate call coverage group that includes the Octel 200/300 as a point of coverage.
Page 767 TRUNK GROUP Table enables the Octel 200/300 to process the call according to the trunk group on which the call was received, instead of according to which port the Octel 200/300 answered the call on. This means integrated ports do not have to be split. The following are some examples of how this can be applied.
Page 768 200/300. Configuring Adaptive Integration on the Octel 200/300 To configure the Octel 200/300Adaptive Integration to work with System 85, changes to the COS, INFORMATION Table, System Parameter Table and SLOTS Table must be made in UPDATE. The following explains the type of changes that may be required.
Page 769 Port COS COS Attribute 58 — DO NOT USE THIS PORT FOR INTEGRATION Assign this COS attribute to those Octel 200/300 ports used in special applications that do not require integration. INFORMATION Table INFORMATION Table Index 25 — QUICK GREETING...
Page 770 Modify System Parameter 116 to be YES. System Parameter 117— RINGBACKS BEFORE ANSWERING AX PORT Modify System Parameter 117 to be 5. This gives the Octel 200/300 extra time to receive the call records from the PBX. Octel 200/300 S.4.1...
Page 771 APIC. This system parameter provides a fail-safe mode of operation. The ports answer calls in AX mode in the event that the Octel 200/300 does not receive call information from the digit display links.
Page 772 12.3-20 Integration Volume Octel 200/300 Configuration Checklist Below is a checklist for configuring the Octel 200/300 message server. The message server command is listed. Configuration Step Command Assign COS Attribute 9 only to mailboxes that will use MWI .A COS...
Page 773 Octel 200/300. These tests verify that APIC Adaptive Integration works properly with the PBX. Some of the tests are made before the Octel 200/300 is connected to the PBX. Always check the PBX for proper operation after any changes are made to the system.
Page 774 The extension numbers of these extensions must be consistent with the format of the mailbox numbers in the Octel 200/300 USER Table. For example, the first digit and the number of digits in the extensions must correspond to the mailbox numbering scheme.
Page 775 This test verifies that dial tone is present on each of the extensions used for the APIC ports. The 25-pair cables should be disconnected from the back of the Octel 200/300. Connect the modular adapter to the 25-pair cable associated with the configured slot.
Page 776 Answer the call on phone C. Verify the talk path. Hang up phone A and phone C. 3. PBX RING-NO-ANSWER FORWARD TEST This test verifies that a call to a ring-no-answer (RNA) extension forwards to the Octel 200/300 access number.
Page 777 AT&T System 85/Definity G2 Adaptive Integration 12.3-25 4. PBX FORWARD ALL CALLS TEST This test verifies that an extension can forward all calls to the Octel 200/300 access number. Connect the modular adapter to the 25-pair cable associated with the configured slot.
Page 778 Determine the cause, and correct the problem before continuing. d. Connect phone C to the jack position of the modular adapter of the next Octel 200/300 port extension. Repeat steps b. through d. until every Octel 200/300 port has successfully transferred a call to the attendant.
Page 779 This section describes the procedure for installing the APIC board. Reconnect the 25-pair cable to the Octel 200/300. Before proceeding with installation, note that there are 18 LEDs on the front edge of the APIC, near the top of the card. The first through fourteenth LEDs are used to indicate card status and are,...
Page 780 Testing Adaptive Integration This section describes the procedures for testing Adaptive Integration features. Once the APIC card is installed and operational and the PBX cable is re-connected to the correct Octel 200/300 ports, proceed with the following tests. 1. CONFIGURING THE OCTEL 200/300 FOR TEST Before proceeding, make the following changes to the Octel 200/300 configuration.
Page 781 This shows the port the call came in on. b. From phone A, call the extension of the Octel 200/300 port 1. Phone A must have the same COR as the digital links to call the Octel 200/300 ports directly.
Page 782 TE C 1 x where x is the port number. Repeat steps a. through d. for each Octel 200/300 port until all of the ports are busied out. This is to confirm that each Octel 200/300 port can answer a trunk call.
Page 783 200/300. Does the Octel 200/300 answer with the greeting configured for the trunk? Determine the cause, and correct the problem before continuing. b. Call the extension of phone B. Does the Octel 200/300 respond with “Thank you, just a moment. . .” Does phone B start ringing? Determine the cause, and correct the problem before continuing.
Page 784 Determine the cause, and correct the problem before continuing. From phone A, call out and back in on a trunk that auto-terminates to the Octel 200/300. When the Octel 200/300 answers, let the system time out; do not enter any digits.
Page 785 You may prefer to use the Quick Message feature to leave a message for phone B instead of following the instructions in step d. and e. d. Call the extension number of phone B. The Octel 200/300 should respond with “Extension EXTB is busy. Please leave a message at the tone, enter another extension number, or press zero for assistance.
Page 786 Take phone B off-hook to make it appear busy. b. From phone A, call phone B. Does the Octel 200/300 answer with the greeting for Trunk Group 0? Determine the cause, and correct the problem before continuing.
Page 787 12.3A-3 To Assign a COS to an Extension for the Octel 200/300 Ports and Links 1 and 2 ......
Page 788 12.3A-2 Integration Volume PB60019-01 Octel 200/300 S.4.1...
Page 789 PROCS. System 85 configurations are commonly referred to as translations. When possible, the relevant SMT PROCS are listed below. To Define the COS for the Octel 200/300 Ports PROC 010,word 1 Field...
Page 790 (Not restricted) Toll/Code Restrict (Not restricted) Auto route selection Site dependant FRL Level Site dependant To Assign a COS to an Extension for the Octel 200/300 Ports and Links 1 and 2 PROC 000, word 1 Field Name Set To Meaning...
Page 791 Field 9 should be set to 1 for button 3, and set to 2 for button 4. PROC 052, word 2 Field Name Set To Meaning Extn Number Extension of an Octel 200/300 port Line Appearance # Type of transfer Ringing Transfer (No Ringing Transfer) Repeat for second call appearance. PROC 054, word 4 Field...
Page 792 To Specify the Characteristics of the ACD (UCD) Group PROC 026, word 1 Field Name Set To Meaning ACD number ACD number for the Octel 200/300 group Group size Number of ports ICI Message number No ICI message Outflow level Site dependant Queue warning lamp Both −...
Page 793 AT&T System 85/Definity G2 SMT Configuration Descriptions with APIC 12.3A-7 To Add the Octel 200/300 Port Extensions to the ACD Group (UCD) Repeat this for each extension that is an Octel 200/300 port. PROC 026, word 3 Field Name Set To...
Page 795 Page To Assign a Cos for the Octel 200/300 Apic Ports ............
Page 796 12.3B-2 Integration Volume Octel 200/300 S.4.1 PB60019-01...
Page 797 The following glossary explains abbreviations used in the examples on the following pages. When you see an abbreviation in parentheses, use the corresponding number as described below. DPCOS The Class of Service which is used for the Octel 200/300 APIC ports. DPEXT Refers to the extension number associated with an Octel 200/300.
Page 798 Stop Hunt Call Waiting Timed Recall Exempt Touchtone Data Protection Transfer/Conf-Three Way Ring Ping Immediate ACD Queue Status Display Page 1 of 2 Note that for the Octel 200/300, the “ACD (UCD) member” must be defined. Octel 200/300 S.4.1 PB60019-01...
Page 799 Misc. Trunk Restriction Grp. 6 Outward Misc. Trunk Restriction Grp. 7 Terminal to Terminal Misc. Trunk Restriction Grp. 8 Termination Toll Restriction Code Restriction Level: Facility Restriction Level: Bearer Capability: ISDN Routing: Page 2 of 2 <endmask> PB60019-01 Octel 200/300 S.4.1...
Page 800 12.3B-6 Integration Volume 2. TO DEFINE ACTUAL OCTEL 200/300 EXTENSIONS CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add Last Service Request Number: Date: State: W Extension No: (DPEXT) Analog? n Set Type: 7405D Class of Service: DPCOS This ext hunts to ext no:...
Page 801 AT&T System 85/Definity G2 Adaptive Integration with APIC 12.3B-7 CSM Release V4 Sys85:R2L4 CON: PATH:tcm:admin:extension:add User Name: D-(DPEXT) OCTEL 200/300 Location: Room: Electronic Mail Address: Supervisor’s Name: Organization No.: Auth Code: Page 3 of 4 CSM Release V4 Sys85:R2L4 CON:...
Page 802 02 are exactly as shown above. Delete button assignments 03 through 07. Program the Set ID to be the same as the extension number of the first Octel 200/300 port, followed by a “D”. For example, if the first Octel 200/300 port is “2401,” the Set ID would be “2401D.”...
Page 803 5. TO DEFINE A DUMMY TRUNK GROUP CSM Release V4 Sys85:R2L4 CON: PATH:fm:admin:trk-grp:add (TGRP) Trunk Group No.: Dial Access Code: Trunk Type: Signaling Type: Page 1 of 3 The trunk type must be 6 (Special Queueing). PB60019-01 Octel 200/300 S.4.1...
Page 804 Under the field “Queuing Trunk Group,” only 1 trunk group can be defined per ACD (UCD) group. When you define an ACD (UCD) group “Supervisor Extension No.,” the System 85 automatically assigns that extension number as a Member 0 of the ACD split. Octel 200/300 S.4.1 PB60019-01...
Page 805 No. Extn Extn No. Extn 0 (DPEXT#1) 1 (DPEXT#2) 2 (DPEXT#3) 3 (DPEXT#4) Page 1 of 1 <endmask> Add ACD (UCD) members to assign the balance of the Octel 200/300 ports to the ACD (UCD) hunt group. PB60019-01 Octel 200/300 S.4.1...
Page 806 CSM Release V4 Sys85:R2L4 CON: PATH: tcm:admin:vdn-add Vector Directory Number:(ACDVDN) Class of Service:DPCOS Name:A-(ACDVDN) OCTEL 200/300 Vector Number:ACDVEC Page 1 of 1 <endmask> The Vector Directory Number must be a valid unused extension in the System 85. Octel 200/300 S.4.1...
Page 807 Page 1 of 2 The Vector features shown above perform an unconditional queuing to the Octel 200/300 hunt group. Call Vectoring has many features and may allow the customer many different ways of handling the ACD (UCD) hunt group. See System 85 documentation for more information on Call Vectoring.
Page 808 10. TO ASSIGN THE CALL VECTOR TO THE VECTORING DIRECTORY NUMBER CSM Release V4 Sys85:R2L4 CON: PATH: tcm:admin:call-vectoring:add Vector Number: (ACDVEC) Vector Measured Console Return Call Directory No. Message Char. Indicator -−−−−−−−−−−−− −−−−−−−− −−−−−−−−−−−− −−−−−−−−−−−− (ACDVDN) / / / Page 1 of 1 <endmask> Octel 200/300 S.4.1 PB60019-01...
Page 809: Chapter 13 Northern Telecom Adaptive Integration With Npic
........... . 13-17 Configuring Adaptive Integration on the Octel 200/300 ......
Page 811: Chapter 13 Northern Telecom Adaptive Integration With Npic
LEDs) is available to the message server. This information includes the following: The trunk group or ANI number of external calls that have been directed to the Octel 200/300 for primary answering The trunk group/ANI number and the original called extension of external calls that have been...
Page 812 Direct Calls From External Trunks If the call comes in on a trunk, the M1 PBX provides the Octel 200/300 with the trunk access code (or the associated ANI number, if ANI is turned on in the switch and the Central Office) as the source of the call.
Page 813 Direct Internal Calls A person can call the Octel 200/300 directly to enter a mailbox, to send a Quick Message, or if configured to support calling across the network, to make a network call. The Octel 200/300 recognizes these calls as internal, because the display shows the calling extension.
Page 814 13-4 Integration Volume The Octel 200/300 answers the call, prompts the caller with the status of the extension, and offers messaging and call processing options. If the caller is using an extension with a valid mailbox number and leaves a message, the mailbox number associated with that extension is attached to the caller’s message.
Page 815 Hardware Requirements Each port to be supported in the Octel 200/300 requires a port on the Northern Telecom switch that is capable of supporting a 2616 telephone set with a display module. It is recommended that the 16 digital telephone ports be distributed across multiple Northern Telecom cards and across multiple loops in the M1 for improved performance and enhanced reliability.
Page 816 Route Datablock. Change each trunk member and put the Octel 200/300 pilot number in the ATDN (auto-terminate directory number). All the incoming CO trunks to be answered by the Octel 200/300 must be autoterminated to the Octel 200/300. For a hunt group configuration, the number used for autoterminate is either the extension of port 1 or of port 2 in the hunt group.
Page 817 Octel 200/300 for screened transfers. Look at CFNA and DFNA for number of ring cycles. Three ring cycles is the minimum required for the Octel 200/300 message server, so the minimum on the PBX should be 4.
Page 818 Following is an example of a four-port Octel 200/300 hunt group where 300 through 303 are port extensions and 600 is the attendant’s extension for the overflow. The pilot number of this hunt group is 300.
Page 819 FBD is for call forward busy denied. Although hunting (HTA) takes precedence over FBA/FBD, this parameter should be set to DENIED . HTA and FNA do not apply for sets configured For some M1 installations, these capabilities must be specifically configured for each Octel 200/300 port extension by the COS. PB60019-01 Octel 200/300 S.4.1...
Page 820 Make set busy 07−12 Message indication key Message cancellation key Table 13-2 M1 Extension Configuration Commands for ACD Group Key # Command Description 2602 2175 4158 02−05 Make set busy 07−12 Message indication key Message cancellation key PB60019-01 Octel 200/300 S.4.1...
Page 821: M1 (2616) Keyboard Layout
Northern Telecom Adaptive Integration with NPIC 13-11 Figure 13-1 M1 (2616) Keyboard Layout PB60019-01 Octel 200/300 S.4.1...
Page 822 M1 should be programmed not to forward internal calls on a busy condition. Internal callers can then use the camp-on feature, but will not have call coverage by the Octel 200/300 when busy. External callers will continue to receive call coverage on busy.
Page 823 If new trunk groups are to be answered by the Octel 200/300 and are not programmed to autoterminate, do that now. Answer YES to the autoprompt of the route Data Block...
Page 824 CFNA = CFNA HUNT = BUSY XFER = TRF Establish Octel 200/300 port extensions: Configure the ports in an ACD or a terminal hunt group with the last extension in the hunt group specified as the overflow extension. Do not included ports configured to support message waiting.
Page 825 13-15 Make changes to Customer Telephones: Program phones that require secondary answering to forward on a no-answer and hunt on busy conditions to the Octel 200/300 hunt group (See note in section 1.3, Incoming Trunks). Set the prompts as follows:...
Page 826 Integration Volume 13.4 OCTEL 200/300 CONFIGURATION This section describes the external and internal changes that must be made to the Octel 200/300 configuration for both message waiting indication and called party identification. Refer to the Product Description volume, General Description chapter, for general sizing considerations and capacity information and to the Configuration volume for additional information.
Page 827 Preparing the Octel 200/300 Before configuring the Octel 200/300 for adaptive integration, complete the following and place a check mark in the n column: Command List the database. Highlight areas where changes are ____ .L ALL...
Page 828 COS Attribute 58 — DO NOT USE THIS PORT FOR INTEGRATION Assign this COS attribute to those Octel 200/300 ports used in special applications that do not require integration. These ports would be supported by standard line cards rather than the NPIC cards.
Page 829 Modify System Parameter 45 to be NONE System Parameter 46 — SYSTEM-RELOAD CANCEL-FORWARD STRING Modify System Parameter 46 to be NONE. System Parameter 77 — PBX PROVIDES MOMENTARY DISCONNECT Modify System Parameter 77 to be YES. PB60019-01 Octel 200/300 S.4.1...
Page 830 Modify System Parameter 117 to be 5. This gives additional time, if needed, to receive the call record from the PBX. The Octel 200/300 normally answers the call at one ring when receiving a call record from the NPIC. This system parameter provides a fail-safe mode of operation.
Page 831 Northern Telecom Adaptive Integration with NPIC 13-21 Octel 200/300 Configuration Checklist Use the checklist for configuring the Octel 200/300 message server. The message server command is listed. When each step is completed, put a check mark in the n column: Configuration Step...
Page 832 Octel 200/300. These tests verify that NPIC Adaptive Integration works correctly with the PBX. Some of the tests are made before the Octel 200/300 is connected to the PBX. Always check the PBX for correct operation after any changes are made to the system.
Page 833 1. INITIAL SETUP OF PORT CONNECTION FOR EACH TEST Before connecting the 25-pair cables to the back of the Octel 200/300, connect phone C to the jack position of the modular adapter of each Octel 200/300 port extension being tested. Starting with port 1, Connect the modular adapter to the 25-pair cable associated with the configured slot.
Page 834 Answer the call. Hang up phone B and phone C. 5. PBX FORWARD ALL CALLS TEST Use this test to verify that an extension can forward all calls to the Octel 200/300 access number. Set phone A to forward all calls to coverage.
Page 835 Answer phone C. Hang up phone B and phone C. 6. MESSAGE WAITING INDICATOR TEST (For installations using the Octel 200/300 to control message-waiting indicators) Use this test to verify that a message-waiting indicator can be set and cleared using the MIK/MCK feature codes programmed.
Page 836 This section describes the procedure for installing the NPIC board. Reconnect the 25-pair cable to the Octel 200/300. The NPIC can be configured in slots A1−A6 in the Octel 200, and in slots A1−A11 in the Octel 300. The connectors P1 through P11 on the Octel 200/300 use a 50-pin male telco connector. Refer to the Installation and Maintenance volume, Installation chapter, for the Northern Telecom NPIC pin assignment chart.
Page 837 Northern Telecom Adaptive Integration with NPIC 13-27 Make any changes to cross-connections before the integration card is installed in the Octel 200/300. Cross-connecting integration links when the integration card is installed could result in damage to Caution! the integration card.
Page 838 M1 coverage paths for forwarding on RNA. 2. TESTING THE Octel 200/300 NPIC PORTS Use this test to verify that all PBX port extensions are connected to the correct Octel 200/300 ports. On the Octel 200/300 terminal, at the @ prompt, enter and select 1.
Page 839 Octel 200/300 and hang up phone A. 5. INTERNAL CALL TO A BUSY EXTENSION Use this test to verify that the Octel 200/300 correctly processes a call forwarded from a busy extension. Take phone B off-hook so that it appears busy.
Page 840 Does the Octel 200/300 answer with the greeting configured for the trunk? Determine the cause, and correct the problem before continuing. b. Call the extension of phone B. Does the Octel 200/300 respond with “Thank you, just a moment. . .” Does phone B start ringing? Determine the cause, and correct the problem before continuing.
Page 841 From phone A, call out and back in on a trunk that autoterminates at the Octel 200/300. When the Octel 200/300 answers, let the system time out; do not enter any digits. d. Does the Octel 200/300 transfer the call to the intercept position that was configured for this trunk group? Determine the cause, and correct the problem before continuing.
Page 843 ......... . 14-11 ICU Port Settings for Voice Mail Integration with the Octel 200/300 ....
Page 845 MD110 Adaptive Integration 14−1 14.1 MD110 INTEGRATION OVERVIEW This chapter explains the MD110 and Octel 200/300 message server configuration requirements and testing procedures for correct operation of the MD110 adaptive integration. The integration between the message server and the MD110 is through an RS−232 serial data link. The connection is made to either an ICU or ICU2 card in the MD110.
Page 846 Refer to the Adaptive Integration Call Processing section, in this chapter, for more detailed information regarding how specific types of calls are handled. Octel 200/300 S.4.1 PB60019-01...
Page 847 Direct Internal Call from Operator 89 = Clear Voice-Mail Port 91 = Forwarded Internal Call No Answer 92 = Forwarded Internal Call Busy 94 = Forwarded External Call No Answer 95 = Forwarded External Call Busy PB60019-01 Octel 200/300 S.4.1...
Page 848 As a further option, the message server may be configured to give the caller the choice of overriding the automatic transfer and leaving a message. Refer to the Feature Description volume, Customizing Mailbox Features chapter, Personal Assistance section. Octel 200/300 S.4.1 PB60019-01...
Page 849 83 is the command type which the message server uses to identify this call as a forwarded internal call. D is the calling party’s extension. T is the called party’s extension. V is the voice mail port number of the port receiving the call. PB60019-01 Octel 200/300 S.4.1...
Page 850 03 is the command that the MD110 uses when the message server update is complete. <STX>06<CR> <LF> 06 is the command that indicates that message waiting indication is ON. <STX>07<CR> <LF> 07 is the command that indicates that message waiting indication is OFF. Octel 200/300 S.4.1 PB60019-01...
Page 851 The data link is out of operation — check all connections. Once connections are verified, test to see if information can successfully be sent or received over the link using a serial terminal. Place test calls and use MON2 command to monitor the message server. The MD110 has a configuration problem. PB60019-01 Octel 200/300 S.4.1...
Page 852 14.3 MD110 REQUIREMENTS This section is a guideline to setting up a Octel 200/300 with MD110 and can be used as a supplement for technicians and field support maintenance personnel. It is not meant to be a replacement for any product related documents and is not a substitute to formal training of technicians.
Page 853 BC 5.3 Message Waiting Lamp over DDNSS/APNSO BC 6.2.2 Channel Associated Signaling (CAS) functionality for BC 7.1 the message server If commands and parameters vary in different BC releases, they are specified in the Ericsson MD110 documentation. PB60019-01 Octel 200/300 S.4.1...
Page 854 In the following example, ITYPE for analog extension for release BC 5.3 is 8. <EXTEI:DIR=4501&&4504,TYPE=EL6,EQU=2−1−13−00,TRAF=03151515,SERV+00001000, CDIV=0015,ITYPE=8 In the following example, ICAT for analog extension for release BC 6, BC 7, BC 8, and BC 9 is 0018. <EXTEI:DIR=4501&&4504,TYPE=EL6,EQU=2−1−13−00,TRAF=03151515,SERV=00001000, CDIV=00015,ICAT=0018; Octel 200/300 S.4.1 PB60019-01...
Page 855 200/300 massage server ports in the hunt group. Examples: Octel 200 (32-port cabinet and 16-port cabinet) Configure the ports with voice mail port numbers from 1 to 48. Since each message server requires its own ICU link, assign the first 32 voice mail port numbers to the 32-port system’s ICU link and the last 16 voice mail port numbers to the 16-port system’s ICU link.
Page 856 MD110 uses to identify that port to the message server. If this is not a collocated system, assign each port’s voice mail port number to be the same as its message server port number. Octel 200/300 S.4.1 PB60019-01...
Page 857 If the MD110 restarts, message waiting indication status may be lost. If this happens, the MD110 has a configuration terminal command that can be used to initiate a message waiting indicator update manually. PB60019-01 Octel 200/300 S.4.1...
Page 858 MD110 extensions. Make sure that the Adaptive Integration feature (SW-X0031) @L F is installed. To configure the Octel 200/300 Adaptive Integration to work with MD110, changes to the COS, able, able, and the able must be made in UPDATE. The...
Page 859 RECONNECT AFTER NO ANSWER: RECONNECT AFTER BUSY: RECONNECT AFTER FAST BUSY: TRANSFER COMPLETE CODE: NONE If the MD110 reconnect codes are other than “F,” these system parameters must be altered prior to operating the message server. Contact PB60019-01 Octel 200/300 S.4.1...
Page 860 Modify System Parameter 85 to be F System Parameter 99 — RINGBACKS BEFORE ANSWERING CX PORT Modify System Parameter 99 to be 3 System Parameter 100 — RINGBACKS BEFORE ANSWERING MX PORT Modify System Parameter 100 to be 1 Octel 200/300 S.4.1 PB60019-01...
Page 861 SPACE (1). Set this PORT NUMBER FOR CALL RECORDS TO FIRST PORT. value to the voice mail port number assigned in the MD110 configuration to port 1 of the message server. The default value is 1. PB60019-01 Octel 200/300 S.4.1...
Page 862 Test. TEST to ensure that MWI and/or CPI are operational. Refer to the next section for the testing procedure. Application Delays. Application delays may need to be changed to handle internally covered calls. Call your technical support center for assistance. Octel 200/300 S.4.1 PB60019-01...
Page 863 Set to 0, if the MD-110 sends call records after answer. Modify System Parameter 117 — RINGBACKS BEFORE .M SYS 117 ANSWERING AX PORT Set to 3 if the MD-110 sends call records before answer. Set to 0 if the MD-110 sends call records after answer. PB60019-01 Octel 200/300 S.4.1...
Page 864 When you exit after making the necessary changes, UPDATE the message server prompts: FOR CHANGES TO TAKE EFFECT, SYSTEM MUST BE RESTARTED. Restart the system. Test to ensure that message waiting notification and/or called party identification are operational. Octel 200/300 S.4.1 PB60019-01...
Page 865 During the testing, the trunk will need to be reconfigured to ring directly into one of the test extensions. Quantity Terminal/Teleprinter connected to the message server Hard copy of the Octel 200/300 message server and MD110 1 each database Extensions for testing, in addition to the port extensions.
Page 866 NO ® Correct the problem before continuing. b. Hang up phone A without dialing Does the message server port 1 hang up immediately? NO ® Correct the problem before continuing. Repeat Steps A and B for each of the message server ports. Octel 200/300 S.4.1 PB60019-01...
Page 867 From phone A, call outside of the MD110 and back in on a trunk that auto-terminates to the message server. Does the message server answer with the company greeting? NO ® Determine the cause and correct the problem before continuing. PB60019-01 Octel 200/300 S.4.1...
Page 868 Activate busy diversion for phone B. Take phone B off-hook so that it appears busy. b. From phone A, call outside of the MD110 and back in on a trunk that auto-terminates to the message server. Octel 200/300 S.4.1 PB60019-01...
Page 869 Dial the extension of phone B. Does the message server respond with the prompt, “Thank you. Just a moment”? After a short interval, does the message server respond with, “Extension EXT-B is unavailable. Please leave a message at the tone”? PB60019-01 Octel 200/300 S.4.1...
Page 870 NO ® Determine the cause and correct the problem before continuing. You may prefer to use the Quick Message feature to leave a message for phone B instead of following the instructions of step d and step e. Octel 200/300 S.4.1 PB60019-01...
Page 871 NO ® Determine the cause and correct the problem before continuing. You may prefer to use the Quick Message feature to leave a message for phone B instead of following the instructions of Step D and Step E. PB60019-01 Octel 200/300 S.4.1...
Page 872 Does the message server respond with “One message will be erased”? Press to exit the system. Does the message server respond with “Good-bye”? NO ® To any of the above, determine the cause and correct the problem before continuing. Hang up phone B. Octel 200/300 S.4.1 PB60019-01...
Page 873 Received call information form PBX over RS-232C with invalid port number RS-232C MW UPDATE Received UPDATE MESSAGE WAITING command from PBX over RS-232C RS-232C MW VERIFICATION Received MESSAGE WAITING VERIFICATION command from PBX over RS-232C RS-232C DIAGNOSTIC RESPONSE Sent Diagnostic response to PBX over RS-232C PB60019-01 Octel 200/300 S.4.1...
Page 875: Chapter 15 Dpnss Integration
15.2 Octel 200/300 Message Server Configuration ..........
Page 877 Adaptive Integration chapter. Refer to the configuration notes for specific PBX integrations related to DPNSS switches. With DPNSS integration, one digital pathway between the PBX and the Octel 200/300 message server transmits both call information and voice communication. The pathway is provided by a 2- MB, 32-time-slot digital link from the PBX to the E1−DTIC card: the first time-slot, time-slot 0, is for...
Page 878 With common channel signalling, a ring-no-answer is defined either by a negative acknowledgment from the PBX or by a time-out waiting for acknowledgment. The value of the time-out is determined as follows: Octel 200/300 S.4.1 PB60019-01...
Page 879 Called-party identification features, where the system forwards the call to personal greeting (internal and external) for the following: All calls Ring-no-answer Busy Automated attendant Outcalling Multiple return-to-operator Personal greeting of original called party on multiple-call forward Direct call (Quick logon) PB60019-01 Octel 200/300 S.4.1...
Page 880 To configure the Octel 200/300 message server to work with a PBX, you must make changes in UPDATE to the System Parameter Table and the Slots Table. The following explains the type of changes that might be required.
Page 881 Set the DPNSS priority X/Y to the opposite of the PBX setting; that is, if the PBX channel is set to X, the channel on the E1 should be set to Y. PB60019-01 Octel 200/300 S.4.1...
Page 882 15-6 Integration Volume SLOT CARD TYPE PORT EXTENSION# MODE OUTCALL TEST DTC17−DPNSS LSP table : DPNS_GPT PRIMARY SYNC RECEIVER OF CLOCK Octel 200/300 S.4.1 PB60019-01...
Page 883 DPNSS Integration 15-7 15.3 DTIC INSTALLATION The E1-DTIC card can be configured in slots A1−A6 in the Octel 200 message server and in slots A1−A11 in the Octel 300 message server. Refer to the Installation and Maintenance volume, DTIC Card chapter for information about the DTIC.
Page 884 (do not enter any digits). Does the message server transfer the call to the appropriate intercept position? NO ® Determine the cause and correct the problem before continuing. Octel 200/300 S.4.1 PB60019-01...
Page 885 MAKE DIRECT INTERNAL CALL TO THE OCTEL 200/300 This test verifies that the Octel 200/300 processes a direct internal call correctly. From phone A, call the extension number for Octel 200/300 access. Does the message server answer with “To enter your mailbox press pound...”? NO ®...
Page 886 Hang up phone B. Is phone B’s message-waiting indication turned OFF? NO ® Determine the cause and correct the problem before continuing. It could take the message server several seconds to turn message-waiting indication OFF. Hang up phone B. Octel 200/300 S.4.1 PB60019-01...
Page 887 DPNSS DTIC. @conn 4 Connecting to DTC17−DPNSS in slot 4 DPNSS> To exit from DPNSS card status, at the DPNSS> prompt, enter EXIT Enter You are disconnected from the card and returned to the @ prompt. PB60019-01 Octel 200/300 S.4.1...
Page 888 IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL DWN DWN 16−30 Virtual The abbreviations for the states are described in Table 16-1. Octel 200/300 S.4.1 PB60019-01...
Page 889 In addition to the state of each DPNSS channel, you can view the trace activity to help resolve problems: 1. Log on to the DTIC. 2. If you want to trace new events as they happen, at the DPNSS> prompt enter PB60019-01 Octel 200/300 S.4.1...
Page 890 CCS Layer 4 RX, which shows the protocol packets received from the message server CCS Layer 4 TX, which shows the protocol packets sent to the message server Message type. Refer to Table 1−2 for a list of message types. Octel 200/300 S.4.1 PB60019-01...
Page 891 Destination address. In a service request the last sequence is the destination address. A destination address is not always necessary in a trace activity. In the event field, the trace displays clearing and rejection information, as shown in Table 15-3. PB60019-01 Octel 200/300 S.4.1...
Page 892 The first DPNSS trace is an example of a trace for an incoming caller that is answered by the message server. In the trace, layer 3 refers to PBX receiving and transmitting activities, and layer 4 refers to CPU or message-server activities. Explanations of each of the message packets follows the screen. Octel 200/300 S.4.1 PB60019-01...
Page 893 Complete (ISRC) message from the PBX. This is a direct call from extension 79060101. The pilot number for the message server is 4000, which appears at the end of the message packet in the destination address. PB60019-01 Octel 200/300 S.4.1...
Page 894 CI/RM Cause:BY *1#*50*79060105#*58*AM*1028 4000# 16153047.86 30 CCS Layer 3 TX EEMC *61# 16153054.06 30 CCS Layer 3 RX CI/RM Cause:CT 16153054.26 30 CCS Layer 4 TX DISCONNECTCause:02 Raw:48 16153054.67 30 CCS Layer 3 TX CI/RM Cause:CT Octel 200/300 S.4.1 PB60019-01...
Page 895 {16B = Call Back When Free − Call Set−Up(Delayed)} {17B = Call Back When Next Used−Request} {18B = Class Of Service} {19 = Loop Avoidance} {20 = Executive Intrusion − Prior Validation} {21 = Executive Intrusion − Request} PB60019-01 Octel 200/300 S.4.1...
Page 896 {52 = } {53 = Diverted − Externally} {54 = Reject} {55 = Acknowledge} {56 = Send Next} {57A = DASS 2 − Service Indicator Code} {58 = Non−Specified Information} {60B = Hold Request} {61 = Reconnected} Octel 200/300 S.4.1 PB60019-01...
Page 897 {93B = Call Distribution − Unlinked} {94 = Signal Not Understood} {95 = Service Unavailable} {96 = Recall Rejected Signal Not Understood} {97B = Call Distribution−Call Set Up} {98 = Ignored−Signal Not Understood} {99 = Ignored−Service Unavailable} {100 = Textual Display} PB60019-01 Octel 200/300 S.4.1...
Page 898 {132 = Night Service − Rediverting} {133 = Night Service − Rediverted} {134 = Night Service − Deactivated} {135 = Queue Information} {136 = Queue Priority} {137 = Swap − Validation} {138 = Swap − Rejected} {139 = } Octel 200/300 S.4.1 PB60019-01...
Page 899 {171B = Call Back Messaging−Request} {172B = Call Back Messaging−Cancel} {173 = Network Address Extension−Calling/Called Identity Complete} {174 = Network Address Extension−Calling/Called Identity Incomplete} {175 = } {176 = Add−On Conference−Cleardown Conference} {177 = Add−On Conference−Party Index} {178 = } PB60019-01 Octel 200/300 S.4.1...
Page 900 {196B = Non−Looped Back Test − Test Request} {197B = Non−Looped Back Test − Sequence Complete} {198B = Non−Looped Back Test − Result} {199 = Autoanswer} {200 = Hands−Free − Activated} {201 = Hands−Free − Deactivated} {202B = Executive Intrusion − Withdraw} Octel 200/300 S.4.1 PB60019-01...
Page 901: Chapter 16 Isdn Integration
16.2 Octel 200/300 Message Server Configuration ..........
Page 903 This feature provides message-waiting indication and called-party identification. Refer to the Adaptive Integration chapter for more general information about Adaptive Integration. With ISDN integration, one digital pathway between the PBX and the Octel 200/300 message server transmits both call information and voice communications. The pathway is provided by a 2 MB, 32-channel digital link from the PBX to the DTIC-E1 card.
Page 904 Message waiting indication features Called-party identification features, where the system forwards the call to personal greeting (internal and external) for the following: All calls Ring-no-answer Busy Automated attendant Outcalling Multiple return-to-operator Direct call (Quick logon) Octel 200/300 S.4.1 PB60019-01...
Page 905 Refer to the Configuration and Installation and Maintenance volumes for details about configuring the message server. To configure the Octel 200/300 message server to work with a PBX, you must make changes to UPDATE in the System Parameter Table and Slots Table. The following sections explain the type of changes that might be required.
Page 906 Extension #. Set the extension number to N. No extension numbers are set. SLOT CARD TYPE PORT EXTENSION# COS MODE OUTCALL TEST SYS −−−− −−−−−−−−−− −−−− −−−−−−−−−− −−− −−−− −−−−−−− −−−− −−− DTC17−ISDN LSP table: EUROISDN Octel 200/300 S.4.1 PB60019-01...
Page 907 16.3 INSTALLING THE DTIC The DTIC-E1 can be configured in slots A1−A6 in the Octel 200 message server and in slots A1−A11 in the Octel 300 message server. The connectors on the Octel 200/300 use a 50-pin male telco connector.
Page 908 (do not enter any digits). Does the message server transfer the call to the appropriate intercept position? NO ® Determine the cause and correct the problem before continuing. Octel 200/300 S.4.1 PB60019-01...
Page 909 MAKE DIRECT INTERNAL CALL TO THE OCTEL 200/300 This test verifies that the Octel 200/300 processes a direct internal call correctly. From phone A, call the extension number for Octel 200/300 access. Does the message server answer with “To enter your mailbox press pound...”? NO ®...
Page 910 Hang up phone B. Is phone B’s message-waiting indication turned OFF? NO ® Determine the cause and correct the problem before continuing. It could take the message server several seconds to turn message-waiting indication OFF. Hang up phone B. Octel 200/300 S.4.1 PB60019-01...
Page 911 IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL Layer 4 Channel States: IDL IDL IDL IDL DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN DWN PB60019-01 Octel 200/300 S.4.1...
Page 912 Third party call active Disconnect in progress Message waiting indication in progress Call transfer in progress ISDN Trunk Status The command STATUS TRUNK displays the current state of the ISDN trunk. An example of an ISDN trunk status screen. Octel 200/300 S.4.1 PB60019-01...
Page 913 CCS Layer 3 RX, shows protocol packets received from the PBX CCS Layer 3 TX, shows protocol packets sent to the PBX CCS Layer 4 RX, shows commands received from the message server CCS Layer 4 TX, shows event sent to the message server PB60019-01 Octel 200/300 S.4.1...
Page 914 This version of ISDN does transfer with a single channel. The first call is put on hold and a call is made to the requested extension. That extension does not answer so the outgoing call is dropped and the held call is retrieved so the caller can leave a message. Octel 200/300 S.4.1 PB60019-01...
Page 915 01131712.53 01 CCS Layer 3 RX Release: Normal call clearing 01131712.60 Dc CCS Layer 3 TX Release Complete: 01131712.68 01 CCS Layer 3 TX Release: Normal call clearing 01131712.73 01 CCS Layer 3 RX Release Complete: Normal call clearing PB60019-01 Octel 200/300 S.4.1...
Page 917: Chapter 17 Qsig Integration
17.2 Octel 200/300 Message Server Configuration ..........
Page 919 This chapter must always be used in conjunction with the Configuration Note, which contains specific information about the integration. While QSIG is an ISO standard protocol that could allow the Octel 200/300 to integrate with various switches, at the time of this writing, the only switch that has implemented the necessary Supplementary Services to allow a satisfactory level of functionality in the integration is the Lucent Definity G3.
Page 920 Port Information Table. Message waiting outcalls (on-site and off-site) use the value defined in Index 8 of the Information Table associated with the calling mailbox COS, while transfers (from the auto-attendant or to personal assistance) use Index 7 of that table. Octel 200/300 S.4.1 PB60019-01...
Page 921 Called-party identification features, where the system forwards the call to personal (or system) greeting for the following: All calls Ring-no-answer Busy Prompt if no greeting is recorded Automated attendant Outcalling Multiple return to operator Direct call (Quick logon) ANI for calling party identification, where applicable PB60019-01 Octel 200/300 S.4.1...
Page 922 17−4 Integration Volume 17.2 OCTEL 200/300 MESSAGE SERVER CONFIGURATION To use QSIG integration, you must make several changes to the Octel 200/300 configuration. Changes are made in UPDATE. This sections explains the type of changes that might be required. Refer to the Configuration and Installation and Maintenance volumes for more details about configuring the message server.
Page 923 Information Table Index 7 multiplied by the Average Ring Time Average Ring Time = Ringback ON time (the sum of Application Delay 53 + 54) plus Ringback OFF time (the sum of Application Delay 55 + 5 divided by 2 PB60019-01 Octel 200/300 S.4.1...
Page 924 Double Interrupted Ringback Minimum Tone Off Long Period Double Interrupted Ringback Maximum Tone Off Short Period Double Interrupted Ringback Minimum Tone Off Short Period Refer to the Installation and Maintenance volume, Maintenance Commands chapter for a description of these application delays. Octel 200/300 S.4.1 PB60019-01 Octel 200...
Page 925 17.3 INSTALLING THE DTIC The DTIC-E1 can be configured in slots A1 − A6 in the Octel 200 and in slots A1 − A11 in the Octel 300. The P1 − P11 connectors on the Octel 200/300 use a 50–pin male telco connector. The Amphenol to BNC Converter fits into that connector and provides a way to attach the twisted pair (120 ohm) or coax cable (75 Ohm) from the message server to the switch.
Page 926 (do not enter any digits). Does the message server transfer the call to the appropriate intercept position? NO ® Determine the cause and correct the problem before continuing. Octel 200/300 S.4.1 PB60019-01...
Page 927 MAKE DIRECT INTERNAL CALL TO THE OCTEL 200/300 This test verifies that the Octel 200/300 processes a direct internal call correctly. From phone A, call the extension number for Octel 200/300 access. Does the message server answer with “To enter your mailbox press pound...”? NO ®...
Page 928 Hang up phone A. Is phone A’s message waiting indication turned OFF? NO ® Determine the cause and correct the problem before continuing. It could take the message server several seconds to turn message waiting indication OFF. Hang up phone A. Octel 200/300 S.4.1 PB60019-01 Octel 200...
Page 929 IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL IDL PB60019-01 Octel 200/300 S.4.1...
Page 930 −−−−−−− Timeslot 16 Signaling Channel Status −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− Mode: If the receive state is “Loss of Signal”, try reversing the cables connecting the DTIC to the PBX. If problem persists, replace cable and/or work with the PBX vendor to resolve. Octel 200/300 S.4.1 PB60019-01 Octel 200...
Page 931 The following two examples of trace activities provide a call scenario, the associated output from the CPT trace, and the output from the card level trace reached by connecting to the DTIC (@CO X, where X = DTIC card channel number). PB60019-01 Octel 200/300 S.4.1...
Page 932 11/18/99 17:40:14 024 QSIGMSG XPAR_SENT 030 11/18/99 17:40:15 024 PORT DISC_FROM chan_030 11/18/99 17:40:15 024 QSIGMSG QSI_DISCO 11/18/99 17:40:15 024 PORT LINE_DROP 003 11/18/99 17:40:15 024 PORT ONHOOK 11/18/99 17:40:15 030 PORT LINE_DROP 003 11/18/99 17:40:15 030 PORT ONHOOK Octel 200/300 S.4.1 PB60019-01 Octel 200...
Page 933 Release Complete: 18174011.36 30 CCS: CCS−−>CS que code:0f data:01 ae af b0 b1 b2 b3 18174011.46 24 CCS: CCS−−>CS que code:0f data:01 ae af b0 b1 b2 b3 qsig> cl tra Trace Queue cleared and unfrozen qsig> PB60019-01 Octel 200/300 S.4.1...
Page 934 11/18/99 15:01:00 011 PORT LINE_DROP 003 11/18/99 15:01:00 011 MSG SENT 8351 11/18/99 15:01:00 PUT_IN FWD_BSY 7820 8351 11/18/99 15:01:00 011 PORT ONHOOK 11/18/99 15:01:08 024 QSIGMSG MSGWAIT 7820 11/18/99 15:01:09 024 QSIGMSG MW_RESULT ON 7820 Octel 200/300 S.4.1 PB60019-01 Octel 200...
Page 935 18150026.42 24 CCS Layer 3 RX Connect: Return Result 18150026.46 24 CCS Layer 3 TX Connect Ack: 18150026.50 24 CCS Layer 4 TX MWI ACK 0001 0001 0000 BDBD 18150026.55 24 CCS Layer 3 TX Release: Normal call clearing qsig> PB60019-01 Octel 200/300 S.4.1...
Page 937 12−6 Definity G3 configuration ROUTE Table COR, 7.1-9 collocated analog networking, 10−7 coverage paths, 7.1-20 remote analog networking, 10−4 hunt group, 7.1-19 naming conventions, 7.1-8 Adding features. See Electronic feature port extensions, 7.1-17 delivery/removal PB60019-01 Octel 200/300 S.4.1...
Page 938 12-18 forwarded external calls, 7.3-4 scripted or sequential mailbox, 12-16 forwarded internal calls, 7.3-5 single greeting, 12-14 configuration requirements, 7.3-6 Backup procedures, 12-3–12-21 hardware requirements, 7.3-6 Basic MIB, digital networking, SNMP, 11B-2 installation, 7.3-25–7.3-41 Octel 200/300 S.4.1 PB60019-01...
Page 939 4-8 transaction types, 7-21 Message Waiting Indication, 4-1 Call Process Trace Log RS-232 interface port, 4-11 AUX, 7A-1 sequential forwarding, 4-4 Event, 7A-1 serial data link. See data link Call processing, MD110, 14−3 PB60019-01 Octel 200/300 S.4.1...
Page 940 6-4 BITTST, 6-10 Network Failure Table, 6-4 CPURGE, 6-10 peg, 8-40 DEX, 6-10 report, 6-4 DKSMAP, 6-10 round trip time for message waiting, 6-4 DSKTST, 6-10 traffic peg, 6-4 FLOPPY, 6-10 CMD PING, 6-28, 11-7 Octel 200/300 S.4.1 PB60019-01...
Page 941 5, 6-6, 6-35 internal modem, 4−17–4−18 network, 6-6 Overture 200/300, 4−26 SNMP manager system, communication with, 6-6 overview, 4−26 system forwarding diagnostic, 6-42 PBX, 4−26 system initialization, 6-42 phone system, 4−26 system status, 6-6, 6-43 PB60019-01 Octel 200/300 S.4.1...
Page 942 Digital Line Card, 2-6 networking, 4−24, 20, 6−24 Digital Network Performance Report, 5-14–5-17, DC power source, DC subassemblies, field wiring, 8−68–8−71 9-48 Digital Networking DC voltage test points, 4−23 Digital Network Performance Report, 5-14–5-17 DCD signal, 4−17 Octel 200/300 S.4.1 PB60019-01...
Page 943 (ASCII) name verification, 8−19–8−22 real-time name problems, 8−64 Namesend feature, 8−13–8−18 uniform numbering plan, 8−3–8−9 configuration, 8−13–8−15 advantages of, 8−4–8−5 network error types and remedies, 8−54 configuring a server to be in, 8−8–8−10 Network Failure Table, 8−53 PB60019-01 Octel 200/300 S.4.1...
Page 944 QSIG, 17−7 Fans, 9-1 DTMF, diagnostic test, 6-35 Fax application processor, 2-7 DTMF In-band Integration, 3-1–3-14 replacement, 9-23–9-24 Adaptive Integration optional software, 3-1 Features configuration tables affected adding. See Electronic feature delivery/removal COS Table, 3-12 Octel 200/300 S.4.1 PB60019-01...
Page 945 Hard Disk Redundancy, 2-16 RS-232C Connector, 2-2 Hard drive status, physical size, 6-33 Serial Integration Card, Meridian 1, 2-9 Hardware system terminal port, 2-1 32-pin teleco connector, Voice 250-i, 2-2 system/voice disk drives, 2-3, 2-5 50-pin teleco connector, 2-2 PB60019-01 Octel 200/300 S.4.1...
Page 946 1-5 procedures, 4−4–4−13 before INSTALL is complete, 1-27–1-32 power requirements, 4−4 exiting and continuing, 1-28 site requirements, 4−4 group fax number, 1-22 required equipment, 4−13 Incoming Call Restriction, 1-19 25-pair cable, 4−26 intercept position, 1-17 Octel 200/300 S.4.1 PB60019-01...
Page 947 LCSTAT command, digital networking, 8−52 DTIC Card, 16-1 Information Table, 16-3 LED, on the LAN card, 11-6 Installing the DTIC, 16-5 LIC. See Line Interface Card message server configuration, 16-3 Line 1, test diagnostics, 6-35 Slots Table, 16-3 PB60019-01 Octel 200/300 S.4.1...
Page 948 11−4 remote analog networking, 2−41, 4−20, 17 sample LIST REPORT command, 5-2 Protocol 2, 4−11 digital networking, 8−65, 8−68 Protocol 4, 9 List Trace Command, 7-8 Protocol 5, 6−11 List Visual Mailbox, command, 2, 6-3 Octel 200/300 S.4.1 PB60019-01...
Page 949 LIST NET DOMAIN command, 8−49 COS attributes, 14−14 LOG command and Call Processing Trace, 8−55 System Parameter indexes, 14−15–14−18 NAMESEND command, 8−15 message waiting indication, 14−1 NAMESTAT command, 8−52 requirements, hardware and software, 14−8 traffic pegs, 8−58–8−61 PB60019-01 Octel 200/300 S.4.1...
Page 950 1-1 PORT STATUS, 6-17, 6-37 ITT 3100 Adaptive Integration, 9-1 Print tone command, 6-17 lamp, 1-1 PRTMAP, 6-17, 6-30 Mitel SX-2000 Adaptive Integration, 10.3-2 RESTART, 6-18 NEAX-2400 Adaptive Integration, 5-1 SDBG, 6-18 SL-1 Adaptive Integration, 6-1 Octel 200/300 S.4.1 PB60019-01...
Page 951 8−19 disable, 6-13 alphabetic (ASCII) name propagation, 8−19 enable, 6-13 alphabetic (ASCII) name verification, 8−19–8−22 external, 4−16–4−17 OctelNet, 9−8–9−9 internal, 4−17–4−18 Names Directory. See DialbyName MODIFY Command, NETWORK SCHEDULE Names propagation, network, 9−9 Table, 13−5 PB60019-01 Octel 200/300 S.4.1...
Page 952 Network Names Table, 9−3 multiple network prefixes per location, 2−35 how to set up, 9−2 network traffic report, 5-17–5-22 how to use Network Names table, 9−3–9−7 overview, 1−1–1−7 NETNAM DELETE command, 9−7 digital, 1−7 Octel 200/300 S.4.1 PB60019-01...
Page 953 12−9 speak times index, INSTALL program, 1-20 network mailbox length, 12−10 Operating Line Voltage, 4−3 number of digits to strip, 12−10 Operating system, command, 4−24 number of digits to strip from self, 12−10 using INSTALL, 12−10 PB60019-01 Octel 200/300 S.4.1...
Page 954 Power failure, 1-9, 2-2 InWATS service, 3-6 Power filter assembly, replacement, 9-31–9-43 trunk hunting group, 3-6 Power line filter, Overture 300, 2-4 trunking, 3-6 Power requirements, 4−4, 4−8 how the Overture 200/300 works with, 3-1–3-4 InWATS service, 3-6 Octel 200/300 S.4.1 PB60019-01...
Page 955 2-13 name to different mailbox, 12-29 shelves, 2-4 network names, 12-31 Power Supply Unit personal distribution list names, 12-36 Octel 200, 9-30 scripted or sequential mailbox, 12-35 Octel 300, 9-31 single greeting, 12-33 Power supply, fuse, 9-30 Prompts...
Page 956 2−43, numbering plan, 2−6–2−11 3−25, 4−25 NUMBERING PLAN Table, 12−2–12−8 verification diagnostic, TEST NET command, NUMBERING PLAN Table form, 3−14–3−15, 3−17, 6−17 11–12, 6−13–6−14 Voicenet, 2−1, 3−1, 4−1 sample, 2−34, 3−15, 4−14, 12, 6−14 Octel 200/300 S.4.1 PB60019-01...
Page 957 RESTART command, 6-18 RIC display phone extensions, 8.1-5 Restore RIC board installation, 8.1-29 all messages, 12-23 software requirements, 8.1-4 all names, 12-25 testing procedure, 8.1-15–8.1-36 command. See Procedures ROLM Integration Card, 2-8 greeting to different mailbox, 12-34 PB60019-01 Octel 200/300 S.4.1...
Page 958 6-4 cable length, 4−14 SL-1 digit display set keyboard layout, 6-8 Centrex, 6-13 SLIC board installation, 6-30 integration error, 8-11 software requirements, 6-5 RS-232C , 2-2 testing, 6-16 connector, 2-28 testing procedure, 6-17–6-35 Octel 200/300 S.4.1 PB60019-01...
Page 959 PR Option: Print Log Files, 7-2 ST Option: Print Status of Log Files, 7-4 Tandeming cases, digital networking, 8−27–8−35 Standard DTMF integration, 1-1–1-4 Telemarketing Line Card, 2-6 Called Party Identification, 1-2 Message Waiting Indication, 1-2 Teleprinter, 4−14 PB60019-01 Octel 200/300 S.4.1...
Page 960 3−17, 6−17 LANSTAT command, 11-8 traffic pegs, 11-10–11-11 TEST SNMP command, 11B-11–11B-12 remote analog networking messages, 11B-11–11B-12 dropped calls, 3−24 Testing network message failures, 2−43–2−44, collocated analog networking, 7−16 3−25–3−26, 4−25 MD110 adaptive integration, 14−22, 15-8, 16-6 Octel 200/300 S.4.1 PB60019-01...
Page 961 UPS. See Uninterruptable power supply hard disk, 2-17 User calling statistics report, 5-25–5-26 Wrist grounding strap, 9-1 User message statistics report, 5-23–5-24 User status detail report, 5-34 USER Table, adding mailboxes auto-incrementing, 1-6 in ranges, 1-6 PB60019-01 Octel 200/300 S.4.1...

This manual is also suitable for:

Octel 300

Avaya Octel 200 Installation And Maintenance Manual

Section 1

Section 2

Chapter 1 Standard DTMF Integration

2 Adaptive Integration

Chapter 2 Adaptive Integration

3 Enhanced Dtmf In-Band Integration

Chapter 3 Enhanced DTMF In-Band Integration

4 Centrex Smdi/Smsi Adaptive Integration

Chapter 4 Centrex SMDI/SMSI Adaptive Integration

5 Neax-2400 Adaptive Integration

Chapter 5 NEAX-2400 Adaptive Integration

6 Northern Telecom Sl-1 Adaptive Integration

Chapter 6 Northern Telecom SL-1 Adaptive Integration

Chapter 7.1 DEFINITY G3 Adaptive Integration

Definity G3 Adaptive Integration

At&T System 75/Definity G1 Adaptive Integration

At&T System 85/Definity G2 Adaptive Integration

Appendix A At&T System 85/Definity G2

Appendix B At&T System 85/Definity G2

Appendix B Contents

Chapter 8.1 ROLM CBX Adaptive Integration

Rolm Cbx Adaptive Integration

Chapter 9 Cortelco Millennium Adaptive Integration

Chapter 10.1 Mitel SX-200 Digital Adaptive Integration

Chapter 11 Meridian 1 Adaptive Integration

Chapter 12.1 Definity G3 Adaptive Integration with APIC

Chapter 13 Northern Telecom Adaptive Integration with NPIC

Chapter 15 DPNSS Integration

Chapter 16 ISDN Integration

Chapter 17 QSIG Integration

Quick Links

Chapters

Related Manuals for Avaya Octel 200

Summary of Contents for Avaya Octel 200