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
Document date
Release 1.0
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
January 12, 2012
Draft, v0.1
Approved, v1.0
Table of Contents
1
OBJECTIVES OF THIS DOCUMENT _____________________________ 1

1.1
1.2
1.3
1.4
1.5
1.6
DOCSIS NEW PRODUCT FEATURES _________________________________ 5

RESOLVED FIELD BULLETIN(S) ____________________________________ 11
DOCSIS RESOLVED PRODUCT DEFICIENCIES _________________________ 12
LETTER OF OPERATIONAL CONSIDERATIONS _________________ 58

3.1
3.2
3.3
1
1
1
2
2
4
RELEASE NOTES ___________________________________________ 5

2.1
2.2
2.3
ARRIS COMMITMENT ____________________________________________

PURPOSE AND SCOPE OF THIS DOCUMENT _____________________________
PRODUCT IDENTIFICATION AND PURPOSE OF RELEASE ___________________
FIRMWARE FILENAME VARIANT INFORMATION _________________________
MINIMUM FIRMWARE BASELINE FOR HARDWARE _______________________
PRODUCT DOCUMENTATION _______________________________________
DOCSIS OPERATIONAL CONSIDERATIONS ___________________________ 58

UNSUPPORTED FEATURES ________________________________________ 60
UPGRADE CONSIDERATIONS ______________________________________ 61
CUSTOMER SERVICE AND SUPPORT__________________________ 65
APPENDIX A: COMPLIANCE MATRIX _____________________________ 66
Touchstone Telephony Firmware - Release 7.3.139
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
SysDescriptor
PacketACE
TS0703139_122011
SW_REV: 7.3.139
DOCSIS 3.0 PacketACE Release 3.29 or later
Release Notes & Letter of Operational Consideration
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
_NA
PURPOSE OF EXTENSION
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 <HW Type>
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 SCDMA 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.
10
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
11
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
Impact
MTA is not processing proxy messages correctly when they

contain more than one Contact header.
Service
Occurrence
High
2.3.2
SIP: Audio Not Resumed After Call Hold
Tracking No.
PROD00176707
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
12
2.3.3
TM804: Cant access MTA MIBs for Lines 3 & 4
Tracking No.
PROD00177761
Description
Impact
On a TM804, line 3 & 4 information could not be accessed for

the following MIBs:
ppSurvPortMaintState
ppSurvPortLcDiagRequest
ppSurvPortLcDiagLastResult
ppSurvPortTable
Service
Occurrence
High
2.3.4
MTA rejects MDCX message during 3WC
Tracking No.
PROD00177793, PROD00176092
Description
Impact
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.
Service
Occurrence
High
2.3.5
SIP: Blind Transfer Call Failures
Tracking No.
PROD00177660, PROD00174209
Description
Impact
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).
Service
Occurrence
High
2.3.6
Scanning Override Page Not Functional
Tracking No.
PROD00178685
Description
Impact
For ARRIS TM822 and TG862 products, the scanning override

webpage will crash when accessed while the modem is
scanning.
Service
Occurrence
High
13
2.3.7
BSOD Functionality
Tracking No.
PROD00177558, PROD00177557, PROD00177010
Description
Impact
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.
Service
Occurrence
High
2.3.8
BSoD traffic fails when frame size is 1526 bytes to

CMTS
Tracking No.
PROD00174040
Description
Impact
1526 byte packets (double tagged packets) arriving at the

CMTS with double tags and then forwarded downstream appear
to be blocked.
Operational
Occurrence
Rare
2.3.9
Incorrect Australian template defaults
Tracking No.
PROD00175875
Description
Impact
The Australian country code template settings for WT1 and

hook-flash timing did not match DOCSIS 2.0 default values.
Service
Occurrence
High
14
2.3.10
No CallerID displayed for Brazil template
Tracking No.
PROD00177272
Description
Impact
When using the Brazil country code template, CallerID

information was not displayed using DTMF signaling protocols.
Service
Occurrence
High
2.3.11
DS LED is Amber when NACO is OFF with DS Bonding
Tracking No.
PROD00177119
Description
Impact
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.
Service
Occurrence
High
2.3.12
CM Activity Not Stopped after RNG-ABORT message
Tracking No.
PROD00175765
Description
Impact
When the CMTS send a Ranging-ABORT message, the CM

must stop all activities on the upstream.
Service
Occurrence
High
2.3.13
Downstream TCP Throughput below Benchmark
Tracking No.
PROD00174082
Description
Impact
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.
Service
Occurrence
Medium
15
2.3.14
Slower Registration Times for Broadcast IM Ranging

Opportunities
Tracking No.
PROD00153458
Description
Impact
E-MTAs using Broadcast IM ranging opportunities for nonprimary US acquisition may observe slower registration times
and more instances of US partial-service.
Service
Occurrence
Low
2.3.15
Web GUI displays incorrect MTA boot file nam
Tracking No.
PROD00163294
Description
Impact
The MTA boot file field under the DHCP Web page displays
garbled information when MTA provisioning is not complete.
Operational
Occurrence
High
2.3.16
SIP: Port 2427 opened
Tracking No.
PROD00160196
Description
Impact
Test showed that port 2427 was incorrectly opened when using
SIP load.
Operational
Occurrence
High
2.3.17
Wrong tones for ChileT Country Code Template
Tracking No.
PROD00174229
Description
Impact
Add support for ChileT country code template to support

customized customer dialtone and ringback tones.
Service
Occurrence
High
16
2.3.18
PCMM: Service Flow and Classifiers not correctly setup
Tracking No.
PROD00174548
Description
Impact
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.
Service
Occurrence
High
2.3.19
SIP Hook-Flash Event Reporting Support
Tracking No.
PROD00173562
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
Tracking No.
PROD00174627
Description
Impact
Add SIP support for caching the last DNS records in case the
next DNS query fails.
Service
Occurrence
High
2.3.21
MTA fails to recognize Hook-Flash detection
Tracking No.
PROD00175740
Description
Impact
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.
Service
Occurrence
High
17
2.3.22
CM Activity Not Stopped After RNG-ABORT message
Tracking No.
PROD00175765
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
Tracking No.
PROD00174077
Description
Impact
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.
Operational
Occurrence
High
2.3.24
Speedtest support is missing on CM820
Tracking No.
PROD00174079
Description
Impact
Internal speed test application support is missing on the

CM820.
Operational
Occurrence
High
18
2.3.25
SIP: P-Preferred-Identity Header uses wrong domain

name after 407 challenge
Tracking No.
PROD00173742, PROD00173163
Description
Impact
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.
Service
Occurrence
High
2.3.26
pNe!!! error log resulting in no dialtone
Tracking No.
PROD00173345
Description
Impact
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.
Service
Occurrence
High
2.3.27
SIP: No Support for Standard INFO Hook Flash
Tracking No.
PROD00173562
Description
Impact
The SIP feature (provisionable by Sip Feature Switch) to enable

standard hook-flash reporting with the SIP INFO message does
not work.
Service
Occurrence
High
2.3.28
Upstream interoperability problems in STDMA mode
Tracking No.
PROD00172625
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.
19
Impact
Service
Occurrence
High
2.3.29
CM Config File limited to 16 NM Access Filters
Tracking No.
PROD00172083
Description
Impact
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.
Operational
Occurrence
High
2.3.30 Modems may Fail to Bond against Cisco 10K CMTS

Tracking No.
PROD00173112, PROD00173389
Description
Impact
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.
Service
Occurrence
High
2.3.31 SIP: End of Call stats not spec compliant

Tracking No.
PROD00173529, PROD00163871
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

Tracking No.
PROD00169429
Description
In certain customer configurations with MDF enabled, RIPv2

packets from CPE devices were not correctly passed by the
20
modem to CMTS and northbound routers.

Impact
Service
Occurrence
High
2.3.33 Incorrect units for Average Signaling Latency MIB

Tracking No.
PROD00171380
Description
Impact
The value returned for the arrisMtaDevSignalingAvgLatency

MIB was not in the milliseconds format.
Operational
Occurrence
High
2.3.34 DST doesn't work with Australia/New Zealand time

Tracking No.
PROD00171830
Description
Impact
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.
Operational
Occurrence
High
2.3.35 RIPv2 packets from LAN side router not forwarded

Tracking No.
PROD00169429
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
Tracking No.
PROD00167200
Description
Added support for handling of Partial Services fallback mode
21
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

Tracking No.
PROD00163762
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

Tracking No.
PROD00171388
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

Tracking No.
PROD00171863
Description
Impact
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.
Service
Occurrence
High
22
2.3.40 Possible MTA reset if SIP Digit Map incorrectly

configured
Tracking No.
PROD00171135
Description
Impact
If the sipCfgDigitMap MIB is provisioned to an invalid length,

then an exception may occur on the modem while generating an
error log entry.
Service
Occurrence
High
2.3.41 BPI Disabled Caused Slower Upload Speeds

Tracking No.
PROD00168534
Description
Impact
Modems operating with BPI disabled may have slower

upstream throughput on some CMTSs that incorrectly handle a
version field of 0.
Service
Occurrence
Medium
2.3.42 Telnet Sessions Not Reset

Tracking No.
PROD00170054
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
Tracking No.
PROD00169814
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
23
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
Tracking No.
PROD00170136
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
Tracking No.
PROD00169300
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

Tracking No.
PROD00169320, PROD00169473
Description
Impact
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.
Operational
Occurrence
High
24
2.3.47 Modem May not Bond on Some DS channels

Tracking No.
PROD00166427
Description
Impact
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.
Service
Occurrence
Medium
2.3.48 SNMP mib get/walk of DS power levels could cause

disruption during active calls
Tracking No.
PROD00169538
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

Tracking No.
PROD00168865
Description
Impact
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.
Service
Occurrence
Low
2.3.50 Duplicate TLV11 Entry Prevent Modems from Being

Operational
Tracking No.
PROD00169064
Description
Duplicate TLV11 in the CM config file may prevent the

provisioned modem from becoming operational.
High
Occurrence
25
Impact
Service
2.3.51 TM804: Incorrect default for Line 4 Endpoint Dialing

method
Tracking No.
PROD00169596
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

Tracking No.
PROD00168891, PROD00169660
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
Tracking No.
PROD00170668
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
26
2.3.54 No speech path between two T.38 enabled endpoints

Tracking No.
PROD00170933, PROD00132117
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
Tracking No.
PROD00170814
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

Tracking No.
PROD00168867
Description
Impact
Increased number of supported QoS classifiers for Dual PRI

trunking applications to support 46 concurrent calls.
Service
Occurrence
High
2.3.57 Total Service Flow Maximum was too low

Tracking No.
PROD00169170, PROD00168867
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.
27
Impact
Service
Occurrence
High
2.3.58 docsIfSigQMicroreflections MIB is incorrect

Tracking No.
PROD00167459
Description
Impact
The docsIfSigQMicroreflections mib does not report

accurately for 4 of the 8 downstreams in the TG852.
Operational
Occurrence
High
2.3.59 Incorrect Ring Cadence for incoming calls (Line 2 only)

Tracking No.
PROD00168861
Description
Impact
When only line 2 is provisioned there is a short burst of ring

splash on an incoming call rather than the provisioned ring
cadence.
Operational
Occurrence
High
2.3.60 Intermittent IGMP Memory Leak

Tracking No.
PROD00167686
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

Tracking No.
PROD00167737
Description
Added arrisCmDoc30SwRegistrationState MIB for reporting

the last step completed during DOCSIS and PacketCable
28
Impact
provisioning and registration.

Operational
Occurrence
High
2.3.62 MTA Does Not Send Option 122 in DHCP Renew

Tracking No.
PROD00168105
Description
Impact
MTA was not requesting Option 122 in DHCP renew requests

for updating provisioning information.
Service
Occurrence
High
2.3.63 arrisCmDoc30SetupTODSyncTimeout Could Not Be Set

Tracking No.
PROD00167692
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

Tracking No.
PROD00166344
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
29
2.3.65 Bulk Call Traffic issues

Tracking No.
Description
PROD00168462,
PROD00166779,
PROD00168046,
PROD00163927,
PROD00168575,
PROD00168733,
PROD00168734
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

Tracking No.
PROD00167140, PROD00165893
Description
Impact
The arrisMtaDevActiveConnections MIB was not returning the

correct number of active connections per line.
Operational
Occurrence
High
2.3.67 Extreme robustness testing issue(s) under investigation

Tracking No.
PROD00161871
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

Tracking No.
PROD00168619, PROD00168421
Description
Modem is unable to provide internet access after receiving

corrupted L2VPN TLVs in the registration response.
30
Impact
Service
Occurrence
High
2.3.69 Repeated access to ARRIS Web pages can cause

stability issues
Tracking No.
PROD00165966
Description
Impact
Multiple connections to the ARRIS web pages may cause

resource leakage on the modem, and lead to modems becoming
unstable.
Service
Occurrence
Low
2.3.70 Internal MAC found in the CPE list of the CM

Tracking No.
PROD00165244
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

Tracking No.
PROD00168338, PROD00166399
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

Tracking No.
PROD00166806
Description
CM Status webpage slow to load when there are multiple

downstreams.
Impact
Operational
31
Occurrence
Low
2.3.73 SIP: Calls may not complete after recovery from an RF

cut
Tracking No.
PROD00166506
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

Tracking No.
PROD00167460
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
Tracking No.
PROD00166848, PROD00166930
Description
Impact
Configuring DHCP option 122 suboption 3 to value of 0.0.0.0

needs to immediately stop the call processing initialization.
Operational
Occurrence
High
2.3.76 During modem registration, multiple exceptions caused

E-MTA to reboot
Tracking No.
PROD00166163, PROD00166409
32
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
Tracking No.
PROD00165084
Description
Impact
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.
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
33
2.3.79 arrisCmDoc30SwServerAddress in string format causes

registration failure
Tracking No.
PROD00165939, PROD00164588
Description
Impact
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.
Service
Occurrence
High
2.3.80 arrisCmDoc30SwServerAddress in string format causes

registration failure
Tracking No.
PROD00164588, PROD00162826
Description
Impact
Modem in IPv4 failed to register with CMTS when the

arrisCmDoc30SwServerAddress field was in string format
instead of an InetAddress.
Service
Occurrence
High
2.3.81 Syslog message shows incorrect vendor type

Tracking No.
PROD00163723
Description
Impact
Vendor type in syslog message for event 2417164298

Touchstone SW Upgrade Successful shows as DOCSIS and
not ARRIS.
Operational
Occurrence
High
34
2.3.82 CM does not handle TLV43 properly in the configuration

file
Tracking No.
PROD00163712
Description
Impact
Modem failed to handle TLV43 encode for ARRIS Vendor

Specific MIBs in the CM configuration file.
Operational
Occurrence
High
2.3.83 SIP: MTA does not ignore the hook flash if call is not
fully established
Tracking No.
PROD00162334
Description
Impact
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.
Service
Occurrence
Low
2.3.84 SIP: Line could be stuck in ringing state

Tracking No.
Impact
PROD00162331, PROD00161681, PROD00162112,

PROD00161630
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.
Service
Occurrence
Low
Description
2.3.85 CM State Webpage may incorrectly display DHCP

status
Tracking No.
PROD00162979
Description
Impact
CM State tab on the modem WebGUI may incorrectly display

DHCP status as Completed even when DHCP is still in
progress.
Operational
Occurrence
High
35
2.3.86 SIP: sipCfgDialFeat and sipCfgDialProxy table issues

Tracking No.
PROD00162282, PROD00162283, PROD00164701
Description
Impact
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.
Service
Occurrence
High
2.3.87 SIP: Telephony line LED stays off

Tracking No.
PROD00164373, PROD00164106
Description
Impact
Telephony line LED stays off if line was once registered then
failed to register, then was finally able to re-register again.
Operational
Occurrence
High
2.3.88 SIP: Message Waiting Indicator not accepted via SNMP

Tracking No.
PROD00160468, PROD00153594
Description
Impact
When the MWI was set via SNMP, the correct settings were not
stored in NVRAM.
Operational
Occurrence
High
2.3.89 Enrollment Inform Trap Message incorrectly set

Tracking No.
PROD00163774
Description
Impact
The MtaDevProvisioningEnrollment Inform Trap message is

being sent out incorrectly when the provisioning mode is
PacketCable.
Operational
Occurrence
Low
2.3.90 Voice calls may fail during high-speed downstream

traffic
Tracking No.
PROD00162840
36
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
Tracking No.
See Below
Description
Impact
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.
Service
Occurrence
Low
2.3.92 arrisMtaDevCallStatsHookStatus not valid when

accessed from CM IP
Tracking No.
PROD00162284
Description
Impact
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.
Operational
Occurrence
High
37
2.3.93 PacketCable Option 177 Configuration and Display

Issues
Tracking No.
See Below
Description
The following issues all relate to PC Option 177 provisioning:
Impact
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.
Service
Occurrence
Low
2.3.94 SIP: EURO Prefix Missing on SysDescr

Tracking No.
PROD00162923
Description
The SysDescr is missing the EURO designation.
Impact
Operational
Occurrence
High
2.3.95 DCID may be Reported Incorrectly after DCC

Tracking No.
PROD00159247
Description
Impact
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.
Operational
Occurrence
Low
38
2.3.96 Firmware Upgrade Failure Event Missing for CVC Error

Tracking No.
PROD00158437
Description
Impact
A CVC Fail event was not being sent when a firmware upgrade
failed because of a bad or missing CVC.
Operational
Occurrence
High
2.3.97 SIP: CallerID Display Issue with PAID Header

Tracking No.
PROD00162557, PROD00162245
Description
Impact
When the incoming SIP invite contains quotes in the PAID

Header, the quotes will be presented to the phone
Operational
Occurrence
High
2.3.98 Voice Quality Metric Issues

Tracking No.
See Below
Description
The following issues are all related to the ARRIS VQM feature.
Impact
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.
Operational
Occurrence
High
39
2.3.99 Battery Telemetry Log Events had incorrect Priority

Level
Tracking No.
PROD00161993
Description
Impact
The battery telemetry log events had a priority level of

informational instead of minor.
Operational
Occurrence
Low
2.3.100
North America Tone Template Issue
Tracking No.
PROD00162361
Description
Impact
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.
Service
Occurrence
Low
2.3.101
E-MTA in PSM may drop calls after 30 minutes
Tracking No.
PROD00157536
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
Tracking No.
PROD00158198
Description
LAN interface does not recover after loopback cable has been
disconnected.
Impact
Service
Occurrence
Reset the unit
40
2.3.103
MU Security Failures
Tracking No.
See Below
Description
Impact
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
Service
Occurrence
Low
2.3.104
Incorrect Australian Ring Cadence
Tracking No.
PROD00162285
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
Tracking No.
PROD00161377
Description
Impact
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.
Service
Occurrence
High
41
2.3.106
SIP: sipCfgDoc30FeatureSwitch MIB Walk Issue
Tracking No.
PROD00161880
Description
Impact
MTA MIB Walk on sipCfgDoc30FeatureSwitch returns wrong

type error.
Operational
Occurrence
High
2.3.107
Registration failures after DCC with S-CDMA
bonded upstreams
Tracking No.
PROD00161923, PROD00161103
Description
Impact
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.
Service
Occurrence
High
2.3.108
SSH Timeout Failure
Tracking No.
PROD00152346
Description
Impact
Occasionally during an automated testing run, a timeout will

occur when logging into the modem via SSH. Subsequent
attempt work fine.
Operational
Occurrence
Low
2.3.109
Extreme robustness testing issue
Tracking No.
PROD00159534
Description
During extreme RF tests, some calls may fail with no dial tone.
Impact
This issue has been resolved as it can no longer be reproduced.

Service
Occurrence
Rare
42
2.3.110
Configure Model 8 units for Maximum battery HUT
Tracking No.
PROD00163111
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
Tracking No.
PROD00159533, PROD00162131
Description
Impact
After recovery from server RF impairment conditions, the

modem may become unpingable and require a modem reset to
recover.
Service
Occurrence
High
2.3.112
arrisMtaDevDhcpMtaIpAddr returns 0.0.0.0
Tracking No.
PROD00161146
Description
Impact
MIB walk of arrisMtaDevDhcpMtaIpAddr.0 returns 0.0.0.0

instead of actual MTA IP address.
Operational
Occurrence
High
43
2.3.113
SIP: Invalid REGISTER messages may cause
MTA loss of Communications
Tracking No.
PROD00161727, PROD00161597
Description
Impact
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.
Service
Occurrence
Low
2.3.114
DCC DS/US move may fail in 1x1 Configuration
Tracking No.
PROD00161323
Description
Impact
CM may reject DCC messages when CMTS sets the Multiple

Receive Channel (MRC) TLV to a non-zero value on 1x1
configurations.
Service
Occurrence
Low
2.3.115
arrisMtaDevProvMethodIndicator issue with
BASIC.2
Tracking No.
PROD00159274
Description
Impact
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.
Service
Occurrence
High
44
2.3.116
arrisCmDoc30SwServerAddress implemented
incorrectly
Tracking No.
PROD00156028
Description
Impact
arrisCmDoc30SwServerAddress MIB walk would return the

value in ASCII format instead of octet string which is required
for InetAddress.
Operational
Occurrence
High
2.3.117
Active call may drop due to remote call metrics
data
Tracking No.
PROD00160768
Description
Impact
Active call may drop if there is a party on hold during 3WC or

Call-Waiting. This may occur on certain call-managementservers when Remote Voice Metrics are enabled and any end of
call stats value contains a + or > symbol.
Service
Occurrence
Medium
2.3.118
SIP: MTA Provisioning fails with no Option 122
subOption 3
Tracking No.
PROD00160518
Description
Impact
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.
Service
Occurrence
High
45
2.3.119
SIP: E-MTA may lose Registration with the Proxy
Tracking No.
PROD00158563
Description
Impact
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.
Service
Occurrence
Rare
2.3.120
LAN Fails to Power Up following MIB walk during
AC Power Failure
Tracking No.
PROD00160444
Description
Impact
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.
Service
Occurrence
Low
2.3.121
Power Save Management not fully implemented
Tracking No.
PROD00160590, PROD00160156
Description
Impact
Power Save Management feature to maximize battery hold-up

time for TM802 Telephony Modems may not fully meet the
specified battery hold-up times.
Operational
Occurrence
Low
46
2.3.122
SIP: MU Security Failures
Tracking No.
PROD00156897
Description
Impact
Security testing with the MU Analytics security suites

indicates errors in handling certain corruptions and attacks on
the SIP, HTTP and SSH ports.
Service
Occurrence
High
2.3.123
Unable to set ARRIS Custom MIBs
Tracking No.
PROD00156818
Description
Impact
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.
Operational
Occurrence
High
2.3.124
Extreme robustness testing issue(s) under
investigation
Tracking No.
See Below
Description
Impact
Service
Occurrence
Rare
2.3.125
PROD00158378: An RF cut during modem registration

may cause the CPE device to temporarily stop receiving
data packets.
DCC failure on multiple techniques
Tracking No.
See Below
Description
Impact
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.
Service
47
Occurrence
High
2.3.126
Call Progress Tone may not default to correct
value
Tracking No.
PROD00160150
Description
Impact
Call progress tone were not correctly set to the default values
for
the
country
that
is
provisioned
in
ppCfgMtaCountryTemplate.
Service
Occurrence
High
2.3.127
DTMF event ascending not working
Tracking No.
PROD00159053
Description
Impact
DTMF Event Ascending failed to work on DOCSIS3.0 releases.

arrisMtaDevDTMFEndEventForceAscending MIB object has
now been added to TS7.3 releases.
Operational
Occurrence
Low
2.3.128
CLI tapi command not accessible
Tracking No.
PROD00159220
Description
Impact
CLI tapi command to access TLM information was not

accessible via the Password of the Day.
Operational
Occurrence
High
48
2.3.129
LVM: WebGUI displays incorrect maintenance
timer value
Tracking No.
PROD00159459
Description
Impact
LVM Maintenance Timer under the Advanced product details

Web page always show 0 minutes.
Operational
Occurrence
High
2.3.130
SECURE provisioning failures due to incorrect
MAC calculation
Tracking No.
PROD00153044
Description
Impact
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.
Service
Occurrence
High
2.3.131
TFTP download retry mechanism Issue
Tracking No.
PROD00159711
Description
Impact
During an upgrade TFTP process, eMTA could result in

sending endless TFTP read requests if a download fails.
Service
Occurrence
Low
2.3.132
Opened ports detected during NMAP port scan
Tracking No.
PROD00158381
Description
Impact
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.
Service
Occurrence
High
49
2.3.133
CM-STATUS Inter operability issues with options
Tracking No.
PROD00158849
Description
Impact
During QAM/FEC Recovery events, CM-STATUS messages

were including downstream information for all previously
recovered downstreams.
Service
Occurrence
High
2.3.134
E-MTA with extended registration times
Tracking No.
PROD00158247
Description
Impact
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.
Service
Occurrence
Rare
2.3.135
arrisCmDoc30DhcpCmIpAddr implemented
incorrectly
Tracking No.
PROD00158990
Description
Impact
arrisCmDoc30DhcpCmIpAddr MIB walk would return the

value in ASCII format instead of octet string which is required
for InetAddress.
Operational
Occurrence
High
2.3.136
Line Card state MIB returns IDLE for
unprovisioned lines
Tracking No.
PROD00156124
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.
50
Impact
Operational
Occurrence
Low
2.3.137
LAN port may not power up after AC Power is
restored
Tracking No.
PROD00158746
Description
Impact
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.
Service
Occurrence
High
2.3.138
LVM: Policy 3 reset timer does not reinitialize to
the default value
Tracking No.
PROD00156834
Description
Impact
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.
Service
Occurrence
High
2.3.139
T.38: E-MTA Reset due to WATCHDOG
Tracking No.
PROD00158407
Description
Impact
E-MTA may reset with reset reason of WATCHDOG on

certain inbound T.38 Fax calls.
Service
Occurrence
Low
51
2.3.140
LVM: Policy 3 Loop Voltage Removal
Tracking No.
PROD00159454
Description
Impact
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.
Service
Occurrence
High
2.3.141
OOR Condition due to CPE Clearing
Tracking No.
PROD00152547
Description
Impact
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.
Service
Occurrence
High
2.3.142
Call Drops after 200 Seconds
Tracking No.
PROD00158454, PROD00152234
Description
Impact
Due to E-MTA sending incorrect DSC-REQ message, an active

call was being dropped after 200 seconds.
Service
Occurrence
Low
2.3.143
SIP: T.38 Call Failure
Tracking No.
PROD00159092, PROD00158307
Description
Impact
When placing a call using T.38, the first call failed due to EMTA incorrectly using the wrong active call-leg.
Service
Occurrence
Low
52
2.3.144
resetMTA does not clear line gain control settings
Tracking No.
PROD00159012
Description
Impact
The arrisMtaDevEndPnt MIBs are not set back to the default

value (or persistent NVM value) upon an MTA reset.
Operational
Occurrence
High
2.3.145
E-MTA uses Test Root certificate by Default
Tracking No.
PROD00157826, PROD00156134
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.
Impact
This issue is documented in AFB-10-0306.

Service
Occurrence
Low
2.3.146
Issue bonding against higher frequencies on a
CMTS
Tracking No.
PROD00157427
Description
Impact
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.
Service
Occurrence
High
53
2.3.147
Issue upgrading using a co-signed image
Tracking No.
PROD00157607
Description
Impact
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.
Operational
Occurrence
High
2.3.148
TM802 only registers in 1x1 mode
Tracking No.
PROD00155825
Description
Impact
Certain CMTSs may not properly handle RCPs in the REGREQ. By adjusting the order of the RCPs, the parsing
algorithm on the CMTS works correctly and modem can
registered in a bonded mode.
Service
Occurrence
High
2.3.149
Provisioning fails due to Illegal TLV11 in
configuration file.
Tracking No.
PROD00156003
Description
Impact
The firmware has been updated so that if ARRIS MIB Objects

in the configuration file missing the index value, provisioning
will still successfully complete.
Service
Occurrence
Low
54
2.3.150
Power Save Mode may cause E-MTA reboot
Tracking No.
PROD00158121
Description
Impact
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.
Service
Occurrence
Low
2.3.151
SDP Payload may cause Bandwidth Error
Tracking No.
PROD00158329
Description
Impact
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.
Service
Occurrence
High
2.3.152
LVM: Policy 3 loop voltage removal
Tracking No.
PROD00156912
Description
Impact
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.
Service
Occurrence
High
55
2.3.153
Classifiers are not deleted
Tracking No.
PROD00158727, PROD00159954
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.
Impact
This issue is documented in AFB-10-307.

Service
Occurrence
Low
2.3.154
Alarm Panel failure due to network delay
Tracking No.
PROD00158972, PROD00159105
Description
Impact
Alarm panels may fail to download the configuration file if the

network delay is excessive.
Service
Occurrence
Rare
2.3.155
Battery charging issue
Tracking No.
PROD00159076, PROD00158751
Description
Impact
A new release of the battery charger firmware is available in

this release to resolve issues noted with the battery charge time.
Operational
Occurrence
High
56
2.3.156
Voice call with data traffic may cause issues
Tracking No.
See Below
Description
The following issues have been identified in the lab when voice
traffic and high utilization data traffic are running
simultaneously:
Impact
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.
Service
Occurrence
Low
2.3.157
Time between off-hook and voice path too great
Tracking No.
PROD00159085
Description
Impact
The post-pickup-delay (PPD) is defined as the time between

off-hook answer and voicepath established. This time was
greater than baseline.
Service
Occurrence
Low
2.3.158
upsEstimatedMinutesRemaining does not report
the correct time
Tracking No.
PROD00159087
Description
Impact
The SNMP MIB Object, upsEstimatedMinutesRemaining, does

not report the correct amount of time remaining in the battery
once AC power is disconnected.
Operational
Occurrence
High
57
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
Methods
May
Reset
with
guiEncrypted
Provisioning
Tracking No.
PROD00171845
Description
Impact
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.
Service
Occurrence
Low
Workaround
None
3.1.2 Event 2417164297 may not be logged during upgrade

Tracking No.
PROD00163833
Description
Impact
When using SNMP to set MIB arrisCmDoc30SwFilename to a

file that is not present on the TFTP server, event 2417164297 is
not logged.
Operational
Occurrence
High
Workaround
None
58

Tracking No.
See Below
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
59
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
60
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
arrisMtaDevLineCardState
not
provisioned
show
0(OOS)
rather
than
IDLE
for
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
61
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_0I09-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.1
arrisCmDoc30MibObjects
CM SNMP Access
In the TS7.3 release, all CM SNMP functionality is disabled by default once the modem
is ranged & registers per revisions in the DOCSIS 3.0 specificiation that tighten the CMs
default SNMP security settings. In order to enable SNMP access to the CM, the
docsDevNMAccess MIB Objects must be included in the CM configuration file.
Here is one example of how this can be accomplished:
SnmpMib
SnmpMib
SnmpMib
SnmpMib
SnmpMib
SnmpMib
=
=
=
=
=
=
docsDevNmAccessCommunity.1 "public"
docsDevNmAccessControl.1 read
docsDevNmAccessInterfaces.1 hexstr: 40
docsDevNmAccessStatus.1 createAndGo
docsDevNmAccessCommunity.2 "private"
docsDevNmAccessControl.2 readWrite
62
SnmpMib = docsDevNmAccessInterfaces.2 hexstr: 40

SnmpMib = docsDevNmAccessStatus.2 createAndGo
LAN / CPEside SNMP access (read-only) for certain MIBs is supported before the
modem is ranged and registered in the same manner as in DOCSIS 2.0 mode.
MTA SNMP Access

Default SNMP security settings and functionality on the MTA side is based upon the
selected MTA provisioning method. For PacketCable 1.5 methods, then SNMP access to
the MTA will be disabled by default until the addition of the proper Community Table
settings in the MTA configuration file per the following example:
{SnmpMib snmpCommunityName.'mtaprov' mso_comm_string}
{SnmpMib snmpCommunitySecurityName.'mtaprov' @mtaprov}
{SnmpMib snmpCommunityStatus.'mtaprov' createAndGo}
NOTE: In terms of configuring SNMP Community Strings, for TS7.3 the

snmpCommunityStatus MIB should be set to createAndGo, instead of the value
Active which was used for SNMP Coexistence in the ARRIS DOCSIS 2.0 releases (ie:
TS6.1)
CallP Feature Switch Modifications

The TS7.3 release has modified the values for the CallP Feature Switch to remove
deprecated feature switches as well as to group common elements together. Please note
that the Provisional Response bit 0x00008000, Lockstep Quarantine Mode bit
0x00000002, and Piggybacked Transmissions of NCS Messages bit 0x00000001 are
opposite behavior from the DOCSIS 2.0 releases.
0x20000000: Allow MTA to automatically generate OSI: DISABLED
0x10000000: Delay DLCX response against connection on onhook only line (for VMWI): DISABLED
0x08000000: Use alternate (non sequential) Caller ID delivery order: DISABLED
0x01000000: Send dtmf digits via RFC2833 with payload 101 without request: DISABLED
0x00800000: Add brackets to IP for MTA FQDN when communicating with call server: DISABLED
0x00400000: Allow NCS Redirect without IPsec: DISABLED
0x00100000: Disable RTP/RTCP authentication/encryption (bit = 0): ENABLED
0x00080000: LUCENT RFC-2833 messaging without request using payload 94: DISABLED
0x00010000: Payload Header Suppression: DISABLED
0x00008000: Disable endpoint from sending provisional responses: DISABLED
0x00004000: DSX (access only) DQoS: DISABLED
0x00001000: NUERA RFC-2833 messaging without request using payload 127: DISABLED
0x00000800: Force the use of DQoS. Reject service if not used: DISABLED
0x00000400: Ignore format-specific SDP attribute lines referring to payload types not listed in media
description (m= line): DISABLED
0x00000100: Omit capability parameters in returned SDP: DISABLED
0x00000080: Omit mptime parameter in returned SDP: DISABLED
0x00000040: Apply auto OSI to both originating and terminating side for NCS calls: DISABLED
0x00000008: Reduce the capability descriptor in the SDP to T38 only: DISABLED
63
0x00000004: If line is not provisioned show 0(OOS) rather than IDLE for arrisMtaDevLineCardState.:
DISABLED
0x00000002: Prevent endpoint from entering the Lockstep quarantine mode: DISABLED
0x00000001: Prevent piggybacked transmissions of NCS messages: DISABLED
The default value for this feature switch is: 0x0.
CLI Command Changes

The TS7.3 release introduced a new CLI structure for troubleshooting E-MTA from
previous Touchstone Telephony firmware releases. The user documentation details the
new CLI and the commands currently available. To obtain access to the MTA section of
the CLI, the user must type voice to redirect to that sub menu. To exit this level, the
user needs to type quit to get back to the main ARRIS menu level for troubleshooting.
64
4 Customer Service and Support

For Technical Support, please visit the ARRIS Technical Support web page at
http://ask.arrisi.com.
Other methods for contacting the support organization are listed below.
North America
Email
Telephone
techsupport.na@arrisi.com
(888) 221 9797 (US toll free)
+1 678 473 5656 (Worldwide)
Office Hours
8:00 a.m. to 8:00 p.m. EST
South America Chile
Email
techsupport.cala@arrisi.com
Telephone
+56 2 678 4500
Office Hours
9:00 a.m. to 6:00 p.m. (Chile local time).
Europe Amsterdam, The Netherlands
Email
techsupport.europe@arrisi.com
Telephone
+31 20 311 2525
Office Hours
8:30 a.m. to 17:30 p.m. CET
Japan Tokyo
Email
techsupport.japan@arrisi.com
Telephone
+81 (0) 3 5371 4142
Office Hours
9:30 a.m. to 6:00 p.m. (Tokyo local time)
Asia
Email
techsupport.asia@arrisi.com
Telephone
+82 31 783 4893
Office Hours
9:30 a.m. to 6:00 p.m. (local time)
Korea
Email
techsupport.asia@arrisi.com
Telephone
+82 31 783 4893
Office Hours
9:30 a.m. to 6:00 p.m. (local time)
Worldwide North America
Email
techsupport@arrisi.com
Telephone
USA +1 678 473 5656
Emergency support is available after normal business hours for customers with
a support contract ID via the listed contact information.
65
Appendix A: Compliance Matrix

DOCSIS 3.0
SP-SECv3.0
SP-CMCIv3.0
SP-PHYv3.0
SP-MULPIv3.0
SP-OSSIv3.0
PacketCable 1.5
PKT-SP-DQOS
PKT-SP-CODEC
PKT-SP-NCS
PKT-SP-MIBS
PKT-SP-MIB-SIG
PKT-SP-PROV
PKT-SP-SEC
CW76 ECNs
I12
I01
I08
I12
I11
CW76 ECNs
I04
I03
I03
I03
I01
I04
I03
Documentation Links:
http://www.cablemodem.com/specifications/specifications30.html
http://www.packetcable.com/specifications/specifications15.html
66
Touchstone
Telephony Firmware
Release 7.3.139
Release Notes and
Letter of Operational
Consideration
Copyright @2012 ARRIS Group, Inc.

All rights reserved
The information disclosed herein is
proprietary to ARRIS Group, Inc and is not to
be used by or disclosed to unauthorized
persons without written consent of ARRIS
Group, Inc. The recipient of this document
shall respect the security status of the
information.
Version: 1.0
Status: Approved
67

TS 7.3.139-Rnloc Docsis (1.0)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TS 7.3.139-Rnloc Docsis (1.0)

Hochgeladen von

Copyright:

Verfügbare Formate

Touchstone

Touchstone Telephony Firmware

2012 ARRIS Group, Inc.

OBJECTIVES OF THIS DOCUMENT _____________________________ 1

DOCSIS NEW PRODUCT FEATURES _________________________________ 5

LETTER OF OPERATIONAL CONSIDERATIONS _________________ 58

RELEASE NOTES ___________________________________________ 5

ARRIS COMMITMENT ____________________________________________

DOCSIS OPERATIONAL CONSIDERATIONS ___________________________ 58

CUSTOMER SERVICE AND SUPPORT__________________________ 65

APPENDIX A: COMPLIANCE MATRIX _____________________________ 66

Touchstone Telephony Firmware - Release 7.3.139

1 Objectives of This Document

1.2 Purpose and Scope of This Document

1.3 Product Identification and Purpose of Release

Maintenance Supplemental Release (MSUP)

Network-Based Call Signaling (NCS)

Release Notes & Letter of Operational Consideration

Touchstone Telephony Firmware - Release 7.3.139

1.4 Firmware Filename Variant Information

Supports the TG852 hardware platform

Supports the TG862 hardware platform

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

Supports WBM760 & CM820 hardware platforms

Monolithic image containing both eRouter and DOCSIS images

Used to validate upgrades and downgrades

Session Initiation Protocol (SIP) firmware image

1.5 Minimum Firmware Baseline for Hardware

TS070198_071510 (TS 7.1.98)

TS070198_071510 (TS 7.1.98)

TS070198_071510 (TS 7.1.98)

TS070198_071510 (TS 7.1.98)

Release Notes & Letter of Operational Consideration

Touchstone Telephony Firmware - Release 7.3.139

TS070397_042811 (TS 7.3.97)

TS070346_081910 (TS 7.3.46)

TS070397_042811 (TS 7.3.97)

TS070397_042811 (TS 7.3.97)

TS070373_121610 (TS 7.3.73)

Release Notes & Letter of Operational Consideration

Touchstone Telephony Firmware - Release 7.3.139

1.6 Product Documentation

Release Notes & Letter of Operational Consideration

Touchstone Telephony Firmware - Release 7.3.139

DOCSIS New Product Features

Argentina Call Tones

SIP GUPI TFTP Override Provisioning Method

Loop Diags Low REN Warning

Support to Ignore Missing Payload Types

Release Notes & Letter of Operational Consideration

Touchstone Telephony Firmware - Release 7.3.139

No new features were added to this release.

Internal SpeedTest Application

Reset Ethernet Connectivity after Loss of DS

Business Services over DOCSIS (BSoD)

Ability to handle non-standard T38 in SDP

Reset Ethernet Connectivity after Loss of DS

Release Notes & Letter of Operational Consideration

Touchstone Telephony Firmware - Release 7.3.139

ResetMTA CLI command

Source IP in Reset Logs

Software Download Filename Check Override Feature

Hardware Power ON Reset Logging