Lucent Gateway Platform System Maintenance Release Notes

Part Number 255-400-006R3.9.0.9 Issue 1, October 4, 2005 Software Version 3.9.0.9

Copyright 2005 Lucent Technologies All Rights Reserved

Lucent Gateway Platform System Maintenance Release Notes

This material is protected by the copyright and trade secret laws of the United States and other countries. It may not be reproduced, distributed, or altered in any

fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements,

contracts or licensing, without the express written consent of Lucent Technologies and the business management owner of the material.

Information Products & Training (IP&T):

Notice

Every effort has been made to ensure that the information in this document was complete and accurate at the time of printing. However,

information is subject to change.

Mandatory customer information

Trademarks

All trademarks and service marks specified herein are owned by their respective companies.

Ordering information

The order number of this document is 255-400-006R3.9.0.9.

Support

Technical support

Please contact your Lucent Technologies Local Customer Support Team (LCS) for technical questions about the information in this document.

Information product support

To comment on this information product online, go to http://www.lucent-info.com/comments or email your comments to [email protected].

Installation and Operations Manual 3.9.0.9 System Release Notes

Section 110-250-004 Issue 1, October 4, 2005

Lucent Technologies, Inc. 3 of 26

Table of Contents

1. Scope........................................................................................................................4

2. Upgrade Files ...........................................................................................................4

3. Upgrade Notes .........................................................................................................4

3.1 In-Service Upgrade (from 3.9.0.8)...............................................................4

3.2 In-Service Upgrade (from 3.9.0.8.SP.12) ....................................................6

3.3 In-Service Upgrade (from 3.9.07.SP.13) .....................................................7

4. EMS/Billing/Traffic Server Qualification ...............................................................9

5. Product Improvements for Maintenance Release 3.9.0.9 ........................................9

5.1 Resolved Error Defects ................................................................................9

6. Hardware Limitations and Issues...........................................................................15

7. Software Limitations and Issues ............................................................................17

7.1 Equipment Management Issues .................................................................17

7.1.1 DS3 IOM Limitations ....................................................................19

7.1.2 STS-1 Limitations..........................................................................19

7.1.3 Ethernet Network Access (ENA)...................................................19

7.1.4 Voice Server Modules....................................................................20

7.2 Primary Rate ISDN Line Limitations ........................................................20

7.3 SS7 and ISDN Signaling Issues.................................................................20

7.4 SS7 and BICC Limitation ..........................................................................21

7.5 BICC Limitations.......................................................................................21

7.6 CAS Signaling Limitations ........................................................................21

7.7 Integrated VoIP Limitations ......................................................................21

7.8 Intelligent Networks Restrictions ..............................................................22

7.9 Call Processing Limitations .......................................................................22

7.10 Session Initiation Protocol (SIP), MGCP and GR-303 Limitations ..........24

7.11 IntVoIP/SIP/MGCP CODEC Negotiation Limitations .............................24

7.12 GR-303 Limitations ...................................................................................25

7.13 System Software Limitations.....................................................................25

7.14 TL1 Restrictions and Security Errata.........................................................25

7.15 Security ......................................................................................................26 26

25

25

25

24

24

22

22

21

21

21

21

20

20

20

19

19

19

17

17

15

9

9

9

7

6

4

4

4

4

3.9.0.9 System Release Notes Installation and Operations Manual

Issue 1, October 4, 2005 Section 110-250-004

4 of 26 Lucent Technologies, Inc.

1. Scope

This document provides detailed information regarding system software

maintenance release 3.9.0.9 for the System Processor (SP). Topics

covered are:

Upgrade file contents and notes

Product limitations

Product improvements

Version 3.9 is a Class 4 release with limited class 5 capability. In

particular, CALEA and Inter-Switch Voice Mail are not supported. It is

not recommended that customers deploy 3.9 as a CLASS 5 switch due to

the CALEA restriction.

All hardware supported by release 3.9.0.9 is listed by CLEI code and part

number in your copy of the Planning and Engineering Guide. This

information is listed under the Part Information tab in the manual.

2. Upgrade Files

The following files and objects are required to upgrade to version 3.9.0.9:

3.9.0.9.tar.gz

3.9.0.9_cpu.tar.gz

3.9.0.9_ds1.tar.gz

3.9.0.9_ds3.tar.gz

3.9.0.9_octds3.tar.gz

3.9.0.9_octds3_2.tar.gz

3.9.0.9_octds3_3.tar.gz

3.9.0.9_trids3.tar.gz

3.9.0.9_trids3_3.tar.gz

3.9.0.9_ena.tar.gz

3.9.0.9_voip.tar.gz

3.9.0.9_voip6.tar.gz

3. Upgrade Notes

3.1 In-Service Upgrade (from 3.9.0.8)

An in-service upgrade from version 3.9.0.8 to version 3.9.0.9 is

supported. For instructions on performing the in-service system

processor upgrade, contact Lucent Worldwide Services (LWS) at




1-866-582-3688 (Option 5). An LWS representative will refer

you to DLP-545, which contains specific steps for completing the

in-service system processor upgrade. DLP-545 can be obtained

from your LWS representative.

Important: The IOMs must be at the following versions prior to

performing the in-service upgrade to 3.9.0.9:

Supported

IOM Type

Part

Number

CLEI Version

DS1 89-0360-A BA9IAA0AAA 3.9.0.8

89-0365-C BA9IX72AAA 3.9.0.8

89-0397-A BA9IX04AAA 3.9.0.8

Triple DS-3/STS-1

89-0410-A BA4A60ZFAA 3.9.0.8

89-0382-B BAA9UVZGAA 3.9.0.8

89-0398-A BAA9UVXGAA 3.9.0.8

Octal DS-3/STS-1

89-0411-A BA4A701FAA 3.9.0.8

High Performance

Triple DS-3

89-0424-A BA9AWX0FAA 3.9.0.8

High Performance

Octal DS-3

89-0425-A BA9AXY0FAA 3.9.0.8

VPS 89-0384-A BAA9Z20GAA 3.9.0.8

VPS8 89-0395-A BA1AX60AAA 3.9.0.8

ENA 89-0390-A BA2A30TGAA 3.9.0.8

For instructions on performing an in-service IOM upgrade, contact

LWS. An LWS representative will refer you to DLP-668, which

contains specific steps for completing an IOM upgrade. DLP-668

can be obtained from your LWS representative.

Important: After upgrading the system processor, you should

check the versions of the IOMs and upgrade, if necessary. For

instructions on performing an in-service IOM upgrade, contact


contains specific steps for completing the upgrade. DLP-668 can

be obtained from your LWS representative.

Supported

IOM Type

Part

Number

CLEI Version

DS1 89-0360-A BA9IAA0AAA 3.9.0.9

89-0365-C BA9IX72AAA 3.9.0.9

89-0397-A BA9IX04AAA 3.9.0.9

Triple DS-3/STS-1

89-0410-A BA4A60ZFAA 3.9.0.9

89-0382-B BAA9UVZGAA 3.9.0.9 Octal DS-3/STS-1

89-0398-A BAA9UVXGAA 3.9.0.9




Supported

IOM Type

Part

Number

CLEI Version

89-0411-A BA4A701FAA 3.9.0.9

High Performance

Triple DS-3

89-0424-A BA9AWX0FAA 3.9.0.9

High Performance

Octal DS-3

89-0425-A BA9AXY0FAA 3.9.0.9

VPS 89-0384-A BAA9Z20GAA 3.9.0.9

VPS8 89-0395-A BA1AX60AAA 3.9.0.9

ENA 89-0390-A BA2A30TGAA 3.9.0.9

3.2 In-Service Upgrade (from 3.9.0.8.SP.12)

An in-service upgrade from version 3.9.0.8.SP.12 to version

3.9.0.9 is supported. For instructions on performing the in-service

system processor upgrade, contact Lucent Worldwide Services

(LWS) at 1-866-582-3688 (Option 5). An LWS representative

will refer you to DLP-545, which contains specific steps for

completing the in-service system processor upgrade. DLP-545 can




Supported

IOM Type

Part

Number

CLEI Version

DS1 89-0360-A BA9IAA0AAA 3.9.0.8.2

89-0365-C BA9IX72AAA 3.9.0.8.2

89-0397-A BA9IX04AAA 3.9.0.8.2

Triple DS-3/STS-1

89-0410-A BA4A60ZFAA 3.9.0.8.2

89-0382-B BAA9UVZGAA 3.9.0.8.2

89-0398-A BAA9UVXGAA 3.9.0.8.2

Octal DS-3/STS-1

89-0411-A BA4A701FAA 3.9.0.8.2

High Performance

Triple DS-3

89-0424-A BA9AWX0FAA 3.9.0.8.2

High Performance

Octal DS-3

89-0425-A BA9AXY0FAA 3.9.0.8.2

VPS 89-0384-A BAA9Z20GAA 3.9.0.8.6

VPS8 89-0395-A BA1AX60AAA 3.9.0.8.6

ENA 89-0390-A BA2A30TGAA 3.9.0.8.1














Supported

IOM Type

Part

Number

CLEI Version

DS1 89-0360-A BA9IAA0AAA 3.9.0.9

89-0365-C BA9IX72AAA 3.9.0.9

89-0397-A BA9IX04AAA 3.9.0.9

Triple DS-3/STS-1

89-0410-A BA4A60ZFAA 3.9.0.9

89-0382-B BAA9UVZGAA 3.9.0.9

89-0398-A BAA9UVXGAA 3.9.0.9

Octal DS-3/STS-1

89-0411-A BA4A701FAA 3.9.0.9

High Performance

Triple DS-3

89-0424-A BA9AWX0FAA 3.9.0.9

High Performance

Octal DS-3

89-0425-A BA9AXY0FAA 3.9.0.9

VPS 89-0384-A BAA9Z20GAA 3.9.0.9

VPS8 89-0395-A BA1AX60AAA 3.9.0.9

ENA 89-0390-A BA2A30TGAA 3.9.0.9

3.3 In-Service Upgrade (from 3.9.0.7.SP.13)

An in-service upgrade from version 3.9.0.7.SP.13 to version

3.9.0.9 is supported. For instructions on performing the in-service

system processor upgrade, contact Lucent Worldwide Services

(LWS) at 1-866-582-3688 (Option 5). An LWS representative

will refer you to DLP-545, which contains specific steps for

completing the in-service system processor upgrade. DLP-545 can




Supported

IOM Type

Part

Number

CLEI Version

DS1 89-0360-A BA9IAA0AAA 3.9.0.7.4

Triple DS-3/STS-1 89-0365-C BA9IX72AAA 3.9.0.7.4




Supported

IOM Type

Part

Number

CLEI Version

89-0397-A BA9IX04AAA 3.9.0.7.6

89-0410-A BA4A60ZFAA 3.9.0.7.6

89-0382-B BAA9UVZGAA 3.9.0.7.7

89-0398-A BAA9UVXGAA 3.9.0.7.7

Octal DS-3/STS-1

89-0411-A BA4A701FAA 3.9.0.7.7

High Performance

Triple DS-3

89-0424-A BA9AWX0FAA 3.9.0.7.7

High Performance

Octal DS-3

89-0425-A BA9AXY0FAA 3.9.0.7.7

VPS 89-0384-A BAA9Z20GAA 3.9.0.7.7

VPS8 89-0395-A BA1AX60AAA 3.9.0.7.7

ENA 89-0390-A BA2A30TGAA 3.9.0.7.1











Supported

IOM Type

Part

Number

CLEI Version

DS1 89-0360-A BA9IAA0AAA 3.9.0.9

89-0365-C BA9IX72AAA 3.9.0.9

89-0397-A BA9IX04AAA 3.9.0.9

Triple DS-3/STS-1

89-0410-A BA4A60ZFAA 3.9.0.9

89-0382-B BAA9UVZGAA 3.9.0.9

89-0398-A BAA9UVXGAA 3.9.0.9

Octal DS-3/STS-1

89-0411-A BA4A701FAA 3.9.0.9

High Performance

Triple DS-3

89-0424-A BA9AWX0FAA 3.9.0.9

High Performance

Octal DS-3

89-0425-A BA9AXY0FAA 3.9.0.9

VPS 89-0384-A BAA9Z20GAA 3.9.0.9

VPS8 89-0395-A BA1AX60AAA 3.9.0.9

ENA 89-0390-A BA2A30TGAA 3.9.0.9




4. EMS/Billing/Traffic Server Qualification

Element Management Server (EMS) version 9.6.2.0 or higher is

required for 3.9.0.9.

TelicaPlexusDc (BTS) version 3.9.0.8.7 or higher is required for

3.9.0.9.

Traffic Collection Application (TCA) 2.0.0.92 or higher is required for

3.9.0.9.

5. Product Improvements for Maintenance Release 3.9.0.9

The following enhancements have been made to the 3.9.0.9 maintenance

release of the SP software.

5.1 Resolved Error Defects

Tracking

Number

Symptom

1152 RTRV-INFO-EQPT should not show previously equipped

information.

9899 DMS-100 is missing mandatory IE in first response to SETUP

message.

28150 CDRs are not being generated for failed calls.

28249 TL1 RTRV-INFO-EQPT command is showing VSM-2 IOMs

as having rear cards.

28710 Deleting Route-Digits DEFAULT-TNS-NOTPRSNT should

not be permitted.

29657,

34206

Ptime value in the sdp-profile is not overridden by the value in

the 200OK for G.711 and G.728 CODECs during actual

media flow.

29701 The exec-bulk-download command fails when the bulk

download file is on a different host.

30134 3.10: slave signaling core at ccUnexpEvent(no.7)

30438 ISUP <=> SIP call is causing a system signaling failure which

occurs upon receipt of a release from the SIP side of the call.

30563 Outgoing CDPN is not changed when changing NOA to

ABBREVPVT.

30603 Standby SP signaling failure occurred during overnight test.

32393 BTS fails to create STATS data file >2GB (large file support.

32397 EMS scheduled system backups are sometimes being started

one hour early.

32758 Serviceability enhancement to capture additional information

during VSM faults that are occurring due to DSP code

problems.




Tracking

Number

Symptom

32851 Two diversion headers are being used even though the

diversion count is equal to one and the OCN is not present.

32858,

31422

Repeated SP failures occurred during SIP to SIP traffic load

testing.

33018 Billing: Call transfer on No Reply call scenario is creating

CDR records with the same originating and terminating

number when the A party is PSTN, the B party is TDMA and

the C party is GSM.

33611 ANI indicator not set correctly when ANI is delivered.

33687 CDR field 164 (Predig) is 0 instead of 4 on 1+ ported number.

33941 CDR field 76 (FINSWGRPM) is not being populated for SIP

DAL-to-SIP WATS or SS7 DAL-to-SS7 WATS calls.

34230 011 calls from ISDN subscriber are failing when carrier

routing is used.

34333 Using an Overflow Treatment with Reroute results in non-

billable CDR.

34438 CICs that have unacknowledged RSC, BLO or UBL messages

are showing up as IDLE instead of TRANSIENT in RTRV-

SS7-TRK.

34686 ROUTE-DIGITS with an action configured to remove all 10

digits from the CdPN is not working correctly for an ISUP

trunk group that terminates to an ISUP trunk group in the

same node.

34688 SIP users are experiencing a double Ringback effect because

the LCS is performing an early bearer cut-through for SIP-to-

ISUP calls.

34749 Digit modification to strip Charge Number and insert it into

Calling Party Number is not working correctly for SS7-to-

ISDN calls.

34789 When deleting an IP address from a SIP trunk group, the IP

address is NOT deleted from the database on the standby SP.

34794 Customer is not able to process calls to local numbers that are

ported to an LRN if the LRN returned is not in the same

calling-area as the original CdPN.

34824 The standby SP faulted after receiving incorrect information

regarding the amount of database memory that was available

to be allocated.

34871 A SIP process failure caused the active SP to failover to the

standby SP due to the inability to find the call pointer that was

associated with a 481 message that was received.




Tracking

Number

Symptom

34874 A CAS-to-SIP call was waiting for an answer from the egress

SIP leg. During that time, the SIP leg released the call and

another incoming call was initiated on the same CAS trunk

group creating a failure condition, which resulted in a system

signaling failure.

34970 Customer enhancement request to generate the SIP FROM

header for ISDN-to-SIP calls in the following format (From:

Anonymous ) if the Calling Party Number has the presentation

indicator set to restricted or there is no Calling Party Number

parameter.

34976 Active SP failure occurred due to watchdog timeout on

ENTTUFS.

35047 Customer enhancement request to log the VSM-to-ENA

module mapping details.

35152 COT (*57) does not include traced number in the AMA

record.

35180 SP script files were missing after SP failover occurred.

35249 Enhancement to log kernel information to the

IomDebugLog.log file when an OS panic occurs (SP-3 only).

35251 System monitoring (watchdog) enhancements.

35262 SNMPtrap fails to send traps, if there is only one BTS

instance running on the system and the bindIp parameter in

.INI is not used.

35303 An incorrect cause code is sent when an ISDN call is

disconnected because of a bad PROGRESS message. The

cause code sent to the two sides is "switching equipment

congestion" instead of "mandatory I.E. missing" to the

terminating interface.

35402 ISDN-to-SS7 call fails when Access Transport in ACM is set

to "Progress indicator, with location as LOC_NETINTER

(network beyond internetworking point)" and ISDN IF is set

for DMS100.

35437 The call duration is being set to zero for SIP-to-SS7 answered

calls that are released due to far end SS7 suspend timer

expiration.

35453 800 Query is causing hung dialogues due to INAP decoding

and TCAP abort errors.

35493 Calls that are failing with a cause code of 41 are showing a

connect date that is equal to the date of the last switch cold

start.

35770 SS7 links are bouncing when the TL1 RTRV-PM-C command

is executed against an Octal IOM that has a high number of

T1 ports In-Service.




Tracking

Number

Symptom

35809 LRN field of module 720 is not populated correctly for non-

ported to non-ported call.

35825 SIP-to-ISDN call is causing the active SP to switch to

protection after having received a release from the SIP side.

35889 The wrong announcement is being played when a 1+7-digit

ISDN-to-SS7 intra-LATA Toll call is dialed.

35907 Stats: CCS and TRSUM reports are not being created for SIP

trunk groups.

35917 Inability to delete existing ROUTE-DIGITS.

36041 Carrier connect information is not being populated on call

forwarded calls (egress trunk group ownclass=EO).

36087 Serviceability enhancement to enhance the visibility of

activity on the slave SP by redirecting the slave SP logs to the

master SP filing system.

36099 ISUP-to-SIP calls are producing a memory leak in the SIP

system process.

36142 SP failover occurred during ISUP congestion due to incorrect

handling of buffered events.

36170 Customer enhancement request to make the ISUP T6 timer

setting applicable regardless of ingress signaling, as long as

egress is ISUP.

36261 SP failover occurred on CAS-to-SIP call when SIP

immediately released the call.

36281 Need support for an in-service upgrade to 89-0424/0425 cards

from 89-0398/0411 cards.

36555 Standby SP faulted after an ISDN interface was deleted.

36600 The SP switched to protection during error processing in

signaling.

36604 SP switched to protection after accessing previously released

memory block.

36666 ISUP reports TICS idle but RTRV-PM-TRKGRP reports

TICS are all OOS.

36717 Serviceability enhancement that retrieves the internal alarm

and condition IDs.

36812 Incoming call was received on a BICC CIC while reroute of

outgoing BICC call, using the same CIC, was in progress. The

resulting glare condition caused signaling to fail.

36859 Enhancement to provide more diagnostic information if the

standby SP reboots due to a particular panic.

36872 Enhancement to monitor CPU and memory utilization on the

SP slave processor.

36916 T1 stuck in OOS-AU,INIT&FAF state.

36918 SIP system process failure caused a failover to the Standby

SP.




Tracking

Number

Symptom

37032 Packets are not being sent on the outbound SIP call leg due to

upper case Content-Type.

37047 Outbound SETUP message does not contain the ChN/OCN of

the inbound IAM.

37230 Cannot make a 7 digit call when the NXX is also a valid NPA

within the rate center.

37296 Addition of tracing on the standby SP to get more information

for a particular call scenario failure.

37308 Add a SP slave 'failed to boot' timeout to detect slave failures

37398 OCN is not being sent in the outgoing SETUP message for

SIP-to-ISDN calls.

37457 BICC-to-SIP call is causing SP-B to SP-B relay channel 19

communication error - cause 1.

37462 System date reverts back to 1937.

37570 Diagnostic enhancement to save SP-2/SP-3 slave process

information into flash memory.

37594 BICC-to-SIP calls are failing.

37595 The alarm indicating that 75% of a CAS trunk group is OOS

is being generated even though all the DS0s are IS.

37629 Standby SP does not update the active SP if GoAhead is not

available.

37657 System process failure occurred on active SP after SP failover,

while standby SP syncing

37726 The EXEC-BULK-DOWNLOAD TL1 command is failing

due to a system timeout error.

37737 ENA (IOM-8) does not fail over after MaxIPTimeouts occurs.

37922 Previously dipped calls are intermittently being routed based

on the CdPN (LRN), even though the LRNs exist in the on-

switch database.

38135 Terminating Partition Routing is not working correctly.

38172 Time out occurs when multiple CAS lines belonging to

different CAS interfaces are deleted.

38219 SP failure occurred while resetting the CICs associated with

an adjacent/remote PC.

38242 SP failover occurred due to signaling process failure during

call capture.

38281 VSM failover occurred with MODULE_ERR_SKDB(67)

error.

38293 SP failure occurred while resetting the CICs associated with

an adjacent PC.

38302 Enhancement to preserve initial log file when numerous

reboots occur.

38313 Update failure occurred on the standby SP.




Tracking

Number

Symptom

38357 Disk management enhancement for writing of system logs and

core images before system reset/reboot.

38444 SP lost heartbeat to signaling and failed over due to running

statistics thread on a large database table.

38515 Aborting the memstat command with ctrl-c causes the utilty to

segmentation fault and dump core.

38680 Backup TAR files are not removed from the system backup

directory when the FTP transfer fails.

38713 IOM failure occurred and re-started for no apparent reason.

38743 SP-B relay channel 19 communication error (cause 8) with no

signaling core.

38825 Two ss7 links failed when the 3rd link was provisioned.

38837 CALL-CAPTVERBOSE does not show Route Advance.

38974 SIP system process memory leak.

39003 Changed current threshold crossing event to contain the

PmType name in the alarm instead of the number.

39132 Automatic Number Announcement only speaks the leading 7

digits of the originators ANI (NPA, NXX and 1st digit of

extension).

39134 Standby SP faulted upon receiving incorrect information

regarding database memory available to be allocated.

39159 Enhancement to capture additional information if EMF

database commands fail.

39221 LCS does not generate Generic Parameter per DigitMod.

39433 M3UA protocol down (pause).

39491 Active SP failure occurred with SP FAILURE: SP-A lost

heartbeat to mgcpa.

39493,

39501Standby signaling failure occurred.

39508 Cannot put A-link into service after moving it from a different

IOM.

39566 SP failovers occurred due to MGCP core and file system

corruption.

39635 SP failure occurred during SIP Auto-Attendant to number

with CFA

39696 SP-B process signaling timed-out waiting to synchronize with

protection SP.

39733 No audio on PSTN-to-SIP calls going over VSM in I/O slot 15

(or I/O slot-17 after switch to protection).

39761 SP failover occurred due to memory inconsistency during call

forwarding.

39874 Signaling failure occurred during cleanup of ISDN call.

39897 Not able to enter more than 50 entries in the screenlist.




Tracking

Number

Symptom

40509 Standby SP failure occurred during switch upgrade.

40536 Terminating Disconnect Timer is approx. 3 minutes and 30

seconds, instead of approx. 11 seconds.

40678 SP-A lost communication to SP-B.

40686 Successive SP failures are occurring on SS7-to-BICC call.

40898 ISDN link deletion failure caused the active SP to failover.

6. Hardware Limitations and Issues

The following hardware limitations are associated with release version

3.9.0.

A front SP-3 module, 89-406, requires a rear SP-3 module, 89-

0417, front switch fabric card (89-0363-D), and Midplane III

(chassis 85-3007 or 85-3008)

The high performance Triple and Octal DS-3 Front IOMs, 89-0424

and 89-0425 can be protected by corresponding 89-0424/0425

IOMs as well as by 89-0410/0411 IOMs.

Note: ISDN, MTP2, CAS and GR-303 peak signaling rates must

be taken into account when using a 89-0410/0411 to protect a 89-

0424/0425, since they support higher signaling rates than the 89-

0410/0411 IOMs (25%, or greater, depending on the signaling).

Note: They cannot be used to protect corresponding Triple and

Octal DS-3/STS-1 IOMs, part numbers 89-0397/ 0398/ 0410/0411,

since they do not support STS-1.

Note: They cannot be used to replace previously provisioned

Triple and Octal DS-3/STS-1 IOMs, part numbers 89-0397/ 0398/

0410/ 0411, since they do not support STS-1.

Class features configured by the ENT-SUBSCRIBER command

will not work in dual-processor mode. Class 5 customers must

configure their switch in single-processor mode. This means that

the calls per second performance will be approximately half for

Class 5 customers.

A Midplane II chassis (85-3004) or Midplane III chassis (85-3307)

requires an Octal rear-protection IOM on DS3 IOMs regardless of

whether the front IOMs are Octal or Triple DS3 IOMs (rear-

working IOMs can be Triples, but the protection IOM must always

be Octal).

An Octal rev. A IOM can be backed up with either an Octal rev. A

IOM or an Octal rev. B IOM; however, an Octal rev. B IOM can

only be backed up with an Octal rev. B IOM. IOM failover won’t




work if an Octal rev. B IOM tries to fail over to an Octal rev. A

IOM.

A Switch Fabric (SF) module must be inserted before its associated

SP module.

SF Rev. B or later is required for operation with Octal DS3 IOMs.

Chassis Part Number 85-3000, CLEI Code BAM9LJ0GRA, does

not support Octal IOMs.

Modules with the following CLEI codes are not supported in this

software version:

Quad OC12c Network Adapter Interface Module (89-

0388-A), CLEI code BAA91Z0GAA

Quad OC3/OC12c Network Adapter Interface Module (89-

0388-B), CLEI code BAA91Z0GAB

Quad OC12c Packet Interface Module (89-0392), CLEI

code BA1AAA0AAA

E1 IO Front Module (89-0396), CLEI code

BA2AV30GAA

GR-303 is supported on Triple DS3/STS-1, 89-0397/0410 (CLEI

BA9IX04AAA, BA4A60ZFAA), and Octal DS3/STS-1,

89-0398/0411 (CLEI BAA9UVXGAA, BA4A701FAA).

GR-303 is not supported on the DS1 module or the Triple DS3,

CLEI Code BA9IX70AAA and BA9IX70AAB (89-0365-A/B).

GR-303 is supported on the Triple DS3, CLEI Code

BA9IX04AAA (89-0397), and the Octal DS3, CLEI Code

BAA9UVXGAA (89-0398).

When using the ENT-EQPT command, redundancy can be set

equal to SEC (redundancy=sec) only if the IOM AID specified is

in a protection slot. Attempting to provision an unsupported slot as

a SEC redundancy returns a DENY message.

CAS is supported on Octal, 89-0382-A/B/0398/0411, (CLEI

BAA9UV0GAA, BAA9UVZGAA, BAA9UVXGAA,

BA4A701FAA) and triple DS3, 89-0397/0410 (CLEI

BA9IX04AAA, BA4A60ZFAA), IOMs only.

When using Octal 89-0382 (CLEI BAA9UV0GAA) IOMs and you

require switch announcements, you have the following options:

1. Use VPS-IOMs, if present in your chassis, to provide

announcements.

2. Upgrade to either 89-0397/0398 (CLEI BA9IX04AAA,

BAA9UVXGAA) or 89-0410/0411 IOMs

(CLEIBA4A60ZFAA, BA4A701FAA) to get announcements

support on the TDM-IOMs.




ENA IOMs can only be provisioned in I/O-8 and will only fail

over to I/O-10. VPS can be provisioned in any slot, but will only

fail over to I/O-17.

You cannot provision I/O-11 (physical slot 15) if the ENA port 4 is

provisioned, nor can you provision the ENA port 4 if I/O-11

(physical slot 15) contains a provisioned card.

Three Way Calling (TWC) and Add On Transfer Call (AOTC)

require 1 or more of the following modules in the system.

89-0397-A Triple DS3 STS-1 I/O Module BA9IX04AAA

89-0410-A Triple DS3 STS-1 I/O with

Tone Detect

BA4A60ZFAA

89-0398-A Octal DS3-STS-1 I/O Module BAA9UVXGAA

89-0411-A Octal DS3 STS-1 I/O with Tone

Detect

BA4A701FAA

7. Software Limitations and Issues

The following software limitations are associated with release version

3.9.0.

CALEA and ISVM (Inter-Switch Voice Mail) are not supported

for 3.9.0.X releases of system software.

7.1 Equipment Management Issues

The absence of carrier on the signaling or management ports on the

protection SP does NOT prevent the SW-TOPROTN-EQPT::SP-x

TL1 command from being executed. It will result in an SP failover,

even if the signaling or management ports do not have carrier (an

Ethernet cable has been pulled). Note: It is recommended that you

check for alarms before issuing any equipment commands that

force failovers.

There is limited support for the CallType key in routing, screening

and digit modification, unless filled by param-defaults associated

with a trunk group or provided with this command. The real call

type associated with the simulated call based on number analysis

of calling and called party number is not available to this feature.

TEST-TRANS: Treatments related to announcements capture the

announcement id. If the announcement takes multiple arguments,

those may not be captured.

24445 Hop counter not currently implemented for BICC trunk

groups.

CDRs for fraud calls are not generated correctly.

24441 Recursive linking of ALTPLAN is not supported.




The IP addresses must be correct and unique on both SPs before

bringing the switch into service.

IP addresses for OS, signaling and craft Ethernet ports should not

be on the same subnet. If it is desired that they be on the same

subnet, contact Lucent Technical Services at 1-866-582-3688 for

provisioning assistance.

If the signaling interfaces are not configured with IP addresses, an

alarm from each SP, stating “lost link on signaling Ethernet,” will

be generated.

Redundancy of an IOM cannot be changed after it has been

provisioned. You must remove the IOM from service, delete it,

then completely re-enter it to change any provisioning for a

redundant IOM.

When switching from SS7 to ISDN signaling or vice-versa, the

signaling link and interface must be deleted and the Octal

DS3/DS1/DS3 IOMs must be rebooted before provisioning can

occur.

If you pull an SP, thus taking it out of service, you must wait 10

seconds before reinserting the SP.

If CPY-MEM fails, the flash update process becomes corrupt. In

this event, contact Lucent Technical Services at 1-866-582-3688.

Using the ED-DATE TL1 command to change the time is not

required or recommended when the NTP is provisioned. If the

new date differs by more than 1000 seconds, then the NTP daemon

may shut down. If this happens, you should reset the NTP server

to 0.0.0.0 then back to the correct server IP address.

A single IOM cannot support signaling links of both 56K and 64K.

The link speed must be the same for all links on a single IOM.

This restriction applies only to DS1 and DS3 IOMs, and does not

apply to Octal DS3 IOMs as a mix in the link speed creates no

problems.

When bulk provisioning T1 ports, it is necessary to wait anywhere

from 20 seconds to 3 or 4 minutes before continuing to provision,

depending on how many blocks of T1s you are provisioning. For

instance, if provisioning T1 blocks on a fully loaded Octal DS3,

you should probably wait 3 or 4 minutes before continuing with

provisioning. The fewer blocks of T1 ports you bulk provision, the

less time you have to wait before continuing with provisioning.

This also prevents the receipt of reply timeouts when adding PCs.

For Midplane II or III, line timing uses slot pairs for provisioning.

Therefore, you cannot have just one IOM in a paired slot. Slots 1

and 2 are paired, as are slots 8 and 10. To use line timing, any

combination of Octal DS3/STS-1 (part number 89-0382-A/B),

Triple DS3/STS-1 (part number 89-0397-A) or Octal DS3/STS-1




(part number 89-0398-A) IOMs must be in place in a given slot

pair.

CALEA CDC is not supported when the SP is running in

Master/Slave mode.

If the LCC is not specified for a subscriber in the ENT–

SUBSCRIBER command, calls are not allowed from the

subscriber.

7.1.1 DS3 IOM Limitations

Operating a FEND loopback on a channel already in a near-end

(NEND) loopback cannot be done because of DS3 interface chip

limitations. If a NEND loopback command was followed by a

FEND loopback command, the DS3 interface chip will only

execute the NEND loopback, but will remember the FEND

request. If the NEND loopback is released, the FEND request is

remembered but will not execute. Issuing a FEND loopback will

not work because the DS3 interface chip thinks a loopback is in

progress. The FEND must also be released. To insure a T3 is put

into a FEND loopback, first send a

RLS-LPBK-T3::<lpbk_id>:::FEND command followed by a

OPR-LPBK-T3::<lpbk_id>:::FEND.

The ED/ENT-T3 command does not support LINECDE=CCHAN;

it only supports B3ZS.

7.1.2 STS-1 Limitations

GR-253 (R6-372) states that there must be a method provided to

detect and report the actual contents of the Received STS Path

Trace message. The RTRV-STS1 command presently only

supports the expected Rx Trace message and the Tx Trace

message.

The system reports an STS Trace ID Mismatch when the J1 byte is

inaccessible. GR-253 (R6-382) states that STS Path Trace

monitoring should be suspended if the J1 byte in the Path

Overhead cannot be accessed (e.g., LOS, LOF, LOP-P and AIS-P).

This means that the system should not report an STS Trace ID

Mismatch just before it declares any of the above mentioned alarm

conditions, or after they clear.

STS reports Trace ID Mismatch events.

7.1.3 Ethernet Network Access (ENA)

Since an ENA failover goes from a lower available IP bandwidth

to a higher available bandwidth, an ENA failover will not take




place if the VPS resources are manually taken out of service

because the available IP bandwidth is considered to be zero.

7.1.4 Voice Server Modules

When the precedence of RTP packets is changed with ED-VOIP-

SYS, the voice server module needs to be rebooted for the settings

to take effect. This can be done with an IOM failover to the

protection voice server module followed by an IOM revert of the

voice server module.

7.2 Primary Rate ISDN Line Limitations

The switch supports National ISDN-2, 5ESS, and DMS-100

variants for one-way and two-way calls leaving the switch.

7.3 SS7 and ISDN Signaling Issues

When editing a T1 out-of-service the mode (OMODE) must be set

to AIS in order to bring MTP2 and LAPD down.

Currently, the signaling point code restart procedure is not

supported.

Alarms for ISUP timer expiry are disabled.

Alarms are not generated if the initial condition for a remote Point

Code is down.

When a call is made and no ISDN circuits are available, the CIC

remains BUSY for approximately 30 seconds.

A maximum of 128 destination point codes total can be

configured.

A signaling link set must contain at least one signaling link with a

link priority set to 0. Any additional links, in the link set, must

have contiguous priorities.

Switch currently does not support T-321 timers.

Trunk Group IDs must be unique in the system.

There can be no more than 100,000 interfaces formed by

TRKGRPS+ ISDNIF+CASIF+GR303IF+MGCP-LNGRP in the

router. The breakdown of each consists of the following: a

maximum of 3808 configurable ISDN interfaces and TRKGRPS

each; a maximum of 56 GR303-IF interfaces; and a maximum of

91392 CAS-IF interfaces (currently, however, it is recommended

that you not configure more than 64,000 CAS-IFs).

The replication of all of the signaling PM data (CC, DPC,

ISDNMSG, ISUPMSG, LSET, MTP3, SLKL3, SLKL2,

SS7ROUTE) is now based on timers instead of counters.




The order of operations for ISDN-IF and ISDN-LNK has been

swapped. An ISDN interface must be provisioned prior to its

respective ISDN link. The ISDN link ID is now unique to its

respective interface ID.

7.4 SS7 and BICC Limitation

BICC and ISUP trunk groups should not be configured to a

common destination point code.

7.5 BICC Limitations

BICC trunk groups must only be configured to either accept

incoming calls only (CICINCOMING) or originate outgoing calls

only (CICOUTGOING). If BICC is being used for both incoming

and outgoing calls, then two different trunk groups need to be

configured.

BICC trunking supports a maximum of 16383 BICC trunks per

Destination Point Code.

If you are unable to change BICC trunk group configuration

settings, you must delete the BICC trunks and the BICC trunk

group and then provision the BICC trunk group and trunks with the

required modifications.

7.6 CAS Signaling Limitations

The maximum CAS ports (T1s) that can be provisioned for one

Octal is 150 T1 ports (3600 T0s).

Parameters in the CAS-IF command cannot be edited after

changing the ALLOC parameter equal to CIRCULAR for one

CAS-IF entry.

When a wink timer (Out Seize Check) expires, the switch does not

remove the trunk from service or report the trunk on a maintenance

list. Instead, the call fails if the wink timer expires, and the trunk

circuit is returned to the idle state. Until this item is resolved, use

the Circular Hunting algorithm on affected trunk groups.

7.7 Integrated VoIP Limitations

If you change the VSM aal5enc encoding parameter (VCMUX,

LLCSNAP), a VSM reboot is required for the change to take

effect.

If you change the ENA format parameter (802.3, DIX II), an

ENA reboot is required for the change to take effect.




Tone Relay support is limited to Named Events per RFC2833,

Section 3.10, Table 1. Tone Relay RTP Payload Method is not

supported.

Automatic ENA failover by loss-of-signal or an IP link monitoring

failure, is only triggered if the number of GiG_E protection ports

in-service is greater than the current working. However, ENA

revert currently does not verify the state of its partner GIG_E ports

prior to revert. You should manually verify the status of the

partner GiG_E ports prior to an ENA revert.

The switch supports the transfer of DTMF tones as Tone Relay

packets over RTP, when a voice call is established using

compressed codecs (using G.729 protocol). However, Tone relay

won't work if the far-end equipment doesn't support it.

Fax/modem support between the switch and some third-party

equipment (such as gateways, IADs) is only available on G711

calls. For calls using compressed codecs(such as the Cisco-5300

which uses a proprietary scheme to switch to G.711 from G.729

for a FAX or modem call), fax/modem calls will not work with

these vendors if they use proprietary signaling protocols.

7.8 Intelligent Networks Restrictions

LNP test calls are currently not supported.

Notification and/or termination messages from the SCP are

currently not supported.

Queries are not sent to the backup SCP. This will not effect

routing if Global Title is used.

7.9 Call Processing Limitations

The SS7 signaling links are not protected during an IOM hardware

failover.

Retrieval of Calling Area entries requires knowing the Calling

Area ID entered.

When an IOM is in protection mode, attempting to add, modify or

delete ISDN, SS7 links or CAS signaling links from the protected

IOM will return DENY messages.

Calling Areas cannot be removed if they are associated with a

subscriber.

When dialing 800 numbers, it is not necessary to prefix 800 with

the number 1.

All Local Calling Areas must contain 555 to generate call type 33.

Specifically, 555 must be a HOME-NXX on your switch, and 555

must also be in your Local Calling Area. If either of these




conditions is not satisfied, then the call is treated as an InterLATA

call and call type 110 is generated. The most efficient way to

provision 555 into all Local Calling Areas is to designate one

HOME-NPA-NXX as 555, add that HOME-NPA-555 to one Rate

Center, and then assign that Rate Center to all Local Calling Areas.

The inter-digit timer has been changed to 2.5 seconds. The

shortened timer will affect any services that require user digit input

such as speed dial or call forwarding.

When a caller with Call Waiting is talking to a second party, and

the caller with Call Waiting receives a call from a third party, the

caller with Call Waiting can flash over to the third party, placing

the second party on hold. Upon disconnecting the call with the

third party, the caller with Call Waiting should either be able to

wait for normal timer expiry before being reconnected with the

second party, or should manually flash over to the second party to

continue the call. Currently, the switch does not wait for timer

expiry or a manual command from the caller, but rather,

automatically cuts back to the second party upon disconnect from

the third party.

N11 calls are populating Nature of Address code incorrectly.

Please contact Lucent Technical Services at 1-866-582-3688.

For ASCII and AMA billing, use Circuit Identification Codes from

0 to 9999. Although the switch supports a CIC range up to 16,000,

the billing records that include CICs greater than 9999 will be

truncated when output in Module 104 in the trunk member number

field. For example, a CIC of 16000 will be truncated to 6000 in

the trunk member field of Module 104.

The ISDN PRI Traffic CCS report does not currently update the

available circuit (AVLCIRC) field to reflect ISDN channels that

are OOS.

The switch will now send the Provisioned Circuit Records (PCRs)

to the traffic collection application every 15 minutes instead of

every 5 minutes. PCRs provide the traffic statistics application

with the circuit count information (i.e., number of available circuits

in a trunk group). The impact of this change is that the circuit

count information is now accurate to within 15 minutes instead of

5 minutes.

Because Feature Group D functionality is fully supported from an

Access Tandem and Inter-Exchange Carrier standpoint for CAS

and ISUP in release 3.8 and above, originating carrier information

(such as connect date, connect time, and elapsed time) is only valid

for Feature Group D trunks. Note: End Office Feature Group D

functionality is not fully supported. For terminating carrier access




calls, the carrier timing information is populated even if the

incoming trunk group is not Feature Group D.

In the Billing module, the Dialing and Presubscription Indicator is

incorrectly populated. Both default to “0” (dial digits cannot be

determined) when the indicator should show that a Carrier Access

Code was used.

7.10 Session Initiation Protocol (SIP), MGCP and GR-303 Limitations

Changing media streams in SIP 18x responses and subsequent 200

OK responses is not supported since it is it is contrary to RFC

3261.

A SIP CANCEL message is not sent out after Invite Timer (T1)

expiry which is consistent with RFC 3261 but inconsistent with

RFC 3398.

If you want to modify the endptvoip IP address on a GigE port,

you must edit the ENET port Out of Service (OOS) and then use

the RMV-EQPT command on the VPS IOM. There is no way to

dynamically update the IP addresses without dropping all calls

associated with a VPS IOM. For example, information would be

entered as such:

ED-ENET::IOM-8-ENET-1::::OOS; (GigE port)

RMV-EQPT::IOM-11; (VPS/VSM IOM)

DLT-ENET-ENDPTVOIP::IOM-8-ENET-1; (Delete Endpoint)

ENT-ENET-ENDPTVOIP::IOM-8-ENET-:::IPADDR=10.18.140.211,

MATEIPADDR=10.18.140.212,SUBNETMASK=255.255.255.0,

DEFAULTGATEWAY=10.18.140.1:IS;

(Enter new IP address to the endpoint)

ED-ENET::IOM-8-ENET-1::::IS;

RST-EQPT::IOM-11;

The switch supports G.711, G.726, G.729, CLEARMODE, X-

CCD, CISCO-CLEAR-CHANNEL codecs, each with 10, 20, 30

and 40ms sampling.

The “state” information on SIP-IPADDR is not persistent.

7.11 IntVoIP/SIP/MGCP CODEC Negotiation Limitations

When the SDP profile contains multiple deep compression CODECs

(G.729 or G.726), only the first available deep compression CODEC

in the preference list will be included in the originating offer from the

switch, e.g., G.729, G.711, G.726. This results in G.711 and G.729

being the offered CODECs in the originating offer (provided G.729 is




available; otherwise, G.726 or G.711 would be offered). This

limitation applies to CODEC negotiation across BICC, SIP, and

MGCP.

7.12 GR-303 Limitations

An Octal DS3 IOM can be provisioned with a maximum of 56

Interface Groups (IFGs).

All ISDN and CAS limitations also apply for GR-303.

7.13 System Software Limitations

UNIX system security does not support password aging or security

logging for FTP and remote login access.

The date/time should be set before configuring the system and

adding the IOM. It is advised that GMT time be used. Please

contact Lucent Technical Services at 1-866-582-3688 for

instructions on how to provision the clock for GMT time.

If OS Ethernet ports are not provisioned, an alarm will be present.

If an IOM protection switch occurs, the monitoring function stops.

Once an IOM revert occurs, the cross-connect to the test port has

to be put out of service (OOS) and restored.

Currently there is no way to retrieve the status of a nailed up DS0

connection unless you know the exact DS0 of one of the

connections. RTRV-CRS-T0 without an AID should return the

status of test port settings.

The ED-SERVICE-ACCESSCODE must put the VMS in-service

to support voice mail. The command would appear as:

ED-SERVICE-ACCESSCODE::VMS::::IS;.

7.14 TL1 Restrictions and Security Errata

Occasionally a “reply timeout” message will be seen while trying

to execute an ENT, ED or DLT TL1 command. The command

may have still worked and should be validated with a RTRV.

The number of TL1 retrieve (RTRV) commands is limited to five

results per second.

It is possible that some TL1 commands may timeout before

completion, depending on system load. Should this occur, please

contact Lucent Technical Services at 1-866-582-3688 for

assistance.

Signaling TL1 commands respond “All Resources Busy” while

standby SP is synchronizing.

Logging into the TL1 agent cannot be done during part of SP sync

on the standby side.




When using the INIT-SYS, ED-BILLSYS, and EXEC-RESTORE-

PLEXUS commands, the target identifier (TID) must always be

used. Therefore, the form of the command must be, as an example,

INIT-SYS:TID::::10; or ED-BILLSYS:TID::::10; or EXEC-

RESTORE-PLEXUS:TID::::10;

Before restoring a backed up database using the EXEC-

RESTORE-PLEXUS command, contact Lucent Technical Services

at 1-866-582-3688 for assistance to ensure a successful database

restoration.

The T3 Idle and T3 Map parameters in the ENT/ED/RTRV-T3

command are not supported.

For the commands INIT-REG-T1/T3/E1/OC12/OC3/STS1, NULL

is the only accepted value in the mondat and montm parameters.

ALL is the only montype that will clear the registers.

The “state” information on the SIP-IPADDR command is not

persistent. If the primary IP address has failed over to the

secondary IP address, and then you fail over the SP, your first SIP

call after the SP failover will initially attempt the call on the wrong

IP address. The call will complete on the secondary IP address

once the SP determines the primary is down. The secondary IP

address will then be made “active” and all subsequent calls will be

made using the "active" IP Address.

7.15 Security

An IP packet filtering application that runs on the SPs is available in this

build. It is important to note that IP packet filtering is only a subset of full

firewall/Session Border Controller functionality (e.g., packet filtering,

bandwidth management, user authentication, network access rules,

network address translation, and back-to-back user-agent). Because IP

filtering and processing filtering rules is a CPU-intensive task that can

degrade overall switch performance, the use of an external network

firewall is highly desirable and recommended. However in the absence of

a firewall, IP filtering can protect the switch from unsophisticated attacks

or accidental misuse. Security is not enabled upon initial boot up. Should

filtering be required, contact Lucent Technical Services at 1-866-582-3688

for assistance.

Lucent Gateway Platform System Maintenance Release Notes

Documents

Transcript of Lucent Gateway Platform System Maintenance Release Notes