Avaya R2MFC Release Notes

  • Hello! I am an AI chatbot trained to assist you with the Avaya R2MFC Release Notes. I’ve already reviewed the document and can help you find the information you need or explain it in simple terms. Just ask your questions, and providing more details will help me assist you more effectively!
RESTRICTED
RNxB25AAxx_SW1.2.doc Nov.10, 2005
R2MFC SW release notes
For f/w Version 1.2
Proprietary Issue 1.2
Author: Jerry Freestone Approved by:
Department: 9D40
Keywords BCM, Norstar, R2MFC
Abstract This document describes the firmware Release Notes for the R2MFC software
release 1.2.
Security classification downgrading: Refer to Northern Networks Corporate procedures
Declassify Never
Funder
Prime
Case
(c) 2000 Northern Networks Ltd.
This document contains restricted, proprietary, copyrighted
information, ownership of which is retained by Nortel
Networks. Nortel Networks consent is required prior to any
reproduction, publication or other use of such information.
RNxB25AAxx_SW1.2.doc -i- Issue 1.2
Table of Contents
REVISION HISTORY...............................................................................................................................III
1 INTRODUCTION.................................................................................................................................1
2 FIRMWARE VERSION CODES........................................................................................................1
3 EQUIPMENT REQUIREMENTS/COMPATIBILITY ....................................................................1
4 FEATURES SUPPORTED...................................................................................................................1
4.1 COUNTRY SUPPORT.......................................................................................................................2
4.2 CUSTOM CONFIGURATION ...........................................................................................................2
4.3 SECOND DIAL TONE......................................................................................................................2
4.4 CLI CONFIGURATION TOOL..........................................................................................................3
5 KNOWN ISSUES..................................................................................................................................3
6 KNOWN LIMITATIONS.....................................................................................................................3
RNxB25AAxx_SW1.2.doc -ii- Issue 1.2
Revision History
Issue 1.1 April 25, 2005 First release.
Issue 1.2 Nov.10, 2005 Updated for Norstar
RNxB25AAxx_SW1.2.doc -iii- Issue 1.2
1 Introduction
This document contains release notes R2MFC software version 1.2. These notes should
be used (along with the quicksheet in the box) to determine compatibility and the best
way to configure the MBM.
This software can be used on both the Norstar R2 trunk card and BCM R2MFC modules.
Please see the installation guide for specific functionality with each system.
2 Firmware Version Codes
The software release is 1.2 but in the CLI interface the software version (build version)
will be 1.22.
3 Equipment Requirements/Compatibility
This software is designed to work the R2MFC MBM in a BCM system. The software is
also designed to work in the Norstar R2MFC trunk module with clock services card.
Please see the appropriate installer guide for minimum system level requirements to use
an R2MFC MBM/trunk module.
4 Features Supported
Release 1.2 software is designed to support of the functionality detailed in the user
guide. Generic configuration of the module is done through the dipswitches on the front
of the module.
configuration
ON
dialtone
country
diagnostic
s
123456
O
N
Specific changes to R2 parameters are done through the CLI tool with a PC.
RNxB25AAxx_SW1.2.doc -1- Issue 1.2
4.1 Country Support
Release 1.1 software supports 5 different variants for R2MFC via the dipswitches on the
front of the module.
123456
Mexico 1
Brazil 1
Mexico
2
123456
123456
Although these rules won’t always apply, (will depend on the specific switch
configurations) the settings roughly translate as follows:
Profile Tested Telco E1 City or Region
Mexico1 Telmex South East Mexico
Mexico2 Telmex Mexico City, Guadalajara
Brazil1 Embratel, Telefonica Sao Paulo
4.2 Custom Configuration
Custom configurations are done through the CLI tool. The dipswitches must be in custom
configuration mode (below) to support a custom configuration.
NOTE: The custom configuration must be saved in the CLI or the configuration will be lost with
power down.
Custo
m
Profile
123456
4.3 Second Dial Tone
The second dial tone feature will provide an artificial dial tone if the if the feature is turned on and
the dialing mode is set to overlap mode. See the install guide for more details.
Disabled
123456
RNxB25AAxx_SW1.2.doc -2- Issue 1.2
Enabled
123456
4.4 CLI configuration tool
The Command Line Interface (CLI) tool is used to check configuration settings, modify
configuration settings and access the on board diagnostic tools. See the installer guide for more
information.
5 Known Issues
TBD
6 Known Limitations
Brazil-1 default configuration cannot work in a tandem BCM switch configuration
because the inbound MFC dialing is limited to 4 digits. The can be changed as a custom
configuration through the CLI interface. Please see the installation manual for details on
how to change the number of incoming digits.
7 Release Deltas
Release 1.16 GA release
Release 1.17
Changes:
1) PRI dial mode is protected against corruption:
a. On startup, if this value is read from EEPROM, it is checked. If invalid value, it's corrected to
the default (overlap) and a SWERR message is printed: "tpc_root: priDialTypeOG corrupted"
b. CLI command SDT (SetDialType) in directory PRI displays the dial type; now it also indicates
if the value is invalid.
c. In call process, if the dial type value is invalid, "overlap sending" is used. (Before this fix it
caused a bad PRI-SETUP message).
Release 1.22
CLI changes :
- Directory INFO
Command Alarm – new command to print a summary of E1 alarms on both links
Command ChannelSummary – new command to print a summary of all slots currently in use on
both the PRI and MFC links.
RNxB25AAxx_SW1.2.doc -3- Issue 1.2
Command ChannelDetails – new command to dump all database information about current
connections. Note that a) the information is intended for programmer use, and b) the command
should be used only when ChannelSummary shows about 2 or 3 connections maximum
(because it produces a lot of output).
- Directory MFC
Command AniOpt - works for Outgoing calls as well.
Command mfcINDia - prints syntax correctly.
- Directory MFC
Command mfcSigPwrLvl – prints/changes the MFC signals’ power level.
- Directory INFO
Command CallDetails – duplicate printing removed.
Functional Issues solved :
- Argentine profile :
End of ANI digits is signalled with I-15.
No ANI digits available is signalled with I-12.
- Channel 31 stuck at Kluber site :
Processing change to prevent recurrence. If the MBM thinks that the channel chosen by the BCM
is not idle, then it will swerr, clear the channel and process the new request from the BCM.
- Regret time problem in Brazil (found during Verification testing) :
Scenario: Outgoing call BCM to CO; CO goes onhook starting the regret timer. BCM user stays
listening to dead air until the end of the regret time period. Problem: BCM line not able to receive
incoming calls, until it makes an outgoing call.
- MFC Signal strength in Brazil :
Brazilian profiles will set the outgoing MFC signals to –8db. All other profiles will remain at the
original level of –10db.
- Sensitivity of E1 alarm detection :
The sensitivity of the E1 alarm processing has been moderated to preclude the failure of calls
during PI testing.
RNxB25AAxx_SW1.2.doc -4- Issue 1.2
/