TS 7.1.98-Rnloc - 1.0

Touchstone
Telephony Firmware
Release 7.1.98
Release Notes and
Letter of Operational
Considerations
Touchstone Telephony Firmware

Release 7.1.98
Release Notes and
Letter of Operational Considerations
Document release
Document date
Release 1.0
July 21, 2010
2010 ARRIS
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.
ARRIS, ARRIS International, and Voice Port are trademarks of ARRIS Licensing Company. Cornerstone is a
registered trademark of ARRIS Licensing Company.
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
July 15, 2010
July 20, 2010
July 21, 2010
Initial Draft, v0.1

Added LOC Section, v0.2
Approver Comments Added, v1.0
Table of Contents
1
OBJECTIVES OF THIS DOCUMENT _____________________________ 1

1.1
1.2
1.3
1.4
1.5
1.6
NEW PRODUCT FEATURES _________________________________________ 4

RESOLVED FIELD BULLETIN(S) ____________________________________ 16
RESOLVED PRODUCT DEFICIENCIES _________________________________ 17
LETTER OF OPERATIONAL CONSIDERATIONS __________________ 73

3.1
3.2
3.3
1
1
1
2
2
3
RELEASE NOTES ____________________________________________ 4

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 _______________________________________
OPERATIONAL CONSIDERATIONS ___________________________________ 73

UNSUPPORTED FEATURES ________________________________________ 83
UPGRADE CONSIDERATIONS ______________________________________ 83
CUSTOMER SERVICE AND SUPPORT __________________________ 88
APPENDIX A: COMPLIANCE MATRIX ______________________________ 89
Touchstone Telephony Firmware - Release 7.1.98
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
Maintenance Supplemental Upgrade (MSUP) 6 - TS 7.1.98
Validation Sequence
Maintenance Supplemental Upgrade (MSUP) 6
Supported DOCSIS
Standard(s)
DOCSIS
3.0
Euro-DOCSIS
3.0
Supported Signaling
Protocol(s)
Network-Based Call Signaling (NCS)

Session Initiation Protocol (SIP)
Supported PacketCable
Standards
PacketCable
1.5
Euro-PacketCable
1.5
Firmware Filename
SysDescriptor
PacketACE
TS070198_071510
SW_REV: 7.1.98
DOCSIS 3.0 PacketACE Release 2.9 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
PURPOSE OF EXTENSION
_NA
North America signed firmware image
_EU
European signed firmware image
MODEL_7
WBM_7
SIP
MAC14
Supports TM7XX models (TM702, TM722)

Supports WBM7XX models (WBM750, WBM760)
Session Initiation Protocol (SIP) firmware image
Used to validate upgrades/downgrades
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
TM702A/B/G
TS070054_101008 (TS7.0.54)
TM722A/B/G
TS070144_050709 (TS7.1.44)
WBM750A/B
WBM030112_101408 (WBM 3.1.12)
WBM750C
WBM030214_032609 (WBM 3.2.14)
WBM760A/B
WBM030214_032609 (WBM 3.2.14)
WBM760C
WBM030214_032609 (WBM 3.2.14)
1.6 Product Documentation

Other relevant information is included in the following documentation:
Product
Touchstone Telephony Guide (TS7.1)
2 Release Notes
The Release Notes describe the New Product Features introduced in the Touchstone
Firmware for the ARRIS Touchstone Telephony Modem(s) and the Touchstone
Telephony Port(s). Included in the Resolved Product Deficiencies section is a list of
resolved operational considerations noted in previous releases.
2.1
New Product Features
Added in TS 7.1.98
Out of Range (OOR) Threshold Change

This release of firmware supports the ability to enable a reduced combination of Out of
Range (OOR) packets 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.
Automatic OSI Feature Switch Update

This release of firmware adds the ability via SNMP to set the automatic OSI to the
behavior previously observed in TS 6.1.60 and prior loads where the OSI was applied to
both originating and terminating calls. This feature is enabled using the
ppCfgMtaCallpFeatureSwitch setting of 0x20000040.
Added in TS 7.1.95
No new features were added in this release.
Added in TS 7.1.94
Added in TS 7.1.92
CallerID Suppression
This release supports the ability to disable portions of the callerID display. Three new
MIB objects have been added to support this new functionality. The MIB objects are
detailed below:
arrisMtaDevEndPntCIDEnable: Determines whether the callerID will be
presented to the phone.
arrisMtaDevEndPntCIDNameEnable: Determines if the individual name will be
made available in the callerID information sent to phone.
arrisMtaDevEndPntCIDDateTimeEnable: Determine if the date/time fields will
be made available in the callerID information sent to phone.
Loop Reversal Control

This release supports the ability to help manage loop reversal interactions for NCS Call
Servers. This feature will revert phones back from loop reversal at the end of a call for
call servers that do not support that signaling. The MIB object,
arrisMtaDevEndPntLoopReversal sets up this management.
Call Waiting Repeat Indefinitely

This firmware release supports the ability to have the call waiting tone continuously
played while the phone is off-hook. This feature can be enabled by using the MIB object
arrisMtaDevEndPntCallWaitingRepeatSteady.
Added in TS 7.1.89
WBM Load Support

This release of firmware synchronizes the TS7.1 and WBM3.2 firmware code streams
and load names for the TM702, TM722, WBM750, and WBM760 series of DOCSIS 3.0
wideband modems. The TS7.1.89 firmware combines the TS7.1 and WBM3.2 load
naming convention by merging the WBM3.2 release into the TS7.1 release. Beginning
with this release, in lieu of releasing both a WBM3.2.x load and a TS7.1.x load, ARRIS
will release only a single TS7.1.x load with different extensions, for example:
TS070189_012710_NA.MODEL_7.img
TS070189_012710_NA.WBM_7.img
(for the TM702/722)

(for the WBM750/760)
SIP: Early Transmission of RTP Media upon 180 Messages

Activation of this feature instructs the MTA to begin transmitting RTP packets upon
receipt of the 180 messages instead of the 200 OK messages. This facilitates the use of
NAT traversal and the playback of pre-dialing early media announcements. To enable
this functionality, youll need to add the sipCfgSipFeatureSwitch2 MIB to the
configuration file and set the 0x10000000 bit.
SIP: Provisioning Method GUPI MAC Supported

A new provisioning method, gupiMacMta, is now available for SIP loads. This
provisioning method can only be selected from the arrisMtaDevProvMethodIndicator.
When this provisioning method is selected, the MTA will ignore the MTA configuration
file name in the DHCP ACK message. In place of the specified configuration filename
the MTA will request a TFTP transfer of a filename using the MTA MAC address with a
bin extension. An example of the requested filename is below:
0000CA123456.bin
Advanced Web Page Login Access Control

This feature provides the ability for the MSO to configure different access levels to the
Advanced webpage based upon whether they are connecting to the WebGUI via the
WAN or LAN/CPE interface. Using the new MIB object
arrisCmDoc30SetupAdvancedWebPageAccess, the levels can be configured as NONE,
LAN only, WAN only, or both. Without this MIB in the configuration file access to the
Advanced web page login prompt is available via the WAN and LAN ports. When
access is disabled, users clicking upon the Advanced tab on the WebGUI will receive an
authorization error.
Added in TS 7.1.81
MIB Object to Invert Current LED Behavior

A new feature has been added to allow the operator the ability to invert the standard DS,
US, and Link dual-color LED behavior on the TM722 model. In the default
configuration, a Green LED represents a device operating in bonded mode with the
CMTS or indicates that a CPE device with 1000-baseT Ethernet or USB 2.0 capabilities
has been connected. Using the MIB Object, arrisCmDoc30SetupInvertMulticolorLED,
the color Amber will now represent a DS or US channel is bonded. This setting is stored
in NVRAM and is persistent across reboots.
Persistent Line Status Feature

A new MIB Object, arrisMtaDevPersistentLineStatus, has been added to the release to
support a persistent line status feature. This feature allows a customer to set a line
permanently down (forceDisable(1)) and for that setting to remain over resets. This MIB
can only be set after registration and by the use of SNMP. To restore a line to service,
the MIB must be set to ignore (Ignore(0)) or reset the unit back to factory defaults.
Endpoint Dialing Method Persistent Feature

Included in this release of firmware is the ability for the operator to store SNMP-initiated
changes of the arrisMtaDevEndPntDialingMethod in NVRAM over reboots and restarts
of the EMTA. Once the unit has ranged and registered, any changes to this MIB via
SNMP will be stored persistently in NVRAM. Should the MIB be included in the
configuration file, then the stored non-volatile value will be overridden until they are
removed from the configuration file at which time the stored values will be used. To
clear this setting from non-volatile memory, change the value again via SNMP, or reset
the unit back to factory defaults.
Transmit and Receive Gain Control Setting per Line

Included in this release of firmware is the ability for the operator to store SNMP-initiated
changes to the transmit (TX) and receive (RX) gain settings on a per line basis in
NVRAM that is persistent over reboots and restarts of the EMTA. Once the modem has
ranged and registered, then any updates to the arrisMtaDevEndPntGainControlTxVoice
and arrisMtaDevEndPntGainControlRxVoice will be stored in non-volatile memory.
Should the MIBs be included in the configuration file, then the stored non-volatile value
will be overridden until they are removed from the configuration file at which time the
stored values will be used. To clear this setting from non-volatile memory, change the
value again via SNMP, or reset the unit back to factory defaults
MDD Override Functionality

This release of firmware includes the ability to override the specified IP mode (IPv4 or
IPv6) contained within the MDD message from the CMTS which tells the CM portion of
the MTA how to obtain a CM IP address from the DHCP server using either IPv4 or
IPv6. This functionality is configured by using the new MIB object
arrisCmDoc30SetupMddIpModeOverride to store the Override mode in non-volatile
memory which is stored over restarts and reboots to be used during CM initialization.
Extreme caution should be used when setting this MIB object as it has the ability to
keep the MTA from registering if a specific mode (such as IPv6 only) is selected, and
then the DHCPv6 server is not available. For this specific example, the modem will
continue to try and register as IPv6 only (ignoring IPv4) until the server is available. The
value of this setting can be viewed or queried via the CLI, SNMP, and on the DHCP
Parameters page of the Advanced WebGUI. To clear this setting from non-volatile
memory, change the value again via SNMP, or reset the unit back to factory defaults
North American PacketCable Support for Euro-DOCSIS units

In this release of firmware, the capability has been added for the MTA to support the
ability to provision the MTA using a North American based PacketCable provisioning
system and Euro-DOCSIS CM functionality. This feature which previously required a
separate firmware image is enabled via the arrisCmDoc30SetupPacketCableRegion MIB
object.
Ability to Suppress FQDN and IP Address in Event Logs

New functionality has been added to allow the MSO to suppress the printing of FQDN
and IP address information in the event log when viewed via the WebGUI interface. This
feature is controlled by the MIB arrisMtaDevEventHideFQDNandIPAddress.
CODECs Supported
This release of firmware supports the following compression CODECs:
G.711 (ARRIS Recommended CODEC)
G.728
G.729
G.729E
G.726-16
G.726-24
G.726-32
G.726-40
RTCP TOS Byte Marking Configuration

In this release, to configure the RTCP TOS byte an MSO can modify the
arrisMtaDevRtcpTosValue MIB Object. The default value for this MIB is 0. In prior
legacy releases, the default value use to be 64. If no value is specified for
arrisMtaDevRtcpTosValue in the configuration file, zero is the value that is used for all
RTCP packets. The IP TOS marking will change instantly for RTCP packets whenever
this MIB object value is changed. This works differently than RTP packets, whereby the
TOS marking is updated only on the establishment of a call.
MTA Post Provisioning

ARRIS has implemented the PacketCable Post Provisioning functionality which allows
the operator to add or remove lines from service via SNMP without rebooting the MTA.
The feature can be controlled with the pktcMtaDevCmsTablepktcMtaDevRealmTable
and pktcNcsEndPntConfigTable MIB tables.
Partial Services Monitoring

A new feature has been added for reporting to the operator via SNMP the status of both
downstream and upstream channels for helping operators monitor partial service
scenarios. When queried, the arrisCmDoc30ProvisionedChannelIDs will display the
Downstream Channel IDs (DCIDs) and Upstream Channel IDs (UCIDs) for all the
provisioned streams. Streams noted in parenthesis () indicate that channels is currently
unavailable.
Reset to Factory Defaults

A new feature is supported in this release to return the MTA back to factory defaults, and
clear any settings currently stored in NVRAM. The feature is activated by the
arrisCmDoc30ResetFactoryDefaults MIB object.
Time Offset Adjustment

Time of Day (TOD) changes within a network cause operator issues with features such as
CLIP information in SIP. The changes are handled through the DHCP timing offset but
these changes only take affect when the devices goes through a DHCP renew. This
release implements an SNMP MIB, arrisCmDoc30SetupTODTimeOffset, which allows

an operator to adjust the TOD using the CM IP Address. The DHCP timing offset
received at renewal will take precedence over this setting.
Fax Only Line

The new SNMP MIB Object, arrisMtaDevEndPntFaxOnlyLineTimeout, can be used to
set an NCS line for fax transmission only. The line will wait the amount of time
specified in this MIB to detect a fax tone before disconnecting the call.
PacketCable 1.5 Voice Quality Metrics

The PacketCable 1.5 Voice Quality Metric Support with a call agent is supported for
NCS in this release of firmware. SNMP MIBs have been added for controlling this
feature, as well as configuring reporting thresholds. Activating this feature greatly
increases the size of the report provided to the call agent by up to 350 characters. To
view the voice quality metrics, this release includes a Voice Quality Metrics page
accessible via the Advanced WebGUI page.
Last Call Voice Quality Metrics (VQM)

A new read-only MIB has been added to the existing MIB in the arrisMtaDevVqm MIB
tree to allow easier access to the VQM information for the last call. The new SNMP
MIB, arrisMtaDevVqmCallNumberIdentifierLastCall, will point the existing
arrisMtaDevVqmCallNumberIdentifer MIB to the appropriate last call information. The
user can now simply read the arrisMtaDevVqmMetricTable to obtain the VQM data.
Highest Temperature Recorded MIBs

This release supports the ability to display the highest temperature ever recorded along
with the date and time in which that occurred. These values are stored in NVRAM and
preserved over reboots. The new SNMP MIB Objects are listed below:
arrisMtaDevPwrSupplyHighestTemperature,
arrisMtaDevPwrSupplyHighestTemperatureTime
arrisMtaDevPwrSupplyHighestTemperatureReset
MTA DHCP Option 122 Enforcement

This release adds a new SNMP MIB object arrisMtaDevDhcpSubOpt3Immediate to
support the ability to configure the MTAs handling for DHCP Option 122 Sub-Option 3
values. When enabled, changes to the SNMP Entity values during a DHCP Renewal or
Rebind process will take effect immediately for directing LinkUp and LinkDown traps to
an alternative trap server instead of waiting for the next MTA reset. This functionality
facilitates the use of multiple redundant provisioning and DHCP servers by operators.
Ability to Disable TurboDOX

This release adds a new SNMP MIB object arrisCmDoc30SetupTurboDoxEnable to
allow TurboDOX to be disabled when placed in the CM configuration file. During
customer traffic testing and lab evaluations, this ability is sometimes needed to obtain
higher data throughput rates. For field deployments, ARRIS recommends this setting
remains the default value which is TurboDOX enabled.
Additional Battery Support

This release of firmware support the new 12 hour BPD066H (6600ah) and 16 hour
BPD088H (8800ah) battery packs in the TM722.
Enhancement to CM ifPhysAddr.16
This release adds support for returning the MTA MAC Address when queried via
ifPhysAddress MIB index 16 on the CM MIB tree. This functionality is needed to
support the automated discovery of MTA specific information by deployed customer
provisioning systems in the field.
SuperG3 Fax Downshift

This release adds support for the new SNMP MIB object, arrisMtaDevSuperG3FaxRelay.
This MIB will enable the capability to downshift (convert) a 33.6K baud pass-through fax
with no redundancy to T.38 Version 0 which transmits at 14.4K baud.
Added in TS 7.1.61A
Added in TS 7.1.61
Secure Shell (SSH) Access Events

This release expands event reporting of the existing SSH feature. As of TS 7.1.61, SSH
connection attempts will be logged to the local event log as well as to network syslog and
SNMP Trap server (if configured). The following login actions will be logged:
SSH LOGIN ACCEPTED
SSH LOGIN REJECTED
SSH LOGIN REJECTED - MAX ATTEMPTS REACHED
Partial Services Monitoring

This release has expanded monitoring for assigned Downstream and Upstream Channel
information. On the CM status Web GUI, content has been expanded to indicate whether
a particular Downstream channel has been provisioned and/or acquired. In addition, the
new arrisCmDoc30ProvisionedChannelIDs MIB has been added to arrisCmDoc30Base.
This MIB displays the Downstream Channel IDs (DCIDs) of all provisioned
Downstreams and the Upstream Channel IDs (UCIDs) of all provisioned Upstreams. The
MIB also provides indication of whether the channel is not locked (Channel ID
surrounded by parenthesis).
10
Multiple CVC Support with Enhanced Firmware Download

The existing Enhanced Firmware Download MIBs have been expanded to include MIBs
for the CVC. The MSO may choose to include the ARRIS manufacturer CVC. With this,
the ARRIS Enhanced Firmware Download MIB Table now includes fields for all
pertinent download data (Hardware model, Server IP, Load filename, CVC). The
presence of a CVC in this MIB will override the use of the standard DOCSIS TLV.
Enhanced Web Page with Downstream Characteristics

The Status Web GUI will now display additional information related to Downstream RF
channels including SNR/MER, as well as corrected and uncorrectable errors.
Dual-Color LED Setting Persist Over Resets

In prior releases, dual-color LED settings were cleared after a modem reset until the
configuration file was retrieved and re-enabled them. In this release, LED settings are
saved and will survive modem resets.
ARRIS Ultrafast Downstream Scanning

This release significantly reduces downstream scanning time by enhancing the ARRIS
proprietary scanning algorithm.
Dialing Method Persistence MIB

The Dialing Method Persistence MIB, arrisMtaDevEndPntDialingMethod, has been
added to allow the selection of the endpoint dialing method (tone, pulse, tone and pulse,
etc). Changes to this MIB initiated via SNMP will persist over reboots and restarts of the
E-MTA.
Loop Diagnostics Support

In this firmware release support for the Loop Diagnostics feature has been extended to
TM702 and TM722 models. The Loop Diagnostics feature can be accessed via SNMP,
WebGUI, and CLI.
Reject Firmware Download while Call in Progress or During AC

Fail
In this firmware release can now reject a firmware upgrade while a call is in progress or
during AC failure to minimize service impacts during upgrades.
Persist Command
In this firmware release supports the CLI command persist for logging persistence
where log settings will be maintained upon the telnet window being closed.
CallP/QoS Statistics Web GUI

In this firmware release the CallP/QoS Web GUI has been expanded to display which
service flows are actually carrying voice traffic. Also in prior releases, ARRIS Password
11
of the Day was required to access the CallP/QoS web page. In this release the web page
is now accessible without a password.
Voice Security
This firmware release supports for voice security functionality to handle encryption of
RTP voice packets.
Daylight Savings Time (DST) Feature

This Daylight Savings Time feature allows the user to configure a rule to define when
DST time changes are applied. This policy defines the start/end dates/times for the DST
for the given region. To enable this feature the MIB, arrisCmDevDSTPolicy, should be
used.
Clear CPE list Feature

In this firmware release the CPE list will be cleared when the E-MTA loses link on all
LAN interfaces. E-MTA will only remove dynamically detected CPEs and not eSAFE
devices or pre-provisioned CPEs.
Message Logging Features

In this firmware release introduces support for ARRIS DHCP, NCS and DSX message
logging functionality.
Added in TS 7.1.44A
Added in TS 7.1.44
Packet Processor for Small Packet Improvement

A new packet processor has been added in this release to improve throughput
performance for smaller packets. This feature is enabled by default but can be disabled
using the MIB Object, arrisCmDoc30SetupPacketProcessorEnable.
Secure Shell (SSH) Feature with Input Timeout Check

This release supports SSH login access to the WBM. This access can be obtained by
using the MIB object, arrisCmDoc30AccessSSHEnable. Once this feature is enabled an
SSH session can be created to the CM IP address port 22 or 192.168.100.1 port 22. The
user name will be root and the password is arris to authenticate the SSH session.
Once that is complete, the password of the day (PWOD) is used for CLI access.
SSH also supports the timeout feature for inactivity on the port. The MIB object,
arriscmDoc30CLITimout, can be used to setup a value in minutes of when the session
should automatically close after inactivity.
12
HTTP Password Protection Control

In order to allow additional flexibility by the operator around HTTP protection, a new
MIB object, arrisCmDoc30AccessHttpPwCtrl, has been added to this release. This MIB
provides the flexibility to determine which of the HTTP pages (none (0), advanced (1), or
basic(2)) are password protected. This MIB value is stored in NVRAM. For the WBM,
this value is defaulted to advanced(1) to protect the advanced web pages.
Enhanced Firmware Loading with Vendor CVC

This release supports the ARRIS feature for Enhanced Firmware Loading, and adds the
capability for the MSO to optionally include a vendor CVC in their confirmation file.
This allows the operator the ability to create a single multiple-vendor common CM
configuration file that can support the upgrade of multiple hardware models.
Primary Downstream Reinitialized after DS loss

If a secondary downstream channel in a bonding group is lost for more than 45 seconds
and the new MIB object arrisCmDoc30SetupSecDsLossReinitEnable has been set in the
configuration file, the E-MTA will reinitialize the primary downstream MAC upon loss
of a secondary downstream channel. Manual interaction will be required to get the
provisioned channels active once downstream channels have recovered. This feature is
intended for use with CMTS systems that do not yet support partial service.
For older D3.0 CMTS firmware versions that do not support a partial services
confirmation code in the REG-ACK message from the CM, a new MIB object
arrisCmDoc30SetupPartServiceFallback20 has been added that will force the CM to reinitialize the primary downstream DOCSIS MAC and register in DOCSIS 2.0 1x1 mode.
When enabled, this prevents the E-MTA from being placed in a reject(na) state when
attempting to register with a missing secondary downstream. Additionally, every 15
minutes the modem will attempt to return to the DOCSIS 3.0 primary bonded
downstream when operating in this mode.
Disabling Channel Bonding

The ARRIS MIB Object, arrisCmDoc30SetupDSBonding, has been added to this release
to disable channel bonding and force DOCSIS 2.0 behavior. The value set in this MIB
Object is stored in NVM so that it will persist across reboots. This behavior will take
effect at the next reboot after setting the MIB Object.
TM722 Hardware Support

The second generation of the TM702, TM722, is supported with this release of firmware.
This new hardware specifically offers additional troubleshooting capabilities with the
introduction of dual-color LED support.
USB Load Support Provided in Standard Load

In this release of firmware, the USB support has been provided in the standard firmware
load. A separate load with an .USB extension is no longer available or needed.
13
Extended Downstream Bandwidth Capture

The TM702/722 fully supports the DOCSIS 3.0 RCP-ID reporting mechanism to the
CMTS and can support up to a 96 MHz receiving window.
Real-Time Control Protocol-Extended Reports (RTCP-XR)

This release supports Voice Quality Metrics (VQM) and Real-Time Control ProtocolExtended Reports (RTCP-XR) packets for NCS signaling. Default operation defaults
RTCP-XR to off. This feature can be turned on by the call server, proxy server, far-end
MTA, or Master Switch setting on the near-end MTA. The Master Switch is accessible
via SNMP and CLI.
Signaling Trace Capability

Touchstone software can now report, through Syslog, a trace of all incoming and
outgoing
NCS
signaling
messages
on
the
MTA.
A
new
MIB,
arrisMtaDevEnableCallpSigTrace, has been created to control this tracing. In addition to
setting the tracing, the last MTA signaling message sent is saved and also available via a
MIB. This feature has the ability to cause a security breech and network congestion. For
additional detail, refer to the Touchstone Software Management Guide.
T.38 Fax Loose and Strict Modes Support for NCS and SIP
This release contains support for T.38 Fax Loose and Strict Modes on NCS and SIP
deployments. T.38 offers more robust digital transmission over an IP network for fax due
to built in redundancy and forward error correction.
European PacketCable Provisioning Specification Changes

The European PacketCable provisioning and call processing MIB Objects have been
upgraded for this release to include support for the following:
draft-ietf-ipcdn-pktc-signaling-09 (PKTC-IETF-SIG-MIB)
draft-ietf-ipcdn-pkct-mtamib-06 (PKTC-IETF-MTA-MIB)
A corresponding configuration file change needs to happen in conjunction with this
upgrade for the E-MTA to correctly function.
SuperG3 Fax Support

In this release, SuperG3 fax support for V.8 CM signaling is supported. A new MIB,
arrisMtaDevSuperG3FaxRelay, has been included in this release to allow the user to
decide how to setup the fax transmission. The default operation will setup the connection
over the G.711 CODEC instead of using T.38. In T.38 mode, SuperG3 is supported at
T.38v0 which is a 14.4 bps connection.
14
15
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-0303
MTA Initiated Call Progress Tones May Cease After 2 Cycles of

Cadence
PROD00153547,
PROD00153541
AFB-10-0301
ARRIS DOCSIS 3.0 Potential Registration Issue with US Channel

Bonding
ARRIS DOCSIS 3.0 Modems May Intermittently Fail to Register
in Bonded Mode
ARRIS DOCSIS 3.0 Potential Upgrade Issue
PROD00151896
AFB-09-0308
AFB-09-0312
PROD00146737
PROD00147348,
PROD00148288
16
2.3
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.
The following issues were resolved in release 7.1.98
2.3.1 NVM Flag Setting Issue on TS 7.1.97

Tracking No.
PROD00157626
Description
Impact
TS 7.1.97 was provided to some customers as an early

candidate build for this release. It was found that NVM Flag
setting in this load would result in upgrade/downgrade issue on
TS 7.3. That load has been removed internally at ARRIS and
should be replaced at all customer locations with the official
release, TS 7.1.98.
Service
Occurrence
High
2.3.2 Bulk Traffic Testing Original Failure

Tracking No.
PROD00154443
Description
Impact
While performing bulk call traffic testing, an issue was noted in

the ARRIS lab where concurrent calls would fail upon
origination. The investigation uncovered an issue where a call
table was becoming filled with stale entries. This resulted in a
failed call attempts on the origination until the table was full of
stale events.
Service
Occurrence
Low
2.3.3 LED Issue after Firmware Upgrade

Tracking No.
PROD00155506
Description
After upgrading the modem, it was noted if the upgrade failed

the LED was no longer correct. When the problem occurred,
the POWER and DS LEDs blinked while the other LEDs
remained off.
However, the modem was completely
17
operational during this time.
Impact
This issue was only observed in the ARRIS lab using an

unsigned image and causing an upgrade failure.
Operational
Occurrence
Low
2.3.4 Firmware Upgrade Failure not Logged in Event Logs

Tracking No.
PROD00155566
Description
Impact
An issue was identified where a firmware upgrade failure was

not noted in the event logs.
Operational
Occurrence
High
2.3.5 SW Version in DHCP Option 43 may not be Correctly

Reported
Tracking No.
PROD00155071
Description
Impact
The text in option 43 suboption 6 in the DHCP DISCOVER

(SW Version) is the same regardless of the firmware type load
(NCS or SIP). This text should change depending of the
signaling supported by the firmware.
Operational
Occurrence
High
2.3.6 IPv6: Bootfile not null-terminated

Tracking No.
PROD00152975
Description
Impact
When using IPv6, if the DHCP server did not null-terminate the
bootfile, random characters could be appended to the file name.
This would result in a TFTP failure as the bootfile name would
not match the filename on the TFTP server.
Operational
Occurrence
High
2.3.7 SDP Capability to Suppress T.38

Tracking No.
PROD00156330
18
Description
Impact
In some scenarios the capability of supporting T38 needs to be

suppressed in the outgoing SDP so that T38 is not negotiated.
Attempting to perform T38 in networks where it is not
supported can cause fax failures. The 0x100 callp feature bit in
the ppCfgCallpFeatureSwitch is now supported in TS 7.1
releases to limit the SDP capabilities.
Service
Occurrence
High
2.3.8 ILEC Ringing and Power Induction/Cross Testing may

Damage Line Card
Tracking No.
PROD00152070
Description
Impact
During corner case testing by the design, several areas for

improvement around line card protection against ILEC signals
was observed.
Issues noted with ringing and power
induction/cross testing were noted to potentially damage the
line card.
Service
Occurrence
High
2.3.9 SIP: Restrict Incoming CODEC Offer not Supported

Tracking No.
PROD00156250
Description
Impact
This release of firmware provides support for the feature, SIP

Restrict Incoming CODEC Offer. This feature allows the
operator to restrict the acceptance of CODECs in the incoming
INVITE
to
the
list
provisioned
in
the
sipCfgProvisionedCodecArray MIB.
Service
Occurrence
High
2.3.10 arrisCmDevResetReasonLog not Supported

Tracking No.
PROD00156023
Description
In prior releases of firmware, the SNMP MIB Object

arrisCmDevResetReasonLog was not supported. When polled,
this MIB would report a value of 0.
Operational
Impact
19
Occurrence
High
2.3.11 Packets Discarded as OOR after Unplugging CPE

Tracking No.
PROD00155119
Description
Impact
When a CPE device was unplug during throughput testing,

some packets were incorrectly being discarded as Out of Range
(OOR).
Service
Occurrence
High
2.3.12 CM-STATUS Message for OOR may not be Sent

Tracking No.
PROD00157215
Description
Impact
An issue was observed where the modem was only sending the
CM-STATUS message after the first reported Out of Range
scenario.
Service
Occurrence
High
2.3.13 Voice Mail Waiting Indicator not consistent on some

LCS systems
Tracking No.
PROD00156759
Description
Impact
The VMWI would not always be turned on or off properly.

This has been corrected by delaying the termination of the RTP
session when the following callp feature switch is enabled
(0x10000000: Delay DLCX response against connection on
onhook only line (for VMWI)).
Operational
Occurrence
Low
2.3.14 E-MTA Reboots Dropping Call Waiting Call

Tracking No.
PROD00156212
Description
When an E-MTA is fully loaded with 2 calls on each line in a

Call Waiting (CW) scenario with the CW call being on on-hold
and an FTP download is initiated, the E-MTA reboots dropping
the first CW call. This is due to an exception when the channel
is un-configured.
20
Impact
Service
Occurrence
High
2.3.15 TEL LED Flashing when Telephone is on-hook

Tracking No.
PROD00154468
Description
The Tel LED may not indicate the true hook status of the
telephony line. If a line is off-hook when an MTA reset occurs
and the line goes on-hook before provisioning is complete, the
LED will flash after the line goes IS. Dial tone is still provided
upon the next off-hook and calls are successfully terminated to
the line. The LED is corrected on the next hook transition.
Impact
This issue as being resolved as no fix planned.

Operational
Occurrence
High
2.3.16 ATDMA DCC may cause No Dial Tone

Tracking No.
PROD00152335
Description
When testing with the ATDMA modulation profile, DCCs

would occasionally result in a problem where the MTA would
not recover causing a no dial tone event. This rare issue was
observed twice out of 100 DCC test case executions.
Impact
This issue can no longer be reproduced and is being resolved.

Service
Occurrence
Rare
2.3.17 Extreme Robustness Testing Issues

Tracking No.
PROD00150523
Description
CM fails to register with a T2/T4 Expired error. A reset of

the modem is required for recovery. The rate of occurrence is 3
in 10,000 iterations of the test cycle.
Impact
This issue can no longer be reproduced and is being resolved.

Service
Occurrence
High
21
2.3.18 Enhanced Firmware Download Events not Sent to

Syslog
Tracking No.
PROD00140664, PROD00147365
Description
When events are generated by the ARRIS Enhanced Firmware

Download feature, an entry is stored in the local event log but
not sent to the SYSLOG server if one is provisioned.
Impact
This issue is being closed as no fix planned.

Operational
Occurrence
High
2.3.19 Source Verify Errors Detected on CMTS

Tracking No.
PROD00149950
Description
Impact
A field issue has been reported stating that source verify errors
are detected on the CMTS where the MTA interface sends
packets with the CMs MAC address. This issue was originally
closed since it could not be reproduced; however, a rare issue
has been identified and a fix applied to this release. The issue
was only seen when telnet was enabled.
Service
Occurrence
Rare
2.3.20 USB Device Address is 0.0.0.0

Tracking No.
PROD00154524
Description
The dotdTpFdbTable MIB had an entry of 0.0.0.0 for the USB

device address. That entry has now been removed. The USB
host address will be displayed after a CPE is connected to the
USB port on the modem.
Operational
Impact
22
Occurrence
High
2.3.21 Unrecognized OID may cause Exception

Tracking No.
PROD00154229
Description
Impact
If an unrecognized OID is processed from the configuration

file, an exception may occur. This was the result of the OID
overflowing the allowed buffer.
Service
Occurrence
Rare
2.3.22 Send Early Media without 100rel Requirement no

Longer Includes SDP in 180
Tracking No.
PROD00153138
Description
Impact
The sipCfgSipFeatureSwitch2.0 = 0x10000000 will no longer

cause the MTA to include SDP in the 180 messages. The
feature will still send early media when it receives a 180 with
SDP without 100rel support.
Service
Occurrence
High
2.3.23 Country Template does not Default to North American

3/3 after E-MTA reset
Tracking No.
PROD00154236
Description
Impact
ppCfgMtaCountryTemplate MIB defaults to NA-57 instead of

NA-33 after an E-MTA reset.
Service
Occurrence
High
2.3.24 Ring Back Tone May Cease after 2 Rings for on-net
Calls Originated from the TM722
Tracking No.
PROD00153547, PROD00153541
Description
E-MTAs running TS7.1 firmware may cease MTA call progress

tones after 2 cycles of cadence. This is the result of a Tone
Table conversion for customers using North America
PacketCable provisioning. All country templates are affected
23
by this issue.
Impact
This issue is documented in AFB-10-0303.

Service
Occurrence
High
2.3.25 SIP: Caller ID Time Displayed Wrong Time on CPE

devices
Tracking No.
PROD00153509
Description
Impact
The Caller ID displays the wrong time on the CPE. The time
displayed had been adjusted by the TOD offset from the current
MTA time.
Operational
Occurrence
High
2.3.26 IPv6: LLC Filter Default Actions not reset after T4

Tracking No.
PROD00152789
Description
Impact
When operating in IPv6 for the CM IP address with LLC filters

that include a default action of discard, the modem may not
recover its IP address and DHCP provisioning information after
a T4 due to a failed IPv6 router solicitation. The modem must
be rebooted locally to recover service.
Service
Occurrence
High
2.3.27 arrisMtaDevMaxCPEAllowed and

arrisMtaDevNetworkAccess MIBs do not Return a Value
Tracking No.
PROD00152930
Description
When performing an SNMP walk of the below MIB Objects, no

value was returned.
Impact
arrisMtaDevMaxCPEAllowed
arrisMtaDevNetworkAccess
Operational
Occurrence
High
24
2.3.28 BPI Registration Failures

Tracking No.
PROD00151222, PROD00151285, PROD00151533
Description
Impact
An issue has been identified with a small number of modems

where BPI registration would fail as a result of missing link to
the CM certificate or key. This solution resolves the problem
with the upgrade; however, an additional reboot will be
observed.
Service
Occurrence
Rare
2.3.29 Mu Security Telnet Protocol Failures

Tracking No.
PROD00152532
Description
Impact
During extended duration Mu Security testing, several high

confidence telnet faults were observed resulting in the modem
rebooting. These faults represent potential security risks when
Telnet access is enabled.
Operational
Occurrence
Low
2.3.30 Modem Unable to Register on some CMTS devices with

more than Two Classifiers in CM configuration file
Tracking No.
PROD00153478
Description
Impact
When a CM configuration file contains more than two

classifiers, the modem is unable to register on some CMTS
networks.
Service
Occurrence
Low
2.3.31 Source Verify Failure Logs on the CMTS

Tracking No.
PROD00145828
Description
Source Verify Failure: cable source slot: 13 mdIfIndex:

0x20000003 CM: 00:15:ce:03:fa:5f CPE: 00:15:ce:03:fa:60 IP:
10.1.60.101 Address in use by 00:15:ce:03:fa:5f
Service
Impact
25
Occurrence
Low
2.3.32 IPDT: Dialing Errors with Dial Pulse

Tracking No.
PROD00153164
Description
Impact
When using the pulse dialing method on an IPDT solution,

some pulse digits were missed resulting in a misdial.
Service
Occurrence
Low
2.3.33 Non-UDP/TCP Packets might be Dropped if MTA

Provisioned
Tracking No.
PROD00153098
Description
Impact
Service degradation might be experienced when sending

35Mbps+ of traffic thru the modem. Less than 1% of the traffic
could be dropped because resource priority is given to the voice
application. This is only an issue with protocols not commonly
used for high throughput applications. TCP and UDP protocols
are handled differently and do not have such a limitation.
Service
Occurrence
Low
2.3.34 EURO: Calls do not Complete when using Dial Pulse

Dialing
Tracking No.
PROD00151250
Description
Impact
European loads fail to complete calls when using dial pulse

dialing.
Service
Occurrence
High
2.3.35 Hook Status and Line Status MIB Objects Not

Impemented
Tracking No.
PROD00152779, PROD00152394
26
Description
Impact
The SNMP MIB Objects, arrisMtaDevCallStatsHookStatus and

arrisMtaDevLineCardState, were not implemented in the
firmware prior to this release.
Operational
Occurrence
High
2.3.36 CM MIB Walk Stops on MTA MIB Objects

Tracking No.
PROD00152635, PROD00152465
Description
Impact
When walking MTA MIBs from the CM IP address, such as the

arrisMtaDevDhcp MIB tree, the MIBs return no such
instance. This could result in the tool being used to perform
the MIB walk to halt and not complete. These MIBs will now
return null values/strings.
Operational
Occurrence
High
2.3.37 Modem Should Ignore DHCPv6 Advertise Message with

"NoAddrsAvail" Status Code
Tracking No.
PROD00152744
Description
Impact
Per RFC 3315, the modem should ignore any DHCPv6

Advertise message with "NoAddrsAvail" status code. If
multiple DHCPv6 servers are present, and the modem is only
provisioned on one of these servers, this may result in a
DHCPv6 failure.
Service
Occurrence
High
2.3.38 E-MTA does not register with the

arrisMtaDevSwDnldNoSvcImpact in CM Configuration
File
Tracking No.
PROD00152427
Description
Impact
The E-MTA will fail to register if the

arrisMtaDevSwDnldNoSvcImpact MIB is included in the CM
configuration file. The E-MTA will register and function
properly if this MIB is included in the MTA configuration file.
Service
Occurrence
High
27
2.3.39 CLI Debug Command 'dsxtrace' did not Enable the DSX
Traces
Tracking No.
PROD00152726
Description
Impact
The dsxtrace command from the Callp CLI will now correctly
enable and disable the DSX tracing.
Operational
Occurrence
High
2.3.40 Call Processing Debug Traces were Persistent

Tracking No.
PROD00152333
Description
Impact
When logging persistence was disabled, the call processing

debug traces (NCS messages, SIP call leg messages, NCS
parser, etc.) were still persistent after the telnet session ended.
This has been adjusted so that unless the logging persistence is
enabled the traces are disabled upon exit from telnet.
Operational
Occurrence
High
2.3.41 US Rate Limit may not be Accurate with Mixed US

Modulations
Tracking No.
PROD00152430
Description
Impact
When mixed modulation US channels are bonded, the upstream

TMax value is not properly enforced resulting in rate limiting
variances of approximately 2Mbps. The modem will go above
its allowed rate limiting value until throttled by the CMTS peak
rate limit setting, resulting in a pattern where the modem
exceeds its upstream rate limiting settings, and then dips below
the rate limit for small intervals.
Service
Occurrence
High When US channel bonding is enabled
2.3.42 ipNetToMediaTable not Responding Correctly to SNMP

getNext
Tracking No.
PROD00152200
Description
Queries of the the ipNetToMediaTable interface 16 via SNMP

GET-NEXT operation returned incorrect data, and did operate
28
Impact
in the same manner as D2.0 for this SNMP MIB object.

Operational
Occurrence
High
2.3.43 Performance Degradation with Large Round Trip Delays

Tracking No.
PROD00151834
Description
Impact
Throughput testing utilizing Ookla speed test servers had

degraded results for DS traffic when large round trip delays
existed in the network between the servers and devices under
test regardless of TCP window size.
Service
Occurrence
High
2.3.44 TS 7.1.89: DOCSIS 3.0 Potential Registration Issue

with US Channel Bonding
Tracking No.
PROD00151896
Description
DOCSIS 3.0 modems running TS 7.1.89 may not complete

successful registration if US channel bonding is enabled and the
modem configuration file includes service flow traffic priorities
of 4 or greater for the primary upstream service flow.
Impact
This issue is disclosed in AFB-10-0301.

Service
Occurrence
High
2.3.45 SIP: Emergency Call Network Hold Media Type Set

Incorrectly
Tracking No.
PROD00152328
Description
Impact
When Network Hold is used for emergency call on hook, the

media type in the SDP was incorrectly set to SENDRECV. It
will now be set to INACTIVE or SENDONLY depending on
the value of sipCfgSipFeatureSwitch.
Service
Occurrence
High
29
2.3.46 SIP: 200 OK Message Does Not Contain the SDP

Tracking No.
PROD00152132
Description
Impact
When sipCfgSipFeatureSwitch2 bit 0x10000000 is enabled to

provide early media without 100rel, SDP will be included both
in the provisional response (18X) and in the 200 OK.
Service
Occurrence
High
2.3.47 IPv6: Small Memory leak if Multicast DSID Forwarding

is Enabled
Tracking No.
PROD00151424
Description
Impact
There is a slow memory leak in the modem that will eventually

cause the modem to reset if Multicast DSID Forwarding (MDF)
is enabled in the CMTS for IPv6.
Service
Occurrence
Medium
2.3.48 Allow leading '/' in the MTA Configuration File

Tracking No.
PROD00148165
Description
The ability to have a / as the leading character in the MTA

configuration file name is now supported. For this to work, the
MTA feature switch must be enabled. The details are listed
below:
Impact
ppCfgMtaFeatureSwitch is 0x400:
Operational
Occurrence
High
2.3.49 Battery Code Not Displayed

Tracking No.
PROD00151724
Description
When a battery of part number 789699 was plugged into the EMTA, the "Ordering Code" showed as "Unavailable". This part
number has been added to the list of supported batteries and is
now displayed correctly on the web page and via SNMP in the
MIB, arrisMtaDevBatteryOrderingCode.
Operational
Impact
30
Occurrence
High
2.3.50 SysObjectID Increments on each Firmware Release

Tracking No.
PROD00151778
Description
Impact
The SysObjectID previously incremented on each firmware

release. The SNMP MIB Object now only increments for new
HW models and not per firmware release.
Operational
Occurrence
High
2.3.51 Webpage TOD may not be Retrieved

Tracking No.
PROD00151605
Description
Impact
The Time of Day (TOD) field was not updated on the web page
if TOD was not successful during the initial registration. The
TOD would be displayed as not provisioned.
Operational
Occurrence
High

Tracking No.
See Below
Description
Impact
Service
Occurrence
Rare
PROD00151239: A single one-time exception was caught

during CM registration
2.3.53 MuSecurity HTTP Unsafe Test Suite Incompatibility

Tracking No.
PROD00151437
Description
The MuSecurity test suite for HTTP Unsafe is not compatible

with the ARRIS D3.0 CPE products. ARRIS CPEs do not
support PUT and DELETE methods due to security concerns.
Impact
This change will make the E-MTA respond that the HTTP PUT
and DELETE methods are not implemented allowing the
MuSecurity test suite to pass with warnings.
Operational
31
Occurrence
High
2.3.54 SIP: Post Provisioning Issue with IfAdminStatus

Tracking No.
PROD00151532, PROD00150319
Description
Impact
If SIP post provisioning is used to modify the line

ifAdminStatus, the set to enable the line will not take effect
upon initial setting.
Service
Occurrence
High
2.3.55 Ring Cadence Default Values for Certain Countries did

not match values from prior ARRIS releases
Tracking No.
PROD00151304
Description
Impact
The SNMP MIB Objects for ring cadence did not default
correctly for the Chile, Japan, Israel, Mexico, MexicoC,
Panama or Brazil LC country templates. Changes have been
made to correctly default the MIBs for these additional
countries.
Service
Occurrence
High
2.3.56 Incorrect Hook Flash Timing

Tracking No.
PROD00151423
Description
The hook flash timing values were incorrectly defaulted to be

300ms for MinHookFlash and 800ms for MaxHookflash for all
country code templates on TM702/TM722G hardware models,
unless the values were specified via MIB in the MTA
configuration file.
Impact
Service
32
Occurrence
High
2.3.57 CM may register in partial services mode

Tracking No.
PROD00150158, PROD00150739, PROD00150822
Description
Impact
It is possible for modems to sometimes register in partial

service mode instead of fully bonded. This causes some
CMTSs to force the modem to re-register in 1x1 mode.
Service
Occurrence
High
2.3.58 Event Logs display MAC address when MAC/FQDN

MIB is set to disabled in configuration file
Tracking No.
PROD00150443
Description
Impact
The arrisMtaDevEventHideMacFQDNandIPAddress MIB

Object was not hiding the MAC address and FQDN of logs that
occurred before the modem had ranged & registered when set to
disabled in the configuration file.
Operational
Occurrence
High
2.3.59 Wrong HTTP Header end of line character

Tracking No.
PROD00150370
Description
Impact
When a customer tries to open the web page of the cable

modem, the modem generates the HTTP response with a bad
HTTP header. The header of the HTTP entity ends with LFLF
(0a 0a) when it should end with CRLF (06 0a). This is not a
problem for main browsers like Internet Explorer, Mozilla, or
Safari.
Operational
Occurrence
Low
2.3.60 Incorrect Static CPE Count may not be Accurate

MAXCPE Counter may be exceeded
Tracking No.
PROD00150815
Description
The Static CPE counter is reset to zero when the ethernet link
goes down on a CM with statically provisioned CPE devices,
33
allowing for the MAXCPE value to be exceeded when

additional dynamic CPE MAC addresses are learned after the
ethernet connection is restored.
Impact
Operational
Occurrence
High When static CPE provisioning is utilized.
2.3.61 Modem may reset occasionally when Configuration File

contains IP filters
Tracking No.
PROD00149578
Description
Impact
The modem may reset occasionally after completing a data

stream when the configuration file contains IP filters. This
problem may occur when the configuration file contains an
outbound IP filter that will get hit by the data stream.
Service
Occurrence
Low
2.3.62 Loop Diagnostics Run on IS Line

Tracking No.
PROD00148965
Description
Impact
Loop Diagnostics can be initiated without taking the line OOS.

This could result in dropping a subscriber call if the line state is
not validated prior to running the command.
Service
Occurrence
High
2.3.63 DS LED Bonded Mode Display may not be Correct

Tracking No.
PROD00147528
Description
Impact
When the modem is provisioned as a DOCSIS 2.0 device on

some CMTS systems, the DS LED remains green even though
it is not operating in a bonded solution and should be amber.
Operational
Occurrence
Low
2.3.64 Short RF Cable Cut may Cause T4 Timeout

Tracking No.
PROD00146173
34
Description
Impact
On short RF cable cuts, the cable modem may go through the

entire T4 process causing an additional delay in recovery of
approximately 60 seconds.
Service
Occurrence
Rare
2.3.65 Modem does not respond to Pings after Short Cable

Cuts
Tracking No.
PROD00150407
Description
This is a Partial Service / CM-STATUS type of issue where the

modem is entering a partial service mode (due to the cable cut),
and the bonded DS flows intermittently may not recover.
Impact
This issue was resolved with a CMTS load change and not an
issue on the E-MTA.
Service
Occurrence
High
2.3.66 Static TFTP port selection could cause failed TFTPs

Tracking No.
PROD00150262
Description
Impact
The TFTP port has been set to be randomly generated and not
use the same port for back-to-back requests to prevent failures
from occurring when a TFTP retransmission is necessary.
Operational
Occurrence
Low
2.3.67 DOCSIS Card Failover Causes T4 Timeout

Tracking No.
PROD00148818
Description
Impact
When DOCSIS sparing takes place, the modem would register a

T4 timeout requiring it to range & register with the CMTS
again, instead of reacquiring the downstream signal with no loss
of service.
Service
Occurrence
High
35
2.3.68 Modems Register in Upstream Partial Service

Tracking No.
PROD00149799, PROD00148644
Description
In cases where the modem has to retransmit some of the

registration messages on CMTS with US Channel Bonding
active, the modem can incorrectly register in an upstream
partial service state.
Impact
Service
Occurrence
High If US Channel Bonding is enabled on CMTS
2.3.69 Dialing Method Line Persistence

Tracking No.
PROD00149566
Description
For dialing method line persistence, the value stored in

NVRAM via manual SNMP action should take precedence over
any dialing method line persistence setting in the configuration
file in order to match previous behavior of TS 6.1 release.
Impact
Operational
Occurrence
High
2.3.70 FQDN with trailing '.' marked invalid

Tracking No.
PROD00149523
Description
Impact
An issue was discovered where a CMS would redirect the

FQDN and append a trailing period - '.'. When this occurred,
the E-MTA would mark the FQDN as invalid causing the DNS
request to not get sent out for resolving the IP address.
Service
Occurrence
High If FQDNs with trailing periods . are used
2.3.71 SIP: Calls Fail for Messages Greater than 1500 bytes
Tracking No.
PROD00149718
Description
When inbound SIP call processing messages to the MTA are

greater than 1500 bytes in size, they are fragmented and not
correctly processed resulting in call failures. This condition can
occur when the SIP proxy uses both Record-Route and Via
headers.
36
Impact
Service
Occurrence
High
2.3.72 LED Behavior is Incorrect during AC Failure Condition

Tracking No.
PROD00149008
Description
Impact
The behavior of the Power and Telephony LEDs during an AC

Failure condition is not correct. The Power LED is lit as solid
ON when it should be flashing, and the MTA LEDs are not lit
when a line goes off-hook.
Operational
Occurrence
High
2.3.73 Multicast Traffic Issue with older CMTSs

Tracking No.
PROD00149127
Description
Impact
When running in either IPv4 or IPv6 mode, the modem will not
pass multicast traffic on some older CMTS loads that
incorrectly populate the MDF setting in the REG-RSP message.
A new MIB to allow customers to override this parameter is
needed for backwards compatibility.
Service
Occurrence
High
2.3.74 Voice Quality Metrics MIBs incorrect

Tracking No.
PROD00149463
Description
Impact
The arrisMtaDevVqmMetricTable MIB results are misaligned

by one index position, causing incorrect results to be returned
when these SNMP MIBs are queried via script or network
monitoring tool. The CLI and WebGUI displays for Voice
Quality Metrics, are not affected by this issue.
Operational
Occurrence
High
2.3.75 MuSecurity Protocol Mutation Attack Test Failure

Tracking No.
PROD00149153
Description
The MuSecurity test suite for protocol mutation attack testing

of TELNET functionality is failing on the modem. A reboot is
37
Impact
required to restore dialtone and CM management (telnet,

WebGUI, SNMP) capabilities.
Service
Occurrence
High
2.3.76 Configuration Parameters Web Page is not accurate

Tracking No.
PROD00148047
Description
Impact
Some fields of the configuration parameters webpage are not

accurate and may reflect incorrect values.
Operational
Occurrence
High
2.3.77 CLI Error Message on CRCX for DSX DQoS

Tracking No.
PROD00145917
Description
When the E-MTA is provisioned to perform DSX DQos, the

following error message may be seen on the console port. This
message is not service affecting.
[ERROR]
[ARRIS.CALLP_SWERR(pid=365)(dqos_process_crcx:435)]:
dqos_process_crcx0:missed dlcx?? conNum=8 curr_state=0
Impact
Operational
Occurrence
Low

Tracking No.
Description
See Below
Impact
PROD00149458: RF cut while the QoS was being

setup event may cause E-MTA to not be able to provide
service
PROD00150338/PROD00150592:
CM registration
failures have been noted during RF impairment testing.
PROD00150014: An issue has been identified where
the modem occasionally reboots after a 10 second cable
cut due to a watchdog timer on the modem.
The above issue have been resolved or determined to be an

issue as a result of other components in the network.
Service
38
Occurrence
Rare
2.3.79 Advanced WebGUI Accessible after Single Login

Tracking No.
PROD00149059
Description
Impact
If a user has logged into the Advanced web page and enabled
access, then other users can also access the web page without
being required to enter the password while the original users
session is still active.
Operational
Occurrence
High
2.3.80 Router Congestion on HTTP Download May Result in

Slower Throughput
Tracking No.
PROD00147023
Description
Impact
An issue has been observed during testing with data collection

machines around the TurboDOX feature on the modem. This
issue is a result of the router between the CMTS, modem, and
test equipment not being able to handle the ACK suppression
algorithm to increase throughput. This issue results in slower
throughput during testing of HTTP downloads.
Service
Occurrence
High
2.3.81 Rate-limit Traffic Shaping on CMTS may cause Lower

US Throughput
Tracking No.
PROD00146904
Description
Impact
When the cable rate-limit token-bucket shaping (default on

some CMTS equipment) setting is enabled on certain CMTS
equipment, the modem encounters a 4% lower US throughput
compared to the performance without the 'shaping' setting.
Service
Occurrence
Low
2.3.82 Foreign EMF Voltage Recovery

Tracking No.
PROD00148904
Description
During initialization of an E-MTA, loop diagnostics are run to
39
Impact
validate the connection. If a foreign EMF voltage is detected,

the line card is placed into a protection state. However, the line
does not automatically recover when the fault is removed.
Service
Occurrence
High
2.3.83 IPv6 SSH Log Events Missing

Tracking No.
PROD00146294
Description
When using IPv6, the SSH events for login accepted/rejected

are not provided to the syslog server or event logs.
Impact
This issue is resolved as a configuration problem.

Operational
Occurrence
High
2.3.84 LED for Line 2 Continues to Blink on a 1 Line Unit

Provisioned on the Switch
Tracking No.
PROD00144137
Description
Impact
Telephony line 2 LED continuously blinking on a unit where

only line 1 is provisioned on the switch. Configuration files
have both lines provisioned.
Operational
Occurrence
High
2.3.85 Incorrect Dual-Color LED Indicator on Some CMTS

Vendors
Tracking No.
PROD00146372
Description
Impact
When using the dual-colored LED feature with some CMTS

vendors equipment, the E-MTAs LEDs will remain Green
(indicating the modem is bonded) even though the modem has
fallen back to a DOCSIS 2.0 mode when the LED should
display Yellow to indicate non-bonded operations.
Operational
Occurrence
High
40
2.3.86 Cant Provision Number of MTA DHCP Retry Attempts

Tracking No.
PROD00146697
Description
Impact
When using BASIC or HYBRID mode provisioning, the MTA

will attempt to provision using SECURE mode (as required by
PacketCable specifications) three times before accepting
another provisioning method. The MIB object for provisioning
the number of SECURE retry attempts via DHCP,
arrisCmDoc30SetupDhcpRetries, is not implemented in this
release.
Operational
Occurrence
High
2.3.87 Battery Telemetry Alarm Syntax Does Not Match Prior

Touchstone Releases
Tracking No.
PROD00146549
Description
Impact
The syntax of the AC Fail Alarm and Alarm Clearing message

need to be updated to match existing Touchstone releases. This
is needed for compatibility with some SNMP monitoring tools.
Operational
Occurrence
High
2.3.88 E-MTA Does Not Display Service Class Name

Tracking No.
PROD00142126
Description
Impact
The E-MTA's service class name is not displayed on the

configuration parameters web page.
Operational
Occurrence
High
2.3.89 Telnet Packets Could Be Sent with the Wrong Source

MAC Address
Tracking No.
PROD00145828
Description
In rare cases, the telnet packets from the CM or MTA interface

could be sent out with the wrong MAC address. This could
cause the CMTS to drop those packets and affect the telnet
session if the Source Verify feature was enabled
41
Impact
Operational
Occurrence
Rare
2.3.90 Upstream Channel Bonding May Result in Partial

Service Mode
Tracking No.
PROD00141227
Description
Impact
Some E-MTAs in an upstream channel bonding group may fail

initial ranging on upstreams with mixed channel-widths,
channel types, or modulations resulting in a partial service
mode of operation.
Service
Occurrence
High
2.3.91 Upstream Drop Classifier Support

Tracking No.
PROD00146368, PROD00146467
Description
Impact
When using the C4 CMTS release 7.1.1.41, the DOCSIS 3.0

Upstream Drop Classifier functionality must be disabled in
order to correctly support DOCSIS 2.0 IP Filtering functionality
in the CM configuration file. In this release, the Upstream
Drop Classifier is enabled.
Service
Occurrence
High
2.3.92 DNS Response of Type CNAME Does Not Work

Tracking No.
PROD00145332
Description
Impact
A DNS response with the type of CNAME rather than A (Host

Address) resulting in the E-MTAs failure to resolve the IP
address. If the DNS response has multiple answer records with
a type of A (Host Address) then the IP address is successfully
resolved.
Service
Occurrence
High
2.3.93 MTA Accepts Unknown Ciphersuites

Tracking No.
PROD00143599
42
Description
Impact
The MTA should ignore unknown RTP/RTCP ciphersuites in a

Create Connection (CRCX) message from the CMS, but
currently they are accepted.
Service
Occurrence
Low
2.3.94 MuSecurity TELNET Failure

Tracking No.
PROD00146132
Description
Impact
A failure was detected in the TELNET portion of the

MuSecurity Mutation Attack Suite related to the MTAs
handling of excessive IAC suboptions in the script.
Operational
Occurrence
High
2.3.95 SIP: Blank digitmap causes exception

Tracking No.
PROD00145881
Description
Impact
Setting any of the digitmaps to an empty string in the MTA

config file can lead to an exception during dialing. By default,
no digitmaps are blank.
Service
Occurrence
High
2.3.96 VQM: Local Metrics Reported to Call Server are All

Zero
Tracking No.
PROD00146129
Description
Impact
An issue has been identified where the local voice quality

metrics are reported as all zero to the call server at the
completion of a call.
Operational
Occurrence
High
2.3.97 Automatic OSI Intermittently Fails on IPDT

Tracking No.
PROD00145969
Description
In an IDPT solution, automatic OSI was not always initiated on

the terminating line due to a timing issue.
43
Impact
Service
Occurrence
Medium
2.3.98 Web Page Related Issues

Tracking No.
Description
See Below
Impact
PROD00146783: The Status web page upstream

symbol rate may be incorrect when different upstream
channel widths are used across various channel IDs.
PROD00146620: The web page incorrectly displays the
provisioning method as Full Packetcable when using
BASIC or HYBRID provisioning methods for the MTA.
PROD00146082& PROD00146625: On the Status web
page under Interface Parameters, the MTA state will be
show as Down even though the MTA is fully
operational. The state will not get updated unless an
SNMP query on the interface setting is performed.
PROD00146570: The correct value of the Loop
Voltage Management Reset Timer is not displayed
when Policy 3 is selected.
PROD00146849: On the Status web page, the reset
codeword (CW) button does not work.
Operational
Occurrence
High
2.3.99 Upgrade Fails if Upgrade Server TLV is set to 0.0.0.0

Tracking No.
PROD00144249, PROD00145093
Description
Impact
In prior Touchstone releases, if the Upgrade Server TLV was

set to 0.0.0.0 in the CM configuration file the E-MTA would
use the same TFTP server IP address that the configuration file
was obtained from in order to download the new firmware
image.
Service
Occurrence
High
2.3.100
SIP: sipCfgDialFeatCode mib does not support
multiple, comma-separated dial strings
Tracking No.
PROD00145489
44
Description
Impact
The SIP dialing feature MIB object, sipCfgDialFeatureCode,

cannot support both DTMF and DP patterns at the same time.
Only one dial string may be provisioned per dial feature.
Operational
Occurrence
Low
2.3.101
VQM Feature only Stores Last 10 calls
Tracking No.
PROD00148617
Description
Impact
The VQM feature only store information for the last 10 calls
instead of the last 50 calls as in other Touchstone releases.
Operational
Occurrence
High
2.3.102
IPv6: E-MTA Not Sending Option Code 17 in
ORO
Tracking No.
PROD00148068
Description
Impact
When running in IPv6 mode, the E-MTA was not including

option code 17 (Vendor Specific Information) in theDHCPv6
Option 6 ORO (Option Request Option) list.
Operational
Occurrence
High
2.3.103
Potential Upgrade Failure
Tracking No.
PROD00147348, PROD00148288
Description
ARRIS has identified a rare issue where the modem may fail to
upgrade successfully. This issue is the result of flash
corruption.
Impact

Service
Occurrence
High
2.3.104
SIP: SIP Message Tracing Information Missing on
Webpage
Tracking No.
PROD00142600
45
Description
Impact
Some details are missing from the SIP message output provided
under the Advanced webpage. The output available from an
SSH/Telnet session with tracing enabled displayed all of the
messaging.
Operational
Occurrence
High
2.3.105
TLV Long Encoding Format Not Supported
Tracking No.
PROD00148414, PROD00148407
Description
Impact
TLV entries encoded in the CM or MTA configuration files

using the long format with two extra bytes in the header field
were rejected preventing the modem from completing
registration.
Service
Occurrence
High
2.3.106
Line may become Stuck in Notification State
Tracking No.
PROD00147886
Description
Impact
If a DNS request fails during the retransmission of a

notification message to the CMS, the line may get stuck in
NOTIFICATION state and require the line to be taken out of
service then back in service to recover.
Service
Occurrence
Low
2.3.107
End of Call Statistics Show Incorrect Data
Tracking No.
PROD00147963, PROD00148226, PROD00126112
Description
When an established call was placed in a connection mode that

required incoming RTP packets to be ignored (such as
INACTIVE or SENDONLY), the discarded packets during this
time were incorrectly reported to the call agent as lost in the
end-of-call statistics.
Impact
Operational
Occurrence
High
46
2.3.108
CallAgentID Only Supports FQDN
Tracking No.
PROD00137537, PROD00148250
Description
Impact
The CallAgentID does not support the ability to use a bracketed

IP address for BASIC and HYBRID provisioning methods.
Service
Occurrence
High
2.3.109
CM Fails to Lock to Secondary Downstream
Tracking No.
PROD00141049, PROD00147082
Description
Impact
In some cases, following a CM power cycle, reset or cable cut,

it is possible for the modem to not successfully lock to one of
its secondary DSs. This results in the CM being in a partial
service state. The condition is reported to the CMTS in the
REG-ACK message during the registration process.
Service
Occurrence
High
2.3.110
IPv6: Lease Times Displayed are not valid
Tracking No.
PROD00144517
Description
Impact
The DHCPv6 lease times stored for the actual IPv6 lease renew,
and rebind times are not displayed correctly. This issue could
be observed via the arrisCmDoc30DhcpLeaseParameters MIB
Objects as well as the web page.
Operational
Occurrence
High
2.3.111
Enhancement to TFTP Retry Mechanism
Tracking No.
PROD00146374
Description
Impact
A failure scenario was noted when a download was attempted

during a mass upgrade and the TFTP server was busy. A new
random back off timer has been added to assist in improving
TFTP download performance in this scenario.
Operational
Occurrence
High
47
2.3.112
Incorrect LED Status during AC-FAIL Condition
Tracking No.
PROD00136974
Description
Impact
During an AC-FAIL condition, the LEDs were not transitioning

to a power save condition. When AC power is not available,
the DS, US, On-line, and Link LEDs should all be off.
Operational
Occurrence
High
2.3.113
PCMM GATE-SET Transaction Failure
Tracking No.
PROD00146982, PROD00140175
Description
Impact
DSX transactions originated by the CMTS with multiple

envelopes were rejected preventing the establishment of a
service flow in a PacketCable Multimedia (PCMM) scenario
where Quality of Service (QOS) is initiated via the Session
Border Controller & Policy Server entities on the network.
Service
Occurrence
High
2.3.114
pktcEnNcsEndPntHookState MIB Object may
Report Incorrect Hook State
Tracking No.
PROD00147670
Description
Impact
The SNMP MIB Object, pktcEnNcsEndPntHookState was not

reporting
the
correct
hook
status
state
(onHookPlusNCSActivity) when ring splash was being played.
Operational
Occurrence
High
2.3.115
Traffic Below Baseline of 99.95%
Tracking No.
PROD00147853
Description
Impact
Several issues were noted to cause NCS and SIP traffic to fall
slightly below the baseline target of 99.95%. This issue was
related to the development of the Voice Quality Metrics feature
and gathering of call statistics data.
Service
Occurrence
High
48
2.3.116
pktcDevEvReportLevel Incorrect for AC Fail Clear
Trap
Tracking No.
PROD00147022
Description
Impact
The SNMP trap for a cleared AC Failure log was being reported
as a Major event instead of Informational for the
pktcDevEvReportLevel.
Operational
Occurrence
High
2.3.117
SIP: SIP Calls Fail after MTA IP Address Change
via DHCP RENEW
Tracking No.
PROD00147208
Description
Impact
SIP calls will fail if the MTA is assigned a new IP address ( that
is different from the current one) during the MTA DHCP
renewal sequence. A reboot of the unit is required to clear the
issue.
Operational
Occurrence
Low
2.3.118
SNMP MIB Object to Show Ethernet Duplex
Status
Tracking No.
PROD00146117
Description
Impact
An SNMP MIB Object to show the Ethernet duplex status was

added to this release to support DOCSIS 3.0 E-MTAs. The
MIB object, arrisCmDoc30BaseReportDuplex, provided this
capability.
Operational
Occurrence
High
2.3.119
DHCP NAK Sent as Broadcast Instead of Unicast
Tracking No.
PROD00145033
Description
DHCP NAK is sent as a broadcast instead of unicast message

during DHCP Renew stage.
Upon further investigation, this is not an issue and the firmware
is operating as designed.
49
Impact
Operational
Occurrence
High
The following issues were resolved in release 7.1.61A
2.3.120
Modems May Intermittently Fail to Register in
Bonded Mode
Tracking No.
PROD00146737
Description
ARRIS has identified an issue where the ARRIS DOCSIS 3.0

modems after a cable cut, reset or reboot may fail to lock on
one of the known good secondary down streams configured due
to a QAM detection issue and will not operate in fully Bonded
Mode. As a result of this issue, the modem will only operate in
Partial Services Mode.
Impact

Service
Occurrence
High
2.3.121
Ignore CMTS (S-TDMA) 10.24MHz Timing in MDD
Tracking No.
PROD00146835
Description
Impact
ARRIS has found that certain CMTS cards do not provide a

reliable 10.24MHz reference in the downstream signal, but that
they still instruct the modem via the MDD to use STDMA
(synchronous TDMA) mode. Since STDMA requires the
modem to use the 10.24MHz reference rather than its own
internal oscillator for its timing, the modems transmit timing is
not reliable when used with these CMTS cards. The problem is
so severe that the modem will often fail to register. To prevent
this problem, ARRIS has modified the load to ignore the
STDMA setting in the MDD and to always use the modems
internal oscillator as its timing reference.
Service
Occurrence
High
50
2.3.122
MTA Time Server Shows 0.0.0.0 on the Modem's
DHCP Web Page
Tracking No.
PROD00140253
Description
Impact
The modem's DHCP web page displays the MTA Timer Server
IP address as 0.0.0.0.
Operational
Occurrence
High
2.3.123
ipNetToMediaPhysAddress MIB Object Failure
Tracking No.
PROD00136590
Description
Impact
An SNMP query of the ipNetToMediaPhysAddress MIB object

with index 16 fails to provide the MTA MAC and MTA IP
address when queried via SNMP.
Operational
Occurrence
High
2.3.124
Fax Failure on Origination from E-MTA
Tracking No.
PROD00138823
Description
Impact
When a standard fax call is originated from an E-MTA, the fax

will fail to complete. Terminating fax calls complete
successfully.
Service
Occurrence
High
2.3.125
Syslog Events May Not Be Sent
Tracking No.
PROD00135017
Description
Impact
After filling up the MTA vendor event log buffer with

approximately 50 logs, syslog events will no longer be sent.
Operational
Occurrence
High
51
2.3.126
Recovery Time Extended for a RF Cut
Tracking No.
PROD00142843
Description
Impact
During an RF cut on a registered E-MTA with both upstream

data and voice, the recovery time is approximately 5 minutes.
This is longer than expected.
Service
Occurrence
High
2.3.127
CM Filter Issues
Tracking No.
PROD00142847, PROD00142849
Description
Impact
The CM filters used for IP packets and UDP traffic currently

are not operational.
Service
Occurrence
High
2.3.128
pktcDevEvEndpointName May Contain
Incomplete Entries
Tracking No.
PROD00142316
Description
Impact
The pktcDevEvEndpointNameMIB object, may contain

incomplete information for the IP and FQDN address. These
values are sometimes cut off in the display.
Operational
Occurrence
High
2.3.129
Web Page Issue with Event Logs
Tracking No.
PROD00142198
Description
Impact
A problem has been observed with the event logs not wrapping
on the web page. When this condition occurs, logs past a
certain date will not be visible.
Operational
Occurrence
Low
52
2.3.130
Extreme Robustness Testing Issue Currently
Under Investigation
Tracking No.
PROD00142274
Description
During recovery of a cable cut if another cable cut occurs, there

is a possibility phone service may temporarily be unavailable.
The CM portion of the E-MTA is still manageable and this
issue has only been seen after numerous cable cuts. The EMTA does automatically recover after an unknown period of
time or the E-MTA could be reset for faster recovery.
Impact
Service
Occurrence
Low
2.3.131
Problem with SNMP MIB Objects in Co-existence
Mode
Tracking No.
PROD00134801
Description
Impact
In coexistence mode, the CM does not populate

snmpTargetParamsTable, snmpNotifyObjects, and
snmpNotifyFilters (OSS.01).
Operational
Occurrence
High
2.3.132
EuroDOCSIS: docsQosParamSetTable Does Not
Comply
Tracking No.
PROD00135779
Description
Impact
In the docsQosParamSetTable, the indices should appear in

order ifIndex, docsQosParamSetType, and
docsQosParamSetServiceFlowId (EuroDocsis 3.0 standard).
On the ARRIS E-MTA, they appear in the order ifIndex,
docsQosParamSetServiceFlowId, and docsQosParamSetType
(EuroDocsis 2.0 standard).
Operational
Occurrence
High
53
2.3.133
EURO Secure MTA Provisioning Mode Not
Working
Tracking No.
PROD00134163
Description
Impact
The Euro-PacketCable 1.5 SECURE provisioning method is not

working at this time. NA PacketCable 1.5 SECURE
provisioning methods work correctly.
Service
Occurrence
High
2.3.134
Call Completion Rate below Baseline with 64-byte
DS Traffic
Tracking No.
PROD00134135
Description
Impact
Call completion rates are below baseline when voice traffic is

present with high data traffic rates of 64-byte traffic in the
downstream direction. This problem does not occur with
packet sizes of 128 bytes or higher.
Service
Occurrence
Low
2.3.135
E-MTA Sometimes Doesnt Bond After DFO
Command from CMTS
Tracking No.
PROD00141420
Description
Impact
The TM702 is getting the Downstream Frequency Override

(DFO) but it is not moving to the indicated DS. After the EMTA fails to get the correct DS, the CMTS will move to the
next frequency until it exhausts all options. At this time, the EMTA will register in D2.0 mode. This DFO issue has only
been seen while interoperating with a specific CMTS vendor.
Service
Occurrence
Low
2.3.136
igmpCacheTable Not Populated
Tracking No.
PROD00134800
Description
In NmAccess mode, the igmpCacheTable is not populated

correctly and is empty.
54
Impact
Operational
Occurrence
High
2.3.137
SIP: sipCfgCallWaitingStarCodeSurvivesReset
does not Survive Reset
Tracking No.
PROD00138153
Description
Impact
Setting this MIB allows persistent storage of a user requesting

that Call Waiting be disabled until the user re-activates Call
Waiting. However, the setting only lasts until next reset.
Service
Occurrence
High
2.3.138
SIP: sub-TLVs 69, 70, and 71 within TLV 43 MIB
in the MTA Configuration File were not supported
Tracking No.
PROD00140480
Description
Impact
TLVs for SIP DigitMap, Dial Feature DigitMap, and Proxy

Dial Feature DigitMap MIBs in the MTA Config file were not
supported.
Service
Occurrence
High
2.3.139
CallP / QoS Statistics Web GUI Incomplete
Tracking No.
PROD00143824
Description
Impact
CallP/QoS Web GUI missing CallP state, LC state, and Payload

Header Suppression information.
Operation
Occurrence
High
2.3.140
Call Waiting Disabled by Default
Tracking No.
PROD00143110
Description
Call Waiting should be enabled but was disabled by default.
Impact
Service
Occurrence
High
55
2.3.141
Pasting Multiple Commands over Telnet does not
Work
Tracking No.
PROD00136034
Description
Impact
Certain Telnet clients are inserting null terminator after new

line characters and causing command not found error message
when pasting multiple CLI commands.
Operational
Occurrence
Low
2.3.142
SIP: sipCfgProvisionedCodecArray Ignored
Tracking No.
PROD00142659
Description
Impact
sipCfgProvisionedCodecArray MIB does not allow space

characters between Codecs that are listed.
Service
Occurrence
High
2.3.143
SIP: Disabling Session Timers causes ReINVITEs to Fail
Tracking No.
PROD00143309
Description
Impact
Enabling the SIP feature switch option to disable Session

Timers causes Re-INVITE messages to fail.
Service
Occurrence
High
2.3.144
VMWI Signal Remained Active after a Reboot
Tracking No.
PROD00143289
Description
Impact
On a MTA reboot, cable cut or taking the line OOS the VMWI
state should return to the default of off but the signal remained
active.
Service
Occurrence
Low
56
2.3.145
SIP: Hook Flash Timing Cannot be changed by
Configuration File
Tracking No.
PROD00143371
Description
Impact
SIP loads do not accept changes to Hook Flash timing

provisioned via MTA config file.
Service
Occurrence
High
2.3.146
Incorrect Quarantine and Hook State
Tracking No.
PROD00143273
Description
Impact
pktcEnNcsEndPntQuarantineState and the

pktcEnNcsEndPntHookstate MIBs returned incorrect values.
Operational
Occurrence
High
2.3.147
Line Card Diags Wont Work via SNMP
Tracking No.
PROD00142938
Description
Impact
ppSurvPortLcDiagRequest MIB for Line Card diags could not

be started via SNMP.
Operational
Occurrence
High
2.3.148
Scanover Web GUI Accessible via the WAN IP
Tracking No.
PROD00142867
Description
Impact
Scanover.htm web page was accessible via the WAN IP where

it should only be available via the LAN IP of 192.168.100.1
scanover.htm when the modem is not ranged and registered.
Operational
Occurrence
High
2.3.149
SIP: Incomplete Information in the SIP-REGISTER
Tracking No.
PROD00143788
Description
SIP User-Agent Hearder missing hardware and software

version information in the SIP-REGISTER messages.
57
Impact
Operational
Occurrence
High
2.3.150
Modems Stuck on TFTP File due to Configuration
Filename
Tracking No.
PROD00143806
Description
Impact
Modems will get stuck in TFTP loop when trying to download

a config file with colons : in the filename.
Service
Occurrence
High
2.3.151
Supervisory Tones are Not Correct
Tracking No.
PROD00143492
Description
Impact
MTA tone tables contain setting for North American tones but
plays European tones.
Service
Occurrence
High
2.3.152
SIP: Telephone Line LEDs are always On
Tracking No.
PROD00143846
Description
Impact
Telephone line 1 and 2 LEDs are always on even when

ifdminStatus for the line is set to down.
Service
Occurrence
Low
2.3.153
LEDs Do Not Correctly Indicate Protection Mode
Tracking No.
PROD00143257, PROD00144195
Description
Impact
When a line goes into protection mode, all LEDs blink except
for the power LED which stays solid. The expected pattern is
the LED for the line in protection should stay solid and all other
LEDs blinking.
Service
Occurrence
Low
58
2.3.154
DCC Fails When in DOCSIS 2.0 Mode on Certain
CMTS/Software
Tracking No.
PROD00139918
Description
Impact
DCC reinit techniques other than reinit-mac did not work in

some DOCSIS 2.0 fallback modes when using NON-ARRIS
CMTS/software. There was not an issue with ARRIS C4
CMTS.
Operational
Occurrence
High
2.3.155
No Error Messages for SDP with Incorrect Case
Tracking No.
PROD00143487
Description
Impact
E-MTA does not report errors when the SDP parameters

contain case errors, specifically when expected upper case
parameters are entered in lower case (SDP Case Sensitivity),
SDP is accepted.
Operational
Occurrence
High
2.3.156
Power Ring Frequency is Not Settable
Tracking No.
PROD00143489
Description
Impact
The power ring frequency was not settable via the config file
with pktcSigPowerRingFrequency MIB and was always 25 Hz.
Service
Occurrence
High
2.3.157
E-MTA Fails to Come On-line Due to MIB Ordering
in the MTA Configuration File
Tracking No.
PROD00144436, PROD00136833
Description
Impact
E-MTA does not come up on-line due to MIB ordering in the

MTA config file even through the ordering of the MIBs should
not matter.
Service
Occurrence
Low
59
2.3.158
pktcSigDevToneTable Changes are not Affecting
the Tone Playout
Tracking No.
PROD00144903
Description
Impact
The pktcSigDevToneTable MIBs could be set in the config file

but any changes were not correctly played out to the CPE.
Service
Occurrence
High
2.3.159
Incorrect Default Flash Timing
Tracking No.
PROD00138347
Description
Impact
The default flash timing was incorrectly set for the Netherlands
template.
Service
Occurrence
High
2.3.160
Active Call is Dropped during Recovery From 1x1
to 4x1
Tracking No.
PROD00143588
Description
Impact
When E-MTA attempts to recover from DOCSIS 2.0 (1x1) to

DOCSIS 3.0 (4x1) while a call is in progress, the call is
dropped.
Service
Occurrence
Low
2.3.161
Status Web GUI may Display Incorrect CABLE
State
Tracking No.
PROD00138812
Description
Impact
Status Web GUI may display CABLE state as Down even

though it is online.
Operational
Occurrence
Low
60
2.3.162
EURO: Apply Country Code Template Settings
before IETF Signaling MIB Adjustments
Tracking No.
Description
PROD00130897, PROD00144973, PROD00144912,

PROD00144978, PROD00144999, PROD00144974
When a country code template is included in the MTA
configuration file, its default settings (Tx/Rx levels, Ringing
Cadences, CallerID / VMWI mode, Power Ringing Frequency,
etc) should be applied before any customizations from the IETF
Signaling MIBs.
Impact
Service
Occurrence
High
2.3.163
Remote Ringback Level is Too Low
Tracking No.
PROD00145233
Description
The remote ringback level was 6dB too low for playout of
network tones towards the far-end endpoint.
Impact
Service
Occurrence
High
2.3.164
ipNetToMediaTable SNMP Query Does Not Work
Tracking No.
PROD00144584
Description
An SNMP MIBWALK of the ipNetToMediaTable failed to

return the correct values for the .2 (Cable) and .16
(PacketCable) interfaces on a GET operation.
Impact
Operational
Occurrence
High
2.3.165
MTA DHCP RENEW Fails when Missing BootP
Settings
Tracking No.
PROD00144375
Description
The E-MTA failed to correctly renew its MTA IP address

when the Bootp parameters were not included by the
provisioning server during the DHCP RENEW sequence. Per
specification, the Bootp file & server are optional for this case.
61
Impact
Service
Occurrence
High
2.3.166
Wrong Response to NCS Local Connection
Options
Tracking No.
PROD00143291
Description
Impact
Updated NCS error response codes to closer match the

recommended values for specific fault conditions.
Service
Occurrence
Rare
2.3.167
Incorrect Data in docsIfSigQUnerroreds MIB Value
Tracking No.
PROD00145379
Description
When queried via a BULK SNMP GET operation, the docsIf

SigQUnerroreds MIB returned a value that was not accurate.
Impact
Operational
Occurrence
High
2.3.168
SIP: Pulse Dial Dialing Does Not Work
Tracking No.
PROD00143517, PROD00144479
Description
Dialed digits were not recognized when using the pulse dialing
method. This problem only affected SIP provisioned units.
Impact
Service
Occurrence
High
2.3.169
SIP: E-MTA Does Not Provision When Lines are
OOS
Tracking No.
PROD00144418
Description
The E-MTA would not complete provisioning if the

ifAdminStatus for either line was set to down(2) in the config
file. This problem only affected SIP provisioned units.
Service
Impact
62
Occurrence
2.3.170
High
MTA MIB WALK Fails to Read Event MIB
Tracking No.
PROD00136535
Description
A MIBWALK initiated using the MTA IP address for the EMTA failed to correctly read the PacketCable Event MIB table.
This issue did not exist for MIBWALKs when using the CM IP
address.
Impact
Operational
Occurrence
High
2.3.171
ifAdminStatus.16 via CM Configuration File Not
Working Properly
Tracking No.
PROD00145058, PROD00145302
Description
Voice MTA functionality could not be controlled by setting the

ifAdminStatus.16 entry in the CM configuration file.
Impact
Service
Occurrence
Low
2.3.172
Config File Rejected When Telnet/SSH MIBs
Present Without TelnetPassword MIB
Tracking No.
PROD00145399
Description
The E-MTA would not complete DOCSIS registration if the

ARRIS Telnet or SSH enable MIBs were included in the CM
configuration file without the corresponding
arrisCmDoc30AccessTelnet Password MIB.
Impact
Service
Occurrence
High
2.3.173
Modem Takes Too Long to Recover on Cached
US Channel
Tracking No.
PROD00143873
Description
When the E-MTA failed to detect a ranging opportunity from
63
the CMTS during the initial ranging period, then an incorrect

value (too high) was used for the backoff timer algorithm.
Impact
Service
Occurrence
Low
2.3.174
Missing Battery Telemetry MIBs
Tracking No.
PROD00145281
Description
Added support for the following MIBs that were missing from
the previous firmware release:
i) arrisMtaDevEstimatedMinutesRemaining
ii) arrisMtaDevEstimatedChargeRemaining
iii) arrisMtaDevPwrSupplySecondsOnBattery
Impact
Operational
Occurrence
High
2.3.175
MTA Provisioning Fails When the Local Address
Portion Missing From callagentid
Tracking No.
PROD00145406
Description
Impact
TI made a change specifically for EURO to fail provisioning

when ca@ is missing from the callagentid mib.
Service
Occurrence
High
2.3.176
MTA Fail to Send a Wildcard RSIP after SNMP
Reset
Tracking No.
PROD00145305
Description
Impact
MTA did not send a wildcard RSIP after SNMP reset for all
endpoints that were managed by the same Notified Entity.
Service
Occurrence
High
2.3.177
SIP: MTA Fails Provisioning Due to MIBs with an
Incorrect Value in the MTA Configuration File
Tracking No.
PROD00145207
64
Description
Impact
Having a MIB with a bad or incorrect value in the MTA config

file will cause the MTA to fail provisioning when it still should
come up with Pass with Warnings.
Service
Occurrence
High
2.3.178
Disabled MTA Still Generates Telnet Debugging
Prints
Tracking No.
PROD00138809
Description
Impact
When the MTA has been disabled (using the ifAdminStatus

MIB), MTA DHCP error logs are still generated and printed to
the telnet session.
Operational
Occurrence
High
The following issues were resolved in release 7.1.44A
2.3.179
E-MTA Factory Yield Improvements
Tracking No.
PROD00143485
Description
Impact
This release of firmware includes fixes to improve the current

yield rate from the factory.
Factory
Occurrence
Low
2.3.180
Incorrect MIB Object Being Sent Up for MTA MAC
Address in MTA Enrollment Inform
Tracking No.
PROD00142334
Description
On an E-MTA with NA MTA MIBs, the

pktcMtaDevProvisioningEnrollment inform is sent up with the
MTA mac address contained in
pktcDevEvReportMacAddress.0. Per the MIB definition for
pktcMtaDevProvisioningEnrollment, the MTA MAC address
should actually be sent up in pktcMtaDevMacAddress.0.
65
Impact
Operational
Occurrence
High
2.3.181
Upstream QoS Classifiers May Not Work Properly
Tracking No.
PROD00142557
Description
Impact
If more than 8 Best Effort US flows are setup in the

configuration file, the upstream QoS classifiers are not enforced
and packets end up being sent up the wrong flow.
Service
Occurrence
Low
2.3.182
Link LED Does Not Flash
Tracking No.
PROD00141262, PROD00141527
Description
Impact
The link LED on the E-MTA does not flash when bridging data
if the packet processor is enabled.
Operational
Occurrence
High
2.3.183
Incorrect sysUptime Field in TRAP Messages
Tracking No.
PROD00132214
Description
Impact
The sysUptime field is not being populated correctly. After just

a few minutes, an Uptime of 245 days is displayed.
Operational
Occurrence
High
2.3.184
E-MTA Loses Downstream Sync After
backoffCounters Debug Command
Tracking No.
PROD00133110
Description
Impact
The modem will lose downstream sync when the

backoffCounters CLI command located on the 'co -> docsis ->
Fw' menu is issued. A modem reboot is required to clear the
issue.
Service
Occurrence
Rare
66
2.3.185
Call Processing Fails When Max Data Throughput
is Applied
Tracking No.
PROD00136585
Description
Impact
When bulk call traffic is setup with a maximum downstream

data rate of 150 Mbps (extrm_dn) and a maximum upstream
data rate of 15 Mbps, the call completion rate will drop
significantly.
Service
Occurrence
High
2.3.186
TM702B: Intermittent Permanent AUTH Reject
BPI Failures
Tracking No.
PROD00138061
Description
Impact
When registering using EURO BPI certificates on a specific

CMTS, the TM702B will sometimes receive a BPI
authorization failure upon initial installation. These units
require a reboot to complete BPI authorization.
Service
Occurrence
High
2.3.187
E-MTA Fails to Recover from RF Outage
Tracking No.
PROD00135300
Description
Impact
When the E-MTA is running in a bonded channel configuration,

the modem does not intermittently recover from RF outages
during a partial service scenario. A reboot action is required to
correct the issue.
Service
Occurrence
High
2.3.188
USB Connectivity Issue
Tracking No.
PROD00139023
Description
If a USB cable is already connected from the cable modem to

the PC when the cable modem is powered up or restarted, the
PC may have limited or no network connectivity. To resolve
this issue, the USB cable must be disconnected and
reconnected, preferably after the cable modem has ranged and
67
Impact
registered.
Service
Occurrence
High
2.3.189
Occasional DSP Reset Causes Extended Traffic
Run Issue
Tracking No.
PROD00138140
Description
During overnight traffic runs, occasional E-MTA DSP resets

have been observed on several units affecting overall traffic
completion rates. This results in a small traffic completion
issue while the E-MTA is resetting.
Impact
This release has improved performance in this area to reduce

the rate of occurrence over prior releases. See PROD00138458
in the RD section for more information.
Service
Occurrence
Rare
2.3.190
Extreme Robustness Testing Issue
Tracking No.
PROD00137299
Description
Impact
After the RF cut, the CM shows operational and CMTS shows

offline. A reboot of the E-MTA is required to recover the unit.
Service
Occurrence
Low
2.3.191
MIB docsifCMSTatusEqualizationData Cannot be
Polled
Tracking No.
PROD00142250
Description
Impact
The MIB Object, docsifCMSTatusEqualizationData, cannot be

polled to display pre-equalization data.
Operational
Occurrence
High
2.3.192
CPE MAC Address Provisioning In Configuration
File Not Supported
Tracking No.
PROD00135767
68
Description
Impact
When the CM is provisioned with a configuration file providing

a CPE MAC address, the MAC address isn't present in the
dot1dTpFdbTable MIB.
Service
Occurrence
Low
2.3.193
False T3 Event in Event Logs
Tracking No.
PROD00138314
Description
Impact
A false T3 event may appear in the event logs as a result of a

race condition on the E-MTA.
Operational
Occurrence
Low
2.3.194
Telnet/HTTP to CM IP Can Fail when Source
Verify Enabled
Tracking No.
PROD00142217, PROD00142201
Description
Impact
If Source Verify is enabled on the CMTS and the CM IP is

accessed from a different subnet than the one the CM is current
using, telnet and HTTP may not work using the CM IP address
after the MTA has completed provisioning.
Operational
Occurrence
High
2.3.195
Reject(na) state on CMTS with Secondary
Downstream Outage
Tracking No.
PROD00136329, PROD00142431
Description
Impact
Some CMTS releases will place modems into a permanent

reject(na) (na - not authorized) state if the REG-ACK is sent
containing a "partial service" confirmation code indicating that
one of the secondary downstreams could not be acquired.
Service
Occurrence
High
2.3.196
Status Page Shows Information for Non-DOCSIS
Signals
Tracking No.
PROD00140052
69
Description
Impact
The status page might show information for non-DOCSIS

signals in the plant. The modem is not using this downstreams
to receive data and it has no effect on operation. This problem
will only happen if the CM is not using all 4 tuners for DOCSIS
and there are other non-DOCSIS QAM signals in the plant.
Operational
Occurrence
High
2.3.197
Nonstandard "NULL" Value for DHCP Option 122
Suboption 3 Not Allowed
Tracking No.
PROD00142149
Description
Impact
Standard procedure for NULL value of option 122 suboption 3

is to disable MTA. GUPI & GupiEncrypted must allow an
empty value for the SNMP entity.
Service
Occurrence
High
2.3.198
DSX Transactions on an E-MTA May Fail Due to
Transaction ID
Tracking No.
PROD00142218
Description
Impact
The DSX transaction ID initiated from a CM has a valid range

of 0 to 32767. However, the DSX processing would error out
on a transaction ID of 0. A DSX transaction with an ID of 0
would fail causing the call attempt to fail. The next call attempt
would be successful due to the transaction ID incrementing past
0.
Service
Occurrence
Low
2.3.199
MTA Feature Switch MIB - MaxCpeBypass
Tracking No.
PROD00138938
Description
Impact
The previously supported DOCSIS 2.0 MIB, MaxCpeBypass, is

now enabled for DOCSIS 3.0 releases.
Operational
Occurrence
High
70
2.3.200
PacketCable1.5: Hybrid.2 Provisioning and
Secure Do Not Work
Tracking No.
PROD00140221, PROD00137757
Description
Impact
Hybrid.2 provisioning and North American secure provisioning

do not work at this time.
Operational
Occurrence
High
2.3.201
Automatic OSI Could Be Triggered During Dialing
Tracking No.
PROD00139066
Description
Impact
If the Automatic OSI feature is enabled, the OSI is triggered

when an off-hook line has its last connection deleted. The line
could be originating a call and the OSI would interrupt the
dialed digits in the case of a call server delete int. The initial
connection created to play dial tone would then get deleted.
Service
Occurrence
High
2.3.202
E-MTA Stores Partial MDD
Tracking No.
PROD00141419
Description
Impact
If the E-MTA received a partial MDD message and the change

count for the next MDD message was the same, the E-MTA
will continue to use the previously received MDD which may
contain stale information. This will result in the E-MTA
eventually registering in a D2.0.
Service
Occurrence
High
2.3.203
E-MTA Provisioning Failure if Mandatory US TLVs
Missing from CMTS
Tracking No.
PROD00139843
Description
Modem registration would previously fail in the CMTS was

missing mandatory US Ambiguity TLVs. This requirement has
been relaxed to support CMTS interoperability.
Service
Impact
71
Occurrence
High
2.3.204
Embedded RQNT and MDCX Messages with "to="
Parameter Rejected
Tracking No.
PROD00132860
Description
Impact
When an embedded RQNT or MDCX message is received with

the "to=" parameter, the message is rejected with an NCS 522
error message when it should be accepted and return a 200 OK
message.
Service
Occurrence
High
2.3.205
Dual Mode May Result in E-MTA Reset
Tracking No.
PROD00129968
Description
Impact
When an E-MTA configured for Annex A initially locks on to

Annex B downstream, the firmware will reboot once to switch
from Euro to NA BPI certificates. This issue does not occur in
the reverse direction.
Service
Occurrence
High
2.3.206
Duplicate TLV-11 Entries in the Configuration File
Tracking No.
PROD00126093
Description
Impact
Downloading a configuration file that contains duplicate TLV11 MIB entries causes the TLV parser to fail and the modem to
abort the registration process. A reboot is required to recover
the modem.
Service
Occurrence
High
72
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
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 E-MTA uses Test Root certificate by Default

Tracking No.
PROD00157826
Description
Impact
In this release of firmware, the E-MTA uses the test root

certificate by default instead of the root certificate. This only
affects Full PacketCable provisioning modes.
Service
Occurrence
High
Workaround
The certificate can be changed/updated on the provisioning

system or the E-MTA can be pointed to the root certificate
using the CLI.
3.1.2 Non TCP/UDP Packets may cause Modem Reboot

Tracking No.
PROD00157230
Description
A modem reboot may occur in denial of service scenarios when

the modem receives very high rates of non TCP or UDP traffic.
Impact
This behavior has been observed when the modem is receiving

a constant stream of 64 byte packets of type 0xFE (unknown) at
a rate of 50Mbps.
Service
Occurrence
Low
Workaround
None
73
3.1.3 SIP: MTA Provisioning may fail due to Server IP Address of

9.9.9.9
Tracking No.
PROD00157570, 157240
Description
Impact
Some provisioning methods may fail with an incorrect Server

IP or SNMP entity address of 9.9.9.0. This issue is limited to
SIP MTA provisioning.
Service
Occurrence
High
Workaround
Use of BASIC.1 provisioning method
3.1.4 SIP: GupiMAC Issues

Tracking No.
PROD00156155, PROD00156824
Description
Impact
The below issues are all related the SIP GupiMAC provisioning
methods.
PROD00156155: Option 122 suboption 6 is required to
successfully provision the MTA when using the
GupiMacMta provision method.
PROD00156824:
E-MTAs provisioning using
GupiMac may get stuck in Telephony TFTP following
an RF Cable Cut.
Service
Occurrence
High
Workaround
Option 122 suboption 6 must be defined in the DHCP options.
3.1.5 E-MTA drops Upstream Traffic

Tracking No.
PROD00155653
Description
Impact
On rare occasions during bulk traffic testing in the lab, ARRIS

has seen modems lose upstream communication on one of its
upstream flows. When this occurs, the modem gets in a state
where it does not see grants from the CMTS even though it
thinks it is requesting bandwidth.
Service
Occurrence
Rare
Workaround
None
74
3.1.6 PCMM Gate-Set Failure

Tracking No.
PROD00155553
Description
Impact
A PCMM Gate-Set Failure is observed when adding a fourth

MGPI grant to a UGS flow. This results in the modem not
responding to the DSC-REQ.
Service
Occurrence
High
Workaround
None
3.1.7 Data Only E-MTA will Still Place MTA in CPE Table
Tracking No.
PROD00153925
Description
Impact
If the E-MTA is provisioned as data only, no voice, the MTA

MAC address will be learned as a CPE.
So if the
MaxCPEAllow is set to 1, the end user CPE will not get an IP
address.
Service
Occurrence
High
Workaround
Increase the MaxCpeAllow MIB to 2 or set the following bit in

the ppCfgMtaFeatureSwitch to 0x00000002.
3.1.8 10Base-T Ethernet Traffic Issue

Tracking No.
PROD00154448
Description
Impact
Current releases of TS 7.1 may not pass data traffic across the
Ethernet port when traffic is negotiated to a speed of 10Base-T.
Service
Occurrence
Low
Workaround
None
3.1.9 Slower Registration Times

Opportunities
for
Broadcast
IM
Ranging
Tracking No.
PROD00153458
Description
Modems using Broadcast IM ranging opportunities for nonprimary US acquisition may observe slower registration times
and more instances of US partial-service.
75
Impact
Operational
Occurrence
High
Workaround
None
3.1.10
SIP: CallerID Information not Suppressed via RFC-3323
Privacy Header
Tracking No.
PROD00152940
Description
Impact
CallerID is not correctly suppressed when the

sipCfgSipFeatureSwitch is set to enable RFC 3323 privacy
header (0x08000000) for SIP INVITE messages.
Operational
Occurrence
High
Workaround
None
3.1.11
SIP: Fax Only Mode Timer may fail for Incoming Call
Tracking No.
PROD00152838
Description
Impact
When a SIP line is setup for Fax Only Mode, the fax time out
timer is started too early (when the INVITE message is
received) creating a situation where the timer can potentially
expire before MTA can answer the call.
Service
Occurrence
High
Workaround
None
3.1.12
SIP: Repeat Dialing may Result in No Ringback Tone
Tracking No.
PROD00152790
Description
Impact
When repeat dialing is activated, if the party being called goes

off-hook first ringback will not be heard.
Service
Occurrence
High
Workaround
None
76
3.1.13
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.
Operational
Occurrence
High
Workaround
None
3.1.14
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
attempts work fine.
Operational
Occurrence
Low
Workaround
Attempt the SSH login again.
3.1.15
SIP: Traps may not be sent to Trap Server
Tracking No.
PROD00151615
Description
Impact
When provisioned in Basic 1, Basic 2, Hybrid 1, or Hyrid 2

provisioning modes, events are logged to the Local Log and
SYSLOG but not the Trap server. For GUPI provisioning, traps
are correctly generated and forwarded to the Trap server.
Operational
Occurrence
High
Workaround
None
77
3.1.16
No Service Impact Upgrade not Delayed
Tracking No.
PROD00152386
Description
Impact
When the arrisMtaDevSwDnldNoSvcImpact MIB is enabled,

the E-MTA should not attempt the upgrade until all lines have
been on-hook for at least 30 seconds. Currently, the upgrade
occurs immediately after all line go on-hook.
Operational
Occurrence
High
Workaround
None
3.1.17
arrisMtaDevPwrSupplyDataShutdownTime can be Set
to Negative Value
Tracking No.
PROD00152332
Description
If the arrisMtaDevPwrSupplyDataShutdown MIB variable is set

to a negative value, then the modem will not shutdown data
services during an AC FAIL situation, resulting in reduced
battery holdup time.
Impact
Service
Occurrence
High
Workaround
None
3.1.18
ARRIS
Daylight
Savings
Time
Unsuccessfully Sets Daylight Savings Time
Policy
MIB
Tracking No.
PROD00151052
Description
ARRIS has identified a condition in which ARRIS Modems

will unsuccessfully set the Daylight Saving Time (DST) when
using the Daylight Saving Time (DST) MIB Policy rule to
adjust Daylight Savings Time on the Modem.
Impact
This issue is documented in AFB-10-301.

Service
Occurrence
High
Workaround
None
78
3.1.19
Extreme Robustness Testing Issues
Tracking No.
See Below
Description
Impact
The following rare issue is currently under investigation.

Service
Occurrence
Rare
Workaround
None
PROD00143438/PROD00150268/PROD00153002: A
DOCSIS 3.0 CM could register in 1x1 mode if an RF cut
occurs during the initial MDD message collection window.
This is a corner case issue.
3.1.20
TM722B: Downgrade to TS 7.0 may Cause Registration
Failure
Tracking No.
PROD00149429
Description
Impact
European-based TM722B hardware models should not be

downgraded to a TS 7.0 firmware release. This could result in
the E-MTA failing to re-range & register on the network after
the upgrade reset occurs.
Service
Occurrence
High
Workaround
None Affected units must be returned to ARRIS for upgrade
3.1.21
USB: Intermittent Connections with Windows 2000
Tracking No.
PROD00149390
Description
Impact
When using Windows 2000, an issue was noted where the USB
port appeared to inconsistently pass data. This issue was only
observed on the USB port.
Service
Occurrence
Rare
Workaround
Use the Ethernet connection for data service.
79
3.1.22
LC
Protection
pktcEnEndPntInfoTable
State
not
Reported
via
Tracking No.
PROD00146018
Description
The PacketCable method for reporting the presence of foreign

potential (LC Overcurrent Protection) is not supported. A walk
of the pktcEnEndPntInfoTable MIB object will return the
default values of NULL. The existing ARRIS MIB
ppSurvPortMaintState provides equivalent information, and
will show a state of istrbl-lcprt when foreign voltage is
detected on the line.
Impact
Operational
Occurrence
High
Workaround
None
3.1.23
S-CDMA: Impairment on Single US may Result in No
Data
Tracking No.
PROD00146544
Description
Impact
When impairments occur on a single S-CDMA upstream

channel when the modem is in a 4 x 4 configuration, the
modem stops passing data on all four channels. The modem
should continue to pass data on the channels with no
impairments.
Service
Occurrence
Low
Workaround
None
3.1.24
Station Maintenance may Cause US FEC Error
Tracking No.
PROD00146830
Description
When station maintenance occurs on frequency bonded

upstreams with high packet rates, FEC errors may be noticed on
the CMTS resulting in a very low rate of packet loss.
Impact
Operational
Occurrence
Low
80
Workaround
3.1.25
None
IPv6: RAs Being Forwarded to CPEs
Tracking No.
PROD00147349
Description
Impact
It has been observed that the modem is incorrectly forwarding

RAs to the CMCI when MDF is disabled. Per section G.4.3.2
of the MULPI spec, these multi-case packets should not be
forwarded to the IPv6 CPE devices.
Operational
Occurrence
High - When using IPv6 addresses
Workaround
None
3.1.26
SIP: Traffic is Below Baseline due to Off-Hook State
Tracking No.
PROD00148341
Description
Impact
During SIP bulk traffic testing, a problem has been observed

where the line card may become stuck in an off-hook state. An
E-MTA reset is required to recover the line.
Service
Occurrence
Low
Workaround
None
3.1.27
Ringing Waveform Setting Issues
Tracking No.
PROD00149278, PROD00149308
Description
Impact
When the arrisMtaDevEndPntRingingWaveform is set, the

waveform is not changed until after the modem is reset. For the
European modems, the modem will only output a trapezoidal
waveform regardless of this MIB setting.
Operational
Occurrence
High
Workaround
None
3.1.28
CAS/DTAS Tone Playout Duration Slightly Off
Tracking No.
PROD00130267
Description
During automated CallerID testing, the CAS/DTAS tone

duration had a measured variant of plus/minus 5 msecs from the
81
specified value of 85 msec.

Impact
Operational
Occurrence
Low
Workaround
None
3.1.29
Hash OID Last Entry in Configuration File
Tracking No.
PROD00131832
Description
Impact
For provisioning methods that require a hash OID entry, it must

be included as the very last line in the MTA configuration file.
Otherwise, a hash OID "mismatch" error will be returned and
the MTA will fail to provision correctly.
Service
Occurrence
High
Workaround
None
3.1.30
MTA Rejects DHCP Offers Without "next-server" Option
Tracking No.
PROD00131656
Description
Impact
A DHCP offer that does not include the next-server or has a

next-server value of "0.0.0.0" is rejected when it should be
allowed.
Service
Occurrence
Rare
Workaround
The DHCP offer needs to include a valid IP address for the

next-server.
82
3.2
Unsupported Features
The following features are not supported in the TS 7.1 release at this time.
3.3
ARRIS WAN Isolation Feature

PacketCable 1.5 Event Reporting Mechanism
Voice Payload Header Suppression
Silence Suppression and UGS/AD Service Flows
Voice Metrics Last 10 Call Logging (SIP)
RTCP-XR Remote Voice Quality Metrics Statistics (SIP)
Time of Day(TOD) Synchronization Feature to obtain TOD after registration
Upgrade Considerations
The following considerations are important to take into account when upgrading to this
firmware release.
CMTS Interoperability with US Channel Bonding

For customers deploying upstream channel bonding in their networks, the minimum
baseline for Touchstone is the TS 7.1 firmware release in combination with the CMTS
releases that support US Channel Bonding. Modems running below the Touchstone
baseline firmware, such as TS 7.0.78, will not register on a CMTS when upstream
channel bonding is enabled. The modems must be upgraded to TS 7.1 before the CMTS
feature for US Channel Bonding is deployed in the network.
CMTS Compatibility Issue with Bonded Downstream Channels

The E-MTA 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-SPMULPIv3_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.
TS 7.1 Firmware Release and C4 CMTS Compatibility

The TS 7.1 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.
TM722 and WBM760 Flash Re-Alignment Upgrade

In order to support future TM722 and WBM760 production, ARRIS implemented a flash
alignment change in TS 7.1.81 and WBM 3.2.48 release. This flash change applies to
TM722 and WBM760 only. Units upgraded to TS 7.1.81 or WBM 3.2.48 and later loads
83
should not be downgraded to an earlier version of firmware. The TM722 and WBM760
may reject any downgrade attempt made on them.
This one-time re-alignment of the flash may delay the recovery time for approximately 2
minutes. During that time, only the power LED will be ON. Once the units are upgraded
to the load, the duration of all future upgrades will not include the extra 2 minute delay.
Bootloader Upgrade
When units are upgraded to the TS 7.1.81 and later releases, the bootloader firmware will
be upgraded resulting in an extra one-time reboot of the EMTA, and will add
approximately 45 seconds to the upgrade process. The unit should not be powered down
during this process.
Web Page Modifications

In this releae of TS 7.1, the web pages have been setup to operate as in prior ARRIS
legacy releases with enhancements in the area of DOCSIS 3.0. Below are some of the
changes that may be noticed after upgrading to this release.
The DS Scanning override page will no longer be available after the E-MTA has
registered.
Status page has additional columns for downstream information.
Restored access to Loop Diagnostics via web page.
Added information on MDD IP mode.
Added links to view logging messages.
Restored VQM functionality.
IPSec Enabled
In this TS 7.1 release, the IPSec behaviour has changed to be enabled by default.
Default Flash Timing Change for SIP Netherlands Template

In the TS 7.1 release, the default hook-flash timing for the Netherlands template has been
changed to 88 - 1200 msec for SIP loads. The default for NCS is un-changed at 300 500 msec.
TM702 Hardware Revision

Earlier revisions TM702 prototype hardware may not fully support voice functionality,
and should not be deployed in the field. To confirm the revision of hardware, check the
Hardware Revision (HW_REV) field in the System Descriptor (sysDescr.0) field and
verify that the TM702 is hardware release 6.0 or higher.
84
Here is a sample sysDescr.0 string:

1: sysDescr.0 (octet string) ARRIS DOCSIS 3.0 / PacketCable 1.5 Touchstone Telephony
Modem <<HW_REV: 6.0; VENDOR: Arris Interactive, L.L.C.; BOOTR: 1.2.0.6;
SW_REV: 7.0.58; MODEL: TM702G>>
MTA DHCP Option 60 Modification

In order to maintain backwards compatibility with deployed MSO provisioning sytems,
the TS 7.X 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 TS 7.X firmware no longer support the use of CPS, SingleMAC,
PacketCableMinusKDC 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 TS 7.1 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 TS 7.1 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
SnmpMib
SnmpMib
=
=
=
=
=
=
=
=
docsDevNmAccessCommunity.1 "public"
docsDevNmAccessControl.1 read
docsDevNmAccessInterfaces.1 hexstr: 40
docsDevNmAccessStatus.1 createAndGo
docsDevNmAccessCommunity.2 "private"
docsDevNmAccessControl.2 readWrite
docsDevNmAccessInterfaces.2 hexstr: 40
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.
85
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 TS 7.1 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:
TS 6.1)
CallP Feature Switch Modifications

The TS 7.1 release has modified the values for the CallP Feature Switch to remove
deprecated feature switches as well as to group common elements together. Below is a
listing of the disabled feature switches.
0x20000000:
0x10000000:
0x08000000:
0x01000000:
0x00800000:
0x00400000:
0x00100000:
0x00080000:
0x00010000:
0x00008000:
0x00004000:
0x00001000:
0x00000800:
0x00000100:
0x00000080:
0x00000040:
0x00000008:
0x00000002:
0x00000001:
Allow MTA to automatically generate OSI

Delay DLCX response against connection on onhook only line (for VMWI)
Use alternate (non sequential) Caller ID delivery order
Send dtmf digits via RFC2833 with payload 101 without request
Add brackets to IP for MTA FQDN when communicating with call server
Allow NCS Redirect without IPsec
Disable RTP/RTCP authentication/encryption (bit = 0)
LUCENT RFC-2833 messaging without request using payload 94
Payload Header Suppression
Disable endpoint from sending provisional responses
DSX (access only) DQoS
NUERA RFC-2833 messaging without request using payload 127
Force the use of DQoS. Reject service if not used
Omit capability parameters in returned SDP
Omit mptime parameter in returned SDP
Apply auto OSI to both originating and terminating side for NCS calls
Reduce the capability descriptor in the SDP to T38 only
Prevent endpoint from entering the Lockstep quarantine mode
Prevent piggybacked transmissions of NCS messages
The default value for this feature switch is: 0x0.
Fixed Line Card and DSP Settings

For the TS 7.1 release, the following values are fixed and can not be changed
Ringing Waveform is fixed to Sinusodial for North America and Trazodial for
Europe.
Loop Current is set as Boost Mode (40 mA)
The Echo Canceller is set to 32 msec
86
CLI Command Changes

The TS 7.X release introduced a new CLI structure for troubleshooting the ARRIS
TM702/TM722 E-MTA and WBM750/760. 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.
87
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)
8:00 a.m. to 8:00 p.m. EST
Office Hours
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)
Korea Seoul
Email
techsupport.asia@arrisi.com
Telephone
+82 2 6007 2880
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.
88
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
CW69 ECNs
I10
I01
I08
I10
I09
CW69 ECNs
I04
I03
I03
I03
I01
I04
I03
Documentation Links:
http://www.cablemodem.com/specifications/specifications30.html
http://www.packetcable.com/specifications/specifications15.html
89
Touchstone
Telephony Firmware
Release 7.1.98
Release Notes and
Letter of Operational
Consideration
Copyright @2010 ARRIS International, Inc.

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

TS 7.1.98-Rnloc - 1.0

Uploaded by

Copyright:

Available Formats

You might also like

TS 7.1.98-Rnloc - 1.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TS 7.1.98-Rnloc - 1.0

Uploaded by

Copyright:

Available Formats

Touchstone

Touchstone Telephony Firmware

Initial Draft, v0.1

OBJECTIVES OF THIS DOCUMENT _____________________________ 1

NEW PRODUCT FEATURES _________________________________________ 4

LETTER OF OPERATIONAL CONSIDERATIONS __________________ 73

RELEASE NOTES ____________________________________________ 4

ARRIS COMMITMENT ____________________________________________

OPERATIONAL CONSIDERATIONS ___________________________________ 73

CUSTOMER SERVICE AND SUPPORT __________________________ 88

APPENDIX A: COMPLIANCE MATRIX ______________________________ 89

Touchstone Telephony Firmware - Release 7.1.98

1 Objectives of This Document

1.2 Purpose and Scope of This Document

1.3 Product Identification and Purpose of Release

Maintenance Supplemental Upgrade (MSUP) 6 - TS 7.1.98

Maintenance Supplemental Upgrade (MSUP) 6

Network-Based Call Signaling (NCS)

Release Notes & Letter of Operational Consideration

Touchstone Telephony Firmware - Release 7.1.98

1.4 Firmware Filename Variant Information

North America signed firmware image

European signed firmware image

Supports TM7XX models (TM702, TM722)

1.5 Minimum Firmware Baseline for Hardware

WBM030112_101408 (WBM 3.1.12)

WBM030214_032609 (WBM 3.2.14)

WBM030214_032609 (WBM 3.2.14)

WBM030214_032609 (WBM 3.2.14)

Release Notes & Letter of Operational Consideration

Touchstone Telephony Firmware - Release 7.1.98

1.6 Product Documentation

Release Notes & Letter of Operational Consideration

Touchstone Telephony Firmware - Release 7.1.98

New Product Features

Out of Range (OOR) Threshold Change

Automatic OSI Feature Switch Update

Release Notes & Letter of Operational Consideration

Touchstone Telephony Firmware - Release 7.1.98

Loop Reversal Control

Call Waiting Repeat Indefinitely

WBM Load Support

(for the TM702/722)

SIP: Early Transmission of RTP Media upon 180 Messages

Release Notes & Letter of Operational Consideration

Touchstone Telephony Firmware - Release 7.1.98

SIP: Provisioning Method GUPI MAC Supported

Advanced Web Page Login Access Control

MIB Object to Invert Current LED Behavior

Persistent Line Status Feature

Endpoint Dialing Method Persistent Feature

Release Notes & Letter of Operational Consideration

Touchstone Telephony Firmware - Release 7.1.98

Transmit and Receive Gain Control Setting per Line

MDD Override Functionality

North American PacketCable Support for Euro-DOCSIS units

Ability to Suppress FQDN and IP Address in Event Logs

Release Notes & Letter of Operational Consideration