TS 7.3.139-RNLOC DOCSIS (1.0)

Touchstone

Telephony Firmware Release 7.3.139 Release Notes and Letter of Operational Considerations

Touchstone Telephony Firmware

Release 7.3.139 Release Notes and Letter of Operational Considerations Document release Release 1.0 Document date January 12, 2012

2012 ARRIS Group, Inc. All Rights Reserved Printed in the USA The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. User must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to ARRIS Group, Inc. ARRIS, ARRIS Group, Inc. and Voice Port are trademarks of ARRIS Group, Inc.. Cornerstone is a registered trademark of ARRIS Group, Inc.. The firmware described in this document is furnished under a license agreement and may only be used in accordance with the terms of that license.

Publication History

January 12, 2012 Draft, v0.1

January 12, 2012 Approved, v1.0

Table of Contents

1 OBJECTIVES OF THIS DOCUMENT _____________________________ 1

1.1 ARRIS COMMITMENT ____________________________________________ 1 1.2 PURPOSE AND SCOPE OF THIS DOCUMENT _____________________________ 1 1.3 PRODUCT IDENTIFICATION AND PURPOSE OF RELEASE ___________________ 1 1.4 FIRMWARE FILENAME VARIANT INFORMATION _________________________ 2 1.5 MINIMUM FIRMWARE BASELINE FOR HARDWARE _______________________ 2 1.6 PRODUCT DOCUMENTATION _______________________________________ 4

2 RELEASE NOTES ___________________________________________ 5

2.1 DOCSIS NEW PRODUCT FEATURES _________________________________ 5

2.2 RESOLVED FIELD BULLETIN(S) ____________________________________ 11 2.3 DOCSIS RESOLVED PRODUCT DEFICIENCIES _________________________ 12

3 LETTER OF OPERATIONAL CONSIDERATIONS _________________ 58

3.1 DOCSIS OPERATIONAL CONSIDERATIONS ___________________________ 58

3.2 UNSUPPORTED FEATURES ________________________________________ 60 3.3 UPGRADE CONSIDERATIONS ______________________________________ 61

4 CUSTOMER SERVICE AND SUPPORT__________________________ 65

APPENDIX A: COMPLIANCE MATRIX _____________________________ 66

Touchstone Telephony Firmware - Release 7.3.139

Release Notes & Letter of Operational Consideration 1

1 Objectives of This Document

1.1 ARRIS Commitment

ARRIS is committed to developing high quality, value-added products and services to the

Multiple System Operator (MSO). ARRIS continually strives toward meeting our

customers needs with solutions that will help achieve their business objectives.

1.2 Purpose and Scope of This Document

This document describes the value-added features and anomaly resolutions associated

with this release. It also informs operators of known Operational Considerations

associated with this product release that have been identified either through ARRIS testing or field operations.

1.3 Product Identification and Purpose of Release

Described in this document is the Touchstone Telephony Firmware. This Touchstone

Firmware release is intended for ARRIS manufactured E-MTAs. Information pertaining

to support for this specific release is detailed in the table below. Not all configurations

and hardware variants are supported with each release.

Product Description MSUP 17 TS 7.3.139

Validation Sequence Maintenance Supplemental Release (MSUP)

Supported DOCSIS Standard(s)

DOCSIS 3.0

Supported Signaling Protocol(s)

Network-Based Call Signaling (NCS)

Session Initiation Protocol (SIP)

Supported PacketCable Standards

PacketCable 1.5

Firmware Filename TS0703139_122011

SysDescriptor SW_REV: 7.3.139

PacketACE DOCSIS 3.0 PacketACE Release 3.29 or later



1.4 Firmware Filename Variant Information

The table below presents the filename extensions used on Touchstone products. Not all

variants of a load are created for a release.

FILENAME EXTENSION PURPOSE OF EXTENSION

_NA North America signed firmware image

MODEL_852 Supports the TG852 hardware platform

MODEL_862 Supports the TG862 hardware platform

MODEL_7_8 Supports the TM702, TM722, TM802, TM822, and TM804 hardware platforms

WBM760_CM820 Supports WBM760 & CM820 hardware platforms

MONO Monolithic image containing both eRouter and DOCSIS images

MAC14 Used to validate upgrades and downgrades

SIP Session Initiation Protocol (SIP) firmware image

1.5 Minimum Firmware Baseline for Hardware

The table below shows the minimum released firmware needed to operate a specific

model of hardware.

Hardware Model Firmware Image

TM702/722 TS070198_071510 (TS 7.1.98)

WBM750A/B TS070198_071510 (TS 7.1.98)

WBM750C TS070198_071510 (TS 7.1.98)

WBM760A/B/C TS070198_071510 (TS 7.1.98)



CM820A/B/C TS070397_042811 (TS 7.3.97)

TM802G TS070346_081910 (TS 7.3.46)

TM804G TS070397_042811 (TS 7.3.97)

TM822G TS070397_042811 (TS 7.3.97)

TG852G TS070373_121610 (TS 7.3.73)

TG862G TS070395_041311 (TS7.3.95)



1.6 Product Documentation

Other relevant information is included in the following documentation:

Product

Touchstone Telephony Guide (TS7.3)



2 Release Notes The Release Notes describe the New Product Features introduced in the Touchstone

Firmware for the ARRIS Touchstone Telephony Modem(s). Included in the Resolved

Product Deficiencies section is a list of resolved operational considerations noted in

previous releases.

2.1 DOCSIS New Product Features

Added in TS 7.3.139

Argentina Call Tones This firmware release introduces support for the Argentina country code template with

customized tone and ring cadence definitions.

SIP GUPI TFTP Override Provisioning Method This firmware release introduces support for the ' gupiTftpSvrOverride(11) provisioning method where the FQDN of the MTA TFTP server is provisioned via the

arrisMtaDevTFTPServerAddrOverrideFQDN MIB in the CM configuration file.

Added in TS 7.3.135

Loop Diags Low REN Warning This firmware release introduces the ability to configure the Loop Diags subsystem so

that detection of Low or no REN on a line results in a Warning, not a Failure. It is

configured via a new feature switch in MIB ppCfgMtaFeatureSwitch.

Support to Ignore Missing Payload Types A configurable feature switch has been introduced to allow the eMTA to ignore a payload

type in an SDP payload attribute line, when the payload type is not listed in any of the

media descriptions. This allows the operator to overcome standards-based SDP checking

of this scenario, and proceed with call setup. The feature switch is located in the MIB

ppCfgMtaCallpFeatureSwitch.

Added in TS 7.3.128

No new features were added to this release.

Added in TS 7.3.123




Added in TS 7.3.120

Internal SpeedTest Application This firmware release adds an internal speed test application which allows an MSO to

perform downloads/uploads to the modem itself, without utilizing a CPE. Measurement

of downstream and upstream speed is accomplished by transferring a file between a

network server and the embedded FTP/HTTP client in the modem. The test may be

initiated either via SNMP or the WebGUI.

Reset Ethernet Connectivity after Loss of DS

This release extends the capabilities of this feature to also support the WBM750 and

TM702 HW models.

Business Services over DOCSIS (BSoD)

This release supports the Cable Labs BSoD/L2VPN specification. The L2VPN feature

allows cable operators to offer a Layer 2 Transparent LAN Service (TLS) to commercial

enterprises, which is one of the principal goals of the CableLabs BSoD initiative. Please

consult your CMTS operations guide for implementing this feature.

Ability to handle non-standard T38 in SDP A new capability has been added to the NCS message parsing to accept the non-standard

value of T38 in the sdp as a valid alternative for t38

Added in TS 7.3.115

Reset Ethernet Connectivity after Loss of DS

This release adds a new MIB, arrisCmDoc30SetupEthernetLinkBounce, which enables

the modem to briefly interrupt and reset the CPE Ethernet connection upon loss of

downstream connectivity due to an extended RF cable cut (T4). This featured is disabled

by default. The MSO can enable this MIB to initiate a DHCP request sooner in order to

shorten recovery time. Currently, this feature is supported for WBM760, CM820,

TM722, TM802, TM822, and TM804.

Added in TS 7.3.110




Added in TS 7.3.108

ResetMTA CLI command A new CLI command resetMTA was added to the Voice menu for resetting just the MTA portion of the modem.

Added in TS 7.3.99

Source IP in Reset Logs When a modem is rebooted via docsDevResetNow, the source IP address of the SNMP

set request PDU is recorded in the last reset log.

Added in TS 7.3.97

Software Download Filename Check Override Feature A new MIB arrisCmDoc30SetupSWDLFilenameCheckOverride was added to allow

SNMP initiated downloads to proceed in the same manner as ARRIS D2.0 products when

the filename is unchanged. This functionality enables the MSO to use symbolic links for

consistency in their firmware filenames included in the CM configuration file. The

default setting for this feature is disabled.

Hardware Power ON Reset Logging An entry and timestamp are now recorded in the last reset reason log for AC power loss and when the hardware reset button is pressed.

ARRIS SIP compatibility mode advertisement In this release, a new MIB arrisCmDoc30DhcpMtaOpt60Override is added for adjusting

the Device Identifier information in DHCP Option 60 for Legacy SIP devices. When

enabled, the PacketCable defined text is replaced with ARRIS SIP compatibility mode" where HW Type is the model of the device, e.g.: TM802G.

Added in TS 7.3.92A


Added in TS 7.3.89

Ability to Keep CPE MAC after Disconnect

In this release, a new MIB arrisCmDoc30SetupKeepCpeOnIfDisconnect is added to this release. When the MIB is set to enable (1), CPEs MAC address will be kept in the



CPE MAC learning table after the CPE is disconnected. The MAC address will be

deleted from the table if the MIB is set to disable (0) which is the default setting.

Added in TS 7.3.87

SIP Post Provisioning

This release of firmware supports the ability to provision the eDVA after it has registered

with a minimal configuration file. The feature supports post provisioning for line

additions, deletions, and other associated data.

Added in TS 7.3.81A


Added in TS 7.3.81

ARRIS Proprietary LVM MIB Support

In addition to the PacketCable 1.5 pktcEnNcsEndPntLVMgmtTable MIBs, the ARRIS

proprietary LVM arrisMtaDevLoopVoltageMgmt MIBs objects are now supported via

the MTA configuration file only.

Added in TS 7.3.65A


Added in TS 7.3.65

Enhancement to Callp Feature Switch Setting between D 2.0 and D 3.0

For networks that cannot support multiple MTA configuration files, a new MIB object,

arrisMtaDoc30AdjustCallpFeatureSwitch has been added that enables the adjustment of

the ppCfgMtaCallpFeatureSwitch to be the same mapping as the feature switch setting

and default values specified in the DOCSIS 2.0 firmware.

The following bits in the ppCfgMtaCallpFeatureSwitch are affected:

1. Allow endpoint to send provisional responses (0x00008000) A value of 0 in DOCSIS 3.0 enables provisional responses.

A value of 1 in DOCSIS 2.0 enables provisional responses.

2. Allow endpoints to enter the Lockstep quarantine mode (0x00000002) A value of 0 in DOCSIS 3.0 enables Lockstep quarantine mode.

A value of 1 in DOCSIS 2.0 enables Lockstep quarantine mode.

3. Allow piggybacked transmission of NCS messages (0x00000001)



A value of 0 in DOCSIS 3.0 enables piggybacked transmission.

A value of 1 in DOCSIS 2.0 enables piggybacked transmission.

When the modem registration is complete the value of the ppCfgMtaCallpFeatureSwitch

will be adjusted if the new arrisMtaDoc30AdjustCallpFeatureSwitch MIB is enabled (1).

The actual definition of the individual bits in the ppCfgMtaCallpFeatureSwitch is not

changed.

S-CDMA Support

Starting TS 7.3.65, synchronous upstream S-CDMA is now supported, however S-

CDMA is disabled by default to help maximize battery hold up time on all Model 8

Telephony Modems. S-CDMA support feature can be implemented by setting the

arrisCmDoc30SetupPowerSaveOption MIB object from the default maxbattery(1) to maxupstream(0). When set to maxupstream(0), the modem will support all upstream types but the battery hold up time will be reduced.

Added in TS 7.3.55

SIP: Provisioning Method GUPI Encrypted MAC MTA Supported

A new provisioning method, gupiEncryptedMacMta, is now available for SIP loads. This

is identical to GUPI MAC MTA provisioning, with support for decrypting the encrypted

provisioning file. This provisioning method can only be selected from the

arrisMtaDevProvMethodIndicator.

Power Save Management (PSM) Enhancement

This firmware release supports an additional enhancement to the PSM feature that will

allow the eMTA to switch to 1x1 bonded mode while keeping the LAN interface fully

powered when the modem loses AC power and the default data shutdown timer of 5

minutes expires. This feature can be implemented by setting the following

arrisMtaDevPwrSupplyEnableDataShutdown MIB object to disabled.

Enhancements to MGPI Functionality

This firmware release adds several updates to the MGPI operations. These include

adding the ability to parse DSC messages with more than 3 classifiers, reject requests for

more UGS-SF than can be support (24), and improvements to the classification of SF.

Added in TS 7.3.46

8x4 Tuner Support

This firmware release will support up to 8 bonded DOCSIS 3.0 downstream channels for

Model 8 units. All combinations of downstream and upstream between 1x1 and 8x4 will

be supported.



Power Save Management

TS7.3 firmware release supports an enhanced Power Save Management (PSM) to

maximize battery hold-up time for all Model 8 Telephony Modems. When the modem

loses AC power and the data shutdown timer expires, the modem will power down the

LAN interface and switch to 1x1 bonded mode. Once AC power is restored, the eMTA

activates data interface and restore its original bonding mode. Due to the nature of the

power-management feature, synchronous upstreams (S-CDMA/S-TDMA) are not

currently supported on Model 8 units.

TM802 Hardware Support

TM802 provides a single 10/100/1000 Base-T Ethernet interface for ultra high speed data

throughput based on the DOCSIS 3.0 cable modem specifications with 8x4 channel

bonding. Please note that USB is not supported on TM802 hardware.

Non-Service Affecting Firmware Download and Application

TS7.3 firmware release now provides an update to the feature which can prevent an

eMTA from resetting after a firmware download during an active call. This feature has

been implemented through the addition of the arrisMtaDevSwDnldNoSvcImpact MIB

object. Value settings are described below with the default setting set to Enable(1):

Disable(0) Always download firmware and reboot immediately after firmware download.

Enable(1) Download firmware immediately but delay the reboot unit all line are on-hook and no connects are active.

StrictEnable(2) Do not download firmware if any phone endpoint is off hook.

Out of Range (OOR) Threshold Change

This release of firmware supports the ability to enable a reduced combination of Out of

Range (OOR) packet sequence numbers the modem will discard and the minimum time it

will wait before it re-synchronizes with the CMTS. When the SNMP MIB Object,

arrisCmDoc30SetupReducedOORThreshold, is set to enabled in the CM configuration

file the packet threshold value is set to 3 packets and the timeout is set to 1 second. The

default behavior of this MIB is disabled in order to be compliant with the DOCSIS

specification which states 1000 packets and a timeout of 2 minutes.

This MIB can also be set via SNMP or the CLI. The value for this MIB is stored to

NVRAM. However, a modem reset is required before the new OOR threshold values

take effect. For a configuration file change, the reboot occurs autonomously. For CLI

and SNMP changes, the operator must manually reset the modem.



2.2 Resolved Field Bulletin(s)

The following field bulletin issues were resolved in this Touchstone firmware release or

previous firmware releases.

Field Bulletin

Number Field Bulletin Title

Product Defect

Number

AFB-10-0307 ARRIS DOCSIS 3.0 E-MTAs Which Experience Multiple T4

Timeouts Prematurely Drop Calls.

PROD00159954

PROD00156134

AFB-10-0306 ARRIS DOCSIS 3.0 E-MTA Certificate Failure with Secure

Provisioning

PROD00156134



2.3 DOCSIS Resolved Product Deficiencies

ARRIS continues to resolve any product deficiencies discovered. This Touchstone

Firmware release contains closure for the detailed issues listed in the following section.

Considerations that aplly to a specific feature implementation will designed with one of

the following prefixes included in the heading:

LVM: Loop Voltage Management

NCS: NCS Signaling Protocol

SIP: Legacy (pre-IMS) SIP Signaling Protocol

SSH: Secure Shell

T.38: T.38 Feature Specific Issue

TR69: TR-069 Specific Issue

The following issues were resolved in release 7.3.139

2.3.1 SIP: Multiple Contact Headers Not Handled Correctly

Tracking No. PROD00161080

Description MTA is not processing proxy messages correctly when they contain more than one Contact header.

Impact Service

Occurrence High

2.3.2 SIP: Audio Not Resumed After Call Hold


Description After being placed on hold, the call audio does not resume in cases where the value of the SDP version is greater than

4294967295.

Impact Service

Occurrence High



2.3.3 TM804: Cant access MTA MIBs for Lines 3 & 4


Description On a TM804, line 3 & 4 information could not be accessed for the following MIBs:

ppSurvPortMaintState

ppSurvPortLcDiagRequest

ppSurvPortLcDiagLastResult

ppSurvPortTable

Impact Service

Occurrence High

2.3.4 MTA rejects MDCX message during 3WC

Tracking No. PROD00177793, PROD00176092

Description During certain features including 3WC, the modem may incorrectly reject an SDP message with zero-IP address while

modifying a connection (MDCX), resulting in a failed call.

Impact Service

Occurrence High

2.3.5 SIP: Blind Transfer Call Failures


Description When making SIP calls, the MTA will fail blind call transfer if the terminating end answers the transferring call too fast (less

than a second).

Impact Service

Occurrence High

2.3.6 Scanning Override Page Not Functional


Description For ARRIS TM822 and TG862 products, the scanning override webpage will crash when accessed while the modem is

scanning.

Impact Service

Occurrence High



2.3.7 BSOD Functionality

Tracking No. PROD00177558, PROD00177557, PROD00177010

Description The following BSOD related issues have been corrected:

Multicast and broadcast traffic cannot properly traverse the L2VPN in the downstream.

Traffic cannot reach an unknown Destination MAC address behind a BSoD enabled CM820A.

When provisioned, the downstream traffic does not work, non-BSOD(traffic to CM) nor BSOD(traffic to

CPE). But Upstream traffic works for both non-BSOD

and BSOD packets.

Impact Service

Occurrence High

2.3.8 BSoD traffic fails when frame size is 1526 bytes to CMTS


Description 1526 byte packets (double tagged packets) arriving at the CMTS with double tags and then forwarded downstream appear

to be blocked.

Impact Operational

Occurrence Rare


2.3.9 Incorrect Australian template defaults


Description The Australian country code template settings for WT1 and hook-flash timing did not match DOCSIS 2.0 default values.

Impact Service

Occurrence High



2.3.10 No CallerID displayed for Brazil template


Description When using the Brazil country code template, CallerID information was not displayed using DTMF signaling protocols.

Impact Service

Occurrence High

2.3.11 DS LED is Amber when NACO is OFF with DS Bonding


Description The DS LED should be green when the DS is bonded. Currently, when in NACO OFF, the LED flashes amber even

when the DS is bonded. Now, the LED will flash green if DS is

bonded, and will flash amber is the DS is unbonded.

Impact Service

Occurrence High

2.3.12 CM Activity Not Stopped after RNG-ABORT message


Description When the CMTS send a Ranging-ABORT message, the CM must stop all activities on the upstream.

Impact Service

Occurrence High

2.3.13 Downstream TCP Throughput below Benchmark


Description In downstream bonding scenarios, TCP protocol throughput is occasionally observed to be slower than expected in traffic

tests. Particularly evident when TCP receive window of size

65K or less.

Impact Service

Occurrence Medium



2.3.14 Slower Registration Times for Broadcast IM Ranging Opportunities


Description E-MTAs using Broadcast IM ranging opportunities for non-primary US acquisition may observe slower registration times

and more instances of US partial-service.

Impact Service

Occurrence Low

2.3.15 Web GUI displays incorrect MTA boot file nam


Description The MTA boot file field under the DHCP Web page displays garbled information when MTA provisioning is not complete.

Impact Operational

Occurrence High

2.3.16 SIP: Port 2427 opened


Description Test showed that port 2427 was incorrectly opened when using SIP load.

Impact Operational

Occurrence High


2.3.17 Wrong tones for ChileT Country Code Template


Description Add support for ChileT country code template to support customized customer dialtone and ringback tones.

Impact Service

Occurrence High



2.3.18 PCMM: Service Flow and Classifiers not correctly setup


Description When using PCMM, an error could occur when modifying the modems service flow and classifier tables while processing a Dynamic Service Change message from the CMTS. This

resulted in calls going over the best effort service flow, rather

than the intended UGS flow.

Impact Service

Occurrence High

2.3.19 SIP Hook-Flash Event Reporting Support


Description Add SIP support to enable hook-flash reporting for the Broadsoft SIP solution.

Impact Service

Occurrence High

2.3.20 SIP: DNS Cache Feature Not Supported


Description Add SIP support for caching the last DNS records in case the next DNS query fails.

Impact Service

Occurrence High

2.3.21 MTA fails to recognize Hook-Flash detection


Description If the MTA line was requested to ignore hookflash and then processed an embedded request that re-enabled hookflash

detection - hookflash detection was not being re-enabled.

Taking the line OOS and then back IS corrects the issue.

Impact Service

Occurrence High



2.3.22 CM Activity Not Stopped After RNG-ABORT message


Description When the CMTS send a Ranging-ABORT message, the CM must stop all activities on the upstream.

Impact Service

Occurrence High


2.3.23 TR69 : Exception in non-TG firmware with TR-069 config file


Description When TR-069 TLVs are used in a config file on a non-gateway hardware platform that does not support TR-069 (all TS 7.3

non-TG platforms), the firmware will crash.

Impact Operational

Occurrence High

2.3.24 Speedtest support is missing on CM820


Description Internal speed test application support is missing on the CM820.

Impact Operational

Occurrence High




2.3.25 SIP: P-Preferred-Identity Header uses wrong domain name after 407 challenge


Description The P-Preferred-Identity header uses the wrong domain name after a 407 challenge to the initial invite. This occurs when the

TO header of the 407 challenge uses a different domain name.

Impact Service

Occurrence High

2.3.26 pNe!!! error log resulting in no dialtone


Description A no dialtone condition may occur if only line 2 is provisioned and the acknowledgement to the RSIP contains a notified entity

parameter. The RSIP ACK may not be accepted causing the

RSIP to be retransmitted and the restart process to not be

completed.

Impact Service

Occurrence High

2.3.27 SIP: No Support for Standard INFO Hook Flash


Description The SIP feature (provisionable by Sip Feature Switch) to enable standard hook-flash reporting with the SIP INFO message does

not work.

Impact Service

Occurrence High

2.3.28 Upstream interoperability problems in STDMA mode


Description To solve interoperability issues with some CMTS using STDMA upstream mode, Arris has added a new CM MIB

arrisCmDoc30SetupIgnoreMddSymbolClockIndicator to enable

the cable modem to operate only in ATDMA mode. The

default value of the MIB is enabled, which disables STDMA.



Impact Service

Occurrence High

2.3.29 CM Config File limited to 16 NM Access Filters


Description Increased the number of NM Access Filters supported in the CM configuration file from 16 to 32 to match implementation

for ARRIS DOCSIS 2.0 products.

Impact Operational

Occurrence High

2.3.30 Modems may Fail to Bond against Cisco 10K CMTS


Description Interoperability issue where in certain Cisco 10K firmware releases, the CMTS will incorrectly select the wrong RCP when

bonding greater than 4 channels. This affected the ability for

ARRIS CM820, TM804, TM822, and TG862 modems to

correctly bond on the secondary channels. This update detects

the condition and compensates for the invalid RCP message.

Impact Service

Occurrence High

2.3.31 SIP: End of Call stats not spec compliant


Description The end of call stats made available at the conclusion of a SIP call are not fully compliant to the RTCP-XR specification

document (draft-ietf-sipping-rtcp-summary-06) as was

advertised in customer documentation.

Impact Operational

Occurrence High

2.3.32 RIPv2 packets from CPE not passed to CMTS


Description In certain customer configurations with MDF enabled, RIPv2 packets from CPE devices were not correctly passed by the



modem to CMTS and northbound routers.

Impact Service

Occurrence High

2.3.33 Incorrect units for Average Signaling Latency MIB


Description The value returned for the arrisMtaDevSignalingAvgLatency MIB was not in the milliseconds format.

Impact Operational

Occurrence High


2.3.34 DST doesn't work with Australia/New Zealand time


Description Daylight Savings Time does not work with Australia/New Zealand time when the start and end end time after not in the same calendar year.

Impact Operational

Occurrence High

2.3.35 RIPv2 packets from LAN side router not forwarded


Description RIPv2 update packets from LAN side CPE routers are not forwarded correctly by the ARRIS modem.

Impact Service

Occurrence High

2.3.36 arrisCmDoc30SetupPartServiceFallback20 MIB does not work for Model 8 HW models


Description Added support for handling of Partial Services fallback mode



into 1x1 for older CMTS software revisions that do not support

partial service. This feature is now supported for all ARRIS

HW models instead of just Model 7 HW.

Impact Operational.

Occurrence High

2.3.37 Modem fails to register for greater than 16 DS


Description The modem will not register in D3.0 mode on Cable MAC domains where greater than 16 Downstreams are provisioned

and advertised in MDD messages. In this case, the modem will

register in D2.0 mode (1x1).

Impact Service

Occurrence High

2.3.38 Web page displayed incorrectly for IE browsers


Description The ARRIS webpage is not rendered correctly when Internet Explorer is using an extra wide setting (more than double the

width of the normal webpage). This issue does not occur for

Firefox, Safari, or Chrome browsers.

Impact Service

Occurrence High

2.3.39 Option 177: Cannot Complete MTA Provisioning


Description When Option 177 provisioning is used, the MTA does not correctly obtain an MTA IP address if Subtype-9 is

encapsulated in the Option-177 DHCP OFFER.

Impact Service

Occurrence High




2.3.40 Possible MTA reset if SIP Digit Map incorrectly configured


Description If the sipCfgDigitMap MIB is provisioned to an invalid length, then an exception may occur on the modem while generating an

error log entry.

Impact Service

Occurrence High


2.3.41 BPI Disabled Caused Slower Upload Speeds


Description Modems operating with BPI disabled may have slower upstream throughput on some CMTSs that incorrectly handle a

version field of 0.

Impact Service

Occurrence Medium

2.3.42 Telnet Sessions Not Reset


Description The Reset Session button on the Technical Support webGUI page did not reset the active telnet sessions, and always

indicated success.

Impact Operational

Occurrence High

2.3.43 Incorrect call results with SIP Digit Maps provisioned via TLV


Description TLV provisioning of a SIP Digit Map may not restrict calls that do not match the provisioned Digit Map. A call may be setup

even if it does not specifically match the provisioned Digit



Map. This issue affects only the TM804 and TM822.

Impact Service

Occurrence High

2.3.44 TM804: No HTTP Loop Diagnostics Capability for lines 3 or 4


Description When performing loop diagnostics via HTTP on the TM804, the Advanced web page only offers the option to run

diagnostics for line numbers 1 or 2.

Impact Operational

Occurrence High

2.3.45 CM820, TM804, TM822: Modem may reboot continuously when using arrisCmDoc30PowerSaveOption in CM config file


Description A possible reboot loop may occur on CM820, TM804, and TM822 hardware models when the

arrisCmDoc30PowerSaveOption MIB is included in the CM

configuration file with a setting of maxbattery (1). This MIB is not applicable for correct operation of these HW models.

Impact Operational

Occurrence High

2.3.46 TM804/TM822 battery hold-up time below 8 hours


Description When operating on battery power, the TM804 and TM822 do not meet the 8-hour battery hold-up time (HUT) requirements

with the 2-cell, 2.6AH battery pack.

Impact Operational

Occurrence High



2.3.47 Modem May not Bond on Some DS channels


Description During initial channel bonding, there was a chance of channel calibration failure which could result in non-bonding. A change

has been made to calibrate during the initial downstream single

channel lock thus avoiding the problem.

Impact Service

Occurrence Medium

2.3.48 SNMP mib get/walk of DS power levels could cause disruption during active calls


Description Active calls may be briefly interrupted (muted) while an SNMP read operation of downstream power levels is being executed.

Impact Service

Occurrence Low

2.3.49 Mixed Mode Load Balancing Issue During Registration


Description When using mixed upstreams, the CM may not send the registration acknowledgement message to the CMTS if the

downstream channel is changed during registration load

balancing. This problem is specific to non-bonded mixed

channels upstreams only.

Impact Service

Occurrence Low

2.3.50 Duplicate TLV11 Entry Prevent Modems from Being Operational


Description Duplicate TLV11 in the CM config file may prevent the provisioned modem from becoming operational.

Occurrence High



Impact Service

2.3.51 TM804: Incorrect default for Line 4 Endpoint Dialing method


Description The default setting for the arrisMtaDevEndPntDialingMethod (tone, pulse, tone and pulse, etc) is incorrect for Line 4. This

may prevent the end-user from being able to place a call.

Impact Operational

Occurrence High

2.3.52 TM804: Cannot Support 3-way Calls on all Four Lines


Description When using TM804 with 4-lines of voice provisioned, only two 3-Way Calling or Call Waiting sessions can be active at any

time on the device.

Impact Operational

Occurrence High

2.3.53 EFL Downloads do not check arrisMtaDevSwDnldNoSvcImpact for strictEnable


Description ARRIS Enhanced Firmware Downloads (EFL) incorrectly did not check if a call is active when

arrisMtaDevSwDnldNoSvcImpact is set to strictEnable.

Impact Service

Occurrence High



2.3.54 No speech path between two T.38 enabled endpoints


Description When ARRIS MTA negotiates T.38 with a non-ARRIS MTA, call processing will incorrectly set T.38 fax modem instead of

establishing voice services. As a result, no speech path is

established.

Impact Service

Occurrence High

2.3.55 Secure software download not initiated correctly when using docsDevSwFilename in the config file


Description When docsDevSwFilename is used in the CM config file, secure software download will error out with a Configuration File CVC Validation Failure.

Impact Service

Occurrence High

2.3.56 Unable to establish QoS for Dual PRI trunking


Description Increased number of supported QoS classifiers for Dual PRI trunking applications to support 46 concurrent calls.

Impact Service

Occurrence High


2.3.57 Total Service Flow Maximum was too low


Description The internal service flow table had previously limited the combined US and DS flows to a maximum total of 64. The

count has been increased to 96 to support MGPI

functionality behind a cable modem.



Impact Service

Occurrence High

2.3.58 docsIfSigQMicroreflections MIB is incorrect


Description The docsIfSigQMicroreflections mib does not report accurately for 4 of the 8 downstreams in the TG852.

Impact Operational

Occurrence High

2.3.59 Incorrect Ring Cadence for incoming calls (Line 2 only)


Description When only line 2 is provisioned there is a short burst of ring splash on an incoming call rather than the provisioned ring

cadence.

Impact Operational

Occurrence High


2.3.60 Intermittent IGMP Memory Leak


Description A memory leak may occur when a leave message occurs within 3 seconds of a join message to the same multicast

group.

Impact Service

Occurrence Low

2.3.61 Modem Registration State not reported


Description Added arrisCmDoc30SwRegistrationState MIB for reporting the last step completed during DOCSIS and PacketCable



provisioning and registration.

Impact Operational

Occurrence High

2.3.62 MTA Does Not Send Option 122 in DHCP Renew


Description MTA was not requesting Option 122 in DHCP renew requests for updating provisioning information.

Impact Service

Occurrence High

2.3.63 arrisCmDoc30SetupTODSyncTimeout Could Not Be Set


Description Added arrisCmDoc30SetupTODSyncTimeout MIB for

enabling and for configuring the Time-of-Day synchronization

interval.

Impact Operational

Occurrence High

2.3.64 Intermittent Loss of Downstream Channel Bonding


Description When the cable modem receives partial MDD messages from overlapping secondary downstreams, the modem may

register in 1x1 mode. This problem has been observed

only on MCMTS.

Impact Service

Occurrence Low



2.3.65 Bulk Call Traffic issues

Tracking No. PROD00168462, PROD00166779, PROD00168046, PROD00163927, PROD00168575, PROD00168733,

PROD00168734

Description When Voice Quality Metrics monitoring is enabled, over an extended period of time, an internal firmware delay

could result in occasional traffic failures, where the line

fails to make or receive a call.

Impact Service

Occurrence Low

2.3.66 arrisMtaDevActiveConnections MIB always returns 0


Description The arrisMtaDevActiveConnections MIB was not returning the correct number of active connections per line.

Impact Operational

Occurrence High

2.3.67 Extreme robustness testing issue(s) under investigation


Description Modem may fail to register in bonded upstream mode after multiple cable cuts during registration. Modem will be in

partial service and self recovers after 15 minutes.

Impact Service

Occurrence Rare

The following issues were resolved in release 7.3.92A

2.3.68 No internet access due to corrupted TLV


Description Modem is unable to provide internet access after receiving corrupted L2VPN TLVs in the registration response.



Impact Service

Occurrence High

2.3.69 Repeated access to ARRIS Web pages can cause stability issues


Description Multiple connections to the ARRIS web pages may cause resource leakage on the modem, and lead to modems becoming

unstable.

Impact Service

Occurrence Low

2.3.70 Internal MAC found in the CPE list of the CM


Description Internal MAC address 0000.ca11.2233 is found in the CPE list of the CM. This reduces the maximum allowed number of

CPEs by one.

Impact Service

Occurrence Low

2.3.71 TG852: IGMPv3 Join and Leave issue


Description When executing D3.0 IP video multicast test, the TG852 does not process all the IGMPv3 Joins and Leaves properly.

Impact Service

Occurrence Low

2.3.72 CM Status Webpage Slow to load


Description CM Status webpage slow to load when there are multiple downstreams.

Impact Operational



Occurrence Low

2.3.73 SIP: Calls may not complete after recovery from an RF cut


Description Calls may not be able to complete after recovery from an RF cut during voice traffic that is long enough to cause a T4.

Impact Service

Occurrence High

2.3.74 SNMP MIB walk may cause an exception error


Description If the modem loses the primary downstream during voice traffic, an SNMP MIB walk may cause an exception resulting

in a reset.

Impact Service

Occurrence Low

2.3.75 Modem configured for CM only should prevent the call processing module to be initialized


Description Configuring DHCP option 122 suboption 3 to value of 0.0.0.0 needs to immediately stop the call processing initialization.

Impact Operational

Occurrence High


2.3.76 During modem registration, multiple exceptions caused E-MTA to reboot




Description When the E-MTA is provisioned as CM-only with an MTA Provisioning Server in 122.3 as 0.0.0.0, the E-MTA will run

into exceptions until the MTA is provisioned.

Impact Service

Occurrence Low

2.3.77 TG852: Filters in the CM configuration file may fail to block CPE access


Description For TG852, the filters that are set to discard the inbound or outbound packets from the CPE to the Ethernet fail to block the

access.

Impact Service

Occurrence High



Tracking No. See Below

Description PROD00163773: When on-hook and off-hook transitions occur during registration, it may cause the MTA to fail

registration with the SIP server.

PROD00162124: Modem failed to recover to its previous bonding mode after an RF cut during modem registration

test.

Impact Service

Occurrence Low




2.3.79 arrisCmDoc30SwServerAddress in string format causes registration failure


Description Modem in IPv4 failed to register with CMTS when the arrisCmDoc30SwServerAddress field was in string format

instead of an InetAddress. This issue is now fully resolved to

be interoperable with customer specified configuration file

format.

Impact Service

Occurrence High


2.3.80 arrisCmDoc30SwServerAddress in string format causes registration failure


Description Modem in IPv4 failed to register with CMTS when the arrisCmDoc30SwServerAddress field was in string format

instead of an InetAddress.

Impact Service

Occurrence High

2.3.81 Syslog message shows incorrect vendor type


Description Vendor type in syslog message for event 2417164298 Touchstone SW Upgrade Successful shows as DOCSIS and not ARRIS.

Impact Operational

Occurrence High



2.3.82 CM does not handle TLV43 properly in the configuration file


Description Modem failed to handle TLV43 encode for ARRIS Vendor Specific MIBs in the CM configuration file.

Impact Operational

Occurrence High

2.3.83 SIP: MTA does not ignore the hook flash if call is not fully established


Description If end point A calls B and B is still ringing, a hook flashes by A would cancel the call attempt and dialtone would be sent to A.

Impact Service

Occurrence Low

2.3.84 SIP: Line could be stuck in ringing state

Tracking No. PROD00162331, PROD00161681, PROD00162112, PROD00161630

Description When the MTA receives an Invite-Cancel message with the reason of local failure while the line is ringing then the ringing

was not getting canceled.

Impact Service

Occurrence Low

2.3.85 CM State Webpage may incorrectly display DHCP status


Description CM State tab on the modem WebGUI may incorrectly display DHCP status as Completed even when DHCP is still in progress.

Impact Operational

Occurrence High



2.3.86 SIP: sipCfgDialFeat and sipCfgDialProxy table issues

Tracking No. PROD00162282, PROD00162283, PROD00164701

Description The configuration changes to sipCfgDialFeat and sipCfgDialProxy tables were not getting correctly updated so

that the invites were not sending the expected digits to the

proxy.

Impact Service

Occurrence High

2.3.87 SIP: Telephony line LED stays off


Description Telephony line LED stays off if line was once registered then failed to register, then was finally able to re-register again.

Impact Operational

Occurrence High

2.3.88 SIP: Message Waiting Indicator not accepted via SNMP


Description When the MWI was set via SNMP, the correct settings were not stored in NVRAM.

Impact Operational

Occurrence High

2.3.89 Enrollment Inform Trap Message incorrectly set


Description The MtaDevProvisioningEnrollment Inform Trap message is being sent out incorrectly when the provisioning mode is

PacketCable.

Impact Operational

Occurrence Low

2.3.90 Voice calls may fail during high-speed downstream traffic




Description While performing bulk call traffic testing, an issue was noted where voice calls may fail when the downstream traffic was at

50Mbps.

Impact Service

Occurrence High


2.3.91 Delay Issues on E-MTA may cause Traffic and Feature Failures


Description PROD00159671: Class features such as three-way calling may fail.

PROD00159452: Fax calls may fail or fail to complete.

PROD00159451: When traffic was run between lines 1 and 2 on the same E-MTA, issues were observed with a low call

completion rate and voice quality.

Impact Service

Occurrence Low

2.3.92 arrisMtaDevCallStatsHookStatus not valid when accessed from CM IP


Description The value of the arrisMtaDevCallStatsHookStatus MIB was always onhook when read using the CM IP. This has been

corrected to provide the correct hook status of the line's from

the CM or MTA IP.

Impact Operational

Occurrence High



2.3.93 PacketCable Option 177 Configuration and Display Issues


Description The following issues all relate to PC Option 177 provisioning:

PROD00163074: The MTA recognizes the DNS server value sent in option 6 (dns server option) but does not

recognize the value sent in option 177.4 (primary dns server

IP) or the value sent in option 177.5 (secondary dns server

IP).

PROD00163122: The DHCP Web Page for the MTA incorrectly displays a value of zero for the CableLabs Client

Configuration Option 177 and Option 122. In addition the

field for the security ticket invalidation incorrectly reports

the suboption type as "9" instead of "12".

PROD00163295: When provisioning configuration is pcable_177, the E-MTA only accept DNS options 177.4 and

177.5. We now allow option 6 to be used if all else fails.

Impact Service

Occurrence Low

2.3.94 SIP: EURO Prefix Missing on SysDescr


Description The SysDescr is missing the EURO designation.

Impact Operational

Occurrence High

2.3.95 DCID may be Reported Incorrectly after DCC


Description If the CMTS calls for a DCC using the unicast, ranging or direct techniques, the DCID is reported as 0 in both the MIB

browser and the RF CLI.

Impact Operational

Occurrence Low



2.3.96 Firmware Upgrade Failure Event Missing for CVC Error


Description A CVC Fail event was not being sent when a firmware upgrade failed because of a bad or missing CVC.

Impact Operational

Occurrence High

2.3.97 SIP: CallerID Display Issue with PAID Header


Description When the incoming SIP invite contains quotes in the PAID Header, the quotes will be presented to the phone

Impact Operational

Occurrence High

2.3.98 Voice Quality Metric Issues


Description The following issues are all related to the ARRIS VQM feature.

PROD00152561: The arrisMtaDevVqmThresholds MIB does not report an error on the MIB browser after setting an

invalid value.

PROD00152388: If the arrisMtaDevVqmThresholds MIB is set during a call, the syslog is not generated.

PROD00152270: The MIB arrisMtaDevVqmCallNumberIdentifier will not be updated

to point to the last call location.The MIB

arrisMtaDevVqmCallNumberIdentifier will not be updated

to point to the last call location.

Impact Operational

Occurrence High



2.3.99 Battery Telemetry Log Events had incorrect Priority Level


Description The battery telemetry log events had a priority level of informational instead of minor.

Impact Operational

Occurrence Low

2.3.100 North America Tone Template Issue


Description For NA tone templates outside of the default NA33 plan, a tone conversion issue may exist. This can result in impacts to the

NA dial tone resulting in a short stutter after the initial 5

seconds of dial tone.

Impact Service

Occurrence Low

2.3.101 E-MTA in PSM may drop calls after 30 minutes


Description When the modem is in Power Save Mode (PSM), active voice calls may drop after 30 minutes into the call.

Impact Service

Occurrence Low

2.3.102 LAN interface does not support loopback mode


Description LAN interface does not recover after loopback cable has been disconnected.

Impact Service

Occurrence Reset the unit



2.3.103 MU Security Failures


Description PROD00156099: Security testing with the MU Analytics security suites failed on LAN Port test due to watchdog

error and telnet lock up.

PROD00159663: Sending mutated SNMP Get Bulk Messages caused a hard failure.

PROD00159668: Remote telnet server may be vulnerable to a buffer overflow attach.

PROD00159664: Mutated telnet packet causes telnet failure

Impact Service

Occurrence Low

2.3.104 Incorrect Australian Ring Cadence


Description The default ring cadence values for Australia country code template were incorrect.

Impact Service

Occurrence High

2.3.105 MTA may fail to detect DTMF digits with a positive twist value greater than 4 dB


Description When using certain CPEs with a positive twist greater than 4 dB, difference in power between the two frequencies of a

DTMF signal, MTA may fail to detect all the digits. Please

note that DTMF positive twist greater than 4 dB is out of

specifications.

Impact Service

Occurrence High



2.3.106 SIP: sipCfgDoc30FeatureSwitch MIB Walk Issue


Description MTA MIB Walk on sipCfgDoc30FeatureSwitch returns wrong type error.

Impact Operational

Occurrence High

2.3.107 Registration failures after DCC with S-CDMA bonded upstreams


Description When testing DCC with the S-CDMA modulation profile, MTA may fail to register on the new downstream, resulting in T4s

and re-registration to the original downstream.

Impact Service

Occurrence High

2.3.108 SSH Timeout Failure


Description Occasionally during an automated testing run, a timeout will occur when logging into the modem via SSH. Subsequent

attempt work fine.

Impact Operational

Occurrence Low

2.3.109 Extreme robustness testing issue


Description During extreme RF tests, some calls may fail with no dial tone.

This issue has been resolved as it can no longer be reproduced.

Impact Service

Occurrence Rare




2.3.110 Configure Model 8 units for Maximum battery HUT


Description Adjust firmware settings on Model 8 units to achieve maximum battery hold up time.

Impact Service

Occurrence High

2.3.111 Modem may become unpingable after extended RF cable cuts


Description After recovery from server RF impairment conditions, the modem may become unpingable and require a modem reset to

recover.

Impact Service

Occurrence High


2.3.112 arrisMtaDevDhcpMtaIpAddr returns 0.0.0.0


Description MIB walk of arrisMtaDevDhcpMtaIpAddr.0 returns 0.0.0.0 instead of actual MTA IP address.

Impact Operational

Occurrence High



2.3.113 SIP: Invalid REGISTER messages may cause MTA loss of Communications


Description When a MTA was bombarded by invalid REGISTER messages, MTA would respond back with 404 (Not Found) messages.

Since the attacker does not ACK back to the 404 responses, this

could consume SIP transaction resources on the MTA and

eventually disrupted normal registration. Impact Service

Occurrence Low

2.3.114 DCC DS/US move may fail in 1x1 Configuration


Description CM may reject DCC messages when CMTS sets the Multiple Receive Channel (MRC) TLV to a non-zero value on 1x1

configurations.

Impact Service

Occurrence Low

2.3.115 arrisMtaDevProvMethodIndicator issue with BASIC.2


Description CM did not ignore the arrisMtaDevProvMethodIndicator when set to ARRIS BASIC.2 which caused registration failures.

Since DOCSIS 3.0 does not support ARRIS BASIC.2, CM

should ignore and default to PacketCable BASIC.1.

Impact Service

Occurrence High



2.3.116 arrisCmDoc30SwServerAddress implemented incorrectly


Description arrisCmDoc30SwServerAddress MIB walk would return the value in ASCII format instead of octet string which is required

for InetAddress. Impact Operational

Occurrence High

2.3.117 Active call may drop due to remote call metrics data


Description Active call may drop if there is a party on hold during 3WC or Call-Waiting. This may occur on certain call-management-

servers when Remote Voice Metrics are enabled and any end of

call stats value contains a + or > symbol.

Impact Service

Occurrence Medium

2.3.118 SIP: MTA Provisioning fails with no Option 122 subOption 3


Description For SIP release, the GUPI and GUPI Encrypted provisioning methods will not successfully provision the MTA when there is

no entry in Option 122 subOption 3.

Impact Service

Occurrence High



2.3.119 SIP: E-MTA may lose Registration with the Proxy


Description There have been occasions where the SIP MTA no longer sends the required periodic registrations to the proxy. There is an

internal timer on the MTA that determines the time before

sending the next registration request. Failed cases show this

timer being set to a very large number. A reset of the MTA is

required to recover the registration. Impact Service

Occurrence Rare

2.3.120 LAN Fails to Power Up following MIB walk during AC Power Failure


Description If the operator walks the ifAdminStatus MIB while the modem is in power save mode with the LAN ports powered down,

those ports will remain powered down even after AC power

recovers.

Impact Service

Occurrence Low

2.3.121 Power Save Management not fully implemented


Description Power Save Management feature to maximize battery hold-up time for TM802 Telephony Modems may not fully meet the

specified battery hold-up times.

Impact Operational

Occurrence Low



2.3.122 SIP: MU Security Failures


Description Security testing with the MU Analytics security suites indicates errors in handling certain corruptions and attacks on

the SIP, HTTP and SSH ports. Impact Service

Occurrence High

2.3.123 Unable to set ARRIS Custom MIBs


Description If SNMP Coexistence has been provisioned in the MTA config file using the traditional PC1.0 MIBs, then the user will be

unable to set any of the ARRIS MIBs. Use PC1.5 Coexistence

provisioning mechanism.

Impact Operational

Occurrence High



Description PROD00158378: An RF cut during modem registration may cause the CPE device to temporarily stop receiving

data packets.

Impact Service

Occurrence Rare

2.3.125 DCC failure on multiple techniques


Description PROD00157399: The E-MTA failed technique 3 on a DOCSIS 2.0 CMTS when the DS and US were changed.

PROD00157428: DCC Load Balancing on the US using technique 1 works inconsistently.

Impact Service



Occurrence High


2.3.126 Call Progress Tone may not default to correct value


Description Call progress tone were not correctly set to the default values for the country that is provisioned in

ppCfgMtaCountryTemplate.

Impact Service

Occurrence High

2.3.127 DTMF event ascending not working


Description DTMF Event Ascending failed to work on DOCSIS3.0 releases. arrisMtaDevDTMFEndEventForceAscending MIB object has

now been added to TS7.3 releases.

Impact Operational

Occurrence Low

2.3.128 CLI tapi command not accessible


Description CLI tapi command to access TLM information was not accessible via the Password of the Day.

Impact Operational

Occurrence High



2.3.129 LVM: WebGUI displays incorrect maintenance timer value


Description LVM Maintenance Timer under the Advanced product details Web page always show 0 minutes.

Impact Operational

Occurrence High

2.3.130 SECURE provisioning failures due to incorrect MAC calculation


Description Secure provisioning will fail for modems with Cable Modem MAC Addresses with the last octet ending in 0xFF. The MTA

certificate will be corrupted causing the security association

fail.

Impact Service

Occurrence High

2.3.131 TFTP download retry mechanism Issue


Description During an upgrade TFTP process, eMTA could result in sending endless TFTP read requests if a download fails.

Impact Service

Occurrence Low

2.3.132 Opened ports detected during NMAP port scan


Description NMAP port scan test showed number of opened ports. NMAP test is to verify that the modem blocks any attempts to scan

ports on the eMTA or attached CPEs.

Impact Service

Occurrence High



2.3.133 CM-STATUS Inter operability issues with options


Description During QAM/FEC Recovery events, CM-STATUS messages were including downstream information for all previously

recovered downstreams.

Impact Service

Occurrence High

2.3.134 E-MTA with extended registration times


Description An issue has been identified where an upstream redirect leads to a modulation profile change where IUCs are different could

cause eMTA to take a longer period of time to register.

Impact Service

Occurrence Rare

2.3.135 arrisCmDoc30DhcpCmIpAddr implemented incorrectly


Description arrisCmDoc30DhcpCmIpAddr MIB walk would return the value in ASCII format instead of octet string which is required

for InetAddress.

Impact Operational

Occurrence High

2.3.136 Line Card state MIB returns IDLE for unprovisioned lines


Description In TS7.3 DOCSIS3.0 releases, arrisMtaDevLineCardState MIB will return a value of IDLE (1) for unprovisioned lines. Previously, DOCSIS2.0 releases would return a value of (0) which is Out Of Service. The 0x4 callp feature bit in the

ppCfgMtaCallpFeatureSwitch is now supported in TS7.3

releases the ability for the MSO to configure the eMTA to

return a value of (0) for unprovisioned lines.



Impact Operational

Occurrence Low

2.3.137 LAN port may not power up after AC Power is restored


Description If you reboot the modem while it is running on battery (or if you boot from battery) and then restore AC power within the

first 5 minutes, the LAN will stay powered down and the

modem will remain in 1x1 bonding mode until the modem is

rebooted again.

Impact Service

Occurrence High

2.3.138 LVM: Policy 3 reset timer does not reinitialize to the default value


Description When the LVM policy is set to 3 and the reset timer, pktcEnNcsEndPntLVMgmtResetTimer, is set, the timer will

start to count down once the MTA starts to reset. However,

after the MTA returns to service, the reset timer does not

reinitialize but continues to count down upon the next loss of

loop voltage.

Impact Service

Occurrence High

2.3.139 T.38: E-MTA Reset due to WATCHDOG


Description E-MTA may reset with reset reason of WATCHDOG on certain inbound T.38 Fax calls.

Impact Service

Occurrence Low



2.3.140 LVM: Policy 3 Loop Voltage Removal


Description On LVM policy 3, loop voltage may be removed approximately 30 seconds after a reset when the eMTA is in bonded upstream

mode even if a valid reset or maintenance timer setting is in

place.

Impact Service

Occurrence High

2.3.141 OOR Condition due to CPE Clearing


Description It is possible that there is a period of time after the CPE behind the modem becomes inactive or lost, the packet sequence

numbers become out of sync between the CMTS and the CM.

If a DS traffic session destined to the CPE remains active, it

could cause the OOR condition on the DSID. SNMP access,

pings to the CM IP address, and data traffic will fail until the

modem is recovered from the OOR condition.

Impact Service

Occurrence High

2.3.142 Call Drops after 200 Seconds


Description Due to E-MTA sending incorrect DSC-REQ message, an active call was being dropped after 200 seconds.

Impact Service

Occurrence Low

2.3.143 SIP: T.38 Call Failure


Description When placing a call using T.38, the first call failed due to E-MTA incorrectly using the wrong active call-leg.

Impact Service

Occurrence Low



2.3.144 resetMTA does not clear line gain control settings


Description The arrisMtaDevEndPnt MIBs are not set back to the default value (or persistent NVM value) upon an MTA reset.

Impact Operational

Occurrence High


2.3.145 E-MTA uses Test Root certificate by Default


Description In this release of firmware, the E-MTA now uses the real root certificate by default instead of the test root certificate. This

issue only affects Full PacketCable provisioning modes.

This issue is documented in AFB-10-0306.

Impact Service

Occurrence Low

2.3.146 Issue bonding against higher frequencies on a CMTS


Description An issue has been identified in some CMTSs where the CMTS improperly selects the CLAB-6M-004 RCP which has an upper

frequency limit of 867 MHz. The CMTS then attempts to

assign the modem to channels above the frequency limit. Per

the specification, a modem should reject this request. However,

to resolve this issue this specification is no longer enforced.

Impact Service

Occurrence High



2.3.147 Issue upgrading using a co-signed image


Description If the PKCS7 headers on an image exceeded a certain size, the new firmware download engine could be forced into an unusual

path in which the image was verified but the wrong data was

written to flash. This resulted in a failed download after a

successful download message has been received.

Impact Operational

Occurrence High

2.3.148 TM802 only registers in 1x1 mode


Description Certain CMTSs may not properly handle RCPs in the REG-REQ. By adjusting the order of the RCPs, the parsing

algorithm on the CMTS works correctly and modem can

registered in a bonded mode.

Impact Service

Occurrence High

2.3.149 Provisioning fails due to Illegal TLV11 in configuration file.


Description The firmware has been updated so that if ARRIS MIB Objects in the configuration file missing the index value, provisioning

will still successfully complete.

Impact Service

Occurrence Low



2.3.150 Power Save Mode may cause E-MTA reboot


Description When AC power is lost on the E-MTA, the E-MTA will no longer operate in bonded mode to reserve battery backup. An

issue has been identified with some older CMTS software loads

that required the addition of a new SNMP MIB object to handle

this change to partial service mode. The MIB,

arrisCmDoc30SetupPowerSaveMode, has been added to allow

PowerSaveMode to work with these older versions of CMTS

SW. The MIB settings are as follows:

reinitmac(1): allows CM to enter PSM when operating with older CMTS software versions.

partialservice(0) is the default behavior for CMTSs that fully support partial service.

Impact Service

Occurrence Low

2.3.151 SDP Payload may cause Bandwidth Error


Description A call from an IMS subscriber to an ARRIS NCS subscriber may result in a 510 Protocol Error on the ARRIS E-MTA. The

root cause is in the SDP payload when the bandwidth

information "b=AS:X" and "b=TIAS:Y" are both present.

Impact Service

Occurrence High

2.3.152 LVM: Policy 3 loop voltage removal


Description On LVM policy 3, loop voltage may be removed approximately 30 seconds after the RF cable is cut when the MTA is in bonded

Upstream mode even if a valid reset or maintenance timer

setting is in place.

Impact Service

Occurrence High



2.3.153 Classifiers are not deleted


Description After a T4, the classifiers were not getting deleted throughout the firmware. As a result, the classifiers list continually

expanded increasing the number of elements that had to be

traversed during classification.

This issue is documented in AFB-10-307.

Impact Service

Occurrence Low

2.3.154 Alarm Panel failure due to network delay


Description Alarm panels may fail to download the configuration file if the network delay is excessive.

Impact Service

Occurrence Rare

2.3.155 Battery charging issue


Description A new release of the battery charger firmware is available in this release to resolve issues noted with the battery charge time.

Impact Operational

Occurrence High



2.3.156 Voice call with data traffic may cause issues


Description The following issues have been identified in the lab when voice traffic and high utilization data traffic are running

simultaneously:

PROD00159080: The MOS score is occasionally below a baseline of 4.0.

PROD00159081: The E-MTA occasionally resets.

PROD00159082: One-way delay exceeds baseline.

PROD00159083: Call completion rate below baseline.

Impact Service

Occurrence Low

2.3.157 Time between off-hook and voice path too great


Description The post-pickup-delay (PPD) is defined as the time between off-hook answer and voicepath established. This time was

greater than baseline.

Impact Service

Occurrence Low

2.3.158 upsEstimatedMinutesRemaining does not report the correct time


Description The SNMP MIB Object, upsEstimatedMinutesRemaining, does not report the correct amount of time remaining in the battery

once AC power is disconnected.

Impact Operational

Occurrence High



3 Letter of Operational Considerations The Letter of Operational Considerations is to inform operators of any system

considerations for the Touchstone Firmware that may affect service, operations, or

maintenance for this product release.

3.1 DOCSIS Operational Considerations

Listed are known Operational Considerations that have been identified during ARRIS standard quality testing that can affect normal operation. Any additional items

discovered during field deployments would be noted in future Release Notes and Letter of Operational Consideration or Field Bulletins. Unless specifically noted, it is ARRIS intention to have all considerations resolved in future product releases.

3.1.1 Modem May Reset with guiEncrypted Provisioning Methods


Description When using the gupiEncryptedMacMta and gupiEncryptedMtaConfig provisioning methods for Legacy SIP

provisioning methods, some installations may intermittently fail

while reading the MTA config file causing the modem to reset.

Impact Service

Occurrence Low

Workaround None

3.1.2 Event 2417164297 may not be logged during upgrade


Description When using SNMP to set MIB arrisCmDoc30SwFilename to a file that is not present on the TFTP server, event 2417164297 is

not logged.

Impact Operational

Occurrence High

Workaround None





Description PROD00163429: Modem failed to recover to its previous bonding mode after an RF cut during modem registration

test.

PROD00163927, PROD00168046: A rare condition was seen during extreme robustness testing where a modem

failed to recover dial tone.

Impact Service

Occurrence Low

Workaround None



3.2 Unsupported Features

The following features are not supported in the TS 7.3 release at this time.

ARRIS WAN Isolation Feature

PacketCable 1.5 Event Reporting Mechanism

Voice / Media Security (Encryption of RTP stream capabilities)

Voice Payload Header Suppression

Silence Suppression and UGS/AD Service Flows

PacketCable 2.0



3.3 Upgrade Considerations

The following considerations are important to take into account when upgrading to this

firmware release.

Model 7 Requires 7.1.98 or Later

Support for Model 7 hardware (TM702/TM722/WBM750/WBM760) was added to TS 7.3 in 7.3.108. These Model 7 units with firmware less than 7.1.98 will need to be upgraded to 7.1.98 or later prior to upgrading to TS 7.3.

Downgrade Limitation

Due to changes in NVRAM settings, downgrade to a release below TS 7.3.55 is no longer

supported.

sysObjectID MIB Object Format Change

Starting in TS7.3 DOCSIS 3.0 releases, the sysObjectID MIB walk with OID

1.3.6.1.2.1.1.2.0 will no longer display the firmware release version. Please use the

sysDescr.0 (1.3.6.1.2.1.1.1.0) or docsDevSWCurrentVers (1.3.6.1.2.1.69.1.3.5.0) MIBs

to obtain the E-MTA firmware release.

Data Shutdown Timer Default Change

Starting in TS7.3.55, the Power Save Management (PSM) feature added in TS7.3.46 has

been changed to shut down the LAN interface after 5 minutes after AC power is lost.

The previous default time before shutdown was 15 minutes after AC power was lost.

arrisMtaDevLineCardState Returns IDLE for Unprovisioned Lines

In TS7.3 DOCSIS3.0 releases, arrisMtaDevLineCardState MIB will return a value of

IDLE(1) for unprovisioned lines. Previously, DOCSIS2.0 releases would return a value of (0) which is Out Of Service. Starting in TS7.3.55, the following 0x00000004 callp feature switch bit in the ppCfgMtaCallpFeatureSwitch adds the ability for the MSO to

configure the eMTA to return a value of (0) for unprovisioned lines.

0x00000004: If line is not provisioned show 0(OOS) rather than IDLE for

arrisMtaDevLineCardState

CMTS Compatibility Issue with Bonded Downstream Channels

The WBM gets placed into a permanent reject(na) state by some CMTS equipment when

the REG-ACK is sent containing a "partial service" confirmation code. This is an issue



on the CMTS and not how the DOCSIS specification defines this type of operation. To

review the specification, please refer to DOCSIS 3.0 specification CM-SP-MULPIv3_0-

I09-090121.pdf Annex C.4 Table C-6 for the partial service code referred to above. It is

important to make sure your CMTS is upgraded to the DOCSIS 3.0 revision to avoid this

problem and a possible service interruption.

TS7.3 Firmware Release and C4 CMTS Compatibility

The TS7.3 firmware release is compatible with C4 CMTS releases 7.1.1.42 and later. An

E-MTA running this release of firmware with an C4 CMTS software prior to 7.1.1.42

will experience issues when attempting to use downstream channel bonding. Please

make sure the C4 CMTS is upgraded prior to installing this new release.

MTA DHCP Option 60 Modification

In order to maintain backwards compatibility with deployed MSO provisioning sytems,

the TS7.3 release advertises a reduced MTA DHCP capabilities string that removes

several "optional" features (T.38, V.152, MGPI, etc) not supported in this release.

ARRIS Proprietary Provisioning Method

The TS7.3 firmware no longer support the use of CPS, SingleMAC, or ARRIS PacketCable proprietary provisioning methods. ARRIS recommends that customers convert to one of the new PacketCable 1.5 provisioning methods listed in the feature

sections. These methods are automatically handled through DHCP Option 60 SubOption

18 which advertises the supported MTA provisioning flows to the provisioning server.

New ARRIS DOCSIS 3.0 CM MIB Tree

For the TS7.3 release, the ARRIS CM MIBs have been created on their own MIB tree as

to not interfere with existing ARRIS MIBs from previous DOCSIS 2.0 releases. The new

branch is called arrisCmDoc30MIB. The new MIBs start at the following OID:

1.3.6.1.4.1.4115.1.3.4.

Documents

TS 7.3.139-RNLOC DOCSIS (1.0)