TS6.1 Feature Guide

Touchstone® Telephony
Feature Guide
Release 6.1 Standard 1.3
Date: June 2009
Chapter 1: Overview
This chapter describes Touchstone Telephony hardware and
firmware features.
Chapter 2: Compliance
This chapter outlines Touchstone Telephony DOCSIS®, Euro-DOC-
SIS, PacketCable,™ and Euro-PacketCable compliance, and
describes ARRIS-proprietary extensions to the standards.
Chapter 3: Telephony Features
This chapter describes telephony features supported in Touchstone
firmware.
Chapter 4: Provisioning Features
This chapter describes provisioning features supported in Touch-
stone firmware.
Chapter 5: Management and Troubleshooting Fea-
tures
This chapter describes management and troubleshooting features
supported in Touchstone firmware.
© 2004–2009 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. Users must take full responsibility for their applications of any products specified in this document.
The information in this document is proprietar y to ARRIS.
ARRIS, C3™, C4®, and Touchstone® are trademarks or registered trademarks of ARRIS Group, Inc. Cadant® is a
registered trademark of ARRIS Group, Inc. All other trademarks and registered trademarks are the property of their
respective holders.
ii
Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Publication history
June 2009 Release 6.1 Standard 1.3 version of this document for TS6.1 MSUP3.
January 2009 Release 6.1 Standard 1.0 version of this document for TS6.1.
September 2007 Release 5.2 Standard 1.1 version of this document for TS5.2.
May 2007 Release 5.1 Standard 1.0 version of this document for TS5.1.
December 2006 Release 5.0 Standard 2.0 version of this document for TS5.0 MSUP.
October 2006 Release 5.0 Standard 1.0 version of this document.
August 2006 Release 4.6 Standard 1.0 version of this document.
December 2005 Release 4.5 Standard 2.0 version of this document for TS4.5 MSUP 2.
November 2005 Release 4.5 Standard 1.2 version of this document for TS4.5 MSUP 1.
April 2005 Release 4.4 Standard 2.0 version of this document for TS4.4 MSUP 3.
March 2005 Release 4.4 Standard 1.0 version of this document.
Feature Guide Release 6.1 Standard 1.3 June 2009

iv Publication history
February 2005 Release 4.3 Standard 1.0 version of this document.
August 2004 Release 4.2 Standard 1.0 version of this document.

Release 4.1 Standard 2.0 version of this document.
April 2004 Release 4.1 Standard 1.0 version of this document.
September 2003 Release 3.2 Standard 1.0 version of this document.

Contents
Audience ........................................................................................... xi
About the Touchstone Telephony Firmware ...................................... xi
Subscriber Interface .................................................................. xii
In this Document .............................................................................. xii
Terminology ...................................................................................... xii
Overview 1
Touchstone Telephony Por t ............................................................... 2
Touchstone Telephony Modems ........................................................ 4
Model 4 ....................................................................................... 4
Model 5 ....................................................................................... 4
Model 5 Multi-line ........................................................................ 5
Model 6 ....................................................................................... 6
Core Functionality ............................................................................. 7
TS6.1 Functionality ............................................................................ 8
Compliance and Interoperability ................................................. 8
Hardware Support ....................................................................... 9
Telephony Functionality .............................................................. 9
Provisioning Functionality ........................................................... 9
Management and Troubleshooting Functionality ...................... 10
Data Functionality ..................................................................... 11
New Features in TS6.1 MSUP ........................................................ 12
T.38 Image and Audio Offer Handling ....................................... 12
SIP BYE Delay .......................................................................... 12
Slovenia Template ..................................................................... 12
WTM652 Support ...................................................................... 12
Dual-Mode Enhancements ....................................................... 12
Persistent Line Status ............................................................... 12
RTP ‘‘End of Event’’ Duration Control ....................................... 13
SIP-specific Enhancements ...................................................... 13
SIP Hook Flash Reporting .................................................. 13
T.38 Call Enhancement ...................................................... 13
New and Changed MIB Objects ................................................ 13
New or Changed CLI Commands ............................................. 14
New Features in TS6.1 .................................................................... 15
Updated Hardware Support ...................................................... 15
New General Features .............................................................. 16

vi Contents
RIPv2 Support .................................................................... 16

Power-Save Enhancements (Model 6 and Newer) ............. 16
ToD Enhancements ............................................................ 16
WTM552- and WTM652-Specific Features ............................... 16
Provisionable Wireless Power Range ................................. 17
Wireless Channel Auto-Detect ........................................... 17
Provisionable Bandwidth Limits .......................................... 17
LAN/WLAN Isolation ........................................................... 17
Improved Access to WRM Web Pages ............................... 18
L2TP Support ..................................................................... 18
WPA Suppor t ...................................................................... 18
WRM Provisioning File Error Reporting ............................. 18
WRM Reset Button Control ................................................ 19
New Telephony Features .......................................................... 19
SuperG3 FAX Support ........................................................ 19
NCS Fax-only Line Support ................................................ 19
SIP Timer Enhancements .................................................. 19
SIP Penalty Box Enhancement ........................................... 20
SIP Post-Provisioning Enhancement .................................. 20
Caller ID Configuration Enhancements .............................. 20
New Provisioning Features ....................................................... 20
New Load Variants ............................................................. 21
Argentina Line Card Template ............................................ 21
PacketCable 1.5 Provisioning Compliance ......................... 21
SIP Feature Switch Enhancement ...................................... 21
Secondar y CM Feature Switch Enhancement ................... 22
Dual-Mode Support (TM601B and TM602B) ...................... 22
Cable Modem Interface Mask Support ............................... 22
New and Changed Troubleshooting Features ........................... 22
VQM Enhancements .......................................................... 23
Reset to Factor y Defaults ................................................... 23
Historic High Temperature .................................................. 23
TFTP Block Size Configuration .......................................... 23
New Management Features ...................................................... 23
WTM552- and WTM652-Specific Additions ....................... 25
IPv6-specific Additions ....................................................... 30
PacketCable 1.5 Battery Backup MIB ................................. 30
PacketCable 1.5 Provisioning Mode Selection ................... 31
RIP MIB Objects ................................................................. 32
Highest Recorded Temperature Objects ............................ 33
New and Changed CLI Commands .......................................... 33
New and Changed Web Pages ................................................. 34
WTM552 and WTM652 Router Access .............................. 34
New RIP Page .................................................................... 34
New Features in TS5.3 .................................................................... 35
New General Features .............................................................. 35
New Provisioning Features ....................................................... 35
New and Changed Troubleshooting Features ........................... 35
LED Pattern Changes ........................................................ 35

Contents vii
VQM Enhancements .......................................................... 36

Reset Reason Logging ....................................................... 36
New and Changed CLI Commands .......................................... 38
New and Changed Logs and Alarms ........................................ 38
Compliance 41
Standards Compliance .................................................................... 41
Optional Functionality ............................................................... 41
Extensions ....................................................................................... 42
TurboDOX Suppor t .................................................................... 42
WTM552- and WTM652-specific Compliance .......................... 42
Specification References ................................................................. 42
DOCSIS 2.0 Specifications ....................................................... 43
CableLabs IPv6 Specifications ................................................. 43
PacketCable Specifications ....................................................... 43
Telephony Features 45
General Functionality ...................................................................... 45
CODECs and Packetization Rates Supported .......................... 46
Multiple CMS Support ............................................................... 47
CMS Redirect Security Option .................................................. 47
Automatic Call Resource Recovery .......................................... 48
CODEC Engineering Rules ............................................................. 48
CODECs and Supported Lines (Model 6 and later) .................. 48
TM602 Engineering Rules .................................................. 49
TM604 and TM608 Lines 1–4 ............................................ 49
TM608 Lines 5–8 ................................................................ 49
CODECs and Supported Lines (Model 5 and earlier) ............... 50
G.729 CODEC Support ...................................................... 50
G.729 CODEC Negotiation ................................................ 50
G.729 Fax and Modem Support ......................................... 52
G.729 Bandwidth Considerations ....................................... 53
DTM602 DECT Support .................................................................. 53
Suppor ted Calling Features ............................................................. 53
End of Call Connection Statistics .................................................... 55
Echo Cancellation and Analog Fax/Modem Support ....................... 57
T.38 Fax Relay Suppor t ................................................................... 58
SDP Parameter List for T.38 Strict ............................................ 58
CallP Feature Switches Affecting the SDP ......................... 59
SDP Parameter List Considerations ......................................... 66
PacketCable 1.5 Extended Signaling ........................................ 66
Image and Audio Offer Handling ............................................... 66
Super G3 FAX Support .................................................................... 67
Loop Voltage Management Option .................................................. 67
Policy 1: Constant Loop Voltage ............................................... 68
Policy 2: QAM Carrier Detect .................................................... 68
Policy 3: MTA In-Ser vice/Manual Reset .................................... 68
Plant Maintenance Timer ................................................... 69

viii Contents
Policy 4: MTA In-Ser vice ........................................................... 69

Inband DTMF Transmission ............................................................ 70
European Productization ................................................................. 71
Gain Compensated Tone Generation .............................................. 71
Sinusoidal Ringing ........................................................................... 73
NCS Retransmission Algorithm ....................................................... 73
Configuration Parameters ......................................................... 73
List of Call Agent IP Addresses ................................................ 75
Adaptive Retransmission .......................................................... 75
SIP eMTA Suppor t ........................................................................... 76
Advanced Hook Flash Behavior ................................................ 77
Connected Alerting State Behavior .................................... 77
Call Waiting State Behavior ................................................ 77
3-Way Calling State Behavior ............................................. 78
SIP Proxy Penalty Box Feature ................................................. 78
Multi-line Interface Guidelines ......................................................... 79
Traffic Model .............................................................................. 79
Engineering Guidelines ............................................................. 79
Detailed Event Conditions ......................................................... 80
Event Condition 1 ............................................................... 80
Event Condition 2 ............................................................... 80
Event Condition 3 ............................................................... 81
Event Condition 4 ............................................................... 81
Event Condition 5 ............................................................... 81
Data Features 83
Upstream Service Flow Usage ........................................................ 83
About the Ethernet Interface ........................................................... 83
About RIP ........................................................................................ 83
Suppor ted eMTAs ..................................................................... 84
Compliance ............................................................................... 84
WTM552/WTM652 Considerations ........................................... 84
Provisioning Features 85
General Provisioning Information .................................................... 85
OUI Ranges .............................................................................. 85
Queue Depth Size Control ........................................................ 85
Jitter Buffer Configuration ......................................................... 85
ToD Resynchronization ............................................................. 86
Adjusting FSK and CAS Gain Levels ........................................ 86
Proprietary Provisioning Modes ...................................................... 87
Provisioning Method Indicator MIB ........................................... 88
Provisioning Status MIB ............................................................ 88
Selecting a Provisioning Mode ........................................................ 88
About ARRIS Enhanced Firmware Loading .................................... 89
Upgrade Process ...................................................................... 89
Enhanced Firmware Loading Options ...................................... 91
ArrisCmDevSwAdminStatus MIB Feature Switch ..................... 91
ArrisCmDevSwTable MIB .......................................................... 92

Contents ix
Ser ver Address Object Interactions .................................... 93

arrisCmDevSwHwModel Values ......................................... 94
Example Lineup ........................................................................ 94
Example Configuration File Excerpt ......................................... 95
Rejecting a Download Request ................................................. 95
Upgrading from NCS to SIP Loads ........................................... 95
Dual-Mode Operation ...................................................................... 96
Post-Provisioning ............................................................................. 97
Companion Utilities ......................................................................... 97
PacketACE ................................................................................ 97
Provisioning Trial and Testing Features ........................................... 97
Maximum Scheduled Codes (MSC) .......................................... 97
Management and Troubleshooting Features 99

Management and Status Monitoring Interfaces ............................... 99
MTA Monitoring Features .............................................................. 100
End-of-Call Statistics ............................................................... 100
Monitoring of Quarantined Events .......................................... 101
Per-Call Syslog Reporting ....................................................... 101
Signaling Trace ....................................................................... 101
Provisioning Status MIB .......................................................... 101
DHCP Information Over SNMP ............................................... 101
Line Card Status MIB .............................................................. 104
Voice Quality Monitoring ......................................................... 104
CallP Signalling Message Trace Logs ..................................... 109
DHCP Message Logging ........................................................ 110
Power Outage Recovery and Timing ............................................. 110
Batter y Management ..................................................................... 111
Initial Battery Charging ........................................................... 111
Boot from Battery (Model 6 and newer) .................................. 111
Batter y Telemetr y .................................................................... 111
Power Failure Operation ......................................................... 112
LED Changes .......................................................................... 112
LED Operation Changes During Battery Charging ........... 113
Installer Visual Indication of Foreign Loop Voltage ........... 113
Batter y Mismatch Indication ............................................. 113
Batter y Status Monitoring ....................................................... 113
SNMP Access Policy and Community Strings ............................... 114
System Descriptor MIB Object ...................................................... 114
Example .................................................................................. 115
Troubleshooting Interfaces ............................................................ 115
Loop Diagnostics ........................................................................... 116
Limitations ............................................................................... 117
For More Information .............................................................. 117
Index 119

x Contents

About This Document
This document describes standards compliance, telephony features, and data

features of Touchstone® Telephony TS6.1 firmware.
Some features described in this document may not be fully tested and sup-
ported in your specific firmware release version. Where possible, features
supported only by specific versions are indicated in this document. See the
Release Notes/Letter of Operational Considerations accompanying your
firmware for further details.
Audience
If you are evaluating Touchstone Telephony products for use in your net-
work, you should read this entire manual.
This manual assumes that you have a basic understanding of DOCSIS and
PacketCable standards, and a working knowledge of cable data and telephony
networks.
About the Touchstone Telephony Firmware
Touchstone Telephony TS6.1 firmware provides operating, maintenance, and

troubleshooting functions for the following ARRIS eMTAs:
• Touchstone Telephony Modems, models 4, 5, and 6
• Touchstone Telephony Ports, model 4
The following Touchstone hardware requires the use of TS4.4 or earlier ver-
sions of Touchstone firmware:

xii About This Document
• TM102
• TM202
• TP204
• TP302
• TP304
Subscriber Touchstone Telephony TS6.1 firmware provides:

Interface • support for LED status indicators
• PacketCable-compatible interfaces to data and telephony ports
• a web-based status monitoring and troubleshooting interface
In this Document
This document contains the following information:

• Chapter 1, ‘‘Overview,’’ provides a brief overview of the Touchstone
Telephony product line.
• Chapter 2, ‘‘Compliance,’’ outlines Touchstone Telephony DOCSIS,
Euro-DOCSIS, and PacketCable compliance, and describes ARRIS-
proprietary extensions to the standards.
• Chapter 3, ‘‘Telephony Features,’’ describes telephony features.
• Chapter 4, ‘‘Provisioning Features,’’ describes provisioning features.
• Chapter 5, ‘‘Management and Troubleshooting Features,’’ describes
management and troubleshooting features.
Terminology
The following is a list of terms and abbreviations used in this manual.

Best Effort (BE)
The default Service Flow type. BE is intended for non-telephony
applications, where jitter and latency are of little importance.
Call Agent (CA)
A device that maintains call state, and controls the line side of calls.
The CA is often a portion of a Call Management Server (CMS).

About This Document xiii
Call Management Server (CMS)

A generic term for the devices connecting a VoIP network to the
PSTN. A CMS includes both a Call Agent (CA) and the PSTN
gateway, and controls audio call connections.
CALFV
Call Forwarding Unconditional (dialing feature).
CallP
Call Processing. Firmware controlling the current state of a call.
CALRT
Call Return (dialing feature).
CAS
CPE Alert Signal. A method of encoding signaling information in a
telephone connection.
CBR
Constant Bit Rate. A data service that provides a guaranteed, fixed
amount of bandwidth. Technically, it is not possible to provide
actual CBR services over an IP network due to factors such as con-
tention and latency. UGS service flows and low-latency hardware
such as the ARRIS™ Cadant® C4 CMTS, however, can provide an
approximation suitable for carrier-grade telephone service.
CFFDS
Call Forwarding Unconditional Disable (dialing feature).
CIDTE
Caller iD Temp Enable (dialing feature).
Classifier
Rules used to classify packets into a Service Flow. The device com-
pares incoming packets to an ordered list of rules at several protocol
levels. Each rule is a row in the docsQosPktClassTable. A
matching rule provides a Service Flow ID (SFID) to which the
packet is classified. All rules need to match for a packet to match a
classifier. Packets that do not match any classifiers are assigned to
the default (or primary) Service Flow.
CLWPD
Call Waiting Permanent Disable (dialing feature).
CM
Cable Modem. Typically a device installed at the subscriber
premises that provides a high-speed data (Internet) connection
through the HFC network.
CMTS
Cable Modem Termination System. A device at a cable headend
that connects to cable modems over an HFC network to an IP net-
work.

xiv About This Document
CODEC
Coder-decoder. In VoIP products, one of several possible schemes
of converting audio (i.e. a phone call) to digital data and vice versa.
Attributes of a codec include fidelity (e.g. voice quality), bandwidth,
and latency.
CPE
Customer Premises Equipment. Subscriber-owned equipment con-
nected to the network. Technically, a cable modem, MTA, or NIU
falls into this category, although many operators do not designate
them as such.
CVC
Code Verification Certificate, an encryption key that allows secure
downloading of encrypted firmware over the HFC network.
DHCP
Dynamic Host Configuration Protocol. An IP protocol used to pro-
vide an IP address and location of services (such as DNS and TFTP)
needed by a device connecting to the network.
DNS
Domain Name Service (Server). An IP service that associates a
domain name (such as www.example.com) with an IP address.
Downstream
In an HFC network, the direction from the headend to the sub-
scriber. Some older cable documentation may refer to this as the
forward path.
DOCSIS
Data Over Cable Service Interface Specification. The interoperabil-
ity standards used for data communications equipment on an HFC
network.
DQoS
Dynamic Quality of Service. The mechanism by which the MTA
chooses the proper quality of service settings for a particular service
flow. Touchstone firmware supports both full PacketCable DQoS
and ‘‘DSx QoS’’ for interoperability with non-PacketCable compli-
ant networks.
eMTA
Embedded MTA. A device, such as the ARRIS Touchstone Tele-
phony Modem, that contains both an MTA and a cable modem.
Euro-DOCSIS
The European version of DOCSIS. Euro-DOCSIS specifies an
8 MHz downstream bandwidth (vs. 6 MHz for DOCSIS); other
minor differences exist as well.

About This Document xv
FQDN
Fully Qualified Domain Name. The name used to identify a single
device on the Internet. See RFC2821 for details.
FSK
Frequency Shift Keying. A method of encoding signaling informa-
tion in a telephone connection.
Global Universal Provisioning Interface (GUPI)
A PacketCable subset, intended to accommodate a wide range of
partially-compliant equipment. SNMP communication uses
SNMPv1 or SNMPv2, with INFORM disabled. IPsec and media
encryption are disabled.
Headend
The ‘‘central office’’ in an HFC network. The headend houses both
video and data equipment. In larger MSO networks, a ‘‘master’’
headend often feeds several ‘‘remote’’ headends to provide distrib-
uted services.
HFC
Hybrid Fiber-Coaxial. A broadband, bi-directional shared media
transmission system using fiber trunks between the headend and
fiber nodes, and coaxial distribution cable between the fiber nodes
and subscriber premises.
IANA
Internet Assigned Numbers Authority. The coordinating body that:
assigns IP addresses to regional Internet registries; recognizes top-
level domains; and assigns protocol numbers for well-known ser-
vices.
Jitter
Variance in packet arrival time. Jitter is a factor in applications such
as telephony, where the originating device sends packets at a con-
stant rate.
Latency
The time required for a signal element (e.g. packet) to pass through
a device or network.
KDC
Kerberos Key Distribution Center.
LCO
Local Connection Options. A structure that describes the character-
istics of the media data connection from the point of view of the
CMS creating the connection.
MAC
Media Access Control. A general term for the link-level networking
layer and associated protocols. MAC protocols used in HFC data
networks include Ethernet, the DOCSIS RF interface, and Home-
PNA.

xvi About This Document
Maintenance window
The usual period of time for performing maintenance and repair
operations. Since these activities often affect service to one or more
subscribers, the maintenance window is usually an overnight period
(often 1 a.m. to 5 a.m. local time).
MD5
Message Digest 5. A one-way hashing algorithm that maps variable
length plaintext into fixed-length (16-byte) ciphertext. MD5 files,
built by a provisioning server, contain provisioning data for each
NIU on the network.
MIB
Management Information Base. The data representing the state of a
managed object in an SNMP-based network management system.
Often used colloquially to refer to a single object or variable in the
base; e.g. ‘‘the lcCmtsUpMaxCbrFlows MIB.’’
MSO
Multi-System Operator. A cable company that operates multiple
headend locations, usually in several cities.
MPI
Micro-Processor Interface. An internal Touchstone Telephony
Modem component.
MTA
Multimedia Terminal Adapter. A subscriber premises device that
contains the network interface, codecs, and all signalling and encap-
sulation functions required for telephony transport, CLASS features
signalling, and QoS signalling. The MTA is an integral part of
Touchstone Telephony embedded MTA (eMTA) products.
NCS
Network-based Call Signaling. The PacketCable protocol used to
control calls.
NIU
Network Interface Unit. A generic term for a device providing data
and telephony connections at a subscriber site. Also referred to as
embedded MTA (eMTA).
NMS
Network Management System. Software, usually SNMP-based,
that allows you to monitor and control devices on the network. In a
VoIP network, managed devices include NIUs, CMTS, servers,
PSTN interface devices, and routers. An NMS works by reading
and setting values of MIB variables presented by each device.
NVRAM
Non-volatile RAM. A block of non-volatile memory used to store
settings that should persist across reboots.

About This Document xvii
Off-net
A call between a Touchstone phone line and a line on the PSTN.
On-net
A call between two Touchstone phone lines. Depending on the
CMS used, the connection may be established directly between the
MTAs or be routed through a gateway.
PacketCable
A CableLabs-led initiative aimed at developing interoperable inter-
face specifications for delivering advanced, real-time multimedia
services over two-way cable plant.
PCM
Pulse Code Modulation. A commonly employed algorithm to digi-
tize an analog signal (e.g. voice) into a digital bit stream using sim-
ple analog to digital conversion techniques. PCM is employed in
the popular G.711 codec.
PLO
Permanent Lock-Out. A line card may enter this state when left off-
hook with no connection after a certain amount of time.
POS
Point of Sale (terminal). Typically, an electronic cash register.
PSTN
Public Switched Telephone Network.
QAM
Quadrature Amplitude Modulation. A method of modulating digital
signals onto an RF carrier, involving both amplitude and phase cod-
ing. QAM16 modulation encodes four digital bits per state and is
used on upstream carriers; QAM64 and QAM256 encode six or
eight bits (respectively) for use on downstream carriers.
QoS
Quality of Service. An attribute of a Service Flow, defining limita-
tions or guarantees for data rate, latency, and jitter.
QPSK
Quadrature Phase Shift Keying. A method of modulating digital
signals onto an RF carrier, using four phase states to encode two
digital bits.
Quarantine
A state where an endpoint (phone line) may potentially buffer
events. Events not quarantined are processed normally. Processing
of quarantined events may be delayed, potentially indefinitely.
RF
Radio Frequency.

xviii About This Document
SDP
Session Description Protocol. SDP describes multimedia sessions
for the purposes of session announcement, session invitation, and
other forms of multimedia session initiation.
Service Flow
A unidirectional, MAC-layer transport service that provides traffic
shaping, policy, and priority according to QoS parameters defined
for the flow.
SFID
Service Flow ID. A number used to identify a particular Service
Flow.
SLAC
Subscriber Line Audio Circuit. An internal Touchstone Telephony
Modem component.
SIP
Session Initiation Protocol. A signaling protocol for Internet con-
ferencing, telephony, presence, events notification and instant mes-
saging.
SNMP
Simple Network Management Protocol.
TFTP
Trivial File Transfer Protocol. Used in DOCSIS networks to trans-
fer firmware and provisioning files to network devices.
TM
Telephony Modem.
Uniform Resource Identifier (URI)
A way to identify a specific phone line for an MTA. For example
sip:<phone number>@<IP address or domain>.
Unsolicited Grant Service (UGS)
A Service Flow type used for applications such as telephony in
which latency and jitter are critical. Packets have a fixed size and
interval. Within the constraints of IP networking, UGS flows
attempt to deliver a constant bit rate (CBR) stream of data.
Upstream
The path from a subscriber device to the headend. Some older cable
documentation may refer to this as the return path or reverse path.
VACM
View-based Access Control Model. An SNMP MIB for controlling
access to management information.
VF
Voice Frequency.

About This Document xix
VoIP
Voice Over Internet Protocol. A generic term for technology that
allows telephone calls to be made across an Internet connection
instead of a traditional two-wire copper connection.
WTM
Wireless Telephony Modem.

xx About This Document

1 Overview
This chapter describes Touchstone Telephony hardware and firmware fea-

tures.
Touchstone Telephony eMTAs (also referred to as Embedded MTAs or
eMTAs), provide the subscriber connection to the HFC IP network.
Touchstone eMTAs running TS6.1 firmware comply to the following stan-
dards:
• DOCSIS 1.1 and DOCSIS 2.0
• Euro-DOCSIS 1.1 and Euro-DOCSIS 2.0
• PacketCable 1.0 and Euro-PacketCable 1.0

2 Chapter 1
Touchstone Telephony Port
The ARRIS Touchstone Telephony Ports, models TP402A and TP404A, are
outdoor network-powered eMTAs that provide:
• up to four lines of telephony service
• cable modem functionality with 10/100BaseT (Model 4) or 10BaseT
(earlier models) Ethernet connections
• CATV passthrough and internal disconnect
The Touchstone Telephony Port is the eMTA of choice for operators who
want to provide primary line service in small business and home environ-
ments.

Overview 3
Note: TS3.2.5 or later versions of Touchstone firmware are required for the
TP302A and TP304A Telephony Ports. TS4.4.8 or later versions of Touch-
stone firmware are required for TP402 and TP404 Telephony Ports. TS6.1
does not support Model 3 or earlier Telephony Ports.

4 Chapter 1
Touchstone Telephony Modems
This section describes the Telephony Modems supported by the current

release of Touchstone firmware.
Model 4 Model 4 Telephony Modems provide one (TM401) or two (TM402) lines of
telephony service and 10/100BaseT Ethernet and USB1.1 data connections.
The TM402 Telephony modems are available in AC-only and battery-backup
models with one or two Li-Ion batteries, allowing a more compact form fac-
tor and enhanced hold times (up to 20 hours of idle backup power).
Model 4 (AC-only) Model 4 (with battery backup)
Supported models include: TM401A, TM401B, TM402A, TM402B,

TM402G, TM402H, and TM402P.

Overview 5
Model 5 Model 5 Telephony Modems provide telephony, 10/100BaseT Ethernet and

USB 1.1 data connections, and optional battery backup.
Model 5 Telephony Modems are available in single-line (TM501), dual-line
(TM502), and four line (TM504) versions, as well as a model (WTM552)
with a wireless router for use in home networking applications.
Model 5 (AC-only) Model 5 (with battery backup)

TM502G, TM502H, TM504G, TM504H, WTM552A, WTM552B,
WTM552G, and WTM552H.
Model 5 Multi-line Multi-line Telephony Modems are indoor units that provide eight or twelve
lines of telephony service, and one 10/100BaseT Ethernet data connection.
These Telephony Modems are intended to provide telephony service in a
small office or multi-dwelling unit.

6 Chapter 1
Supported models include: TM508A and TM512A.
Model 6 Model 6 Telephony Modems are the latest generation of ARRIS eMTAs, pro-
viding improved technology and features, including expanded downstream
frequency (88 MHz to 1 GHz) support, as well as a model (WTM652) with a
wireless router for use in home networking applications. As with previous
generations, Model 6 Telephony Modems provide telephony, 10/100BaseT
Ethernet and optional USB 1.1 data connections, and optional battery
backup.

Overview 7

TM602G, TM602H, TM604G, WTM652A, TM652B, and WTM652G.
Core Functionality
Touchstone firmware provides the following core functionality:

• Multiple provisioning methods (see the Touchstone Telephony Provi-
sioning Guide for a list of provisioning modes)
• Support for up to 16 Upstream Service Flows (SFIDs)
• Support for 10ms and 20ms packetization rates (see ‘‘CODECs and
Packetization Rates Supported’’ on page 46 for details)
• Automatic recovery following power failure conditions
• Automatic recovery following restoration of RF cable cut conditions
• Support of SNMP v1/v2c and v3 coexistence, with up to 16 permitted
entries/rows (see the Touchstone Telephony Management Guide for
details)
• CPE Ethernet — 10/100 BaseT / full-duplex / auto-negotiate function-
ality.
• CPE USB 1.1 — fully supported
• USB to Ethernet bridging functionality
• Internet (WAN) Isolation / Standby Switch functionality (see the Touch-
stone Telephony Provisioning Guide for details)
• Battery State Telemetry Notification (see the Touchstone Telephony
Management Guide for details)

8 Chapter 1
TS6.1 Functionality
The TS6.1 firmware provides the following functionality:
Compliance and TS6.1 provides the following compliance and interoperability features:
Interoperability • Standards compatibility as follows:
– DOCSIS 2.0 and DOCSIS 1.1, including CableLabs CW53 ECNs
– PacketCable 1.0, including CW46 ECNs
– Euro-DOCSIS 2.0 and Euro-DOCSIS 1.1, including ECW28 ECNs
– Euro-PacketCable 1.0, including ECW28 ECNs
– SNMPv3, IPsec, and encrypted voice traffic as required by PacketCa-
ble specifications
– Supports RFC 2833 (DTMF relay) functionality, a method for carry-
ing DTMF and other telephony signals and events in RTP packets,
instead of sending audio tones over the network. This functionality
is especially important when using highly-compressed CODECs such
as G.729, which may distort DTMF tones.
The MTA signals RFC 2833 support by specifying ‘‘telephone-
event’’ in its list of available CODECs during negotiation. For SIP
loads, add ‘‘telephone-event’’ to the end of the CODEC list in the
sipCfgProvisionedCodecArray object.
• Interoperability with ARRIS and other vendors’ CMTS products.

• Supports a variety of non-PacketCable compliant provisioning software
and cable data equipment, allowing Touchstone Telephony eMTAs to
interoperate with a wide range of equipment.
• Fully NCS compliant.
• Optional SIP signaling protocol support (available through a specific
SIP firmware load).
• Supports PacketCable Multimedia QoS for interoperability testing and
lab trials (TS4.4 MSUP3 and later loads; see ‘‘SIP eMTA Support’’ on
page 76).
• End-to-end DQoS, providing an added layer of authentication, as well
as DSx DQoS support (see the Touchstone Telephony Provisioning
Guide for details).

Overview 9
• DOCSIS 2.0 auto-detect (patent pending)—ARRIS eMTAs can auto-

matically configure themselves for DOCSIS 2.0 operation based on the
presence of DOCSIS 2.0 upstreams.
• DOCSIS1.0 fragmentation support for use with certain older DOCSIS
1.0 CMTS units that also support fragmentation.
Hardware Support TS6.1 provides the following Touchstone hardware support.

• Supports Model 4, Model 5, and Model 6 Touchstone Telephony
Modems, including multi-line Telephony Modems.
• Supports Model 4 Touchstone Telephony Ports.
• Supports an Ethernet interface to CPE.
• Supports a USB interface to CPE (on eMTAs equipped with USB).
Telephony TS6.1 provides the following telephony-related functionality and support:

Functionality • Supports G.711, G.728, G.729, G.729E, G726-16, G726-24, G726-32,
and G726-40 CODECs.
• Supports access to 911 (emergency), 411 (directory), 311 (non-emer-
gency), and 611 (repair) services.
• Dial pulse support for all eMTAs at 10pps or 20pps ±2pps for networks
using either GR-303 gateways (patent pending) or soft switches.
• Support for dialup fax and modem connections, disabling echo cancel-
lation upon detecting fax or modem start tones.
• Dedicated fax line support.
• An adaptive jitter buffer minimizes voice delay based on network con-
ditions.
• Supports KDC ticket caching for lower outage recovery times.
• Selectable sinusoidal or trapezoidal ringing wave forms to compensate
for CPE incompatibility. Sinusoidal is default for North American tem-
plates; other templates default to trapezoidal.
Provisioning TS6.1 provides a variety of provisioning options and functionality as follows:

Functionality • Full PacketCable provisioning with SNMPv3 Network Management
capabilities.
• Supports several ARRIS-proprietary provisioning modes for use with
PacketCable-compliant and non-compliant provisioning software.

10 Chapter 1
• ARRIS Enhanced Firmware Downloading feature (patent pending) that

allows customers to match different firmware loads to multiple Touch-
stone hardware products in a single configuration file. Firmware down-
loads are not applied until all lines are on-hook. See ‘‘About ARRIS
Enhanced Firmware Loading’’ on page 89 for details.
• Secure firmware downloading, conforming to the DOCSIS 1.1 specifi-
cation.
• Ability to accept firmware download requests while a call is in
progress, applying the downloaded firmware only after all lines have
gone idle for 30 seconds.
• Supports DHCP option 122 or option 177 provisioning of MTA IP
addresses.
• Support for the PacketCable Service Provider root certificate, the Pack-
etCable Service Provider Test root certificate, and the ability to down-
load other Service Provider root certificates (see the Touchstone Tele-
phony Provisioning Guide for details).
• Configurable CallP feature to disable IPsec on CMS redirection.
• Retains the following settings (made using SNMP) over restarts: loop
current, ringing waveform, phase reversed modem tone, dynamic equal-
izer.
Management and TS6.1 provides the following management and troubleshooting functionality:
Troubleshooting • PacketCable 1.0-compatible alarm and log interface.
Functionality
• Battery telemetry support (allows monitoring of battery status at the
headend).
• Web-based status monitoring and troubleshooting interface.
• Maintain loop idle voltage management output from the Telephony
Modem when the telephony service connection is interrupted for short
time durations (see ‘‘Loop Voltage Management Option’’ on page 67).
• Supports Telnet and encrypted SSH access to a troubleshooting com-
mand line interface (CLI).
• Support for automatically timing out Telnet or SSH sessions after a cer-
tain amount of idle time.
• Automatic optional disabling of access to Telnet or SSH sessions after
exiting the session.
• Optional persistent logging capability after exiting a Telnet or SSH ses-
sion.

Overview 11
• PacketACE support for ARRIS Enhanced Firmware Downloading func-

tionality TLVs.
• Simple DHCP server for improved debugging.
• Supports end of call statistics (see ‘‘End of Call Connection Statistics’’
on page 55).
• Supports Voice Quality Metric reporting.
• Provides MGCP and DHCP message trace logs.
• Support for loop diagnostics (see ‘‘Loop Diagnostics’’ on page 116 for
details).
• Support for periodic ToD resynchronization (see ‘‘ToD Resynchroniza-
tion’’ on page 86 for details).
Data Functionality TS6.1 supports the following general data transport functionality:
• Supports IPv6 bridging of data packets.
• Supports RIPv2 routing functionality for use in business services and
similar applications.
• Supports the TurboDOX protocol, increasing performance of TCP
applications such as FTP and HTTP.

12 Chapter 1
New Features in TS6.1 MSUP
The following new features are available in TS6.1 MSUP releases.
T.38 Image and When originating a call, a SIP T.38 device may provide offers with both
Audio Offer Han- image and audio media in INVITE and reINVITE messages. When pre-
dling sented with both media offers, Touchstone firmware behaves as follows
depending on the version:
• Versions prior to TS6.1 MSUP3 prefer image media and disable other
media.
• TS6.1 MSUP3 and newer versions choose the media type depending on
whether or not the eMTA detects a fax tone. If the eMTA detects a fax
tone, it selects image media; otherwise, it answers with active audio.
SIP BYE Delay In a PSTN environment, the called party typically can hang up for a few sec-
onds without disconnecting the call. Touchstone SIP loads, TS6.1 MSUP3
and newer, can provide the same behavior by setting the sipCfgPortCall-
ByeDelay object.
Slovenia Template TS6.1 MSUP3 supports definitions for Slovenia tones and ring cadences.
See the Touchstone Telephony Provisioning Guide for the default definitions.
WTM652 Support TS6.1 MSUP2 introduces support for the WTM652A/B/G Telephony
Modem, a two-line Telephony Modem with four Ethernet ports and 802.11
wireless connectivity. To support the new model, TS6.1 MSUP introduces a
new load variant: MODEL_6_WR.
The WTM652B Telephony Modem supports dual-mode operation.
Dual-Mode En- TS6.1 MSUP2 and later versions of Touchstone firmware provide support for
hancements mixed DOCSIS environments (that is, both North American and Euro-DOC-
SIS downstreams on the same plant). A dual-mode Touchstone device
ranged on one annex can be moved to the other annex type using Down-
stream Frequency Override in a RNG-RSP message.

Overview 13
Persistent Line Operators may set a line status that persists across resets. This can be used to
Status hold a line out of service.
The arrisMtaDevPersistentLineStatus MIB object, and the equivalent CallP
CLI command spls, control persistent line settings.
RTP ‘‘End of TS6.1 MSUP provides a new MIB object, arrisMtaDevDTMFEndEvent-

Event’’ Duration ForceAscending, to enable or disable the ability to set the RFC 2833 DTMF
Control ‘‘end event’’ duration to be at least as big as the last ‘‘interim’’ event dura-
tion.
SIP-specific En- The following new features are specific to SIP loads.
hancements
SIP Hook Flash Reporting
TS6.1 MSUP now supports SIP hook flash reporting using the standard SIP
INFO message. An earlier (non-standard) method is still supported for back-
wards compatibility.
T.38 Call Enhancement
When making a SIP T.38 call, the calling party might provide offers with
both image and audio media in INVITE and reINVITE messages. In previ-
ous loads, the SIP eMTA gave preference to image and disabled all other
media.
In TS6.1 MSUP SIP loads, When the eMTA receives an offer with both
active audio and image/t38, and fax tone has not been detected, then the
MTA answers with active audio. If the MTA detects a fax tone, it answers
with active image/t38. This changes the existing message flow so that the
SIP eMTA always sends the offer when switching to T.38 and switching back
from T.38, regardless of whether the MTA originated the fax.
No provisioning is necessary to enable this feature.
New and Changed The following MIB objects were introduced or changed in TS6.1 MSUP
MIB Objects releases.
sipCfgPortCallByeDelay
The time, in seconds, that the MTA waits after the subscriber hangs
up before sending a BYE signal. Applies only when the subscriber
is the called party, and only to Touchstone SIP loads.
arrisMtaDevPersistentLineStatus
Allows operators to set a line down, with the status persisting across
resets. This object cannot be set in a configuration file.

14 Chapter 1
sipCfgSipFeatureSwitch
Adds several new bit settings:
0x00000020:
(MSUP1) signals hook flash events using the standard SIP
INFO message.
0x00000010:
(MSUP3)
0x00000004:
(MSUP3)
0x00000002:
(MSUP3)
0x00000001:
(MSUP3)
arrisWrmDevWlanApPowerLevel
Sets the WRM wireless power range.
arrisWrmDevWlanApConfigChannel
A new value, auto(0), specifies auto-selection of an unused wireless
channel.
arrisWrmDevWlanQoSConfigEnable
Enables bandwidth limitations on WRM Ethernet and wireless inter-
faces.
arrisWrmDevWlanQoSConfigTotalBandwidth
Sets the maximum interface speeds for the entire WRM.
arrisWrmDevWlanQoSConfigHomeBandwidth
Sets the maximum interface speed for the WRM Ethernet and
SSID1 wireless interfaces.
arrisWrmDevWlanQoSConfigPrivateBandwidth
Sets the maximum interface speed for the WRM SSID2 wireless
interface.
arrisWrmDevWlanApIsolationInter
Enables or disables direct communication between CPE devices on
the same SSID.
arrisWrmDevWlanApIsolationExtra
different SSIDs on the same WRM.
arrisWrmDevWlanApConfigLanAccess
the wireless interface and devices on the Ethernet ports (including
the WRM configuration web pages).

Overview 15
New or Changed The following CLI commands were introduced or changed in TS6.1 MSUP
CLI Commands releases.
CallP sub-mode:
spls: Sets a persistent line status (equivalent to using the arrisM-
taDevPersistentLineStatus MIB object).
dst: Adds a new column, ‘‘serviceStatus,’’ to display the persistent

line status.
WRM commands:
redirect set wlan power: Sets the WRM wireless power range.
redirect set wlan channel: A new value, auto, specifies auto-selec-

tion of an unused wireless channel.
redirect set qos mode: Enables bandwidth limitations on WRM
Ethernet and wireless interfaces.
redirect set qos speed: Sets the maximum interface speeds for
WRM, Ethernet, and wireless interfaces.
redirect set wlan isolation inter: Enables isolation of CPEs con-
nected to the same SSID on the WRM.
redirect set wlan isolation extra: Enables isolation of CPEs con-
nected to different SSIDs on the same WRM.
redirect set wlan isolation lan access: Enables isolation of CPEs
connected to WRM Ethernet ports.
MAIN mode:
dsxparams: Controls the display of DSX trace messages when
DSX tracing is active (using replevl 15).
New Features in TS6.1
The following new features are available in TS6.1.
Updated Hardware TS6.1 introduces support for the following Telephony Modem models:
Support • TM601A/B single-line Telephony Modem
• TM604G/H four-line Telephony Modem
• TM608G eight-line Telephony Modem
• DTM602G two-line Telephony Modem with DECT6.0 cordless handset

16 Chapter 1
• TM601B and TM602B dual-mode (DOCSIS/Euro-DOCSIS) Telephony

Modems
• Updated TM602 Telephony Modem hardware, providing enhanced
power-save capability, extended downstream range to 1 GHz, and wide-
band CODEC support
TS6.1 also supports new battery types:
• BPB044S (4-cell, 4400 mAh)
• BPB088S (8-cell, 8800 mAh)
See the Touchstone Battery Reference for complete details about battery sup-
port.
New General TS6.1 introduces the following new general features.

Features
RIPv2 Support
TS6.1 supports RIPv2 routing on Model 4, Model 5, and Model 6 Telephony

Modems. Functionality is the same across all models, but the WTM552 and
WTM652 provide a different management and provisioning interface. See
the Touchstone Telephony Provisioning Guide and the Touchstone Telephony
Management Guide for details.
Power-Save Enhancements (Model 6 and Newer)
TS6.1 provides the following power-save enhancements for Model 6 and

newer Telephony Modems to extend battery hold-up times:
• Receiver power-save
• DSP clock frequency reduction
ToD Enhancements
TS6.1 provides the following enhancements to Time of Day (ToD) support:

• The arrisCmDevTODTimeOffset object provides the ability to update
the time offset, used to adjust for Daylight Savings Time shifts. This
setting applies to both the CM and MTA clocks.
• The arrisCmDevDSTPolicy MIB object provides the ability to set Day-
light Saving Time policy based on the month, weekday and time in each
year, eliminating the need to update the DHCP time offset option.

Overview 17
WTM552- and The following features are specific to the WTM552 and WTM652 Telephony
WTM652-Specific Modems.
Features
Provisionable Wireless Power Range
The wireless transmit power level can be configured in ‘‘low,’’ ‘‘medium,’’

and ‘‘high’’ power ranges as follows:
Power Level Range (dB) Average (dB)
Low 10–14 12
Medium 12–16 14
High 14–18 16
You can use either the redirect set wlan power CLI command, or the
arrisWrmDevWlanApPowerLevel MIB object to set the power range.
Wireless Channel Auto-Detect
The WRM can automatically detect and set itself to an otherwise unused
wireless channel. This is useful for deployment in high-density housing or
other areas with many wireless networks.
The wireless channel can be set through the WRM ‘‘Channel and SSID’’ web
page, the redirect set wlan channel CLI command, or the arrisWrmDe-
vWlanApConfigChannel MIB object.
Provisionable Bandwidth Limits
TS6.1 MSUP releases provide the ability to configure bandwidth limits on

the LAN and wireless LAN interfaces. This can be used to prevent any one
device or interface from consuming too much bandwidth relative to other
interfaces.
Bandwidth limits can be set using the redirect set qos mode and redirect
set qos speed CLI commands, or the arrisWrmDevWlanQoSConfigEn-
able, arrisWrmDevWlanQoSConfigTotalBandwidth, arrisWrmDevWlan-
QoSConfigHomeBandwidth, and arrisWrmDevWlanQoSConfigPrivate-
Bandwidth MIB objects.
LAN/WLAN Isolation
Touchstone firmware can be provisioned to prevent CPE devices, connected

to the WRM LAN or wireless interfaces, from direct communication. When
isolation is active, all traffic between CPEs must travel through the cable
interface. The following types of CPE-CPE communications may be
affected:

18 Chapter 1
• Inter-WLAN isolation: prevents inter-CPE communication in the same

SSID
• Extra-WLAN isolation: prevents direct communication between CPEs
in one SSID with CPEs in another SSID
• LAN access: prevents direct access to the WRM LAN IP and to CPEs
connected to LAN Ethernet ports
Isolation can be configured using the redirect set wlan isolation inter, redi-
rect set wlan isolation extra, and redirect set wlan isolation lan access
CLI commands, and the arrisWrmDevWlanApIsolationInter, arrisWrmDe-
vWlanApIsolationExtra, and arrisWrmDevWlanApConfigLanAccess MIB
objects.
Improved Access to WRM Web Pages
Connecting to IP address 192.168.100.1 has always accessed the trou-

bleshooting pages. The WRM pages are accessible at 192.168.2.1 by default,
but this often requires manually configuring a local PC to access the WRM
pages.
TS6.1 adds a Wireless Router link to the standard web pages, which places
the WRM pages in a frame. This allows access to both the standard and
WRM pages from the same IP address.
L2TP Support
WTM552 and WTM652 Telephony Modems running TS6.1 firmware sup-

port Internet access using L2TP to the gateway. See the Touchstone Tele-
phony Provisioning Guide for details.
WPA Support
TS6.1 supports Wi-fi Protected Access (WPA and WPA Enterprise), a secu-
rity protocol used on wireless networks. WPA can be configured through the
WRM web pages, CLI, or SNMP.
WRM Provisioning File Error Reporting
TS6.1 provides support to report and help debug provisioning file errors. The
primary tool is the provf.html web page, which shows the following informa-
tion:
• provisioning file name
• time the file was downloaded

Overview 19
• IP address of the TFTP server

• provisioning file status (for example: OK, file not found, error)
• first error found (if any)
To enable and view the provisioning file page, see the Touchstone Telephony
Provisioning Guide.
WRM Reset Button Control
TS6.1 provides a new feature switch to disable the ‘‘reset to factory default’’
functionality of the WRM Reset button. To disable factory resets, set bit 5
(0x04000000) of the arrisCmDevModemFeatureSwitch2 object to 1.
New Telephony TS6.1 introduces the following telephony-related features.

Features
SuperG3 FAX Support
TS6.1 supports SuperG3 FAX transfers for all Model 6 and newer Telephony
Modems, as well as for TM508 and TM512 Telephony Modems. The eMTA
detects a V.8 signal and can negotiate G.711 transport (up to 33.6Kbps) or
T.38.
TS6.1 supports T.38 version 3, which provides V.34 (SuperG3) FAX capabil-
ity, as well as version 0 (supported in previous versions). See Chapter 3 for
details.
NCS Fax-only Line Support
Previous versions of Touchstone firmware supported a fax-only line feature

in SIP loads. In TS6.1, this feature also applies to NCS loads.
The arrisMtaDevEndPntFaxOnlyLineTimeout MIB object replaces the SIP-
only sipCfgPortFaxOnlyTimeout object, which is still present for backward-
compatibility. The object is indexed by line number; for example, arris-
MtaDevEndPntFaxOnlyLineTimeout.1 applies to line 1.
To enable fax-only support, set the object that applies to the line to the time-
out value, in seconds. The timer starts when the line connects; if the timer
expires before the line receives a send or receive FAX tone, the Telephony
Modem drops the call.
SIP Timer Enhancements
SIP loads provide extended control over various session timers. The follow-
ing is a list of new MIB objects that allow tuning of SIP timers:

20 Chapter 1
sipCfgSessionExpires
Specifies the preferred session expiry timeout, in seconds, sent in
the SIP Invite message. The default is 1800 seconds. Set this object
to 0 to allow the proxy to control the session expiration timer set-
tings.
sipCfgRegExpires
Specifies the preferred registration expiry timeout, in seconds, sent
in the SIP Register response. The default value is 0, which omits
the timeout from the SIP Register response.
When this object is set to a non-zero value, The actual timeout is the
lesser of this value and the expiry time returned by the registrar in
the 200 OK message.
SIP Penalty Box Enhancement
TS6.1 allows proxy entries in the SIP Penalty Box to time out after a speci-
fied number of hours.
SIP Post-Provisioning Enhancement
TS6.1 supports SIP post-provisioning without taking lines out of service. In

previous versions, post-provisioning could result in a dropped call.
Caller ID Configuration Enhancements
TS6.1 modifies the arrisMtaDevDefaultReasonNoCIDName object to pro-

vide an excludeName(4) option to send ‘‘no name’’ using MDMF format
without name parameters.
The new arrisMtaDevOffHookFskDelay object specifies the time, in mil-
liseconds, that the MTA delays transmitting FSK tones after receiving the
ACK from the CPE. The defaults depend on the load type and country tem-
plate:
• EURO loads: 100ms (T12 timer value)
• NA loads: 261ms (previous default)
• Israel country template (EURO and NA): 50ms
The new CallP scwidDelay command is equivalent to the arrisMtaDevOff-
HookFskDelay object. The command accepts one parameter, the delay time
in milliseconds. Omitting the parameter displays the current delay.

Overview 21
New Provisioning See the Touchstone Telephony Provisioning Guide for details about new pro-
Features visioning features.
New Load Variants
To reduce memory requirements, TS6.1 provides the following model-based

load variants:
MODEL_4_5
Replaces MODEL_4_5_6. Supports all 1- to 4-line Model 4 and
Model 5 Telephony Modems.
MODEL_6
Supports all 1- to 4-line Model 6 Telephony Modems.
MODEL_5_ML
Replaces MODEL_4_5_6. Supports TM508 and TM512 Telephony
Modems.
MODEL_6_ML
Supports TM608 Telephony Modems.
Argentina Line Card Template
TS6.1 defines a line card template for Argentina. To specify this template,
set the ppCfgMtaCountryTemplate object to Argentina(33).
PacketCable 1.5 Provisioning Compliance
TS6.1 supports the following PacketCable 1.5 provisioning modes:

BASIC.1, BASIC.2
These are similar, but not identical, to the ARRIS BASIC provision-
ing modes. The ARRIS modes continue to be supported for back-
ward compatibility.
HYBRID.1, HYBRID.2
These provisioning modes are similar to the ARRIS PacketCa-
bleMinusKDC provisioning mode.
SECURE
The Full PacketCable provisioning mode that has been supported in
previous versions of Touchstone firmware.
SIP Feature Switch Enhancement
Two new SIP Feature Switches are available:

22 Chapter 1
• Set bit 0x00000400 to force the MTA to play a busy tone when a call is
rejected.
• Set bit 0x00000040 to force the MTA to play stutter dialtone when the
subscriber performs a hook flash.
Secondary CM Feature Switch Enhancement
The secondary CM Feature Switch (arrisCmDevModemFeatureSwitch2)

supports the following new switches:
• Set bit 2 (0x20000000) to enable the eMTA to replace older CPE MAC
addresses in the forwarding table with newer addresses. This may be
useful when deploying a Telephony Modem in public-access areas (for
example, a WTM552 or WTM652 in a retail business that wishes to
provide wireless access to its customers).
Note: This feature is non-compliant with DOCSIS specifications, and is
disabled by default.
• Set bit 5 (0x04000000) to disable the ability to reset the WRM to fac-
tory default settings using the WRM Reset button.
Dual-Mode Support (TM601B and TM602B)
TS6.1 supports special ‘‘dual-mode’’ versions of TM601B and TM602B

Telephony Modems. Dual-mode Telephony Modems are capable of config-
uring themselves for either DOCSIS or Euro-DOCSIS operation based on the
type of downstream detected.
Note: TS6.1 MSUP provides dual-mode support for WTM652B Telephony
Modems.
Dual-mode Telephony Modems have both DOCSIS and Euro-DOCSIS cer-
tificates to support secure provisioning on either platform.
The arrisCmDevDualModeDiscoveredMarket object stores the discovered
market (Europe or North America).
Cable Modem Interface Mask Support
TS6.1 supports the Cable Modem Interface Mask (CMIM). The CMIM is a
new field in the upstream classifiers that can be used to filter out traffic based
on the CM interface receiving the packet.

Overview 23
New and Changed See the Touchstone Telephony Troubleshooting Guide for details about new
Troubleshooting troubleshooting features.
Features
VQM Enhancements
TS6.1 updates the Voice Quality Monitoring (VQM) feature to provide NCS
voice metrics to the Call Agent as required by PacketCable 1.5 specifications.
NCS voice metrics now conform to the requirements in the IETF draft-auer-
bach-mgcp-rtcpxr-06 document. TS6.1 also provides partial compliance to
IETF SIP Voice Quality Reporting requirements.
For customers retrieving VQM data through SNMP, reading the new arris-
MtaDevVqmCallNumberIdentifierLastCall MIB object updates the arris-
MtaDevVqmCallNumberIdentifier object to the location of the last call data.
Reset to Factory Defaults
TS6.1 provides the ability to reset a Telephony Modem to its factory default
configuration. The reset can be performed through SNMP (using the arris-
MtaDevRestoreNvmFactoryDefault object).
Historic High Temperature
TS6.1 stores the highest battery charger temperature recorded in non-volatile

memory, with the time and date that it occurred. New MIB objects provide
this information and allows the data to be reset.
Recording the highest temperature is available only when the arrisMtaDev-
PwrSupplyOverTempAlarmControl MIB object is enabled.
TFTP Block Size Configuration
The new arrisCmDevTftpBlkSize MIB object sets the block size for TFTP
downloads. Increasing the block size can shorten the time needed to down-
load files using TFTP.
Valid range: 32 to 1448 octets. The default value is 0, which specifies
512-octet blocks.
New Management For more information about any management-related feature, see the Touch-
Features stone Telephony Management Guide.
TS6.1 supports IPv6 access on the cable modem side of Touchstone eMTAs,
allowing operators to reclaim IPv4 address blocks for use with MTAs.

24 Chapter 1
New and Changed The CM configuration file now supports LongSnmpMib, providing support
MIB Objects for large MIB objects (up to 65535 octets).
The sipCfgSipFeatureSwitch object supports a new switch, with a value of
0x0400, to always play busy tone on receipt of a 486 (Busy) message.
The arrisCmDevModemFeatureSwitch2 object supports a new switch, with

a value of 0x20000000, to enable the eMTA to replace older CPE MAC
addresses in the forwarding table when the table fills up.
The arrisMtaDevRestoreNvmFactoryDefault object, when set to 1, resets
the Telephony Modem to its factory-default configuration.
The arrisCmDevTODTimeOffset object provides the ability to update the
time offset, used to adjust for Daylight Savings Time shifts. This setting
applies to both the CM and MTA clocks.
The arrisCmDevDSTPolicy MIB object provides the ability to set Daylight
Saving Time policy based on the month, weekday and time in each year,
eliminating the need to update the DHCP time offset option.
The arrisCmDevTftpBlkSize object sets the TFTP block size used to down-
load provisioning files and firmware updates.
The arrisMtaDevEndPntFaxOnlyLineTimeout object extends the function-
ality of the sipCfgPortFaxOnlyTimeout object to NCS loads.
The arrisMtaDevDefaultReasonNoCIDName object is modified to add a
new value, excludeName(4), to send ‘‘no name’’ using MDMF format with-
out name parameters.
The arrisMtaDevOffHookFskDelay object sets the time, in milliseconds, that
the MTA delays transmitting FSK tones after receiving the ACK from the
CPE.
The arrisMtaDevVqmCallNumberIdentifierLastCall object updates the
arrisMtaDevVqmCallNumberIdentifier object to the location of the last call
data.
The sipCfgSessionExpires object specifies the preferred session expiry
timeout, in seconds, sent in the SIP Invite message.
The sipCfgRegExpires object specifies the preferred registration expiry
timeout, in seconds, sent in the SIP Register response.
The sipCfgPenaltyBoxTimeout object sets the expiration time, in hours, for
entries in the SIP Penalty Box. When the timer expires, the entry is removed
from the Penalty Box.
The arrisMtaDevSuperG3FaxRelay object determines how to respond to a
V.8 signal on a FAX connection. See ‘‘Super G3 FAX Support’’ on page 67
for details.

Overview 25
The arrisMtaDevT38Timeout object determines how long the MTA waits for
the Call Agent to modify a FAX connection to T.38. If the timer expires, the
MTA reports a T.38 failure.
For dual-mode Telephony Modems, the arrisCmDevDualModeDiscovered-
Market object stores the discovered market mode value. The value returned
is one of: noDualMode(0) (for all non-dual mode Telephony Modems);
europe(1), or northAmerica(2).
WTM552- and WTM652-Specific Additions
The new ARRIS-WRM-DEVICE-MIB allows complete provisioning and

management of the WTM552 or WTM652 Wireless Router Module (WRM).
The following object is equivalent to the sdc save command.
arrisWrmDevSaveSettings
If set to true(1), the WRM checks the configuration for consistency;
if it does not find any errors, it saves the new settings and reboots.
If writing the object returns ‘‘Error: Inconsistent value,’’ check the
configuration for problems and re-try.
The following objects control LAN IP parameters in the WRM.
arrisWrmDevNATEnable
Enables or disables Network Address Translation (NAT) on the
WRM.
Note: NAT must be disabled in order to transmit RIP information.
arrisWrmDevLanIpAddr
The IP address for the WRM LAN interface. All IP addresses
assigned by the WRM’s DHCP server are based from this IP
address.
arrisWrmDevLanIpMask
The subnet Mask for the WRM LAN interface. Together with
arrisWrmDevLanIpAddr, this object defines the subnet on the
WRM LAN interface.
arrisWrmDevLanIpPoolStart
Determines the first IP address in the WRM’s DHCP IP address
pool.
The value of this object only determines the last 8 bits of the IP
address. The first 3 bytes (24 bits) of the IP address come from the
first 3 bytes of arrisWrmDevLanIpAddr.
arrisWrmDevLanIpPoolEnd
Determines the last IP address in the WRM’s DHCP IP Address
pool.

26 Chapter 1
The value of this object only determines the last 8 bits of the IP
address. The first 3 bytes (24 bits) of the IP address come from the
first 3 bytes of arrisWrmDevLanIpAddr.
arrisWrmDevLanDhcp
Set to enable(1) to enable the WRM DHCP server, or disable(2) to
disable it.
arrisWrmDevLanLease
Sets the lease time of addresses assigned by the DHCP server:
forever(0), halfHour(1), oneHour(2), twoHours(3), halfDay(4),
oneDay(5), twoDays(6), oneWeek(7), or twoWeeks(8).
arrisWrmDevLanDomain
A string containing the domain name of the WRM LAN.
arrisWrmDevWlanAp
Set to enable(1) to configure the WRM as an access point, or dis-
able(2) to configure the WRM as a standalone or master.
The following objects control WLAN IP parameters in the WRM.

arrisWrmDevWlanApDhcpc
Enables or disables the DHCP client when in AP mode.
arrisWrmDevWlanApConfigTable
A table containing MIB objects which control WLAN basic param-
eters. Parameters related to WLAN security are covered in arrisWr-
mDevWlanApSecuConfigTable. The following eight objects are
part of this table.
arrisWrmDevWlanApConfigIndex
Part of the arrisWrmDevWlanApConfigTable. The index that
uniquely identifies the SSID to which this entry is applicable. Two
SSIDs are available; index 0 is the public BSSID, and 1 is the pri-
vate BSSID.
arrisWrmDevWlanApConfigChannel
The channel number. Valid range: auto(0) to automatically select
an unused channel, or 1 to 11 to specify a channel.
arrisWrmDevWlanApConfigMode
Sets the wireless mode:
0: off (wireless disabled)
1: 802.11g and 802.11b
2: 802.11g only
3: 802.11b only
arrisWrmDevWlanApConfigSsid
Part of the arrisWrmDevWlanApConfigTable. A string containing
the SSID name.

Overview 27
arrisWrmDevWlanApConfigSSidBroad
Part of the arrisWrmDevWlanApConfigTable. Set to enable(1) to
broadcast the SSID, or disable(2) to disable broadcasting.
arrisWrmDevWlanApConfigProtec
Part of the arrisWrmDevWlanApConfigTable. Set to 1 to enable
WLAN protect mode, or 0 to disable. Enabling protect mode can
reduce wireless network interference, but can also reduce the physi-
cal range or throughput.
arrisWrmDevWlanApConfigQos
Part of the arrisWrmDevWlanApConfigTable. Set to 1 to enable
WLAN 802.11e QoS, or 0 to disable.
arrisWrmDevWlanApSecuConfigTable
This table contains objects that control WLAN security parameters
not covered in the arrisWrmDevWlanApConfigTable. The next 12
entries are part of this table.
arrisWrmDevWlanApSecuConfigIndex
Part of the arrisWrmDevWlanApSecuConfigTable. The index that
uniquely identifies the SSID to which this entry is applicable. Two
SSIDs are available; index 1 is the public BSSID, and 2 is the pri-
vate BSSID.
arrisWrmDevWlanApSecuConfigEnable
Part of the arrisWrmDevWlanApSecuConfigTable. Sets the
WLAN security mode. One of: disable(0), wep(1), wpa(2),
wpa2(3), or wpa_wpa2(4).
arrisWrmDevWlanApSecuConfigWep
Part of the arrisWrmDevWlanApSecuConfigTable. Sets the
authentication mode for WEP. One of: open(1), share(2), or
auto(3).
arrisWrmDevWlanApSecuConfigWepK_type
Part of the arrisWrmDevWlanApSecuConfigTable. Sets the WEP
key size. One of:
bit_64(1): 64-bit
bit_128(2): 128-bit
arrisWrmDevWlanApSecuConfigWepK_index
Part of the arrisWrmDevWlanApSecuConfigTable. Selects the
WEP key index to use. Valid range: 1 to 4.
arrisWrmDevWlanApSecuConfigWepK_gen
Part of the arrisWrmDevWlanApSecuConfigTable. Selects the
WEP passphrase, used to generate group keys. The string can be up
to 64 characters long.
arrisWrmDevWlanApSecuConfigWepK_man
Part of the arrisWrmDevWlanApSecuConfigTable. Manually
specifies the WEP key. For a 64-bit WEP key, use 10 hexadecimal
digits. for a 128-bit WEP key, use 26 hexadecimal digits.

28 Chapter 1
arrisWrmDevWlanApSecuConfigWpaEncry
Part of the arrisWrmDevWlanApSecuConfigTable. Specifies the
WPA encryption mode. One of: tkip(0) or aes(1).
arrisWrmDevWlanApSecuConfigWpaphrase
guest passphrase (not currently supported).
arrisWrmDevWlanApSecuConfigWpaObsecu
Part of the arrisWrmDevWlanApSecuConfigTable. Set to
enable(1) to enable WPA Obscure PSK, or disable(2) to disable.
arrisWrmDevWlanApSecuConfigWpa2phrase
WPA2 guest passphrase (not currently supported).
arrisWrmDevWlanApSecuConfigWpa2Obsecu
Part of the arrisWrmDevWlanApSecuConfigTable. Set to 1 to
enable WPA2 Obscure PSK, or 0 to disable.
arrisWrmDevWlanApPowerLevel
Sets the WRM wireless power range; one of: high(0), middle(1), or
low(2).
The following objects control WRM bandwidth.

arrisWrmDevWlanQoSConfigEnable
Enables or disables bandwidth limitations on WRM Ethernet and
wireless interfaces.
arrisWrmDevWlanQoSConfigTotalBandwidth
Sets the maximum interface speeds for the entire WRM, in kbps.
Valid range: 100 to 100000 kbps.
arrisWrmDevWlanQoSConfigHomeBandwidth
Sets the maximum interface speed for the WRM Ethernet and
SSID1 wireless interfaces. Valid range: 100 to 100000 kbps.
arrisWrmDevWlanQoSConfigPrivateBandwidth
Sets the maximum interface speed for the WRM SSID2 wireless
interface. Valid range: 100 to 100000 kbps.
The following objects control communication between CPE devices on the
WRM.
arrisWrmDevWlanApIsolationInter
the same SSID.
arrisWrmDevWlanApIsolationExtra
different SSIDs on the same WRM.

Overview 29
arrisWrmDevWlanApConfigLanAccess
the wireless interface and devices on the Ethernet ports (including
the WRM configuration web pages).
The following objects control RIPv2 parameters in the WRM device, that are
not covered by the standard rip2 MIBs.
arrisWrmDevRip2Table
The objects in this table control RIPv2 parameters in the WRM
device that are not covered by rip2IfConfTable.
arrisWrmDevRip2KeyId
An unsigned 8-bit value that contains the Key Identifier or Key-ID.
This identifies the key used to create the Authentication Data for
this RIP-2 message whenever rip2IfConfAuthType has a value other
than noAuthentication.
arrisWrmDevRip2AdvertisementInt
The interval, in seconds, between transmits of routing table updates.
arrisWrmDevRipTransmitStatus
active(1), inactive(2), Returns active(1) when the WRM is actively
transmitting RIP updates, or inactive(2) otherwise. To enable trans-
mission of RIP updates, rip2IfConfSend must be active and
arrisWrmDevNATEnable must be disabled.
arrisWrmDevRipReceiveStatus
Returns active(1) when the WRM is receiving RIP updates, or inac-
tive(2) otherwise. To enable receiving RIP updates, rip2IfConfRe-
ceive must be active.
The following object controls the web page password.

arrisWrmDevPwd
A string containing the password to the WRM web pages. The
default is blank (no password).
Note: Once you have changed the WRM password, you cannot
return to the default blank password by setting this object. To
restore the default, you must either factory-reset the WRM or use
the WRM configuration pages.
The following objects relate to provisioning file troubleshooting.
arrisWrmDevProvStatus
The provisioning file status; one of:
−3: Error: File not found
−2: Error: failure during provisioning file download
−1: no provisioning file specified
0: no errors found
1+: number of errors found in the provisioning file

30 Chapter 1
arrisWrmDevProvFileName
A string containing the provisioning file name.
arrisWrmDevProvFile
A long string (up to 2048 octets) containing provisioning com-
mands. This object allows the CM configuration file to contain
WRM provisioning as well.
arrisWrmDevProvDLTime
Returns the time of day when the provisioning file was downloaded.
arrisWrmDevHpg
Set to enable(1) to enable the hidden page (Provisioning File Errors
page), or disable(2) to disable.
IPv6-specific Additions
The following MIB objects apply to IPv6.

arrisCmDevDhcpIpMode
Returns the DHCP IP address type: 0 (null), 1 (IPv4), or 2 (IPv6).
arrisCmDevDhcpCmIpAddrV6
The currently-leased IPv6 IP address.
arrisCmDevDhcpCmSubNetMaskV6
For IPv6 addresses, returns the prefix length. For IPv4 addresses,
returns the number of bits representing the subnet.
arrisCmDevDhcpCmGatewayIpAddrV6
The IPv6 gateway address.
arrisCmDevDhcpPrimaryDhcpServerIpAddrV6
The primary DHCP server IPv6 address.
arrisCmDevDhcpTimeSvrIpAddrV6
The current Time server IPv6 address.
The following objects apply to Enhanced Firmware Loading.
arrisCmDevSwServerAddressType
The IP address type for the firmware upgrade server: 0 (null), 1
(IPv4), or 2 (IPv6).
arrisCmDevSwServerAddress
The IPv4 or IPv6 address of the firmware upgrade server.
PacketCable 1.5 Battery Backup MIB
TS6.1 is fully compliant with the PacketCable 1.5 Battery Backup MIB. The
supported objects are:

Overview 31
upsShutdownType
Specifies the type of UPS shutdown to perform. TS6.1 supports
only the output(1) type (do not provide battery power in the event
of an AC failure).
upsShutdownAfterDelay
Shuts off the UPS output after the specified time (in seconds). Valid
range: 1 to 604800 (7 days), or −1 (the default) to disable the timer.
This object cannot be set on TM402, TM508, and TM512 Tele-
phony Modems and always returns −1.
upsStartupAfterDelay
Turns on the UPS output after the specified time (in seconds),
assuming that the UPS output is currently off. Valid range: 1 to
604800 (7 days), or −1 (the default) to disable the timer.

upsRebootWithDuration
Immediately executes the specified upsShutdownType for the
specified time (in seconds). After this period, the eMTA enables the
UPS output. Valid range: 1 to 604800 (7 days), or −1 (the default)
to disable the timer.
Note: The upsAutoRestart object is not required by PacketCable 1.5 and is
not supported in TS6.1.
PacketCable 1.5 Provisioning Mode Selection
To differentiate between the ARRIS BASIC provisioning modes and Packet-

Cable BASIC provisioning modes, TS6.1 introduces the arrisMtaDevPacket-
cableProvisioningFlow object. When the value of arrisMtaDev-
ProvMethodIndicator is fullPacketCable(1), this object selects the actual
PacketCable provisioning mode. See the Touchstone Telephony Provisioning
Guide for details.
For PacketCable BASIC provisioning modes, the pktcMtaDevConfigHash
object must be present in the configuration file and have a value equal to the
hash of the configuration file. The MTA calculates the hash of the down-
loaded configuration file and halts provisioning if the hash values do not
match.

32 Chapter 1
RIP MIB Objects
The following objects from the RIP MIB are supported:

rip2IfConfAddress
The IP Address of this system on the indicated subnet. For unnum-
bered interfaces, the value 0.0.0.N, where the least significant 24
bits (N) is the ifIndex for the IP Interface in network byte order.
rip2IfConfDomain
The value inserted into the Routing Domain field of all RIP packets
sent on this interface. The default is 0.
rip2IfConfAuthType
The authentication type used on this interface: noAuthentication(1)
(the default), simplePassword(2), or md5(3).
rip2IfConfAuthKey
A string, up to 16 octets, containing the authentication key. Used
only when rip2IfConfAuthType has a value other than noAuthenti-
cation. The authentication string is unreadable.
rip2IfConfSend
The type of RIP updates sent on this interface; one of: doNot-
Send(1) (no updates), or ripVersion2(2) (send RIPv2 updates)
rip2IfConfReceive
The RIP updates accepted by this interface; one of: rip2(1),
rip1OrRip2(2) (the default), or doNotRecieve(3).
rip2IfConfDefaultMetric
The metric value used for the default route entry in RIP updates
originated on this interface. Valid range: 0 to 15.
Note: The MTA is always connected to a CMTS through the WAN
interface, so the metric will always be 1 for the WAN interface.
rip2IfConfStatus
Writing invalid deletes this interface.
rip2IfConfSrcAddress
The IP address this system uses as a source address on this inter-
face. If it is a numbered interface, the address be the same as
rip2IfConfAddress. On unnumbered interfaces, it must be the
value of rip2IfConfAddress for some interface on the system.
ARRIS-proprietary MIB objects for RIP are:
arrisCmDevRouterLanEnable
Enables or disables the router.
arrisCmDevRouterLanIpAddr
The current router LAN IP address.

Overview 33
arrisCmDevRouterLanSubNetMask
The current router LAN subnet mask.
Highest Recorded Temperature Objects
Highest temperature recording MIB objects (valid when the arrisMtaDev-

PwrSupplyOverTempAlarmControl MIB object is enabled):
arrisMtaDevPwrSupplyHighestTemperature
Provides the highest temperature, in degrees C, recorded by the bat-
tery charger.
arrisMtaDevPwrSupplyHighestTemperatureTime
Provides the date and time that the eMTA recorded the high temper-
ature.
arrisMtaDevPwrSupplyHighestTemperatureClear
Resets the highest temperature and time data.
New and Changed See the TS6.1 introduces the following additions and changes to the CLI
CLI Commands commands. Touchstone Telephony Troubleshooting Guide for syntax details
or examples for any CLI command.
The following commands have been modified to display IPv6 information
when the CM is using IPv6 addressing:
• cmDhcpACK (Cable Modem)
• cmDisp (Cable Modem)
New RIP sub-mode, that includes the following commands:
• arpshow (prints the ARP table)
• routeshow (prints the routing table)
• riprouteshow (shows the RIP routing table)
• ripdebuglevel (displays RIP debug messages)
• ripconfig (displays the RIP configuration)
• ripstatus (enables or disables the interface)
• ripsend (configures the RIP send type)
• ripreceive (configure RIP receive)
• ripauthtype (configures the RIP authorization type)
• rippassword (sets the RIP simple password)
• ripmd5addkey (sets the RIP MD5 password)

34 Chapter 1
• ripmd5delkey (deletes the RIP MD5 password)

CallP sub-mode changes:
• A new command, check, displays the resource usage of the SIP stack.
• A new command, dds, displays the size of CallP data structures.
• The existing dmon command also prints the largest NCS messages sent
and received, with the message sizes (in bytes).
• A new command, SG3Fax, displays and changes the SuperG3 support
status.
• A new command, scwidDelay, displays or sets the delay time (in mil-
liseconds) between reception of the SCWID ACK and transmission of
the FSK response.
System sub-mode changes:
• The sysinfo and http_all commands were modified to show current
RIP status.
• The sysinfo command also was modified to display the current DST
policy setting.
WRM sub-mode changes:
• A new command, redirect show provf, shows the remote provisioning
file download status.
• The following new commands apply to RIP configuration:
– redirect set rip iface (set the RIP interface type)
– set rip reset (resets the RIP sub-system)
– set rtbl add (explicitly adds a route to the routing table)
– set rtbl delete (deletes a route from the routing table)
New and Changed TS6.1 made the following changes to the web-based interface.
Web Pages
WTM552 and WTM652 Router Access
TS6.1 allows access to the Wireless Router Module from the standard web-
access IP address of 192.168.100.1, using the Wireless Router link. See the
Touchstone Telephony Troubleshooting Guide for details.
New RIP Page

Overview 35
TS6.1 provides a new page for displaying (and on WTM552 or WTM652

Telephony Modems, changing) RIP information. You can access the RIP
page on WTM552 and WTM652 Telephony Modems by using the Wireless
Router link to display the Wireless Router Module pages, then follow the
LAN Setup link.
For other Telephony Modems, the RIP link provides information about the
RIP configuration.
New Features in TS5.3
The following new features are available in TS5.3.
New General TS5.3 supports firmware downloads while lines are off-hook, deferring appli-
Features cation of the new load until the MTA is idle. See ‘‘About ARRIS Enhanced
Firmware Loading’’ on page 89 for details.
TS5.3 provides an option for the MTA to recover call resources when a line
goes on-hook and the CMS fails to send a Delete Connection (DLCX) com-
mand. See ‘‘Automatic Call Resource Recovery’’ on page 48 for details.
New Provisioning See the Touchstone Telephony Provisioning Guide for details about new pro-
Features visioning features.
TS5.3 provides a new North American −6/+6 dB loss plan. This template is
the default for D11PLUS loads.
D11PLUS loads have an expanded Rx/Tx gain range, from ±2dB to ±16dB.
FSK and CAS tone levels can now be adjusted to improve control of Caller
ID behavior during Call Waiting. Two MIB objects set the levels, and a third
object toggles between the set and default levels. See ‘‘Adjusting FSK and
CAS Gain Levels’’ on page 86 for details.
New and Changed See the Touchstone Telephony Troubleshooting Guide for details about new
Troubleshooting and changed troubleshooting features.
Features
LED Pattern Changes
For D11PLUS loads, TS5.3 changes the Power and Battery LED sequences
to provide a ‘‘low battery’’ indication.

36 Chapter 1
VQM Enhancements
TS5.3 reports the number of total RTP packets lost as part of the Voice Qual-
ity Monitoring statistics. The arrisMtaDevMonitoring MIB provides this
statistic, as well as:
• Start time of the last call
• End time of the last call
A new MIB object, arrisMtaDevVqmHistorySize, provides a method to con-
trol the size of the VQM history buffer. Valid range: 2 to 50 calls. Default:
10.
The following additional metrics are now supported:

• Transmitted packets and octets
• Received packets and octets
• Packet loss
• Interval jitter
Reset Reason Logging
TS5.3 provides a history of the last ten reset reasons (patent pending), using
the arrisCmDevResetReasonLogTable. This table is stored in non-volatile
RAM, and can be disabled to prevent multiple resets from reducing eMTA
life (for example, during extended testing). A second MIB object , arrisCm-
DevLastHwResetReason, provides the last reset reason.
The new Log sub-mode rrdmp CLI command shows the reset reason log.
The System sub-mode sysinfo command also provides the last reset reason
code (supported in previous firmware versions).
New and Changed TS5.3 introduces the following MIB objects.

MIB Objects arrisMtaDevAutomaticCallResourceRecovery
The time, in seconds, the MTA waits before automatically recover-
ing resources associated with the call after detecting an on-hook
event. The default is 0 (disable automatic recovery), except in
D11PLUS loads where the default is 60 seconds. See ‘‘Automatic
Call Resource Recovery’’ on page 48 for details.
arrisCmDevLastHwResetReason
Provides the reason for the last MTA resets (up to 10): watchdog,
hardware, or firmware.
The following MIB objects provide VQM enhancements:

Overview 37
arrisMtaDevRtpPktsLostTotal
The number of RTP packets lost on all endpoints since the MTA
was last powered-up or reset.
arrisMtaDevLastCallStartTime
The start time of the last call made from the MTA.
arrisMtaDevLastCallEndTime
The end time of the last call made from the MTA.
The following MIB objects can be used to control off-hook FSK and CAS
gain for CW-CID and VMWI:
arrisMtaDevLevelControlOffHookFSK
Gain adjustment for MTA-generated FSK tones (CID and VMWI)
while the line is off-hook. The MTA uses this value only when the
arrisMtaDevLevelControlOffHookEnable MIB object is enabled.
Valid range: −32 to −10 (dBm). Default: −15.

arrisMtaDevLevelControlOffHookCAS
Gain adjustment for MTA-generated CAS tones (CID and VMWI)

arrisMtaDevLevelControlOffHookEnable
Set to enable(1) to enable use of the arrisMtaDevLevelCon-
trolOffHookCAS and arrisMtaDevLevelControlOffHookFSK MIB
objects for setting gain levels. The default is disable(0).
The following objects apply to the Reset Reason logging feature:
arrisCmDevResetReasonLogTable
Provides a history of the last ten reset reasons. This table is stored
in non-volatile RAM.
arrisCmDevLastHwResetReason
Provides the last reset reason.
arrisCmDevResetReasonLogDisable
Enables or disables the logging table. Disabling the table prevent
multiple resets from reducing eMTA life (for example, during
extended testing).
The following objects apply to firmware downloading enhancements:
arrisMtaDevSwDnldNoSvcImpact
Set to enabled (default) to wait for lines to go on-hook before
applying new firmware. Set to disabled to immediately apply new
firmware (which resets the NIU).

38 Chapter 1
arrisMtaDevNsadSwDnldStatus
Shows the current firmware download status:
• download-idle(0): no firmware download in progress
• download-Acceptance-In-Progress(1): acceptance in progress
(downloading)
• download-Application-Pending(2): firmware downloaded; wait-
ing for lines to go on-hook
Note: If the arrisMtaDevSwDnldNoSvcImpact object is set to dis-
abled, the NIU applies the firmware without waiting for lines to go
on-hook and resets. The default is enabled in D11PLUS loads, and
disabled in other loads.
The arrisMtaDevVqmMetricTable provides the following new index values:

txPackets (60)
txOctets (61)
rxPackets (62)
rxOctets (63)
packetLoss (64)
intervalJitter (65)
The sipCfgSipFeatureSwitch MIB object supports a new feature switch:

0x00000800 (enable SIP Proxy Penalty Box).
For D11PLUS loads only, the valid range for the arrisMtaDevGainCon-
trolTxVoice and arrisMtaDevGainControlRxVoice objects has been
expanded to ±16dB.
The ppCfgMtaCountryTemplate object provides the following new country
template value: northAmerica66(32).
New and Changed See the Touchstone Telephony Troubleshooting Guide for syntax details or
CLI Commands examples for any CLI command.
TS5.3 introduces the following additions and changes to the CLI commands.
Log sub-mode:
A new command, buffer, displays debug messages that were gener-
ated before registration completed (TS5.2 MSUP).
A new command, rrdmp, displays the reset reason log (TS5.2
MSUP).

Overview 39
New and Changed For D11PLUS loads, the Power Supply Telemetry alarm severity level is
Logs and Alarms changed from Information to Minor.

40 Chapter 1

2 Compliance
This chapter outlines Touchstone Telephony DOCSIS®, Euro-DOCSIS,

PacketCable,™ and Euro-PacketCable compliance, and describes ARRIS-
proprietary extensions to the standards.
Standards Compliance
Touchstone Telephony Modems running version TS6.1 firmware comply

with the following standards:
• DOCSIS 1.1 (all Touchstone eMTAs)
• Euro-DOCSIS 1.1 (all Touchstone eMTAs)
• PacketCable 1.0 (all Touchstone Telephony Modems)
• DOCSIS 2.0 (all Touchstone Telephony Modems)
• Euro-DOCSIS 2.0 (all Touchstone Telephony Modems)
• Euro-PacketCable 1.0 (.EURO load only)
TS6.1 SIP loads comply with the following SIP-related RFCs:
• SIP: Session Initiation Protocol, RFC 3261
• An Offer/Answer Model with Session Description Protocol (SDP),
RFC 3264
• A Privacy Mechanism for the Session Initiation Protocol (SIP),
RFC 3323
• A Message Summary and Message Waiting Indication Event Package
for the Session Initiation Protocol (SIP), RFC 3842

42 Chapter 2
Optional TS6.1 supports the following optional functionality specified by DOCSIS and
Functionality PacketCable standards:
• Support for multiple CODECs (see ‘‘CODECs and Packetization Rates
Supported’’ on page 46)
• Support for 10 ms and 20 ms packetization rates (see ‘‘CODECs and
Packetization Rates Supported’’ on page 46)
• Support for up to 16 Upstream Service Flows
• Support for analog Fax/Modems, including automatic tone detection,
echo cancellation disable and switching to the G.711 CODEC
• 802.11b/g wireless LANs, when used with the WTM552 or WTM652
Telephony Modems
Extensions
Touchstone firmware provides various extensions to DOCSIS and PacketCa-

ble standards. These extensions may be enabled through a configuration file
or MIB objects.
TurboDOX Support TurboDOX is a TI-proprietary protocol, supported in hardware. Enabling

TurboDOX increases performance of TCP-based protocols such as FTP and
HTTP.
TurboDOX is enabled by default. Use the arrisCmDevTurboDoxEnable
object to control TurboDOX operation.
WTM552- and The WTM552 and WTM652 are Wifi Certified and WMM PowerSave certi-
WTM652-specific fied. The WTM552 and WTM652 also support IEEE 802.11E Quality of
Compliance Service (QoS).
WTM652G Telephony Modems are Energy STAR compliant.
Specification References
All DOCSIS specifications are available at the DOCSIS web site 〈http://
www.cablemodem.com/specifications/〉.
All PacketCable specifications are available at the PacketCable web site
〈http://www.packetcable.com/specifications/〉.

Compliance 43
DOCSIS 2.0 • DOCSIS 2.0 Radio Frequency Interface Specification, SP-

Specifications RFIv2.0-I11-060206
• DOCSIS 2.0 Operations Support System Interface Specification, CM-
SP-OSSIv2.0-I10-070803
• DOCSIS 1.1 Baseline Privacy Plus Interface Specification, SP-
BPI+-I12-050812
• DOCSIS 1.1 Cable Modem to Customer Premise Equipment Interface
Specification, SP-CMCI-I10-050408
• eDOCSIS Specification, CM-SP-eDOCSIS-I13-070803
CableLabs IPv6 • CableLabs Assigned Names and Numbers, CL-SP-CANN-I01-070119

Specifications • CableLabs DHCP Options Registry, CL.SP-CANN-DHCP-Reg-
I01-070119
PacketCable Spec- • PacketCable Audio/Video Codecs Specification, PKT-SP-CODEC-

ifications C01-071129
• PacketCable Dynamic Quality-of-Service Specification, PKT-SP-
DQOS-C01-071129
• PacketCable Network-Based Call Signaling Protocol Specification,
PKT-SP-EC-MGCP-C01-071129
• PacketCable MIBs Framework Specification, PKT-SP-MIBS-
C01-071129
• PacketCable MTA MIB Specification, PKT-SP-MIB-MTA-C01-071129
• PacketCable Signaling MIB Specification, PKT-SP-MIB-SIG-
C01-071129
• PacketCable MTA Device Provisioning Specification, PKT-SP-PROV-
C01-071129
• PacketCable Security Specification, PKT-SP-SEC-C01-071129
• PacketCable Residential SIP Telephony Feature Specification, PKT-SP-
RSTF-I01-060927
• PacketCable RST UE Provisioning Specification, PKT-SP-RST-UE-
PROV-I01-080905

44 Chapter 2

3 Telephony Features
This chapter describes telephony features supported in Touchstone firmware.
General Functionality
Touchstone firmware provides the following core telephony functionality:

• Support for multiple CODECs (see ‘‘CODECs and Packetization Rates
Supported’’ on page 46 below).
• Support for 10 ms and 20 ms packetization rates (see ‘‘CODECs and
Packetization Rates Supported’’ on page 46 below).
• DTMF support.
• Pulse dialing support. TS6.1 supports both direct relay of dial pulses to
the CMS, or DTMF in-band tone relay (patent pending) to an IPDT.
Pulse rate is 10pps or 20pps ±2pps.
• Support for analog Fax/Modems, including automatic tone detection,
echo cancellation disable and switching to the G.711 CODEC.
• Configurable 32 ms (default) and 8 ms echo cancellation tail for Model
4 and later Touchstone eMTAs. See ‘‘Echo Cancellation and Analog
Fax/Modem Support’’ on page 57 for details.
• Supports Payload Header Suppression (PHS) for voice traffic.
• Interoperability with all ARRIS VoIP solutions.
• Dynamic Quality of Service (DQoS) support for Unsolicited Grant Ser-
vice (UGS) service flows for telephony connections. Supports both full
PacketCable (end-to-end) DQoS and access-side (DSx) DQoS.
• Supports the following line card templates:
– North American Standard (−5/−7 dB) loss plan (default for all but
D11PLUS loads)

46 Chapter 3
– North American High (−3/−3 dB) loss plan

– North American 0/−9 dB loss plan
– North American −6/−6 dB loss plan (default for D11PLUS loads)
– Netherlands −3/−9.5 dB and 0/−9 dB loss plans
– Australia, Austria, Belgium, Chile, France, Germany, Ireland, Israel,
Mexico, MexicoC, Norway, Panama, Poland, Poland1010, Portugal,
Spain, and Switzerland templates Japan600L412 (lab trial and inter-
operability tests only)
– Chile, Israel, Mexico, MexicoC templates
• Full NCS compliance.
• TS6.1 supports SNMPv3, IPSEC, and encrypted voice traffic as
required by PacketCable specifications.
• Supports RFC 2833 functionality. RFC 2833 defines a method for car-
rying DTMF and other telephony signals and events in RTP packets,
instead of sending audio tones over the network.
• Support for dialup fax and modem connections, disabling echo cancel-
lation upon detecting fax or modem start tones.
• Support for dedicated fax lines. A dedicated fax line times out and
drops a call if the MTA does not detect no fax or modem tones within a
configurable time.
• T.38 support
• Supports access to 911 (emergency), 411 (directory), 311 (non-emer-
gency), and 611 (repair) services.
• SIP compliance, including per-line SIP proxy and registrar, when using
the Euro-DOCSIS SIP load (North American operation is supported
only for interoperability and lab trials).
• Supports configurable firmware download request rejection while a call
is in progress.
• Supports waiting to apply firmware downloads until all lines are on-
hook.
CODECs and In addition to continued support for the G.711 CODEC, Touchstone firmware
Packetization supports the following PacketCable™ optional and recommended CODECs:
Rates Supported • G.728
• G.729, G729E

• G.726-16, G.726-24, G.726-32, G.726-40

Touchstone firmware uses the G.711 CODEC as a default, unless the CMS
directs the Touchstone eMTA to negotiate a different CODEC with other
MTAs.
Implementation of CODECs is defined by the PacketCable Audio/Video
Codes Specification, PKT-SP-CODEC-C01-071129
Note: If the Touchstone MTA detects a fax or modem call, the MTA automat-
ically uses the G.711 CODEC only if negotiated as a backup CODEC.
The supported packetization rates in TS6.1 are 10 ms and 20 ms.
Multiple CMS Touchstone eMTAs support up to 64 Call Server IP addresses, provisioned in

Support the MTA configuration file with IP Security turned off. Each call Server
DNS entry can have up to six alias IP addresses associated with it. Support
for multiple CMSs allows for load balancing, where an MTA can be redi-
rected to use a CMS with a lighter load.
Internally, the eMTA creates an inbound and outbound pass policy for each
Call Server IP address, for a maximum of 132 policies (128 pass policies for
CMS IP addresses and four drop policies).
Example configuration:
• 10 CMSs x 6 IP aliases per CMS = 60 IP addresses
There are four IP addresses left over, so:
• 4 CMSs x 1 IP address per CMS = 4 IP addresses
In this example, there are 64 CMS IP addresses (the maximum) defined, but
only 14 CMS names defined in the MTA configuration file (with IPsec turned
off).
Another example configuration is: 64 CMSs x 1 IP alias per CMS = 64 IP
addresses. This would also reach the maximum of 64 CMS IP addresses.
Therefore, there are 64 CMS names defined in the MTA configuration file,
with IPsec turned off.
Note: When IPsec is active, the eMTA does not store security associations
until communications are initiated between the eMTA and the Call Server.
Touchstone eMTAs can store up to 10 security associations, and each associ-
ation represents both upstream and downstream communications. Therefore,
there is a limit of 10 Call Servers with which the Touchstone eMTA can com-
municate at any one time when IPsec is turned on.

48 Chapter 3
CMS Redirect A CallP Feature Switch bit controls security enforcement during CMS redi-
Security Option rection operations.
Per PacketCable specifications, if an eMTA is redirected to a new CMS not
included in the eMTA’s CMS table, the eMTA must establish an IPsec associ-
ation with the new CMS, even if IPsec is disabled on the originally connected
CMS.
Using this CallP Feature Switch setting in the configuration file, the Tele-
phony Modem can redirect to a call server that is not provisioned in the Tele-
phony Modem’s CMS table without attempting to establish an IPsec associa-
tion with the new call server. Enabling this bit applies only to redirection.
The Telephony Modem does not respond to call servers not provisioned in
the Telephony Modem’s CMS table.
Automatic Call Re- TS5.3 and later versions of Touchstone firmware can automatically recover
source Recovery resources related to the call upon detection of an on-hook event. Normally,
the CMS sends a Delete Connection (DLCX) event upon call completion; if
the MTA does not receive the DLCX event within a provisioned amount of
time, the MTA can automatically delete the connection.
Note: Active calls are not subject to resource recovery.
The arrisMtaDevAutomaticCallResourceRecovery MIB object controls
automatic recovery. The valid range is 0 (disables automatic recovery) to
3600 seconds. D11PLUS loads set the default value to 60; other loads set the
default value to 0.
Note: Connections created in REPLCATE, NETWTEST, and NETWLOOP
modes are not subject to automatic deletion.
For more information, see the Touchstone Firmware Provisioning Guide.
CODEC Engineering Rules
Touchstone firmware supports the following PacketCable optional and rec-

ommended CODECs:
• G.711
• G.728
• G.729, G729E
• G.726-16, G.726-24, G.726-32, G.726-40

CODECs and Sup- This section describes how low bit-rate CODECs and T.38/SuperG3 FAX
ported Lines relay interact for Model 6 and later Telephony Modems.
(Model 6 and later)
TM602 Engineering Rules
The following rules apply to the TM602:

• Two instances of T.38/SuperG3 fax relay total for lines 1-2; T.38/SG3
can be supported on any line
• One instance of low bit-rate (LBR) CODEC for lines 1-2; low bit-rate
CODECs can be supported on any line
The following table shows CODEC support for each line and call leg.
Line 1 2
Leg 1 2 1 2
T.38/SG3 T.38/SG3
LBR G.711 LBR G.711
G.711 G.711 G.711 G.711
T.38/SG3 LBR G.711
TM604 and TM608 Lines 1–4
The following rules apply to the TM604 and lines 1 through 4 of the TM608.
• One instance of T.38/SuperG3 fax relay total for lines 1–4; T.38/SG3
• One instance of Low Bit Rate code (LBR) for lines 1–4; LBR codec
Line 1 2 3 4
Leg 1 2 1 2 1 2 1 2
T.38/SG3 G.711 G.711 G.711 G.711 G.711 G.711
G.711 G.711 T.38/SG3 G.711 G.711 G.711 G.711
G.711 G.711 G.711 G.711 LBR G.711 G.711 G.711
G.711 G.711 G.711 G.711 G.711 G.711 LBR G.711
TM608 Lines 5–8
The following rules apply to lines 5 through 8 of the TM608.

• T.38 fax relay can be supported on each line for lines 5-8

50 Chapter 3
• One instance of Low bit rate codec (LBR) can be supported on each
line for lines 5-8;
Line 5 6 7 8
Leg 1 2 1 2 1 2 1 2
T.38 T.38 T.38 T.38
G.711 G.711 G.711 G.711 G.711 G.711 G.711 G.711
LBR G.711 LBR G.711 LBR G.711 LBR G.711
LBR G.711 G.711 G.711 T.38 LBR G.711
CODECs and Sup- When the MTA uses compressed (non-G.711) CODECs, the maximum num-
ported Lines ber of compressed calls per MTA allowed depends on the number of lines
(Model 5 and earli- supported by the MTA:
er) Number Compressed
of lines calls allowed
1 or 2 2
4 4
8 8
12 12
For this restriction, a three-way call counts as two calls.
G.729 CODEC Support
The Touchstone Telephony Modem supports the G.729 CODEC to perform

toll-quality voice compression such as G.729. The G.729 CODEC is defined
in ITU-T Rec. G.729 Annex A, Reduced Complexity 8 kbit/s CS-ACELP
Speech Codec, November 1996, and can compress voice as low as 8 kb/s.
Sometimes the G.729 CODEC is referred to as G.729A, since other varia-
tions such as G.729E have been subsequently defined.
G.729 CODEC Negotiation
By IANA definition and PacketCable specification, compliant Call Agents

use ‘‘G729’’ in the NCS Local Connection Options (LCO) to instruct an end-
point to use the G.729 CODEC. Touchstone firmware also supports
‘‘G729A’’ since some Call Agents use this syntax. IANA also defines a static
payload type of 18 for G.729, which is used by default unless negotiated to
use a different dynamic payload type in the allowed range of 96 through 127.
The following is an example Create Connection (CRCX) command issued by
a Call Agent, instructing the endpoint to use the G.729 CODEC:

CRCX 1001 aaln/1@mta216.dev36 MGCP 1.0 NCS 1.0

C: 28963
L: mp:20, a:G729
M: inactive
The endpoint responds to this message and provides its Local Connection
Descriptor indicating the use of G.729:
200 1001 OK
I: 7A438
v=0
o=- 54445402 54445402 IN IP4 10.1.36.216
s=-
c=IN IP4 10.1.36.216
t=0 0
m=audio 51538 RTP/AVP 18
b=AS:24
a=mptime:20
a=rtpmap:18 G729/8000/1
a=sqn: 0
a=cdsc: 1 audio RTP/AVP 0 8 15 18 96 97 98 2 99 101
a=cpar: a=rtpmap:96 G729E/8000/1
a=cpar: a=rtpmap:97 G726-16/8000/1
a=cpar: a=rtpmap:98 G726-24/8000/1
a=cpar: a=rtpmap:99 G726-40/8000/1
a=cpar: a=rtpmap:101 telephone-event/8000/1
a=cpar: a=fmtp:101 0-15,144,149,159
a=cdsc: 11 image udptl t38
a=cpar: a=T38FaxVersion:0
a=cpar: a=T38FaxRateManagement:transferredTCF
a=cpar: a=T38FaxMaxDatagram:160
a=cpar: a=T38FaxUdpEC:t38UDPRedundancy
The Call Agent may also specify a backup CODEC in a CRCX such as the
following:
C: 28963
L: mp:20;20, a:G729;PCMU
M: inactive
The endpoint responds accordingly:

200 1001 OK
I: 7A438
v=0
o=- 54445402 54445402 IN IP4 10.1.36.216
s=-
c=IN IP4 10.1.36.216

52 Chapter 3
t=0 0
m=audio 51538 RTP/AVP 18 0
b=AS:24
a=mptime:20
a=rtpmap:18 G729/8000/1
a=rtpmap:0 PCMU/8000/1
a=sqn: 0
a=cpar: a=rtpmap:97 G726-16/8000/1
a=cpar: a=rtpmap:98 G726-24/8000/1
a=cpar: a=rtpmap:99 G726-40/8000/1
a=cpar: a=fmtp:101 0-15,144,149,159
In this example, the endpoint can autonomously fall back to PCMU if neces-
sary.
G.729 Fax and Modem Support
Since the G.729 CODEC highly compresses audio, it can not adequately sup-
port analog fax or modem transmission. Depending upon the call setup, the
endpoint responds as follows when local fax or modem tones are detected:
• If a fax tone is detected, T.38 Fax Relay is allowed by the Call Agent,
and the use of T.38 is negotiated between endpoints, then a T.38 Start
event is generated and the fax is transmitted using T.38 Fax Relay.
• Otherwise, if either PCMU or PCMA is allowed by the Call Agent and
negotiated with the far end as a backup CODEC, the endpoint automati-
cally switches to PCMU or PCMA respectively.
• Otherwise, the endpoint simply notifies the fax or modem detection
event to the Call Agent, if specifically requested to do so. Then, the
Call Agent can modify the connection to use either PCMU or PCMA.
Using PCMU or PCMA as a backup CODEC to G.729 provides the follow-
ing advantages:
• Upon detection of fax or modem tones, the endpoint can quickly switch
to PCMU or PCMA without waiting for specific instructions from the
Call Agent to do so. This helps to prevent fax or modem failure which
may occur if the endpoint has to wait too long for instructions to switch
to PCMU or PCMA.

• When PCMU or PCMA is negotiated as a backup CODEC, and DQoS

is in use, the CMTS reserves bandwidth between the Telephony Modem
and CMTS when the call is initially set up. If the Telephony Modem
needs to switch to PCMA or PCMU the necessary bandwidth is already
reserved.
G.729 Bandwidth Considerations
There is one disadvantage to specifying PCMA or PCMU as a backup

CODEC: when DQoS is in use, the CMTS always reserves enough band-
width for PCMA or PCMU even when G.729 is being used. This extra band-
width is wasted during normal voice calls, but may be used for Best Effort
data traffic.
Note: When only G.729 is allowed (i.e. PCMU and PCMA are not allowed as
a backup CODEC), the CMTS reserves only the bandwidth needed to carry
the call. However, there is no guarantee that extra bandwidth would be avail-
able if a switch to PCMU or PCMA became necessary, which would result in
a failed fax or modem call.
DTM602 DECT Support
TS6.1 provides support for the DTM602, a two-line Telephony Modem with
an integrated DECT 6.0 handset. This section provides an overview of the
unique DTM602 features.
The DTM602 behaves like a TM602 in most respects. The DECT module is
bridged to telephony Line 1 and the Ethernet interface; both the Line 1 and
Ethernet jacks are available for connections to other hardware.
If the DTM602 has battery backup, and AC power is removed, the Telephony
Modem shuts down the Ethernet and DECT modules (according to the value
of the arrisMtaDevPwrSupplyDataShutdownTime MIB object). With data
shutdown enabled, the DECT handset can still make and receive calls, but
any extended features are disabled.
Supported Calling Features
Touchstone firmware supports the following calling features:

• Automatic Number Assignment Confirmation (ANAC) via CID2

54 Chapter 3
• Direct Distance Dialing (DDD)

• Critical Interdigital Timing for Dialing Plan
• International DDD (IDDD) Local Billing Control
• Residence Distinctive Alerting Service
• Free Terminating Service
• Code Restriction & Diversion
• Toll Restricted Service
• DTMF Dialing
• Pulse Dialing
• CLASS™: Calling Number Delivery
• CLASS: Customer Originated Trace
• CLASS: Anonymous Call Rejection
• CLASS: Calling Number Delivery Blocking
• CLASS: Calling Identity Delivery & Suppression
• CLASS: Calling Name Delivery Blocking
• CLASS: Calling Name Delivery
• CLASS: Calling Identity Delivery on Call Waiting
• Speed Calling 8
• Speed Calling 30
• Call Waiting
• Cancel Call Waiting (*70)
• Call Waiting Deluxe
• Access to Telecommunications Relay Service (TDD)
• Intercept Routing for blank/changed/etc. phone numbers
• Customer-Changeable Speed Calling
• Call Forwarding Variable
• Call Forwarding Busy Line
• Call Forwarding — Don’t Answer — All Calls
• VIP Alert (Distinctive Ringing)
• Visual Message Waiting Indicator (FSK)

• Message Waiting Tone (stutter dial tone)

• Conference Calling — Six-Way Station Controlled
• Call Hold, Call Pick-up, Toll Free Calling
• Emergency Calling Services (E911)
• Customer Call Back (Automatic Recall) (*69)
• Three-Way Calling
• Service Provider Originated Trace
• Courtesy Ring Generation
• Multiple Directory Numbers on a Line
• Customer Access Treatment (CAT) code restrictions
• Semi-Restricted Originating & Terminating (including 1010xxx block-
ing)
• Fully Restricted Originating & Terminating
• Single-Digit Dialing
• Manual Line Service
• Direct Connect
• Denied Terminating Service
• Denied Originating Service
• Local Number Portability
• Remote Activation of Call Forwarding (RACF)
• Outside Calling Area Alerting (OCAA)
End of Call Connection Statistics
Touchstone firmware supports the PacketCable-defined call connection statis-

tics, with clarifications as defined in ECN EC-MGCP-N-04.0175-7. Previ-
ously, the PacketCable NCS specification implied that these statistics were
related to the connection mode requested by the CMS. The EC clarifies the
requirement to ensure that the statistics represent the actual packets
sent/received regardless of the current connection state of the call.
Note: End-of-call connection statistics and Voice Quality Monitoring (VQM)
statistics are different features. For information about the VQM feature, see
‘‘Voice Quality Monitoring’’ on page 104.

56 Chapter 3
Touchstone firmware makes end-of-call connection statistics available

through proprietary MIB objects and Syslog messages. The arrisMtaDevEn-
ableCallStatsSyslogRpt MIB object controls end-of-call statistics reporting
through Syslog. The arrisMtaDevEnableCallSigLastMsgRpt MIB object
controls reporting of the last 4K of signaling messages through Syslog. Each
MIB may be set independently, and interact as follows:
CallStats LastMsg CMS LoC
Messages Sent
MIB MIB Alarm
Inactive None
Disabled
Active None
Disabled
Inactive None
Enabled
Active None
Inactive None
Disabled
Active Last messages sent/received
Enabled
Inactive Last 4K of messages sent/received
Enabled
Active Last 4K of messages sent/received
See the Touchstone Telephony Management Guide for details.

The eMTA sends connection statistics to the call server (and optionally, Sys-
log servers) during the call tear-down procedure. PacketCable-compliant call
servers provide a method of reporting these captured statistics. See the call
server documentation for instructions on accessing the statistics.
The statistics provide information on the performance of the network includ-
ing the following:
• Number of packets sent
• Number of octets sent
• Number of packets received
• Number of octets received
• Number of packets lost in transit
• Interarrival jitter
Note: This is the mean deviation (smoothed absolute value) of the dif-
ference in packet spacing at the receiver compared to the sender for a
pair of packets.
• Average transmission delay
Note: This statistic reports the network delay, not one-way delay. It
does not account for delay within the device by jitter buffers and other
components; it strictly measures the delay of the traffic traveling the
user’s network.

In addition to the parameters above, an endpoint that has received one or

more RTCP sender or receiver reports from its peer must also send the fol-
lowing statistics:
• Remote packets sent
• Remote octets sent
• Remote packets lost
• Remote jitter
Complete definitions of these statistics can be found in the PacketCable Net-
work-Based Call Signaling Protocol Specification (PC-NCS), PKT-SP-EC-
MGCP-C01-071129.
Echo Cancellation and Analog Fax/Modem Support
ARRIS Model 4 and later Touchstone eMTAs support:

• echo cancellation per ITU G.168/G, with a 28 dB echo return loss
• Group I-III compliant facsimile devices
• analog voice band modems up to v.92
Echo cancellation provides a selectable echo cancellation tail of 8 ms or
32 ms. The default tail for TS4.3 and later is 32 ms, and 8 ms for earlier ver-
sions.
Add the arrisMtaDevEchoCancellerTailLength MIB object to the configu-
ration file to use an 8 ms setting if needed.
Note: Touchstone hardware prior to Model 4 supports only the 8 ms echo
cancellation tail.
Echo cancellation operates in one of three modes:
• enabled
• enabled with non-linear processor (NLP) disabled
• disabled
The echo cancellation feature is always enabled for normal voice calls. How-
ever, for analog fax/modem calls, the ARRIS eMTA sets the echo cancella-
tion mode depending on detected tones:

58 Chapter 3
Tones Detected Mode

Calling (CNG),
V.21 preamble, or
NLP disabled
‘‘slow’’ speed CED
(14.4k or lower)
‘‘high’’ speed CED
completely disabled
(28.8k and higher)
If the eMTA detects fax/modem tones, and a CODEC other than G.711 is
active, the eMTA automatically switches to the G.711 CODEC if G.711 was
negotiated as a backup CODEC when the call was set up. Upon completion
of a fax call, the eMTA automatically re-enables echo cancellation but does
not switch back to the original CODEC unless instructed to switch by the
Call Agent. The eMTA does not automatically re-enable echo cancellation
after a modem call completes.
T.38 Fax Relay Support
Touchstone firmware supports T.38 fax relay. T.38 fax relay provides higher
reliability of fax transmissions using redundancy to tolerate packet loss.
Touchstone firmware supports call agent-controlled T.38 as defined in PKT-
SP-NCS1.5-I03-070412, Appendix A.
T.38 support requires that SDP capability reporting be enabled (the default
setting).
SDP Parameter When T.38 Strict mode is enabled, the eMTA sends an SDP list as shown
List for T.38 Strict below. The bolded portion indicates the capability descriptor.
v=0
o=- 48186 48188 IN IP4 10.1.36.218
s=-
c=IN IP4 10.1.36.218
t=0 0
m=audio 61304 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
a=ptime:20
a=sqn:0
a=cdsc:1 audio RTP/AVP 0 8 15 18 96 97 98 2 99 101
a=cpar:a=rtpmap:96 G729E/8000/1
a=cpar:a=rtpmap:97 G726-16/8000/1
a=cpar:a=rtpmap:98 G726-24/8000/1

a=cpar:a=rtpmap:2 G726-32/8000/1
a=cpar:a=rtpmap:99 G726-40/8000/1
a=cdsc:11 image udptl t38
a=cpar:a=T38FaxVersion:0
a=cpar:a=T38FaxRateManagement:transferredTCF
a=cpar:a=T38FaxMaxDatagram:160
a=cpar:a=T38FaxUdpEC:t38UDPRedundancy
a=cpar:a=T38MaxBitRate:14400
m=image 0 udptl t38
If the capability descriptor causes interoperability issues, set bit 0x00000008

of the CallP Feature Switch. See the Touchstone Telephony Provisioning
Guide for more information about the feature switch.
CallP Feature Switches Affecting the SDP
The following feature switches affect the SDP, returned in response to a Cre-
ate (CRCX) or Modify (MDCX) Connection command.
Bit Description
0x00000008 Reduce the capability descriptor in the SDP to T38 only
(default = 0, no reduction).
0x00000010 SDP compliancy (default = 1, generates compliant SDP).
0x00000080 Omit mptime parameter in returned SDP (default = 0,
mptime included).
0x00000100 Omit capability parameters in returned SDP (default = 0,
capability descriptors included).
0x00001000 NUERA RFC 2833 messaging without request using pay-
load 127 (default = 0, telephone-event is negotiated nor-
mally).
0x00080000 LUCENT RFC 2833 messaging without request using pay-
load 94 (default = 0, telephone-event is negotiated normally).
0x00100000 Allow AES encryption for RTP/RTCP (default = 1, AES
encryption is negotiated normally).
0x01000000 Send DTMF digits via RFC 2833 with payload 101 without
request (default = 0, telephone-event is negotiated normally).
The following CRCX command is used to generate all the SDP examples,
unless otherwise specified:
C: 1234
M: recvonly
L: mp:20, a:PCMU, fxr/fx:t38-loose, xrm/mcr:on
The default feature switch settings generate the following SDP:

v=0
o=- 381749076 381749076 IN IP4 10.1.36.219

60 Chapter 3
s=-
c=IN IP4 10.1.36.219
t=0 0
b=AS:81
a=rtcp-xr:voip-metrics
a=mptime:20
a=X-pc-secret:base64:ZNos/qs530eSDJ4FvdL2GJBR62lS5UKyQ7n9og4
IaaDbA9Blpg6lM2PfOaHEGg== U5Q5N/eWnimq9Q/yjWwY2hACRIY6a9qqEQ
Us8tm54lEmEE6LXkCB51+3sqxlQg==
a=X-pc-csuites-rtp:62/51 64/51 60/51 60/50
a=X-pc-csuites-rtcp:81/70 81/71 82/70 82/71 80/70
a=sqn: 0
a=cpar: a=fmtp:18 annexb=no
a=cpar: a=rtpmap:97 G726-16/8000/1
a=cpar: a=rtpmap:98 G726-24/8000/1
a=cpar: a=rtpmap:2 G726-32/8000/1
a=cpar: a=rtpmap:99 G726-40/8000/1
a=cpar: a=fmtp:101 0-15,144,149,159
When the SDP Compliance switch (0x00000010) is disabled, and all other
switches are set to their default values, the SDP becomes:
v=0
c=IN IP4 10.1.36.219
a=mptime:20
a=X-pc-secret:base64:+JLpxeajZEoknvXbL7YSSK87FP5iIga4HWr3G0k
CJ6fjxE6tFLhNx920eXVCmw== Y6XT294www0KXeqt3x0jqspuzcEU/bNA/r
RTOJ1jBviqsw/JaO91i/tKDTbTdw==
a=X-pc-csuites-rtp:62/51 64/51 60/51 60/50
Note that the Capability Descriptor is suppressed; therefore, the settings for
both ‘‘Omit Capability Descriptor’’ and ‘‘Reduce Capability Descriptor’’ are
irrelevant. Other features are unaffected.
When the ‘‘Omit Capability Descriptor’’ switch (0x00000100) is enabled,
and all other switches are set to their default values, the SDP becomes:
v=0

o=- 381749076 381749076 IN IP4 10.1.36.219

s=-
c=IN IP4 10.1.36.219
t=0 0
b=AS:81
a=mptime:20
a=X-pc-csuites-rtp:62/51 64/51 60/51 60/50
The Capability Descriptor has been omitted from the default SDP; therefore,
the ‘‘Reduce Capability Descriptor’’ setting is irrelevant.
When the ‘‘Reduce Capability Descriptor’’ switch (0x00000008) is enabled,
and all other switches are set to their default values, the SDP becomes:
v=0
o=- 381749076 381749076 IN IP4 10.1.36.219
s=-
c=IN IP4 10.1.36.219
t=0 0
b=AS:81
a=mptime:20
a=X-pc-csuites-rtp:62/51 64/51 60/51 60/50
a=sqn: 0
In this example, the Capability Descriptor is reduced to only the information

required to relay support for UDPTL T.38 to the far end. This allows the far
end to support T.38 strict mode as defined in the PacketCable 1.5 NCS speci-
fication.
When the ‘‘Omit mptime’’ switch (0x00000080) is enabled, and all other
v=0
o=- 382093395 382093395 IN IP4 10.1.36.219
s=-
c=IN IP4 10.1.36.219
t=0 0

62 Chapter 3

b=AS:81
a=X-pc-secret:base64:XI51bgXR5MNUdaKXisS0tjYCc90x3f7jA+ojyam
W/O/M2BlCaejlrRLOdApR6w== 6LbN8ULCFGMjcR2T3l1uZuBcfWM2vfGn09
YTmR6OhHfQwC4eE+WWSX7AarnFPA==
a=X-pc-csuites-rtp:62/51 64/51 60/51 60/50
a=sqn: 0
a=cpar: a=rtpmap:97 G726-16/8000/1
a=cpar: a=rtpmap:98 G726-24/8000/1
a=cpar: a=rtpmap:2 G726-32/8000/1
a=cpar: a=rtpmap:99 G726-40/8000/1
a=cpar: a=fmtp:101 0-15,144,149,159
In this example, neither the a=ptime nor the a=mptime parameters are
included in the SDP since the packetization rate is the default (20 ms). If the
Call Agent had specified a different packetization rate (for example, 10 ms),
then the a=ptime parameter is included as follows:
v=0
o=- 382093395 382093395 IN IP4 10.1.36.219
s=-
c=IN IP4 10.1.36.219
t=0 0
b=AS:81
a=ptime:10
a=X-pc-secret:base64:XI51bgXR5MNUdaKXisS0tjYCc90x3f7jA+ojyam
W/O/M2BlCaejlrRLOdApR6w== 6LbN8ULCFGMjcR2T3l1uZuBcfWM2vfGn09
YTmR6OhHfQwC4eE+WWSX7AarnFPA==
a=X-pc-csuites-rtp:62/51 64/51 60/51 60/50
a=sqn: 0
a=cpar: a=rtpmap:97 G726-16/8000/1
a=cpar: a=rtpmap:98 G726-24/8000/1

a=cpar: a=rtpmap:2 G726-32/8000/1

a=cpar: a=rtpmap:99 G726-40/8000/1
a=cpar: a=fmtp:101 0-15,144,149,159
When the ‘‘Allow AES Encryption’’ switch (0x00100000) is disabled, and all
other switches are set to their default values, the SDP becomes;
v=0
o=- 381749076 381749076 IN IP4 10.1.36.219
s=-
c=IN IP4 10.1.36.219
t=0 0
b=AS:81
a=mptime:20
a=sqn: 0
a=cpar: a=rtpmap:97 G726-16/8000/1
a=cpar: a=rtpmap:98 G726-24/8000/1
a=cpar: a=rtpmap:2 G726-32/8000/1
a=cpar: a=rtpmap:99 G726-40/8000/1
a=cpar: a=fmtp:101 0-15,144,149,159
The last three CPFS bits (0x00001000, 0x00080000, and 0x01000000) are
related to RFC 2833. They are used in specific configurations and are
designed to skip CODEC negotiation. For example, when the ‘‘Nuera
RFC2833’’ feature is enabled, and all other switches are set to their default
values, the SDP becomes:
v=0
o=- 382250430 382250430 IN IP4 10.1.36.219
s=-
c=IN IP4 10.1.36.219
t=0 0

64 Chapter 3
b=AS:81
a=mptime:20
a=X-pc-secret:base64:Qb8GFLNXP4Z3yiyxFx1Ws9vLph9qG6bTIXezUlz
rwia7iiNvPPkVYdZhZ77NEQ== zZjgwXRR2j5F04lDXefPTV06PT8g31Hn5V
Ea6NJvFPFsPiraDeDI35EI8KO+4A==
a=X-pc-csuites-rtp:62/51 64/51 60/51 60/50
a=sqn: 0
a=cpar: a=rtpmap:97 G726-16/8000/1
a=cpar: a=rtpmap:98 G726-24/8000/1
a=cpar: a=rtpmap:2 G726-32/8000/1
a=cpar: a=rtpmap:99 G726-40/8000/1
a=cpar: a=fmtp:127 0-15,144,149,159
Note that this feature does not add SDP attributes, but modifies the Capabil-
ity Descriptor slightly. Payload type 127 is used for RFC 2833 support.
When the ‘‘Lucent RFC2833’’ switch is enabled, and all other switches are
set to their default values, the SDP becomes:
v=0
o=- 382318343 382318343 IN IP4 10.1.36.219
s=-
c=IN IP4 10.1.36.219
t=0 0
b=AS:81
a=mptime:20
a=X-pc-secret:base64:Kue6n+ZSGpXrB2iAJIAUQNst6AtAS7Ad7zC3oGP
ry9XKdURiy4Y6iLaDEhk5lg== GgaMtuqF7/egjksBpQ8SZeWnXCAlr1EeNH
AHV7EY0fv03Y0MYAYa1zz/lvO5dg==
a=X-pc-csuites-rtp:62/51 64/51 60/51 60/50
a=sqn: 0
a=cpar: a=rtpmap:97 G726-16/8000/1

a=cpar: a=rtpmap:98 G726-24/8000/1

a=cpar: a=rtpmap:2 G726-32/8000/1
a=cpar: a=rtpmap:99 G726-40/8000/1
a=cpar: a=fmtp:94 0-15,144,149,159
This feature does not add SDP attributes, but modifies the Capability
Descriptor. In this case, payload type 94 is used for RFC 2833 support.
Note: The three feature switches that affect RFC 2833 negotiation are mutu-
ally exclusive. At most, only one of the bits may be set in the CallP Feature
Switch. Enabling multiple RFC 2833 features may result in unexpected
behavior.
When the ‘‘RFC2833 Digits’’ switch (0x01000000) is enabled, and all other
v=0
o=- 382360201 382360201 IN IP4 10.1.36.219
s=-
c=IN IP4 10.1.36.219
t=0 0
m=audio 53560 RTP/AVP 0 101
b=AS:81
a=mptime:20 -
a=rtpmap:101 telephone-event/8000/1
a=fmtp:101 0-15
a=X-pc-secret:base64:rwZISK4HN5wlZzehiOBSEJXsRQbexmiwm1Ou4pE
nXFr4lSTXQYdAsKFT5lhkkw== tWyPwAvBg6EbSs4+FoY7rWOn0l8pcQPxGm
iwlNGPfo3Suehu0CncQ2egC4JQ6w==
a=X-pc-csuites-rtp:62/51 64/51 60/51 60/50
a=sqn: 0
a=cpar: a=rtpmap:97 G726-16/8000/1
a=cpar: a=rtpmap:98 G726-24/8000/1
a=cpar: a=rtpmap:2 G726-32/8000/1
a=cpar: a=rtpmap:99 G726-40/8000/1
a=cpar: a=fmtp:101 0-15,144,149,159

66 Chapter 3
Note that this feature affects the SDP, including the Capability Descriptor.
‘‘101’’ is added to the m= line and two new attributes indicate that the end-
point is prepared to receive RFC 2833 digits.
SDP Parameter The complete list of Call Processing features (including T.38 Fax Relay)
List Considera- requires a Session Description Protocol (SDP) parameter list longer than 512
tions bytes. Some CMSs and SIP proxies do not support a parameter list longer
than 512 bytes. To reduce the SDP parameter list size, set the ‘‘Suppress
SDP Capability Attribute Parameters’’ CallP Feature Switch (bit
0x00000100) to 1.
Setting this bit disables T.38 strict mode functionality; T.38 loose mode is
still available.
For more SDP-related options, see the CallP Feature Switch details in the
Touchstone Telephony Provisioning Guide.
PacketCable 1.5 TS5.2 and later versions of Touchstone firmware support the PacketCable 1.5
Extended Signal- NCS Extended Signaling MIB fax detection objects for T.38 signaling. The
ing following objects are supported:
pktcEnNcsMinimumDtmfPlayout
The minimum time a digit is played when the MTA receives an
RFC 2833 digit event.
pktcEnNcsEndPntQuarantineState
The endpoint state, based on the NCS quarantine states (for exam-
ple, notification or lockstep).
pktcEnNcsEndPntHookState
The hook state (on-hook or off-hook) of the endpoint.
pktcEnNcsEndPntFaxDetection
Configures whether the MTA uses T.38 when detecting a CNG
(calling) tone. The default is disabled, which prevents using T.38
(needed for Super G3 fax transmission, which supports a higher
transmission rate than T.38).
See the Touchstone Telephony Provisioning Guide for further details.
Image and Audio When originating a call, a SIP T.38 device may provide offers with both
Offer Handling image and audio media in INVITE and reINVITE messages. When pre-
sented with both media offers, Touchstone firmware behaves as follows
depending on the version:

• Versions prior to TS6.1 MSUP3 prefer image media and disable other
media.
• TS6.1 MSUP3 and newer versions choose the media type depending on
whether or not the eMTA detects a fax tone. If the eMTA detects a fax
tone, it selects image media; otherwise, it answers with active audio.
Super G3 FAX Support
TS6.1 and newer versions of Touchstone firmware support SuperG3 FAX

transmission, including V.8 data exchange detection.
When the eMTA detects the V.8 signal, fax transmission proceeds depending
on the setting of the arrisMtaDevSuperG3FaxRelay MIB object:
• When set to disable(0) (the default), the MTA uses the V.8 detection as
a trigger to set up the endpoint for FAX transmission (adjust the jitter
buffer, turn off echo cancellation) and allow the FAX machines to han-
dle the negotiation and transmit the fax using G.711.
• When set to enable(1), the MTA uses the V.8 detection as a trigger to
start T.38.
To switch the FAX call from SuperG3 to T.38, the Telephony Modem
mutes audio to prevent the FAX machine from negotiating to SuperG3
before switching to T.38. Depending on the T.38 negotiation, this
switch either forces the FAX machines to downshift to G3 speeds (<=
14.4) which is the current maximum rate supported for T.38 version 0,
or initiate the T.38 over RTP.
If the connection is negotiated for T.38 version 0, the audio remains
muted until the CMS transitions the connection to T.38. During the
muted period, the terminating fax machine receives silence. The maxi-
mum amount of this silence period can be controlled by the arrisM-
taDevT38Timeout MIB object. This object defaults to 30 seconds,
which is consistent with existing behavior. Alter this value only if FAX
transmissions are consistently failing due T.38 not re-trying.
If the connection has been negotiated for T.38 version 3 with RTP, the V.8
signal triggers the switch to T.38 RTP negotiated payload.
Loop Voltage Management Option
The Loop Voltage Management option is supported by all current Touchstone

hardware, and provides the following management policies. The MIB
objects responsible for this feature are arrisMtaDevLoopVoltagePolicy,
arrisMtaDevLoopVoltageResetTimeout, and

68 Chapter 3
arrisMtaDevLoopVoltageMaintTimeout.
The Advanced ‘‘Product Details’’ web page shows the current loop voltage
management settings under the ‘‘Optional Features’’ heading. If Policy 3 is
set, the web page displays the reset timer setting.
Policy 1: Constant When this option is selected, the MTA maintains loop voltage at all times
Loop Voltage with the following two exceptions:
• During firmware initialization of the line card. Touchstone MTAs
remove loop voltage for up to 1 second during firmware initialization,
although typically this time is shorter.
• When the unit has no power.
Policy 2: QAM When this option is selected, the MTA maintains loop voltage when it can
Carrier Detect lock onto a QAM carrier, including digital video QAM carriers. The
assumption is that if the Telephony Modem can recognize a carrier, the con-
nection is intact (has not been cut by a burglar).
When the Telephony Modem loses its carrier, after the T4 timeout expires
(20–30 seconds), the modem scans cached and preset frequencies, then scans
the entire spectrum. If the cable is truly cut, the scan takes 1 to 2 minutes to
complete. If the modem lost its carrier, but can detect other RF energy (such
as analog carriers), the scan can take up to 30 minutes to complete. If a
North American Telephony Modem does not detect any QAM carriers after
scanning the STD and HRC/IRC frequencies, it removes loop voltage then
continues with slow scanning.
Once the Telephony Modem removes loop voltage, it does not re-apply loop
voltage until it re-registers with MTA provisioning, except after a hard reset
(power-cycle or pressing the Reset button). After a hard reset, the Telephony
Modem maintains loop voltage until it completes STD and HRC/IRC fre-
quency scans.
Policy 3: MTA In- When this option is selected, the Telephony Modem maintains loop voltage
Service/Manual when in-service or during manually-initiated resets and T4 timeouts. The
Reset Telephony Modem is considered in-service when MTA TFTP is complete.
Both subscriber resets (pushing the Reset button) and headend-initiated resets
(SNMP, firmware upgrade) are considered manually initiated.
During a reset, if the MTA does not return to service within a provisionable
amount of time (8 to 1800 seconds, default 5 minutes), it removes loop volt-
age as a failsafe operation.
Once reset, the MTA returns to service. Any subsequent out of service con-
ditions are viewed as a potential malicious cable cut and the MTA removes

loop voltage after the T4 timer and the reset timer expire.
Plant Maintenance Timer
In TS4.5 and newer versions, Policy 3 provides a one-shot Plant Maintenance

Timer (PMT) to maintain loop voltage during extended plant maintenance
intervals. The PMT may be started by setting the arrisMtaDevLoopVolt-
ageMaintTimeout object, only over the RF interface, for 0 to 1440 minutes
(24 hours). While the PMT is running, the Telephony Modem maintains loop
voltage, regardless of connection status, until the timer expires or is reset
to 0. The exceptions are:
• Loop voltage may drop momentarily if the Telephony Modem re-regis-
ters during the maintenance interval.
• Rebooting or power-cycling the Telephony Modem clears the PMT;
loop voltage is then governed by the failsafe timer.
Policy 4: MTA In- When this option is selected, the Telephony Modem removes loop voltage
Service when the MTA is out of service. This is the default policy. Using this
option, the MTA goes through the following steps:
1 When applying initial AC power, Model 4 Telephony Modems apply
loop voltage to all lines. Model 5 and newer Telephony Modems do
not apply loop voltage on initial power-up.
2 While initializing (usually within 15 seconds of power-up), the MTA
removes loop voltage. If the Telephony Modem resets during this
step, it re-applies the loop voltage.
3 When the MTA completes TFTP and the lines are provisioned, it
applies loop voltage only to lines that are provisioned. If a provi-
sioned line goes off-hook before the MTA has contacted the call
server, the modem immediately attempts to contact the call server and
allows the call to continue. Loop voltage is applied even if the call
server cannot be reached.
4 After the MTA device is in service and there is an interruption to the
RF, loop voltage remains present on the lines until a T4 timeout
occurs (generally 20 to 30 seconds).

70 Chapter 3
The following table compares each policy with pre-TS4.4 behavior.

Stage Prior to TS4.4 Policy 1 Policy 2 Policy 3 Policy 4 (default)
First 10-15 sec- ON (Model 4) ON (Model 4) ON (Model 4) ON (Model 4) ON (Model 4)
onds after power- OFF (Model 5) OFF (Model 5) OFF (Model 5) OFF (Model 5) OFF (Model 5)
up
First 10-15 sec- Same status as Same status as Same status as Same status as Same status as
onds after reset prior to reset prior to reset prior to reset prior to reset prior to reset
Scanning for DS ON ON ON for first full ON until failsafe OFF
signal pass through timer expires,
spectrum, then OFF thereafter
OFF if no QAM
lock occurred
Ranging/ OFF for several ON except for Same status as Same status as OFF
Registering seconds, between <500ms dip dur- final state from final state from
CM registration ing MTA registra- scanning, OFF for scanning, then
complete and tion <500ms dip dur- OFF if timer
MTA TFTP com- ing MTA registra- expires during
pletion tion this process, OFF
for <500ms dip
during MTA reg-
istration
MTA Registered ON ON ON ON ON
Loss of signal ON ON ON ON ON
prior to T4
Scanning after T4 ON ON ON for first full ON until failsafe OFF
pass through timer expires,
spectrum, then OFF thereafter
OFF if no QAM
lock occurred
Inband DTMF Transmission
Touchstone firmware provides a feature to allow inband transmission of

DTMF tones, even if a line is configured for pulse-only dialing. Once a call
is established, Touchstone MTAs pass all DTMF tones received from a CPE
through the upstream voice path. MTAs configured for pulse-only dialing
operation drop any DTMF tones received before the call is fully established.
This feature allows a subscriber, provided with pulse-only dialing capabili-
ties, to send DTMF tones to the far end. This might be used for calling card
number entry, bank card data entry, automated service responses, and similar
services.
Inband DTMF transmission is automatically enabled after a call has been
established. No special configuration or changes to the dialing method are
needed to enable this feature.
Note: If a line is provisioned as pulse-dialing only, the MTA does not process
received DTMF digits beyond treating them as audio to pass to the upstream
voice path. If the CMS requests that the MTA notify the CMS of any col-
lected digits, the received DTMF tones will not be reported.

European Productization
Touchstone firmware provides support for Euro-PacketCable provisioning

and call processing parametrics. This includes support for the following
IETF MIBs:
• draft-ietf-ipcdn-pktc-signaling-09 (PKTC-IETF-SIG-MIB)
• draft-ietf-ipcdn-pktc-mtamib-06 (PKTC-IETF-MTA-MIB)
In order to enable European support on your system, the following require-
ments must be met:
• European firmware release (with a .EURO load name).
• The provisioning system must be fully Euro-PacketCable compliant.
NCS-based European firmware loads support only the Full PacketCable pro-
visioning method.
Gain Compensated Tone Generation
Touchstone firmware provides a patent-pending feature to automatically

adjust FSK and CAS tone generation to compensate for MSO-selected loss
value settings in certain country code templates (selected by ppCfgMTA-
CountryTemplate). This feature is supported only for the following country
code templates:
• All North American templates (0/−9, −3/−3, −5/−7, and −6/−6)
• All Netherlands templates (−3.5/−9.5 and 0/−9)
• Austria
• Belgium
• Czech Republic
• France
• Germany
• Hungary
• Ireland Japan
• Japan600
• Japan600L412

72 Chapter 3
• Poland
• Poland1010
• Portugal
• Switzerland
For these template selections, this feature automatically adjusts FSK and tone
levels to compensate for the loss plan values so that generated FSK and CAS
tones are always within applicable specifications. The specification used for
each template and the resulting FSK and CAS tone levels are given in the fol-
lowing table.
Country Templates Tone Spec CID Spec FSK Tone CAS Tone
Australia ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Austria ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Belgium ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Brazil ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Chile ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Czech Republic ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
France ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Germany ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Hungary ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Ireland ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Israel ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Mexico Bellcore Bellcore GR30-CORE −13.5 dBV ± 1.5 dB −16 dBV ± 2.5 dB
GR506/CORE
MexicoC Bellcore Bellcore GR30-CORE −13.5 dBV ± 1.5 dB −16 dBV ± 2.5 dB
GR506/CORE
Netherlands ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Netherlands09 ETSI 300-001 ETSI EN 300-659-1 14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
North America09 Bellcore Bellcore GR30-CORE −13.5 dBV ± 1.5 dB −20 dBm ± 1 dB
GR506/CORE
GR506/CORE
GR506/CORE
GR506/CORE
Norway ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Panama Bellcore Bellcore GR30-CORE −13.5 dBV ± 1.5 dB −16 dBV ± 2.5 dB
GR506/CORE
Poland ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Portugal ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Slovakia ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Spain ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB

Country Templates Tone Spec CID Spec FSK Tone CAS Tone
Sweden ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
Switzerland ETSI 300-001 ETSI EN 300-659-1 −14.5 dBV ± 2.5 dB −16 dBV ± 2.5 dB
1
Lab trials and interoperability testing only
Sinusoidal Ringing
The sinusoidal ringing feature is supported on Model 4 and newer Telephony

Modems, to address isolated instances of ringing failures on certain CPE
devices that do not conform to industry standard ringing specifications. For
these devices, the default trapezoidal ringing waveform cannot properly ring
the phone. Sinusoidal ringing closely emulates the ringing waveform pro-
vided by a Class 5 switch.
CAUTION
Potentially service-affecting
Sinusoidal ringing is supported only for North American templates on
Model 4 and newer hardware. Use of this feature with other templates, or
with other hardware, may result in loss of service.
Use the arrisMtaDevEndPntRingingWaveform object to specify sinusoidal

or trapezoidal ringing. Setting this MIB with a network management tool
makes the setting persistent over reboots; placing it in the configuration file
leaves the setting non-persistent.
NCS Retransmission Algorithm
All NCS messages initiated by the eMTA are retransmitted when necessary
according to the NCS retransmission algorithm defined in the PacketCable
1.5 Network-Based Call Signaling Protocol Specification, PKT-SP-
NCS1.5-I02-050812, section 7.4.2. This section describes the retransmission
algorithm implemented by TS5.0 and later versions of Touchstone firmware.
Configuration The following MIB objects, which may be configured on each endpoint of
Parameters the eMTA, control the NCS retransmission algorithm as follows:
• pktcNcsEndPntConfigThist (tHist) — Defines the lifetime of a trans-
action. An endpoint allows (2 * tHist) time from its initial transmission
of an NCS message for the Call Agent to respond before considering
the message lost and communications down. At this time the endpoint
enters the Disconnected state according to the PacketCable 1.5

74 Chapter 3
Network-Based Call Signaling Protocol Specification, PKT-SP-

NCS1.5-I02-050812, section 7.4.3.6. The default value for tHist is 30
seconds.
• pktcNcsEndPntConfigTSMax (TSMax) — Defines the amount of
time, beginning when an NCS message is initially transmitted, in which
an endpoint is allowed to retransmit. Note that when this time expires
and the endpoint stops retransmitting an NCS message, it may still wait
for a response until (2 * tHist) time elapses. Note also that the endpoint
may stop retransmitting before TSMax time if, for example, all Call
Agent IP addresses have been attempted and the maximum number of
retransmissions was reached. The default value for TSMax is 20 sec-
onds.
• pktcNcsEndPntConfigMax1 (Max1) — Defines the maximum number
of retransmission attempts allowed to a single IP address in the list of
Call Agent IP addresses, excluding the last IP address. Note that the
message is initially transmitted, and then retransmitted Max1 times for
a total of Max1 + 1. Once Max1 is reached, retransmission will con-
tinue on subsequent IP addresses if necessary. The default value for
Max1 is five retransmission attempts.
• pktcNcsEndPntConfigMax1QEnable (Max1QEnable) — After Max1
retransmission attempts, the endpoint is allowed to re-query the DNS
server to see if the list of IP addresses has changed. The eMTA re-
queries the DNS server at this time only if Max1QEnable is set to
TRUE. The default value for Max1QEnable is TRUE.
• pktcNcsEndPntConfigMax2 (Max2) — Defines the maximum number
of retransmission attempts allowed to the last IP address in the list of
Call Agent IP addresses. Note that the message is initially transmitted,
and then retransmitted Max2 times for a total of Max2 + 1. Once Max2
is reached, the endpoint will stop retransmitting, but may continue to
wait for a response as long as (2 * tHist) time has not yet lapsed. Note
also that Max2 may not be reached if, for example, TSMax time expires
before the endpoint has a change to reach Max2. The default value for
Max2 is seven retransmission attempts.
• pktcNcsEndPntConfigMax2QEnable (Max2QEnable) — After Max2
retransmission attempts, the endpoint once again re-queries the DNS
server to see if the list of IP addresses has changed, but only if
Max2QEnable is set to TRUE. The default value for Max2QEnable is
TRUE.
• pktcNcsEndPntConfigRtoInit (RtoInit) — Defines the initial amount
of time to wait after sending the initial NCS message before sending the
first retransmission. There are exceptions to the use of this value which
are described later. The default value for RtoInit is 200 ms.
• pktcNcsEndPntConfigRtoMax (RtoMax) — Defines the maximum
amount of time to wait before sending the next retransmission. As
mentioned, the initial retransmission of an NCS message takes place at
RtoInit time (with noted exceptions). All subsequent wait times are

exponentially longer based on a randomly chosen number between the

amount of time the endpoint waited last time and two times that value
up to a limit of RtoMax time. The default value for RtoMax is 4 sec-
onds.
List of Call Agent TS6.1 allows up to six IP addresses per Call Agent Fully Qualified Domain
IP Addresses Name (FQDN). If the DNS server is queried and more than six IP addresses
are found, only the first six returned in the list will be used. Note that
depending on configuration, the DNS server may return a randomly ordered
list of IP addresses; therefore, the list may appear to change on subsequent
re-queries causing unexpected behavior. Therefore, you should limit the list
of IP addresses configured on the DNS server to six or less.
The default values for the retransmission timers are based on the Call Agent
FQDN resolving to only a few IP addresses. It is important to adjust these
values accordingly based on the number of IP addresses actually configured.
For example, if all of the default values are used and the endpoint is required
to retransmit an NCS message. It will typically only retransmit on the first
three IP addresses since it takes on average about 6.5 seconds per IP address.
An endpoint’s Notified Entity is defined in PacketCable 1.5 Network-Based
Call Signaling Protocol Specification, PKT-SP-NCS1.5-I02-050812, to be
the Call Agent in which all NCS messages initiated from the MTA are sent.
Response messages are always transmitted to the source of the message
regardless of the Notified Entity’s location. In order to provide a quick
recovery from a Call Agent failover, TS6.1 automatically switches from
using one IP address to another in the list when it receives an NCS message
from its Notified Entity from an IP address in the list that it is currently not
using.
For example, the endpoint’s Notified Entity resolves to four IP addresses:
IP1, IP2, IP3, and IP4, and the endpoint is currently set up to use IP1 (that is,
starts by using IP1 when it needs to transmit an NCS message). In the mean-
time, the endpoint receives a command from its Notified Entity on IP4. At
this time, the endpoint marks IP4 as the first IP address to use when it needs
to transmit an NCS message. This typically saves time when a backup Call
Agent takes control of the endpoint. Note that this functionality is not
required by PacketCable, but is permitted since an endpoint is allowed to
begin transmission of any NCS message using any IP address from the list of
resolved Call Agent IP addresses.
Adaptive Retrans- As mentioned earlier, RtoInit is not always used as the initial delay between
mission the initial transmission of an NCS message to its first retransmission. TS6.1
supports optional functionality described in PacketCable 1.5 Network-Based
Call Signaling Protocol Specification, PKT-SP-NCS1.5-I02-050812, section
8.5.2, by providing a more adaptive retransmission algorithm. This adaptive
approach is only used after the Telephony Modem has successfully measured
the round trip delay of 100 Telephony Modem-initialed NCS messages.
After such time, the Telephony Modem maintains a value of the average
acknowledgment delay (AAD) based on the last 1000 messages initiated.

76 Chapter 3
The count is less than 1000 if the eMTA has not yet initiated 1000 messages,
but is always greater than 100. The eMTA also maintains a value of the aver-
age deviation (ADEV) from the average acknowledgment delay. The sample
size is limited to the last 1000 NCS messages, which provides more weight
to recent messages to more quickly adapt to network changes.
These two values are used to calculate the initial retransmission delay of all
NCS messages initiated. The formula for calculating the initial retransmis-
sion delay is as follows:
AAD + (2 * ADEV)
Subsequent retransmission delay is calculated by first doubling AAD, and

then computing a random number between (0.5 * AAD) and AAD. The
delay is then set to that random number plus (2 * ADEV), but limited by
RtoMax. This, once again, provides an exponential back-off with a random
element similar to the standard retransmission algorithm described earlier.
SIP eMTA Support
Touchstone SIP loads provide SIP support, as a dedicated, separate load.

The SIP load supports PacketCable provisioning methods, and the following
SIP-only provisioning methods:
• GUPI with MTA Configuration File Encryption
• GUPI MAC MTA
• GUPI Encrypted MAC MTA
SIP loads also support all other provisioning methods except Single MAC
provisioning.
SIP loads support basic call features, including:
• Call Waiting
• Disable Call Waiting
• Three Way Calling
• Call Forwarding
• Caller ID Blocking
• Caller ID
• Call Waiting Caller ID

• Advanced Hook Flash handling

Additional proxy-based call features may be supported, depending on the SIP
proxy selected. Contact ARRIS technical support or the SIP proxy vendor
for details.
A new ARRIS private SNMP MIB is designed to properly store SIP-related
provisioning data through a SIP MTA configuration file, and standard SIP
client information for required messaging.
Advanced Hook Several European countries process hook flash-based call features in different
Flash Behavior ways. Some countries use flash as a standalone signal (similar to the United
States). Other countries expect dial tone to be played following a hook flash.
The user then enters a DTMF digit used to determine what to do with the two
connections. This feature is referred to as the Advanced Flash Feature.
By default, Touchstone SIP firmware assumes North American-style hook
flash processing. Setting the ‘‘Advanced Flash Handling’’ SIP Feature
Switch bit (0x10000000) changes the behavior as follows.
Connected Alerting State Behavior
If a line on a Touchstone eMTA is connected to a remote party and receives a

new incoming call, the state of the line becomes ‘‘connected alerting.’’ This
means that there is a connected call as well as a new incoming call that has
triggered call waiting tone to be played. In this state, the user can press flash
on the phone to get dial tone. The user can then enter a DTMF digit from
0 to 3. The actions for each of those digits are:
Digit Action
DTMF 0 The eMTA rejects the incoming call and returns to the
original call. The line is now in the connected state.
DTMF 1 The eMTA disconnects the original call and answers the
incoming call that triggered the call waiting tone. The
line is now in the connected state.
DTMF 2 The eMTA puts the original call on hold and answers the
incoming call (same as North American hook flash
behavior). The line is now in the call waiting state.
DTMF 3 The eMTA conferences the incoming call with the origi-
nal call. The line is now in the conference state.
Call Waiting State Behavior
If a line on a Touchstone eMTA currently has one active call and one waiting
call (this state is entered by pressing flash followed by a DTMF 2 from the
connected alerting state as mentioned above) the state of the line is ‘‘call
waiting.’’ In this state, the user can press flash on the phone to get dial tone.
The user can then enter a DTMF digit from 0 to 4. The actions for each of
those digits are:

78 Chapter 3
Digit Action
DTMF 0 Disconnects the current call and connects the waiting
call (or plays ringback if the call has not been answered).
DTMF 1 The eMTA disconnects the waiting call and reconnects
to the current call. The line is now in the connected
state.
DTMF 2 (Invalid) Plays busy tone, then reconnects the current
call.
DTMF 3 The eMTA conferences the waiting call with the current
call. The line is now in the conference state.
DTMF 4 Blind transfer: the eMTA transfers the current call to the
outbound call. The eMTA plays stutter dial tone to indi-
cate success, or busy followed by reorder to indicate fail-
ure.
No digit The flash state times out after 15 seconds, briefly plays
busy tone, then reconnects to the current call.
Flash A second flash with no intervening DTMF digit restarts
dial tone.
3-Way Calling State Behavior
If a line on a Touchstone eMTA currently has one active call, and the user
presses flash to put the active call on hold and dials a new phone number, and
the remote party answers, the state of the line is ‘‘3-way calling.’’ In this
state, the user can press flash on the phone to get dial tone. The user can then
enter a DTMF digit from 1 to 4. The actions for each of those digits are:
Digit Action
DTMF 1 The eMTA disconnects the active call and answers the
waiting call. The line is now in the connected state.
DTMF 2 The eMTA puts the current call on hold and answers the
waiting call. The line transitions to the call waiting
state.
DTMF 3 The eMTA conferences the waiting call with the active
call (same as North American hook flash behavior). The
line is now in the conference state.
DTMF 4 The eMTA transfers the current call to the outbound call
and disconnects the line, leaving the other two parties
connected. Note that if the originator of a 3-way call
hangs up without transferring the call, all parties are dis-
connected.

SIP Proxy Penalty The SIP Proxy Penalty Box feature is available in SIP loads, and used when
Box Feature using SRV to address multiple SIP proxies. If a proxy does not respond to an
MTA message within 32 seconds, the MTA places that SRV record in the
penalty box (effectively blacklisting the proxy).
The penalty box can hold up to five proxy addresses. Proxies are released
from the penalty box only under the following conditions:
• A sixth proxy times out; the first proxy to be placed in the penalty box
is then released.
• The MTA is reset.
• All other known proxies have message send failures.
To enable the Penalty Box feature, set the 0x00400000 and 0x00000800 bits
in the SIP Feature Switch (sipCfgSipFeatureSwitch).
Multi-line Interface Guidelines
Touchstone TM508A and TM512A Multi-line eMTAs are designed to sup-

port small business and multiple dwelling unit (MDU) applications. The
TM508A and TM512A ringer and line interface circuits have capacity limits
that are consistent with engineering practices for traditional PBX and multi-
line voice systems.
Traffic Model The traffic model for multi-line eMTAs is based on the following assump-
tions:
• 10 CCS (Centum Call Seconds) or 0.28 Erlangs for each of the 12 lines
• 5 minutes per call
• 3 rings per call
• 75% inbound calls
These assumptions reflect a business application expecting fewer rings before
answering and more calls. A residential MDU application would differ
allowing for more rings before answering and fewer calls. Typical per line
CCS for residential applications is below 3 CCS and typical per line CCS for
business applications is below 9 CCS.
Using the above per-line 10 CCS traffic model, ARRIS calculated the proba-
bility of 3 lines ringing simultaneously to be approximately 0.01% and the
probability of 6 lines off-hook to be approximately 4%. The TM508A and
TM512A are designed to significantly exceed the requirements of this sce-
nario.

80 Chapter 3
Engineering Each line interface provides a 48Vdc nominal battery feed with 5 REN
Guidelines (Ringer Equivalent Number) per line ringing capacity. The eMTA supports a
maximum simultaneous load of 24 REN. High loop current (boost mode) is
a configurable option.
The TM508A and TM512A are designed for a business application per the
calling model described above. The probability of line interface event condi-
tions exceeding the described limitations in a real world environment are
believed to be extremely low. However, in a testing environment these limi-
tations can be exceeded through the use of a traffic simulation device. When
operated beyond the noted limitations, behavior such as reduced ringing lev-
els, ringing pre-trip and degraded voice quality may be experienced. The fol-
lowing table specifies the line conditions and simultaneous event transients
for which the TM508A and TM512A have been designed and tested. The
event conditions are described below.
Line Operation Requirement
Initial Line Condition Simultaneous Event Transient1
Event Condition
Lines Lines Ringing2 Lines Off-Hook Lines Ring
Off-Hook (REN) Detecting3 Tripping4
1 0 ≤ 24 6 0
2 0 ≤ 24 0 4
3 ≤6 ≤ 24 3 0
4 ≤6 ≤ 24 0 3
5 ≤ 12 0 0 0
1
Duration lasting up to 200 mS and coincident with the line condition defined in the columns to the left
2
Any number of available lines may be ringing as long as each line does not exceed 5 REN and the total
does not exceed 24 REN.
3
Detecting occurs during the silent interval of the ringing cadence or while a line is Idle (i.e. call origina-
tion)
4
Tripping occurs during the ringing interval of the ringing cadence
Detailed Event Event Condition 1

Conditions
All lines of the multi-line eMTA are initially on-hook with up to 12 lines
ringing. The event transient occurs when 6 lines are taken off-hook simulta-
neously either during the silent interval of the ringing cadence (ringing
waveform off) or while a line is idle.
Event Condition 2
ringing. The event transient occurs when 4 ringing lines are taken off-hook
simultaneously during the ringing interval (ringing waveform on) of the ring-
ing cadence.

Event Condition 3
Up to 6 lines of the multi-line eMTA are initially off-hook with up to 6 of the

on-hook lines ringing. The event transient occurs when 3 lines are taken off-
hook simultaneously either during the silent interval of the ringing cadence
(ringing waveform off) or while a line is idle.
Event Condition 4
Up to 6 lines of the multi-line eMTA are initially off-hook with up to 6 of the

on-hook lines ringing. The event transient occurs when 3 ringing lines are
taken off-hook simultaneously during the ringing interval (ringing waveform
on) of the ringing cadence.
Event Condition 5
ringing. The event transient occurs when up to 12 lines are taken off-hook
(not simultaneously) to originate/terminate a call. The number of lines taken
off-hook simultaneously must not exceed the requirements defined in Event
Conditions 1 through 4 and therefore the process of taking multiple lines off-
hook must be staggered before Event Condition 5 requirements can be satis-
fied.

82 Chapter 3

4 Data Features
This chapter describes data features supported in Touchstone firmware.
Upstream Service Flow Usage
Touchstone firmware supports a maximum of 16 Upstream Service Flows,

also referred to as service flow IDs (SIDs). In general, these SIDs are uti-
lized as follows:
• Primary best effort
• MGCP Signaling
• Bearer Path service flows
• up to 10 Service Flows available for classified/prioritized data services
About the Ethernet Interface
The TM508/TM512 multi-line Telephony Modems provide a single

10/100Base T Ethernet interface. Use this interface only for limited-band-
width applications, since heavy telephony usage requires most of the band-
width provided by a typical upstream.
About RIP
RIPv2 (Router Information Protocol) is a simple, standard routing protocol

for exchanging routing information between routers and gateway devices. Its
advantages include low bandwidth overhead and ease of configuration for use
in small networks.

84 Chapter 4
Touchstone support for RIPv2 can be enabled by adding a few lines to the
CM configuration file, allowing support for RIP as part of a ‘‘business ser-
vices’’ package.
Supported eMTAs TS6.1 supports RIP on the following Touchstone eMTAs:

• TM401, TM402
• TM501, TM502, TM504
• WTM552 (see below)
• TM508, TM512
• TM601, TM602, TM604
• TM608
• WTM652
Note: WTM552 and WTM652 RIPv2 support differs from support for other
Telephony Modems, as described below.
Compliance Touchstone firmware complies with the following IETF specifications:

• RFC2453 (RIPv2)
• RFC1724 (RIPv2 MIB, partial support)
• RFC2082 (RIP MD5 authentication)
WTM552/WTM652 The WTM552 and WTM652 support RIP on the Wireless Router Module
Considerations (WRM) rather than in the primary Telephony Modem processor. The WRM
implementation has several differences from other Telephony Modem imple-
mentations:
Provisioning
All Telephony Modems can provision RIP through the CM configu-
ration file. The WTM552 and WTM652 can also provision RIP
through SNMP, the CLI, the web pages, or remote provisioning.
Administration
All Telephony Modems can make changes to the RIP configuration
through the CLI. The WTM552 and WTM652 can also make
changes through SNMP or the web pages.

5 Provisioning Features
This chapter describes provisioning features supported in Touchstone

firmware.
General Provisioning Information
See the Touchstone Telephony Provisioning Guide for details about the provi-
sioning features listed in this section.
OUI Ranges The following table shows OUI support for various versions of Touchstone
firmware support.
Firmware Version OUI ranges supported
All versions 00:00:CA
TS4.4.20 and newer 00:13:11
00:15:96 00:15:CE
00:15:A2 00:15:CF
TS4.5 and newer
00:15:A3 00:15:D0
00:15:A4 00:15:D1
00:1D:CD 00:1D:D2
00:1D:CE 00:1D:D3
TS5.2.37 and newer 00:1D:CF 00:1D:D4
00:1D:D0 00:1D:D5
00:1D:D1 00:1D:D6
Queue Depth Size The upstream RTP queue size can be set by using the arrisMtaDevRTP-
Control TxQueueSize object in the configuration file.

86 Chapter 5
Jitter Buffer Touchstone firmware allows adjustments to the MTA jitter buffer behavior
Configuration and size.
• The arrisMtaDevVPJitterBufferMode object controls the jitter buffer
behavior (adaptive or fixed modes).
• The arrisMtaDevVPNomJitterBuffer object sets the nominal jitter buf-
fer size (in packets).
• The arrisMtaDevVPMaxJitterBuffer object sets the maximum jitter
buffer size (in packets).
TS5.0 and newer versions of Touchstone firmware allow further adjustments
to the jitter buffer for Voice Band Data (fax, modem, POS terminal) calls.
The following MIBs allow the eMTA to automatically override the normal
jitter buffer settings when it detects a Voice Band Data call:
• The arrisMtaDevVbdOverwriteLineBitmap MIB allows per-line con-
trol of jitter buffer override.
• The arrisMtaDevVbdOverwriteMinJitterBuffer MIB specifies the min-
imum Voice Band Data call jitter buffer setting.
• The arrisMtaDevVbdOverwriteNomJitterBuffer MIB specifies the
nominal Voice Band Data call jitter buffer setting.
• The arrisMtaDevVbdOverwriteMaxJitterBuffer MIB specifies the
maximum Voice Band Data call jitter buffer setting.
If you change these parameters with an SNMP manager, the new settings
take effect starting with the next phone call. See the Touchstone Telephony
Provisioning Guide for more information.
ToD Resynchro- When an eMTA registers, it queries a Time of Day (ToD) server for the cor-
nization rect time and date. Typically, the eMTA is left running and rebooted very
infrequently; the eMTA’s clock can drift and accumulate error over time.
TS5.0 and later versions of Touchstone firmware provide the ability for
Touchstone eMTAs to periodically query the ToD server after registration, to
maintain reasonably accurate time. The default behavior is to query only
during registration, but you can provision the eMTA to query the ToD server
in one-hour increments between one hour and 180 days.
This feature is unique to Touchstone firmware and eMTAs. See the Touch-
stone Telephony Provisioning Guide for more details.
Adjusting FSK and TS5.3 and later versions of Touchstone firmware allow adjustment of the
CAS Gain Levels FSK and CAS gain levels to improve control over CW-CID applications.
The following MIB objects can be used to adjust FSK and CAS gain levels:

arrisMtaDevLevelControlOffHookFSK
Gain adjustment for MTA-generated FSK tones (CID and VMWI)

arrisMtaDevLevelControlOffHookCAS
Gain adjustment for MTA-generated CAS tones (CID and VMWI)

arrisMtaDevLevelControlOffHookEnable
Set to enable(1) to enable use of the arrisMtaDevLevelCon-
trolOffHookCAS and arrisMtaDevLevelControlOffHookFSK MIB
objects for setting gain levels. The default is disable(0), which uses
the established arrisMtaDevGainControlFSK and arrisMtaDev-
GainControlCAS objects for both on-hook and off-hook levels.
The following table shows how the new and existing MIB objects interact.
arrisMtaDev. . .
LevelControl GainControl LevelControl
OffHookEnable FSK CAS OffHookFSK OffHookCAS
Controls both Controls both
Disabled on and off on and off Not used Not used
hook gains hook gains
Controls only Controls only Controls Controls
Enabled
on-hook gain on-hook gain off-hook gain off-hook gain
Proprietary Provisioning Modes
Besides standard PacketCable and DOCSIS-only provisioning modes, TS6.1

supports the following proprietary provisioning modes:
• PacketCable without KDC
• Global Universal Provisioning Interface (GUPI)
• Global Universal Provisioning Interface MAC MTA
• Global Universal Provisioning Interface MAC Encrypted MTA
• GUPI MAC MTA with TFTP Server Override
• Global Universal Provisioning Interface with MTA Configuration File
Encryption (Patent pending)

88 Chapter 5
• ARRIS modified version of Simplified PacketCable Provisioning

(Basic.1 and Basic.2)
• Single MAC/Single Configuration File
See the Touchstone Telephony Provisioning Guide for details about each pro-
visioning mode.
Note: European-specific versions of Touchstone firmware (i.e. .EURO loads)
support only the Full PacketCable provisioning mode.
Provisioning Use of a configuration file option introduced to Touchstone firmware after

Method Indicator TS4.1.22 may require use of the new Provisioning Method Indicator MIB.
MIB Generally, the affected features are Basic.1 and Basic.2 provisioning meth-
ods, newly defined county code templates, and Gateway Dial Pulse Support.
Provisioning The arrisMtaDevProvState object reports the current provisioning state of

Status MIB the MTA. The possible values of this MIB represent the following steps of
the provisioning sequence, and depend on the provisioning method used. See
the Touchstone Telephony Management Guide for details.
Selecting a Provisioning Mode
Touchstone firmware supports two different methods for selecting a provi-

sioning mode:
• (TS4.0 and newer) Set the arrisMtaDevProvMethodIndicator MIB
object in the CM configuration file. The MTA advertises the selected
provisioning mode (‘‘BASIC’’ for Basic.1 or Basic.2, ‘‘SECURE’’ for
others) in DHCP Option 60 sub-option 18.
• (TS5.2 and newer) Set the arrisMtaDevSpecialConfigurationOver-
rideEnable MIB object in the CM configuration file. The MTA adver-
tises all three PacketCable provisioning modes (SECURE, BASIC,
HYBRID) in DHCP Option 60 sub-option 18.
Note: The .EPA load variant enables the arrisMtaDevSpecialConfigu-
rationOverrideEnable object by default.

About ARRIS Enhanced Firmware Loading
The ARRIS Enhanced Firmware Loading feature (patent pending) provides

the ability to embed a common firmware load lineup table in configuration
files that matches firmware loads to Touchstone eMTAs. It supports a multi-
ple-vendor common configuration file that works with multiple Touchstone
eMTAs, while still being backward compatible with non-ARRIS equipment.
By eliminating the need for customized configuration files by product type,
Enhanced Firmware Loading simplifies firmware upgrades and improves the
general quality of the process.
Upgrade Process TS5.3 made some changes to the upgrade process. Previous firmware ver-
sions could reject a firmware download while a call was in progress; TS5.3
can download and store the new firmware while a call is in progress and
apply the new load once all lines are idle.
When a Touchstone eMTA ranges and registers with the headend and
receives the arrisCmDevSwTable object (see ‘‘Enhanced Firmware Loading
Options’’ on page 91 for a listing of relevant MIB objects) in its configura-
tion file, it proceeds as follows:
Download Acceptance
1 If the eMTA is running on battery power, the eMTA rejects the
download and the process stops. Otherwise, it proceeds to
step 2.
2 (TS5.2 and newer) The eMTA checks the docsDevSwAdmin-
Status object.
If the value is allowProvisioningUpgrade, proceed to step 3.

Otherwise, the device uses the standard docsDevSoftware
MIBs for its upgrade decision-making.
A setting of upgradeFromMgt is not allowed in the configura-
tion file and returns an error condition.
3 The eMTA checks the arrisCmDevSwAdminStatus object.
• If the value is allowArrisProvisioningUpgrade, proceed to
step 4.
• If its value is ignoreArrisProvisioningUpgrade, the device
uses the standard docsDevSoftware MIBs for its upgrade
decision-making.

90 Chapter 5
A setting of upgradeFromArrisMgt is not allowed in the con-

figuration file and returns an error condition (see the Touchstone
Telephony Troubleshooting Guide for details).
4 The eMTA scans the arrisCmDevSwTable, looking for matches
between arrisCmDevSwHwModel and its known model type.
• If it finds a match, it checks the optional arrisCmDevSwHw-
Rev for a match to its known hardware revision. A blank
entry for arrisCmDevSwHwRev is a match only if there is no
entry with an explicit match to the eMTA’s hardware revision.
Upon finding a match, proceed to step 5.
• If it cannot match the model type or find a qualifying revision,
then the system logs an error (see the Touchstone Telephony
Troubleshooting Guide for details) and aborts to the standard
DOCSIS upgrade process.
5 The eMTA reads the arrisCmDevSwTable entry matched in
step 4, retrieves the arrisCmDevSwServerAddressType and
arrisCmDevSwServerAddress to obtain the IPv4 or IPv6
address of the TFTP server, and the ArrisCmDevSwFilename
for the firmware file name to download, then downloads its
firmware.
Download Application
After downloading the firmware:
1 The eMTA checks the arrisMtaDevSwDnldNoSvcImpact
object.
If the value is disabled, the eMTA immediately applies the
firmware and resets. Otherwise, proceed to step 2.
2 The eMTA checks for calls in process and applies the new
firmware load only if all MTA lines are idle. Any of the follow-
ing conditions constitute an active connection for the purpose of
firmware application:
• One or more lines off-hook
• Connection currently assigned to the line (including for 911
calls)
• Playing VMWI
• Ringing a line
3 If an active connection exists, the eMTA waits for all lines to go
idle then starts a 30-second timer.
4 If the timer expires with no lines becoming active, the eMTA
applies the firmware and resets; otherwise, it returns to step 3.

Note that Touchstone firmware disables Enhanced Firmware Loading if the

value of docsDevSwAdminStatus is not allowProvisioningUpgrade. This
change allows deployment of provisioning files where the docsDevSw-
AdminStatus object is not specified, but the Enhanced Firmware Loading
and the normal upgrade TLVs are specified. Upgrading this behaves as fol-
lows:
• Non-ARRIS devices upgrade using the DOCSIS upgrade objects.
• ARRIS devices automatically use Enhanced Firmware Loading to run
the correct firmware load.
• An ARRIS eMTA, manually-upgraded using SNMP, has the docsDev-
SwAdminStatus set to ignoreProvisioningUpgrade; this disables
Enhanced Firmware Loading on that device. To restore the firmware
load specified in the load lineup, change docsDevSwAdminStatus to
allowProvisioningUpgrade and reset the modem using docsDev-
ResetNow.
During the server communication and firmware image file download, there is
no interruption to eMTA operation. During this phase of the procedure, all
operation continues normally. However, per the DOCSIS and PacketCable
specifications, once the image is downloaded into the eMTA, the device must
automatically execute a reset operation to copy the new image into the active
flash memory and apply the functionality of the new image.
Enhanced Enhanced Firmware Loading is controlled by several SNMP MIB variables,

Firmware Loading described below. These variables are all ARRIS-specific and do not interfere
Options with non-ARRIS eMTAs. All of these variables can be added to the vendor-
specific section of configuration files. The ARRIS PacketACE software (ver-
sion 3.2 and higher) also supports these objects for easy addition to configu-
ration files. Each object can also be controlled remotely using standard
SNMP MIB browser software.
Touchstone firmware can reject a firmware upgrade while a call is in
progress, complying with a PacketCable 1.5 requirement to minimize service
impacts. See the Touchstone Telephony Provisioning Guide for details.
ArrisCmDevSw- Enhanced Firmware Loading has a feature switch named arrisCm-

AdminStatus MIB DevSwAdminStatus that parallels the standard DOCSIS docsDevSw-
Feature Switch AdminStatus object. This object has three different settings:
upgradeFromArrisMgt(1)
Immediately upgrade the device using Enhanced Firmware Loading.
If a valid entry can’t be found then an error condition is returned.
This is not a valid setting for this MIB in configuration files.
allowArrisProvisioningUpgrade(2)
Allow provisioning file upgrade using Enhanced Firmware Loading.
This setting overrides the DOCSIS upgrade mechanism unless a
valid entry cannot be found in the load lineup table for the device.

92 Chapter 5
If a valid entry cannot be found, then an error is returned and the

standard DOCSIS upgrade mechanism takes over.
ignoreArrisProvisioningUpgrade(3)
Disable Enhanced Firmware Loading and use the standard DOCSIS
upgrade mechanism. This is the power up default setting for all
ARRIS products.
ArrisCmDev- The arrisCmDevSwTable drives the main decision-making algorithm of

SwTable MIB Enhanced Firmware Loading. The table can handle up to 32 load lineups. If
you try to add more than 32 entries to this table, the eMTA generates an ille-
gal SNMP SET during the ranging and registering process. Per DOCSIS
specifications, the eMTA does not range and register until this problem is
corrected. Each row of the table contains the following MIB objects:

MIB column variable Description Valid Setting Req/Opt

ArrisCmDevSwCus- A customer-defined string 1–64 byte ASCII string* Optional
tomerLoadId that can be added to iden-
tify load lineups. This
string is unused by the
firmware upgrade mecha-
nism.
ArrisCmDevSwHw- Defines which Touchstone 1–16 byte ASCII string* Required
Model hardware model type this
row applies to.
ArrisCmDevSwHw- Defines the Touchstone Integer, 0 to 255 Optional
Rev hardware revision of the
currently defined model.
arrisCmDe- Specifies the IP address 0–2 Required
vSwServerAd- type used for the firmware
dressType upgrade server address: 0
(null), 1 (IPv4), or 2
(IPv6).
arrisCmDe- Specifies the IPv4 or IPv6 Any valid IP Required
vSwServerAddress address of the TFTP
server to use for firmware
upgrades.
arrisCmDevSwServer Defines an IP address of Any valid IP Deprecated
the TFTP server to use for
firmware upgrades.
Replaced by the
arrisCmDevSwSer-
vareAddressType and
arrisCmDevSwSer-
vareAddress objects. See
below for interactions with
the new addressing
objects.
ArrisCmDevSwFile- Defines what file name the 1–64 byte ASCII string* Required
name device should request
from TFTP server.
* – 1 byte reserved for null terminator
Server Address Object Interactions
The following interactions take place between the deprecated arrisCmDe-

vSwServer MIB object and the new arrisCmDevSwServerAddress object.
These interactions allow for backward-compatibility with older Touchstone
firmware versions that do not support IPv6 operation.

94 Chapter 5
• Setting arrisCmDevSwServer with an IPv4 address automatically

updates the arrisCmDevSwServerAddress with the configured IPv4
address, and sets the arrisCmDevSwServerAddressType to indicate
an IPv4 address.
• Setting arrisCmDevSwServerAddressType to indicate an IPv4
address, and the arrisCmDevSwServerAddress to an IPv4 address,
automatically sets the arrisCmDevSwServer object to the configured
IPv4 address.
• Setting arrisCmDevSwServerAddressType to indicate an IPv6
address, and arrisCmDevSwServerAddress to an IPv6 address, auto-
matically sets arrisCmDevSwServer to 0.0.0.0.
arrisCmDevSwHwModel Values
The following list shows common arrisCmDevSwHwModel ASCII strings

for firmware loads supporting Enhanced Firmware Loading:
• TM102A • TP304A • TM402H • TM504G • TM602B

• TM102B • TP402A • TM402P • TM504H • TM602G
• TM102D • TP404A • TM501A • WTM552A • TM602H
• TM102E • TM401A • TM501B • WTM552B • TM604G
• TM202A • TM401B • TM502A • WTM552G • WTM652A
• TM202B • TM402A • TM502B • WTM552H • WTM652B
• TM202P • TM402B • TM502C • TM508A • WTM652G
• TP204A • TM402C • TM502G • TM512A
• TP302A • TM402G • TM502H • TM602A
Example Lineup Below is an example firmware lineup table for various ARRIS Touchstone
products. This table is mirrored in the following configuration file excerpt.
In this example, Enhanced Firmware Loading is assumed enabled by setting
arrisCmDevSwAdminStatus to allowArrisProvisioningUpgrade(2).
Customer Load Id HW Model HW Revision TFTP IP Address Upgrade Filename

Lab NA TM502 Rev. 2 TM502G 2 10.1.50.21 TS0500_07112006.bin
Node 3 NA TM402 Rev. 3 TM402P 3 10.1.50.21 TS0500_07112006.bin
Euro TM402 Rev. 3 TM402Q 3 10.1.51.21 TS0401_09302003.bin
Euro TM402 Non-Rev. 3 TM402Q blank (see note 1) 10.1.51.21 TS0401_09222003.bin
Node 1 TM202 Non-Rev. 2 TM202P blank (see note 1) 10.1.52.21 TS030203_090503A.bin
Node 2 TM202 Rev. 2 TM202P 2 10.1.52.21 TS030203_090503A.bin
Note 1: Not specifying a hardware revision makes that entry a wildcard for any unspecified hardware revisions.

Note: The Enhanced Firmware Loading feature does not distinguish between
dual-mode and single-mode TM601B/TM602B Telephony Modems. Speci-
fying a TS5.2 load for a dual-mode Telephony Modem causes the Telephony
Modem to ignore North American DOCSIS carriers.
Example Configu- The following configuration file excerpt implements the firmware lineup
ration File Excerpt shown above. This excerpt would typically be placed in a vendor-specific
section of a configuration file.
SnmpMib = arrisCmDevSwAdminStatus.0 2
SnmpMib = arrisCmDevSwCustomerLoadId.1 "Lab NA TM502 Rev. 2"
SnmpMib = arrisCmDevSwHwModel.1 "TM502G"
SnmpMib = arrisCmDevSwHwRev.1 2
SnmpMib = arrisCmDevSwServer.1 10.1.50.21
SnmpMib = arrisCmDevSwFilename.1 "TS0500_07112006.bin"
SnmpMib = arrisCmDevSwCustomerLoadId.2 "Node 3 NA TM402 Rev. 3"
SnmpMib = arrisCmDevSwHwModel.2 "TM402P"
SnmpMib = arrisCmDevSwCustomerLoadId.3 "Euro TM402 Rev. 3"
SnmpMib = arrisCmDevSwHwModel.3 "TM402Q"
SnmpMib = arrisCmDevSwCustomerLoadId.4 "Euro TM402 Non-Rev. 3"
SnmpMib = arrisCmDevSwHwModel.4 "TM402Q"
SnmpMib = arrisCmDevSwCustomerLoadId.5 "Node 1 TM202 Non-Rev. 2"
SnmpMib = arrisCmDevSwFilename.5 "TS030203_090503A.bin"
SnmpMib = arrisCmDevSwCustomerLoadId.6 "Node 2 TM202 Rev. 2"
SnmpMib = arrisCmDevSwFilename.6 "TS030203_090503A.bin"
Rejecting a Down- TS4.5 MSUP2 and newer versions can reject a firmware upgrade while a call
load Request is in progress, complying with a PacketCable 1.5 requirement to minimize
service impacts. See the Touchstone Telephony Provisioning Guide for
details.

96 Chapter 5
Upgrading from Upgrading from NCS loads newer than TS4.4.20 to TS6.1 SIP loads is
NCS to SIP Loads straightforward: replace the load name in the provisioning file, and add SIP
MIB objects as required, then reboot the eMTA.
Customers upgrading from TS4.4.20 or earlier NCS-based versions of
Touchstone firmware to a TS4.5 or newer SIP-based release must first
upgrade to TS4.4.20 or a newer release (either NCS- or SIP-based) as an
intermediate step before upgrading to a newer SIP load. The upgrade pro-
ceeds as follows:
1 The operator initiates an upgrade to the intermediate release.
2 The eMTA upgrades the boot loader firmware, then reboots both the
CM and MTA.
3 The eMTA automatically upgrades the firmware image then reboots
(normal MTA upgrade sequence).
4 The operator initiates the upgrade to the new SIP release.
5 The eMTA automatically upgrades to the SIP firmware image then
reboots (normal MTA upgrade sequence).
Note: ARRIS recommends using either TS4.4.28B or TS4.4.41 as the inter-
mediate load (both loads are NCS-based), especially if you plan for any
delays between the intermediate release and the final SIP release.
Dual-Mode Operation
TM601B, TM602B, and WTM652B Telephony Modems are available in

dual-mode versions that can configure themselves for on DOCSIS or Euro-
DOCSIS operation based on the type of downstream first detected.
When a dual-mode Telephony Modem ranges and registers for the first time,
it stores the detected signal type in non-volatile memory. During subsequent
reboots, it automatically scans for the stored signal type.
If a dual-mode Telephony Modem is moved to a plant with a different signal
type, it uses several methods to detect and lock to a new signal. For example,
if a dual-mode Telephony Modem had originally ranged and registered on a
North American DOCSIS plant, and then was moved to a Euro-DOCSIS
plant, it would use the following procedure:
1 Scan all cached frequencies using annex B.
2 Perform a general scan for downstream carriers, switching between
Annex A and Annex B, up to 20 times.
3 Scan all cached frequencies using annex A.

4 Repeat step 2 (up to 20 times).

5 Scan all cached frequencies using annex B again.
Post-Provisioning
Touchstone SIP loads provide two post-provisioning methods for making

line-level changes to the MTA provisioning without requiring a reset. Post-
provisioning allows activation of inactive lines (or vice versa) as well as other
line changes.
The supported post-provisioning methods are:
• SNMP—changing line-level MIB objects is now supported. To ensure
that changes are not lost at the next MTA reset, you must also make the
changes to the MTA provisioning file.
• Configuration file re-download—the eMTA accepts and applies line-
level changes in the MTA configuration file without resetting.
Companion Utilities
PacketACE The ARRIS PacketACE tools are designed for use with Touchstone firmware.
PacketACE is a configuration editor that simplifies building configuration
files from common fragments.
See the release notes to determine which version of PacketACE to use with
TS6.1 firmware. See the PacketACE Configuration Tools User’s Guide for
more information about PacketACE.
Provisioning Trial and Testing Features
The features in this section are implemented only for lab trial and interoper-
ability testing.

98 Chapter 5
Maximum Sched- Maximum Scheduled Codes (MSC) is a DOCSIS 2.0 feature that provides a
uled Codes (MSC) compromise between required transmit power and SCDMA channel capacity
in plants where upstream attenuation would otherwise limit the number of
active codes per channel.
For example, DOCSIS standards limit transmit power of a cable modem to
53 dBmV. When spread over 128 active codes, the effective power per code
is 32 dBmV. By enabling MSC, an operator can (through the CMTS) guar-
antee that individual modems will be required to transmit up to a limited
number of active codes simultaneously. In this example, by limiting MSC to
32 codes, the modem can increase the transmit power by 6 dB per code. The
trade-off is potentially higher fragmentation and increased upstream latency.
This feature must be supported in the CMTS and enabled in the modem’s
configuration file.

6 Management and Trou-
bleshooting Features
This chapter describes management and troubleshooting features supported

in Touchstone firmware.
Management and Status Monitoring Interfaces
Touchstone firmware provides the following interfaces for management and

status monitoring. The Touchstone Telephony Troubleshooting Guide pro-
vides more details of each interface.
Front panel LEDs
The front panel LEDs can be used to track the ranging and register-
ing process at initial startup. During normal operation, the LEDs
show the status of data and telephony interfaces.
Web-based troubleshooting interface
A simple HTTP (web) server provides several pages showing status,
logs, and other information about the Telephony Modem. You can
access the web pages from either the subscriber (CPE) side or net-
work (cable) side, or disable access from either side.
SNMP
Using an SNMP-based network management system, you can read
cable modem and MTA MIB variables to determine the status of
Touchstone eMTAs and (in some cases) change the MIBs to correct
an issue.
Logging/Syslog
The MTA and cable modem can be configured to send logs and
alarms to a Syslog server. Touchstone firmware supports logs and
alarms required by DOCSIS and PacketCable standards as well as
an extensive set of proprietary messages.

100 Chapter 6
CLI
Touchstone firmware supports a low-level command-line interface
to the eMTA internals. You can access the CLI using telnet, after
enabling access through the web-based interface.
MTA Monitoring Features
Touchstone firmware provides a variety of features, beyond basic network

monitoring MIBs. The features described in this section apply to TS4.5
MSUP2 and newer releases.
End-of-Call TS4.5 MSUP2 and newer releases provide MIB objects for monitoring MTA
Statistics end-of-call statistics.
The monitoring MIB is broken into groups under arrisMtaDevTrace:
• Objects that report on a device level (the counter values represent the
sum total for all endpoints). These objects are indexed by the endpoint
number in the MIB table arrisMtaDevCallStatsEntry.
• Objects that report on a per call level (the counter values represent the
total count for the most recently completed call on an endpoint), under
arrisMtaDevTrace.
• Objects that control and reset counters, under MtaDevControl.

The following figure represents the general structure of these MIBs.
Device−Level MIB Objects
MIB Object Value

Sum of all endpoint values
Per−call level Per−call level

MIB objects MIB objects
MIB object value MIB object value

endpoint #1 endpoint #2

Monitoring of Touchstone firmware can generate an Loss of Comms trap when the eMTA
Quarantined quarantines (defers, perhaps indefinitely) a CallP event while in the discon-
Events nected state (loss of communications with the call server). See the Touch-
stone Telephony Management Guide for details.
Per-Call Syslog Touchstone firmware can generate a Syslog report of call status and monitor-
Reporting ing information on a per-call basis.
In addition to statistical data, the Syslog report can also include up to the last
4K bytes of signaling messages associated with the last call in a circular buf-
fer. The Syslog report can be configured to supply only statistical data, or
statistical data and signaling messages.
Syslog reporting can be enabled or disabled using the arrisMtaDevEnable-
CallStatsSyslogRpt MIB object.
Signaling Trace Touchstone firmware can report, through Syslog, a trace of all incoming and
outgoing signaling messages on an MTA. A new MIB object controls trac-
ing. See the Touchstone Telephony Management Guide for details and con-
siderations.
The last MTA signaling message sent is available through a set of MIBs. See
the Touchstone Telephony Management Guide for details.
Provisioning The arrisMtaDevProvState MIB reports the current provisioning state of the
Status MIB MTA. The possible values of this MIB represent the following steps of the
provisioning sequence, and depend on the provisioning method used. See the
Touchstone Telephony Management Guide for details.
DHCP Information TS5.0 and later versions of Touchstone firmware provide information about
Over SNMP the Touchstone eMTA’s DHCP parameters and configuration through SNMP.
The following read-only MIBs contain current DHCP information for the
cable modem. They are available only from the CM IP address.
arrisCmDevDhcpCmIpAddr
Displays the currently leased IP address.
arrisCmDevDhcpCmSubNetMask
Displays the current IP subnet mask in use.
arrisCmDevDhcpCmGatewayIpAddr
Displays the current IP gateway address in use.
arrisCmDevDhcpCmConfigFile
Displays the CM configuration file to be retrieved.

102 Chapter 6
arrisCmDevDhcpState
Displays the current DHCP state of the CM: idle(0), discover(1),
selecting(2), requesting(3), bound(4), renew(5), rebind(6).
arrisCmDevDhcpPrimaryDhcpServerIpAddr
Displays the primary DHCP server address.
arrisCmDevDhcpTftpSvrIpAddr
Displays the current TFTP Server IP address in use.
arrisCmDevDhcpTimeSvrIpAddr
Displays the current ToD server IP address in use.
arrisCmDevDhcpCmTimeOffset
Displays the current Time offset being used by the CM.
arrisCmDevDhcpPrimaryTeleDhcpSvr
Displays the primary DHCP server being used by the MTA.
arrisCmDevDhcpSecondaryTeleDhcpSvr
Displays the secondary DHCP server being used by the MTA.
arrisMtaDevDhcpOfferedLeaseTime
Displays the Offered IP Lease time, in seconds.
arrisCmDevDhcpLeaseTimeRemaining
Displays the Remaining IP Lease time, in seconds.
arrisCmDevDhcpTimeUntilRenew
Displays the current time, in seconds, remaining before the MTA
starts the lease renewal process.
arrisCmDevDhcpTimeUntilRebind
Displays the current time, in seconds, remaining before the CM
starts the lease rebinding process.
The following read-only MIBs contain current DHCP information for the
MTA. They are available from both the CM and MTA IP addresses.
arrisMtaDevDhcpMtaIpFQDN
Displays the currently defined MTA FQDN.
arrisMtaDevDhcpMtaIpAddr
Displays the currently leased IP address.
arrisMtaDevDhcpMtaSubNetMask
Displays the current IP subnet mask in use.
arrisMtaDevDhcpMtaGatewayIpAddr
Displays the current IP gateway address in use.
arrisMtaDevDhcpMtaConfigFile
Displays the MTA configuration file to be retrieved.

arrisMtaDevDhcpState
Displays the current DHCP state of the MTA: idle(0), discover(1),
selecting(2), requesting(3), bound(4), renew(5), rebind(6).
arrisMtaDevDhcpPrimaryDhcpSvrIpAddr
Displays the primary DHCP server address.
arrisMtaDevDhcpSecondaryDhcpSvrIpAddr
Displays the secondary DHCP server address.
arrisMtaDevDhcpPrimaryDNSSvrIpAddr
Displays the primary DNS server address.
arrisMtaDevDhcpSecondaryDNSSvrIpAddr
Displays the secondary DNS server address.
arrisMtaDevDhcpOfferedLeaseTime
Displays the current IP Lease time expressed in seconds.
arrisMtaDevDhcpLeaseTimeRemaining
Displays the remaining IP Lease time expressed in seconds.
arrisMtaDevDhcpTimeUntilRenew
starts the lease renewal process.
arrisMtaDevDhcpTimeUntilRebind
starts the lease rebinding process.
arrisMtaDevDhcpPktcOptionId
Displays the PacketCable DHCP Option ID of 122/177.
arrisMtaDevDhcpSvcProviderSnmpEntity
Current FQDN of the Service Provider’s SNMP Entity.
arrisMtaDevDhcpKerberosRealmFqdn
FQDN of the Kerberos Realm.
arrisMtaDevDhcpRequestTgt
A boolean value that indicates whether an MTA should or should
not utilize a TGT (Ticket Granting Ticket) when obtaining a service
ticket for one of the PacketCable application servers.
arrisMtaDevDhcpProvTimer
Defines the maximum time allowed for the MTA provisioning
process to complete. If this timer expires before the MTA has com-
pleted the provisioning process, the MTA should reset the timer and
re-start its provisioning process from the beginning.
arrisMtaDevDhcpSecTicketInvalid
Defines a Kerberos Ticket Control Mask that instructs the MTA to
invalidate the specific application server Kerberos ticket(s) that are
stored locally in the MTA NVRAM.

104 Chapter 6
Line Card Status The arrisMtaDevLineCard MIB object indicates the line card status: oos(0),
MIB idle(1), addressing(2), talking(3), frwd-disc(5), ringing(6), onhook-tx(7),
plo(14).
Voice Quality The Voice Quality Monitoring (VQM) feature provides a per-line history of
Monitoring voice call quality metrics. VQM data is available from SNMP, CLI, and
HTTP. The information provided is an extension of RFC 3611 recommenda-
tions.
Touchstone firmware supports VQM on Model 4 and newer Telephony
Modems, including multi-line models. Metrics are provided for both the
near-end (MTA) and far-end sides of the call (the far-end MTA must also
support RTCP-XR). Remote VQM is disabled by default.
Note: Touchstone firmware does not support reporting VQM data to the
CMS. The eMTA ignores any VQM requests from the CMS.
A monitoring feature provides a Syslog notification if MOS scores fall below
a threshold specified by the arrisMtaDevVqmThresholds objects.
See the Touchstone Telephony Troubleshooting Guide for usage instructions
and a listing of VQM-related MIB objects.
The following list briefly describes the metrics returned by the VQM feature,
noting metrics that are extensions of RFC 3611. See RFC 3611 for full
descriptions of those metrics.
Call End Time (extension)
A timestamp defining the time the call ended.
Call Start Time (extension)
A timestamp defining the time the call began.
Call Duration (extension)
The total length of the call time, in hours, minutes, and seconds.
Line Number (extension)
The phone line used for this call.
Remote IP Address (extension)
The IP address of the destination endpoint.
CW Errors(extension)
The number of codeword errors that occurred during the call.
CW Error Rate (extension)
The ratio of errored codewords to total received codewords during
the call.
SNR (extension)
The signal-to-noise ratio, in dB.

MicroReflections (extension)
Microreflection power, in dBc. A microreflection is energy on a
transmission line that is reflected back toward the point of origin
due to an impedance mismatch.
Downstream Power (extension)
The downstream power, in dBmV, measured at the eMTA.
Upstream Power (extension)
The upstream power, in dBmV, measured at the eMTA. The average
Echo Quality Index (EQI). The EQI is an estimate of the quality of
echo signals presented to the LEC. The value displayed is
between 0 and 1, with higher values indicating higher echo quality.
Low EQI measurements represent a high risk for echo-related prob-
lems.
EQI Minimum (extension)
The minimum measured Echo Quality Index.
EQI Maximum (extension)
The maximum measured Echo Quality Index.
EQI Instantaneous (extension)
The last measured Echo Quality Index value.
Loss Rate
The fraction of RTP data packets from the source, lost since the
beginning of reception. Valid range: 0 (no packet loss) to 255 (near-
complete packet loss). Duplicated packets and discarded packets
are not counted as lost. However, significantly late packets may be
counted as lost.
Discard Rate
The fraction of RTP data packets from the source that have been dis-
carded since the beginning of reception, due to late or early arrival,
under-run, or overflow at the receiving jitter buffer. Valid range: 0
(no packets discarded) to 255 (nearly all packets discarded).
Burst Density
The fraction of RTP data packets within burst periods since the
beginning of reception that were either lost or discarded. Valid
range: 0 (no packets lost/discarded, or no packets received) to 255
(nearly all packets lost/discarded).
Gap Density
The fraction of RTP data packets, within inter-burst gaps since the
beginning of reception, that were either lost or discarded. Valid
range: 0 (no packets lost/discarded, or no packets received) to 255
(nearly all packets lost/discarded).
Burst Duration
The mean duration, in milliseconds, of the burst periods that have
occurred since the beginning of reception. The duration of each
period is calculated based upon the packets that mark the beginning

106 Chapter 6
and end of that period. If there have been no burst periods, the burst
duration value is zero.
Gap Duration
The mean duration, in milliseconds, of the gap periods that have
occurred since the beginning of reception. The duration of each
period is calculated based upon the packet that marks the end of the
prior burst and the packet that marks the beginning of the subse-
quent burst.
In the case of a gap that occurs at the beginning of reception, the
sum of the timestamp of the prior burst packet and the duration of
the prior burst packet are replaced by the reception start time. In the
case of a gap that occurs at the end of reception, the timestamp of
the subsequent burst packet is replaced by the reception end time. If
there have been no gap periods, the gap duration value is zero.
Round Trip Delay
The most recently calculated round trip time between RTP inter-
faces, in milliseconds.
End System Delay
The most recently estimated end system delay, in milliseconds. End
system delay is the sum of the total sample accumulation and
encoding delay associated with the sending direction and the jitter
buffer, decoding, and playout buffer delay associated with the
receiving direction.
Signal Level
The voice signal relative level — the ratio of the signal level to a
0dBm0 reference, expressed in decibels. Signal level is measured
only for packets containing speech energy. This measurement pro-
vides a real time indication that the signal level may be excessively
high or low.
signal level = 10 Log10 ( rms talkspurt power(mW) )
A value of 127 indicates that this parameter is unavailable. Typical

values are in the −15 to −20 dBm range.
Noise Level
The ratio of the silent period background noise level to a 0 dBm0
reference, expressed in decibels.
noise level = 10 Log10 ( rms silence power (mW) )
A value of 127 indicates that this parameter is unavailable.

Echo Return Loss
The residual echo return loss (RERL), in decibels. may be mea-
sured directly by the VoIP end system’s echo canceller or may be
estimated by adding the echo return loss (ERL) and echo return loss
enhancement (ERLE) values reported by the echo canceller.

RERL(dB) = ERL (dB) + ERLE (dB)

In the case of a VoIP gateway, the source of echo is typically line
echo that occurs at 2–4 wire conversion points in the network. This
can be in the 8–12 dB range. A line echo canceler can provide an
ERLE of 30 dB or more and hence reduce this to 40–50 dB. A typi-
cal handset would result in 40–50 dB of echo loss due to acoustic
feedback.
Gmin
The gap threshold, the value used for this report to determine if a
gap exists. The recommended value of 16 corresponds to a burst
period having a minimum density of 6.25% of lost or discarded
packets, which may cause noticeable degradation in call quality.
During gap periods, if packet loss or discard occurs, each lost or dis-
carded packet would be preceded by and followed by a sequence of
at least 16 received non-discarded packets.
Lost or discarded packets that occur within Gmin packets of a report
being generated may be reclassified as part of a burst or gap in later
reports.
R Factor
A voice quality metric describing the segment of the call that is car-
ried over this RTP session. Valid range: 0 to 100, with a value of 94
corresponding to toll quality voice and values of 50 or less regarded
as unusable. This metric is defined as including the effects of delay,
consistent with ITU-T G.107 [6] and ETSI TS 101 329-5 [3].
External R Factor
A voice quality metric describing the segment of the call that is car-
ried over a network segment external to the RTP segment. The valid
range and interpretation are the same as defined for the RTP R fac-
tor described above. This metric includes the effects of delay, con-
sistent with ITU-T G.107 and ETSI TS 101 329-5, and relates to the
outward voice path from the VoIP termination for which this metrics
block applies.
MOS-LQ
The estimated Mean Opinion Score for Listening Quality (MOS-
LQ). Valid range: 10 to 50, corresponding to MOS × 10. For exam-
ple, a value of 35 corresponds to an estimated MOS score of 3.5.
MOS-LQ does not include the effects of delay and can be compared
to MOS scores obtained from listening quality (ACR) tests.

108 Chapter 6
MOS-CQ
The estimated Mean Opinion Score for Conversational Quality
(MOS-CQ). Valid range: 10 to 50, corresponding to MOS × 10, as
for MOS-LQ.
Pkt Loss Concealment
The Packet Loss Concealment (PLC) method; Describes how the
eMTA is concealing lost packets. The value is one of the following:
Standard A simple replay or interpolation algorithm is being
used to fill-in the missing packet; this approach typi-
cally conceals isolated lost packets at low packet
loss rates.
Enhanced An enhanced interpolation algorithm is being used;
algorithms of this type can conceal high packet loss
rates effectively.
Disabled Silence is being inserted in place of lost packets.
Unspecified No information is available concerning the use of
PLC; however, for some codecs this may be inferred.
Jitter Buf Adaptive

Describes the jitter buffer adaptation; one of the following:
Adaptive The jitter buffer size is being dynamically adjusted
to deal with varying levels of jitter. See the jitter
buffer size parameters below for details.
Non-adaptive The jitter buffer size is maintained at a fixed level.
See the jitter buffer size parameters below for
details.
Jitter Buf Rate

The adjustment rate (J) in adaptive mode, referred to as ‘‘JB rate’’ in
RFC 3611. Valid range: 0 to 15. This parameter is defined in terms
of the approximate time taken to fully adjust to a step change in
peak to peak jitter from 30 ms to 100 ms such that:
adjustment time = 2 × J × frame size (ms)
A value of 0 indicates that the adjustment time is unknown.
JB Nominal Delay
The current nominal jitter buffer delay, in milliseconds, which cor-
responds to the nominal jitter buffer delay for packets that arrive
exactly on time.
JB Max Delay (JB max)
The current maximum jitter buffer delay in milliseconds, which cor-
responds to the earliest arriving packet that would not be discarded.
In adaptive jitter buffer implementations, this value may dynami-
cally vary up to JB abs max (see below).

JB Abs. Max Delay (JB abs max)

The absolute maximum delay in milliseconds, that the adaptive jitter
buffer can reach under worst case conditions. If this value exceeds
65535 milliseconds, the report shows a value of 65535. This param-
eter MUST be provided for adaptive jitter buffer implementations
and its value MUST be set to JB max for fixed jitter buffer imple-
mentations.
Tx Packets
The number of RTP packets transmitted during this call.
Tx Octets
The number of octets transmitted during this call.
Rx Packets
The number of RTP packets received during this call.
Rx Octets
The number of octets received during this call.
Packet Loss
The percentage of RTP packets lost during this call.
Jitter
The estimated statistical variance of the RTP data packet interarrival
time, in milliseconds.
Originator
Indicates whether the MTA originated the call: 1 if the MTA origi-
nated the call; 0 otherwise.
CallP Signalling Touchstone eMTAs keep a log of CallP signalling messages (NCS and SIP)
Message Trace sent or received by the MTA. The number of signalling messages stored
Logs depends on the number of lines supported by the eMTA:
Number Max. Number Buffer
of Lines of Messages Size
1 250 25K
*
2 250 25K
4 1500 150K
8 1500 150K
12 1500 150K
*
Includes 4-line Telephony Ports
Note: Depending on the size of the messages stored, the buffer may contain a
smaller number of messages than the maximum shown above. SIP loads
generate larger messages, reducing the number of messages actually stored.
The eMTA uses a circular buffer scheme to store messages. When a new
message would exceed the maximum buffer size, the eMTA deletes the oldest
messages as needed.

110 Chapter 6
You can display message trace logs, enable or disable logging, or clear the
logs, either through the CLI or the web-based troubleshooting interface. See
the Touchstone Telephony Troubleshooting Guide for details. You can also
enable or disable logging using the arrisMtaDevEnableMGCPLog object.
Logging is enabled by default.
DHCP Message Touchstone firmware provides two 5K byte buffers, one for the MTA and one
Logging for the CM, to log transmitted or received DHCP messages. Each buffer
stores up to 50 of the last DHCP messages exchanged.
Note: The eMTA captures the original DHCP Discover-Offer exchange, and
all subsequent Renew exchanges. The original Offer can be overwritten in
time, but the Offer data is always available through the DHCPAck CLI com-
mand.
The eMTA uses a circular buffer scheme to store messages. When a new
message would exceed the maximum buffer size, the eMTA deletes the oldest
messages as needed.
You can display DHCP logs, enable or disable logging, or clear the logs,
either through the CLI or the web-based troubleshooting interface. See the
Touchstone Telephony Troubleshooting Guide for details. You can also
enable or disable logging using the arrisMtaDevEnableDHCPLog object.
Logging is enabled by default.
Power Outage Recovery and Timing
Telephony Modems with battery backup support automatic switching to DC

powering upon loss of the AC power supply. There is no interruption to the
modem operation as a result of the switch to battery power. Note that there
are certain changes to modem functions while operating on battery power.
See ‘‘Power Failure Operation’’ on page 112 for more details.
Telephony Modems without battery backup, including units deployed with-
out batteries, and battery-backed units which experience loss of AC power
durations which exceed installed battery capacity, cease to operate upon loss
of AC power. Recovery timing from power loss events depends largely on
the recovery capability of network components. However, there is a small
eMTA contribution to the amount of time required to fully recover. For the
ARRIS Touchstone Telephony Modem, this time is approximately 25 to 30
seconds. The following figure shows a representation of this recovery tim-
ing.

Battery Management
Touchstone firmware provides a sophisticated management and monitoring

scheme to maximize battery hold times and extend the useful life of backup
batteries.
Initial Battery When the Telephony Modem is powered up, whether for the first time or
Charging after replacing a battery, it begins a battery charging and testing sequence.
See the Installation Guide for your Telephony Modem for details about the
charging and testing sequence.
Boot from Battery Model 6 and newer Telephony Modems support a Boot from Battery feature,
(Model 6 and new- allowing a Telephony Modem to begin service without AC power.
er) To start a Telephony Modem from a battery, follow these steps:
1 If a battery is installed in the Telephony Modem, remove it.
2 Install the battery into the Telephony Modem.
3 Press the Reset button on the back of the Telephony Modem, using a
pointed, non-metallic object.
Battery Telemetry Touchstone firmware provides battery telemetry through the following man-
agement interfaces:
• LED display
• Web-based interface
• CLI
• SNMP

112 Chapter 6
• Logs and alarms

• Telemetry block
The Telemetry block provides an interface between the signals from an AC
power supply with battery backup and the Telephony Modem network man-
agement agent. The following diagram shows the TM508A/TM512A
Telemetry block and the contacts.
Telemetry
1 2 3 4 Rtn
The following table defines the function of each contact in the Telemetry
block. When the Telephony Modem detects a short between RTN and
another contact, it generates the alarm shown.
Contact Alarm Generated
1 AC Fail
2 Replace Battery
3 Battery Missing
4 Battery Low
RTN (telemetry return line) not applicable
Power Failure When a Telephony Modem with battery backup capabilities loses AC power,
Operation it immediately takes the following actions:
1 Shuts off LEDs to conserve battery power.
2 Disables the ability to download new firmware until the AC power is
restored. This prevents corrupting the Telephony Modem’s firmware
load in case the battery fails before the Telephony Modem could com-
plete the download.
In addition, the Telephony Modem by default shuts down the data services
running over the Ethernet and (on Model 5 and Model 6 Telephony Modems)
USB ports after 15 minutes of power loss. You can change the amount of
time before the Telephony Modem disables data services, or disable data
shutdown altogether. See the Touchstone Telephony Provisioning Guide for
details.

LED Changes LED Operation Changes During Battery Charging
As of TS4.4, the LEDs only flash when AC power is not present and the bat-
tery is low, or else when the battery needs to be replaced. The LED does not
flash during normal charging.
For D11PLUS loads, TS5.3 changes the Power and Battery LED sequences
to provide a ‘‘low battery’’ indication. See the Touchstone Telephony Trou-
bleshooting Guide for details.
Installer Visual Indication of Foreign Loop Voltage
Telephony Modem LEDs flash any time the line card transitions to the Line
Card Over-current Protection State. This indicates foreign voltage is present
on the loop. This condition occurs most often at installation time.
Battery Mismatch Indication
When an unsupported battery is inserted in a Telephony Modem (for exam-

ple, an 8.8Ah battery inserted in a TM502 or WTM552), it repeats the fol-
lowing sequence:
• Battery LED on, all others off
• Battery LED off, all others on
The MTA also sets a ‘‘Battery Mismatch’’ alarm. To clear this issue, replace
the battery with one of the proper type.
Battery Status TS4.5 MSUP2 introduces enhanced battery status monitoring through SNMP.
Monitoring New MIBs provide an estimate of remaining battery charge as a percentage
of full charge, and in minutes remaining to depletion.
Two- and four-line, Model 5 and Model 6 Telephony Modems have battery
charger hardware that reports an accurate estimate of battery capacity within
5 minutes of initialization. The TM402 battery charger provides only limited
capacity information, so Touchstone firmware provides a conservative esti-
mate of remaining charge.
The ‘‘Power Supply Telemetry’’ alarms and logs provide a report of any sta-
tus changes to the power system, including the battery and the charger.
See the Touchstone Telephony Management Guide for details.

114 Chapter 6
SNMP Access Policy and Community Strings
An SNMP access policy provides tighter security for Touchstone eMTAs.

SNMP access to both CM MIBs and MTA MIBs are affected.
In addition, for SNMPv1 and v2, the PacketCable-defined split of CM and
eMTA MIBs requires provisioning separate SNMP community strings in
both the MTA and the CM configuration files.
The primary impact of this change is that MTA Co-existence must be added
to the MTA configuration file only, and that VACM table group names need
to be unique within the MTA or CM configuration files.
System Descriptor MIB Object
Touchstone Telephony Modems support the sysDescr MIB object. This

object provides firmware version and product description information in the
format specified in section 4.2.1 of the DOCSIS Operations Support System
Interface Specification, CM-SP-OSSIv2.0-I10-070803 The specification
requires the sysDescr object to be in the following format:
any text <<HW_REV: hardware version information;
VENDOR: vendor name; BOOTR: BootROM version;
SW_REV: firmware version; MODEL: hardware model information>> any text
Since the content is in a consistent format, the object can be automatically

parsed and used for various functions such as determining when firmware
upgrades are required. The fields in the sysDescr.0 object are:

Field Meaning Description

HW_REV Hardware Revision The hardware revision of the
Telephony Modem. ARRIS
updates this field as needed to
reflect significant hardware
changes or improvements to the
product.
VENDOR Vendor Name The vendor name; in this case,
‘‘Arris Interactive, L.L.C.’’
BOOTR Boot ROM The BootROM image version that
is embedded in the product, and
used to load the application
firmware image.
SW_REV Firmware Revision The firmware version of the appli-
cation firmware image currently
loaded on the Telephony Modem.
Note: In addition to the System
Descriptor MIB object (sys-
Descr.0), the SW_REV informa-
tion is also available in the docs-
DevSwCurrentVers MIB object.
MODEL Model Number The hardware model number of
the Telephony Modem.
Example The following is an example of the sysDescr.0 contents for the TS6.1
firmware release.
ARRIS DOCSIS 2.0 / PacketCable 1.0 Touchstone Telephony Modem
<<HW_REV: 04; VENDOR: Arris Interactive, L.L.C.; BOOTR: 5.50;
SW_REV: 5.3.11T.ML.D11PLUS; MODEL: TM512A>>
Troubleshooting Interfaces
Touchstone firmware provides status information through a web-based inter-

face, and complete control over the eMTA through a CLI interface. The CLI
interface can be accessed through Telnet (all versions) and through SSH
(SSHv2, TS4.5 MSUP2 and newer versions). Several MIBs control access to
each interface.

116 Chapter 6
For more information, see the Touchstone Telephony Troubleshooting Guide.
Loop Diagnostics
TS5.0 and later versions of Touchstone firmware supports remote execution

of in-house wiring tests. You can run loop diagnostics tests using SNMP, the
CLI, or the web-based interface.
Loop diagnostics include the following tests:
Hazardous Potential Test
Tests for the presence of a foreign AC or DC voltage from tip to
ground or ring to ground. Failure conditions are:
• tip-ground or ring-ground AC voltage is greater than 50 VRMS
• tip-ground or ring-ground DC voltage is greater than 135 V

Foreign Electromotive Test
Tests for the presence of an AC or DC voltage from tip to ground or
ring to ground. Failure conditions are:
• tip-ground or ring-ground AC voltage is greater than 10 VRMS
• tip-ground or ring-ground DC voltage is greater than 10 V

(Model 4 Telephony Modems) or 6 V (Model 5 Telephony
Modems)
Resistive Faults Test
Tests the tip to ring, tip to ground, and ring to ground DC resistance.
Failure condition: tip-ring, tip-ground or ring-ground DC resistance
is less than 150 kΩ. This test discriminates between a resistive fault
in the loop and a receiver off-hook condition from properly working
terminal equipment.
Receiver Off Hook Test
Failure condition: detection of a non-linear tip-ring DC resistance
Ringers Test
Measures the terminal equipment’s AC ringer impedance.
Failure condition: the measured equivalent ringer count across tip-
ring is less than 0.175 REN (no phones connected or broken wire)
or greater than 5 REN (too many phones connected).
Note: Due to offsets in the TM402 linecard circuitry, the Ringers
test may return small values even when no load (phone) is attached
to the line.

Limitations
CAUTION
Service affecting
Performing loop diagnostics requires the line under test to be first taken out
of service. Perform loop diagnostics only during installation or a scheduled
maintenance window, unless the subscriber is unable to use the line.
TS6.1 supports Loop Diagnostics on:

• TM402, TM502, TM504, WTM552 Touchstone Telephony Modems
• TM508, TM512, and TM608 multi-line Telephony Modems
• TM602, TM604, and WTM652 Touchstone Telephony Modems
• TP402 and TP404 Touchstone Telephony Ports
Loop Diagnostics and Line Card Diagnostics always run together.
For More Informa- For details about executing loop diagnostics, and how to obtain and interpret
tion test results, see the Touchstone Telephony Troubleshooting Guide.

118 Chapter 6

7 Index
arrisCmDevSwServerAddress, MIB 30, 90, 93–94

arrisCmDevSwServerAddressType, MIB 30, 90, 93–94
arrisCmDevSwTable, MIB 89–90, 92
arrisCmDevTftpBlkSize, MIB 23–24
3-way calling state behavior 78 arrisCmDevTODTimeOffset, MIB 16, 24
arrisCmDevTurboDoxEnable, MIB 42
arrisMtaDevAutomaticCallResourceRecovery, MIB 36, 48
A arrisMtaDevCallStatsEntry, MIB 100
AC power loss 112 arrisMtaDevDefaultReasonNoCIDName, MIB 20, 24
access policy, SNMP 114 arrisMtaDevDhcpKerberosRealmFqdn, MIB 103
adjusting CW-CID tones 86 arrisMtaDevDhcpLeaseTimeRemaining, MIB 103
advanced hook flash feature, SIP 77 arrisMtaDevDhcpMtaConfigFile, MIB 102
affecting SDP, feature switch 59 arrisMtaDevDhcpMtaGatewayIpAddr, MIB 102
arrisCmDevDhcpCmConfigFile, MIB 101 arrisMtaDevDhcpMtaIpAddr, MIB 102
arrisCmDevDhcpCmGatewayIpAddr, MIB 101 arrisMtaDevDhcpMtaIpFQDN, MIB 102
arrisCmDevDhcpCmGatewayIpAddrV6, MIB 30 arrisMtaDevDhcpMtaSubNetMask, MIB 102
arrisCmDevDhcpCmIpAddr, MIB 101 arrisMtaDevDhcpOfferedLeaseTime, MIB 102–103
arrisCmDevDhcpCmIpAddrV6, MIB 30 arrisMtaDevDhcpPktcOptionId, MIB 103
arrisCmDevDhcpCmSubNetMask, MIB 101 arrisMtaDevDhcpPrimaryDhcpSvrIpAddr, MIB 103
arrisCmDevDhcpCmSubNetMaskV6, MIB 30 arrisMtaDevDhcpPrimaryDNSSvrIpAddr, MIB 103
arrisCmDevDhcpCmTimeOffset, MIB 102 arrisMtaDevDhcpProvTimer, MIB 103
arrisCmDevDhcpIpMode, MIB 30 arrisMtaDevDhcpRequestTgt, MIB 103
arrisCmDevDhcpLeaseTimeRemaining, MIB 102 arrisMtaDevDhcpSecondaryDhcpSvrIpAddr, MIB 103
arrisCmDevDhcpPrimaryDhcpServerIpAddr, MIB 102 arrisMtaDevDhcpSecondaryDNSSvrIpAddr, MIB 103
arrisCmDevDhcpPrimaryDhcpServerIpAddrV6, MIB 30 arrisMtaDevDhcpSecTicketInvalid, MIB 103
arrisCmDevDhcpPrimaryTeleDhcpSvr, MIB 102 arrisMtaDevDhcpState, MIB 103
arrisCmDevDhcpSecondaryTeleDhcpSvr, MIB 102 arrisMtaDevDhcpSvcProviderSnmpEntity, MIB 103
arrisCmDevDhcpState, MIB 102 arrisMtaDevDhcpTimeUntilRebind, MIB 103
arrisCmDevDhcpTftpSvrIpAddr, MIB 102 arrisMtaDevDhcpTimeUntilRenew, MIB 103
arrisCmDevDhcpTimeSvrIpAddr, MIB 102 arrisMtaDevDTMFEndEventForceAscending, MIB 13
arrisCmDevDhcpTimeSvrIpAddrV6, MIB 30 arrisMtaDevEchoCancellerTailLength, MIB 57
arrisCmDevDhcpTimeUntilRebind, MIB 102 arrisMtaDevEnableCallSigLastMsgRpt, MIB 56
arrisCmDevDhcpTimeUntilRenew, MIB 102 arrisMtaDevEnableCallStatsSyslogRpt, MIB 56, 101
arrisCmDevDSTPolicy, MIB 16, 24 arrisMtaDevEnableDHCPLog, MIB 110
arrisCmDevDualModeDiscoveredMarket, MIB 22, 25 arrisMtaDevEnableMGCPLog, MIB 110
arrisCmDevLastHwResetReason, MIB 36–37 arrisMtaDevEndPntFaxOnlyLineTimeout, MIB 19, 24
arrisCmDevModemFeatureSwitch2, MIB 19, 22, 24 arrisMtaDevEndPntRingingWaveform, MIB 73
arrisCmDevResetReasonLogDisable, MIB 37 arrisMtaDevGainControlCAS, MIB 87
arrisCmDevResetReasonLogTable, MIB 36–37 arrisMtaDevGainControlFSK, MIB 87
arrisCmDevRouterLanEnable, MIB 32 arrisMtaDevGainControlRxVoice, MIB 38
arrisCmDevRouterLanIpAddr, MIB 32 arrisMtaDevGainControlTxVoice, MIB 38
arrisCmDevRouterLanSubNetMask, MIB 33 arrisMtaDevLastCallEndTime, MIB 37
arrisCmDevSwAdminStatus, MIB 89, 91, 94 arrisMtaDevLastCallStartTime, MIB 37
ArrisCmDevSwCustomerLoadId, MIB 93 arrisMtaDevLevelControlOffHookCAS, MIB 37, 87
ArrisCmDevSwFilename, MIB 90, 93 arrisMtaDevLevelControlOffHookEnable, MIB 37, 87
ArrisCmDevSwHwModel, MIB 93 arrisMtaDevLevelControlOffHookFSK, MIB 37, 87
arrisCmDevSwHwModel, MIB 90, 94 arrisMtaDevLineCard, MIB 104
ArrisCmDevSwHwRev, MIB 93 arrisMtaDevLoopVoltageMaintTimeout, MIB 68–69
arrisCmDevSwHwRev, MIB 90 arrisMtaDevLoopVoltagePolicy, MIB 67
arrisCmDevSwServareAddress, MIB 93 arrisMtaDevLoopVoltageResetTimeout, MIB 67
arrisCmDevSwServareAddressType, MIB 93 arrisMtaDevMonitoring, MIB 36
arrisCmDevSwServer, MIB 93–94 arrisMtaDevNsadSwDnldStatus, MIB 38

120 Chapter 7
arrisMtaDevOffHookFskDelay, MIB 20, 24 arrisWrmDevWlanApSecuConfigWepK_type, MIB 27

arrisMtaDevPacketcableProvisioningFlow, MIB 31 arrisWrmDevWlanApSecuConfigWpa2Obsecu, MIB 28
arrisMtaDevPersistentLineStatus, MIB 13, 15 arrisWrmDevWlanApSecuConfigWpa2phrase, MIB 28
arrisMtaDevProvMethodIndicator, MIB 31, 88 arrisWrmDevWlanApSecuConfigWpaEncry, MIB 28
arrisMtaDevProvState, MIB 88, 101 arrisWrmDevWlanApSecuConfigWpaObsecu, MIB 28
arrisMtaDevPwrSupplyDataShutdownTime, MIB 53 arrisWrmDevWlanApSecuConfigWpaphrase, MIB 28
arrisMtaDevPwrSupplyHighestTemperature, MIB 33 arrisWrmDevWlanQoSConfigEnable, MIB 14, 17, 28
arrisMtaDevPwrSupplyHighestTemperatureClear, MIB 33 arrisWrmDevWlanQoSConfigHomeBandwidth, MIB 14, 17, 28
arrisMtaDevPwrSupplyHighestTemperatureTime, MIB 33 arrisWrmDevWlanQoSConfigPrivateBandwidth, MIB 14, 17, 28
arrisMtaDevPwrSupplyOverTempAlarmControl, MIB 23, 33 arrisWrmDevWlanQoSConfigTotalBandwidth, MIB 14, 17, 28
arrisMtaDevRestoreNvmFactoryDefault, MIB 23–24 automatic resource recovery 35–36
arrisMtaDevRtpPktsLostTotal, MIB 37
arrisMtaDevRTPTxQueueSize, MIB 85
arrisMtaDevSpecialConfigurationOverrideEnable, MIB 88
B
arrisMtaDevSuperG3FaxRelay, MIB 24, 67 bandwidth considerations, G.729 53
arrisMtaDevSwDnldNoSvcImpact, MIB 37–38, 90 battery
arrisMtaDevT38Timeout, MIB 25, 67 boot from 111
arrisMtaDevTrace, MIB 100 telemetry 111
arrisMtaDevVbdOverwriteLineBitmap, MIB 86 bearer path service flow 83
arrisMtaDevVbdOverwriteMaxJitterBuffer, MIB 86 behavior
arrisMtaDevVbdOverwriteMinJitterBuffer, MIB 86 3-way calling state 78
arrisMtaDevVbdOverwriteNomJitterBuffer, MIB 86 call waiting state 77
arrisMtaDevVPJitterBufferMode, MIB 86 connected alerting state 77
arrisMtaDevVPMaxJitterBuffer, MIB 86 best effort service flow 83
arrisMtaDevVPNomJitterBuffer, MIB 86 boot from battery 111
arrisMtaDevVqmCallNumberIdentifier, MIB 23–24 BootROM image version 115
arrisMtaDevVqmCallNumberIdentifierLastCall, MIB 23–24
arrisMtaDevVqmHistorySize, MIB 36
arrisMtaDevVqmMetricTable, MIB 38
C
arrisMtaDevVqmThresholds, MIB 104 call waiting state behavior 77
arrisWrmDevHpg, MIB 30 CallP
arrisWrmDevLanDhcp, MIB 26 feature switch, disabling the capability descriptor 59
arrisWrmDevLanDomain, MIB 26 message trace logs 109
arrisWrmDevLanIpAddr, MIB 25–26 capability descriptor, CallP feature switch, disabling 59
arrisWrmDevLanIpMask, MIB 25 card status, line 104
arrisWrmDevLanIpPoolEnd, MIB 25 CAS gain level 86
arrisWrmDevLanIpPoolStart, MIB 25 certification
arrisWrmDevLanLease, MIB 26 Wifi 42
arrisWrmDevNATEnable, MIB 25, 29 WMM PowerSave 42
arrisWrmDevProvDLTime, MIB 30 CMS
arrisWrmDevProvFile, MIB 30 redirection 48
arrisWrmDevProvFileName, MIB 30 support, multiple 47
arrisWrmDevProvStatus, MIB 29 CODEC
arrisWrmDevPwd, MIB 29 G.729 50
arrisWrmDevRip2AdvertisementInt, MIB 29 support 9
arrisWrmDevRip2KeyId, MIB 29 G.729 50
arrisWrmDevRip2Table, MIB 29 CODECs supported 46, 48
arrisWrmDevRipReceiveStatus, MIB 29 community strings, SNMP 114
arrisWrmDevRipTransmitStatus, MIB 29 connected alerting state behavior 77
arrisWrmDevSaveSettings, MIB 25 connection statistics
arrisWrmDevWlanAp, MIB 26 end of call 55
arrisWrmDevWlanApConfigChannel, MIB 14, 17, 26 monitoring, end of call 100
arrisWrmDevWlanApConfigIndex, MIB 26 considerations, SDP parameter list 66
arrisWrmDevWlanApConfigLanAccess, MIB 14, 18, 29 CW-CID tones, adjusting 86
arrisWrmDevWlanApConfigMode, MIB 26
arrisWrmDevWlanApConfigProtec, MIB 27
arrisWrmDevWlanApConfigQos, MIB 27
D
arrisWrmDevWlanApConfigSsid, MIB 26 D11PLUS-specific, default resource recovery time 36
arrisWrmDevWlanApConfigSSidBroad, MIB 27 default resource recovery time, D11PLUS-specific 36
arrisWrmDevWlanApConfigTable, MIB 26–27 descriptor, CallP feature switch, disabling the capability 59
arrisWrmDevWlanApDhcpc, MIB 26 diagnostics, loop 116
arrisWrmDevWlanApIsolationExtra, MIB 14, 18, 28 disabling the capability descriptor, CallP feature switch 59
arrisWrmDevWlanApIsolationInter, MIB 14, 18, 28 docsDevResetNow, MIB 91
arrisWrmDevWlanApPowerLevel, MIB 14, 17, 28 docsDevSoftware, MIB 89
arrisWrmDevWlanApSecuConfigEnable, MIB 27 docsDevSwAdminStatus, MIB 89, 91
arrisWrmDevWlanApSecuConfigIndex, MIB 27 docsDevSwCurrentVers, MIB 115
arrisWrmDevWlanApSecuConfigTable, MIB 26–28 DTMF
arrisWrmDevWlanApSecuConfigWep, MIB 27 with, RFC2833 65
arrisWrmDevWlanApSecuConfigWepK_gen, MIB 27 relay 8
arrisWrmDevWlanApSecuConfigWepK_index, MIB 27 transmission, inband 70
arrisWrmDevWlanApSecuConfigWepK_man, MIB 27 dual-mode 22, 96
with enhanced firmware loading 95

Index 121
E interface
management 99
earlier NCS loads to SIP, firmware upgrade, from 96
status monitoring 99
echo cancellation 57
Echo Quality Index 105
eMTA see NIU J
eMTA support, SIP 76
jitter buffer, provisioning 86
end
statistics 55
statistics, monitoring 100 L
Enhanced Firmware Loading 89
level
enhanced firmware loading, dual-mode, with 95
CAS gain 86
Euro-PacketCable provisioning 71
FSK gain 86
extended signaling, PacketCable 1.5 66
line
over-current protection state 113
F card status 104
list considerations, SDP parameter 66
failure operation, power 112
loading, dual-mode, with enhanced firmware 95
fax relay, T.38 58
loads to SIP, firmware upgrade, from earlier NCS 96
FAX, SuperG3 67
log, reset reason 36
fax support, G.729 52
logs, CallP message trace 109
fax/modem support 57
loop
feature
diagnostics 116
SIP advanced hook flash 77
management option 67
affecting SDP 59
management, plant maintenance timer 69
disabling the capability descriptor, CallP 59
loss, AC power 112
RFC2833, related 63
field, hardware revision 115
firmware M
functionality 8
management
loading, dual-mode, with enhanced 95
interface 99
upgrade, from earlier NCS loads to SIP 96
option, loop voltage 67
upgrade, MIB 92
plant maintenance timer, loop voltage 69
upgrade options 91
media handling, T.38 66
upgrade, process 89
message trace logs, CallP 109
upgrading 89
MGCP 83
version 115
MIB
flash feature, SIP advanced hook 77
arrisCmDevDhcpCmConfigFile 101
from earlier NCS loads to SIP, firmware upgrade 96
arrisCmDevDhcpCmGatewayIpAddr 101
FSK gain level 86
arrisCmDevDhcpCmGatewayIpAddrV6 30
functionality, firmware 8
arrisCmDevDhcpCmIpAddr 101
arrisCmDevDhcpCmIpAddrV6 30
G arrisCmDevDhcpCmSubNetMask 101
arrisCmDevDhcpCmSubNetMaskV6 30
G.729
arrisCmDevDhcpCmTimeOffset 102
bandwidth considerations 53
arrisCmDevDhcpIpMode 30
CODEC negotiation 50
arrisCmDevDhcpLeaseTimeRemaining 102
CODEC support 50
arrisCmDevDhcpPrimaryDhcpServerIpAddr 102
fax support 52
arrisCmDevDhcpPrimaryDhcpServerIpAddrV6 30
modem support 52
arrisCmDevDhcpPrimaryTeleDhcpSvr 102
gain
arrisCmDevDhcpSecondaryTeleDhcpSvr 102
tone generation 71
arrisCmDevDhcpState 102
level, CAS 86
arrisCmDevDhcpTftpSvrIpAddr 102
level, FSK 86
arrisCmDevDhcpTimeSvrIpAddr 102
Rx 35
arrisCmDevDhcpTimeSvrIpAddrV6 30
Tx 35
arrisCmDevDhcpTimeUntilRebind 102
generation, gain compensated tone 71
arrisCmDevDhcpTimeUntilRenew 102
arrisCmDevDSTPolicy 16, 24
H arrisCmDevDualModeDiscoveredMarket 22, 25
arrisCmDevLastHwResetReason 36–37
handling, T.38 media 66
arrisCmDevModemFeatureSwitch2 19, 22, 24
hardware
arrisCmDevResetReasonLogDisable 37
model number 115
arrisCmDevResetReasonLogTable 36–37
field 115
arrisCmDevRouterLanEnable 32
hook flash feature, SIP advanced 77
arrisCmDevRouterLanIpAddr 32
arrisCmDevRouterLanSubNetMask 33
I arrisCmDevSwAdminStatus 89, 91, 94
ArrisCmDevSwCustomerLoadId 93
IETF MIB support 71
ArrisCmDevSwFilename 90, 93
image version, BootROM 115
ArrisCmDevSwHwModel 93
inband DTMF transmission 70
arrisCmDevSwHwModel 90, 94
ArrisCmDevSwHwRev 93

122 Chapter 7
arrisCmDevSwHwRev 90 arrisMtaDevT38Timeout 25, 67

arrisCmDevSwServareAddress 93 arrisMtaDevTrace 100
arrisCmDevSwServareAddressType 93 arrisMtaDevVbdOverwriteLineBitmap 86
arrisCmDevSwServer 93–94 arrisMtaDevVbdOverwriteMaxJitterBuffer 86
arrisCmDevSwServerAddress 30, 90, 93–94 arrisMtaDevVbdOverwriteMinJitterBuffer 86
arrisCmDevSwServerAddressType 30, 90, 93–94 arrisMtaDevVbdOverwriteNomJitterBuffer 86
arrisCmDevSwTable 89–90, 92 arrisMtaDevVPJitterBufferMode 86
arrisCmDevTftpBlkSize 23–24 arrisMtaDevVPMaxJitterBuffer 86
arrisCmDevTODTimeOffset 16, 24 arrisMtaDevVPNomJitterBuffer 86
arrisCmDevTurboDoxEnable 42 arrisMtaDevVqmCallNumberIdentifier 23–24
arrisMtaDevAutomaticCallResourceRecovery 36, 48 arrisMtaDevVqmCallNumberIdentifierLastCall 23–24
arrisMtaDevCallStatsEntry 100 arrisMtaDevVqmHistorySize 36
arrisMtaDevDefaultReasonNoCIDName 20, 24 arrisMtaDevVqmMetricTable 38
arrisMtaDevDhcpKerberosRealmFqdn 103 arrisMtaDevVqmThresholds 104
arrisMtaDevDhcpLeaseTimeRemaining 103 arrisWrmDevHpg 30
arrisMtaDevDhcpMtaConfigFile 102 arrisWrmDevLanDhcp 26
arrisMtaDevDhcpMtaGatewayIpAddr 102 arrisWrmDevLanDomain 26
arrisMtaDevDhcpMtaIpAddr 102 arrisWrmDevLanIpAddr 25–26
arrisMtaDevDhcpMtaIpFQDN 102 arrisWrmDevLanIpMask 25
arrisMtaDevDhcpMtaSubNetMask 102 arrisWrmDevLanIpPoolEnd 25
arrisMtaDevDhcpOfferedLeaseTime 102–103 arrisWrmDevLanIpPoolStart 25
arrisMtaDevDhcpPktcOptionId 103 arrisWrmDevLanLease 26
arrisMtaDevDhcpPrimaryDhcpSvrIpAddr 103 arrisWrmDevNATEnable 25, 29
arrisMtaDevDhcpPrimaryDNSSvrIpAddr 103 arrisWrmDevProvDLTime 30
arrisMtaDevDhcpProvTimer 103 arrisWrmDevProvFile 30
arrisMtaDevDhcpRequestTgt 103 arrisWrmDevProvFileName 30
arrisMtaDevDhcpSecondaryDhcpSvrIpAddr 103 arrisWrmDevProvStatus 29
arrisMtaDevDhcpSecondaryDNSSvrIpAddr 103 arrisWrmDevPwd 29
arrisMtaDevDhcpSecTicketInvalid 103 arrisWrmDevRip2AdvertisementInt 29
arrisMtaDevDhcpState 103 arrisWrmDevRip2KeyId 29
arrisMtaDevDhcpSvcProviderSnmpEntity 103 arrisWrmDevRip2Table 29
arrisMtaDevDhcpTimeUntilRebind 103 arrisWrmDevRipReceiveStatus 29
arrisMtaDevDhcpTimeUntilRenew 103 arrisWrmDevRipTransmitStatus 29
arrisMtaDevDTMFEndEventForceAscending 13 arrisWrmDevSaveSettings 25
arrisMtaDevEchoCancellerTailLength 57 arrisWrmDevWlanAp 26
arrisMtaDevEnableCallSigLastMsgRpt 56 arrisWrmDevWlanApConfigChannel 14, 17, 26
arrisMtaDevEnableCallStatsSyslogRpt 56, 101 arrisWrmDevWlanApConfigIndex 26
arrisMtaDevEnableDHCPLog 110 arrisWrmDevWlanApConfigLanAccess 14, 18, 29
arrisMtaDevEnableMGCPLog 110 arrisWrmDevWlanApConfigMode 26
arrisMtaDevEndPntFaxOnlyLineTimeout 19, 24 arrisWrmDevWlanApConfigProtec 27
arrisMtaDevEndPntRingingWaveform 73 arrisWrmDevWlanApConfigQos 27
arrisMtaDevGainControlCAS 87 arrisWrmDevWlanApConfigSsid 26
arrisMtaDevGainControlFSK 87 arrisWrmDevWlanApConfigSSidBroad 27
arrisMtaDevGainControlRxVoice 38 arrisWrmDevWlanApConfigTable 26–27
arrisMtaDevGainControlTxVoice 38 arrisWrmDevWlanApDhcpc 26
arrisMtaDevLastCallEndTime 37 arrisWrmDevWlanApIsolationExtra 14, 18, 28
arrisMtaDevLastCallStartTime 37 arrisWrmDevWlanApIsolationInter 14, 18, 28
arrisMtaDevLevelControlOffHookCAS 37, 87 arrisWrmDevWlanApPowerLevel 14, 17, 28
arrisMtaDevLevelControlOffHookEnable 37, 87 arrisWrmDevWlanApSecuConfigEnable 27
arrisMtaDevLevelControlOffHookFSK 37, 87 arrisWrmDevWlanApSecuConfigIndex 27
arrisMtaDevLineCard 104 arrisWrmDevWlanApSecuConfigTable 26–28
arrisMtaDevLoopVoltageMaintTimeout 68–69 arrisWrmDevWlanApSecuConfigWep 27
arrisMtaDevLoopVoltagePolicy 67 arrisWrmDevWlanApSecuConfigWepK_gen 27
arrisMtaDevLoopVoltageResetTimeout 67 arrisWrmDevWlanApSecuConfigWepK_index 27
arrisMtaDevMonitoring 36 arrisWrmDevWlanApSecuConfigWepK_man 27
arrisMtaDevNsadSwDnldStatus 38 arrisWrmDevWlanApSecuConfigWepK_type 27
arrisMtaDevOffHookFskDelay 20, 24 arrisWrmDevWlanApSecuConfigWpa2Obsecu 28
arrisMtaDevPacketcableProvisioningFlow 31 arrisWrmDevWlanApSecuConfigWpa2phrase 28
arrisMtaDevPersistentLineStatus 13, 15 arrisWrmDevWlanApSecuConfigWpaEncry 28
arrisMtaDevProvMethodIndicator 31, 88 arrisWrmDevWlanApSecuConfigWpaObsecu 28
arrisMtaDevProvState 88, 101 arrisWrmDevWlanApSecuConfigWpaphrase 28
arrisMtaDevPwrSupplyDataShutdownTime 53 arrisWrmDevWlanQoSConfigEnable 14, 17, 28
arrisMtaDevPwrSupplyHighestTemperature 33 arrisWrmDevWlanQoSConfigHomeBandwidth 14, 17, 28
arrisMtaDevPwrSupplyHighestTemperatureClear 33 arrisWrmDevWlanQoSConfigPrivateBandwidth 14, 17, 28
arrisMtaDevPwrSupplyHighestTemperatureTime 33 arrisWrmDevWlanQoSConfigTotalBandwidth 14, 17, 28
arrisMtaDevPwrSupplyOverTempAlarmControl 23, 33 docsDevResetNow 91
arrisMtaDevRestoreNvmFactoryDefault 23–24 docsDevSoftware 89
arrisMtaDevRtpPktsLostTotal 37 docsDevSwAdminStatus 89, 91
arrisMtaDevRTPTxQueueSize 85 docsDevSwCurrentVers 115
arrisMtaDevSpecialConfigurationOverrideEnable 88 docsQosPktClassTable xiii
arrisMtaDevSuperG3FaxRelay 24, 67 firmware upgrade 92
arrisMtaDevSwDnldNoSvcImpact 37–38, 90 MtaDevControl 100

Index 123
pktcEnNcsEndPntFaxDetection 66 pktcEnNcsEndPntQuarantineState, MIB 66

pktcEnNcsEndPntHookState 66 pktcEnNcsMinimumDtmfPlayout, MIB 66
pktcEnNcsEndPntQuarantineState 66 pktcMtaDevConfigHash, MIB 31
pktcEnNcsMinimumDtmfPlayout 66 pktcNcsEndPntConfigMax1, MIB 74
pktcMtaDevConfigHash 31 pktcNcsEndPntConfigMax1QEnable, MIB 74
pktcNcsEndPntConfigMax1 74 pktcNcsEndPntConfigMax2, MIB 74
pktcNcsEndPntConfigMax1QEnable 74 pktcNcsEndPntConfigMax2QEnable, MIB 74
pktcNcsEndPntConfigMax2 74 pktcNcsEndPntConfigRtoInit, MIB 74
pktcNcsEndPntConfigMax2QEnable 74 pktcNcsEndPntConfigRtoMax, MIB 74
pktcNcsEndPntConfigRtoInit 74 pktcNcsEndPntConfigThist, MIB 73
pktcNcsEndPntConfigRtoMax 74 pktcNcsEndPntConfigTSMax, MIB 74
pktcNcsEndPntConfigThist 73 plant maintenance timer, loop voltage management 69
pktcNcsEndPntConfigTSMax 74 PMT 69
ppCfgMTACountryTemplate 71 post-provisioning 97
ppCfgMtaCountryTemplate 21, 38 power
rip2IfConfAddress 32 failure operation 112
rip2IfConfAuthKey 32 loss, AC 112
rip2IfConfAuthType 29, 32 recovery and timing 110
rip2IfConfDefaultMetric 32 ppCfgMTACountryTemplate, MIB 71
rip2IfConfDomain 32 ppCfgMtaCountryTemplate, MIB 21, 38
rip2IfConfReceive 29, 32 process, firmware upgrade 89
rip2IfConfSend 29, 32 protection state, line card over-current 113
rip2IfConfSrcAddress 32 provisioning
rip2IfConfStatus 32 Euro-PacketCable 71
rip2IfConfTable 29 jitter buffer 86
sipCfgPenaltyBoxTimeout 24 proxy penalty box, SIP 79
sipCfgPortCallByeDelay 12–13
sipCfgPortFaxOnlyTimeout 19, 24
sipCfgProvisionedCodecArray 8
R
sipCfgRegExpires 20, 24 ranges, OUI 85
sipCfgSessionExpires 20, 24 rates, packetization 47
sipCfgSipFeatureSwitch 14, 24, 38, 79 reason log, reset 36
support, IETF 71 recovery and timing, power outage 110
sysDescr 114 redirection, CMS 48
upsAutoRestart 31 related feature switch, RFC2833 63
upsRebootWithDuration 31 relay, DTMF 8
upsShutdownAfterDelay 31 reporting, per-call Syslog 101
upsShutdownType 31 reset reason log 36
upsStartupAfterDelay 31 resource
model number, hardware 115 automatic 35–36
modem support, G.729 52 D11PLUS-specific, default 36
monitoring, end of call connection statistics 100 retransmission algorithm, NCS 73
MtaDevControl, MIB 100 RFC2833 8
multiple CMS support 47 DTMF interactions with 65
related feature switch 63
ring support, sinusoidal 73
N rip2IfConfAddress, MIB 32
NCS rip2IfConfAuthKey, MIB 32
loads to SIP, firmware upgrade, from earlier 96 rip2IfConfAuthType, MIB 29, 32
retransmission algorithm 73 rip2IfConfDefaultMetric, MIB 32
rip2IfConfDomain, MIB 32
rip2IfConfReceive, MIB 29, 32
O rip2IfConfSend, MIB 29, 32
operation, power failure 112 rip2IfConfSrcAddress, MIB 32
option, loop voltage management 67 rip2IfConfStatus, MIB 32
options, firmware upgrade 91 rip2IfConfTable, MIB 29
OUI ranges 85 Rx gain 35
over-current protection state, line card 113
S
P SDP
PacketACE 91, 97 feature switch affecting 59
PacketCable 1.5 extended signaling 66 parameter list considerations 66
packetization rates 47 service
parameter list considerations, SDP 66 bearer path 83
penalty box, SIP proxy 79 best effort 83
per-call Syslog upstream 83
reporting 101 signaling, PacketCable 1.5 extended 66
statistics 101 sinusoidal ring support 73
pktcEnNcsEndPntFaxDetection, MIB 66 SIP
pktcEnNcsEndPntHookState, MIB 66 advanced hook flash feature 77
eMTA support 76

124 Chapter 7
firmware upgrade, from earlier NCS loads to 96 V

proxy penalty box 79
V.8 67
sipCfgPenaltyBoxTimeout, MIB 24
version
sipCfgPortCallByeDelay, MIB 12–13
BootROM image 115
sipCfgPortFaxOnlyTimeout, MIB 19, 24
firmware 115
sipCfgProvisionedCodecArray, MIB 8
Voice Band Data 86
sipCfgRegExpires, MIB 20, 24
sipCfgSessionExpires, MIB 20, 24
sipCfgSipFeatureSwitch, MIB 14, 24, 38, 79 W
SNMP
Wifi certification 42
access policy 114
with
community strings 114
enhanced firmware loading, dual-mode 95
state behavior
RFC2833, DTMF interactions 65
3-way calling 78
WMM PowerSave certification 42
call waiting 77
connected alerting 77
statistics
end of call connection 55
monitoring, end of call connection 100
per-call Syslog 101
status
line card 104
interface 99
SuperG3 FAX 67
support
CODEC 9
fax/modem 57
IETF MIB 71
multiple CMS 47
sinusoidal ring 73
SIP eMTA 76
supported, CODECs 46, 48
sysDescr, MIB 114
Syslog
reporting, per-call 101
statistics, per-call 101
system descriptor 114
T
T.38
fax relay 58
media handling 66
telemetry, battery 111
timer, loop voltage management, plant maintenance 69
timing, power outage recovery and 110
to SIP, firmware upgrade, from earlier NCS loads 96
tone generation, gain compensated 71
tones, adjusting CW-CID 86
trace logs, CallP message 109
transmission, inband DTMF 70
TurboDOX 42
Tx gain 35
U
upgrade
from earlier NCS loads to SIP, firmware 96
MIB, firmware 92
options, firmware 91
process, firmware 89
upgrading firmware 89
upsAutoRestart, MIB 31
upsRebootWithDuration, MIB 31
upsShutdownAfterDelay, MIB 31
upsShutdownType, MIB 31
upsStartupAfterDelay, MIB 31
upstream service flow 83

Touchstone® Telephony
Feature Guide
© 2004–2009 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. Users must take full responsibility for their
applications of any products specified in this document. The
information in this document is proprietar y to ARRIS.
ARRIS, C3™, C4®, and Touchstone® are trademarks or

registered trademarks of ARRIS Group, Inc. Cadant® is a
registered trademark of ARRIS Group, Inc. All other
trademarks and registered trademarks are the property of
their respective holders.

TS6.1 Feature Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TS6.1 Feature Guide

Uploaded by

Copyright:

Available Formats

Touchstone® Telephony

Printed in the USA

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

October 2006 Release 5.0 Standard 1.0 version of this document.

August 2006 Release 4.6 Standard 1.0 version of this document.

March 2005 Release 4.4 Standard 1.0 version of this document.

Feature Guide Release 6.1 Standard 1.3 June 2009

February 2005 Release 4.3 Standard 1.0 version of this document.

August 2004 Release 4.2 Standard 1.0 version of this document.

April 2004 Release 4.1 Standard 1.0 version of this document.

September 2003 Release 3.2 Standard 1.0 version of this document.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Feature Guide Release 6.1 Standard 1.3 June 2009

RIPv2 Support .................................................................... 16

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

VQM Enhancements .......................................................... 36

Feature Guide Release 6.1 Standard 1.3 June 2009

Policy 4: MTA In-Ser vice ........................................................... 69

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Ser ver Address Object Interactions .................................... 93

Management and Troubleshooting Features 99

Feature Guide Release 6.1 Standard 1.3 June 2009

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

This document describes standards compliance, telephony features, and data

About the Touchstone Telephony Firmware

Touchstone Telephony TS6.1 firmware provides operating, maintenance, and

Feature Guide Release 6.1 Standard 1.3 June 2009

Subscriber Touchstone Telephony TS6.1 firmware provides:

This document contains the following information:

The following is a list of terms and abbreviations used in this manual.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Call Management Server (CMS)

Feature Guide Release 6.1 Standard 1.3 June 2009

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Feature Guide Release 6.1 Standard 1.3 June 2009

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Feature Guide Release 6.1 Standard 1.3 June 2009

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Feature Guide Release 6.1 Standard 1.3 June 2009

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

This chapter describes Touchstone Telephony hardware and firmware fea-

Feature Guide Release 6.1 Standard 1.3 June 2009

Touchstone Telephony Port

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Feature Guide Release 6.1 Standard 1.3 June 2009

Touchstone Telephony Modems

This section describes the Telephony Modems supported by the current

Supported models include: TM401A, TM401B, TM402A, TM402B,

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Model 5 Model 5 Telephony Modems provide telephony, 10/100BaseT Ethernet and

Supported models include: TM501A, TM501B, TM502A, TM502B,

Feature Guide Release 6.1 Standard 1.3 June 2009

Supported models include: TM508A and TM512A.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Supported models include: TM601A, TM601B, TM602A, TM602B,

Touchstone firmware provides the following core functionality:

Feature Guide Release 6.1 Standard 1.3 June 2009

The TS6.1 firmware provides the following functionality:

• Interoperability with ARRIS and other vendors’ CMTS products.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

• DOCSIS 2.0 auto-detect (patent pending)—ARRIS eMTAs can auto-

Hardware Support TS6.1 provides the following Touchstone hardware support.

Telephony TS6.1 provides the following telephony-related functionality and support:

Provisioning TS6.1 provides a variety of provisioning options and functionality as follows: