TS 7.1.109-Rnloc 1.0

Touchstone
Telephony Firmware

Release 7.1.109

Release Notes and
Letter of Operational
Considerations

Touchstone
Telephony Firmware

Release 7.1.109

Release Notes and
Letter of Operational Considerations
Document release Release 1.0
Document date April 15, 2011

2011 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

April 11, 2011
April 15, 2011
Initial Draft, v0.1
Approver Comments Added, v1.0

Table of Contents

1 OBJECTIVES OF THIS DOCUMENT _____________________________ 1
1.1 ARRIS COMMITMENT ____________________________________________ 1
1.2 PURPOSE AND SCOPE OF THIS DOCUMENT _____________________________ 1
1.3 PRODUCT IDENTIFICATION AND PURPOSE OF RELEASE ___________________ 1
1.4 FIRMWARE FILENAME VARIANT INFORMATION _________________________ 2
1.5 MINIMUM FIRMWARE BASELINE FOR HARDWARE _______________________ 2
1.6 PRODUCT DOCUMENTATION _______________________________________ 3
2 RELEASE NOTES ___________________________________________ 4
2.1 NEW PRODUCT FEATURES _________________________________________ 4
2.2 RESOLVED FIELD BULLETIN(S) ____________________________________ 16
2.3 RESOLVED PRODUCT DEFICIENCIES _________________________________ 17
3 LETTER OF OPERATIONAL CONSIDERATIONS _________________ 93
3.1 OPERATIONAL CONSIDERATIONS ___________________________________ 93
3.2 UNSUPPORTED FEATURES ________________________________________ 97
3.3 UPGRADE CONSIDERATIONS ______________________________________ 97
4 CUSTOMER SERVICE AND SUPPORT_________________________ 103
APPENDIX A: COMPLIANCE MATRIX ____________________________ 104
Touchstone Telephony Firmware - Release 7.1.109
Release Notes & Letter of Operational Consideration 1

1 Objectives of This Document
1.1 ARRIS Commitment
ARRIS is committed to developing high quality, value-added products and services to the
Multiple System Operator (MSO). ARRIS continually strives toward meeting our
customers needs with solutions that will help achieve their business objectives.
1.2 Purpose and Scope of This Document
This document describes the value-added features and anomaly resolutions associated
with this release. It also informs operators of known Operational Considerations
associated with this product release that have been identified either through ARRIS
testing or field operations.
1.3 Product Identification and Purpose of Release
Described in this document is the Touchstone Telephony Firmware. This Touchstone
Firmware release is intended for ARRIS manufactured E-MTAs. Information pertaining
to support for this specific release is detailed in the table below. Not all configurations
and hardware variants are supported with each release.

Product Description Maintenance Supplemental Upgrade (MSUP) 8 - TS 7.1.109
Validation Sequence Maintenance Supplemental Upgrade (MSUP) 8
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 TS0701109_040611
SysDescriptor SW_REV: 7.1.109
PacketACE DOCSIS 3.0 PacketACE Release 3.11 or later

1.4 Firmware Filename Variant Information
The table below presents the filename extensions used on Touchstone products. Not all
variants of a load are created for a release.

FILENAME EXTENSION PURPOSE OF EXTENSION
_NA North America signed firmware image
_EU European signed firmware image
MODEL_7 Supports TM7XX models (TM702, TM722)
WBM_7 Supports WBM7XX models (WBM750, WBM760)
SIP Session Initiation Protocol (SIP) firmware image
MAC14 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.109
Ability to Keep CPE MAC after Disconnect
In this release, a MIB arrisCmDoc30SetupKeepCpeOnIfDisconnect is added for
controlling this functionality. When the MIB is set to enable (1), CPEs MAC address
will be kept in the CPE MAC learning table after the CPE is disconnected. The MAC
address will be deleted from the table if the MIB is set to disable (0) which is the default
setting.

Added in TS 7.1.103
SIP: Provisioning Method GUPI Encrypted MAC MTA Supported
A new provisioning method, gupiEncryptedMacMta, is now available for SIP loads. This
is identical to GUPI MAC MTA provisioning, with support for decrypting the encrypted
provisioning file. This provisioning method can only be selected from the
arrisMtaDevProvMethodIndicator.

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 (for the TM702/722)
TS070189_012710_NA.WBM_7.img (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).
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
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, arrisCmDoc30SetupDSTPolicy,
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.
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 re-
initialize 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.
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 Protocol-
Extended 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.


2.2 Resolved Field Bulletin(s)
The following field bulletin issues were resolved in this Touchstone firmware release or
previous firmware releases.

Field Bulletin
Number
Field Bulletin Title
Product Defect
Number
AFB-10-0307 ARRIS DOCSIS 3.0 E-MTAs Which Experience Multiple T4
Timeouts Prematurely Drop Calls
PROD00158727
AFB-10-0306 ARRIS DOCSIS 3.0 E-MTA Certificate Failure with Secure
Provisioning
PROD00156134
AFB-10-0303 MTA Initiated Call Progress Tones May Cease After 2 Cycles of
Cadence
PROD00153547,
PROD00153541
AFB-10-0302 ARRIS Daylight Savings Time Policy MIB Unsuccessfully Sets
Daylight Savings Time on ARRIS Modems
PROD00150934
PROD00151052
AFB-10-0301 ARRIS DOCSIS 3.0 Potential Registration Issue with US Channel
Bonding
PROD00151896
AFB-09-0308 ARRIS DOCSIS 3.0 Modems May Intermittently Fail to Register
in Bonded Mode
PROD00146737
AFB-09-0312 ARRIS DOCSIS 3.0 Potential Upgrade Issue PROD00147348,
PROD00148288


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.
Considerations that apply to a specific feature implementation will designed with one of
the following prefixes included in the heading:

SIP: SIP Signaling Protocol
NCS: NCS Signaling Protocol
T.38: T.38 Feature Specific Issue
SSH: Secure Shell
LVM: Loop Voltage Management

The following issues were resolved in release 7.1.109

2.3.1 MTA provisioning executed twice for GUPI provisioning
Tracking No. PROD00161010
Description When using a GUPI provisioning method the MTA
provisioning may be executed twice the first time the modem
registers.

Impact Operational
Occurrence High
2.3.2 arrisMtaDevPktcDevEvEndpointName MIB issue
Description arrisMtaDevPktcDevEvEndpointName MIB does not return a
value.
Impact Operational
Occurrence High

2.3.3 Remote Metric MIB arrisMtaDevVqmEnableRemote
settings are not persistent.
Description arrisMtaDevVqmEnableRemote MIB changes are now
persistently stored across power cycles.
Impact Operational
Occurrence High
2.3.4 SIP: Caller ID not displayed correctly when only TEL
URI is present
Description No Caller ID number is displayed when only TEL URI is
present in the SIP Invite message.
Impact Service
Occurrence High
2.3.5 sipCfgProvisionedCodecArray fails to accept G729E
Description When a Codec that requires a dynamic payload type is
provisioned in the sipCfgProvisionedCodecArray the payload
type generated in the offer is not a valid value.
Impact Service
Occurrence High
2.3.6 arrisMtaDevProvState MIB issue
Description The arrisMtaDevProvState MIB was not accessible. This MIB
has been added and provides the current state during the
provisioning process. See PROD00168642 in the
Considerations section for limitations.
Impact Service
Occurrence High

2.3.7 Upstream Load Balancing does not work properly
Description If the CMTS sends incorrect information on the MTC and MRC
TLVs the modem will reject the UCC-REQ message even in
1x1 configurations.
Impact Service
Occurrence High
2.3.8 E-MTA does not send Option 122 in the renew request
Description The D3.0 E-MTA was not requesting Option 122.1 in the CM
DHCP renew request.
Impact Service
Occurrence High
2.3.9 arrisCmDevRegistrationState does not return a value
Description arrisCmDevRegistrationState mib walk fails to return the
registration state. arrisCmDoc30SwRegistrationState MIB has
been added to support DOCSIS 3.0 modems.
Impact Operational
Occurrence High
2.3.10 SIP: EURO Prefix Missing on SysDescr
Description The SysDescr is missing the EURO designation.
Impact Operational
Occurrence High
2.3.11 LVM: Policy 3 reset timer does not reinitialize to the
default value

Description When the LVM policy is set to 3 and the reset timer,
pktcEnNcsEndPntLVMgmtResetTimer, is set, the timer will
start to count down once the MTA starts to reset. However,
after the MTA returns to service, the reset timer does not
reinitialize but continues to count down upon the next loss of
loop voltage.
Impact Service
Occurrence High
2.3.12 MTA may fail to detect DTMF digits with a positive twist
value greater than 4 dB
Description When using certain CPEs with a positive twist greater than 4
dB, difference in power between the two frequencies of a
DTMF signal, MTA may fail to detect all the digits. Please
note that DTMF positive twist greater than 4 dB is out of
specifications.
Impact Service
Occurrence High
2.3.13 SIP: E-MTA may lose Registration with the Proxy
Description There have been occasions where the SIP MTA no longer sends
the required periodic registrations to the proxy. There is an
internal timer on the MTA that determines the time before
sending the next registration request. Failed cases show this
timer being set to a very large number. A reset of the MTA is
required to recover the registration.
Impact Service
Occurrence Rare
2.3.14 DCC DS/US move may fail in 1x1 Configuration
Description CM may reject DCC messages when CMTS sets the Multiple
Receive Channel (MRC) TLV to a non-zero value on 1x1
configurations.
Impact Service

Occurrence Low
2.3.15 arrisMtaDevProvMethodIndicator issue with BASIC.2
Description CM did not ignore the arrisMtaDevProvMethodIndicator when
set to ARRIS BASIC.2 which caused registration failures.
Since DOCSIS 3.0 does not support ARRIS BASIC.2, CM
should ignore and default to PacketCable BASIC.1.
Impact Service
Occurrence High
2.3.16 arrisCmDoc30SwServerAddress implemented
incorrectly
Tracking No. PROD00156028, PROD00162130
Description arrisCmDoc30SwServerAddress MIB walk would return the
value in ASCII format instead of octet string which is required
for InetAddress.
Impact Operational
Occurrence High
2.3.17 Registration failures after DCC with S-CDMA bonded
upstreams
Description When testing DCC with the S-CDMA modulation profile, MTA
may fail to register on the new downstream, resulting in T4s
and re-registration to the original downstream.
Impact Service
Occurrence High
2.3.18 Incorrect Australian Ring Cadence
Description The default ring cadence values for Australia country code
template were incorrect.

Impact Service

Occurrence High
2.3.19 arrisCmDoc30SwServerAddress in string format causes
registration failure
Description Modem in IPv4 failed to register with CMTS when the
arrisCmDoc30SwServerAddress field was in string format
instead of an InetAddress.
Impact Service
Occurrence High
2.3.20 CM does not handle TLV43 properly in the configuration
file
Description Modem failed to handle TLV43 encode for ARRIS Vendor
Specific MIBs in the CM configuration file.
Impact Operational
Occurrence High
2.3.21 CM State Webpage may incorrectly display DHCP
status
Description CM State tab on the modem WebGUI may incorrectly display
DHCP status as Completed even when DHCP is still in
progress.
Impact Operational
Occurrence High
2.3.22 North America Tone Template Issue
Description For NA tone templates outside of the default NA33 plan, a tone
conversion issue may exist. This can result in impacts to the
NA dial tone resulting in a short stutter after the initial 5
seconds of dial tone.
Impact Service

Occurrence Low
2.3.23 CAS/DTAS Tone Playout Duration Slightly Off
Description During automated CallerID testing, the CAS/DTAS tone
duration had a measured variant of plus/minus 5 msec from the
specified value of 85 msec. No fix planned.
Impact Operational
Occurrence Low
2.3.24 Hash OID Last Entry in Configuration File
Description 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. No fix planned.
Impact Service
Occurrence High
2.3.25 MTA Rejects DHCP Offers Without "next-server" Option
Description 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. No fix planned.
Impact Service
Occurrence Rare
2.3.26 Ringing Waveform Setting Issues
Description 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.
Impact Operational

Occurrence High
2.3.27 SIP: Traffic is Below Baseline due to Off-Hook State
Description 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.
Impact Service
Occurrence Low
2.3.28 IPv6: RAs Being Forwarded to CPEs
Description 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.
Impact Operational
Occurrence High - When using IPv6 addresses
2.3.29 Station Maintenance may Cause US FEC Error
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
2.3.30 S-CDMA: Impairment on Single US may Result in No
Data
Description 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.

Impact Service
Occurrence Low
2.3.31 TM722B: Downgrade to TS 7.0 may Cause Registration
Failure
Description 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.
Impact Service
Occurrence High
2.3.32 USB: Intermittent Connections with Windows 2000
Description 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.
Impact Service
Occurrence Rare
2.3.33 ARRIS Daylight Savings Time Policy MIB
Unsuccessfully Sets Daylight Savings Time
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.

This issue is documented in AFB-10-0302.
Impact Service
Occurrence High

2.3.34 arrisMtaDevPwrSupplyDataShutdownTime can be Set
to Negative Value
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
2.3.35 No Service Impact Upgrade not delayed
Description 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.
Impact Operational
Occurrence High
2.3.36 Voice Quality Metric Issues
Tracking No. See Below
Description The following issues are all related to the ARRIS VQM feature.

PROD00152561: The arrisMtaDevVqmThresholds
MIB does not report an error on the MIB browser after
setting an invalid value.
PROD00152388: If the arrisMtaDevVqmThresholds
MIB is set during a call, the syslog is not generated.
PROD00152270: The MIB
arrisMtaDevVqmCallNumberIdentifier will not be
updated to point to the last call location.
Impact Operational
Occurrence High

2.3.37 10Base-T Ethernet Traffic Issue
Description 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.
Impact Service
Occurrence Low
2.3.38 Data Only E-MTA will Still Place MTA in CPE Table
Description 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.
Impact Service
Occurrence High
2.3.39 Extreme Robustness testing issue(s) under investigation
Description PROD00158378: An RF cut during modem registration
may cause CPE device to temporarily stop receiving
data packets.
PROD00160070: During extreme RF tests, some calls
may fail with no dial tone.
Impact Service
Occurrence Rare
2.3.40 SIP: T.38 Call Failure
Description When placing a call using T.38, the first call failed due to E-
MTA incorrectly using the wrong active call-leg.
Impact Service
Occurrence Low

2.3.41 Euro Post Provisioning Issue
Description The pktcNcsEndPntConfigCallAgentId MIB object is not
available to be set or changed in the MTA post-provisioning.
No Fix Planned.
Impact Service
Occurrence High
2.3.42 CM in IPv6 Mode may ignore DHCP advertise message
Description Some DHCP servers include a status code of NoAddrAvailable
in the advertise message. This will cause the CM to ignore the
advertise message and not complete DHCP properly.
Impact Service
Occurrence High


2.3.43 Active call may drop due to remote call metrics data
Description Active call may drop if there is a party on hold during 3WC or
Call-Waiting. This may occur on certain call-management-
servers when Remote Voice Metrics are enabled and any end of
call stats value contains a + or > symbol.
Impact Service
Occurrence Medium
2.3.44 SIP: E-MTA may lose Registration with the Proxy
Description There have been occasions where the SIP MTA no longer sends
the required periodic registrations to the proxy. There is an

internal timer on the MTA that determines the time before
sending the next registration request. Failed cases show this
timer being set to a very large number. A reset of the MTA is
required to recover the registration.
Impact Service
Occurrence Rare
2.3.45 One-way Audio issue with Trunking IAD
Description E-MTA when used with trunking IAD, one-way audio was
observed on the 27
th
call.
Impact Service
Occurrence Rare
2.3.46 E-MTA May Fail to send CM-STATUS Message
Description E-MTA fails to send CM-STATUS message to the CMTS when
a loss of MDD is detected in a secondary channel.
Impact Service
Occurrence Low
2.3.47 DHCP option 61 client identifier not specification
compliant
Description The format of client identifier option was not compliant with
the requirement in RFC3315 and RFC4361.
Impact Service
Occurrence Rare
2.3.48 E-MTA resets due to control characters or spaces in the
configuration file name
Description E-MTA was hitting an exception and resetting during TFTP of
the configuration file due to either control characters (i.e. \r) or
spaces present in the file name.

Impact Service
Occurrence High
2.3.49 DocsDevFilterIpTosMask MIB overwrites
docsDevFilterIpTos
Description Setting the docsDevFilterIpTosMask to a non-zero value in the
configuration file does not take effect. Instead it overwrites the
docsDevFilterIpTos value.
Impact Service
Occurrence High
2.3.50 SIP: GUPI MAC Issues
Tracking No. See below.
Description 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.
PROD00158048: E-MTAs provisioning using
GupiMac may get stuck in Telephony TFTP following
an RF Cable Cut.
Impact Service
Occurrence High
2.3.51 arrisCmDoc30DhcpCmIpAddr implemented incorrectly
Description arrisCmDoc30DhcpCmIpAddr MIB walk would return the
value in ASCII format instead of octet string which is required
for InetAddress.
Impact Operational
Occurrence High
2.3.52 Extreme Robustness Tesing Issues

Description 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.

This issue was due to CMTS limitations.
Impact Service
Occurrence Rare
2.3.53 E-MTA drops Upstream Traffic
Description 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.

This issue was never reproduced.
Impact Service
Occurrence Rare
2.3.54 Call Progress Tone may not default to correct value
Description Call progress tone were not correctly set to the default values
for the country that is provisioned in
ppCfgMtaCountryTemplate.
Impact Service
Occurrence High
2.3.55 TFTP download retry mechanism issue
Description During an upgrade TFTP process, eMTA could result in
sending endless TFTP read requests if a download fails.
Impact Service
Occurrence Low

2.3.56 LVM: Web GUI displays incorrect maintenance timer
value
Description LVM Maintenance Timer under the Advanced product details
Web page always show 0 minutes.
Impact Operational
Occurrence High
2.3.57 LVM: Policy 3 Loop Voltage Removal
Description On LVM policy 3, loop voltage may be removed approximately
30 seconds after a reset when the eMTA is in bonded upstream
mode even if a valid reset or maintenance timer setting is in
place.
Impact Service
Occurrence High
2.3.58 CM-STATUS Inter operability issues with options
Description During QAM/FEC Recovery events, CM-STATUS messages
were including downstream information for all previously
recovered downstreams.
Impact Service
Occurrence High
2.3.59 E-MTA with extended registration times
Description An issue has been identified where an upstream redirect leads to
a modulation profile change where IUCs are different could
cause eMTA to take a longer period of time to register.
Impact Service
Occurrence Rare

2.3.60 Non TCP/UDP Packets may cause Modem Reboot
Description A modem reboot may occur in denial of service scenarios when
the modem receives very high rates of non TCP or UDP traffic.
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.
Impact Service
Occurrence Low
2.3.61 DTMF event ascending not working
Description DTMF Event Ascending failed to work on DOCSIS3.0 releases.
arrisMtaDevDTMFEndEventForceAscending MIB object has
now been added to TS7.1 releases.
Impact Operational
Occurrence Low
2.3.62 resetMTA does not clear line gain control settings
Description The arrisMtaDevEndPnt MIBs are not set back to the default
value (or persistent NVM value) upon an MTA reset.
Impact Operational
Occurrence High
2.3.63 Classifiers are not deleted
Description After a T4, the classifiers were not getting deleted throughout
the firmware. As a result, the classifiers list continually
expanded increasing the number of elements that had to be
traversed during classification.

This issue is documented in AFB-10-0307
Impact Service

Occurrence Low
2.3.64 Traffic Interruption due to Exceptions
Description Occasional interruptions in traffic have been observed during
traffic testing due to firmware exceptions causing eMTA to
reset.
Impact Service
Occurrence Rare
2.3.65 OOR Condition due to CPE Clearing
Description It is possible that there is a period of time after the CPE behind
the modem becomes inactive or lost, the packet sequence
numbers become out of sync between the CMTS and the CM.
If a DS traffic session destined to the CPE remains active, it
could cause the OOR condition on the DSID. SNMP access,
pings to the CM IP address, and data traffic will fail until the
modem is recovered from the OOR condition.
Impact Service
Occurrence High
2.3.66 Line Card state MIB returns IDLE for unprovisioned lines
Description In TS7.1 DOCSIS3.0 releases, arrisMtaDevLineCardState MIB
will return a value of IDLE (1) for unprovisioned lines.
Previously, DOCSIS2.0 releases would return a value of (0)
which is Out Of Service. The 0x4 callp feature bit in the
ppCfgMtaCallpFeatureSwitch is now supported in TS7.1
releases the ability for the MSO to configure the eMTA to
return a value of (0) for unprovisioned lines.
Impact Operational
Occurrence Low

2.3.67 SIP: MTA Provisioning may fail due to Server IP
Address of 9.9.9.9
Tracking No. PROD00157570, PROD00157240, PROD00159011
Description Some provisioning methods may fail with an incorrect Server
IP or SNMP entity address of 9.9.9.9. This issue is limited to
SIP MTA provisioning.
Impact Service
Occurrence High
2.3.68 E-MTA uses Test Root certificate by Default
Description In this release of firmware, the E-MTA uses the test root
certificate by default instead of the real root certificate. This
only affects Full PacketCable provisioning modes.

This issue is documented in AFB-10-0306
Impact Service
Occurrence High
2.3.69 SDP Payload may cause Bandwidth Error
Description A call from an IMS subscriber to an ARRIS NCS subscriber
may result in a 510 Protocol Error on the ARRIS E-MTA. The
root cause is in the SDP payload when the bandwidth
information "b=AS:X" and "b=TIAS:Y" are both present.
Impact Service
Occurrence High
2.3.70 PCMM Gate-Set Failure
Description A PCMM Gate-Set Failure is observed when adding a fourth
MGPI grant to the UGS flow. This results in the modem not
responding to the DSC-REQ.
Impact Service

Occurrence High
2.3.71 LVM: Policy 3 loop voltage removal
Description On LVM policy 3, loop voltage may be removed approximately
30 seconds after the RF cable is cut when the MTA is in bonded
upstream mode even if a valid reset or maintenance timer
setting is in place.
Impact Service
Occurrence High


2.3.72 NVM Flag Setting Issue on TS 7.1.97
Description 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.
Impact Service
Occurrence High
2.3.73 Bulk Traffic Testing Original Failure
Description 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.
Impact Service
Occurrence Low

2.3.74 LED Issue after Firmware Upgrade
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
operational during this time.

This issue was only observed in the ARRIS lab using an
unsigned image and causing an upgrade failure.
Impact Operational
Occurrence Low
2.3.75 Firmware Upgrade Failure not Logged in Event Logs
Description An issue was identified where a firmware upgrade failure was
not noted in the event logs.
Impact Operational
Occurrence High
2.3.76 SW Version in DHCP Option 43 may not be Correctly
Reported
Description 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.
Impact Operational
Occurrence High
2.3.77 IPv6: Bootfile not null-terminated
Description 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.
Impact Operational
Occurrence High
2.3.78 SDP Capability to Suppress T.38
Description 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.
Impact Service
Occurrence High
2.3.79 ILEC Ringing and Power Induction/Cross Testing may
Damage Line Card
Description 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.
Impact Service
Occurrence High
2.3.80 SIP: Restrict Incoming CODEC Offer not Supported
Description 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.
Impact Service
Occurrence High

2.3.81 arrisCmDevResetReasonLog not Supported
Description In prior releases of firmware, the SNMP MIB Object
arrisCmDevResetReasonLog was not supported. When polled,
this MIB would report a value of 0.
Impact Operational
Occurrence High
2.3.82 Packets Discarded as OOR after Unplugging CPE
Description When a CPE device was unplug during throughput testing,
some packets were incorrectly being discarded as Out of Range
(OOR).
Impact Service
Occurrence High
2.3.83 CM-STATUS Message for OOR may not be Sent
Description An issue was observed where the modem was only sending the
CM-STATUS message after the first reported Out of Range
scenario.
Impact Service
Occurrence High
2.3.84 Voice Mail Waiting Indicator not consistent on some
LCS systems
Description 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)).
Impact Operational
Occurrence Low

2.3.85 E-MTA Reboots Dropping Call Waiting Call
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.
Impact Service
Occurrence High
2.3.86 TEL LED Flashing when Telephone is on-hook
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.

This issue as being resolved as no fix planned.
Impact Operational
Occurrence High
2.3.87 ATDMA DCC may cause No Dial Tone
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.

This issue can no longer be reproduced and is being resolved.
Impact Service
Occurrence Rare
2.3.88 Extreme Robustness Testing Issues

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.

This issue can no longer be reproduced and is being resolved.
Impact Service
Occurrence High
2.3.89 Enhanced Firmware Download Events not Sent to
Syslog
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.

This issue is being closed as no fix planned.
Impact Operational
Occurrence High


2.3.90 Source Verify Errors Detected on CMTS
Description 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.
Impact Service
Occurrence Rare

2.3.91 USB Device Address is 0.0.0.0
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.
Impact Operational
Occurrence High
2.3.92 Unrecognized OID may cause Exception
Description 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.
Impact Service
Occurrence Rare
2.3.93 Send Early Media without 100rel Requirement no
Longer Includes SDP in 180
Description 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.
Impact Service
Occurrence High
2.3.94 Country Template does not Default to North American
3/3 after E-MTA reset
Description ppCfgMtaCountryTemplate MIB defaults to NA-57 instead of
NA-33 after an E-MTA reset.
Impact Service
Occurrence High

2.3.95 Ring Back Tone May Cease after 2 Rings for on-net
Calls Originated from the TM722
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
by this issue.

This issue is documented in AFB-10-0303.
Impact Service
Occurrence High
2.3.96 SIP: Caller ID Time Displayed Wrong Time on CPE
devices
Description 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.
Impact Operational
Occurrence High
2.3.97 IPv6: LLC Filter Default Actions not reset after T4
Description 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.
Impact Service
Occurrence High
2.3.98 arrisMtaDevMaxCPEAllowed and
arrisMtaDevNetworkAccess MIBs do not Return a Value

Description When performing an SNMP walk of the below MIB Objects, no
value was returned.

arrisMtaDevMaxCPEAllowed
arrisMtaDevNetworkAccess
Impact Operational
Occurrence High
2.3.99 BPI Registration Failures
Description 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.
Impact Service
Occurrence Rare
2.3.100 Mu Security Telnet Protocol Failures
Description 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.
Impact Operational
Occurrence Low
2.3.101 Modem Unable to Register on some CMTS
devices with more than Two Classifiers in CM
configuration file
Description When a CM configuration file contains more than two
classifiers, the modem is unable to register on some CMTS
networks.
Impact Service
Occurrence Low

2.3.102 Source Verify Failure Logs on the CMTS
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
Impact Service
Occurrence Low
2.3.103 IPDT: Dialing Errors with Dial Pulse
Description When using the pulse dialing method on an IPDT solution,
some pulse digits were missed resulting in a misdial.
Impact Service
Occurrence Low
2.3.104 Non-UDP/TCP Packets might be Dropped if MTA
Provisioned
Description 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.
Impact Service
Occurrence Low
2.3.105 EURO: Calls do not Complete when using Dial
Pulse Dialing
Description European loads fail to complete calls when using dial pulse
dialing.
Impact Service
Occurrence High

2.3.106 Hook Status and Line Status MIB Objects Not
Impemented
Description The SNMP MIB Objects, arrisMtaDevCallStatsHookStatus and
arrisMtaDevLineCardState, were not implemented in the
firmware prior to this release.
Impact Operational
Occurrence High
2.3.107 CM MIB Walk Stops on MTA MIB Objects
Description 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.
Impact Operational
Occurrence High
2.3.108 Modem Should Ignore DHCPv6 Advertise
Message with "NoAddrsAvail" Status Code
Description 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.
Impact Service
Occurrence High

2.3.109 E-MTA does not register with the
arrisMtaDevSwDnldNoSvcImpact in CM Configuration
File
Description 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.
Impact Service
Occurrence High
2.3.110 CLI Debug Command 'dsxtrace' did not Enable
the DSX Traces
Description The dsxtrace command from the Callp CLI will now correctly
enable and disable the DSX tracing.
Impact Operational
Occurrence High
2.3.111 Call Processing Debug Traces were Persistent
Description 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.
Impact Operational
Occurrence High
2.3.112 US Rate Limit may not be Accurate with Mixed US
Modulations
Description 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.
Impact Service
Occurrence High When US channel bonding is enabled
2.3.113 ipNetToMediaTable not Responding Correctly to
SNMP getNext
Description Queries of the the ipNetToMediaTable interface 16 via SNMP
GET-NEXT operation returned incorrect data, and did operate
in the same manner as D2.0 for this SNMP MIB object.
Impact Operational
Occurrence High
2.3.114 Performance Degradation with Large Round Trip
Delays
Description 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.
Impact Service
Occurrence High
2.3.115 TS 7.1.89: DOCSIS 3.0 Potential Registration
Issue with US Channel Bonding
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.

This issue is disclosed in AFB-10-0301.
Impact Service
Occurrence High

2.3.116 SIP: Emergency Call Network Hold Media Type
Set Incorrectly
Description 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.
Impact Service
Occurrence High
2.3.117 SIP: 200 OK Message Does Not Contain the SDP
Description 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.
Impact Service
Occurrence High
2.3.118 IPv6: Small Memory leak if Multicast DSID
Forwarding is Enabled
Description 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.
Impact Service
Occurrence Medium
2.3.119 Allow leading '/' in the MTA Configuration File
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:

ppCfgMtaFeatureSwitch is 0x400:

Impact Operational
Occurrence High
2.3.120 Battery Code Not Displayed
Description When a battery of part number 789699 was plugged into the E-
MTA, 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.
Impact Operational
Occurrence High
2.3.121 SysObjectID Increments on each Firmware
Release
Description The SysObjectID previously incremented on each firmware
release. The SNMP MIB Object now only increments for new
HW models and not per firmware release.
Impact Operational
Occurrence High
2.3.122 Webpage TOD may not be Retrieved
Description 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.
Impact Operational
Occurrence High
Description PROD00151239: A single one-time exception was caught
during CM registration


Impact Service
Occurrence Rare
2.3.124 MuSecurity HTTP Unsafe Test Suite
Incompatibility
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.

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.
Impact Operational
Occurrence High
2.3.125 SIP: Post Provisioning Issue with IfAdminStatus
Description If SIP post provisioning is used to modify the line
ifAdminStatus, the set to enable the line will not take effect
upon initial setting.
Impact Service
Occurrence High


2.3.126 Ring Cadence Default Values for Certain
Countries did not match values from prior ARRIS
releases
Description 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.
Impact Service
Occurrence High
2.3.127 Incorrect Hook Flash Timing
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
Occurrence High
2.3.128 CM may register in partial services mode
Description 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.
Impact Service
Occurrence High
2.3.129 Event Logs display MAC address when
MAC/FQDN MIB is set to disabled in configuration file
Description 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.
Impact Operational
Occurrence High

2.3.130 Wrong HTTP Header end of line character
Description 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.
Impact Operational
Occurrence Low
2.3.131 Incorrect Static CPE Count may not be Accurate
MAXCPE Counter may be exceeded
Description The Static CPE counter is reset to zero when the ethernet link
goes down on a CM with statically provisioned CPE devices,
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.132 Modem may reset occasionally when
Configuration File contains IP filters
Description 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.
Impact Service
Occurrence Low
2.3.133 Loop Diagnostics Run on IS Line

Description 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.
Impact Service
Occurrence High
2.3.134 DS LED Bonded Mode Display may not be
Correct
Description 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.
Impact Operational
Occurrence Low
2.3.135 Short RF Cable Cut may Cause T4 Timeout
Description 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.
Impact Service
Occurrence Rare
2.3.136 Modem does not respond to Pings after Short
Cable Cuts
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.

This issue was resolved with a CMTS load change and not an
issue on the E-MTA.
Impact Service
Occurrence High

2.3.137 Static TFTP port selection could cause failed
TFTPs
Description 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.
Impact Operational
Occurrence Low
2.3.138 DOCSIS Card Failover Causes T4 Timeout
Description 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.
Impact Service
Occurrence High
2.3.139 Modems Register in Upstream Partial Service
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.140 Dialing Method Line Persistence
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.141 FQDN with trailing '.' marked invalid
Description 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.
Impact Service
Occurrence High If FQDNs with trailing periods . are used
2.3.142 SIP: Calls Fail for Messages Greater than 1500
bytes
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.
Impact Service
Occurrence High
2.3.143 LED Behavior is Incorrect during AC Failure
Condition
Description 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.
Impact Operational
Occurrence High
2.3.144 Multicast Traffic Issue with older CMTSs
Description 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.
Impact Service
Occurrence High
2.3.145 Voice Quality Metrics MIBs incorrect
Description 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.
Impact Operational
Occurrence High
2.3.146 MuSecurity Protocol Mutation Attack Test Failure
Description The MuSecurity test suite for protocol mutation attack testing
of TELNET functionality is failing on the modem. A reboot is
required to restore dialtone and CM management (telnet,
WebGUI, SNMP) capabilities.
Impact Service
Occurrence High
2.3.147 Configuration Parameters Web Page is not
accurate
Description Some fields of the configuration parameters webpage are not
accurate and may reflect incorrect values.
Impact Operational
Occurrence High
2.3.148 CLI Error Message on CRCX for DSX DQoS

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
Description 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.
Impact Service
Occurrence Rare
2.3.150 Advanced WebGUI Accessible after Single Login
Description 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.
Impact Operational
Occurrence High
2.3.151 Router Congestion on HTTP Download May
Result in Slower Throughput

Description 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.
Impact Service
Occurrence High
2.3.152 Rate-limit Traffic Shaping on CMTS may cause
Lower US Throughput
Description 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.
Impact Service
Occurrence Low
2.3.153 Foreign EMF Voltage Recovery
Description During initialization of an E-MTA, loop diagnostics are run to
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.
Impact Service
Occurrence High
2.3.154 IPv6 SSH Log Events Missing
Description When using IPv6, the SSH events for login accepted/rejected
are not provided to the syslog server or event logs.

This issue is resolved as a configuration problem.
Impact Operational
Occurrence High


2.3.155 LED for Line 2 Continues to Blink on a 1 Line Unit
Provisioned on the Switch
Description Telephony line 2 LED continuously blinking on a unit where
only line 1 is provisioned on the switch. Configuration files
have both lines provisioned.
Impact Operational
Occurrence High
2.3.156 Incorrect Dual-Color LED Indicator on Some
CMTS Vendors
Description 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.
Impact Operational
Occurrence High
2.3.157 Cant Provision Number of MTA DHCP Retry
Attempts
Description 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.
Impact Operational
Occurrence High

2.3.158 Battery Telemetry Alarm Syntax Does Not Match
Prior Touchstone Releases
Description 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.
Impact Operational
Occurrence High
2.3.159 E-MTA Does Not Display Service Class Name
Description The E-MTA's service class name is not displayed on the
configuration parameters web page.
Impact Operational
Occurrence High
2.3.160 Telnet Packets Could Be Sent with the Wrong
Source MAC Address
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
Impact Operational
Occurrence Rare
2.3.161 Upstream Channel Bonding May Result in Partial
Service Mode
Description 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.
Impact Service
Occurrence High

2.3.162 Upstream Drop Classifier Support
Description 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.
Impact Service
Occurrence High
2.3.163 DNS Response of Type CNAME Does Not Work
Description 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.
Impact Service
Occurrence High
2.3.164 MTA Accepts Unknown Ciphersuites
Description The MTA should ignore unknown RTP/RTCP ciphersuites in a
Create Connection (CRCX) message from the CMS, but
currently they are accepted.
Impact Service
Occurrence Low
2.3.165 MuSecurity TELNET Failure
Description 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.
Impact Operational
Occurrence High

2.3.166 SIP: Blank digitmap causes exception
Description 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.
Impact Service
Occurrence High
2.3.167 VQM: Local Metrics Reported to Call Server are
All Zero
Description 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.
Impact Operational
Occurrence High
2.3.168 Automatic OSI Intermittently Fails on IPDT
Description In an IDPT solution, automatic OSI was not always initiated on
the terminating line due to a timing issue.
Impact Service
Occurrence Medium
2.3.169 Web Page Related Issues
Description 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.
Impact Operational
Occurrence High
2.3.170 Upgrade Fails if Upgrade Server TLV is set to
0.0.0.0
Description 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.
Impact Service
Occurrence High
2.3.171 SIP: sipCfgDialFeatCode mib does not support
multiple, comma-separated dial strings
Description 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.
Impact Operational
Occurrence Low
2.3.172 VQM Feature only Stores Last 10 calls
Description The VQM feature only store information for the last 10 calls
instead of the last 50 calls as in other Touchstone releases.
Impact Operational
Occurrence High

2.3.173 IPv6: E-MTA Not Sending Option Code 17 in
ORO
Description 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.
Impact Operational
Occurrence High
2.3.174 Potential Upgrade Failure
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.175 SIP: SIP Message Tracing Information Missing on
Webpage
Description 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.
Impact Operational
Occurrence High
2.3.176 TLV Long Encoding Format Not Supported
Description 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.

Impact Service
Occurrence High
2.3.177 Line may become Stuck in Notification State
Description 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.
Impact Service
Occurrence Low
2.3.178 End of Call Statistics Show Incorrect Data
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
2.3.179 CallAgentID Only Supports FQDN
Description The CallAgentID does not support the ability to use a bracketed
IP address for BASIC and HYBRID provisioning methods.
Impact Service
Occurrence High
2.3.180 CM Fails to Lock to Secondary Downstream
Description 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.
Impact Service
Occurrence High
2.3.181 IPv6: Lease Times Displayed are not valid
Description 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.
Impact Operational
Occurrence High
2.3.182 Enhancement to TFTP Retry Mechanism
Description 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.
Impact Operational
Occurrence High
2.3.183 Incorrect LED Status during AC-FAIL Condition
Description 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.
Impact Operational
Occurrence High
2.3.184 PCMM GATE-SET Transaction Failure
Description 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.
Impact Service
Occurrence High
2.3.185 pktcEnNcsEndPntHookState MIB Object may
Report Incorrect Hook State
Description The SNMP MIB Object, pktcEnNcsEndPntHookState was not
reporting the correct hook status state
(onHookPlusNCSActivity) when ring splash was being played.
Impact Operational
Occurrence High
2.3.186 Traffic Below Baseline of 99.95%
Description 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.
Impact Service
Occurrence High
2.3.187 pktcDevEvReportLevel Incorrect for AC Fail Clear
Trap
Description The SNMP trap for a cleared AC Failure log was being reported
as a Major event instead of Informational for the
pktcDevEvReportLevel.
Impact Operational
Occurrence High
2.3.188 SIP: SIP Calls Fail after MTA IP Address Change
via DHCP RENEW
Description 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.
Impact Operational
Occurrence Low
2.3.189 SNMP MIB Object to Show Ethernet Duplex
Status
Description 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.
Impact Operational
Occurrence High
2.3.190 DHCP NAK Sent as Broadcast Instead of Unicast
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.
Impact Operational
Occurrence High

The following issues were resolved in release 7.1.61A
2.3.191 Modems May Intermittently Fail to Register in
Bonded Mode
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.192 Ignore CMTS (S-TDMA) 10.24MHz Timing in MDD
Description 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.
Impact Service
Occurrence High

2.3.193 MTA Time Server Shows 0.0.0.0 on the Modem's
DHCP Web Page
Description The modem's DHCP web page displays the MTA Timer Server
IP address as 0.0.0.0.
Impact Operational
Occurrence High
2.3.194 ipNetToMediaPhysAddress MIB Object Failure

Description 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.
Impact Operational
Occurrence High
2.3.195 Fax Failure on Origination from E-MTA
Description When a standard fax call is originated from an E-MTA, the fax
will fail to complete. Terminating fax calls complete
successfully.
Impact Service
Occurrence High
2.3.196 Syslog Events May Not Be Sent
Description After filling up the MTA vendor event log buffer with
approximately 50 logs, syslog events will no longer be sent.
Impact Operational
Occurrence High
2.3.197 Recovery Time Extended for a RF Cut
Description 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.
Impact Service
Occurrence High
2.3.198 CM Filter Issues
Description The CM filters used for IP packets and UDP traffic currently
are not operational.
Impact Service
Occurrence High

2.3.199 pktcDevEvEndpointName May Contain
Incomplete Entries
Description The pktcDevEvEndpointNameMIB object, may contain
incomplete information for the IP and FQDN address. These
values are sometimes cut off in the display.
Impact Operational
Occurrence High
2.3.200 Web Page Issue with Event Logs
Description 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.
Impact Operational
Occurrence Low
2.3.201 Extreme Robustness Testing Issue Currently
Under Investigation
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 E-
MTA 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.202 Problem with SNMP MIB Objects in Co-existence
Mode
Description In coexistence mode, the CM does not populate
snmpTargetParamsTable, snmpNotifyObjects, and
snmpNotifyFilters (OSS.01).

Impact Operational
Occurrence High
2.3.203 EuroDOCSIS: docsQosParamSetTable Does Not
Comply
Description 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).
Impact Operational
Occurrence High
2.3.204 EURO Secure MTA Provisioning Mode Not
Working
Description The Euro-PacketCable 1.5 SECURE provisioning method is not
working at this time. NA PacketCable 1.5 SECURE
provisioning methods work correctly.
Impact Service
Occurrence High
2.3.205 Call Completion Rate below Baseline with 64-byte
DS Traffic
Description 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.
Impact Service
Occurrence Low

2.3.206 E-MTA Sometimes Doesnt Bond After DFO
Command from CMTS
Description The TM702 is getting the Downstream Frequency Override
(DFO) but it is not moving to the indicated DS. After the E-
MTA fails to get the correct DS, the CMTS will move to the
next frequency until it exhausts all options. At this time, the E-
MTA will register in D2.0 mode. This DFO issue has only
been seen while interoperating with a specific CMTS vendor.
Impact Service
Occurrence Low
2.3.207 igmpCacheTable Not Populated
Description In NmAccess mode, the igmpCacheTable is not populated
correctly and is empty.
Impact Operational
Occurrence High
2.3.208 SIP: sipCfgCallWaitingStarCodeSurvivesReset
does not Survive Reset
Description 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.
Impact Service
Occurrence High
2.3.209 SIP: sub-TLVs 69, 70, and 71 within TLV 43 MIB
in the MTA Configuration File were not supported
Description TLVs for SIP DigitMap, Dial Feature DigitMap, and Proxy
Dial Feature DigitMap MIBs in the MTA Config file were not
supported.
Impact Service

Occurrence High
2.3.210 CallP / QoS Statistics Web GUI Incomplete
Description CallP/QoS Web GUI missing CallP state, LC state, and Payload
Header Suppression information.
Impact Operation
Occurrence High
2.3.211 Call Waiting Disabled by Default
Description Call Waiting should be enabled but was disabled by default.
Impact Service
Occurrence High
2.3.212 Pasting Multiple Commands over Telnet does not
Work
Description Certain Telnet clients are inserting null terminator after new
line characters and causing command not found error message
when pasting multiple CLI commands.
Impact Operational
Occurrence Low
2.3.213 SIP: sipCfgProvisionedCodecArray Ignored
Description sipCfgProvisionedCodecArray MIB does not allow space
characters between Codecs that are listed.
Impact Service
Occurrence High
2.3.214 SIP: Disabling Session Timers causes Re-
INVITEs to Fail

Description Enabling the SIP feature switch option to disable Session
Timers causes Re-INVITE messages to fail.
Impact Service
Occurrence High
2.3.215 VMWI Signal Remained Active after a Reboot
Description 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.
Impact Service
Occurrence Low
2.3.216 SIP: Hook Flash Timing Cannot be changed by
Configuration File
Description SIP loads do not accept changes to Hook Flash timing
provisioned via MTA config file.
Impact Service
Occurrence High
2.3.217 Incorrect Quarantine and Hook State
Description pktcEnNcsEndPntQuarantineState and the
pktcEnNcsEndPntHookstate MIBs returned incorrect values.
Impact Operational
Occurrence High
2.3.218 Line Card Diags Wont Work via SNMP
Description ppSurvPortLcDiagRequest MIB for Line Card diags could not
be started via SNMP.
Impact Operational
Occurrence High

2.3.219 Scanover Web GUI Accessible via the WAN IP
Description 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.
Impact Operational
Occurrence High
2.3.220 SIP: Incomplete Information in the SIP-REGISTER
Description SIP User-Agent Hearder missing hardware and software
version information in the SIP-REGISTER messages.
Impact Operational
Occurrence High
2.3.221 Modems Stuck on TFTP File due to Configuration
Filename
Description Modems will get stuck in TFTP loop when trying to download
a config file with colons : in the filename.
Impact Service
Occurrence High
2.3.222 Supervisory Tones are Not Correct
Description MTA tone tables contain setting for North American tones but
plays European tones.
Impact Service
Occurrence High
2.3.223 SIP: Telephone Line LEDs are always On
Description Telephone line 1 and 2 LEDs are always on even when
ifdminStatus for the line is set to down.

Impact Service
Occurrence Low
2.3.224 LEDs Do Not Correctly Indicate Protection Mode
Description 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.
Impact Service
Occurrence Low
2.3.225 DCC Fails When in DOCSIS 2.0 Mode on Certain
CMTS/Software
Description 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.
Impact Operational
Occurrence High
2.3.226 No Error Messages for SDP with Incorrect Case
Description 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.
Impact Operational
Occurrence High
2.3.227 Power Ring Frequency is Not Settable
Description The power ring frequency was not settable via the config file
with pktcSigPowerRingFrequency MIB and was always 25 Hz.

Impact Service
Occurrence High
2.3.228 E-MTA Fails to Come On-line Due to MIB Ordering
in the MTA Configuration File
Description 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.
Impact Service
Occurrence Low
2.3.229 pktcSigDevToneTable Changes are not Affecting
the Tone Playout
Description The pktcSigDevToneTable MIBs could be set in the config file
but any changes were not correctly played out to the CPE.
Impact Service
Occurrence High
2.3.230 Incorrect Default Flash Timing
Description The default flash timing was incorrectly set for the Netherlands
template.
Impact Service
Occurrence High
2.3.231 Active Call is Dropped during Recovery From 1x1
to 4x1
Description 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.
Impact Service

Occurrence Low
2.3.232 Status Web GUI may Display Incorrect CABLE
State
Description Status Web GUI may display CABLE state as Down even
though it is online.
Impact Operational
Occurrence Low
2.3.233 EURO: Apply Country Code Template Settings
before IETF Signaling MIB Adjustments
Tracking No. PROD00130897, PROD00144973, PROD00144912,
PROD00144978, PROD00144999, PROD00144974
Description 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.234 Remote Ringback Level is Too Low
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.235 ipNetToMediaTable SNMP Query Does Not Work
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.236 MTA DHCP RENEW Fails when Missing BootP
Settings
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.

Impact Service
Occurrence High
2.3.237 Wrong Response to NCS Local Connection
Options
Description Updated NCS error response codes to closer match the
recommended values for specific fault conditions.
Impact Service
Occurrence Rare
2.3.238 Incorrect Data in docsIfSigQUnerroreds MIB Value
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.239 SIP: Pulse Dial Dialing Does Not Work
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.240 SIP: E-MTA Does Not Provision When Lines are
OOS
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.
Impact Service
Occurrence High
2.3.241 MTA MIB WALK Fails to Read Event MIB
Description A MIBWALK initiated using the MTA IP address for the E-
MTA 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.242 ifAdminStatus.16 via CM Configuration File Not
Working Properly
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.243 Config File Rejected When Telnet/SSH MIBs
Present Without TelnetPassword MIB
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.244 Modem Takes Too Long to Recover on Cached
US Channel
Description When the E-MTA failed to detect a ranging opportunity from
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.245 Missing Battery Telemetry MIBs
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.246 MTA Provisioning Fails When the Local Address
Portion Missing From callagentid
Description TI made a change specifically for EURO to fail provisioning
when ca@ is missing from the callagentid mib.
Impact Service
Occurrence High

2.3.247 MTA Fail to Send a Wildcard RSIP after SNMP
Reset
Description MTA did not send a wildcard RSIP after SNMP reset for all
endpoints that were managed by the same Notified Entity.
Impact Service
Occurrence High
2.3.248 SIP: MTA Fails Provisioning Due to MIBs with an
Incorrect Value in the MTA Configuration File
Description 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.
Impact Service
Occurrence High
2.3.249 Disabled MTA Still Generates Telnet Debugging
Prints
Description When the MTA has been disabled (using the ifAdminStatus
MIB), MTA DHCP error logs are still generated and printed to
the telnet session.
Impact Operational
Occurrence High

The following issues were resolved in release 7.1.44A
2.3.250 E-MTA Factory Yield Improvements
Description This release of firmware includes fixes to improve the current
yield rate from the factory.
Impact Factory

Occurrence Low

2.3.251 Incorrect MIB Object Being Sent Up for MTA MAC
Address in MTA Enrollment Inform
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.
Impact Operational
Occurrence High
2.3.252 Upstream QoS Classifiers May Not Work Properly
Description 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.
Impact Service
Occurrence Low
2.3.253 Link LED Does Not Flash
Description The link LED on the E-MTA does not flash when bridging data
if the packet processor is enabled.
Impact Operational
Occurrence High
2.3.254 Incorrect sysUptime Field in TRAP Messages
Description The sysUptime field is not being populated correctly. After just
a few minutes, an Uptime of 245 days is displayed.

Impact Operational
Occurrence High
2.3.255 E-MTA Loses Downstream Sync After
backoffCounters Debug Command
Description 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.
Impact Service
Occurrence Rare
2.3.256 Call Processing Fails When Max Data Throughput
is Applied
Description 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.
Impact Service
Occurrence High
2.3.257 TM702B: Intermittent Permanent AUTH Reject
BPI Failures
Description 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.
Impact Service
Occurrence High
2.3.258 E-MTA Fails to Recover from RF Outage

Description 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.
Impact Service
Occurrence High
2.3.259 USB Connectivity Issue
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
registered.
Impact Service
Occurrence High
2.3.260 Occasional DSP Reset Causes Extended Traffic
Run Issue
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.

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.
Impact Service
Occurrence Rare
2.3.261 Extreme Robustness Testing Issue
Description After the RF cut, the CM shows operational and CMTS shows
offline. A reboot of the E-MTA is required to recover the unit.
Impact Service

Occurrence Low
2.3.262 MIB docsifCMSTatusEqualizationData Cannot be
Polled
Description The MIB Object, docsifCMSTatusEqualizationData, cannot be
polled to display pre-equalization data.
Impact Operational
Occurrence High
2.3.263 CPE MAC Address Provisioning In Configuration
File Not Supported
Description When the CM is provisioned with a configuration file providing
a CPE MAC address, the MAC address isn't present in the
dot1dTpFdbTable MIB.
Impact Service
Occurrence Low
2.3.264 False T3 Event in Event Logs
Description A false T3 event may appear in the event logs as a result of a
race condition on the E-MTA.
Impact Operational
Occurrence Low
2.3.265 Telnet/HTTP to CM IP Can Fail when Source
Verify Enabled
Description 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.
Impact Operational
Occurrence High

2.3.266 Reject(na) state on CMTS with Secondary
Downstream Outage
Description 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.
Impact Service
Occurrence High
2.3.267 Status Page Shows Information for Non-DOCSIS
Signals
Description 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.
Impact Operational
Occurrence High
2.3.268 Nonstandard "NULL" Value for DHCP Option 122
Suboption 3 Not Allowed
Description 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.
Impact Service
Occurrence High
2.3.269 DSX Transactions on an E-MTA May Fail Due to
Transaction ID
Description 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.
Impact Service
Occurrence Low
2.3.270 MTA Feature Switch MIB - MaxCpeBypass
Description The previously supported DOCSIS 2.0 MIB, MaxCpeBypass, is
now enabled for DOCSIS 3.0 releases.
Impact Operational
Occurrence High
2.3.271 PacketCable1.5: Hybrid.2 Provisioning and
Secure Do Not Work
Description Hybrid.2 provisioning and North American secure provisioning
do not work at this time.
Impact Operational
Occurrence High
2.3.272 Automatic OSI Could Be Triggered During Dialing
Description 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.
Impact Service
Occurrence High
2.3.273 E-MTA Stores Partial MDD
Description 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.
Impact Service
Occurrence High
2.3.274 E-MTA Provisioning Failure if Mandatory US TLVs
Missing from CMTS
Description Modem registration would previously fail in the CMTS was
missing mandatory US Ambiguity TLVs. This requirement has
been relaxed to support CMTS interoperability.
Impact Service
Occurrence High
2.3.275 Embedded RQNT and MDCX Messages with "to="
Parameter Rejected
Description 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.
Impact Service
Occurrence High
2.3.276 Dual Mode May Result in E-MTA Reset
Description 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.
Impact Service
Occurrence High
2.3.277 Duplicate TLV-11 Entries in the Configuration File

Description Downloading a configuration file that contains duplicate TLV-
11 MIB entries causes the TLV parser to fail and the modem to
abort the registration process. A reboot is required to recover
the modem.
Impact Service
Occurrence High

3 Letter of Operational Considerations
The Letter of Operational Considerations is to inform operators of any system
considerations for the Touchstone Firmware that may affect service, operations, or
maintenance for this product release.
3.1 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 SIP : MTA Supports Only One Contact Header
Description MTA supports only one(1) Contact header from the SIP proxy.
Impact Service
Occurrence High
Workaround None
3.1.2 REG-ACK may not be received by the CMTS
Description When CMTS has a short T6 timer, the CM REG-ACK may not
be seen by the CMTS. The CM may take up to 15 minutes to
complete registration.
Impact Service
Occurrence Rare
Workaround Increase the CMTS T6 timer to greater than 30 seconds.
3.1.3 Opened ports detected during NMAP port scan
Description NMAP port scan test showed number of opened ports. NMAP
test is to verify that the modem blocks any attempts to scan
ports on the eMTA or attached CPEs.

Impact Service
Occurrence High
Workaround None
3.1.4 Syslog message shows incorrect vendor type
Description Vendor type in syslog message for event 2417164298
Touchstone SW Upgrade Successful shows as DOCSIS and
not ARRIS.
Impact Operational
Occurrence High
Workaround None
3.1.5 SIP: Port 2427 opened
Description Test showed that port 2427 was incorrectly opened when using
SIP load.
Impact Operational
Occurrence High
Workaround None
3.1.6 Slower Registration Times for Broadcast IM Ranging
Opportunities
Description Modems using Broadcast IM ranging opportunities for non-
primary US acquisition may observe slower registration times
and more instances of US partial-service.
Impact Operational
Occurrence High
Workaround None

3.1.7 SIP: CallerID Information not suppressed via RFC-3323
Privacy Header
Description CallerID is not correctly suppressed when the
sipCfgSipFeatureSwitch is set to enable RFC 3323 privacy
header (0x08000000) for SIP INVITE messages.
Impact Operational
Occurrence High
Workaround None
3.1.8 SIP: Fax Only Mode Timer may fail for Incoming Call
Description 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.
Impact Service
Occurrence High
Workaround None
3.1.9 SIP: Repeat Dialing may Result in No Ringback Tone
Description When repeat dialing is activated, if the party being called goes
off-hook first ringback will not be heard.
Impact Service
Occurrence High
Workaround None
3.1.10 SSH Timeout Failure
Description Occasionally during an automated testing run, a timeout will
occur when logging into the modem via SSH. Subsequent
attempts work fine.
Impact Operational

Occurrence Low
Workaround Attempt the SSH login again.
3.1.11 SIP: Traps may not be sent to Trap Server
Description 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.
Impact Operational
Occurrence High
Workaround None
3.1.12 LC Protection State not Reported via
pktcEnEndPntInfoTable
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.2 Unsupported Features
The following features are not supported in the TS 7.1 release at this time.
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
SIP Post Provisioning (158987) (158992)

3.3 Upgrade Considerations
The following considerations are important to take into account when upgrading to this
firmware release.
Root Certificate Change for Full PacketCable Provisioning
This release of firmware resolves an issue in earlier production e-MTAs where the
default root certificate was set to the test root certificate instead of the real root
certificate. The SNMP MIB object, arrisMtaDoc30RootCertType (OID:
1.3.6.1.4.1.4115.1.3.5.1.2.2), can be used to change the default root certificate being used
by the E-MTA. This SNMP MIB Object must be placed in the CM configuration file. If
E-MTAs deployed are currently using the test root certification, service will be
impacted unless this MIB object is added to the configuration file for releases TS 7.1.103
and higher.
sysObjectID MIB Object Format Change
Starting in TS7.1.103 DOCSIS 3.0 releases, the sysObjectID MIB walk with OID
1.3.6.1.2.1.1.2.0 will no longer display the firmware release version. Please use the
sysDescr.0 (1.3.6.1.2.1.1.1.0) or docsDevSWCurrentVers (1.3.6.1.2.1.69.1.3.5.0) MIBs
to obtain the E-MTA firmware release.
arrisMtaDevLineCardState Returns IDLE for Unprovisioned Lines
In TS7.1 DOCSIS3.0 releases, arrisMtaDevLineCardState MIB will return a value of
IDLE(1) for unprovisioned lines. Previously, DOCSIS2.0 releases would return a value
of (0) which is Out Of Service. Starting in TS7.1.103, the following 0x00000004 callp
feature switch bit in the ppCfgMtaCallpFeatureSwitch adds the ability for the MSO to
configure the eMTA to return a value of (0) for unprovisioned lines.
0x00000004: If line is not provisioned show 0(OOS) rather than IDLE for
arrisMtaDevLineCardState

CMTS 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-SP-
MULPIv3_0-I09-090121.pdf Annex C.4 Table C-6 for the partial service code referred to
above. It is important to make sure your CMTS is upgraded to the DOCSIS 3.0 revision
to avoid this problem and a possible service interruption.
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
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.
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 = docsDevNmAccessCommunity.1 "public"
SnmpMib = docsDevNmAccessControl.1 read
SnmpMib = docsDevNmAccessInterfaces.1 hexstr: 40
SnmpMib = docsDevNmAccessStatus.1 createAndGo
SnmpMib = docsDevNmAccessCommunity.2 "private"
SnmpMib = docsDevNmAccessControl.2 readWrite
SnmpMib = docsDevNmAccessInterfaces.2 hexstr: 40
SnmpMib = docsDevNmAccessStatus.2 createAndGo

LAN / CPEside SNMP access (read-only) for certain MIBs is supported before the
modem is ranged and registered in the same manner as in DOCSIS 2.0 mode.
MTA SNMP Access
Default SNMP security settings and functionality on the MTA side is based upon the
selected MTA provisioning method. For PacketCable 1.5 methods, then SNMP access to
the MTA will be disabled by default until the addition of the proper Community Table
settings in the MTA configuration file per the following example:

{SnmpMib snmpCommunityName.'mtaprov' mso_comm_string}
{SnmpMib snmpCommunitySecurityName.'mtaprov' @mtaprov}
{SnmpMib snmpCommunityStatus.'mtaprov' createAndGo}

NOTE: In terms of configuring SNMP Community Strings, for 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. Please note
that the Provisional Response bit 0x00008000, Lockstep Quarantine Mode bit
0x00000002, and Piggybacked Transmissions of NCS Messages bit 0x00000001 are
opposite behavior from the DOCSIS 2.0 releases.

0x20000000: MTA generates automatic OSI
0x10000000: Delay DLCX response against connection on onhook only line (for VMWI)
0x08000000: Use alternate (non sequential) Caller ID delivery order
0x04000000: Use hard-coded values for Flash timing (90 - 800 ms)
0x01000000: Send dtmf digits via RFC2833 with payload 101 without request
0x00800000: Add brackets to IP for MTA FQDN when communicating with call server
0x00400000: Allow NCS Redirect without IPsec
0x00100000: Allow AES encryption for RTP/RTCP (bit = 0)
0x00080000: LUCENT RFC-2833 messaging without request using payload 94
0x00010000: Payload Header Suppression
0x00008000: Disable endpoint from sending provisional responses: DISABLED
0x00004000: DSX (access only) DQoS
0x00001000: NUERA RFC-2833 messaging without request using payload 127
0x00000800: Force the use of DQoS. Reject service if not used
0x00000100: Enable DOCSIS 2.0 backward compatibility for DQoS
0x00000080: Omit mptime parameter in returned SDP
0x00000008: Reduce the capability descriptor in the SDP to T38 only
0x00000004: If line is not provisioned show 0 (OOS) rather than IDLE for arrisMtaDevLineCardState
0x00000002: Prevent endpoint to enter the Lockstep quarantine mode
0x00000001: Stop 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

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.


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

Office Hours
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
South America Chile
Email
Telephone
Office Hours
techsupport.cala@arrisi.com
+56 2 678 4500
9:00 a.m. to 6:00 p.m. (Chile local time).
Europe Amsterdam, The Netherlands
Email
Telephone
Office Hours
techsupport.europe@arrisi.com
+31 20 311 2525
8:30 a.m. to 17:30 p.m. CET
Japan Tokyo
Email
Telephone
Office Hours
techsupport.japan@arrisi.com
+81 (0) 3 5371 4142
9:30 a.m. to 6:00 p.m. (Tokyo local time)
Korea Seoul
Email
Telephone
Office Hours
techsupport.asia@arrisi.com
+82 2 6007 2880
9:30 a.m. to 6:00 p.m. (local time)
Worldwide North America
Email
Telephone
techsupport@arrisi.com
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.

Appendix A: Compliance Matrix

DOCSIS 3.0 CW69 ECNs
SP-SECv3.0 I10
SP-CMCIv3.0 I01
SP-PHYv3.0 I08
SP-MULPIv3.0 I10
SP-OSSIv3.0 I09
PacketCable 1.5 CW69 ECNs
PKT-SP-DQOS I04
PKT-SP-CODEC I03
PKT-SP-NCS I03
PKT-SP-MIBS I03
PKT-SP-MIB-SIG I01
PKT-SP-PROV I04
PKT-SP-SEC I03

Documentation Links:
http://www.cablemodem.com/specifications/specifications30.html
http://www.packetcable.com/specifications/specifications15.html


Touchstone

Telephony Firmware

Release 7.1.109

Release Notes and
Letter of Operational
Consideration

Copyright @2011 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: Released

TS 7.1.109-Rnloc 1.0

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

TS 7.1.109-Rnloc 1.0

Diunggah oleh

Hak Cipta:

Format Tersedia

Touchstone

Anda mungkin juga menyukai