All information contained in this document is subject to change without notice. Nortel
reserves the right to make changes to equipment design or program components as
progress in engineering, manufacturing methods, or other circumstances may warrant.
*Nortel, the Nortel logo, the Globemark, Unified Networks, Meridian 1 PBX, Communication
Server 1000 (CS 1000), and Communication Server 2100 (CS 2100) are trademarks of
Nortel.
TelStrat is a registered trademark of TelStrat International, Ltd. Microsoft, MS-DOS, and
Windows are trademarks of Microsoft Corporation.
Standard 1.0
Publication history
June 2005This is the Standard 1.0 issue of the Remote Gateway 9100 Series
and RLC Release Notes for Remote Gateway 9100 Series product
release 1.6.0. This document provides updated Known problems
and Issues corrected sections.
21.6.0 Release Notes for Remote Gateway 9100 Series and RLC
June 2005
Contents
In this document
About this document4
What’s new in release 1.6.0?6
Hardware, software, and documentation requirements8
Upgrade file names for this release12
Performing upgrades14
Operation15
Issues Corrected Since 1.5.217
Known problems in this release20
1.6.0 Release Notes for Remote Gateway 9100 Series and RLC3
Standard 1.0
About this document
This document applies to the following firmware and software:
Release 1.6.0 firmware for the Remote Gateway 9150 units, Remote
Gateway 911x series units, Digital Telephone IP Adapter units, and Reach
Line Card (RLC)
Release 1.6.0 software for Remote Gateway 9100 Series
Release 1.6.0 software for Remote Gateway 9100 Series Configuration
Manager
Version 34 firmware for ISDN U-interface and ISDN ST-interface
Document purpose
This document describes the features, known problems, and work-arounds for
the Remote Gateway 9150 unit, Remote Gateway 911x series units, Digital
Telephone IP Adapter units, and the RLC. It also provides:
information that is not provided in the:
— Reach Line Card Installation and Administration Guide
(NTP 555-8421-210)
— Remote Gateway 9150 Installation and Administration Guide
(NTP 555-8421-215)
— Remote Gateway 911x Series Installation and Administration Guide
(NTP 555-8421-220)
— Digital Telephone IP Adapter Installation and Administration Guide
(NTP 555-8421-211)
clarification for items that can prevent the system from operating correctly
if they are not configured correctly. Refer to “How to achieve a successful
implementation” on page 5 for more details.
Who should read this document
This document is written for individuals who are responsible for the installation,
configuration, and day-to-day management of the Remote Gateway 9150 unit,
Remote Gateway 911x series unit, Digital Telephone IP Adapter unit, and RLC.
41.6.0 Release Notes for Remote Gateway 9100 Series and RLC
June 2005
How to achieve a successful implementation
The instructions provided in the Reach Line Card Installation and
Administration Guide (NTP 555-8421-210) and the Remote Gateway 9100
Series Installation Testing—Job Aide help you achieve a successful
implementation. Specifically, pay close attention to the instructions for
configuring the following:
PBX configuration for ports, DN Discovery, and Caller ID security
PSTN numbers used to contact Remote Gateway 9100 Series units
prefix configuration in PSTN numbers on the RLC
BRI trunk configuration on the Remote Gateway 9150 unit
Remote Gateway 9100 Series naming convention
Unless otherwise specified, the term “Remote Gateway 9100 Series units” refers
to the following products:
Remote Gateway 9110 unit
Remote Gateway 9115 unit
Remote Gateway 9150 unit
Digital Telephone IP Adapter unit (Internal and External)
The product name “Remote Gateway 9100 Series” refers to all of the “Remote
Gateway 9100 Series units” as well as the RLC.
PBX terminology
Throughout this document, the term “host PBX” refers to any of the following
Nortel PBX platforms:
Meridian 1 PBX
Communication Server 1000 (CS 1000)
Communication Server 2100 (CS 2100)
1.6.0 Release Notes for Remote Gateway 9100 Series and RLC5
Standard 1.0
What’s new in release 1.6.0?
This is a Remote Gateway 9100 Series minor release that includes the following:
Hardware upgrade
The Remote Gateway 9115 and Digital Telephone External IP Adapter
units are receiving a component hardware upgrade. All Remote Gateway
9115 releases prior to and including NTDR77BC-04 and all Digital
Telephone External IP Adapter releases prior to and including
NTDE02BC-04 include a NetSilicon Net5 and Net10 (nicknamed “Five
and Dime”) processor. This Five and Dime processor is no longer being
manufactured. Therefore, Nortel is replacing this processor with a new
NetSilicon Net40 processor. This hardware upgrade is effective with
Remote Gateway 9115 release NTDR77BC-05 and above as well as Digital
Telephone External IP Adapter release NTDE02BC-05 and above.
Performance and functionality remain the same across the all units.
Note: Only the Remote Gateway 9115 and Digital Telephone External IP
Adapter units are impacted by this hardware upgrade. No other Remote
Gateway 9100 Series products are receiving a hardware upgrade at this
time. This hardware upgrade is not due to any known defects with the Five
and Dime processor. Nortel is undertaking this hardware upgrade to extend
the life of the Remote Gateway 9115 and Digital Telephone External IP
Adapter units.
New Users
: Once Nortel exhausts the inventory of Remote Gateway 9115
and Digital Telephone External IP Adapter units that contain the Five and
Dime processor, all subsequent shipments will contain the Net40 processor.
When performing a firmware upgrade, review the release number on the
bar code on the back of the Remote Gateway 9115 and Digital Telephone
External IP Adapter unit(s) you receive. Upgrade your unit using the
appropriate firmware upgrade file. Refer to “Upgrade file names for this
release” on page 12 to determine the appropriate file to use.
61.6.0 Release Notes for Remote Gateway 9100 Series and RLC
June 2005
Existing Users: No action is required on the part of existing users. Existing
units do not need to be returned to Nortel for a hardware upgrade. When
performing a firmware upgrade, review the release number on the bar code
on the back of the existing Remote Gateway 9115 and Digital Telephone
External IP Adapter unit(s). Upgrade your unit using the appropriate
firmware upgrade file. Refer to “Upgrade file names for this release” on
page 12 to determine the appropriate file to use.
Other issue corrections
Refer to “Issues Corrected Since 1.5.2” on page 17 for further details.
1.6.0 Release Notes for Remote Gateway 9100 Series and RLC7
Standard 1.0
Hardware, software, and documentation
requirements
This section identifies the following items that are required to support this
release:
supported PBX platforms and software releases
current hardware, software, and firmware versions
documentation requirements
Meridian 1 PBX software and platforms
Meridian 1 PBX 11, 11C – Cabinet, 11C – Chassis, 11E, 51C, 61C, 71C, and
81C platforms are supported using software release 23 (or higher) with the
following four packages:
package# 0 BASIC (Basic Call Processing)
package# 19 DDSP (Digit Display)
package# 95 CPND (Caller Party Name Display)
package# 170 ARIE (Meridian Modular Sets)
Note: The Meridian 1 PBX 11 Chassis platform restrictions are shown in the
following table:
HardwareRestrictions
16-port (single-slot) RLC NTDR68xxsupported in slots 1, 2, 3 in the main chassis
and 7, 8, 9, 10 in the expander chassis
32-port (double-slot) RLC NTDR71xxsupported in slot 1 or 2 in the main chassis
(maximum of 1) and 7, 8, or 9 in the
expander chassis (maximum of 2)
Since the 32-port RLC requires two backplane connections, it cannot be
provisioned in slot 10 of an Meridian 1 PBX 11 cabinet, as this slot has only one
backplane connection.
81.6.0 Release Notes for Remote Gateway 9100 Series and RLC
June 2005
CS 1000 software and platforms
Contact your Nortel distributor for CS 1000 platform information. CS 1000 uses
software release 2 or higher.
CS 2100 software and platforms
The following CS 2100 platforms (using software release MSL12 or higher) are
supported:
SuperNode (with series 70 Processor)
SuperNode SE (with series 70 Processor)
Note: CS 2100 platforms require a patch to support M39xx digital telephone
sets with QoS transitioning. Refer to the Reach Line Card Installation and Administration Guide (NTP 555-8421-210) for more information.
Hardware, software, and firmware
The following table identifies the hardware, software, and firmware supported
by the Meridian 1 PBX release.
Current
Nortel
Product
RLC 16-port NANTDR68AENTDR68AA1.6.0
RLC 32-port IPE-NANTDR70AENTDR70AA1.6.0
RLC 32-port Opt 11-NANTDR71AENTDR71AA1.6.0
9150-North AmericanNTDR69AENTDR69AA1.6.0
9150-International (CALA and
Asia-Pac)
9150-Australia/New ZealandNTDR92BENTDR92BA1.6.0
RLC 16-port-EuroNTDR68BENTDR68BA1.6.0
RLC 32-port IPE-EuroNTDR70BENTDR70BA1.6.0
RLC 32-port Opt 11-EuroNTDR71BENTDR71BA1.6.0
1.6.0 Release Notes for Remote Gateway 9100 Series and RLC9
Product #
NTDR92AENTDR92AA1.6.0
Minimum
Nortel
Product #
Current Firmware
Available
Standard 1.0
Product
9150-EuropeanNTDR92CENTDR92CA1.6.0
9110-GlobalDiscontinuedDiscontinued1.6.0
9115-GlobalNTDR77BC1.6.0
Digital Telephone Internal IP
Adapter
Digital Telephone External IP
Adapter
DSP ModuleNTDR73AANTDR73AAN/A
ISDN BRI U-interface moduleNTDR74ABNTDR74AB34
ISDN BRI ST-interface module NTDR75AANTDR75AA34
Note: With version 1.6.0 of Configuration Manager, you can log on to a unit
with an earlier firmware version to upgrade to the current firmware version.
Documentation
Current
Nortel
Product #
DiscontinuedDiscontinued1.6.0
NTDE02BC1.6.0
Minimum
Nortel
Product #
Current Firmware
Available
To ensure a successful, trouble-free implementation of the RLC, Remote
Gateway 9150 unit, Remote Gateway 911x series unit, and Digital Telephone IP
Adapter unit into your network, have the following items available before you
proceed:
To ensure a successful, trouble-free implementation of the RLC, Remote
Gateway 9150 unit, Remote Gateway 911x series unit, and Digital Telephone IP
Adapter unit into your network, have the following items available before you
proceed:
core documentation (confirm that you have the most up-to-date documents
by checking the Nortel website, as noted under ““Obtaining the
documentation” on page 11”).
— this document
— Reach Line Card Installation and Administration Guide
(NTP 555-8421-210)
101.6.0 Release Notes for Remote Gateway 9100 Series and RLC
June 2005
— Remote Gateway 9150 Installation and Administration Guide
(NTP 555-8421-215)
— Remote Gateway 911x Series Installation and Administration Guide
(NTP 555-8421-220)
— Digital Telephone IP Adapter Installation and Administration Guide
(NTP 555-8421-211)
— Remote Gateway 9100 Series Network Engineering Guidelines
(NTP 555-8421-103)
— Remote Gateway 9100 Series Product CD-ROM (NTDR81AH)
The Remote Gateway 9100 Series Product CD-ROM contains firmware
and software as well as documentation in Portable Document Format
(PDF).
supplementary documents and job aids:
— Remote Gateway 911x Series Quick Start Guide
— Digital Telephone IP Adapter Quick Start Guide
— Installer’s Notes for your hardware component (provided in the box)
— Remote Gateway 9100 Series and RLC Planning Forms (available on
the web)
— Remote Gateway 9100 Series Installation Testing—Job Aide (available
on the web)
Obtaining the documentation
You can obtain the documentation from your Nortel distributor, or on the
Worl d wid e Web a t www.nortel.com. Click on the Technical Documentation
link and navigate to the Remote Gateway 9100 Series document(s) that you are
interested in reading or downloading.
1.6.0 Release Notes for Remote Gateway 9100 Series and RLC11
Standard 1.0
Upgrade file names for this release
Firmware and software files are initially provided on the Remote Gateway 9100
Series Product CD-ROM (NTDR81AH). Upgrade files that are downloaded
from the Nortel website are provided in self-extracting executable files.
The following table identifies the upgrade files supported by this document for
the Meridian 1 PBX release.
Notes:
If you are using an CS 2100 PBX, contact your Nortel support
representative to determine the CS 2100 upgrade file names.
To check the current firmware follow the procedure on page 14.
Remote Gateway 911x series units –
NTDR77BC – Release 4 and prior
Remote Gateway 9115 units –
NTDR77BC – Release 5 and higher
Digital Telephone Internal IP Adapter
units
Digital Telephone External IP
Adapter units – NTDE02BC –
Release 4 and prior
Digital Telephone External IP
Adapter units – NTDE02BC –
Release 5 and higher
ISDN BRI U-interface moduleisdn34u.exebri34u.upg
ISDN BRI ST-interface moduleisdn34s.exebri34s.upg
121.6.0 Release Notes for Remote Gateway 9100 Series and RLC
911x-1_6_0.exe911x-1_6_0.upg
911x40-1_6_0.exe911x40-1_6_0.upg
IPAdapter-1_6_0.exeIPAdapter-1_6_0.upg
IPAdapter-1_6_0.exeIPAdapter-1_6_0.upg
IPAdapter40-1_6_0.exe IPAdapter40-1_6_0.upg
June 2005
Component
Configuration Managercm1_6_0.exenot applicable
Obtaining the latest upgrade files
You can obtain the latest upgrade files from your Nortel distributor, or on the
Worl d wid e Web a t www.nortel.com. Click on the Software Downloads link
and navigate to the file(s) that you are interested in.
Nortel delivery file
nameUpgrade file name
Note: The setup.exe file provided within the
cm1_6_0.exe file is used to perform the
Configuration Manager upgrade.
1.6.0 Release Notes for Remote Gateway 9100 Series and RLC13
Standard 1.0
Performing upgrades
For complete details on performing upgrades, refer to the appropriate
Installation and Administration Guide for your specific product.
ATTENT I O N
The protocol for communication between the RLC and the
Remote Gateway 9100 Series units requires that they be
running the same version of firmware for them to
communicate with each other.
Nortel recommends that you perform a firmware upgrade if you are using older
versions of firmware (release 1.3.4.x or earlier). To check the version of
firmware you are using, do one of the following:
If you are not connected to the device, open Configuration Manager and
connect to the Remote Gateway 9100 Series unit. A window displays the
RLC or Remote Gateway 9100 Series unit firmware version.
If you are already connected to the device, choose System Information →
System Data. The unit firmware version displays.
WARNING
To eliminate any confusion in board numbering, the RLC
automatically sets its Unit ID to 254 with this release when
upgrading from releases prior to 1.2.0.
The RLC now identifies the Remote Gateway 9100 Series
units by their Unit ID, not by their Unit Number or Node Name.
If the Unit ID is not the same as the Unit Number in the
Remote Connection Configuration on the RLC, the Unit ID in
the 9150 or 911x System Configuration sheet must be
changed to match the Unit Number.
To maintain compatibility with all installations that support a
single Remote Gateway 9100 Series unit, the upgrade
process assigns the default Unit ID of “1” to each unit to match
the default at the RLC. Following an upgrade, administrators
responsible for multiple Remote Gateway 9100 Series units on
a single RLC must configure the correct Unit ID at each
Remote Gateway 9100 Series unit.
141.6.0 Release Notes for Remote Gateway 9100 Series and RLC
June 2005
Operation
This section provides important information about the operation of the Remote
Gateway 9100 Series units.
Classless Inter-Domain Routing (CIDR) capability
The Remote Gateway 9100 Series family of products does not support Classless
Inter-Domain Routing (CIDR), also called supernetting. A CIDR example is a
Class C IP Address with a Class B IP Network Mask as follows:
RLC - Class C IP Address 192.168.1.1 with a Class B IP Network Mask
255.255.0.0
9150 - Class C IP Address 192.168.1.1 with a Class B IP Network Mask
255.255.0.0
ICMP re-directs result in the RLC and Remote Gateway 9150 unit
losing connectivity
Internet Control Message Protocol (ICMP) re-directs are not supported by the
Remote Gateway 9100 Series family of products when the IP Network Mask
sent does not adhere to the current IP Network Mask configured in Remote
Gateway 9100 Seriess Configuration Manager. An ICMP re-direct, which is a
classless message (no mask identified), sent to a Remote Gateway 9100 Series
unit creates a routing table entry within the product that is based on the inherent
IP class mask not the configured class map.
For example, a Remote Gateway 9100 Series unit configured with a Class A IP
address and a Class B IP Network Mask that is sent an ICMP re-direct which
provides a Class A IP address entry, causes all traffic in the Class A scope to be
re-directed to the new path.
Nortel recommends that you only install the Remote Gateway 9100 Series
family of products with one gateway on the subnet.
1.6.0 Release Notes for Remote Gateway 9100 Series and RLC15
Standard 1.0
Use of Speed Call feature
When you are using a Speed Call feature in conjunction with the Remote
Gateway 9100 Series product, you must configure the host PBX for Class of
Service CNDA for each TN. Configuring Class of Service CNDA ensures that
the Remote Gateway 9100 Series product does not incorrectly detect an
emergency 911 call.
161.6.0 Release Notes for Remote Gateway 9100 Series and RLC
June 2005
Issues Corrected Since 1.5.2
The following issues have been corrected since product release 1.5.2:
M3902 digital telephone sets connected to Remote Gateway 9150
units audio level (Q00969221)
When making a telephone call using an M3902 digital telephone set, speech
became faint. An unexpected Handsfree On message was being sent to an
M3902 digital telephone set whose Handsfree Allowed (HFA) Class of Service
was not programmed on the host PBX. In this case, the audio level of the M3902
digital telephone set would be drastically lowered and remain in the state until
the M3902 digital telephone set was re-set. Pressing the hookswitch quickly
several times in a row would induce this problem. The Remote Gateway 9150
unit now blocks the transmission of handsfree microphone related messages for
digital telephone sets with handsfree disabled.
ACD agents not receiving the call force tone (Q01021293)
Agents were receiving the ACD force tone, but not until after the call was
actually connected and the agent had already heard the far end answer. The
Remote Gateway 9150 unit’s firmware now prevents the call force tone to the
ACD agent in a more expedited manner to prevent this from occurring.
1.6.0 Release Notes for Remote Gateway 9100 Series and RLC17
Standard 1.0
The ISDN link between the RLC and Remote Gateway 9100 Series
units is always up because of lamp audit (Q01058550)
When the RLC was connected through the PSTN to the Remote Gateway 9100
Series units and the lamp audit would run with no active calls, the data port of
the RLC would dial the ISDN line of the Remote Gateway 9100 Series units. A
new X11 message was added for M39xx series digital telephone sets that would
send an Icon Status message to the M39xx series digital telephone set during
Lamp Audit. This was a new message that the Remote Gateway 9100 Series
product did not recognize and was therefore passing it to the Remote Gateway
9100 Series units each time it was received. In an on-demand connection
environment, this was causing the signaling link to be established each
successive time. The Remote Gateway 9100 Series firmware is now aware of
this new message type and prevents redundant transmission of this message
during a lamp audit.
During a transfer on a Remote Gateway 9150 unit, a local call is
inbound (Q01080804)
When a second inbound local ISDN call was received, while the telephone user
was in the middle of transferring an already received local ISDN call, the second
inbound call was dismissed from the digital telephone set once the telephone
user completed the transfer of the initial inbound call. The Remote Gateway
9150 units firmware now includes logic to handle the second inbound call
correctly when a transfer is progressing on the first inbound call.
In CS 2100 PBX environments, the Remote Gateway 9150 unit
produces a one-way voice path (Q01098111)
In CS 2100 PBX environments, the Remote Gateway 9150 unit was producing a
one-way voice path after picking up a call that was on hold. The Remote
Gateway 9150 firmware is now aware of Key Map Download (KMDs)
messages on their way to the digital telephone set and establishes the switch type
accordingly to the CS 2100 PBX. The Remote Gateway 9150 unit no longer
produces a one-way voice path.
181.6.0 Release Notes for Remote Gateway 9100 Series and RLC
June 2005
Remote Gateway 9150 unit experiences upexpected warm re-starts
(Q01110229)
During normal operation, Remote Gateway 9150 units were experiencing
spontaneous warm re-starts. This release addresses the spontaneous warm
re-start issue on the Remote Gateway 9150 unit.
1.6.0 Release Notes for Remote Gateway 9100 Series and RLC19
Standard 1.0
Known problems in this release
This section describes known problems with this release and suggests solutions
to these problems, if solutions are available.
M3902 digital telephone sets connected to Remote Gateway 9150
units connected to CS 1000 PBXs have display irregularities in
survivable mode (Q00352179)
When CS 1000 PBXs go into survivable mode, M3902 digital telephone sets
connected to Remote Gateway 9150 units connected to these PBXs react
abnormally. These digital telephone sets temporarily present abnormal messages
in their telephone set displays.
RLC maintenance LED stays off when RLC is disabled using DISS
command in Load 32 on CS 1000 PBXs (Q00352255)
Maintenance LEDs on RLCs installed in CS 1000 PBXs do not respond
properly to the Load 32 (LD32) command, Disable Shelf (DISS). The LED is
off, or dark, when the RLC is operating correctly. The LED’s being on, or lit,
usually indicates that the RLC is disabled or experiencing some sort of a
problem. When the maintenance LED remains off after you enter the DISS
command, enter the Disable Card (DISC) command for that card.
After you re-set the configuration of a Remote Gateway 911x series unit,
altering the unit's configuration with the Configuration Wizard results in the
following error: 1250 - Invalid Command. After re-setting the configuration of a
Remote Gateway 911x series unit, you must re-enter the configuration manually.
201.6.0 Release Notes for Remote Gateway 9100 Series and RLC
June 2005
M3905 digital telephone sets do not play tone B for a second
incoming call (Q00557165)
If an M3905 digital telephone set is on a call when another call comes in, it does
not alert the user by playing tone B. The only indication that the user has of a
second incoming call is the flashing of the call indicator.
After re-boot of Remote Gateway 9150 unit, ATA port does not work
(Q00659815)
After re-boot of a Remote Gateway 9150 unit, the ATA port does not work. As a
work around, re-boot each ATA as well.
Comfort noise does not accurately track background noise
(Q00666182)
The Remote Gateway 9100 Series product does generate comfort noise, but at a
fixed level. This issue can cause noise pumping to occur. When the “silent”
party starts speaking again, the noise floor can change and it can be noticeable.
You can avoid this by disabling VAD.
Display Log number 93 is not always logged (Q00688016)
Display Log number 93 is not logged when dialing from the local key. This log
indicates that the Emergency Access Code (EAC) has been dialed from a port.
When an Emergency number is dialed using the local key, it does not display in
the Display Logs.
Multiple sets with Call Forward on local BRI inbound call are not
treated correctly (Q00699973)
When placing two or more digital telephone sets in DN's to Alert Trunk Group
mode and placing two or more of these same digital telephone sets in Call
Forward to a PBX DN mode, multiple digital telephone sets with Call Forward
on a local BRI inbound telephone call are not treated correctly. The single
incoming BRI telephone call gets answered and does not terminate the second or
more Call Forward telephone call.
1.6.0 Release Notes for Remote Gateway 9100 Series and RLC21
Standard 1.0
Cannot access the Remote Gateway 911x series unit with an IP
interface (Q00764649)
The ARP table on the PC connected with a cross-connect cable does not time
out. It still associates the previous MAC address with the IP address. When the
Remote Gateway 911x series unit originates a PING, the table is updated with
the new MAC and all begins to function properly. This problem can be resolved
by entering an “arp -d” command on the PC to clear the ARP table.
Signaling link is lost on a normal closure over PSTN after a QoS
transition (Q00795922)
When you configure signaling for Permanent mode over IP and On-demand
mode over PSTN, the RLC generates an abnormal failure over PSTN after being
cleared normally due to an Idle condition detected. If after the QoS transition
occurs, additional B-channels are established, the problem does not occur.
Remote Gateway 9150 unit does not reconnect after a failed PSTN
test (Q00810610)
The following scenario describes the instance where the Remote Gateway 9150
unit is not reconnecting after a failed PSTN connectivity test:
Configure the RLC and Remote Gateway 9150 unit for PSTN only mode.
Perform a disruptive PSTN connectivity test. If the test fails, the Remote
Gateway 9150 unit stays in a state where it no longer attempts to connect when
the user presses a DN key to initiate a re-connection to the RLC.
To resolve this issue, re-set the Remote Gateway 9150 unit so that it can
reconnect to the RLC.
221.6.0 Release Notes for Remote Gateway 9100 Series and RLC
June 2005
The Display Logs shows incorrect DSP Resource Allocation
messages when under QoS (Q00831871)
The following scenario describes the instance when the Display Logs are
showing incorrect DSP Resource Allocation messages when under QoS:
The Remote Gateway 911x series unit is being used over IP with PSTN fallback
enabled and the unit is in fallback mode. The Remote Gateway 911x series unit
user places a local call, thus dropping the PSTN connection to the RLC. If a call
is attempted from the host PBX to the Remote Gateway 911x series unit, the
RLC logs the following, for example:
055 JAN28 10:22 CallInfo Voice call did not succeed to Remote Site:9, due
to: No BW [BW required 8.000000, Priority 2]
029 JAN28 10:22 CallInfo DSP Resource Allocation failed on Port 9
029 JAN28 10:22 CallInfo DSP Resource Allocation failed on Port 9
029 JAN28 10:22 CallInfo DSP Resource Allocation failed on Port 9
Display Log 55 is correct, there is no bandwidth. Display Log 29 is incorrect
because there are DSPs available.
RLC dials Remote Gateway 911x series unit when it should not
(Q00832974)
The following scenario describes the instance where the RLC is dialing the
Remote Gateway 911x series unit when it should not:
Configure the RLC and Remote Gateway 911x series unit for IP with PSTN
fallback. In this configuration, the RLC should not dial the Remote Gateway
911x series unit. It is always the Remote Gateway 911x series unit that should
dial the RLC to prevent local key confusion.
1.6.0 Release Notes for Remote Gateway 9100 Series and RLC23
Standard 1.0
The Display Logs are filled when the Remote Gateway 911x series
unit user places a local call and interrupts the PSTN connection
(Q00833068)
The following scenario describes the instance when the Display Logs are filled
when the Remote Gateway 911x series unit user places a local call and interrupts
the PSTN connection:
When Remote Gateway 911x series unit user pressed the local key and interrupts
the current PSTN connection between the RLC and Remote Gateway 911x
series unit, the Remote Gateway 911x series unit logs the following:
045 JAN29 10:32 CallInfo Primary trunk dropped to place 911 call
Display Log 45 is not correct in this case as the Remote Gateway 911x series
unit user did not place a 911 call. The Remote Gateway 911x series unit user
placed a normal local call.
Double digits are dialed if you press the digital telephone set
(connected to a Remote Gateway 911x series unit) keys rapidly
(Q00856590)
This problem is a timing issue between the messaging from the host PBX and
the messaging from the Remote Gateway 911x series unit itself.
In this scenario, the digital telephone set connected to the Remote Gateway 911x
series unit transmits a DN key press to the host PBX. This causes the host PBX
to light the DN indicator. When this message is received by the RLC, the
message causes the RLC to allocate a voice path to the Remote Gateway 911x
series unit. This takes approximately 250-300ms and during that time, all other
messaging to the digital telephone set is blocked. If during this window of time,
you press an additional key, such as a DTMF key, the digital telephone set is still
in the IDLE state and interprets the key press as being a pre-dialed digit. The
digit is forwarded to the host PBX and the host PBX accepts it as a dialed digit,
knowing that the set is already off-hook. At some point later, the digital
telephone set receives the UCPS: DialTone state message causing it to transmit
any pre-dialed digits. This causes the digit to be transmitted again, leading to the
double digit press scenario.
241.6.0 Release Notes for Remote Gateway 9100 Series and RLC
M3904 digital telephone sets connected to the Remote Gateway 9150 unit lose
manually entered key feature labels on the DBA key. This occurs with M3904
digital telephone sets and DBA add on modules. The DBA keys are BFS keys on
the host PBX.
Manually entered DBA keys should maintain the key label. However, after a
couple of days the manually entered DBA key labels become scrambled. The
DBA key still functions although the key label is no longer configured correctly.
To correct this issue, re-configure the DBA keys manually through the M3904
digital telephone set.
Software reset on the Remote Gateway 911x series unit over PSTN
causes the M39xx digital telephone sets to not operate (Q00910329)
When the Remote Gateway 911x series unit is connected over PSTN and reset
through software, the M39xx digital telephone set does not operate. The M39xx
digital telephone is in a bad state. The M39xx digital telephone set does not
respond to key presses. The assigned key labels do not always display. To
resolve this issue, reset the M39xx digital telephone set.
Configuring MADNs from a CS 2100 PBX rings a local only digital
telephone set connected to the Remote Gateway 9150 unit
(Q00950744)
If you configure MADNs from a CS 2100 PBX, the CS 2100 PBX rings a local
only digital telephone set connected to the Remote Gateway 9150 unit. Do not
configure MADNs on CS 2100 PBX for local only digital telephone sets
connected to Remote Gateway 9150 unit.
1.6.0 Release Notes for Remote Gateway 9100 Series and RLC25
Standard 1.0
MADN indicator on digital telephone sets connected to Remote
Gateway 9150 units connected to CS 2100 PBXs remains lit when you
SPRE offline (Q00950865)
The following describes the scenario in a CS 2100 PBX environment where the
MADN indicator remains lit when you SPREE offline:
Digital telephone set A is connected to a Remote Gateway 9150 unit connected
to CS 2100 PBX. Digital telephone set B key 10 is a MADN of digital telephone
set A. Digital telephone set A dials a SPRE code to go offline. The digital
telephone set B key 10 MADN indicator remains lit after the Remote Gateway
9150 unit goes offline.
The work around is to SPRE offline using digital telephone set B.
In CS 2100 PBX environments, DBAs do not display feature key labels
when connected to Remote Gateway 911x series units (Q00953356)
If you configure Auto Dial and DN keys on DBAs from the CS 2100 PBX and
attach the DBAs to digital telephone sets connected to a Remote Gateway 911x
series units, the DBAs do not display the feature key labels. However, the
features operate properly. The work around is to manually place labels on the
DBA keys for the particular features.
Upgrading the Remote Gateway 911x series unit to product release
1.5.x in CS 2100 PBX environments generates an override error
message (Q00968561)
When upgrading a Remote Gateway 911x series unit that resides in a CS 2100
environment to product release 1.5.x and using the Syslog feature, the Remote
Gateway 9100 Series product generates CS 2100 PBX alarm and alert when it
should not. In addition, Syslog 067 – Port P1: Local Feature Overrides PBX
Feature on key P2 – displays in the Syslog.
261.6.0 Release Notes for Remote Gateway 9100 Series and RLC
June 2005
Intermittent Call Party Name display corruption on M3903 digital
telephone set (Q00970580)
When receiving an inbound ISDN call to an M3903 digital telephone connected
to the Remote Gateway 9150 unit, the call is answered successfully. However,
the M3903 digital telephone set display is intermittently corrupted and does not
always display the correct Calling Line Indication (CLID) and Call Party Name
information.
1.6.0 Release Notes for Remote Gateway 9100 Series and RLC27
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.