384i Release Notes for Software Version Includes G3 Enhancement Set and Networking. P/N 92000RNT75A Issue 1-0, March 1999 Printed in U.S.A.

Transcription

1 384i Release Notes for Software Version Includes G3 Enhancement Set and Networking P/N 92000RNT75A Issue 1-0, March 1999 Printed in U.S.A.

2 This manual has been developed by Nitsuko America. It is intended for the use of its customers and service personnel, and should be read in its entirety before attempting to install or program the system. Any comments or suggestions for improving this manual would be appreciated. Forward your remarks to: Nitsuko America, Telecom Division 4 Forest Parkway Shelton, CT Attention: Manager, Technical Publications Nothing contained in this manual shall be deemed to be, and this manual does not constitute, a warranty of, or representation with respect to, any of the equipment covered. This manual is subject to change without notice and Nitsuko America has no obligation to provide any updates or corrections to this manual. Further, Nitsuko America also reserves the right, without prior notice, to make changes in equipment design or components as it deems appropriate. No representation is made that this manual is complete or accurate in all respects and Nitsuko America shall not be liable for any errors or omissions. In no event shall Nitsuko America be liable for any incidental or consequential damages in connection with the use of this manual. This document contains proprietary information that is protected by copyright. All rights are reserved. No part of this document may be photocopied or reproduced without prior written consent of Nitsuko America by Nitsuko America. All Rights Reserved. Printed in U.S.A.

3 Release Notes Table of Contents 384i System Software New Features...1 ISDN, BRI: BRI Compatibility Added...1 Transfer: Prevent Recall of Transferred Call...1 Voice Mail: Port Assignment Program Changed to Allow Up to 48 Voice Mail Ports...2 Voice Mail: Queuing...2 Enhancements to Existing Features...2 Caller ID: Remote Log-On Protocol Sent to Voice Mail...2 Handsfree: Automatic Handsfree with Call Coverage and Park Features...2 IDSN, PRI: Channel Information Changed...2 Voice Mail: Networking Voice Mail Requires Circuit Type Software Corrections...3 ACD: Overflow to Voice Mail Has No Answer Supervision...3 Call Forwarding: Beeps with Forwarded Voice Call Intercom Corrected...3 Call Forwarding: Immediate with Both Ringing Programming Can Not Chain Forward...3 Call Forwarding: Extensions within Same Ring Group Cause System Lockup...4 ISDN: Abbreviated Dial Numbers Have No DTMF Receiver...4 ISDN: DID Trunk From ISDN Does Not Forward to VAU or Voice Mail...4 ISDN: Hold and Transfer Used on Outgoing Calls...4 ISDN: Incoming DID and DISA Calls Receive No Dial Tone...4 ITSU-B: Format of Up-Stream Data Changed...5 Networking: Call Could Result in One-Way Conversation...5 Networking: Tandem Trunking Ignores Program with Two Incoming Calls...5 TAPI: Call Transfer From an Even Port Indicates Voice Mail: Answering Machine Emulation Does Not Work With Voice Mail Ports i System Software New Features...7 Enhancements to Existing Features...7 Call Coverage Key: Programmable for Incoming/Outgoing or Just Incoming...7 Software Corrections...7 ISDN: Call Reference Conflict...7 ISDN: Channel ID Information Element Missing...7 ISDN, PRI: Channel Lockup Due to Layer 1 and Layer 2 Errors...7 ISDN, PRI: Incoming Call on Channel 23 Results in Next Outgoing Call Being Rejected...7 Networking: Tie Line Loop Key Flashes Incorrectly on Hold...8 P Command Corrections i System Software New Features...9 Enhancements to Existing Features...9 Conference: Number of Outside Parties Increased...9 Night Service: Automatic Night Service, Program 0401-Item 2 Added...9 Voice Mail: Networking Voice Mail Circuit Type...9 Software Corrections...9 ACD: Agent Recording Feature...9 ACD: Conference Including a 3-ACI Causes Lockup...10 Call Forwarding, Fixed: Extension Rings After Transfer to Voice Mail...10 E911: Alarm Ring Option Bypassed...10 ISDN, BRI: Line Key Seized Results in One-Way Talk Path...10 ISDN, BRI: No SPID or Single SPID Cause CO Problems...10 ISDN, BRI: Overflow to Voice Mail Does Not Work...11 ISDN, PRI: Digital Gain Control Could Result in Data Communications Error...11 Networking: Call in Voice Mail Queue Locks Up...11 Networking: DTMF Receiver Not Cleared After Tie Line on Hold...11 Networking: Tie Line Call Transferred to ACD Master Number Remains on Hold...11 Networking: Voice Mail Call with BGM Enabled Holds T1 Channel...12 Tie Lines: 911 on Wink Start Line Does Not Work...12 Trunk Queuing: System Automatically Redials ARS Buffer Call or i

4 Release Notes Voice Mail: Call in Voice Mail Queue Locks Up i System Software New Features...13 Enhancements to Existing Features...13 ISDN, BRI: Automatic Recovery from DATA LINK FAILURE...13 Software Corrections...13 ARS: Account Codes Dialed Before Number Does Not Work...13 ISDN: Repeat Redial Function Key Does Not Work...13 ISDN: Automatic On-Hook Transfer on ISDN Line Does Not Connect...13 ISDN, BRI: Account Code Does Not Work...13 ISDN, BRI: ARS Does Not Work on BRI Lines...14 ISDN, PRI: Data Communications Error with ATSU Modem i System Software New Features...15 Enhancements to Existing Features...15 E911: Forced Disconnect Follows Timer to Disconnect Call...15 Software Corrections...15 Account Codes: Extension Receiving Transfer Can Enter Account Code...15 ARS: 555 Routing To Long Distance Carrier Does Not Work...15 ARS: Dial Treatment X Fixed...15 E911: Forced Disconnect with VAU Does Not Work...15 E911: PBX Access Code Not Required in ARS Dial Treatment...15 E911: Two Forced E911 Calls Will Not Disconnected Each Other...16 Networking: ISDN Trunk Across Network Does Not Receive Busy Signal...16 Night Service: System Ignores Night Mode Programming i System Software New Features...17 Enhancements to Existing Features...17 Software Corrections...17 Abbreviated Dialing: Only Tenant Group 1 Works Without Preselecting Lines...17 Call Forward: Both Ring Using Voice Mail Port Locks Up Phone...17 Call Forward: Both Ring with Call Coverage Key...17 Conference, Voice Call/Privacy Release: Outside Caller Disconnects Causing Reset...17 Conference, Voice Call/Privacy Release: Program 0405, Timer 9 Not Used...17 Conference, Voice Call/Privacy Release: Reverts to Non-Privacy Mode With Maximum Members...18 Conference, Voice Call/Privacy Release: Reverts to Non-Privacy Mode with Two Parties...18 Directory Dialing: Only Tenant Group 1 Work for Directory Dialing...18 ISDN: Layer 2 Timer T203 Default Changed...18 ISDN: Problem Sending Complete Information Element ( A1H )...18 ISDN, PRI: Data Communications Error Received with PRI ASTU Modem i System Software New Features...19 Enhancements to Existing Features...19 Call Coverage Key: DND and Off-Hook Signaling Programs Followed...19 Caller ID: View Information for Second Call...19 Paging: Combined Paging With a Function Key...19 Park: Extended Park Hold Timer Added...20 Voice Mail: Transferred Calls Will Ring Extensions with Park and Page Before Paging...20 Voice Mail: VAU Plays Announcements to Voice Mail Ports...20 Software Corrections...20 Caller ID: Transferred Calls will Display Caller ID...20 ISDN, PRI: Can Not Make Outgoing Call...20 Loop Keys:...20 Voice Mail: Off-Premise Transfer With Call Screening Receive Call Announce Message...21 ii

5 Release Notes 384i System Software New Features...23 Conference, Voice Call/Privacy Release: Non-Private Line Option Added...23 Enhancements to Existing Features...23 ISDN, PRI: Channel Assignment for Outgoing Calls Now Based on Program Software Corrections...23 Call Forwarding: Follow Me with VAU Reminder Messages Enabled Causes Reset...23 CDTU-B: Multiple DTMF Receivers can Not be Activated i System Software New Features...25 Enhancements to Existing Features...25 E911: Forced Outgoing Dialing Required Entries in Program 2108 and SMDR: Dialed Number Field Increased...25 Software Corrections...26 Account Codes: Digits Dialed After Timer Expired on BRI Calls Not Sent to CO...26 ACD: Voice Mail Could Lockup CO Line...26 E911: 911 on BRI Trunks Other Than in Trunk Group 1 Did Not Reroute...26 E911: Busy Trunk Could Cause Port Lockup...26 E911: Conference Calls Not Dropped with Forced Outgoing Dialing...26 E911: Forced Outgoing Dialing on Barged In Trunk Does Not Dial...26 E911: Forced Outgoing Dialing on Busy Trunk Redials Too Quickly...26 E911: Forced Outgoing Dialing on Hold Calls...27 E911: Forced Outgoing Dialing On Incoming Call Does Not Disconnect...27 E911: Missing or Double Digit Occurs on SLT s Dialing 91x Except E911: Program 0907 Cleared Prevents Extension From Dialing E911: Restricted and Common Restricted Codes Ignored with E E911: Restricted Trunks Will Dial E911: SLT s Cut Thru When Dialing E911: SLT s Dialing Dials Incorrectly...27 E911: SLT s Selecting Trunk From Trunk Group ReRoutes Call...28 E911: SLT s Using Hookflash to Disconnect from Intercom Call Don t Dial E911: T1 PRI or BRI PCB s Must Sync Before E911 Can Dial...28 E911: Tenants 2-4 Have No Trunks, E911 Does Not Dial...28 E911: Using Trunk Access Code or Pressing Busy Trunk Key Does Not Force E ISDN, PRI: Clock Sync Error Could Occur With Internal Clock Selected...28 Toll Restriction: No Toll Restriction if 9 Required for Dialing C.O...28 Voice Mail: Off-Premise Transfer Does Not Work Due to Quick Dialing i System Software New Features...31 Enhancements to Existing Features...31 Software Corrections...31 E911: Account Code Required for 911 When ARS and PBX Access Codes Enabled...31 E911: Account Codes Required With ARS...31 E911: Forced Account Codes Delay 911 Dialing...31 E911: SLT s Placing a 911 Call Do Not Follow Program 0907 Setting...32 E911: SLT s Have Delayed Talk Path With ARS and Forced Account Codes Enabled...32 Documentation Corrections...32 Account Codes: Asterisk Within PBX Access Code Stops Dialing...32 E911: Compatibility i System Software New Features...37 Enhancements to Existing Features...37 Caller ID: Missed Call Redial Now Accepts Up to 12 Digits...37 Software Corrections...37 ACD: ANI Information Not Sent With Pt Command...37 ACD: P7 Command Not Sent If Outside Caller Hung Up First...37 Networking: Can Not Leave a Message Across the Network...37 iii

6 Release Notes iv 384i System Software New Features...39 Enhancements to Existing Features...39 ISDN: No Progress Indicator in ALERT Message Receives Two-Way Speach Path...39 Software Corrections...39 Account Codes: SLT Dialing Account Code and 911 Receive Delay...39 ACD: Work Time Fixed on ISDN Line...39 ARS: X Does Not Work Before Dial Treatment Code Strings...39 Call Forwarding: Fixed Call Forward Causes Non-Stop Ringing...39 E911: 911 Call Delayed with Forced Verifiable Account Codes...40 E911: 911 Call Dropped with Forced Outgoing Call...40 E911: Forced Account Code Delays 911 and Required Account Code...40 E911: Trunk Rotate on No Dial Tone Feature Does Not Work with Forced Trunk Disconnect: Trunk s Work Memory Does Not Clear...40 French Optima (P/N 92230F): French Calendar Prompts...40 ISDN: Forced Trunk Disconnect Does Not Work...40 ISDN: Flash Using Service Code #3 Does Not Work...41 ISDN, BRI: Last Number Redial Does Not Retain Complete Number...41 ISDN, BRI: Last Number Redial Does Not Work When Busy Signal Received...41 ISDN, BRI: SMDR Records Two Times...41 Networking: Can Not Leave a Message Across the Network for a Busy Extension...41 Networking: Transfer Recall Does Not Work...41 Networking: Trunk Lockup Occurs When Transferring to Department Ring Group...41 Single Line Telephones, Digital: Flash Using Service Code #3 Does Not Work Correctly...42 Transfer: Department Group Does Not Receive Transfer and Doesn t Recall i System Software New Features...43 Enhancements to Existing Features...43 ISDN, PRI: Trunk Number Translation For Channel ID Based on Trunk Group Number...43 Software Corrections...43 Central Office Calls, Placing: Dial Tone Detection Timer Does Not Clear...43 Central Office Calls, Placing: DTMF Receivers Not Released With Program 0921: Item 3.44 ISDN: E911 Alarm Sounds Only If 911 Call Completed...44 ISDN, BRI: Digits Dialed After * Treated As Sub-Address or Account Code...44 ISDN, BRI: E911 Alarm Not Displayed on Phones Using BRI Trunks...45 ISDN, BRI: E911 Using ARS s Dial Treatment Table Mixes Up Digits...45 ISDN: Transferred Calls Missing Caller ID Information...45 Networking: Protocol Sent to Non-Networked Trunk Using F-Route Access...45 PMS: System Sending Commands to PMS in Initial Mode i System Software New Features...47 Enhancements to Existing Features...47 PC Programming: Reset Command is Delayed 10 Seconds...47 Software Corrections...47 Networking: SLT s Have Delayed Dialing...47 Networking: Transferred Call Between Systems Could Cause Trunk Lock Up...47 Networking: Transferring a Call Between Systems Could Cause Trunk Lock Up i System Software New Features...49 Telephones: New Model Phones Available...49 Enhancements to Existing Features...50 Barge In: Use Barge In to Transfer a Call Into a Conference Call...50 Barge In: Use Barge In With Conference Calls...50 Call Coverage Key: Ringing Line Preference Can Now Apply to Call Coverage Keys...51 Caller ID: Missed Call Redial Now Saves 12 digits...51 Central Office Calls, Answering: Universal Answer Programming Changed...51 Networking: E&M Trunks Detects Hookflash...51 SMDR: Trunks Can Print Dialed Number on SMDR Reports...52 Traffic Management Report: Time Output Options Added...52

7 Release Notes Night Service: Transfer Call for Universal Night Answer (UNA)...52 Voice Announce Unit: Transfer Calls to the VAU...53 Warning Tone for Long Conversation: Feature Available For DISA Callers...53 Software Corrections...53 Barge In: Department Step Calling Then Barge In Causes Lockup...53 Barge-In: System Now Prompts for Destination Extension...54 Call Forwarding: Chain Call Forward to Virtual Extensions Ring Incorrectly...54 Call Forwarding: Keyset Display on Chain Call Forwards Now Display Correctly...54 Call Forwarding, Fixed: Extensions Continue Ringing Even After Call Picked Up...54 Camp On: Continued Ringing with Camp On to Call Forwarded Extension...55 Camp On: Extension Hears Ringback Tone When Camping On to Blocked Extension...55 Central Office Calls, Answering: System Ignores Program 0410 for Department Groups...55 Central Office Calls, Placing: If No Dial Tone, Display Does Not Show Digits Dialed...55 E911: Incompleted 911 Call Redials Digits on Next Call...55 Networking: Analog E&M Trunks Sending DTMF Tones for Protocol Signals...55 Voice Mail: Message Center Key Lamp Remains Lit...55 Voice Over: Call Timer Resets i System Software New Features...57 Enhancements to Existing Features...57 Software Corrections...57 Barge-In: Barging In on Conference Causes Continuous Ringing...57 Barge-In: System Reboot May Occur With Barge-In Feature...57 CDTU: Using Barge-In While Plugging in CDTU Causes CDTU Lockup...57 Model 3 Phones: Feedback Occurs on Start Up...57 SMDR: Transferring to Master Number Results in Incorrect Time on SMDR i System Software New Features...59 Enhancements to Existing Features...59 Software Corrections...59 Networking: Department Group With Simultaneous Ring Causes Trunk Lock Up...59 Voice Announce Unit: OPA Message Disconnected Before Completed i System Software New Features...61 Enhancements to Existing Features...61 Paging: External Paging Now Allowed If Internal Page is Busy...61 Software Corrections...61 ACD: Queue Status Does Not Change with Volume Keys...61 Caller ID: Automatic Viewing of Transferred Calls Doesn t Display...61 i-series Phones: Paging Interrupts Soft Key Operation...61 PC Attendant: Loop Key Lock Up...61 Voice Mail: Message Waiting LED Does Not Light i System Software New Features...63 Enhancements to Existing Features...63 Software Corrections...63 CDTU: With T1 PCB, CDTU Locks Up With System Restart i System Software New Features...65 Enhancements to Existing Features...65 Software Corrections...65 Networking: Transferred Intercom Call Will Now Display Call Timer...65 Networking: Transferring to ACD Master Number From Same System Not Allowed...65 Networking: Trunk Lockup Occurs When Call Tries to Recall To Voice Mail...65 Networking: Voice Mail Transfer Recall Results in No Talk Path...65 v

8 Release Notes 384i System Software New Features...67 Enhancements to Existing Features...67 Software Corrections...67 DIMU: New Command Added for DTMF Receiver...67 Central Office Calls, Receiving: Call in Queue Tried to Queue Again...67 Central Office Calls, Receiving: DTMF Trunk Locked in Queue if DTMF Receives Error..67 Voice Announce Unit: Incoming Call Hears Silence...67 vi

9 Release Notes 384i System Software i System Software These release notes explain the Feature Enhancements, Additional Enhancements, and Software Corrections in 384i System Software version IMPORTANT: Due to voice mail enhancements made in this software release, when upgrading your system software to , the voice mail feature will require reprogramming (Program 1003 and 0410: Item 3). Due to these enhancements, this software (and any future release) is not backwards compatible. Refer to "Voice Mail: Port Assignment Program Changed to Allow Up to 48 Voice Mail Ports" for further information. 1. New Features 1.1 ISDN, BRI: BRI Compatibility Added The system now provides compatibility with ISDN Basic Rate (BRI) services, including: Basic BRI Call Control (BCC) Point-to-Point BRI Terminal Connection (no daisy-chaining) Point-to-Multipoint BRI Terminal Connection (daisy-chaining) Capacity of 32 BRI circuits and 64 BRI channels BRI services require the installation of BRI Interface PCBs (P/N 92191). Each BRI Interface PCB has two BRI circuits. There are two channels (ports) per circuit (2B+D), providing 64K Clear B- Channel and 16K Clear D-Channel response. The BRI Interface PCB uses a single universal slot. The system allows the installation of up to 16 BRI Interface PCBs with a maximum of 32 BRI circuits and 64 BRI channels. An incoming analog or 3.1 Khz type data call to the 384i system will follow the settings in Program Incoming ISDN (3.1 Khz Audtio) Ring Group first. If this program is not set, the system will then follow the settings in Program Incoming Trunk Ring Group Assignment. Each BRI Has Two TEI s For each BRI line, two different TEI s will be assigned to two different SPID s. The two different SPID s (as defined in Program 0311) for each BRI line, will be related to different trunk logical port numbers. One BRI provides two trunk logical ports when it is connected to a CO line. Each SPID is assigned to a different TEI. This relationship is made in the initialization of the BRI line when it is connected to the CO. This relationship between SPID and TEI s are created as follows. LOGICAL-PORT-NUMBER + 0 = SPID-1 LOGICAL-PORT-NUMBER + 1 = SPID-2 For further information, refer to the ISDN manual (P/N 92000ISDN**). 1.2 Transfer: Prevent Recall of Transferred Call The Class of Service option has been enhanced. If programmed, the new option allows an extension user to transfer a call and the system will prevent it from recalling if the call is not answered. Program Class of Service Options (Part B); Item 20, No Recall sets this option. The entries are: 0 = allows recall 1 = prevents recall (default = 0) 1

10 Release Notes 384i System Software Voice Mail: Port Assignment Program Changed to Allow Up to 48 Voice Mail Ports Prior to this software release, up to 16 voice mail ports could be assigned in Program Voice Mail Port Assignment. With this software, Program 1017 is no longer used and is replaced by Program Extension (Department) Group. This program change will now allow up to 48 voice mail ports to be programmed. Using Program 1003, voice mail ports are assigned to an Extension (Department) Group. This group is then assigned as the voice mail group. Only one voice mail group is allowed per system and the group can not exceed 48 ports. Once the ports have been assigned to a group in Program 1003, Program Extension (Department) Group Options, Item 3: Voice Mail Group is used to designate which Extension Group is to be assigned as the Voice Mail group (0=not voice mail group, 1=voice mail group). The Voice Mail Master Number should still be assigned to a voice mail group in Program Voice Mail Master Number. 1.4 Voice Mail: Queuing When accessing the voice mail, the system now provides a voice mail queue. If all the voice mail ports are busy, any calls trying to get to voice mail will be placed in a queue. As the voice mail ports become available, the calls will be connected to the voice mail in the order in which they were received. The voice mail queue follows the programming of the Department Hunting, Program Extension (Department) Group Options, Item 3: Voice Mail Group, which assigns a voice mail department group. As this feature follows Department Hunting, the queue can hold a maximum of 10 calls. If the queue is full or if voice mail ports are not assigned to a Department Group in Program Extension (Department) Groups, the calls will be handled as though there were no voice mail queuing feature enabled. The calls will either access voice mail if a port is available or they will receive a busy signal. With this software version, when using networked voice mail, the circuit type for the phantom voice mail ports at the remote site must be set to 3. The system must then be reset in order for the changes to take effect. Prior to software version , the circuit type for remote phantom voice mail ports had to be set to 0. The voice mail queuing feature does not work with the Conversation Record feature. 2. Enhancements to Existing Features 2.1 Caller ID: Remote Log-On Protocol Sent to Voice Mail A Caller-ID/ANI trunk can now send Remote Log-On Protocol with Caller ID digits to voice mail. When the trunk 001 receives the Caller ID as 12345, the protocol becomes ***6001*12345*. To enable this feature, set Program Basic Trunk Port Setup (Part B); Item 5 - Caller ID to Voice Mail to 0. 0 = allows sending Caller ID digits 1 = deny 2.2 Handsfree: Automatic Handsfree with Call Coverage and Park Features The Automatic Handsfree feature can now be used with either the Call Coverage or Park features. To use Automatic Handsfree, Program Tenant Group Options (Part A); Item 6, Automatic Handsfree must be set to 1 (enabled). 2.3 IDSN, PRI: Channel Information Changed The previous software design had a fixed relationship between the trunk port numbers indicated on the PRI and the physical ISDN channels. Channel 1 was the first trunk, channel 2 was the second 2

11 Release Notes 384i System Software trunk, etc. All setup messages sent from the 384i system contained a Channel ID Information Element which contained exclusive CH number data. If the CO sent a setup message with the same Channel ID as the system sent to the CO, a call collision would occur. This required a change in the channel handling on ISDN calls. With this software release, all 23 PRI channels must be programmed exactly the same. This is due to the fact that there is no association with channels and line numbers. So, for example, if the central office sends an incoming call on channel 2, because the system will assign the lowest available channel, the call could actually be received in the 384i system on channel 1. Calls will be handled based on the programming for the logical port. This means that all the trunks for an ISDN line must be programmed the same. If you re placing an outgoing call using a loop key, the telephone s display will indicate the line number the call is using, but the channel is independent of the line number and will not necessarily be the same. The setup messages from the 384i will no longer contain a Channel ID Information Element. All calls from the 384i will wait until it receives a Channel ID Information Element from the CO as part of a Call Proceeding, Alerting, or Setup Acknowledge before determining a channel number. With this version of software, there is no fixed relationship between the trunk number and channel number. 2.4 Voice Mail: Networking Voice Mail Requires Circuit Type 3 With with this software release, when using networked voice mail, the circuit type for the phantom voice mail ports at the remote site must be set to 3 in Program Extension Circuit Type. The system must then be reset in order for the changes to take effect. Prior to this software version, the circuit type for remote phantom voice mail ports had to be set to Software Corrections 3.1 ACD: Overflow to Voice Mail Has No Answer Supervision If an incoming ACD call overflows to voice mail, Answer Supervision will now be sent to the CO. Previously, if the system was programmed as detailed below, incoming ACD calls overflowing to voice mail did not receive Answer Supervision. - If trunks are programmed as DID, Tie line, or T1 wink start ANI/DNIS (Program 0901, Items set to 3, 5, or 6) - In Program 1908, ACD Overflow Options, if the overflow destination is set to 9 (voice mail) and no ACD announcement is used 3.2 Call Forwarding: Beeps with Forwarded Voice Call Intercom Corrected When a voice call is forwarded to another keyset, which is also set for voice call, the beeps preceeding the call will now be received as follows: - Keysets with the microphone ON will receive two beeps - Keysets with the microphone OFF will receive one beep 3.3 Call Forwarding: Immediate with Both Ringing Programming Can Not Chain Forward Extension A is forward to Extension B with Call Forward Immediate with Both Ringing. Extension B is programmed with Call Forwarding with Ring No Answer to Extension C. Under these conditions, the following could occur: - An incoming call to Extension A rings both Extension A and Extension B. - With no answer, Extension B forwards the call to Extension C. Extension A continues to ring. - Extension C answers the call. - Extension A continues to ring. 3

12 Release Notes 384i System Software Extension A answers the call. The call is then pulled away from Extension C. With this release of software, Extension B will not be able to forward its calls when another extension has Call Forward Immediate with Both Ringing set to that extension. 3.4 Call Forwarding: Extensions within Same Ring Group Cause System Lockup Depending on the setup of the Call Forwarding feature, an incoming call to an extension that is Call Forwarded could cause the system to lockup. The lockup will occur if: - The system is programmed as: System Software prior to : Program Class of Service Options (Part A); Item 6, Automatic Off Hook Signaling set to 0 (manual off-hook signaling). System Software or above (option added in ): Program Class of Service Options (Part B); Item 12, Forced Off Hook Signal From CO is set to 0 (off-hook signaling from a CO is disabled). - Extension A and Extension B are in the same ring group. - Extension A s station port number is lower than Extension B s station port number. - Extension A is Call Forwarded to Extension B. - Extension B is busy and an incoming call is received in the ring group. 3.5 ISDN: Abbreviated Dial Numbers Have No DTMF Receiver When placing an Abbreviated Dial call from a keyset on an ISDN trunk, no DTMF tones were sent when the dial keys were pressed. With this software release, the caller will now be able to use the dial pad to send digits after the call has been answered. 3.6 ISDN: DID Trunk From ISDN Does Not Forward to VAU or Voice Mail In previous software, a DID call from an ISDN trunk did not forward to the VAU or Voice Mail after the DID Ring-No Answer Timer (Program 0405, Item 31) expired. This is resolved with this software version. 3.7 ISDN: Hold and Transfer Used on Outgoing Calls When placing an outgoing call on an ISDN trunk, the call will now be able to be placed on hold or transferred before it is answered by the receiving party. Previously, the caller would have to wait until the call was answered before using the Hold or Transfer features. 3.8 ISDN: Incoming DID and DISA Calls Receive No Dial Tone When a DID or DISA trunk (as programmed in Program Basic Trunk Port Setup (Part A); Items 14-17, Trunk Service Type) received on incoming call on an ISDN trunk, the system did not send back dial tone to the outside party. This will no longer occur with this software release. 4

13 Release Notes 384i System Software ITSU-B: Format of Up-Stream Data Changed The format of up-stream data from the ITSU-B regarding Layer 1 status has been changed as follows: Old Format: New Format: length 04 H length 04 H resource no. (21 H or 22 H) resource no. (21 H or 22 H) message genre 23 H : L1-INFORMATION message genre 29 H : L1_INFORMATION data condition data condition # condition hex 1 byte 01H layer1 establish 02H layer1 disconnect 03H layer1 establish 04H layer1 disconnect # condition hex 1 byte 01H layer1 establish 03H layer1 disconnect 3.10 Networking: Call Could Result in One-Way Conversation One way conversation could occur if an extension user: - Places or receives a call across the network, then - Places the call on hold and picks its up again, then - Presses a key on the dial pad With this software, this should no longer occur Networking: Tandem Trunking Ignores Program with Two Incoming Calls In prior software, two incoming calls from across the network to the same extension would be tandem trunked regardless of how Program Basic Trunk Port Setup (Part A), Item 31: Loop Disconnect Supervision was set if the following occurred: - While active on an incoming call received from across the network, an extension user receives a second incoming call from across the network. - The extension user places the first call on hold and answers the second call - The extension user completes the second call and then hangs up. This will no longer occur with this software release TAPI: Call Transfer From an Even Port Indicates 30 When the TAPI driver receives a call transfer indication from an extension with an even port, the ring type is indicated as 30. The same transfer from an extension with an odd port will indicate 33 as the ring type. The ring type from an extension with an even port will now be indicated as a Voice Mail: Answering Machine Emulation Does Not Work With Voice Mail Ports 9-16 If the Answering Machine Emulation feature uses voice mail ports 9-16 in Program 1017, the feature will now work correctly. With software version and above, this feature did not work with voice mail ports

14 Release Notes 384i System Software

15 Release Notes 384i System Software i System Software These release notes explain the Feature Enhancements, Additional Enhancements, and Software Corrections in 384i System Software version New Features No New Features in this release. 2. Enhancements to Existing Features 2.1 Call Coverage Key: Programmable for Incoming/Outgoing or Just Incoming A new program, Program Class of Service Options (Part B); Item 22 Receiving Call Coverage Key Calls is now available. This option enables Call Coverage Keys to be used to place and receive calls, or for receiving calls only. The entries are: 0 = Incoming and Outgoing Calls 1 = Incoming Calls Only (Default = 0) 3. Software Corrections 3.1 ISDN: Call Reference Conflict If a call reference number conflict happened between an outgoing call and an incoming call on an ISDN trunk, the system recognized both calls as being active. When one of the calls was disconnected, the second call remained active even after being cleared by the CO. With this software release, the system will clear a duplicated call when a call reference conflict occurs. 3.2 ISDN: Channel ID Information Element Missing When an ISDN trunk received a SETUP-ACKNOWLEDGE, CALL_PROCEEDING, ALERT, or CONNECT message that did not include the Channel ID Information Element or if it did not indicate the proper channel number, the 384i system did not reject the call. The 384i system will now respond to these types of messages by sending a DISCONNECT message. This will clear the call. The 384i system will then try to re-establish the call. 3.3 ISDN, PRI: Channel Lockup Due to Layer 1 and Layer 2 Errors When making an outgoing call, the system would believe the trunk was busy, but the hardware handshaking to the PRI card would indicate the trunk as being idle. This was due to errors in Layer 1 and Layer 2. The only way this problem could be resolved would be by unplugging the PRI card and reseatting it. This will no longer occur with this software version. 3.4 ISDN, PRI: Incoming Call on Channel 23 Results in Next Outgoing Call Being Rejected An incoming call on channel 23 would cause the next outgoing call made to be rejected because the Channel ID Information Element was missing. This would occur even if other channels on the PRI were idle. This is corrected in this software release. 7

16 Release Notes 384i System Software Networking: Tie Line Loop Key Flashes Incorrectly on Hold After placing a network Tie line on hold, the loop key will flash. If a user dials a F-route access code and accesses the same network Tie line, the loop key that has the Tie line on hold will change from a hold flash to a steady green. With this software release, the loop key will indicate a hold flash while the call is on Hold. 3.6 P Command Corrections The following items have been corrected in the P commands: When ACD agents parked a call in a system Park orbit, the 384i did not send any P command. The Management Information System (MIS) did not change the trunk s status. The 384i will send the PB command to the MIS showing HOLD status. When ACD agents picked up a call parked in a system Park orbit, the 384i did not send any P command to clear the ACD agent. The 384i will send the PC and P7 commands which clears the old ACD agent, then P5 and P6 commands which indicates the extension that picked up the call. When an agent picked up an ACD incoming call using a Call Coverage Key, the 384i sent the P6 command to the MIS. If an ACD incoming call was not in queue and an agent was ringing, the MIS might not change the agent s status after picking up the ACD call. The 384i will send PA command to the MIS. 8

17 Release Notes 384i System Software i System Software These release notes explain the Enhancements and Software Corrections in 384i System Software version New Features No New Features in this release. 2. Enhancements to Existing Features 2.1 Conference: Number of Outside Parties Increased Conference lets an extension user add additional inside and outside callers to their conversation. With Conference, a user may set up a multiple-party telephone meeting without leaving the office. The system allows either four or eight parties maximum per conference. This software release enhances the Conference feature to allow any number of conferenced parties to be outside parties. Previously, no more than two parties in a Conference could be outside callers. Program Basic Trunk Port Setup (Part A), Item 23 Unsupervised Conference Call CODEC Gain Type controls the gain for each trunk to be conferenced. 2.2 Night Service: Automatic Night Service, Program 0401-Item 2 Added With this software release, Program Tenant Group Options (Part A), Item 2: Automatic Night Service Enabled has been added back in to the system programming. This option had been removed with software version and replaced with Program Automatic Night Service Patterns, Program Weekly Night Service Switching, or Program Holiday Night Service Switching. The system will now follow the setting for the tenant group for Automatic Night Service in Program 0401 (enable=1, disable=0) and will then use the service patterns set in Program 0801, 0802, or 0803 for routing the calls. The information for the night service is now stored on the battery-backed RAM. This means that if not using the Automatic Night Service (0401 set to 0 ), in case of a power failure while in night mode, when the power is restored, the system will still be in night mode. 2.3 Voice Mail: Networking Voice Mail Circuit Type With the release of software version , when using networked voice mail, the circuit type for the phantom voice mail ports at the remote site had to be set to 3. With this software release, the circuit type no longer has to be set to Software Corrections 3.1 ACD: Agent Recording Feature Program Station Class Of Service Options (Part B), Item 18: Prevent ACD Agent Recording Control entries have been changed. This feature is documented as 0 allowed an ACD Agent the ability to control the ACD Record feature and 1 prevented their control. The system software, however, worked the opposite. With this software release, 0 will allow control, 1 will prevent control. 9

18 Release Notes 384i System Software ACD: Conference Including a 3-ACI Causes Lockup ACI Call Recording allows you to use a recording device connected to an Analog Communications Interface (ACI) to record ACD Agents calls. While recording a conference call, if the CO disconnects first, the ACI does not disconnect, the agent s COS is changed to disable recording, and the ACI and the conference circuit gets locked up. This will no longer occur with this software release. Note: Program Conference Circuit Setup must not be assigned to block Call Forwarding, Fixed: Extension Rings After Transfer to Voice Mail With Station A programmed for Immediate Call Forward to Station B, with no answer at Station B the call will now transfer properly to voice mail if so programmed. Previously, if Station B was programmed to forward to voice mail with no answer, after the call was transferred to voice mail, Station B would continue to ring. This problem has existed since software, but will no longer happen with this software release. 3.4 E911: Alarm Ring Option Bypassed The system will now check the setting in Program Class of Service Options (Part B), Item 9: 911 Alarm Ring. In prior software, the system would ignore the programmed setting for the Alarm Ring option. 3.5 ISDN, BRI: Line Key Seized Results in One-Way Talk Path When a keyset is programmed with line keys 1 and 2 for BRI, a one-way talk path results if the following occurs: - An outgoing call is made on line key 1. - The outgoing call on line key 1 is placed on hold after being answered by the called party. - Line key 2 is seized and CO dial tone is heard. - Retrieve call on line key 1 from hold. With this software release, this will no longer occur. 3.6 ISDN, BRI: No SPID or Single SPID Cause CO Problems 10 Several problems relating to either no SPID or single SPID received (as defined in Program 0311) have been resolved. If a Single SPID is Defined: If the BRI port received an incoming call without matching the SPID to the incoming called number, the incoming call always appeared on the first TEI trunk port. This trunk port is used for the first SPID. The system will now reject an incoming call if the SPID does not match the incoming called number. An outgoing call on a BRI port could be made without programming the SPID to the TEI related to the BRI port. The CO must reject this call since it did not go through a SPID initial

19 Release Notes 384i System Software sequence when the BRI line was connected to the network. The system will now block an outgoing call when the SPID data is not defined because there is no associated TEI information from the central office. If No SPID is Defined: The BRI port could not handle a call if no SPID was programmed. The software will now handle a call with no SPID programmed as a call for TEI ISDN, BRI: Overflow to Voice Mail Does Not Work A system with a BRI line programmed to overflow to voice mail will now route to the voice mail as programmed. Previously, after Program System Timers (Part A); Item 62 - DIL No Answer Recall Time expired, the system would not divert the call to the voice mail as programmed in Program DIL No Answer Destination. This is fixed with this software version. 3.8 ISDN, PRI: Digital Gain Control Could Result in Data Communications Error When a PRI channel goes idle, the system will initialize the gain for a random trunk. This could cause noise and problems on channels in use. With this software release, this will no longer occur. 3.9 Networking: Call in Voice Mail Queue Locks Up A call that is forwarded across the network to voice mail and must wait in voice mail queue before connecting to voice mail will now work correctly. Previously, a call transferred across the network that had to wait in the voice mail queue would lock up once a voice mail port became available. This will no longer occur with this software version Networking: DTMF Receiver Not Cleared After Tie Line on Hold When a networked tie line is place on hold, the system will now release the DTMF receiver when the call is answered. Previously, if the call was on hold for an extended amount of time, the system would not clear the DTMF receiver once the call was answered Networking: Tie Line Call Transferred to ACD Master Number Remains on Hold With the following situation, a transferred call would remain on hold because the call did not send a Network Hold Answer Protocol Digit after being answered. - System A and System B are connected with a network tie line. - An extension on System A receives a DID call and it is routed to an extension on System B over a tie line. - The extension on System B answers the call and transfers it to an ACD master number. - An ACD agent on System B tries to answer the call, but hears silence. The calling party remains on hold. The system will now send a Network Hold Answer Protocol Digit after the call is transferred to the ACD master number. 11

20 Release Notes 384i System Software Networking: Voice Mail Call with BGM Enabled Holds T1 Channel With Background Music on, if an extension user calls the remote voice mail using a T1 channel, when the extension goes idle, the T1 channel will be disconnected. Previously, when the extension went idle after hanging up from voice mail, they would continue to hear the call activity on the T1 channel that had been used. The channel would be disconnected only after the extension user placed another call. This will no longer occur with this software release Tie Lines: 911 on Wink Start Line Does Not Work When dialing 911 on a tie line with wink start, the call will now go through. With previous software, a tie line with wink start would not dial out properly after the wink. This is fixed with this software release Trunk Queuing: System Automatically Redials ARS Buffer Call or 911 If an extension uses the Trunk Queuing feature, when a line becomes available, the extension will receive dial tone. Previously, if an extension used the Trunk Queuing feature, when a line became available, the last call in the ARS buffer would be dialed automatically. This would also include 911 if this number had been dialed. This problem could be cleared by performing a system reset, but once ARS was used again to place a call, that extension would experience this same problem when using the Trunk Queuing feature. This problem has existed since the ARS feature was implemented but will no longer occur with this software release Voice Mail: Call in Voice Mail Queue Locks Up A call that is forwarded to voice mail and is in the voice mail queue before connecting to voice mail will now work correctly. Previously, a call transferred to voice mail that had to wait in the voice mail queue would lock up once a voice mail port became available. This will no longer occur with this software version. 12

21 Release Notes 384i System Software i System Software These release notes explain the Enhancements and Software Corrections in 384i System Software version This software requires a new EPROM for the ITSU-B card (check sum=abbfh). 1. New Features No New Features in this release. 2. Enhancements to Existing Features 2.1 ISDN, BRI: Automatic Recovery from DATA LINK FAILURE If a data link error detection is indicated by the ITSU-B, the system will now try to recover the data link and send the SPID to the central office. This will occur even if Program ISDN BRI Layer 3 Options; Item 10 - Response to Layer 2 Data Link (DL) Release Message is set to 2 for No Response. To provide this enhancement, the ITSU-B must be able to indicate to the system when a data link error has occurred. This requires a new EPROM for the ITSU-B PCB (check sum ABBFH). 3. Software Corrections 3.1 ARS: Account Codes Dialed Before Number Does Not Work With the ARS feature enabled, when dialing an Account Code before the telephone number, the system will route the call correctly. Previously, the system would route the call differently depending on if the Account Code was dialed before or after the telephone number. The system will now route the call correctly, regardless of when the Account Code is entered. 3.2 ISDN: Repeat Redial Function Key Does Not Work When using a Repeat Redial function key after placing a call on an ISDN trunk, the feature key will now work correctly. With prior software, this feature key did not work when the last outside call was placed on an ISDN trunk. 3.3 ISDN: Automatic On-Hook Transfer on ISDN Line Does Not Connect When using the Automatic On-Hook Transfer feature with an ISDN line, the feature will now work correctly. With prior software, the following would occur: 1) Station A calls Station B. 2) Station B answers the call. 3) Station B places the call on hold. 4) Station B makes an ISDN outgoing call. 5) Station B hangs up handset. The held call (Station A) is not transferred to the number called on the ISDN trunk. 3.4 ISDN, BRI: Account Code Does Not Work With previous software, the Account Code feature did not work with BRI lines. This is now fixed with this release of software. 13

22 Release Notes 384i System Software ISDN, BRI: ARS Does Not Work on BRI Lines Previously, the Automatic Route Selection feature did not dial out on any BRI lines. With this software release, ARS can use the BRI lines without any system problems. 3.6 ISDN, PRI: Data Communications Error with ATSU Modem With previous software, the PRI ATSU modem could experience problems with data communications. This occurred due to an incorrect digital gain control setting. This will no longer occur with this release of software. 14

23 Release Notes 384i System Software i System Software These release notes explain the Enhancements and Software Corrections in 384i System Software version New Features No New Features in this release. 2. Enhancements to Existing Features 2.1 E911: Forced Disconnect Follows Timer to Disconnect Call When all lines in the programmed trunk group (Program Separate ARS Routing Options, Emergency Calls) are busy and the system must drop a call in order to place a 911 call, the system will now follow the timer setting in Program Analog Trunk (ATRU PCB) Timers (Part A), Item 9 (Flash - Hooking 1), 10 (Flash - Hooking 2) or 11 (Ground Start Time) to disconnect the call (systems are usually set for Item 10, Flash - Hooking 2). 3. Software Corrections 3.1 Account Codes: Extension Receiving Transfer Can Enter Account Code When a call is transfer to an extension, the extension receiving the call will now be able to enter an Account Code for the call if Program Account Code Setup; Item 3, Account Codes for Incoming Calls is enabled. Thils also includes calls picked up using a Call Coverage key. In previous software, the system would prevent the entry of an Account Code. 3.2 ARS: 555 Routing To Long Distance Carrier Does Not Work When dialing xxxx or xxxx, the system would follow the system routing for 555 and could not be routed to a long distance carrier if so programmed for 800 or 900 calls. This is fixed with this software release. 3.3 ARS: Dial Treatment X Fixed When using X in an ARS Dial Treatment, the feature will now work correctly. In prior software, this system did not recognize the X. 3.4 E911: Forced Disconnect with VAU Does Not Work When using the E911 feature on a system with a VAU, if all lines are busy, the system would not disconnect a line to place the 911 call. With this software release, if all lines are busy when a 911 call is placed, the system will disconnect a trunk and place the call immediately. 3.5 E911: PBX Access Code Not Required in ARS Dial Treatment When using the E911 feature with ARS, the system will not require the PBX access code to be entered into the ARS dial treatment. The system will automatically select a line from the trunk group assigned in Program Separate ARS Routing Options, Emergency Calls if no access code is entered or a line from a different trunk group is selected. If a user dials a PBX access code before dialing 911, the system will either: - Process the call as dialed if the line seized is within the proper trunk group. OR - Disregard the PBX access code and seize a line from the assigned trunk group and then dial 911. With prior software, this feature was not working. 15