TS75 Firmware MSUP5 STD
TS75 Firmware MSUP5 STD
Standard 1.2
August 2012
ii
© 2009–2012 ARRIS
All rights reserved
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.
August 2012 Release 7.5 Standard 1.2 version of this document for TS7.5 MSUP5.
March 2012 Release 7.5 Standard 1.1 version of this document for TS7.5 MSUP4.
January 2012 Release 7.5 Standard 1.0 version of this document for TS7.5.
Overview 1
About This Manual ............................................................................ 1
Audience ..................................................................................... 1
In This Manual ............................................................................ 2
Suppor ted Hardware ......................................................................... 2
Model 7 ....................................................................................... 2
Model 8 ....................................................................................... 3
Subscriber Interface .................................................................... 3
Load Name Extensions ..................................................................... 4
Examples .................................................................................... 5
Firmware Functionality ...................................................................... 6
Firmware Download Center ........................................................ 6
Standards Compliance ...................................................................... 7
Standard Functionality ................................................................ 7
Optional Functionality ................................................................. 7
DOCSIS Specifications ............................................................... 7
PacketCable Specifications ......................................................... 8
SIP Specifications ....................................................................... 8
CableLabs IPv6 Specifications ................................................. 10
New Features in TS7.5 MSUP5 ...................................................... 10
New Features in TS7.5 .................................................................... 10
Unified SIP Loads ..................................................................... 10
IPv6 CPE Operations ................................................................ 10
New Hardware Support ............................................................ 11
Terminology ..................................................................................... 12
Provisioning 19
General Provisioning Information .................................................... 20
Ser vice Flow Limitations ........................................................... 20
OUI Ranges .............................................................................. 20
Configuring ToD Offset ............................................................. 20
Setting the DST Policy .............................................................. 21
Clearing the CPE List ............................................................... 21
Operations 205
Batter y Management ..................................................................... 205
Initial Battery Charging ........................................................... 206
Boot from Battery .................................................................... 206
Batter y Telemetr y .................................................................... 206
Power Failure Operation ......................................................... 206
LED Changes .......................................................................... 207
LED Operation Changes During Battery Charging ........... 207
Installer Visual Indication of Foreign Loop Voltage ........... 207
Batter y Mismatch Indication ............................................. 207
Batter y Status Monitoring ....................................................... 207
Highest Charger Temperature Recording ............................... 207
About IPv6 Support ....................................................................... 208
Suppor ted Hardware ............................................................... 208
IPv6 Multicast Support ............................................................ 208
Before Registration ........................................................... 209
During Registration ........................................................... 209
After Registration .............................................................. 209
IPv6 Management ......................................................................... 211
Filtering IPv6 Traffic ................................................................ 211
MLD Snooping .................................................................. 211
Upstream Drop Classifiers ............................................... 211
Coexistence ............................................................................ 212
DHCPv6 MIB Objects ............................................................. 212
SNMP Access ......................................................................... 214
Event Reporting ............................................................................. 215
Collecting Events .................................................................... 215
Event Formats ......................................................................... 215
Administration 359
Administration Objects .................................................................. 360
System Description Objects .................................................... 360
sysDescr Object ............................................................... 360
sysObjectID Object ........................................................... 361
sysORTable Objects ......................................................... 362
Bridging and Routing Objects ................................................. 362
dot1dBridge Objects ......................................................... 362
rip2 Objects ...................................................................... 362
arrisRouterMib Objects ..................................................... 363
End of Call Connection Statistics .................................................. 364
NCS Behavior ......................................................................... 364
SIP Behavior ........................................................................... 365
End-of-Call Statistics MIB Objects .......................................... 365
Clearing Counters ................................................................... 365
Device Level End-of-Call Statistics ......................................... 366
Last Signaling Message Sent ................................................. 367
Line Level Status ..................................................................... 367
Per-Call Syslog Reporting ....................................................... 369
Per Call Syslog Report Example ...................................... 369
Message Trace Example .................................................. 370
Procedure: Managing Voice Quality Monitoring ........................... 371
About Voice Quality Monitoring ............................................... 371
VQM Data ............................................................................... 371
Inter preting Results ................................................................. 377
Maintenance 397
Over view of Maintenance Interfaces ............................................. 397
CLI Access Levels and Defaults ............................................. 398
WebGUI Access Levels and Defaults ..................................... 398
About TACACS+ Support ........................................................ 399
LED Patterns ................................................................................. 399
Batter y Mismatch .................................................................... 400
Wiring Problems ...................................................................... 400
TM702 Normal Operation ....................................................... 400
TM722/TM802/TM804/TM822 Normal Operation ................... 401
TM702/TM722/TM802/TM804/TM822 Startup Sequence ...... 402
eDVA Star tup Sequence ................................................... 402
Cable Modem Startup Sequence ..................................... 402
TG852G Normal Operation ..................................................... 402
TG852G Startup Sequence .................................................... 404
eDVA Star tup Sequence ................................................... 404
Cable Modem Startup Sequence ..................................... 404
TG852G/CT Normal Operation ............................................... 404
TG852G/CT Startup Sequence .............................................. 405
eDVA Star tup Sequence ................................................... 405
Cable Modem Startup Sequence ..................................... 406
SIP Concepts ................................................................................ 407
Dialogs .................................................................................... 407
Transactions ............................................................................ 407
Authorization ........................................................................... 407
Registration ............................................................................. 408
Subscriptions .......................................................................... 408
Implicit Subscriptions ........................................................ 408
Call Legs ................................................................................. 409
Basic Call Flow ................................................................. 409
References 461
Suppor ted Calling Features ........................................................... 461
Countr y Code Templates ............................................................... 464
Nor th American Ring Cadences ............................................. 465
Netherlands/Netherlands09 Ring Cadences .......................... 466
Provisioning European Ring Cadences .................................. 466
Austria Ring Cadences ........................................................... 467
Index 697
Audience This manual assumes that you have a basic understanding of DOCSIS and
PacketCable standards, and a working knowledge of cable data and telephony
networks.
Supported Hardware
Model 7 All Model 7 Telephony Modems and Wideband Cable Modems provide
100/1000BaseT Ethernet data connections. Some models also provide USB
data connectivity for Windows-based computers. In addition, Telephony
Modems provide up to two lines of telephone service and optional battery
backup.
Note: TS7.5 disables USB support for WBM750 Wideband Cable Modems
only.
Examples The following examples show how load names describe the functionality of
the load.
TS070518_111011_NA.MODEL_702.SIP.PC20.img
TS070518_111011_EU.MODEL_702.SIP.PC20.img
TS7.5 North American and European firmware images for TM702
Telephony Modems, using SIP signaling and PacketCable 2.0 SIP
provisioning.
TS070518_111011_NA.MODEL_852.MONO.SIP.PC20.img
TS7.5 North American firmware image for TG852 Telephony Gate-
ways, using SIP signaling and PacketCable 2.0 SIP provisioning.
Firmware Functionality
Firmware Down- ARRIS provides the ability to download firmware updates directly from the
load Center Internet, using the ARRIS Software/Firmware Delivery Tool. Benefits
include an archive of released loads and email notification of updated loads.
To obtain an account, contact ARRIS Technical Support.
Standards Compliance
Standard Func- Touchstone Telephony Modems running version TS7.5 firmware comply
tionality with the following standards:
• DOCSIS 3.0
• PacketCable 2.0
• Euro-DOCSIS 3.0
• Euro-PacketCable 1.0
• PacketCable 1.5 and PacketCable 1.0
Optional TS7.5 supports the following optional functionality specified by DOCSIS and
Functionality PacketCable standards:
• Support for multiple CODECs (see ‘‘CODECs and Packetization Rates
Supported’’ on page 60)
• Support for 10 ms and 20 ms packetization rates
• Support for up to 32 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/n wireless LANs (Data Gateways and Telephony Gateways
only)
DOCSIS Specifica- All DOCSIS specifications are available at the DOCSIS web site 〈http://
tions www.cablemodem.com/specifications/〉.
• DOCSIS 3.0 Radio Frequency Interface Specification, SP-
RFIv2.0-I11-060206
• DOCSIS 3.0 Operations Support System Interface Specification, CM-
SP-OSSIv3.0-I15-100115
• DOCSIS 1.1 Baseline Privacy Plus Interface Specification, SP-
BPI+-I12-050812
• DOCSIS 1.1 Cable Modem to Customer Premise Equipment Interface
Specification, CM-SP-CMCIv3.0-I01-080320
PacketCable Spec- TS7.5 supports PacketCable 2.0 operation. The following list shows Packet-
ifications Cable 2.0 specifications that apply to Touchstone PC20 loads. All PacketCa-
ble specifications are available at the PacketCable web site 〈http://
www.packetcable.com/specifications/〉.
• PacketCable SIP and SDP Stage 3 Specification, PKT-
SP-24.229-I06-100120
• Organization of Subscriber Data Specification, PKT-
SP-23.008-I03-080425
• Access Security for IP-based Services Specification, PKT-
SP-33.203-I05-090528
• Residential SIP Telephony Feature Specification, PKT-SP-RSTF-
I08-110127
• Residential SIP Telephony E-DVA Specification, PKT-SP-RST-E-DVA-
I-8-110127
• RST E-UE Provisioning Specification, PKT-SP-RST-EUE-PROV-
I06-110127
• UE Provisioning Data Model Specification, PKT-SP-UE-DATA-
I02-100527
• E-UE Provisioning Framework Specification, PKT-SP-EUE-PROV-
I06-110127
• Codec and Media Specification, PKT-SP-CODEC-MEDIA-I09-100527
• Business SIP Services (BSS) Feature Specification, PKT-SP-BSSF-
I03-100527
• PacketCable MTA Device Provisioning Specification, PKT-SP-
PROV1.5-I04-090624
• Quality of Service Specification, PKT-SP-QOS-I02-080425
SIP Specifications In addition to the PacketCable specifications listed above, TS7.5 ARRIS SIP
loads comply or partially comply with the following SIP-related RFCs:
• The SIP INFO Method, RFC 2976
• SIP: Session Initiation Protocol, RFC 3261
• Reliability of Provisional Responses in Session Initiation Protocol
(SIP), RFC 3262
TS7.5 firmware provides the following new features and functionality over
TS7.3 and TS7.4:
Unified SIP Loads TS7.5 provides both ARRIS Legacy SIP and PacketCable 2.0 SIP support in
separate load variants. Previous Touchstone firmware versions supported
only one variant.
IPv6 CPE Opera- TS7.5 now supports IPv6 operation for both the CM and subscriber inter-
tions faces, including the wireless interfaces. Dual Stack Lite (DS-Lite) support
allows simultaneous IPv4 and IPv6 operation.
Touchstone Gateway products support IPv6 operation in the eRouter as well.
Terminology
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.
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 or E-UE 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.
DOCSIS
Data Over Cable Service Interface Specification. The interoperabil-
ity standards used for data communications equipment on an HFC
network.
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.
DQoS
Dynamic Quality of Service. The mechanism by which the eDVA
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.
eDVA
Embedded Digital Voice Adapter, the PacketCable 2.0 term for the
portion of an E-UE that contains the network interface, CODECs,
and all signalling and encapsulation functions required for tele-
phony transport, CLASS features signalling, and QoS signalling.
Referred to as an MTA in earlier PacketCable specifications and
Touchstone firmware documentation.
eMTA
See E-UE.
E-UE
Embedded User Equipment, the PacketCable 2.0 term for a cable
modem with an embedded eDVA. Referred to as an eMTA in earlier
PacketCable specifications and Touchstone firmware documenta-
tion.
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.
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.
KDC
Kerberos Key Distribution Center.
Latency
The time required for a signal element (e.g. packet) to pass through
a device or network.
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.
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.’’ However, the term
‘‘MIB object’’ is more precise and is used in this documentation.
MPI
Micro-Processor Interface. An internal Touchstone Telephony
Modem component.
MSO
Multi-System Operator. A cable company that operates multiple
headend locations, usually in several cities.
MTA
See eDVA.
NCS
Network-based Call Signaling. The PacketCable protocol used to
control calls.
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.
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
eDVAs 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.
P-CSCF
Proxy-Call Session Control Function. In PacketCable 2.0 networks,
this is the SIP server that provides connectivity between the eDVA
and the PSTN.
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.
Proxy
See P-CSCF.
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.
RST
Residential SIP Telephony, the specification for PacketCable 2.0
telephony.
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 eDVA. 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.
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.
OUI Ranges The following table shows OUI support for various versions of Touchstone
firmware support.
Firmware Version OUI ranges supported
00:00:CA 00:13:11
00:15:96 00:15:CE
00:15:A2 00:15:CF
00:15:A3 00:15:D0
00:15:A4 00:15:D1
TS7.0 and newer
00:1D:CD 00:1D:D2
00:1D:CE 00:1D:D3
00:1D:CF 00:1D:D4
00:1D:D0 00:1D:D5
00:1D:D1 00:1D:D6
Configuring ToD Time of Day changes, including for Daylight Savings Time shifts, normally
Offset occur during DHCP Renew operations. It may be necessary to manually
change the offset, especially in SIP deployments where the eDVA clock is
used as a source for Calling Line Presentation (CLIP) information.
1 To change the ToD offset, set the arrisCmDoc30SetupTODTimeOff-
set MIB object to the desired offset (in seconds). Valid range:
−43200 (−12 hours) to 46800 (+13 hours).
Setting the DST DST policies may vary due to national legislation or local preferences.
Policy TS7.1 MSUP2 and newer versions of Touchstone firmware provides control
over local DST policy.
1 To change the DST policy, set the arrisCmDoc30SetupDSTPolicy
object to a string with the following format:
start=month/day/weekday/hour;end=month/day/weekday/hour
where. . . is. . .
month the month: 1 for January, to 12 for December.
day The day: −31 to −1 to count backwards from the
end of the month, 1 to 31 to count forward from
the beginning of the month.
weekday The day of the week that DST begins or ends: 1
for Monday, to 7 for Sunday, or 0 to ignore the
weekday and use the exact date. If not zero,
DST begins or ends on the specified weekday
after the date if the date is positive, or before the
date if negative.
hour The hour at which DST begins or ends: 00 to 23.
Example:
start=3/8/7/02;end=11/1/7/02
Implements the U.S. DST policy in effect since March 2007: DST
begins at 2 a.m. on the second Sunday in March and ends at 2 a.m. on
the first Sunday in November.
Clearing the CPE When the Telephony Modem loses link on all LAN interfaces, the modem
List clears its CPE list. This allows subscribers allowed only one CPE device to
swap computers without resetting the Telephony Modem or calling support.
Provisioning Considerations
Upgrading from When re-using a DOCSIS 2.0 configuration file for TS7.0 and newer versions
DOCSIS 2.0 of Touchstone firmware, several settings need to be changed as described
below.
When re-using a DOCSIS 2.0 configuration file for TS7.0 and newer versions
of Touchstone firmware, several CallP Feature Switch settings must be tog-
gled (i.e. change 1 to 0 and vice versa) to provide equivalent functionality:
Bit Description
0x00000001 NCS piggybacked message support
0x00000002 Lockstep quarantine mode
0x00008000 NCS provisional responses support
The following switches were removed or changed in TS7.0 and newer ver-
sions. Set all removed bits to 0 to prevent accidental enabling of new fea-
tures in future releases.
Hardware-Specific Certain hardware models may require special upgrade procedures when
Upgrade Limita- upgrading from earlier versions of Touchstone firmware. TS7.5 disables cer-
tions tain features for specific hardware. These issues are described below.
WBM750/WBM760
TS7.5 does not support USB operation for WBM750 Wideband Cable
Modems. Subscribers using Ethernet connections are not affected.
Note: Due to memory constraints, early Rev 1 versions of the WBM750 can-
not run TS7.5.
The following upgrade considerations apply:
• Upgrading to TS7.5 from TS7.1.95 or WBM3.2.20, or earlier versions
of Touchstone firmware, require an interim upgrade using TS7.1.96.
Model 8 Hardware
DG860
Due to memory constraints, the DG860 Data Gateway stores only one copy
of the gateway firmware. However, the DOCSIS portion of the load is dual-
banked. Therefore, it is possible that a download error could leave the gate-
way with a corrupted image. Forcing the unit to re-download the firmware
should correct this problem.
About IPsec IPsec (Internet Protocol Security) is a collection of Internet standards used to
encrypt and authenticate IP packets, to provide message integrity and privacy.
IPsec provides security at the network layer (all TCP and UDP packets, and
layers above).
IPsec is controlled by setting the pktcMtaDevCmsIpsecCtrl object for each
CMS that the eDVA can communicate with; you can include this object in the
eDVA configuration file. The object is indexed by the CMS FQDN for North
American loads. Set the object to true(1) to enable IPsec between the eDVA
and a particular CMS, and false(2) to disable it.
Note: Touchstone E-UEs use only the IPsec ESP transport mode.
Cable Modem In- TS7.5 supports the Cable Modem Interface Mask (CMIM). The CMIM is a
terface Mask field in the upstream classifiers that can be used to filter out traffic based on
the CM interface receiving the packet. When this field is present in the US
classifier, a packet matches the classifier only if the traditional fields match
and the source interface of the packet is present in the CMIM of the classifier.
The CMIM is an encoded 2- or 4-byte mask where each bit represents the
interface whose ifIndex matches the bit position. The short form of the mask
omits bits 16 through 31. For example, the RF interface has an ifIndex of 2
which corresponds to bit 2 of the CMIM. For this mask, bit position 0 is the
most significant bit of the most significant word. For example, a CMIM clas-
sifier intended to match all of the CPE ports (external interfaces) of a CM has
a CMIM value setting bits 1 and 5-15, so an encoding of either 0x47FF or
0x47FF0000 is valid. See ‘‘Interface Index Scheme’’ on page 26 for a list of
valid ifIndex values.
Voice and Signal- TS7.5 firmware uses a random selection of ports in the range 49152 through
ing Ports 65535 for RTP- and RTCP-based voice communications. The port numbers
cannot be modified or used for other purposes.
By default, the eDVA uses port 2727 on the upstream, and port 2427 on the
downstream, to send and receive signaling information. You can change the
default port number in the eDVA configuration file. You can also change the
transmit port by sending an NCS message from the call server once the
eDVA is operating.
Interface Index Touchstone firmware generally conforms to the eDOCSIS specification, CM-
Scheme SP-eDOCSIS-I13-070803, for ifIndex designations. The following table lists
the specified defaults.
Interface Type
1 Primary CPE interface (Ethernet)
2 CATV MAC interface
3 RF downstream channel
4 RF upstream channel
5–11 Other CPE interfaces (telephony, data)
12 Wireless SSID 0
13 Wireless SSID 1
14 Wireless SSID 2
15 Wireless SSID 3
16 PacketCable E-UE
17 Reserved for eSTB-IP26
18 Reserved for eSTB-DSG27
19–31 Reserved for other eDOCSIS interfaces
32 + Other CPE interfaces
Interface Types
Configuration File CM and eDVA provisioning files, as described in DOCSIS and PacketCable
Provisioning specifications, use TLV (Type/Length/Value) objects to specify configuration
Notes parameters. This section provides information useful in provisioning Touch-
stone products through configuration files.
TS7.5 supports TLV-39, used to set DOCSIS 2.0 mode when operating with a
DOCSIS 2.0 CMTS or a DOCSIS 3.0 CMTS but not in Multiple Transmit
Channel mode. When operating in Multiple Transmit Channel mode, the
TLV-39 setting is ignored.
When not in Multiple Transmit Channel mode, if the provisioning file sets
TLV-39 to disabled, the E-UE advertises itself as a DOCSIS 2.0 device even
when registering on a DOCSIS 1.1 upstream. The following flowchart shows
the registration process when advertising DOCSIS 2.0 capabilities.
MTA locks
on DS during
initial registration
Begin scanning
for another
downstream
Provisioning Con- Provisioning changes are necessary to transition from a Touchstone North
siderations for Eu- American load to the EURO load. The basic flow sequence remains the
ropean Loads same; however, some OIDs change from the North American PacketCable
MIBs to the IETF PacketCable MIBs. The objects that require OID changes
are highlighted below.
• pktcMtaDevConfigFile
• pktcMtaDevProvConfigHash
• pktcMtaDevProvConfigKey
• pktcMtaDevConfigFile
• pktcMtaDevProvConfigHash
• pktcMtaDevProvConfigKey
IPv6 eRouter Con- When provisioned for IPv6 addressing, the eRouter expects an IPv6 address
siderations with a /56 prefix, either from DHCPv6 or by static assignment. This is a
requirement for CPE devices to successfully connect to the eRouter.
DHCP Interactions
When a Touchstone E-UE registers, the CM and eDVA make separate DHCP
and TFTP requests.
CM-side Interac- The Telephony Modem CM component sends various information to the pro-
tions visioning server using the DHCP options described below.
DHCP option 51, described in RFC 2132, allows a client device to request a
particular lease time for its IP address. The option contains a 32-bit number
specifying the requested lease time in seconds.
Touchstone firmware sends DHCP option 51 in DHCP Request messages
during IP address renew and rebind operations.
eDVA-side Interac- The Telephony Modem eDVA component sends various information to the
tions provisioning server using the DHCP options described below.
Gateway Interac- The router portion of Touchstone Gateways sends various information to the
tions provisioning server using the DHCP options described below.
See ‘‘XML Configuration File’’ on page 495 for an example XML configura-
tion file.
Disabling Option Touchstone firmware can be configured to ignore the ‘‘SNMP Entity’’
122 Sub-Option 3 (DHCP Option 122 Sub-Option 3) comparison checks during eDVA DHCP
Enforcement Renew and Rebind processing. This may be necessary if you want to allow
the eDVA to direct Link Up and Link Down traps to an alternate trap server.
To configure this setting, set the arrisMtaDevDhcpSubOpt3Immediate
object to off(1) to disable the override, or on(2) to enable the override.
Provisioning Modes
This mode is also called ‘‘Full PacketCable,’’ and is the default provisioning
mode. The data and telephony components have unique IP addresses, MAC
addresses, and configuration files (i.e. two of each per E-UE). When the E-
UE registers, it makes two separate DHCP and TFTP requests.
SNMP communication uses SNMPv3, sending an SNMPv3 INFORM. The
E-UE and provisioning system support Kerberos mutual authentication and
Kerberized SNMPv3 messaging.
IPsec is supported, and may be enabled or disabled using the pktcMtaDev-
CmsIpsecCtrl object (enabled by default). Media encryption (voice secu-
rity) can be enabled on a per-call basis using NCS signaling (the LCO/SDP
options) or disabled per eDVA using a feature switch. The feature switch is
stored in NVRAM.
The following diagram shows the full PacketCable event sequence. All
events are included.
CM/ DOCSIS DOCSIS DOCSIS Prov PKT PKT PKT MSO
Flow CMTS Syslog
eDVA DHCP TFTP ToD Server DHCP DNS TFTP KDC
Begin DOCSIS Initialization/Registration
DHCP Broadcast Discover (Option Code 122)
CM-1
DHCP Offer (Option Code 122 w/telephony service provider’s DHCP server address = [255.255.255.255])
CM-2
DHCP Request
CM-3
DHCP Ack
CM-4
DOCSIS 1.1 CM config file request
CM-5
DOCSIS 1.1 CM config file
CM-6
ToD Request
CM-7
ToD Response
CM-8
CM registration with CMTS
CM-9
CMTS Registration ACK
CM-10
End DOCSIS Initialization/Registration
DHCP Broadcast Discover (opt. code 60 w/MTA device identifier, request opt. 122
MTA-1
DHCP Offer (opt. code 122 w/name of provisioning realm
MTA-2
DHCP Request
MTA-3
DHCP Ack
MTA-4
DNS Request
MTA-5
DNS Srv (KDC host name associated with the provisioning realm)
MTA-6
DNS Request
MTA-7
DNS Response (KDC IP address)
MTA-8
AS Request
MTA-9
AS Reply
MTA-10
TGS Request
MTA-11
TGS Reply
MTA-12
AP Request (Key Mgmt Prot Ver., Protocol ID, KRB_AP_REP, ciphersuites, SHA-1 HMAC
MTA-13
AP Reply (Key Mgmt Prot Ver., Protocol ID, KRB_AP_REP, ciphersuite selected, key lifetime, Ack req., HMAC
MTA-14
SNMP Inform
MTA-15
SNMP Get Request(s) for MTA device capabilities (optional/iterative)
MTA-16
SNMP Get Response(s) containing MTA device capabilities (optional/iterative)
MTA-17
MTA config file
MTA-18
SNMP Set with URL encoded file download access method (TFTP or HTTP), filename, hash, and encryption key (if required)
MTA-19
Resolve TFTP server FQDN
MTA-20
TFTP server IP address
MTA-21
Telephony config file request
MTA-22
Telephony config file
MTA-23
MTA send telephony service provider Syslog a notification of provisioning completed (optional
MTA-24
Notify completion of telephony provisioning (MTA MAC address, ESN, pass/fail)
MTA-25
PacketCable HYBRID
PacketCable BASIC
The following diagram shows the sequence for PacketCable BASIC.1. This
sequence skips several steps in the eDVA provisioning. The PacketCable
BASIC.2 sequence is nearly identical to BASIC.1, but does not skip the last
step in the eDVA provisioning.
CM/ DOCSIS DOCSIS DOCSIS Prov PKT PKT PKT MSO
Flow CMTS Syslog
eDVA DHCP TFTP ToD Server DHCP DNS TFTP KDC
Begin DOCSIS Initialization/Registration
DHCP Broadcast Discover (Option Code 122)
CM-1
DHCP Offer (Option Code 122 w/telephony service provider’s DHCP server address = [255.255.255.255])
CM-2
DHCP Request
CM-3
DHCP Ack
CM-4
DOCSIS 1.1 CM config file request
CM-5
DOCSIS 1.1 CM config file
CM-6
ToD Request
CM-7
ToD Response
CM-8
CM registration with CMTS
CM-9
CMTS Registration ACK
CM-10
End DOCSIS Initialization/Registration
DHCP Broadcast Discover (opt. code 60 w/MTA device identifier, request opt. 122
MTA-1
DHCP Offer (opt. code 122 w/name of provisioning realm
MTA-2
DHCP Request
MTA-3
DHCP Ack
MTA-4
DNS Request
MTA-5
DNS Srv (KDC host name associated with the provisioning realm)
MTA-6
DNS Request
MTA-7
DNS Response (KDC IP address)
MTA-8
AS Request
MTA-9
AS Reply
MTA-10
TGS Request
MTA-11
TGS Reply
MTA-12
AP Request (Key Mgmt Prot Ver., Protocol ID, KRB_AP_REP, ciphersuites, SHA-1 HMAC
MTA-13
AP Reply (Key Mgmt Prot Ver., Protocol ID, KRB_AP_REP, ciphersuite selected, key lifetime, Ack req., HMAC
MTA-14
SNMP Inform
MTA-15
SNMP Get Request(s) for MTA device capabilities (optional/iterative)
MTA-16
SNMP Get Response(s) containing MTA device capabilities (optional/iterative)
MTA-17
MTA config file
MTA-18
SNMP Set with URL encoded file download access method (TFTP or HTTP), filename, hash, and encryption key (if required)
MTA-19
Resolve TFTP server FQDN
MTA-20
TFTP server IP address
MTA-21
Telephony config file request
MTA-22
Telephony config file
MTA-23
MTA send telephony service provider Syslog a notification of provisioning completed (optional
MTA-24
Notify completion of telephony provisioning (MTA MAC address, ESN, pass/fail)
MTA-25
Setting Up the Set up the provisioning data as follows to use a non-PacketCable compliant
Provisioning provisioning server:
Server Data • The eDVA DHCP offer may not use DNS (option 6), SNMP, or security
(Kerberos or Ticket Granting).
• The FQDN must be in IPv4 format (i.e. an IP address such as 10.1.2.3
rather than a domain name such as tt4.example.net).
Note 1: All PacketCable provisioning modes require a PacketCable-com-
pliant provisioning server.
Verifying eDVA The MIB object pktcMtaDevProvisioningState indicates the status of the
Provisioning and eDVA initialization process. The MIB object pktcNcsEndPntStatusError
Endpoint Status indicates whether the endpoint has successfully registered with the call
server.
Options Required The following DHCP options are required in all CM and eDVA offers. The
in All Provisioning E-UE cannot function without a subnet mask and at least one router, DNS
Modes server, and Syslog server.
Option Description
1 Subnet mask
3 IP address of the gateway router (one or more)
6 IP address of the DNS servers (one or more)
7 IP address of the log servers (one or more)
Note: In addition to the required options listed above, ARRIS strongly rec-
ommends including option 4 (IP address of the ToD server) in all CM and
eDVA offers.
PacketCable These options are valid for Full PacketCable and PacketCable minus KDC
Modes provisioning modes. Note that options 122 and 177 are mutually exclusive
(specify one or the other, not both). Option 177 is the default for PacketCa-
ble minus KDC.
CM DHCP Option 4: ToD Server IP Address
CAUTION
Potentially service-affecting
Override settings can potentially prevent the eDVA from registering. For
example, setting this object to ipv6(2) when no DHCPv6 server is available
causes the eDVA to attempt to register as IPv6 only, ignoring any DHCPv4
servers. Since this setting is stored in non-volatile memory, you must either
change the value through SNMP or reset the Telephony Modem to factory
defaults to clear the setting.
Displaying the You can view the current MDD setting and override using the ‘‘DHCP
MDD Setting Parameters’’ troubleshooting page (select DHCP in the Advanced pages).
This page displays both the MDD Override setting and the selected MDD
mode.
The CM generates log messages in response to MDD settings or overrides:
• ‘‘MDD IP mode Set’’ — override disabled. The log message shows the
mode set by the MDD message.
This section describes provisioning modes and flows appropriate to IPv6 sup-
port.
Provisioning Touchstone firmware supports the following provisioning modes for IPv6:
Modes • SECURE (full PacketCable)
• BASIC.1/2 (PacketCable and ARRIS versions)
• HYBRID.1/2
• GUPI
• GUPI with Encrypted E-UE config file
• PacketCable Minus KDC
Single MAC provisioning is explicitly not supported.
docsIf3CmMd- TS7.5 supports the docsIf3CmMdCfgTable objects for controlling IPv6 pro-
CfgTable Objects visioning.
docsIf3CmMdCfgIpProvMode
Specifies whether the CM honors or ignores the TLV5.1 message
from the CMTS. See ‘‘Selecting an Addressing Mode’’ below for
details.
Equivalent ARRIS object: arrisCmDoc30SetupMddIpModeOver-
ride. Use only one object in the configuration file; using both
objects may produce unexpected results.
Note: When changing the arrisCmDoc30SetupMddIpModeOver-
ride object, the CM resets immediately regardless of the doc-
sIf3CmMdCfgIpProvModeResetOnChange setting.
docsIf3CmMdCfgIpProvModeResetOnChange
Specifies whether the CM resets when the docsIf3CmMdCfgIp-
ProvMode object changes. The default is false(2).
docsIf3CmMdCfgIpProvModeResetOnChangeHoldOffTimer
When docsIf3CmMdCfgIpProvModeResetOnChange is set to
true(1), this object specifies the time, in seconds, that the CM waits
before resetting. The default value of 0 means the CM resets imme-
diately.
docsIf3CmMdCfgIpProvModeStorageType
Specifies whether the value of docsIf3CmMdCfgIpProvMode per-
sists across reboots. The default nonVolatile(3) causes the value to
persist. If set to volatile(2), the value persists over one reset.
Selecting an Ad- Touchstone firmware supports the DOCSIS 3.0 MAC Domain Descriptor
dressing Mode (MDD) message, defined in the MAC and Upper Layer Protocols Interface
Specification, , for selecting IPv4 or IPv6 addressing. The CM uses TLV 5.1
in the MDD to select the addressing mode as follows:
Value Addressing Mode
0 IPv4
1 IPv6
Alternate Provisioning Mode (APM):
2
try IPv6 first, then IPv4
3 Dual Provisioning Mode (DPM)
If the E-UE does not find an MDD during provisioning, it always selects
IPv4 addressing.
The docsIf3CmMdCfgIpProvMode object can override the MDD and set
IPv4 or IPv6 operation.
CAUTION
Potentially service-affecting
Use this feature carefully. An invalid setting could isolate the Telephony
Modem from the network.
DHCP Behavior for When the CM receives an MDD message that specifies IPv6 operation, it
IPv6 Provisioning acquires its IP address according to the MAC and Upper Layer Protocols
Interface Specification, TS7.5 supports both SLAAC and DHCPv6 mecha-
nisms.
TS7.5 supports the DHCPv6 options listed in the following table. For
details, see the DOCSIS 2.0 + IPv6 Cable Modem Technical Report, CM-TR-
DOCSIS2.0-IPv6-V01-080307.
Provisioning File The configuration file must be specific to either IPv6 or IPv4. If the plant has
Notes mixed IPv4 and IPv6 CMs, each address type requires separate provisioning
files.
IPv6 addresses must be fully qualified and not compressed. For example, an
IPv6 address of 2001:0200:0000:0000:0000:0000:0000:0022 cannot be
entered as 2001:0200::0022.
TLV-38 Enhance- Touchstone firmware supports TLV-38 (Notification) sub-type 8 (SNMP noti-
ments fication IPv6 address). Specify this sub-TLV to send SNMP traps and
informs to an IPv6-configured receiver.
WBM760 Consid- Upgrading WBM760 models from loads earlier than TS7.1.95, or TS7.3
erations loads earlier than TS7.3.38, requires in interim upgrade to TS7.3.38 and then
to TS7.5.
Upgrading from Customers upgrading Telephony Modems or Telephony Gateways from NCS
Earlier NCS Loads loads TS7.1.98 or newer can upgrade directly to TS7.5 NCS loads. Earlier
to TS7.5 NCS loads require an interim upgrade to TS7.1.98. You may need to review the
Loads contents of configuration files to take advantage of new features.
Upgrading from Customers upgrading from TS7.1 or TS7.3 SIP loads can upgrade directly to
Earlier SIP Loads TS7.5 ARRIS SIP loads.
to TS7.5 SIP Customers upgrading from TS7.2 or TS7.4 can upgrade directly to TS7.5
Loads ARRIS PC20 loads.
You may need to review the contents of configuration files to take advantage
of new features.
Upgrading Be- Customers upgrading from earlier TS7.x NCS loads to a TS7.5 SIP load, or
tween NCS Loads vice versa, must replace eDVA configuration files with MIB objects appropri-
and SIP Loads ate to the load.
Upgrading the Follow these steps to upgrade the Touchstone firmware load using a provi-
Firmware through sioning server.
Provisioning 1 Install the new firmware on the TFTP server.
2 Use the provisioning server to add or verify the following items in the
cable modem configuration file:
Upgrading the Follow these steps to upgrade the Touchstone firmware load using an SNMP
Firmware through manager. See ‘‘Using Enhanced Firmware Loading’’ on page 47 for infor-
SNMP mation about the Touchstone Firmware Upgrade System.
1 Using the provisioning server, add the ManufacturerCVC to the con-
figuration file.
2 Using the SNMP manager, set the following docsDevSoftware
objects:
docsDevSwServerAddressType
Set to 1 for IPv4 server addressing or 2 for IPv6 addressing.
docsDevSwServerAddress
The IP address of the server containing the load.
docsDevSwFilename
The file name of the load.
docsDevSwAdminStatus
Set to upgradeFromMgt(1).
The E-UE downloads the new firmware, then resets.
3 Verify that the E-UE has the new load by checking the value of the
docsDevSwOperStatus object.
Upgrade Process Note 1: Telephony Modems do not begin or continue a firmware upgrade
when running on battery power. This prevents a potential corruption issue if
a battery were to fail while an upgrade is in progress.
Note 2: Touchstone firmware can download and store new firmware while a
call is in progress, then apply the new load once all lines are idle. Alterna-
tively, the E-UE can reject a request to start downloading firmware if any line
is off-hook.
When a Touchstone E-UE ranges and registers with the headend and receives
the arrisCmDoc30SwTable object (see ‘‘Enhanced Firmware Loading
Options’’ on page 49 for a listing of relevant MIB objects) in its configura-
tion file, it proceeds as follows:
Download Acceptance
1 If the E-UE is running on battery power, the E-UE rejects the
download and the process stops. Otherwise, it proceeds to
step 2.
2 The E-UE checks the docsDevSwAdminStatus object.
If the value is allowProvisioningUpgrade, proceed to step 3.
Otherwise, the device uses the standard docsDevSoftware MIB
objects for its upgrade decision-making.
A setting of upgradeFromMgt is not allowed in the configura-
tion file and returns an error condition.
3 The E-UE checks the arrisCmDoc30SwAdminStatus object.
• If the value is allowArrisProvisioningUpgrade, proceed to
step 4.
• If its value is ignoreArrisProvisioningUpgrade, the device
uses the standard docsDevSoftware MIB objects for its
upgrade decision-making.
• Ringing a line
3 If an active connection exists, the eDVA waits for all lines to go
idle then starts a 30-second timer.
4 If the timer expires with no lines becoming active, the E-UE
applies the firmware and resets; otherwise, it returns to step 3.
Touchstone firmware disables Enhanced Firmware Loading if docsDevSw-
AdminStatus is set to either upgradeFromMgt(1) or ignoreProvi-
sioningUpgrade(3). This allows deployment of provisioning files where the
docsDevSwAdminStatus object is not specified, or set to the default value
of allowProvisioningUpgrade(2), and both the Enhanced Firmware Loading
and the standard DOCSIS upgrade mechanisms are defined. This configura-
tion behaves as follows:
• Non-ARRIS devices upgrade using the DOCSIS upgrade objects.
• ARRIS devices automatically use Enhanced Firmware Loading to load
the correct firmware version.
• When an E-UE is manually upgraded using SNMP, it automatically sets
the docsDevSwAdminStatus object to ignoreProvisioningUp-
grade(3); this disables Enhanced Firmware Loading on ARRIS devices
and standard DOCSIS upgrading on all devices. To restore the ARRIS
firmware load specified in the load lineup, change docsDevSwAdmin-
Status to allowProvisioningUpgrade and reset the modem using
docsDevResetNow.
During the server communication and firmware image file download, there is
no interruption to E-UE 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 E-UE, 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.
upgradeFromArrisMgt(1)
Immediately upgrade the device using Enhanced Firmware Loading.
If a valid entry cannot be found, then an error condition is returned.
This is not a valid setting 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.
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.
arrisCmDoc30SwHwModel Values
Firmware Down- Touchstone firmware may generate the following log messages in response to
load Log Mes- a firmware download request.
sages Event ID Context Severity Message
2417164299 CM Error Touchstone SW Upgrade
Aborted due to Battery AC-
FAIL Condition
2417164304 CM Error Touchstone SW Upgrade
Aborted due to Call in
Progress
2417164305 CM Notice Touchstone SW Upgrade
Reboot Delayed due to Call
in Progress
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
arrisCmDoc30SwAdminStatus to allowArrisProvisioningUpgrade(2).
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 TM802 Rev. 1"
SnmpMib = arrisCmDevSwHwModel.1 "TM802G"
SnmpMib = arrisCmDevSwHwRev.1 1
SnmpMib = arrisCmDevSwServer.1 10.1.50.21
SnmpMib = arrisCmDevSwFilename.1 "TS0701_07112006.bin"
SnmpMib = arrisCmDevSwCustomerLoadId.2 "Node 1 TM822"
SnmpMib = arrisCmDevSwHwModel.2 "TM822G"
SnmpMib = arrisCmDevSwServer.2 10.1.50.21
SnmpMib = arrisCmDevSwFilename.2 "TS0701_07112006.bin"
SnmpMib = arrisCmDevSwCustomerLoadId.3 "Euro TM802 Rev. 1"
Rejecting a Down- TS7.5 can reject a firmware upgrade while a call is in progress, complying
load Request with a PacketCable 1.5 requirement to minimize service impacts.
Setting Up ARRIS Follow these steps to set up Enhanced Firmware Loading in a configuration
Enhanced file.
Firmware Loading 1 Use a provisioning server, or PacketACE version 5.8 or newer, to cre-
ate an entry in the arrisCmDoc30SwTable with the following set-
tings:
• arrisCmDoc30SwCustomerLoadId (optional): name of the load
lineup.
• arrisCmDoc30SwHwModel: the Touchstone E-UE model (see
‘‘arrisCmDoc30SwHwModel Values’’ on page 51 for a list of valid
model names).
• arrisCmDoc30SwHwRev (optional): the hardware revision of the
E-UE. Leave blank for this entry to apply to all revisions of the
same model.
• arrisCmDoc30SwServerAddressType: The CM addressing type
(the eDVA always uses IPv4 addressing). Either 1 to use IPv4, or 2
for IPv6.
• arrisCmDoc30SwServerAddress: the IP address of the TFTP
server containing the firmware load for E-UEs matching the model
and revision.
• arrisCmDoc30SwFilename: the file name of the firmware load for
E-UEs matching the model and revision.
2 In the configuration file, set the arrisCmDoc30SwAdminStatus
object to allowArrisProvisioningUpgrade.
Note: The E-UE uses Enhanced Firmware Loading to download its
firmware during the next reboot, unless the E-UE is running on bat-
tery power.
3 Do one of the following to force the E-UE to immediately download
its firmware file, if desired:
• Reboot the E-UE, either directly or by setting the docsDevReset-
Now object to true(1) from the network manager.
Specifying and Follow these steps to specify a CVC for a firmware load.
Verifying a CVC Note: If you specify a CVC using these steps, any manufacturer or co-signer
CVC specified in standard DOCSIS TLVs is used only for a standard DOC-
SIS download.
1 To specify a CVC to use with the firmware load:
a Break the CVC into segments of 255 octets or less.
b Populate the arrisCmDoc30SwCvc1, arrisCmDoc30SwCvc2,
arrisCmDoc30SwCvc3, and arrisCmDoc30SwCvc4 objects in
the configuration file with the segmented CVC.
2 To verify the CVC value after firmware loading, check the arrisCm-
Doc30SwCvcStatus object.
L2VPN Provisioning
+
TS7.5 MSUP5 introduces Business Services over DOCSIS (BSoD) support +
as described in CM-SP-L2VPN-I09-100611. The following services are sup- +
ported: +
Transparent LAN Service (TLS) +
TLS is intended for commercial enterprise customers. It intercon- +
nects subscriber enterprise LANs using Layer 2 Virtual Private Net- +
work (L2VPN) forwarding. A cable operator offers TLS by provid- +
ing one L2VPN for each commercial enterprise. +
Note: The object setting takes effect at the next reboot, and persists
across reboots. If this object is set to disable(0), the modem disables
DOCSIS 3.0 operation until re-enabled.
2 To configure how the Telephony Modem handles partial service situa-
tions, proceed to ‘‘Recovery from Partial Service’’ on page 267.
3 To display the current bonding mode, query the arrisCmDoc30Bond-
ingMode object. This object contains a string showing the current
DOCSIS operating mode and the number of bonded downstream and
upstream channels.
Examples:
DOCSIS3.0 4x1
DOCSIS2.0 1x1
DOCSIS and PacketCable standards specify the use of service flows to sepa-
rate and prioritize voice and data traffic. Touchstone firmware provides two
QoS modes.
See CM-SP-MULPIv3.0-I12-100115 for detailed descriptions of Service
Flow types.
Full DQoS Mode Touchstone firmware defaults to Dynamic Quality of Service (DQoS) provi-
sioning. Full DQoS simplifies provisioning tasks by only requiring that the
primary Best Effort (BE) and MGCP (signaling) flows be provisioned. The
firmware dynamically sets up and tears down UGS service flows, using a
standard set of parameters designed for efficient use in DOCSIS-based net-
works, as needed. The CMS controls the bandwidth authorization as speci-
fied in the PacketCable Dynamic Quality of Service Specification, PKT-SP-
DQOS1.5-I03-070412.
Full DQoS provides an added layer of security by authenticating eDVAs that
contact the CMS during call setup. Each session is authorized; the session
authorization uses a handle (the Gate ID) assigned by the CMTS, passed to
the CMS, and sent to the eDVA using an NCS message, to match requests
with authorizations. Upon receiving call-signaling information, the eDVA
passes the Gate-ID to the CMTS in a DSA/DSC message.
DSX QoS Mode Touchstone firmware supports an ARRIS-proprietary feature that implements
QoS using UGS flows for voice transmission using DOCSIS 1.1 DSx mes-
saging. This functionality provides a level of QoS in a network where the
CMS and CMTS do not support the PacketCable Full DQoS model.
DSx QoS functionality can be activated using a feature switch. When acti-
vated, the firmware sends the appropriate DSx messages needed to
Add/Modify/Delete the UGS service flows. DSx messages flow only
between the CMTS and the eDVA, and do not involve the CMS in any valida-
tion or requests for setting up or monitoring the UGS flows.
Note: When using this functionality with the ARRIS C4 CMTS, PacketCable
authorization needs to be disabled. Contact your next level of support for
instructions.
Dual-Mode Operation
Configuration Use European CVCs in configuration files for Dual Mode units. This allows
Files and Signed configuration files for a normal European unit to work for Dual Mode Tele-
Loads phony Modems as well. If the firmware load for a Dual Mode unit is signed,
it should be European signed.
Certificates Dual Mode Telephony Modems are programmed with four certificates, a
European and North American certificate each for the CM and eDVA.
When the Telephony Modem boots up, it checks the value of the Dual Mode
Discovered Market (DMDM) stored in NVM, and uses the certificates that
correspond to that region. If the DMDM value is uninitialized, which would
be the case the first time the Telephony Modem is installed or after a factory
reset, it uses European signed certificates.
This CODEC array would set G.729 as the default with DTMF relay enabled.
If ‘‘PCMU’’ or ‘‘PCMA’’ are not specified, the SIP firmware automatically
switches to the G.711 CODEC when needed for fax or modem calls, based
on the value of the sipCfgDefaultG711 object.
If the pktcEDVADtmfRelay object is set to true(1), the eDVA also specifies
‘‘telephone-event’’ in the list of supported CODECs.
Implementation of CODECs is defined by the Codec and Media Specifica-
tion, PKT-SP-CODEC-MEDIA-I09-100527.
The supported packetization rates in TS7.5 are 10 and 20 ms.
G.729 CODEC Touchstone firmware supports the G.729 CODEC to perform toll-quality
Support voice compression. 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 variations such as G.729E have
been subsequently defined.
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:
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 0
b=AS:24
a=mptime:20
a=rtpmap:18 G729/8000/1
a=rtpmap:0 PCMU/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
In this example, the endpoint can autonomously fall back to PCMU if neces-
sary.
For outbound calls, SIP loads send the CODECs specified in either the
pktcEUERSTBCallPrefCodecList object (PC20 loads) or the sipCfgProvi-
sionedCodecArray object (ARRIS SIP loads) object in the initial INVITE.
To include G.729, add ‘‘G729’’ to the list. A typical configuration might
include one of the following settings:
{SnmpMib pktcEUERSTBCallPrefCodecList.0 "PCMU,PCMA,G729"}
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.
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.
CODECs and Sup- This section describes how low bit-rate CODECs and T.38/SuperG3 FAX
ported Lines relay interact.
The following rules apply to Model 7 and Model 8 Telephony Modems and
Telephony Gateways:
• 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
Note: You must set this object using an SNMP manager. If this object
is included in a configuration file, the eDVA ignores the setting.
2 To set line status using the CLI, enter the following commands:
Console> voice ↵
Voice> callp ↵
Call Processing> spls {line} {state} ↵
Where:
line
is the line number: 1 to the number of lines supported by the
Telephony Modem.
state
is either 0 to use normal state processing, or 1 to force-disable
the line.
Controlling LED WBM760, TM722, and Model 8 modems provide multi-colored DS, US, and
Behavior Link LEDs. If desired, follow these steps to control the behavior of the
multi-color LEDs:
1 To enable multi-color functionality, use the arrisCmDoc30SetupMul-
tiColorLedBitmap object. Set a bit to 1 to enable multi-color func-
tionality (green for high-speed connections, amber for normal speed);
or 0 to use green for all connection speeds. The valid bits are:
• 0x1: Link LED
• 0x2: US LED
• 0x4: DS LED
Default: 7.
This setting persists across reboots.
2 To invert the color display (amber for high-speed connections, green
for normal speed), set the arrisCmDoc30SetupInvertMulticol-
orLEDs object to enable(1). The following table shows the DS, US,
and Link LED colors for each setting and condition.
DS US Link
Value
Bonded Non-bonded Bonded Non-bonded GigE 10/100BaseT
disable Green Amber Green Amber Green Amber
enable Amber Green Amber Green Amber Green
Controlling ToS Touchstone firmware sets the ToS byte in RTCP packets to a value of 0. Fol-
Byte Marking low these steps to change the value of the RTCP ToS byte.
1 Using an SNMP network manager, change the arrisMtaDevRtcpTos-
Value object to the desired value. Valid range: 0 to 63.
Controlling IPsec IPsec (Internet Protocol Security) is a collection of Internet standards used to
Functionality encrypt and authenticate IP packets, to provide message integrity and privacy.
IPsec provides security at the network layer (all TCP and UDP packets, and
layers above).
Note: Touchstone E-UEs use only the IPsec ESP transport mode.
IPsec is enabled by default. Follow these steps to provision IPsec functional-
ity.
1 For each CMS that the eDVA can communicate with, set the pktcMta-
DevCmsIpsecCtrl object in the eDVA configuration file. The object
is indexed by the CMS FQDN. Set the object to true(1) to enable
IPsec between the eDVA and a particular CMS, and false(2) to dis-
able it.
2 Reboot the eDVA to allow the new provisioning to take effect.
Configuring the Telephony Modems support both trapezoidal and sinusoidal ringing
Ringing Waveform waveforms when used with North American country templates. You may
need to change the waveform if certain non-EIA compliant subscriber equip-
ment does not recognize the trapezoidal waveform (in short, the phone does
not ring).
CAUTION
Potentially service-affecting
Sinusoidal ringing is only supported for North American templates, and other
templates using 20 Hz ringing. Use of this feature with other templates may
result in loss of service.
Configuring Loop Touchstone Telephony Modems support a ‘‘boost,’’ or high loop current
Current mode to compensate for faulty CPE or wiring. Use this setting, for example,
to alleviate issues related to off-hook not being detected or fax machines fail-
ing to operate properly due to increased current draw by the equipment.
Loop current varies depending on boost mode and country template:
• Normal mode: 23 mA
• Boost mode (North American templates): 40 mA
• Boost mode (other templates): 33 mA
eDVAs using North American country templates (that is, the value of the
ppCfgMtaCountryTemplate object is one of northAmerica57(1),
northAmerica33(17), northAmerica09(18), or northAmerica66(32))
default to high (boost) loop current. Other country templates default to nor-
mal loop current.
Note: If you set the loop current through SNMP, the eDVA does not retain the
setting over reboots. If you set the loop current in the configuration file, the
setting is written to NVRAM and retained over reboots.
1 To specify normal loop current (the default for non-North American
loads), set the ppCfgPortLoopCurrent.line object to 1, where line is
the line number to set (beginning with .1).
2 To specify high loop current (the default for North American loads),
set the ppCfgPortLoopCurrent.line object to 2.
Note: High loop current reduces battery hold-up times.
Loop Voltage Man- Use the pktcEnNcsEndPntLVMgmtPolicy to set the Loop Voltage Manage-
agement Policies ment policy. The following policies are supported:
• voltageAtAllTimes(1)
• voltageUnlessRFQAMabsent(2)
• voltageBasedOnServiceOrTimers(3)
• voltageBasedOnService(4) (default)
When this option is selected, the eDVA maintains loop voltage at all times
with the following two exceptions:
• During firmware initialization of the line card. Touchstone eDVAs
remove loop voltage for up to 1 second during firmware initialization,
although typically this time is shorter.
• When the unit has no power.
When this option is selected, the eDVA maintains loop voltage when it can
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 the
modem does not detect any QAM carriers after scanning the STD and LRC
When this option is selected, the Telephony Modem maintains loop voltage
when in-service or during manually-initiated resets and T4 timeouts. The
Telephony Modem is considered in-service when eDVA TFTP is complete.
Both subscriber resets (pushing the Reset button) and headend-initiated resets
(SNMP, firmware upgrade) are considered manually-initiated.
Two timers govern the behavior of the eDVA during resets or outages:
pktcEnNcsEndPntLVMgmtResetTimer
The reset timer determines how long the eDVA maintains loop volt-
age during a reset.
Note: If the reset timer is set to a period longer than the scanning
time between resets (typically 7 minutes), the eDVA never drops
loop voltage.
pktcEnNcsEndPntLVMgmtMaintTimer
The plant maintenance timer (PMT) determines how long the eDVA
maintains loop voltage when the E-UE loses its downstream signal.
This timer may be used to maintain loop voltage during extended
plant maintenance intervals.
When both timers expire without the eDVA completing provisioning, or the
T4 timer expires as well, the eDVA drops loop voltage.
This is the default policy. Using this option, the eDVA goes through the fol-
lowing steps:
1 When applying initial AC power, Telephony Modems do not apply
loop voltage.
2 When the eDVA completes TFTP and the lines are provisioned, it
applies loop voltage only if the eDVA completes provisioning and the
pktcMtaDevProvisioningState MIB object has one of the following
values:
• pass(1)
• passWithWarnings(4)
• passWithIncompleteParsing(5)
Loop Voltage Man- The pktcEnNcsEndPntLVMgmtTable table contains the loop voltage policy
agement MIB Ob- and timers. This table is indexed by ifIndex; an index value of 1 applies the
jects policy settings to all eDVA lines.
The objects in the pktcEnNcsEndPntLVMgmtTable are:
pktcEnNcsEndPntLVMgmtPolicy
Defines the policy; one of:
• voltageAtAllTimes(1)
• voltageUnlessRFQAMabsent(2)
• voltageBasedOnServiceOrTimers(3)
• voltageBasedOnService(4)
See ‘‘Loop Voltage Management Policies’’ above for descriptions of
each policy.
pktcEnNcsEndPntLVMgmtResetTimer
The time, in minutes, allowed for an eDVA to successfully provision
after a reset. This timer applies only when pktcEnNcsEndPnt-
LVMgmtPolicy is set to a value of voltageBasedOnServiceOr-
Timers(3). In all other cases, reading this object returns a value of
zero.
The eDVA starts the timer upon a hard reboot, a soft reset or a T4
timeout. The timer value persists the last configured value (i.e., not
the countdown value) of this MIB Object across hard reboots and
soft resets.
Valid range: 0 to 1440 (minutes). Default: 5.
pktcEnNcsEndPntLVMgmtMaintTimer
The time, in minutes, that the eDVA maintains loop voltage regard-
less of the eDVA’s connection or provisioning status. This timer
applies only when pktcEnNcsEndPntLVMgmtPolicy is set to a
value of voltageBasedOnServiceOrTimers(3). In all other cases,
reading this object returns a value of zero. The current timer value
persists across soft resets, but resets to zero for a hard reset or
power-cycle.
The eDVA starts the timer when it is set to a value greater than zero.
The eDVA maintains loop voltage until the timer expires.
Valid range: 0 to 1440 (minutes). Default: 0.
Note: This object is only used with policy option 3 and is ignored if a
policy setting of other than 3 is used.
3 For eDVAs using policy 3, modify the plant maintenance timer (if
necessary) by setting the pktcEnNcsEndPntLVMgmtMaintTimer
object. Valid range: 0 to 1440 minutes (24 hours).
4 Reset the eDVA to enable the new loop voltage policy on the eDVA.
Feature Switches
Bit Description
Bit Description
0x00001000 Nuera RFC 2833 messaging without request using payload
127 (NCS only)
Set this bit to instruct the eDVA to generate RFC 2833 events
with a payload type of 127 without specifically being
instructed to do so (for compatibility with the Nuera RDT).
Clear this bit (the default) to generate RFC 2833 events
using NCS signaling and SDP exchange.
0x00004000 DSx/Access only DQoS (NCS and SIP)
Set this bit to use DSx/Access-only DQoS only between the
CM and CMTS.
0x00008000 Disable endpoint from sending provisional responses (NCS
only)
Set this bit to disable sending provisional responses to the
CMS if execution of the CRCX or MDCX commands takes
additional time to execute. The ARRIS eDVA sends this
provisional response if DQoS is to be performed, due to the
extra amount of time it takes to set up bandwidth between
the CM and CMTS. Once the provisional response is issued,
the CMS should stop retransmitting the command. When
the eDVA has completed the transaction, it transmits a
‘‘final’’ response back to the CMS. This ‘‘final’’ response
must be acknowledged by the CMS; otherwise, the eDVA
retransmits it until it is acknowledged.
The default is to send provisional responses in accordance
with PacketCable ECN MGCP-N-02218. Set this bit to pro-
vide compatibility with CMS vendors that are not capable of
supporting provisional responses.
0x00010000 Payload Header Suppression (NCS and SIP)
Set this bit to allow Payload Header Suppression of voice
packets between the CM and CMTS.
Note: This bit only affects PHS for RTP voice packet
streams. Its setting does not affect PHS for DOCSIS data
packets, which is controlled through the DOCSIS MIB.
Conversely, DOCSIS MIB settings do not affect PHS for
RTP voice packets.
0x00080000 LUCENT RFC-2833 messaging without request using pay-
load 94 (NCS only)
Some CMS vendors use RFC 2833 to have the eDVA pass
detected telephony events (e.g. offhook, onhook, digits) to a
PSTN gateway in-band, similar to ABCD robbed-bit signal-
ing. For compatibility with Lucent iMerge, set this bit to
instruct the eDVA to generate RFC 2833 events with a pay-
load type of 94 during call setup, without specifically being
instructed to do so. Clear this bit (the default) to generate
RFC 2833 events using NCS signaling and SDP exchange.
Bit Description
0x00100000 Allow AES encryption for RTP/RTCP (NCS only)
Clear this bit (the default) to allow the negotiation of voice
encryption, which is a requirement of PacketCable, and is
enabled by default on a per call basis. Set this bit to disable
this feature, and reduce the size of the eDVA’s SDP message
since encryption parameters are not included.
Note: If the CMS (and far end) can handle the increased size
of the SDP with AES encryption enabled, then set this bit
to 0, as the far end is capable of negotiating voice security
parameters (including NULL encryption) and the CMS will
instruct the eDVA on whether to use encryption or not on a
per-call basis.
0x00400000 NCS Redirect without IPsec (NCS only)
Set this bit to allow a CMS to redirect the eDVA to another
CMS that is not provisioned in the eDVA CMS table, allow-
ing the eDVA to communicate with the CMS without
attempting to establish an IPsec association first. Setting this
bit is for redirect cases only; the eDVA does not respond to
call servers not provisioned in the eDVA’s CMS table.
0x00800000 Add brackets around IP for eDVA FQDN (NCS only)
Set this bit to enable the eDVA to send an NCS message with
a bracketed IP address as part of the eDVA FQDN when
communicating with the call server.
For call servers that use IP address information instead of
FQDNs, the brackets surrounding the IP address are manda-
tory.
The following example shows the messaging format with
this feature switch enabled.
RSIP 78 aaln/1@[10.10.13.11] MGCP 1.0
NCS 1.0
0x01000000 Send DTMF digits via RFC 2833 with operator-specified
payload without request (NCS only)
Set this bit to instruct the eDVA to generate RFC 2833
DTMF events using a payload type defined in the ppCfg-
Rfc2833DigitPayloadType MIB object without being
instructed to do so by the CMS. The default payload type
value is 101.
0x08000000 Use alternate (non-sequential) Caller ID delivery order (NCS
and SIP)
Set this bit to have the eDVA present Caller ID in an alter-
nate (non-sequential) order. This may be required for com-
pliance with some CPE devices that expect Caller ID infor-
mation to be presented in a non-standard format. Clear this
bit (the default) to use a sequential order based on the param-
eter type (date/time, then number, then name).
Bit Description
0x10000000 Delay DLCX against connection on on-hook only line (for
VMWI) (NCS only)
Set this bit to delay processing of a Delete Connection mes-
sage from the CMS for a line that is on-hook, to allow any
queued RTP packets in the DSP jitter buffer to be played out.
In the case of VMWI, this prevents the DSP connection from
being closed while delivering FSK signals for VMWI. The
default setting for this bit is cleared (0).
0x20000000 Enable Automatic OSI (NCS only)
Set this bit to have the eDVA automatically generate OSI
(Open Switch Interval) to the CPE upon far end termination
of a call (i.e. the eDVA receives a DLCX command for the
last connection on the endpoint).
The arrisMtaDevAutomaticOsiDelay object specifies the
delay, in 100 ms increments, before sending the OSI. The
eDVA cancels OSI generation if any of the following events
occur before the timer expires:
• line goes on-hook
• hook flash on the line
• a new connection is created on the line
• CMS receives OSI request
The valid range for the MIB object is 0 (no delay) to 100
(10 seconds).
Example
If your configuration requires DSx-QoS, set the feature switch to include the
0x4000 and 0x10000 flags, using PacketACE or a provisioning server. If no
other flags are required, the setting would be as follows:
SnmpMib = ppCfgMtaCallpFeatureSwitch.0 hexstr: 00.01.C2.33 =
00.00.82.33 (default)
+ 00.01.40.00 (additional features)
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).
0x00000080 Omit mptime parameter in returned SDP (default = 0,
mptime 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 an operator-defined
payload without request (default = 0, telephone-event is
negotiated normally).
The following CRCX message is used to generate all the SDP examples,
unless otherwise specified:
CRCX 19901 aaln/[email protected] MGCP 1.0 NCS 1.0
C: 1234
M: recvonly
L: mp:20, a:PCMU, fxr/fx:t38-loose, xrm/mcr:on
The default feature switch settings are (0x0 for NCS loads, and 0x0020 for
SIP loads) generate the following SDP:
v=0
o=- 381749076 381749076 IN IP4 10.1.36.219
s=-
c=IN IP4 10.1.36.219
t=0 0
m=audio 65496 RTP/AVP 0
b=AS:81
a=rtcp-xr:voip-metrics
a=mptime:20
a=rtpmap:0 PCMU/8000/1
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=cdsc: 1 audio RTP/AVP 0 8 15 18 96 97 98 2 99 101
a=cpar: a=fmtp:18 annexb=no
a=cpar: a=rtpmap:101 telephone-event/8000/1
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, 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
m=audio 58810 RTP/AVP 0
b=AS:81
a=rtcp-xr:voip-metrics
a=ptime:10
a=rtpmap:0 PCMU/8000/1
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=X-pc-csuites-rtcp:81/70 81/71 82/70 82/71 80/70
a=sqn: 0
a=cdsc: 1 audio RTP/AVP 0 8 15 18 96 97 98 2 99 101
a=cpar: a=fmtp:18 annexb=no
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:161
a=cpar: a=T38FaxUdpEC:t38UDPRedundancy
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
m=audio 65496 RTP/AVP 0
b=AS:81
a=rtcp-xr:voip-metrics
a=mptime:20
a=rtpmap:0 PCMU/8000/1
a=sqn: 0
a=cdsc: 1 audio RTP/AVP 0 8 15 18 96 97 98 2 99 101
a=cpar: a=fmtp:18 annexb=no
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:161
a=cpar: a=T38FaxUdpEC:t38UDPRedundancy
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
m=audio 63672 RTP/AVP 0
b=AS:81
a=rtcp-xr:voip-metrics
a=mptime:20
a=rtpmap:0 PCMU/8000/1
a=X-pc-secret:base64:Qb8GFLNXP4Z3yiyxFx1Ws9vLph9qG6bTIXezUlz
rwia7iiNvPPkVYdZhZ77NEQ== zZjgwXRR2j5F04lDXefPTV06PT8g31Hn5V
Ea6NJvFPFsPiraDeDI35EI8KO+4A==
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=cdsc: 1 audio RTP/AVP 0 8 15 18 96 97 98 2 99 127
a=cpar: a=fmtp:18 annexb=no
a=cpar: a=rtpmap:127 telephone-event/8000/1
a=cpar: a=fmtp:127 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:161
a=cpar: a=T38FaxUdpEC:t38UDPRedundancy
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
m=audio 49688 RTP/AVP 0
b=AS:81
a=rtcp-xr:voip-metrics
a=mptime:20
a=rtpmap:0 PCMU/8000/1
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=X-pc-csuites-rtcp:81/70 81/71 82/70 82/71 80/70
a=sqn: 0
a=cdsc: 1 audio RTP/AVP 0 8 15 18 96 97 98 2 99 94
a=cpar: a=fmtp:18 annexb=no
a=cpar: a=rtpmap:94 telephone-event/8000/1
a=cpar: a=fmtp:94 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:161
a=cpar: a=T38FaxUdpEC:t38UDPRedundancy
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
switches are set to their default values, the SDP becomes:
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=rtcp-xr:voip-metrics
a=mptime:20 -
a=rtpmap:0 PCMU/8000/1
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=X-pc-csuites-rtcp:81/70 81/71 82/70 82/71 80/70
a=sqn: 0
a=cdsc: 1 audio RTP/AVP 0 8 15 18 96 97 98 2 99 101
a=cpar: a=fmtp:18 annexb=no
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:161
a=cpar: a=T38FaxUdpEC:t38UDPRedundancy
Note that this feature affects the SDP, including the Capability Descriptor.
the payload type specified by ppCfgRfc2833DigitPayloadType is added to
the m= line (the default value is ‘‘101’’) and two new attributes indicate that
the endpoint is prepared to receive RFC 2833 digits.
eDVA Feature Touchstone firmware supports an eDVA feature switch that allows you to
Switch enable several features, described below.
The ppCfgMtaFeatureSwitch object is a 32-bit value, where each bit
enables or disables a certain feature. The following values are currently
available:
Bit Value Description
0x00000000 Default behavior.
0x00000001 hashBypass
Disables hash checking of the configuration file during
provisioning. Disabling hash checking may be required
to maintain compatibility with older non-PacketCable
compliant provisioning systems. D11PLUS loads ignore
this setting, and always bypass hash checking.
0x00000002 maxCPEBypass
eDVA MAC addresses are not counted against the Max-
CpeAllowed TLV. This is required to enable telephony
if policy requires this TLV to have a value of 1. Without
this switch setting, you must set the MaxCpeAllowed
TLV to 2 or higher to enable telephony. D11PLUS loads
ignore this setting, and always ignore the eDVA in the
CPE count.
0x00000004 mtaFilterBypass
eDVA packets bypass the CM CPE filters (interface 0).
This switch has no effect on filters applied against inter-
face 16 (eDVA). D11PLUS loads ignore this setting, and
always bypass the CPE filters.
The default eDVA feature switch value is 0, except for D11PLUS loads
which have a default value of 0x06.
Note: If you include eDVA feature switch settings in the configuration, set
the object in the CM configuration file, not the eDVA configuration file.
SIP Feature Switch The SIP feature switch MIB object sipCfgSipFeatureSwitch is a group of
flags that enable or disable extended features in the SIP load. The supported
flags are:
Bit Value Description
0x00000001 Restrict Incoming Offers
Set this bit to restrict incoming OFFERs to only the
CODECs listed in the pktcEUERSTBCallPrefCode-
cList object.
The default value is 0x24c1e188 for .TW loads, and 0 for all other SIP loads.
If the eDVA detects fax/modem tones, and a CODEC other than G.711 is
active, the eDVA 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 eDVA automatically re-enables echo cancellation. but does
not switch back to the original CODEC unless instructed to switch by the
Call Agent. After a modem call completes, the eDVA re-enables echo can-
cellation when instructed by the Call Agent.
Adaptive Jitter Touchstone firmware supports jitter buffers for fax/modem calls. These
Buffers buffers automatically adapt their size to accommodate the required jitter. See
‘‘Configuring Jitter Buffers’’ on page 105 for configuring jitter buffer sizes.
Configuring the The default echo cancellation tail length is 32 ms. Follow these steps to con-
Echo Cancellation figure the desired echo cancellation tail length.
Tail Length 1 In the eDVA configuration file, add the arrisMtaDevEchoCanceller-
TailLength object and set it to eightMs or thirtyTwoMs (default) as
desired.
2 Reset the eDVA.
The eDVA sets the echo cancellation tail as configured, then marks the
MIB read-only.
RFC 2833 (also called DTMF Relay) specifies a method for carrying 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 eDVA signals RFC 2833 support by specifying ‘‘telephone-event’’ in its
list of available CODECs during negotiation. By default, the CMS instructs
the eDVA to enable or disable RFC 2833 and selects the payload type to use.
Touchstone firmware provides feature switches to override the CMS and
enable RFC 2833 support with a specific payload type.
ppCfgRfc2833DigitPayloadType
When bit 0x01000000 is enabled in the CallP Feature Switch, the
eDVA sends RFC 2833 events with the payload type specified by
this object.
Valid range: 97 to 127. Default: 101.
Touchstone firmware supports T.38 fax relay, version 0. T.38 fax relay pro-
vides 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 eDVA 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
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).
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:
CRCX 19901 aaln/[email protected] MGCP 1.0 NCS 1.0
C: 1234
M: recvonly
L: mp:20, a:PCMU, fxr/fx:t38-loose, xrm/mcr:on
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
m=audio 65496 RTP/AVP 0
b=AS:81
a=rtcp-xr:voip-metrics
a=mptime:20
a=rtpmap:0 PCMU/8000/1
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
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, 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
m=audio 58810 RTP/AVP 0
b=AS:81
a=rtcp-xr:voip-metrics
a=ptime:10
a=rtpmap:0 PCMU/8000/1
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=X-pc-csuites-rtcp:81/70 81/71 82/70 82/71 80/70
a=sqn: 0
a=cdsc: 1 audio RTP/AVP 0 8 15 18 96 97 98 2 99 101
a=cpar: a=fmtp:18 annexb=no
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=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:161
a=cpar: a=T38FaxUdpEC:t38UDPRedundancy
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
m=audio 63672 RTP/AVP 0
b=AS:81
a=rtcp-xr:voip-metrics
a=mptime:20
a=rtpmap:0 PCMU/8000/1
a=X-pc-secret:base64:Qb8GFLNXP4Z3yiyxFx1Ws9vLph9qG6bTIXezUlz
rwia7iiNvPPkVYdZhZ77NEQ== zZjgwXRR2j5F04lDXefPTV06PT8g31Hn5V
Ea6NJvFPFsPiraDeDI35EI8KO+4A==
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=cdsc: 1 audio RTP/AVP 0 8 15 18 96 97 98 2 99 127
a=cpar: a=fmtp:18 annexb=no
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=cpar: a=rtpmap:127 telephone-event/8000/1
a=cpar: a=fmtp:127 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:161
a=cpar: a=T38FaxUdpEC:t38UDPRedundancy
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
m=audio 49688 RTP/AVP 0
b=AS:81
a=rtcp-xr:voip-metrics
a=mptime:20
a=rtpmap:0 PCMU/8000/1
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=X-pc-csuites-rtcp:81/70 81/71 82/70 82/71 80/70
a=sqn: 0
a=cdsc: 1 audio RTP/AVP 0 8 15 18 96 97 98 2 99 94
a=cpar: a=fmtp:18 annexb=no
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=cpar: a=rtpmap:94 telephone-event/8000/1
a=cpar: a=fmtp:94 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:161
a=cpar: a=T38FaxUdpEC:t38UDPRedundancy
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
switches are set to their default values, the SDP becomes:
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=rtcp-xr:voip-metrics
a=mptime:20 -
a=rtpmap:0 PCMU/8000/1
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=X-pc-csuites-rtcp:81/70 81/71 82/70 82/71 80/70
a=sqn: 0
a=cdsc: 1 audio RTP/AVP 0 8 15 18 96 97 98 2 99 101
a=cpar: a=fmtp:18 annexb=no
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=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:161
a=cpar: a=T38FaxUdpEC:t38UDPRedundancy
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 or P-CSCFs 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 ‘‘CallP
Feature Switch’’ on page 74.
PacketCable 1.5 Touchstone firmware supports the PacketCable 1.5 NCS Extended Signaling
Extended Signal- MIB fax detection objects for T.38 signaling. The following objects are sup-
ing ported:
pktcEnNcsMinimumDtmfPlayout
The minimum time a digit is played when the eDVA 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
(NCS only) Configures whether the eDVA uses T.38 when detecting
a CNG (calling) tone. The default is disabled, which prevents using
T.38.
arrisMtaDevEndPntFaxOnlyLineTimeout
(NCS only) Configures fax-only mode for a line. Specifies the time,
in seconds, to wait for fax or modem tones after receiving the SDP
from the remote endpoint. If the time expires before detecting fax
or modem tones, the eDVA drops the call. Valid range: 0 to 600.
sipCfgPortFaxOnlyTimeout
(SIP only) Configures fax-only mode for a line. Specifies the time,
in seconds, to wait for fax or modem tones after receiving the SDP
from the remote endpoint. If the time expires before detecting fax
or modem tones, the eDVA drops the call. Valid range: 0 to 600.
sipCfgPortMaxT38HSRedLevel
(SIP only) Sets the maximum high-speed redundancy level used for
T.38 fax relay, in both send and receive directions. The value of this
object is the number of older data packets included in each T.38
datagram when transferring fax data. The actual redundancy level
used is determined by negotiation with the remote endpoint. Valid
range: 0 to 2. Default: 1.
arrisMtaDevT38Timeout
(NCS only) The time, in seconds, that the eDVA waits for the Call
Agent to modify the connection to T.38. The far end receives
silence until the Call Agent modifies the connection.
Controlling T.38 Follow these steps to configure T.38 fax detection and fax-only mode. See
and Fax-Only ‘‘Configuring SIP T.38 and Fax-Only Modes’’ on page 103 for SIP-specific
Modes alternative configuration instructions.
1 Set the pktcEnNcsEndPntFaxDetection object (use the line number
as an index, starting with 1) to configure whether the eDVA detects
CNG (calling) tones and starts T.38 mode.
The default value, false(2), disables detection of CNG tones on the
endpoint. Disabling CNG detection prevents the eDVA from using
T.38 mode, which may be desired when the fax machines are capable
of Super G3 (which uses a higher transmission rate).
Note: If you make this change using an SNMP browser, the new set-
ting takes effect on the next connection.
2 If needed, set the pktcEnNcsMinimumDtmfPlayout object to specify
the minimum time, in milliseconds, that the eDVA plays out a digit
tone when receiving an RFC 2833 digit event on the specified end-
point. The actual play-out time is the maximum of this setting and the
time specified in the RFC 2833 packet.
Valid range: 40 to 100, or 0 (the default), which always uses the time
specified in the RFC 2833 packet.
3 Set fax-only mode by adding the arrisMtaDevEndPntFaxOnlyLine-
Timeout (NCS) or sipCfgPortFaxOnlyTimeout (SIP) MIB object to
the eDVA configuration file. This MIB object is specific to a line, so
it must be specified with the line number; for example, arrisMtaDev-
EndPntFaxOnlyLineTimeout.1 for line 1. The value specifies the
timeout, in seconds, after which the eDVA drops the call if it does not
detect fax or modem tones.
Valid range (either object): 0 (disabled) to 600 seconds. The default is
0.
Configuring T.38 Follow these steps to configure the MaxDatagram size for T.38.
MaxDatagram Size 1 In the eDVA configuration file, set the ppCfgPortT38MaxDatagram
object to the desired datagram size.
Valid range: 160 to 65535 octets. Default: 160.
2 Reset the eDVA to have the new datagram size take effect.
Configuring SIP Follow these steps to configure T.38 and fax-only modes for a line. Each
T.38 and Fax-Only MIB object specified must be set in the eDVA configuration file.
Modes 1 Set the T.38 mode by adding the sipCfgPortT38Mode MIB object to
the eDVA configuration file. This MIB object is specific to a line, so
it must be specified with the line number; for example, sipCfg-
PortT38Mode.2 for line 2.
If you change these MIB objects with an SNMP manager, the new settings
take effect starting with the next phone call.
Setting Standard Follow these steps to set standard jitter buffer parameters.
Jitter Buffer Pa- 1 Set the arrisMtaDevVPJitterBufferMode object to either 1 (adaptive,
rameters the default) or 2 (fixed).
2 Configure the nominal voice call jitter buffer size by setting the
arrisMtaDevVPNomJitterBuffer object. The value represents a mul-
tiple of the packetization rate. Valid range: 1 to 4. Default: 1.
3 Configure the maximum voice call jitter buffer size by setting the
arrisMtaDevVPMaxJitterBuffer object. The value represents a multi-
ple of the packetization rate. Valid range: 1 to 4. Default: 3.
Note: The nominal jitter buffer setting must be less than the maximum
jitter buffer setting.
Setting Voice Follow these steps to enable and configure jitter buffer and override settings
Band Data Jitter for Voice Band Data (fax, modem, POS terminal) calls.
Buffer Parameters 1 Set the arrisMtaDevVbdOverwriteLineBitmap to control jitter buffer
override on each line. The least significant bit controls line 1, so a
value of 3 enables override on lines 1 and 2.
2 Configure the minimum, nominal, and maximum jitter buffer settings
for Voice Band Data calls by setting the following objects. The valid
range for all three objects is 10 to 135; the following table shows the
default value for each object.
Default
Object Description
Value
arrisMtaDevVbdOver- 25 Minimum fax/modem call
writeMinJitterBuffer jitter buffer setting.
arrisMtaDevVbdOver- 25 Nominal fax/modem call
writeNomJitterBuffer jitter buffer setting.
arrisMtaDevVbdOver- 135 Maximum fax/modem
writeMaxJitterBuffer call jitter buffer setting.
Note: The minimum jitter buffer setting must be less than the nominal
setting, which in turn must be less than the maximum jitter buffer set-
ting.
Configuring Cus- Follow these steps to configure custom jitter buffer settings.
tom Jitter Buffer Note: Custom jitter buffer settings use units of milliseconds, rather than
Settings packet multiples used by the standard and VBD methods.
1 Enable custom jitter buffer settings by setting the arrisMtaDevCus-
tomJitterBufferEnabled object to on(1). The default is off(0).
When custom jitter buffer settings are enabled, the default settings
are:
• Minimum: 5 milliseconds
• Nominal: 10 milliseconds
• Maximum: 60 milliseconds
2 Configure the minimum, nominal, and maximum custom jitter buffer
settings by setting the following objects. The valid range for all three
objects is 5 to 135 (milliseconds).
arrisMtaDevCustomMinJitterBuffer
Minimum custom jitter buffer duration.
arrisMtaDevCustomNomJitterBuffer
Nominal custom jitter buffer duration.
arrisMtaDevCustomMaxJitterBuffer
Maximum custom jitter buffer duration.
Configuring Power Follow these steps to configure the power ring frequency.
Ring Frequency 1 Select the pktcSigPowerRingFrequency object and input the appro-
priate frequency for your network. The following frequencies are
valid:
• 20 Hz (1)
• 25 Hz (2) (default for Belgium, Germany, Netherlands, Nether-
lands09, Poland, Spain, Norway, and Switzerland)
• 33.33 Hz (3)
• 50 Hz (4) (default for Austria, France, and Hungary)
• 15 Hz (5)
• 16 Hz (6)
• 22 Hz (7)
• 23 Hz (8)
• 45 Hz (9)
Configuring On- Follow these steps to configure the on-hook Caller ID functionality.
Hook Caller ID 1 Set the protocol by modifying the pktcSigDevCallerIdSigProtocol
object. Supported protocols are fsk(1) (default) and dtmf(2).
2 Select the pktcSigDevCIDMode object and select from one of the fol-
lowing modes:
• lrAsETS—The Line Reversal occurs first, then the Dual Tone Alert
Signal, and finally the FSK is sent but before the first ring pattern.
The delay between the end of the Line Reversal and the start of the
Dual Tone Alert Signal is configurable via the pktcSigDevCID-
DTASAfterLR object.
Note 1: The delay between the Dual Tone Alert Signal and the start of
transmission of the FSK containing the Caller ID information for both
the dtAsETS and lrAsETS Caller ID methods is configurable using
the pktcSigDevCIDFskAfterDTAS object.
Note 2: The delay between the end of the complete transmission of
the FSK containing the Caller ID information and the start of the first
ring pattern for dtAsETS, rpAsETS, and lrAsETS caller ID methods is
configurable via the pktcSigDevCIDRingAfterFSK object.
Configuring Visual Follow these steps to configure visual message waiting indicator.
Message Waiting 1 Select the pktcSigDevVmwiMode object and select from one of the
Indicator following modes:
• dtAsETS (default for Austria, Belgium, France, Germany, Nether-
lands, Netherlands09, Norway, Spain, and Switzerland)—The FSK
is sent after the Dual Tone Alert Signal but before the first ring pat-
tern.
• rpAsETS (default for Hungary)—The FSK is sent after the Ring
Pulse. The delay between the end of the Ring Pulse Alert Signal
and the start of the transmission of the FSK containing the VMWI
information is configurable via the pktcSigDevVmwiFskAfter-
RPAS object.
pktcSigDevVmwiDTASAfterLR object.
Note: The delay between the end of the Dual Tone Alert Signal and
the start of the transmission of the FSK information containing the
VMWI information for the dtAsETS and lrAsETS alerting signal
methods is configurable via the pktcSigDevVmwiFskAfterDTAS
object.
Configuring Tone Touchstone firmware allows configuration of call progress tones for North
Operations American and European templates. See ‘‘Configuring Call Progress Tones’’
on page 111 for instructions.
Configuring Hook Touchstone firmware allows configuration of hook flash timing for North
Flash Timing American and European templates. See ‘‘Configuring Hook Flash Timing’’
on page 123 for instructions.
MIB Tables Touchstone firmware uses two MIB tables to define call progress tones. See
‘‘Default Tone Settings’’ on page 477 for a list of default tone definitions for
each country code type.
pktcSigDevToneTable
Defines the tone type, repeat count, and whether the last tone should
be held steady after completing the cadence. Each entry in the table
contains the following objects:
• pktcSigDevToneType: the index for the table (see below).
• pktcSigDevToneWholeToneRepeatCount: the number of times
to repeat the entire sequence.
• pktcSigDevToneSteady: set to true(1) to keep the last tone in the
sequence on until reaching the timeout.
pktcSigDevMultiFreqToneTable
Defines the actual frequencies for each tone defined in the tone ta-
ble. Each entry in this table contains the following objects:
• pktcSigDevToneNumber: A secondary index, indicating the
sequence number of the defined tone. Up to eight tones may be
defined for a tone type.
• pktcSigDevToneFirstFrequency, pktcSigDevToneSecondFre-
quency, pktcSigDevToneThirdFrequency, pktcSigDevTone-
FourthFrequency: Up to four frequencies per defined tone. To
disable a frequency, set it to 0.
• pktcSigDevToneFreqMode: Determines how the frequencies
define the tone:
– firstModulatedBySecond(1): The first frequency is modulated
by the second frequency, according to the percentage specified
by pktcSigDevToneFreqAmpModePrtg. The third and fourth
frequencies are ignored.
– summation(2): All specified frequencies are added together
without adding modulation.
• pktcSigDevToneFreqAmpModePrtg: The percentage of ampli-
tude modulation to apply when using the firstModulatedBySec-
ond setting.
• userDefined1 (18)
• userDefined2 (19)
• userDefined3 (20)
• userDefined4 (21)
On-Hook vs. Off- Touchstone firmware allows separate gain control for on-hook and off-hook
Hook Gain levels. By default, the standard gain control MIB objects control levels for
both conditions, but setting the "arrisMtaDevLevelControlOffHookEnable"
to enable(1) allows off-hook gain to be configured separately using the arris-
MtaDevLevelControlOffHookCAS and arrisMtaDevLevelControlOffHook-
FSK objects.
arrisMtaDev. . .
LevelControl GainControl
OffHookEnable OffHookFSK OffHookCAS FSK CAS
Controls both Controls both
Disabled Not used Not used on and off on and off
hook gains hook gains
Controls Controls Controls only Controls only
Enabled
off-hook gain off-hook gain on-hook gain on-hook gain
Configuring Gain Follow these steps as necessary to configure gain control settings.
Control using 1 Adjust eDVA-generated on-hook and default off-hook FSK tones
SNMP (CID and VMWI) by setting the arrisMtaDevGainControlFSK
object. Valid range: −10 to 2 (dBm). Default: 0.
2 Adjust the transmit digital gain adjustment for eDVA-generated on-
hook and default off-hook CAS tone by setting the arrisMtaDevGain-
ControlCAS object. Valid range: −2 to 2 (dBm). Default: 0.
3 To set off-hook FSK and CAS tone levels that are different from the
on-hook levels:
CAUTION
Service affecting
Changing the delta Rx/Tx Gain from the default value based on the country
template used may affect overall voice transmission quality, local tone levels,
digit detection, and modem/fax tone detection. PESQ scores may also be
affected when additional loss is introduced.
8 Adjust the transmit digital gain adjustment for voice by setting the
arrisMtaDevGainControlTxVoice object. Valid range: −2 to 2
(dBm). Default: 0.
Note: This setting does not affect local tone or FSK levels.
9 Adjust the receive digital gain adjustment for voice by setting the
arrisMtaDevGainControlRxVoice object. Valid range: −16 to 16
(dBm), or −128 (the default) to use the eDVA-wide setting.
Note: Even though the deltaRx/Tx Gain MIB objects are defined to be
line-based, setting the object for any valid line sets the delta gain for
all lines. Also, if the same delta Rx/Tx Gain object appears multiple
times in the CM configuration file using different indexes, the eDVA
uses the last instance to set the gain.
CAUTION
Potentially service-affecting
Setting endpoint gain too high or too low may disable the voice path. Lower
settings beyond recommended levels may impact voice quality or fax or
modem transmission.
Configuring Gain Follow these steps to adjust gain controls using the CLI.
using the CLI
CAUTION
Service affecting
Changing the Rx/Tx gain from the default value may affect overall voice
transmission quality, local tone levels, digit detection, and modem/fax tone
detection. PESQ scores may also be affected when additional loss is intro-
duced.
value is the gain adjustment, in dBm. The valid range depends on the
tone being adjusted, as shown in the table above.
Preset Frequency The following MIB objects control preset frequencies. You can make
MIB Objects changes to these objects using an SNMP manager or through the configura-
tion file.
arrisCmDevPresetFrequency
Entries in a table of up to 20 preset frequencies.
arrisCmDevClearPresetFrequencies
Set to true(1) to clear the preset frequency table.
arrisCmDevClearCachedFrequencies
Set to true(1) to clear the cached frequencies.
Provisioning Pre- Follow these steps to provision the preset frequency table using an SNMP
set Frequencies manager or in the provisioning file.
using SNMP 1 Set an entry in the table by entering the frequency (in Hz) in one of
the arrisCmDevPresetFrequency objects; for example, use
arrisCmDevPresetFrequency.1 to set the first entry.
4 If you make any changes in the configuration file, reboot the E-UE to
load the changes.
Accessing the Follow these steps to gain access to the Scanning Override screen.
Scanning Override Note: The Scanning Override screen may be accessed only from a LAN
Screen interface before the Telephony Modem has registered (WAN access is not
allowed). If the modem has registered, it redirects attempts to access the
Scanning Override screen to the Status screen.
1 Connect a computer with a web browser to the E-UE, as described in
‘‘Using the Web-based Troubleshooting Interface’’ on page 439.
2 In the browser’s address bar, enter the URL:
http://192.168.100.1/scanover.htm
Specifying a Follow these steps to specify a primary downstream frequency and optional
Downstream Upstream Channel Descriptor (UCD). You can specify up to five frequencies
Frequency to search; if the E-UE does not find a carrier on one of those frequencies, it
begins the normal scanning process at 861 MHz.
1 Use ‘‘Accessing the Scanning Override Screen’’ on page 119 to dis-
play the Scanning Override screen.
2 Type a frequency, in MHz, in the ‘‘Downstream Frequency’’ field.
For example, enter 581 to specify 581 MHz.
3 (optional) Enter a UCD identifier in the Upstream Channel ID field.
4 Click the Save Freq button.
The E-UE stores the specified frequency and UCD (if specified).
The Save Freq action stores the frequency in the cache of the E-UE.
This can be used to pre-provision the cable modem to a specific fre-
quency.
Clearing Stored Follow these steps to clear all stored frequencies. The E-UE returns to the
Frequencies default behavior of scanning the downstream spectrum for a data signal.
1 Use ‘‘Accessing the Scanning Override Screen’’ on page 119 to dis-
play the Scanning Override screen.
2 Click the Clear Now button.
The E-UE clears the stored frequencies.
Action Follow these steps to configure dial pulse support on Touchstone eDVAs.
Note: The arrisMtaDevEndPntDialingMethod object setting is stored in
non-volatile memory when set through SNMP after the eDVA has completed
registration.
1 To enable Gateway (IPDT) dial pulse support, set the arrisMtaDev-
EndPntDialingMethod object to 5 (pulse and DTMF detection).
Gateway Dial The following configuration file provides an example of how to configure
Pulse Example Gateway dial pulse support.
TelephonyConfigFileBeginEnd = 1
SnmpMib = pktcMtaDevEnabled.0 true
SnmpMib = arrisMtaDevEndPntDialingMethod.1 toneAndPulseWithDTMFRelay
SnmpMib = arrisMtaDevEndPntDialingMethod.2 toneAndPulseWithDTMFRelay
SnmpMib = pktcSigDefCallSigTos.0 0
SnmpMib = pktcSigDefMediaStreamTos.0 0
SnmpMib = pktcSigTosFormatSelector.0 ipv4TOSOctet
SnmpMib = pktcMtaDevRealmOrgName.DEV50 "Really Amazing Telephone Company"
SnmpMib = pktcNcsEndPntConfigCallAgentId.9 "[email protected]"
SnmpMib = pktcNcsEndPntConfigCallAgentId.10 "[email protected]"
SnmpMib = pktcNcsEndPntConfigCallAgentUdpPort.9 2727
SnmpMib = pktcNcsEndPntConfigCallAgentUdpPort.10 2727
SnmpMib = pktcMtaDevCmsKerbRealmName.SN05.DEV2 "SWLAB.ATL.ARRIS"
SnmpMib = pktcMtaDevCmsIpsecCtrl.SN05.DEV2 true
SnmpMib = pktcNcsEndPntConfigMWD.9 10
SnmpMib = pktcNcsEndPntConfigMWD.10 10
SnmpMib = pktcMtaDevCmsUnsolicitedKeyNomTimeout.SN05.DEV2 20000
SnmpMib = pktcMtaDevRealmOrgName.SWLAB.ATL.ARRIS "Really Amazing Telephone Company"
TelephonyConfigFileBeginEnd = 255
Default Timing The country code template determines the default minimum and maximum
Settings flash timings, overriding the defaults specified by the PacketCable MIB. See
‘‘Country Code Templates’’ on page 464 for a list of default hook flash tim-
ings for each supported country code.
Ring cadence and ring splash may be provisioned through the PKTC-IETF-
MTA-MIB objects pktcSigDevRgCadence (standard ring), pktcSigDev-
R0Cadence through pktcSigDevR7Cadence (distinctive ringing), and pktc-
SigDevRsCadence (ring splash). These objects consist of the following
fields:
0 59 60 63
repeat
(4 bits)
Post-Provisioning
Touchstone firmware provides the ability to post-provision lines and other
device definitions, allowing you to add or remove service without restarting
the eDVA.
NCS Post-Provi- Touchstone NCS loads are fully compliant with PacketCable eDVA Post-Pro-
sioning visioning functionality, described in section 7.6 of the PacketCable MTA
Device Provisioning Specification , PKT-SP-PROV1.5-I04-090624. You can
post-provision:
• CMS entries
• KDC realms
• Endpoints (lines)
Provisioning a Gateway
Use this procedure to provision a Model 8 Touchstone gateway product.
Gateways provide a built-in Wireless Router Module (WRM) with up to four
Ethernet connections and 802.11b/g/n wireless (wifi) service. The wireless
interface supports up to four SSIDs, one of which is provisionable by the
subscriber.
Model 8 Touchstone Gateway products conform to the eRouter specification,
CM-SP-eRouter-I06-110623.
For detailed business services configuration instructions, see the Business
Service Configuration Feature Sheet for your Touchstone Gateway model.
Provisioning Meth- You can provision the WRM using any of the following methods:
ods • web pages (webGUI) — for details, see the ARRIS Router Setup Web
GUI User Guide.
• SNMP (using the ARRIS-ROUTER-MIB)
• CLI (using the Gateway sub-mode)
• XML (provisioning file using ARRIS-ROUTER-MIB objects)
This procedure focuses on SNMP provisioning.
There is no order of preference among the provisioning methods; the last
change before a commit is the change applied.
Provisioning Gateway provisioning uses the following order of precedence, highest to low-
Precedence est priority:
1 SNMP management
2 web-based interface (subscriber login) — changes persist until the
gateway is reset to factory defaults
3 CM or XML configuration file
If a technician makes a change in the web-based interface, the change applies
only until the gateway restarts.
About IPv6 Opera- IPv6 support is available in TS7.5 and newer versions of Touchstone
tion firmware. The default gateway configuration automatically provides dual-
stack operation, assigning both IPv4 and IPv6 addresses to CPE devices con-
necting through both Ethernet and wifi. Furthermore, the gateway supports
DS-Lite (Dual-Stack lite), allowing customers provisioned with IPv6-only
addresses to access IPv4-only resources over the Internet. DS-Lite encapsu-
lates IPv4 traffic in an IPv6 tunnel, and sends it to an operator’s NAT device.
See below for configuration details.
The gateway can assign IPv6 addresses to CPE devices using either of the
following methods:
• DHCPv6
• Stateless Address Auto-Configuration (SLAAC)
Note: When provisioned for IPv6, the gateway requires an IPv6 address with
a 56-bit prefix, either from DHCPv6 or by static assignment. This is required
for proper CPE device connection.
See below for configuration details.
Setting the Oper- Follow these steps to configure the WRM operating mode.
ating Mode 1 To change pass-through mode, set the arrisRouterLanPassThru
object to true(1) to enable pass-through (bridging) mode or false(2)
for routing mode. Change this object from the CM IP address.
2 To shut down wireless operation, set the arrisRouterWiFiEnableRa-
dio object to false(2).
Configuring the Follow these steps to set a specific channel, or allow the WRM to auto-detect
Wireless Channel and select an unused wireless channel.
1 To set channel auto-detect, set the arrisRouterWiFiChannel object to
0.
Configuring DNS The gateway supports overriding and settting DNS relay. Follow these steps
Override/Relay to configure DNS Override and DNS Relay from SNMP.
1 For routers using IPv4 addressing, set the following MIB objects:
arrisRouterLanRelayDNS
Set to true(1) to enable DNS Relay, or false(2) to disable (the
default). DNS Relay allows the gateway to act as a DNS server,
forwarding DNS requests to actual servers and caching the
results for later use. CPE devices attached to the gateway
receive the gateway address for DNS services, regardless of any
DNS server addresses furnished through DHCP.
arrisRouterLanOverrideDNS
Set to true(1) to enable DNS Override, or false(2) to disable
(the default). DNS Override replaces any DNS information sent
by the DHCP server with the IPv4 addresses in the arrisRouter-
LanDNSTable.
Configuring IPv6 By default, the Gateway uses SLAAC to provide IPv6 addresses to CPE
CPE Addressing devices. If local practices require DHCP, follow these steps to configure the
gateway IPv6 DHCPv6 server.
1 Enable or disable the local DHCPv6 server using the arrisRouter-
LanUseDHCPV6 object. The default value of false(2) disables
DHCPv6 services, using SLAAC to assign IPv6 addresses.
2 If using DHCPv6, configure the service using the following objects:
arrisRouterLanPrefixLengthV6
The length, in bits, of the subnet prefix. The valid range for
IPv6 addressing is 64 to 128.
arrisRouterLanStartDHCPV6
The start of the IP address range provided by the DHCPv6
server.
arrisRouterLanEndDHCPV6
The end of the IP address range provided by the DHCPv6
server.
arrisRouterLanLeaseTimeV6
The lease time, in seconds.
arrisRouterDSLiteWanLSNATAddrType
The address type of the LSNAT router; either ipv6(2) to specify
an IPv6 address, or dns(16) to specify the FQDN.
arrisRouterDSLiteWanLSNATAddr
The IPv6 address, or FQDN, of the LSNAT server.
Provisioning Gateway provisioning uses the following order of precedence, highest to low-
Precedence est priority:
1 SNMP management
2 web-based interface (subscriber login) — changes persist until the
gateway is reset to factory defaults
3 CM or XML configuration file
If a technician makes a change in the web-based interface, the change applies
only until the gateway restarts.
XML File Format An XML provisioning file has a top-level element named <mib>, that con-
tains any number of elements using the name of MIB objects in the arris-
RouterMib. The index attribute may be used to configure multiple table
entries. The default index value is 0.
The following is a very simple example, that changes only the timeout for
logins to the WebGUI.
<?xml version="1.0" encoding="us-ascii" ?>
<mib>
<arrisRouterAdminTimeout index="0">900</arrisRouterAdminTimeout>
</mib>
Action Follow these steps to provision the router using an XML file.
1 To activate XML router provisioning, set the arrisRouterXmlProvi-
sioningFile object to the URL describing the location and name of
the provisioning file. The protocol may be either tftp:// or
http:// as needed.
If the file name is omitted, the default file name is the gateway MAC
address with a .xml extension. The gateway downloads the configu-
ration file after completing the DHCP sequence.
2 To check the result of XML provisioning, read the arrisRouterXml-
ProvisioningStatus object. Possible values returned include:
notSpecified(1)
XML provisioning was not enabled or has not begun.
inProgress(2)
The gateway is downloading the XML provisioning file.
downloadSuccess(3)
The gateway has successfully downloaded the XML provision-
ing file.
serverError(4)
The TFTP or HTTP server returned an error.
fileNotFound(5)
The TFTP or HTTP server returned a ‘‘file not found’’ error.
fileFormatError(6)
The gateway detected an error in the XML provisioning file.
Note: If the gateway successfully performs XML provisioning, it
stores a copy of the provisioning file. If a later provisioning attempt
fails, the gateway uses the copy to apply provisioning.
3 To manually start XML provisioning, set the arrisRouterXmlProvi-
sioningStatus object to downloadFromMgt(7).
TR-069 Provisioning
Enabling TR-069 To enable TR-069 support, set the arrisTR69EnableCWMP object to true(1)
Support in the CM configuration file. The default is false(2).
TS7.5 supports most objects in the InternetGatewayDevice group. See
‘‘Supported TR-098 Objects’’ on page 262 for a list. See the TR-098 specifi-
cation for available objects and their descriptions.
Example Configuration
The following is an example configuration file segment.
{VendorSpecific
{VendorID 0000ca}
{TR69AcsInfo
{Tr69AcsUrl https://ttmacs.example.net:8048/service/cwmp}
{Tr69AcsUserName incognito}
{Tr69AcsPassword incognitoo}
{Tr69CrURL http://10.1.38.9:15627/acscall}
{Tr69CrUserName username}
{Tr69CrPassword password}
{Tr69AcsPerInfEnable 1}
{Tr69AcsPerInfInterval 180}
{Tr69AcsXAllowDocsCfg 0}
}
}
TR69AcsInfo Sub- The following define the sub-TLVs in the TR69AcsInfo group.
TLV Formal Defini-
tions
Tr69AcsUrl
TR69AcsUserName
The string defines the user ID for logging into the ACS server.
TR69AcsPassword
The string defines the password for logging into the ACS server.
TR69CrUserName
The string defines the user name for the ACS when using the Connection
Request mechanism to the Gateway.
TR69CrPassword
The string defines the password for the ACS when using the Connection
Request mechanism to the Gateway.
TR69AcsPerInfEnable
Enables or disables Periodic Inform. When enabled, the CPE sends periodic
status information to the ACS using an inform method.
TR69AcsPerInfInterval
The time, in seconds, that the CPE must attempt to connect to the ACS to
send a Periodic Inform.
TR69AcsXAllowDocsCfg
TR69CrURL
The URL to the Gateway that the ACS uses for a Connection Request. The
URL must be specified as: http://gatewayIP:15627/acscall
Terminology PacketCable 2.0 introduces new terminology and abbreviations for telephony
components within a network. The following table shows PacketCable 1.x
terms with their equivalent PacketCable 2.0 terms.
This document uses the terms E-UE for the entire Telephony Modem, eDVA
for the telephony portion, and CM for the cable modem portion.
Configuration Provisioning an eDVA conforms to the following model. Note that TS7.5
Concepts uses a simplified version of the PacketCable 2.0 model, and the simplified
version is shown as follows:
IMPI.2
IMPI.1
AppMap.1 AppMap.2
OrgID: 4491 OrgID: 4491
AppID: 1 (RST) AppID: 1 (RST)
Operator
The operator indirectly associates users with a P-CSCF. Multiple
operators could be associated with various third-party telephony
providers or with remote locations in the MSO’s network. TS7.5
supports one operator definition.
User
A user consists of two components:
• IMPU (IP Multimedia Public User) — the public identity of the
user. This could be the phone number assigned to the user, or
some other unique user name. The IMPU associates a user with a
phone line through the pktcEUEUsrIMPUAdditionalInfo object.
Multiple users may share a line, implementing a Teen Line ser-
vice or as part of a transition to a new area code or exchange.
• IMPI (IP Multimedia Private Identity) — the private identity of
the user. Primarily, the IMPI defines the credentials for the
IMPU.
Application
Defines the service(s) to be provided to a user. TS7.5 supports only
the Residential SIP Telephony (RST) application. The application
map defines the application and selects a profile.
Profile
Selects a digit map and an associated collection of features. A pro-
file may be applied to one or more users.
Feature
Defines capabilities and dialing features available to a profile. Fea-
tures include basic call functionality (including timer durations),
announcements, Caller ID display, and common dialing features.
Each feature is defined as an entry in one or more tables, allowing
profiles to contain different feature configurations. User-based fea-
tures are indexed normally; network-based features (or network-
based components of features) use the Operator index.
The following restrictions apply:
• Touchstone firmware supports only one P-CSCF (but can fail over to a
second P-CSCF) and only one operator per E-UE.
• Touchstone firmware supports only the PacketCable Residential SIP
Telephony (RST) application.
• Multiple users can be assigned to a line, but a user can be associated
only with one line.
Each box in the above figure is associated with a table in the PacketCable 2.0
MIBs. Arrows represent an index to a row in each table, connected with
another table. The boxes labeled IMPU and IMPI are contiguous since
TS7.5 requires them to be permanently associated.
Supported Fea- The following table shows which RST feature MIB tables are supported in
tures TS7.5.
MIB Table Support
RST Feature
Network User
Basic Call Partial Partial
Announcement Partial No
Activation Status n/a Partial
No Answer Timeout n/a Partial
CallerID n/a Partial
CallerID Display n/a Partial
CallerID Block n/a No
CallerID Delivery n/a No
Call Forward No Partial
Call Hold n/a No
Call Transfer n/a No
Do Not Disturb n/a No
MWI Partial n/a
Auto Recall n/a No
Auto Callback n/a No
Busy Line Verify No n/a
Emergency Services Partial n/a
Selective Call Forward n/a No
For details about partially supported feature tables, see the ‘‘Compliance’’
chapter of the Touchstone Telephony Feature Guide.
Barge-In The Join: header (RFC 3911) may used to barge-in to an existing call. A
brief tone is played to the existing call as the calls are conferenced together.
Loopback The SIP eDVA can terminate loopback calls. When a loopback call is
received, the phone does not ring. It automatically answers the call and loops
back media or packets to the originator. The eDVA has a 2 call per line
resource limitation. The user may make a call or receive a call while a loop-
back call is in progress. If another call is placed, either by an incoming call
or a new outbound call, the loopback call is disconnected.
Origination Mode
Termination Mode
When the eDVA receives the BYE signal, it starts a 20-second timer. If the
timer expires before the subscriber hangs up, the eDVA invokes the ‘‘perma-
nent sequence.’’
Permanent Sequence
Emergency Calls Any number matching the pattern associated with the digit map action
EMERGENCY-CALL is treated as an emergency call. Emergency calls have
special treatment. The subscriber is, by default, not allowed to terminate an
emergency call(this can be overridden by setting the sipCfgSipFea-
tureSwitch bit 0x00000100). If the user goes on hook, and the default
behavior is in effect, the eDVA does not send a BYE message. Instead, the
call is put on ‘‘Network Hold’’ as follows:
1 When the subscriber goes on-hook during an emergency call, the
Touchstone eDVA sends an INVITE (priority:emergency SDP:a=inac-
tive). This causes the PSAP operator to hear a tone that indicates that
the user went on-hook.
2 The PSAP operator can send an INVITE (priority:emergency
SDP:a=sendrecv) that causes the eDVA to ring. If the user goes off-
hook before receiving such an INVITE, then it should send the invite
to re-establish two-way communications.
3 The Network Hold Timer specifies the maximum time that an emer-
gency call is preserved in the Network Hold state. The timer is started
every time that the user goes on-hook during an emergency call, and is
cleared if the user goes off hook. If the Network Hold Timer expires,
then the eDVA sends a BYE message to finally terminate the call.
The default value for the Network Hold Timer is 45 minutes.
Distinctive Ring- Several distinctive ringing types, corresponding to R0 through R7, are
ing defined by the country template. If the Alert-Info: header is received,
Touchstone firmware compares the header to the strings specified in the MIB
objects sipCfgAlertInfoR0 through sipCfgAlertInfoR7. If the header
matches one of these, the eDVA plays the corresponding R0–R7 tone. TS7.5
also supports tones WT1 through WT4 for use with Call Waiting, and maps
R1 through R4 to WT1 through WT4 for a Call Waiting alert.
The following configuration shows the default string settings.
{SnmpMib sipCfgAlertInfoR0.0 "< http://127.0.0.1/Bellcore-dr0 >"}
{SnmpMib sipCfgAlertInfoR1.0 "< http://127.0.0.1/Bellcore-dr1 >"}
{SnmpMib sipCfgAlertInfoR2.0 "< http://127.0.0.1/Bellcore-dr2 >"}
{SnmpMib sipCfgAlertInfoR3.0 "< http://127.0.0.1/Bellcore-dr3 >"}
{SnmpMib sipCfgAlertInfoR4.0 "< http://127.0.0.1/Bellcore-dr4 >"}
{SnmpMib sipCfgAlertInfoR5.0 "< http://127.0.0.1/Bellcore-dr5 >"}
{SnmpMib sipCfgAlertInfoR6.0 "< http://127.0.0.1/Bellcore-dr6 >"}
{SnmpMib sipCfgAlertInfoR7.0 "< http://127.0.0.1/Bellcore-dr7 >"}
Configuration The most efficient way to configure PacketCable 2.0 SIP is to use a ‘‘top-
Overview down/bottom-up’’ approach, building and interlinking the MIB tables in the
following order:
1 Operator table
2 P-CSCF table
3 Feature and Digit Map tables
4 Profile to Feature tables
5 Application Map tables
6 IMPI table
7 IMPU table
See ‘‘PacketCable 2.0 Concepts’’ on page 137 for an overview of how the
tables interconnect.
Configuring Oper- Operator information includes the Operator and P-CSCF tables. Follow
ator Information these steps:
1 Configure the Operator table. The index for each object is typically 1;
this index is used in other tables to refer to this Operator table.
a Set the pktcEUEDevOpDomain object to the domain name; for
example, atl.ga.example.com.
b Set the pktcEUERSTKeepAlive object to set the in-service/out-
of-service status:
Configuring Users Follow these steps to configure user and feature tables:
and Features 1 To configure features, proceed to ‘‘Provisioning PacketCable 2.0 Fea-
tures’’ on page 148.
2 To configure user information, proceed to ‘‘Provisioning PacketCable
2.0 Users’’ on page 163.
3 To configure application profiles, proceed to ‘‘Provisioning PacketCa-
ble 2.0 Application Profiles’’ on page 165. Digit map configuration is
described in ‘‘Configuring PacketCable 2.0 Digit Maps’’ on page 155.
4 To configure the Application Map, proceed to ‘‘Provisioning Packet-
Cable 2.0 Application Maps’’ on page 166.
Post-Provisioning Follow these steps to change the provisioning status of one or more lines
SIP Lines without rebooting the eDVA.
Note: This task applies only to line-level parameters.
The following MIB objects require a restart of the SIP stack and are not
updated by this feature:
• sipCfgGenLinger
• sipCfgTimerF
1 Create a configuration file containing the line-level parameters to
change, and make the file available for download on a reachable TFTP
server.
2 Using an SNMP network manager, set the arrisMtaDevSipConfig-
FileURL object to the URL of the configuration file.
The eDVA downloads the configuration file and applies the line-level
changes. Touchstone firmware does not take lines out of service or
interrupt calls in process.
4 To make the configuration changes permanent, modify the standard
configuration file to reflect the changes.
Note: If the post-provisioning changes are not copied to the standard
configuration file, the eDVA loses those changes when re-initialized.
Configuring T.38 Configuring T.38 and fax operation is identical for both PC20 and ARRIS
and Fax-Only SIP loads. See ‘‘Configuring T.38 and Fax-Only Modes’’ on page 201 for
Modes details.
Feature Support In PacketCable 2.0, a ‘‘feature’’ includes anything that can be enabled or con-
figured. If all features are disabled, the eDVA can receive incoming calls and
make only emergency outgoing calls. By default, all features are disabled.
All features are defined and enabled in the pktcEUERSTAppProfileToFeat-
Table. Some features may be further configured as follows:
digit map
In addition to defining valid phone numbers, the digit map defines
Vertical Service Codes used to invoke or control dialing features.
Network table
Network tables are associated with an operator table, and control
provisioning associated with all users. Not all features have net-
work tables.
User table
User tables are associated with individual users, and control provi-
sioning for that user. Not all features have user tables.
The pktcEUERSTAppFeatID object specifies a feature type. The following
are valid features:
• digitMap(2) — A digit map that enables the supported features.
• basicCall(3) — Basic Call capabilities. The user-side table defines the
CODECs available; the network-side table defines timers and the off-
hook alert sequence.
• announcement(4) — Announcements. The Announcement Map table
defines tones to play when the eDVA receives various response codes
(such as ‘‘486 Busy’’).
• statusChange(5) — UE Status Change. This feature defines the mini-
mum registration expiration interval.
• noAnsTimeout(6) — Defines how long the eDVA rings a line before
sending a ‘‘480 Temporarily Unavailable’’ response to the originator.
• callerId(7) — Sets the preferred presentation status (anonymous or
public) on Caller ID for outgoing calls.
• callerIdDisplay(8) — Controls the display of Caller ID information for
incoming calls.
P-CSCF Dialing In TS7.5, any dialing features not supported by the digit map are treated as P-
Features CSCF dialing features. To enable a P-CSCF dialing feature, map the P-
CSCF-defined dialing code to the MAKE-CALL action, passing the dialing
code to the P-CSCF.
Example:
"*99" : MAKE-CALL ( "sip:" #0 =domain =dialString )
The P-CSCF must instruct the eDVA to play stutter tone or provide other
confirmation, if necessary.
Basic Call Config- Follow these steps to configure a basic call feature.
uration 1 Configure the user-side table, pktcEUERSTBasicCallTable, as fol-
lows:
pktcEUERSTBCallPrefCodecList
(optional) A comma-delimited list of the CODECs sent in the
SDP. If left unconfigured, the eDVA offers G.711.
Note: For backward-compatibility with earlier versions of
Touchstone firmware, this object also accepts a semicolon-
delimited list supported by the now-deprecated sipCfgProvi-
sionedCodecArray object.
pktcEUERSTBCallStatus
Set to createAndGo(4).
2 (optional) Configure the network-side table, pktcEUERSTNfBasic-
CallTable, as follows. The index is .oper.x, where oper is the index
of the entry in the Operator table. All the values in this table have rea-
sonable defaults.
pktcEUERSTNfBCallByeDelay
The Bye delay, in seconds. When set to a non-zero value, a
called party can hang up the phone then pick up before the timer
expires without ending the call.
pktcEUERSTNfBCallPermSeqTone1
The URI specifying the first tone in the permanent sequence.
See ‘‘Permanent Sequence’’ on page 172 for details and
defaults.
pktcEUERSTNfBCallPermSeqTimer1
The duration of the first tone in the permanent sequence.
pktcEUERSTNfBCallPermSeqTone2
The URI specifying the second tone in the permanent sequence.
pktcEUERSTNfBCallPermSeqTimer2
The duration of the second tone in the permanent sequence.
pktcEUERSTNfBCallPermSeqTone3
The URI specifying the third tone in the permanent sequence.
pktcEUERSTNfBCallPermSeqTimer3
The duration of the third tone in the permanent sequence.
pktcEUERSTNfBCallPermSeqTone4
The URI specifying the last tone in the permanent sequence.
pktcEUERSTNfBCallPermSeqTimer4
The duration of the last tone in the permanent sequence.
pktcEUERSTNFBCallOrigModLongIntDig
The long interdigit timer, in seconds. If you configure the ‘‘L’’
timer in the digit map, do not set this object.
pktcEUERSTNfBCallStatus
Set to createAndGo(4). Setting only this object creates an
entry with reasonable default values.
Configuring the In TS7.5, Status Change is used to periodically re-register with the network.
Status Change One entry in the pktcEUERSTUEActStatChgTable is supported in TS7.5
Feature and applies to the entire eDVA.
Follow these steps to configure the Status Change entry.
1 Set the pktcEUERSTUEActStatChgRegExp object to the desired
registration expiration time, in seconds.
2 Set the pktcEUERSTUEActStatChgStatus object to create-
AndGo(4).
Configuring No Follow these steps to configure the No Answer timeout feature. This feature
Answer Timeout allows the eDVA to disconnect a call if the called party does not answer
before the timer expires.
1 Set the pktcEUERSTNoAnsTODuration object to the desired No
Answer timeout, in seconds.
Configuring Caller Configuring Caller ID requires setup of several tables. Follow these steps to
ID configure Caller ID.
1 Set up the user’s presentation by creating an entry in the pktcEUER-
STCIDTable with the following values:
pktcEUERSTCIDPPS
Set the presentation status to public(2).
pktcEUERSTCIDStatus
Set to createAndGo(4).
2 Set up the display feature by creating an entry in the pktcEUERST-
CIDDisTable with the following values:
pktcEUERSTCIDDisDefCountry
Enter the country code data, to be stripped from the display
information sent to the subscriber’s CPE. For example, the US
country code is 1.
pktcEUERSTCIDDisTimeAdj
The adjustment, in minutes, from UTC.
pktcEUERSTCIDDisDSTFlag
Set to 1 to adjust for Daylight Savings Time, or 0 to ignore DST.
pktcEUERSTCIDDisDSTInfo
To use the above two objects for adjusting the time, set this to an
empty string. Otherwise, set to a POSIX timezone string as
defined in RFC 4833. If you set this object, the eDVA ignores
the above two objects.
pktcEUERSTCIDDisCIDCWActStat
Set to true(1) to disable CID-CW.
Note: You can disable CID-CW for the entire eDVA by setting
bit 0x02000000 of the SIP Feature Switch sipCfgSipFea-
tureSwitch.
pktcEUERSTCIDDisStatus
Set to createAndGo(4).
Configuring Emer- Follow these steps to configure emergency services. See ‘‘Emergency Calls’’
gency Services on page 173 for an overview of emergency call processing.
1 Add a rule to the digit map to associate a dial string with emergency
calls. For example:
"911" : EMERGENCY-CALL ("sip:" "911" =domain =Emergencytg )
Configuring Dis- Setting Alert-Info strings for distinctive ringing and alert (Call Waiting) tones
tinctive Ring/Alert is identical for both PC20 and ARRIS SIP loads. See ‘‘Configuring Distinc-
Tones tive Ring/Alert Tones’’ on page 202 for details.
Default: 16 seconds.
symbol definitions
A symbol is a string constant, used to define common pattern or
action strings and to make rules more human-readable. An example
symbol definition is:
LocalNumber = [2-9]x{6}
map definitions
maps consist of a series of rules defined as:
pattern : action
Patterns are completely defined in the Residential SIP Telephony
Feature Specification. The following list describes the more com-
mon components of a pattern.
• Numbers 0 through 9, and the * and # symbols, represent standard
keypad keys. The characters ‘‘x’’ and ‘‘X’’ represent a single
numeric keypress.
• S, T, L, and Z represent the defined timers. Of these, the Z timer
must precede a keypress.
• An = sign followed by a name represents a defined symbol.
Example: =LocalNumber
• Square brackets enclosing a series of keys, such as [2345],
match any single keypress in that series. A range of numeric keys
may be represented using a hyphen, so [2-5] is equivalent to
[2345]. The character ‘‘x’’ or ‘‘X’’ is equivalent to [0-9]. If
the first character in the series is a caret (ˆ), then the series
matches a keypress not represented — for example, [ˆ01*#] is
equivalent to [2-9].
• A keypress (or a series enclosed in square brackets) followed by a
number or range in curly brackets, such as x{6}, matches when
the specified number (or some number within the range) of
matching keys are pressed. For example, 1x{2-4}# matches
1xx#, 1xxx#, or 1xxxx#.
• All or part of a pattern may be enclosed in parentheses to specify
a sub-pattern. A sub-pattern may be used in an action, as
described below.
• Two slashes (//) indicate that the rest of the line is a comment.
Actions, like patterns, are completely defined in the Residential SIP Tele-
phony Feature Specification. An action consists of a command, followed by
a parameter string enclosed in parentheses. Multiple actions can be specified,
and are separated by a semicolon (;). TS7.5 supports the following com-
mands in actions:
• MAKE-CALL (uri) — URI representing the specified destination (usu-
ally a phone, but could include dialing codes handled in the network)
• CID-DELIVER (string) — send the specified Caller ID information
• CID-SUPPRESS (string) — do not send Caller ID information
TS7.5 Compliance TS7.5 generally conforms to PacketCable 2.0 specifications for digit maps,
with PacketCa- with the following exceptions:
ble 2.0 • The Start Timer ‘‘T’’ is supported, with a default value of 16 seconds,
and can be changed in the digit map. However, its behavior is hard-
coded to play reorder tone, equivalent to defining the rule ‘‘T’’ :
REORDER in the digit map. Configuring this timer in the digit map is
deprecated; use the pktcEUERSTNfBCallOrigDTTimer object to set
this timer.
• The Long Interdigit Timer ‘‘L’’ can be defined but is not supported in
rules. However, if the Short Interdigit Timer ‘‘S’’ is not defined, the
‘‘L’’ timer definition is applied to rules where ‘‘S’’ is specified. Config-
uring this timer in the digit map is deprecated; use the pktcEUERSTNF-
BCallOrigModLongIntDig object to set this timer.
Note: In TS7.5, a single digit map applies to all lines in the E-UE.
TIMER L=16 // Long interdigit timer. The allowable time between digits
// the digit map.
TIMER Z=2.0 // Long duration timer. The duration a particular digit is
// Symbols
domain = "@tel.example.com"
areaCode = "303"
dialString = ";user=dialstring" // Just to shorten things
homeEmergencyNumber = "911"
localEmergencyNumber = "911" // alternate emergency number
lcltg = ";tgid=Local_trunk-group-id"
ldtg = ";tgid=Long_Distance_trunk-group-id"
intltg = ";tgid=International-trunk-group-id"
Emergencytg = ";tgid=911PSAP-trunk-group-id"
Opertg = ";tgid=Local_Operator-trunk-group-id"
ldcic = ";cic=0333"
intlcic = ";cic=8937"
TollFreecic = ";cic=0110"
// Maps
MAP MainTable = // This is where processing starts
"T" : REORDER // Reorder Tone or Annc.
"0S" : MAKE-CALL ("sip:0" =domain =Opertg)
"0#" : MAKE-CALL ("sip:0" =domain =Opertg)
"00" : MAKE-CALL ("sip:0" =ldcic =domain =ldtg)
"(=Emergency)" : EMERGENCY-CALL ("sip:" "911" =domain =Emergencytg )
// map N11 to routing number or reorder if not assigned
"211" : MAKE-CALL ("sip:" "+13035551111" =domain =lcltg)
"311" : MAKE-CALL ("sip:" "+13035552222" =domain =lcltg)
"411" : MAKE-CALL ("sip:" "411" =domain =Opertg)
"511" : REORDER // Reorder Tone
"611" : MAKE-CALL ("sip:" "+13035552224" =domain =lcltg)
"711" : MAKE-CALL ("sip:" "+18885552225" =TollFreecic =domain =lcltg)
pktcEUEUsrIMPIId
The user’s login information used to authenticate the eDVA to
the headend.
pktcEUEUsrIMPICredsType
The type of credentials used to confirm the private identity.
Only password(3) is supported in TS7.5 and is the default.
pktcEUEUsrIMPICredentials
The user’s password. Reading this object always returns an
empty string.
pktcEUEUsrIMPIRowStatus
Set to createAndGo(4).
Note: In most cases, a single IMPI table entry is associated with all
public users.
2 Configure an IMPU table entry in the eDVA configuration file. Set
the objects in this entry as follows:
pktcEUEUsrIMPUIdType
(optional) The public user identification type. Both publicIden-
tity(3) (the default) and userName(6) are supported in TS7.5.
pktcEUEUsrIMPUId
The public user identification. The content of this object
depends on the value of pktcEUEUsrIMPUIdType:
• publicIdentity(3): phonenumber@domain
• userName(6): phonenumber (Touchstone firmware adds the
default domain to the phone number to create the full public
identity)
pktcEUEUsrIMPUIMPIIndexRef
The index into the pktcEUEUsrIMPITable, specifying the IMPI
entry associated with the public user.
pktcEUEUsrIMPUDispInfo
The display name in SIP messages, associated with Caller ID
name delivery.
pktcEUEUsrIMPUOpIndexRefs
The index into the pktcEUEDevOpTable, specifying the opera-
tor entry associated with the public user. In TS7.5, this is usu-
ally 1 since only one operator entry is supported.
pktcEUEUsrIMPUAdminStat
(optional) Accept the default of active(1) to enable the line.
pktcEUEUsrIMPUAdditionalInfo
If only one public user is associated with a phone line, the eDVA
automatically maps the first user to line 1 and the second user to
line 2. For multiple phone numbers associated with a line, as is
the case with a Teen Line service or an NPA or exchange transi-
tion, set this object as follows:
IEP#line;OEP#line
The line is the ifIndex for the line (usually 9 for line 1 and so
on), and must be same for both IEP (Input EndPoint) and OEP
(Output EndPoint).
pktcEUEUsrIMPURowStatus
Set to createAndGo(4).
Action Follow these steps to provision an Application Profile. The profile must be
provisioned in the eDVA configuration file.
1 Set the pktcEUERSTAppFeatID to the feature type being specified.
See ‘‘Provisioning PacketCable 2.0 Features’’ on page 148 for a list of
valid feature types.
2 Set the pktcEUERSTAppFeatIndexRef object to the index of an entry
in the pktcEUERSTAppProfileToFeatTable. This specifies the fea-
ture definition to use.
3 (optional) Set the pktcEUERSTAppAdminStat object to active (the
default) to activate this feature, or inactive to disable this feature.
4 Set the pktcEUERSTAppStatus to createAndGo(4).
Indexing The pktcEUEUsrAppMapTable uses a dual index for each entry: .user.map,
where user index is the index of the IMPU entry that this map is associated
with; the map is the application index (usually 1 since TS7.5 supports only
the PacketCable RST application).
Action Follow these steps to provision an application map. You must add these
objects to the eDVA configuration file.
1 Set the pktcEUEUsrAppMapAppOrgID object to the enterprise num-
ber of the organization defining the application: always 4491 for
PacketCable.
2 Set the pktcEUEUsrAppMapAppIdentifier object to the application:
always 1 for Residential SIP Telephony (RST).
3 Set the pktcEUEUsrAppMapAppIndexRef object to the index of the
entry in the pktcEUERSTAppProfileToFeatTable corresponding to
the profile associated with this map.
4 (optional) Set the pktcEUEUsrAppMapAppAdminStat object to
active (default) to enable the application for this user, or inactive to
disable the application.
5 Set the pktcEUEUsrAppMapRowStatus object to createAndGo(4).
Priority The eDVA follows these steps to determine which tone to play when receiv-
ing a failure response.
1 If the (sipCfgSipFeatureSwitch) object has the playBusyToneOn-
Reject(0x00000400) bit set, the eDVA always plays busy tone.
Playing Busy Tone To override PacketCable 2.0 behavior and play busy tone for all failure
for All Errors responses, follow these steps.
1 Set the 0x00000400 bit of the sipCfgSipFeatureSwitch in the eDVA
configuration file.
2 Restart the eDVA to make the change take effect.
Configuring Indi- Follow these steps to configure a tone to play for a specific failure response.
vidual Response 1 For each response code, set the pktcEUERSTNfAncMapURI object,
Tones either in an SNMP manager or in the eDVA configuration file. This
object must be indexed by both the domain entry (TS7.5 allows only
one domain per E-UE) and the response code; for example,
pktcEUERSTNfAncMapRspCode.1.404, and contain the URI of the
PacketCable-defined tone to play. For example:
{pktcEUERSTNfAncMapRspCode.1.404 "file:///PacketCableRST/bz"}
The following failure codes are supported:
• 404, 406, 408
• 480, 484, 486, 487
• 500, 503, 504
• 600, 603
Note: A URI sent in the Error-Info header of the failure response
takes precedence over these settings.
2 If using an SNMP manager, set the pktcEUERSTNfAncMapStatus
object, indexed by the same domain and response code, to create-
AndGo(4). Otherwise, restart the eDVA to make the change take
effect.
3 To remove an entry, set the pktcEUERSTNfAncMapStatus object,
indexed by the same domain and response code, to destroy(6).
Note: Attempting to remove the entry for response codes 486, 487, or
600 resets the entry to its default value.
Clearing MWI Indi- It may be necessary to clear MWI indicators in response to a subscriber trou-
cators ble call. Follow these steps to clear the indicators.
1 Set the sipCfgPortMWIClear.line object to true(1). The line is the
line number for which the indicators should be cleared; use 1 for
line 1, and so on.
2 Repeat step 1 for each line that needs to be cleared.
Provisioning the By default, the eDVA subscribes to the P-CSCF MWI package (message-
MWI Subscription summary). Follow these steps to provision the eDVA to subscribe to a differ-
ent server’s MWI package.
1 Set the sipCfgMWITargetAddrType object to ipv4(1). TS7.5 sup-
ports only IPv4 for the E-UE.
2 Set the sipCfgMWITargetAddr object to the IP address of the device
that the eDVA should subscribe the MWI package to.
3 (optional) Set the sipCfgMWITargetPort object to the port number of
the MWI service. The default is 5060.
4 To recommend a subscription duration, set the pktcEUERST-
NfMWISubDuration object to the recommended time before the sub-
scription expires.
Valid range: 0 to 4000000 seconds. Default: 3600.
Barge-In The Join: header (RFC 3911) may used to barge-in to an existing call. A
brief tone is played to the existing call as the calls are conferenced together.
Loopback The SIP eDVA can terminate loopback calls. When a loopback call is
received, the phone does not ring. It automatically answers the call and loops
back media or packets to the originator. The eDVA has a 2 call per line
resource limitation. The user may make a call or receive a call while a loop-
back call is in progress. If another call is placed, either by an incoming call
or a new outbound call, the loopback call is disconnected.
Packet Loopback is analogous to NETWLOOP, and controlled by the
sipCfgPacketLoopbackNumber object. Media Loopback is analogous to
NETWTEST, and controlled by the sipCfgMediaLoopbackNumber object.
Origination Mode
Termination Mode
When the eDVA receives the BYE signal, it starts a 20-second timer. If the
timer expires before the subscriber hangs up, the eDVA invokes the ‘‘perma-
nent sequence.’’
Permanent Sequence
Other loads:
1 OSI for 1 second
2 Silence for 10 seconds
3 Howler tone for 60 seconds
If the subscriber has not hung up the phone by the time the sequence ends,
the line enters a lockout state until the subscriber hangs up.
The following table shows the MIB objects used to provision the permanent
sequence and the default values for each object.
Object TW Loads Other Loads
pktcEUERSTNfBCallPermSeqTone1 "file:///PacketCableRST/ro" "file:///PacketCableRST/osi"
pktcEUERSTNfBCallPermSeqTimer1 30 1
pktcEUERSTNfBCallPermSeqTone2 "file:///PacketCableRST/osi" "file:///PacketCableRST/nt"
pktcEUERSTNfBCallPermSeqTimer2 1 10
pktcEUERSTNfBCallPermSeqTone3 "file:///PacketCableRST/nt" "file:///PacketCableRST/ot"
pktcEUERSTNfBCallPermSeqTimer3 4 60
pktcEUERSTNfBCallPermSeqTone4 "file:///PacketCableRST/ot" ""
pktcEUERSTNfBCallPermSeqTimer4 60 0
Emergency Calls Any number matching the pattern associated with the digit map action
EMERGENCY-CALL is treated as an emergency call. Emergency calls have
special treatment. The subscriber is, by default, not allowed to terminate an
emergency call(this can be overridden by setting the sipCfgSipFea-
tureSwitch bit 0x00000100). If the user goes on hook, and the default
behavior is in effect, the eDVA does not send a BYE message. Instead, the
call is put on ‘‘Network Hold’’ as follows:
1 When the subscriber goes on-hook during an emergency call, the
Touchstone eDVA sends an INVITE (priority:emergency SDP:a=inac-
tive). This causes the PSAP operator to hear a tone that indicates that
the user went on-hook.
2 The PSAP operator can send an INVITE (priority:emergency
SDP:a=sendrecv) that causes the eDVA to ring. If the user goes off-
hook before receiving such an INVITE, then it should send the invite
to re-establish two-way communications.
3 The Network Hold Timer specifies the maximum time that an emer-
gency call is preserved in the Network Hold state. The timer is started
every time that the user goes on-hook during an emergency call, and is
cleared if the user goes off hook. If the Network Hold Timer expires,
then the eDVA sends a BYE message to finally terminate the call.
The default value for the Network Hold Timer is 45 minutes.
Distinctive Ring- Several distinctive ringing types, corresponding to R0 through R7, are
ing defined by the country template. If the Alert-Info: header is received,
Touchstone firmware compares the header to the strings specified in the MIB
objects sipCfgAlertInfoR0 through sipCfgAlertInfoR7. If the header
matches one of these, the eDVA plays the corresponding R0–R7 tone. TS7.5
also supports tones WT1 through WT4 for use with Call Waiting, and maps
R1 through R4 to WT1 through WT4 for a Call Waiting alert.
The following configuration shows the default string settings.
{SnmpMib sipCfgAlertInfoR0.0 "< http://127.0.0.1/Bellcore-dr0 >"}
{SnmpMib sipCfgAlertInfoR1.0 "< http://127.0.0.1/Bellcore-dr1 >"}
{SnmpMib sipCfgAlertInfoR2.0 "< http://127.0.0.1/Bellcore-dr2 >"}
{SnmpMib sipCfgAlertInfoR3.0 "< http://127.0.0.1/Bellcore-dr3 >"}
{SnmpMib sipCfgAlertInfoR4.0 "< http://127.0.0.1/Bellcore-dr4 >"}
{SnmpMib sipCfgAlertInfoR5.0 "< http://127.0.0.1/Bellcore-dr5 >"}
{SnmpMib sipCfgAlertInfoR6.0 "< http://127.0.0.1/Bellcore-dr6 >"}
{SnmpMib sipCfgAlertInfoR7.0 "< http://127.0.0.1/Bellcore-dr7 >"}
Information Re- The SIP load requires three pieces of information to function properly:
quired for SIP Outbound P-CSCF
The destination device for all outbound messages. The setting is
used as the domain in the Request-URI for all outgoing INVITE
messages. The E-UE supports a ‘‘global’’ proxy that applies to all
lines, and a per-line proxy that applies to a single line. See ‘‘Con-
figuring Per-Line Proxy and Registrar’’ on page 194 for details.
Registrar
Registration messages are sent to the outbound proxy’s IP address,
but the Request-URI address is provisioned as the registrar address.
This setting may or may not be the same as the outbound proxy set-
ting. The E-UE supports a ‘‘global’’ registrar that applies to all
lines, and a per-line registrar that applies to a single line. See ‘‘Con-
figuring Per-Line Proxy and Registrar’’ on page 194 for details.
Domain Settings
The domain is set as part of the DHCP process of the Telephony
Modem using DHCP Option 15. This domain is used in all to and
from URIs that the Telephony Modem generates.
The following are examples of REGISTER and INVITE messages with the
following provisioning when bit 0x04000000 of the SIP Feature Switch is
not set (bit value = 0):
Domain arris-i.org
sipCfgProxyAdr ser.arris-i.org;5060
sipCfgRegistrarAdr registrar.arris-i.org;5060
User-id (phone #) 7705552001
Called Number 7705552002
REGISTER sip:registrar.arris-i.org:5060 SIP/2.0
From: "SIP1 Line1"<sip:[email protected]>;
tag=94b73228-a013d16-13c4-20-21829ddd-20
To: "SIP1 Line1"<sip:[email protected]>
Call-ID: 94b6e3b0-a013d16-13c4-20-22ce4f5-20
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 10.1.61.22:5060;branch=z9hG4bK-20-7ed6-6787cc6b
Allow: INVITE,ACK,BYE,CANCEL,NOTIFY
Max-Forwards: 70
Contact: "SIP1 Line1"<sip:[email protected]:5060>
Content-Length: 0
INVITE sip:[email protected]:5060 SIP/2.0
From: "SIP1 Line1"<sip:[email protected]>;
tag=94b73808-a013d16-13c4-62-4e4a1883-62
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 1 INVITE
Via: SIP/2.0/UDP 10.1.61.22:5060;branch=z9hG4bK-62-180b5-631cc050
Allow: INVITE,ACK,BYE,CANCEL,NOTIFY
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
Content-Type: application/SDP
Content-Length: 168
<SDP REMOVED>
SIP Registration All SIP Touchstone firmware loads use the same algorithm for normal regis-
Behavior tration and re-registration:
• Registration begins after a randomized wait time between 1 and
(MaxWaitDelay) seconds. The default for MaxWaitDelay is 10 min-
utes; the pktcNcsEndPntConfigMWD object controls the delay time
(in seconds). Note that line 1 uses index 9, line 2 uses index 10, and so
on.
• By default, the registrar sends the registration in the 200 OK response
to a REGISTER request. The sipCfgRegExpires object can specify a
suggestion to the registrar for a desired registration expiry value. If the
specified value is non-zero, the eDVA uses the smaller of the expiry
value returned by the registrar in the 200 OK or the value specified in
sipCfgRegExpires. If sipCfgRegExpires is unconfigured or specified
to zero, no expires value is specified in the REGISTER request.
• After registration, the eDVA attempts to re-register after a random time
between 50% and 75% of the expiration time.
• If registration is unsuccessful (for example, the eDVA receives no
response or a 401 response), the eDVA retries registration using a back-
off algorithm at intervals specified by RFC 3261.
The backoff algorithm is exponential. The initial backoff starts at the value
specified by sipCfgRegTimerMin (default: 60 seconds). The interval
between retry attempts doubles until it is greater than the value specified by
sipCfgRegTimerMax (default: 1800 seconds). The interval between retries
is not to exceed the value specified by sipCfgRegTimerMax. The eDVA
uses the following formula to calculate the delay:
time = min( TimerMax, (TimerMin × 2ˆ(#failures-1)) )
The default values are 60 and 1800 seconds, and can be changed by specify-
ing new values in the eDVA configuration file.
Each REGISTER attempt is not a single message. The eDVA will retry
REGISTER messages based on the retransmission algorithm specified in
RFC 3261. By default, the eDVA retries 7 times over a 32-second interval.
The retransmission algorithm is also exponential. The basis interval is speci-
fied by T1 (sipCfgT1). The total time to retransmit is specified by TimerF
(sipCfgTimerF).
SIP Feature Switch The SIP feature switch enables or disables extended features in the SIP load.
See ‘‘SIP Feature Switch’’ on page 85 for a detailed description of each
switch.
Provisioning This section describes various SIP features that can be configured in the pro-
Details visioning file.
Digit Map
Proxy Address
The proxy address specifies the destination where the eDVA sends all SIP
requests. You must also specify the proxy type, IP or DNS.
{SnmpMib sipCfgProxyAdr.0 "ser.arris-i.org;5060"}
{SnmpMib sipCfgProxyType.0 dns}
Registrar Address
The registrar address specifies the text of the top line of the REGISTER
request.
{SnmpMib sipCfgRegistrarAdr.0 "registrar.arris-i.org;5060"}
{SnmpMib sipCfgRegistrarType.0 dns}
Loopback
The following MIB objects allow incoming calls to be looped back to the
originator. A match is done on the incoming call and compared to the strings
below to determine which type of loopback occurs.
{SnmpMib sipCfgMediaLoopbackNumber.0 "7705558001"}
{SnmpMib sipCfgPacketLoopbackNumber.0 "7705558002"}
Packetization Rate
Repeat Dialing
There are certain phone numbers (eg. 911) that Call Forwarding should not
accept as forwarding numbers. The sipCfgCallForwardForbiddenNumbers
MIB object specifies which numbers are not allowed as forwarding numbers.
This object can be set only in the configuration file. Multiple numbers may
be specified separated by | as follows:
{SnmpMib sipCfgCallForwardForbiddenNumbers.0 "911|900|1900|0"}
To clear this setting, to re-locate the MTA to another customer that may have
a different preference or for some other reason, use the sipCfgResetCall-
WaitingStarCode MIB object to clear the NVM setting. The MIB object
controls the setting of this value on a per-line basis, using a bit string to indi-
cate which lines should be reset.
# reset lines 1 and 2
{SnmpMib sipCfgResetCallWaitingStarCode.0 0x00000003}
Default G.711
When using G.729 as the primary voice CODEC, the eDVA must switch to a
G.711 CODEC to support faxes transmission. Touchstone firmware switches
to PCMU in this situation by default. Some customers require PCMA as the
pass-through CODEC.
Use the sipCfgDefaultG711 MIB object to specify a different pass-through
CODEC, as follows:
{SnmpMIb sipCfgDefaultG711.0 pcma}
Domain Override
Emergency Calls
The end user is never allowed to terminate an emergency call. If the user
goes on hook, the eDVA does not send a BYE message. Instead, the call is
put on "Network Hold" as follows:
1 When the end user goes on-hook during an emergency call, the
Touchstone eDVA sends an INVITE (priority:emergency SDP:a=inac-
tive). This causes the PSAP operator to hear a tone that indicates that
the user went on-hook.
2 The PSAP operator can send an INVITE (prioirty:emergency
SDP:a=sendrecv) that causes the eDVA to ring. If the user goes off-
hook before receiving such an INVITE, then it should send the invite
to re-establish two-way communications.
3 The Network Hold Timer specifies the maximum time that an emer-
gency call is preserved in the Network Hold state. The timer is started
every time that the user goes on-hook during an emergency call, and is
cleared if the user goes off hook. If the Network Hold Timer expires,
then the eDVA sends a BYE message to finally terminate the call.
The default value for the Network Hold Timer is 45 minutes.
See PKT-SP-RSTF-I08-110127 section 8.5.5.8 for more details on
Network Hold for Emergency Calls, including call flows for various
Network Hold scenarios.
Pulse Dialing
Example:
{SnmpMib sipCfgPortFeatureSettings.1 02}
Distinctive Ringing
Dialing Features
Proxy features are sent directly to the proxy in an INVITE message. No con-
figuration is necessary to handle these features. The proxy itself defines what
feature is associated with a particular dialing code.
Call Transfer
Uses the target dialog (RFC 4538) if supported by far-end; otherwise, sends
REFER on the existing Call Leg.
In most cases, call transfer is initiated by the pivot phone going on hook.
This triggers a transfer if Call Transfer is enabled, and the call is in one of the
threeWayCalling, callingHolding, or conference states. When advanced
flash digit handling is enabled, call transfer can be initiated by the 4 digit.
The transfer is performed by the pivot phone. The pivot phone sends a
REFER message to the original call. This REFER message includes a
ReferTo: header which notifies the party being transferred who to contact.
Embedded in the ReferTo: header is a Replaces: header (RFC 3891). The
party receiving the REFER message then sends an INVITE to the party refer-
enced in the ReferTo: header. The Replaces: header is then copied to its own
header in this INVITE. The party receiving the INVITE with the Replaces:
header uses this header to determine which call to disconnect and replace
with the transferred party.
Feature Capabilities
Ten MIB objects allow control of certain features on a per-line basis. The
objects follow a naming convention of sipCfgfeatCapability, where feat is
the specific feature. Each MIB object consists of a hexadecimal bit string (32
bits wide) where each bit is a flag corresponding to a different line. These
objects can be only set in the configuration file.
When a feature capability of a particular line is set to zero (off), that feature
is disabled for that line regardless of the value of any other MIB object,
including sipCfgFeatureSettings. By default, all feature capabilities are
enabled for every line; all ten MIB objects default to the hex value
FFFFFFFF (which is a string of 32 ones). When a feature is enabled, the
user may still enable or disable the feature using dial codes. However, if the
feature capability is disabled in the configuration file, the dial code to enable
that feature does not work.
The following table lists the controllable features and the corresponding MIB
object controlling its capability:
Feature MIB Object
Caller ID Display sipCfgCallerIdDisplayCapability
Caller ID Send sipCfgCallerIdSendCapability
Anonymous Call Rejection sipCfgAnonCallRejectionCapability
Call Waiting sipCfgCallWaitingCapability
Three Way Calling sipCfgThreeWayCallCapability
Call Transfer sipCfgCallTransferCapability
Call Forwarding sipCfgCallForwardCapability
Call Return sipCfgCallReturnCapability
Call Redial sipCfgCallRedialCapability
Call Holding sipCfgCallHoldCapability
Examples:
To disable three-way calling for lines 1 and 3, add the following line to the
configuration file:
{SnmpMib sipCfgThreeWayCallCapability.0 FFFFFFFA}
Note: For an 8- or 12-line Telephony Modem, this is identical to setting the
value to 00000FFA because only the 12 least significant bits are used.
To disable three-way calling for all lines on a Telephony Modem, modify the
setting as follows:
{SnmpMib sipCfgThreeWayCallCapability.0 00000000}
To enable three-way calls for all lines, delete any settings for sipCfgThree-
WayCallCapability from the configuration file and reset the modem.
For any of these changes to take effect, the modem needs to be reset to down-
load the updated configuration file.
Timers
Minimal Example The following configuration file fragment provides a minimal example of SIP
configuration.
set mcns_config_params {
{TelephonyConfigFileBeginEnd 1}
# eDVA Enabled
{SnmpMib pktcMtaDevEnabled.0 1}
# Proxy Address
{SnmpMib sipCfgProxyAdr.0 "ser.arris-i.org;5060"}
{SnmpMib sipCfgProxyType.0 1}
# Phone Number
{SnmpMib sipCfgPortUserName.1 7705558001}
# Caller-ID Display
{SnmpMib sipCfgPortDisplayName.1 "David Line1"}
# Line 1 Enabled
{SnmpMib ifAdminStatus.9 1 }
# Phone Number
{SnmpMib sipCfgPortUserName.2 7705558002}
# Caller-ID Display
{SnmpMib sipCfgPortDisplayName.2 "David Line2"}
# Line 2 Enabled
{SnmpMib ifAdminStatus.10 1 }
{TelephonyConfigFileBeginEnd 255}
}
Per-Line The following table describes MIB objects for per-line proxy/registrar sup-
Proxy/Registrar port. These objects must be set in the configuration file to be effective. For
Objects details about the SIP registration process, see ‘‘SIP Registration Behavior’’
on page 177.
MIB Object
Description (Per-line)
Global Per-line
sipCfgRegistrarAdr sipCfgPortRegistrarAdr Registrar Server
sipCfgPortRegistrarPort Registrar Server port. The per-line set-
ting is only valid if paired with a setting
for sipCfgPortRegistrarAdr.
sipCfgRegistrarType sipCfgPortRegistrarType The type of address specified by the
sipCfgPortRegistrarAdr object. It is
only valid if paired with a setting for
sipCfgPortRegistrarAdr. When both
objects are defined in the configuration
file, this value overrides the setting in
the sipCfgRegistrarType for this line.
Valid values for this setting are ipv4(0)
and dns(1).
sipCfgProxyAdr sipCfgPortProxyAdr Proxy Server address
sipCfgPortProxyPort Proxy Server port. It is only valid if
paired with a setting for sipCfgPort-
ProxyAdr.
sipCfgProxyType sipCfgPortProxyType The type of address specified by the
sipCfgPortProxyAdr object. It is only
valid if paired with a setting for sipCfg-
PortProxyAdr. When both objects are
defined in the configuration file, this
value overrides the setting in sipCfg-
ProxyType for this line. Valid values
for this setting are ipv4(0) and dns(1).
Use the line number as the index for each object; for example, sipCfgPort-
ProxyAdr.2 specifies the proxy IP address for line 2.
T.38 Provisioning The MIB object sipCfgPortT38Mode controls T.38 behavior. It allows the
Overview following values:
Value Description
t38Off(1) (default) Disables T.38.
t38Loose(2) Enables T.38 Loose mode. In loose mode, the
eDVA can use T.38 for fax transmission whether
or not the remote endpoint has indicated T.38
support.
t38Strict(3) Enables T.38 Strict mode. In strict mode, the
eDVA can use T.38 for fax transmission only if
the far end indicated support for T.38 during ses-
sion negotiation.
Global Call Fea- The sipCfgPortFeatureSettings object allows you to control operation of
ture Control the following call features:
• outbound Caller ID
• anonymous call rejection
• call waiting
• three-way calling
The sipCfgPortFeatureSettings object is structured as a collection of bit
flags, as shown in the following table. The default value is 0.
Bit Description
0x40 callerIdPermanentDisable
Set this bit to set the default outbound Caller ID method to
‘‘restrictive.’’ The default setting presents Caller ID.
0x20 anonCallRejectionEnable
Set this bit to enable anonymous call rejection. The subscriber
can use a ‘‘star’’ code to disable anonymous call rejection if
desired. The default setting permits anonymous calls.
0x10 callWaitingPermanentDisable
Set this bit to disable Call Waiting. The subscriber can use a
‘‘star’’ code to enable Call Waiting if desired. The default set-
ting is to enable Call Waiting.
0x08 threeWayCallingDisable
Set this bit to disable hook flash processing during an active call.
The default setting is to allow hook flash processing.
0x04 callIdReceiptDisable
Set this bit to disable local CallerID display.
0x02 callTransferEnable
Set this bit to enable Call Transfer. The bit can only be set in the
configuration file.
Per-line Call Fea- Ten MIB objects provide per-line control over common calling features,
ture Control allowing subscribers to order each feature separately. Each object is a map of
32 bits; the least significant bit represents line 1. Setting a bit to 0 disables
the corresponding feature for that line.
These MIB objects must be set in the eDVA configuration file, and are not
persistent across reboots. The default value for all these objects is
0xFFFFFFFF (feature enabled on all lines).
Each Telephony Modem ignores bits beyond its line capacity. For example,
on a TM702 Telephony Modem, 0x00000003 is equivalent to 0xFFFFFFFF.
CM Configuration Follow these steps to modify the cable modem configuration file for SIP sup-
File Changes port.
1 Modify the PcIpClassification MIB. The Classification for
Upstream and Downstream packets should be set up with a different
port number to indicate the correct SIP source port(s). PcIpSource-
PortStart and PcIpSourcePortEnd should be set to 5060 in both
UpstreamPacketClassification and DownstreamPacketClassifi-
cation.
eDVA Configura- Follow these steps to enable SIP support in the eDVA configuration file.
tion File Changes 1 Modify the ppCfgMtaCallpFeatureSwitch object. To use QoS for a
SIP eDVA load, the value of the feature switch must be set to 0x4020
or decimal 16416. If these bits are not set in the feature switch, the
eDVA transmits RTP packets using Best Effort. Other QoS-specific
settings may be needed depending on the CMTS (and its firmware
load) used.
10 To define a ‘‘busy’’ digit map (that is, in effect when busy tone is
playing), specify the map using the sipCfgBusyDigitMap object. The
digit map format is the same as for the default digit map, and can be
set only in the configuration file.
11 If desired, modify the digit map timers:
• Tpar (partial dial time-out)—modify the pktcNcsEndPntConfigPar-
tialDialTO object. The default is 16 seconds.
Setting up Timers Touchstone firmware provides MIB objects for controlling the registration
and retransmission (T1) timers. These objects must be set in the eDVA con-
figuration file.
Note: The default values for these objects correspond to RFC 3261 guide-
lines.
1 To configure the registration wait time, set the sipCfgRegTimerMin
and sipCfgRegTimerMax objects to the desired minimum and maxi-
mum wait times.
The defaults for these objects are 0 and 1800 seconds, respectively.
At startup, an eDVA waits for a random amount of time (bounded by
these objects) before beginning registration.
2 To change the T1 timer value, in milliseconds, set the sipCfgT1
object. T1 is the base interval for the exponential back-off algorithm,
used for retransmitting INVITE messages.
Default: 500 (ms).
3 To change the number of transmission attempts for outgoing INVITE
messages, set the sipCfgMaxRetrans object. The default is 7.
The defaults for this object and sipCfgT1 provide the following
retransmission timing:
a Initial INVITE (0 s)
b First retransmission (0.5 s) (500 ms delay)
c Second retransmission (1.5 s) (1 s delay)
d Third retransmission (3.5 s) (2 s delay)
e Fourth retransmission (7.5 s) (4 s delay)
f Fifth retransmission (15.5 s) (8 s delay)
g Sixth (final) retransmission (31.5 s) (16 s delay)
4 To specify a preferred session expiry timeout value, set the
sipCfgSessionExpires object to the desired value (in seconds).
When this object is set, the Telephony Modem configures the SIP
INVITE message depending on the value of the object:
Value INVITE Behavior
0 No Session-Expires header included.
1–89 The Session-Expires header includes a value of
1800.
90+ The Session-Expires header includes the value speci-
fied in the object.
Configuring Per- Follow these steps to provision per-line proxy and registrar. Each MIB
Line Proxy and object specified must be set in the eDVA configuration file. These objects
Registrar override the default proxy and registrar settings, so any line that does not
specify per-line MIB objects uses the default proxy and registrar.
1 Override the default proxy address, port, and address type by setting
the sipCfgPortProxyAdr, sipCfgPortProxyPort, and sipCfgPort-
ProxyType objects in the eDVA configuration file; for example:
• ipaddr and port is the IP address and port number of the SIP regis-
trar;
• type is the IP address type (0 for IPv4 and 1 for DNS).
3 Restart the eDVA to make the per-line proxy/registrar settings take
effect.
Specifying a SIP Follow these steps to specify a SIP domain name other than the domain spec-
Domain Name ified in the proxy or provisioned FQDN.
1 Add the sipCfgDomainOverride object to the configuration file. This
object must contain the desired domain name.
Note: When this object is set, the eDVA ignores the ‘‘Domain Over-
ride" SIP Feature Switch setting.
2 Restart the eDVA to download and apply the updated configuration.
Requirements and To provision SIP features, you must first modify the CM and eDVA configu-
Limitations ration files as described in ‘‘Provisioning SIP Support’’ on page 187.
You can provision up to 50 dialing features and up to 50 proxy dialing fea-
tures in the eDVA configuration file.
Proxy Dialing Some dialing features require the eDVA to handle the tones, but the proxy
Features handles the actual messaging. These are known as hybrid features. Five
MIB objects control the setup and requirements for hybrid dialing features.
The index number of each object groups the objects by dialing feature.
These objects replace the sipCfgDialProxyMap object supported in loads
prior to TS5.2.
sipCfgDialProxyNumber
The dialing feature number. See the table below for dialing feature
values.
sipCfgDialProxyCode
A string containing the dialing code that activates the feature (for
example, ‘‘*88’’).
sipCfgDialProxyTone
The response tone; either stutterTone(1) or dialTone(2).
sipCfgDialProxyActive
A 32-bit string that identifies which lines enable the dialing feature.
The least significant bit corresponds to line 1; for example, the value
3 activates the dialing feature on lines 1 and 2.
sipCfgDialProxyMessageType
For a proxy-based dialing feature, determines the type of message
sent to the proxy: invite(1) or refer(2). Most dialing features should
use invite(1).
sipCfgDialProxyMethod
(optional) Determines how the dialing code is passed to the proxy:
default(0) prepends the dialing code to the dial string; pc20(1)
sends the dialing code to the proxy as the host of the SIP URI and
the dial string in a user parameter in the SIP URI.
Value Feature
callReDial(60) Call Redial
callHold(61) Call Hold
repeatDialingEnable(62) Enable Repeat Dialing
repeatDialingCancel(63) Cancel Repeat Dialing
callWaitTempDisable(70) Call Waiting Temp Disable (CALWD)
callWaitPermDisableToggle(71) Call Waiting Permanent Disable Toggle (CLWPD)
callWaitPermanentDisable(72) Call Waiting Permanent Disable
callWaitPermanentEnable(73) Call Waiting Permanent Enable
callerIDPermBlockToggle(90) Caller ID Permanent Block Toggle (CIDPB)
callerIDTempEnable(91) Caller ID Temp Enable (CIDTE)
callerIDTempBlock(92) Caller ID Temp Block (CIDTB)
Setting up Dialing Add the MIB objects described below to the eDVA configuration file to set
Features up dialing features. The sipCfgDialFeatMap MIB object, provided in earlier
loads, is supported for backwards compatibility but no longer documented.
The MIB objects for each feature are distinguished by the index; for exam-
ple, sipCfgDialFeatName.1 and sipCfgDialFeatName.2 are two different
features.
Note: Certain dialing features, including Hotline, Warmline, and Repeat Dial-
ing, require further configuration. See the appropriate task for any extended
configuration required.
1 Add the sipCfgDialFeatName object to enable particular dialing fea-
tures. See ‘‘Supported Dialing Features’’ on page 197 for a list of
supported features.
2 Add the sipCfgDialFeatCode object to define a dialing code for a
particular feature. You can specify up to three codes, separated by a
comma, for each feature. For example, use *70,1170 to allow either
*70 or 1170 to activate a feature.
Configuring The SIP load includes support for specifying a hotline or warmline number in
Warmline or the configuration file. A hotline automatically dials the specified number as
Hotline soon as the specified line goes off-hook; a warmline automatically dials the
specified number after providing dial tone for a specified amount of time.
Add the objects described below to the eDVA configuration file to set up a
hotline or warmline for a specific line.
1 In the configuration file, set the sipCfgPortWarmOrHotlineNumber
object to the phone number to dial. This object is specific to a line, so
it must be specified with the line number; for example,
sipCfgPortWarmOrHotlineNumber.2 for line 2.
Configuring Follow these steps to configure the Repeat Dialing feature. Configuring any
Repeat Dialing busy indication dialing feature uses the same steps.
1 Add two entries to the sipCfgDialFeatTable in the eDVA configura-
tion file, to set up and cancel Repeat Dialing. The following example
enables Repeat Dialing when the subscriber presses *5 during a busy
signal, and cancels Repeat Dialing with #5:
/* enable Repeat Dialing */
{SnmpMib sipCfgDialFeatName.1 Integer 62}
{SnmpMib sipCfgDialFeatCode.1 String "*5"}
{SnmpMib sipCfgDialFeatTone.1 Integer 1} /* stutter */
{SnmpMib sipCfgDialFeatActive.1 HexString 0x00000003}
{SnmpMib sipCfgDialFeatMode.1 Integer 2} /* busy mode only */
sipCfgRepeatDialingTimeout
The time, in seconds, that Repeat Dialing is active (and unsuc-
cessful) before the eDVA cancels the feature. Default: 1800 sec-
onds.
sipCfgRepeatDialingSessionProgressTimer
The time, in seconds, the eDVA waits after receiving a ‘‘183
Session Progress’’ provisional response before alerting the sub-
scriber. This delay is needed because many PSTN calls receive
this response before receiving a negative INVITE. Default: 2
seconds.
Note: This object must be set in the configuration file. Changes
made to this object persist across reboots.
4 Reset the eDVA to enable the feature.
Configuring T.38 Follow these steps to configure T.38 and fax-only modes for a line. Each
and Fax-Only MIB object specified must be set in the eDVA configuration file.
Modes 1 Set the T.38 mode by adding the sipCfgPortT38Mode MIB object to
the eDVA configuration file. This MIB object is specific to a line, so
it must be specified with the line number; for example, sipCfg-
PortT38Mode.2 for line 2.
Configuring Dis- Follow these steps to set the expected Alert-Info strings for distinctive ring-
tinctive Ring/Alert ing and alert (Call Waiting) tones. Each MIB object specified must be set in
Tones the eDVA configuration file. For more information, see ‘‘Distinctive Ring-
ing’’ on page 174.
1 In the eDVA configuration file, set the following MIB objects:
MIB Object Description
sipCfgAlertInfoR0 The value of the Alert-Info header field to
instruct the eDVA to play the R0 ring
cadence.
sipCfgAlertInfoR1 The value of the Alert-Info header field to
instruct the eDVA to play either the R1 ring
cadence (call not active) or the WT1 call
waiting tone (call active).
sipCfgAlertInfoR2 The value of the Alert-Info header field to
instruct the eDVA to play either the R2 ring
cadence (call not active) or the WT2 call
waiting tone (call active).
sipCfgAlertInfoR3 The value of the Alert-Info header field to
instruct the eDVA to play either the R3 ring
cadence (call not active) or the WT3 call
waiting tone (call active).
sipCfgAlertInfoR4 The value of the Alert-Info header field to
instruct the eDVA to play either the R4 ring
cadence (call not active) or the WT4 call
waiting tone (call active).
sipCfgAlertInfoR5 The value of the Alert-Info header field to
instruct the eDVA to play the R5 ring
cadence.
sipCfgAlertInfoR6 The value of the Alert-Info header field to
instruct the eDVA to play the R6 ring
cadence.
sipCfgAlertInfoR7 The value of the Alert-Info header field to
instruct the eDVA to play the R7 ring
cadence.
Battery Management
Initial Battery When the E-UE is powered up, whether for the first time or after replacing a
Charging battery, it begins a battery charging and testing sequence. See the Touchstone
Battery Reference Manual for details about the charging and testing
sequence.
Boot from Battery Touchstone E-UEs support a Boot from Battery feature, allowing an E-UE to
begin service without AC power.
To start an E-UE from a battery, follow these steps:
1 If a battery is installed in the E-UE, remove it.
2 Install the battery into the E-UE.
3 Press the Reset button on the back of the E-UE 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
Power Failure When an E-UE with battery backup capabilities loses AC power, it immedi-
Operation ately takes the following actions:
1 Shuts off some LEDs to conserve battery power.
2 Disables the ability to download new firmware until the AC power is
restored. This prevents corrupting the E-UE’s firmware load in case
the battery fails before the E-UE could complete the download.
3 Shuts down the data services running over all LAN ports after the
time specified by the arrisMtaDevPwrSupplyDataShutdownTime
object. The default time is 5 minutes for TG852 Telephony Gateways,
and 15 minutes for other models. To disable data shutdown alto-
gether, set the arrisMtaDevPwrSupplyEnableDataShutdown object
to disabled(2).
4 After the shutdown timer expires, Model 8 E-UEs disable bonded
mode, switching to 1x1 unbonded (see ‘‘Model 8 Power Manage-
ment’’ on page 269 for details).
The Battery LED only flashes when AC power is not present and the battery
is low, or else when the battery needs to be replaced. The Battery LED does
not flash during normal charging.
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 Status Touchstone firmware provides battery status monitoring through SNMP. Bat-
Monitoring tery MIB objects provide an estimate of remaining battery charge as a per-
centage of full charge, and in minutes remaining to depletion.
E-UEs have battery charger hardware that reports an accurate estimate of bat-
tery capacity within 5 minutes of initialization.
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.
Highest Charger Touchstone firmware provides a feature to record and report the historic high
Temperature charger temperature. These MIB objects are available only when the arris-
Recording MtaDevPwrSupplyOverTempAlarmControl 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 E-UE recorded the high tempera-
ture.
arrisMtaDevPwrSupplyHighestTemperatureClear
Resets the highest temperature and time data.
IPv6 allows cable operators to expand their IP address ranges for cable
modems, allowing reclamation of traditional IPv4 addresses for use with
eDVAs. TS7.5 supports the following IPv6-related protocols:
• DHCPv6
• DNSv6
• TFTPv6
• TODv6
• SNMPv6
• TELNETv6
• HTTPv6
• SSHv6
Note: Touchstone firmware does not support Early Authentication and
Encryption (EAE) functionality.
Supported Hard- Touchstone firmware supports single- and dual-stack CPE traffic on all
ware Model 8 Touchstone devices as follows:
CM provisioned and managed in IPv6 mode:
• supports single stack IPv4 traffic to and from CPEs.
• supports single stack IPv6 traffic to and from CPEs.
• supports IPv4 and IPv6 traffic simultaneously to and from CPEs.
CM provisioned and managed in IPv4 mode:
supports IPv4 and IPv6 traffic simultaneously to and from CPEs.
TS7.5 and newer versions of Touchstone firmware support IPv6 operation on
all Model 8 Data Gateway and Telephony Gateway products.
Note: IPv6 operation is supported only on the cable modem (CM) and
eRouter components of Touchstone products. The eDVA component sup-
ports only IPv4 operation.
Before Registration
The CM:
• filters multicast traffic not addressed to the IPv6 Link Local Scope All
Nodes Address or the Solicited Node Addresses.
• learns the pre-registration DSID from the MDD message.
• forwards pre-registration multicast traffic to its IP stack based on the
pre-registration DSID as defined in the ‘‘DSID based Filtering and For-
warding by a Cable Modem’’ section of CM-SP-
MULPIv3.0-I12-100115.
During Registration
After Registration
The CM:
• stops forwarding multicast traffic labeled with the Pre-Registration
DSID, after receiving the REG-RSP message.
• forwards multicast traffic based on the DSIDs and Group MAC
Addresses received in the REG-RSP message, as specified by the
‘‘DSID based Filtering and Forwarding by a Cable Modem’’ section of
CM-SP-MULPIv3.0-I12-100115.
• filters multicast traffic based on DSIDs and Group MAC Addresses
received in the REG-RSP message. The CMTS always includes the
IPv6 Link Local Scope All Nodes Address, and the CMâs Solicited
Node Addresses, in the REG-RSP message.
• supports Multicast DSID Encodings (TLV 50.4) described in the ‘‘Mul-
ticast Encodings’’ section of CM-SP-MULPIv3.0-I12-100115, as well
as Security Association Encodings (TLV 51) described in the ‘‘Security
Association Encoding’’ section of CM-SP-MULPIv3.0-I12-100115,
received in the REG-RSP message.
IPv6 Management
MLD Snooping
Coexistence TS7.5 supports SNMPv6 co-existence for both the ARRIS version of coexis-
tence and coexistence using the coexistence MIBs.
The following is an example provisioning file fragment for setting up co-
existence.
SnmpMib = snmpCommunityStatus.rocablelabs createAndGo
SnmpMib = snmpCommunityName.rocablelabs "ro_cm"
SnmpMib = snmpCommunitySecurityName.rocablelabs "rotesting1"
SnmpMib = snmpCommunityStorageType.rocablelabs volatile
SnmpMib = snmpCommunityStatus.rwcablelabs createAndGo
SnmpMib = snmpCommunityName.rwcablelabs "rw_cm"
SnmpMib = snmpCommunitySecurityName.rwcablelabs "rwtesting1"
SnmpMib = snmpCommunityStorageType.rwcablelabs volatile
SnmpMib = vacmSecurityToGroupStatus.1 rotesting1 createAndGo
SnmpMib = vacmGroupName.1 rotesting1 "rotesting2"
SnmpMib = vacmSecurityToGroupStorageType.1 rotesting1 volatile
SnmpMib = vacmSecurityToGroupStatus.1 rwtesting1 createAndGo
SnmpMib = vacmGroupName.1 rwtesting1 "rwtesting2"
SnmpMib = vacmSecurityToGroupStorageType.1 rwtesting1 volatile
SnmpMib = vacmSecurityToGroupStatus.2 rotesting1 createAndGo
SnmpMib = vacmGroupName.2 rotesting1 "rotesting2"
SnmpMib = vacmSecurityToGroupStorageType.2 rotesting1 volatile
SnmpMib = vacmSecurityToGroupStatus.2 rwtesting1 createAndGo
SnmpMib = vacmGroupName.2 rwtesting1 "rwtesting2"
SnmpMib = vacmSecurityToGroupStorageType.2 rwtesting1 volatile
SnmpMib = vacmAccessStatus.rotesting2 1 1 createAndGo
SnmpMib = vacmAccessContextMatch.rotesting2 1 1 exact
SnmpMib = vacmAccessReadViewName.rotesting2 1 1 "docsisManagerView"
SnmpMib = vacmAccessStorageType.rotesting2 1 1 volatile
SnmpMib = vacmAccessStatus.rwtesting2 1 1 createAndGo
SnmpMib = vacmAccessContextMatch.rwtesting2 1 1 exact
SnmpMib = vacmAccessReadViewName.rwtesting2 1 1 "docsisManagerView"
SnmpMib = vacmAccessWriteViewName.rwtesting2 1 1 "docsisManagerView"
SnmpMib = vacmAccessStorageType.rwtesting2 1 1 volatile
SnmpMib = vacmAccessStatus.rotesting2 2 1 createAndGo
SnmpMib = vacmAccessContextMatch.rotesting2 2 1 exact
SnmpMib = vacmAccessReadViewName.rotesting2 2 1 "docsisManagerView"
SnmpMib = vacmAccessStorageType.rotesting2 2 1 volatile
SnmpMib = vacmAccessStatus.rwtesting2 2 1 createAndGo
SnmpMib = vacmAccessContextMatch.rwtesting2 2 1 exact
SnmpMib = vacmAccessReadViewName.rwtesting2 2 1 "docsisManagerView"
SnmpMib = vacmAccessWriteViewName.rwtesting2 2 1 "docsisManagerView"
SnmpMib = vacmAccessStorageType.rwtesting2 2 1 volatile
SNMPV3Kickstart =
SNMPV3SecurityName = "docsisManager"
SNMPV3PublicNumber = hexstr: C1.FC.52.36.97.06.C0.22.99.61.D5.CA.C5.
4F.C6.68.51.71.A8.DC.69.AB.EB.D6.21.AC.AC.1D.FC.A6.0A.3A.8E.77.B5.15.AB.
AC.60.7C.5F.EB.AF.5F.86.B8.3F.2B.A1.DB.3D.ED.51.E2.EB.5D.E0.6A.EB.2D.AE.
E3.A4.DA.AC.DA.30.42.DC.A2.3C.5B.FE.65.83.B8.B8.9E.48.02.FB.70.A5.E9.97.
0C.95.9F.96.44.B4.BA.B4.2C.71.97.D1.1A.96.99.C9.4F.9C.53.3F.00.24.3E.1A.
12.AB.23.CF.DB.05.6C.97.62.4B.B2.A3.FC.7D.91.F4.90.C7.7C
DHCPv6 MIB The following MIB objects indicate the DHCP mode (v4 or v6) and assigned
Objects IP address. The address type for each object is one of the following:
ipv4(1):
DHCPv4
ipv6(2):
DHCPv6
ipv4z(3):
IPv4 non-global address with a zone index
ipv6z(4):
IPv6 non-global address with a zone index
dns(16):
DNS domain name
The objects are:
docsDevServerDhcpAddressType
The IP address type of the assigned address, or unknown(0) if the
IP address was statically assigned.
docsDevServerDhcpAddress
The IP address assigned to the CM, or an empty string if the IP
address was statically assigned.
The following MIB objects indicate the IP address and type of the assigned
time and TFTP servers:
docsDevServerTimeAddressType
The IP address type for the time server.
docsDevServerTimeAddress
The IP address of the time server.
docsDevServerConfigTftpAddressType
The IP address type of the TFTP server.
docsDevServerConfigTftpAddress
The IP address of the TFTP server.
The Syslog server address must be configured manually, either through an
SNMP manager or the configuration file. In either case, the following two
objects must be set in the order shown:
docsDevEvSyslogAddressType
The IP address type; either 1 (IPv4) or 2 (IPv6).
docsDevEvSyslogAddress
The IP address of the Syslog server, or a blank string to disable Sys-
log transmission.
The following read-only MIB objects are part of arrisCmDoc30DhcpCmPa-
rameters, and provide DHCP information.
arrisCmDoc30DhcpCmIpAddrType
(read-only) The type of the currently leased IP address.
arrisCmDoc30DhcpCmIpAddr
(read-only) The currently leased IP address.
arrisCmDoc30DhcpCmSubNetMask
(read-only) The current IP subnet mask in use.
arrisCmDoc30DhcpCmGatewayIpAddr
(read-only) The current IP gateway address in use.
arrisCmDoc30DhcpCmConfigFile
(read-only) The CM configuration file name.
SNMP Access The CM expects SNMP access to use the same IP mode (IPv4 or IPv6) that it
is provisioned with.
Event Reporting
Event Formats TS7.5 firmware provides log messages for both the cable modem and eDVA
sections of the Touchstone E-UE.
Hiding FQDN and The Event Log web page, described in ‘‘Using the Web-based Troubleshoot-
IP Information in ing Interface’’ on page 439, displays the FQDN (or IP address) of the eDVA
the Event Log for eDVA-related events in the Endpoint Name field. TS7.5 firmware can
hide this information from basic users for security purposes.
Note: Users with access to the Advanced pages (using the Password of the
Day) can always see FQDN and IP address information.
Follow these steps to enable or suppress FQDN and IP information in the
Event Log.
1 To suppress FQDN and IP information, set the arrisMtaDevEvent-
HideMacFQDNandIPAddress MIB object to enabled(1) in the CM
or eDVA configuration file and reboot the eDVA.
For basic users, the Event Log page replaces FQDN and IP informa-
tion by asterisks:
Note: Users that have entered the correct Password of the Day can see
FQDN and IP information on the Advanced Event Log webpage
regardless of the setting of the arrisMtaDevEventHideMacFQDNand-
IPAddress object.
The Event Log page displays FQDN and IP information to all users:
References The following CableLabs® specifications define the PacketCable 1.0 event
reporting mechanism:
PKT-SP-MEM1.5-I03-070412
PacketCable Management Event Mechanism
PKT-SP-EVEMIB1.5-I02-050812
PacketCable Management Event MIB Specification
PKT-TR-MEMEVENT-ID-V01-0000929
PacketCable Management Event Identifiers
Event Summary
Touchstone firmware generates events (alarms and log messages) from both
the CM and eDVA components. This manual documents only ARRIS-spe-
cific events; for DOCSIS CM events, see the DOCSIS 3.0 Operations Sup-
port System Interface Specification, CM-SP-OSSIv3.0-I15-100115.
eDVA States The following is a list of valid eDVA states and their meanings. The
ppSurvMtaMaintState object contains the current state.
eDVA Line States The following is a list of valid eDVA line states and their meanings. The
value of the ppSurvPortMaintState object provides the current line state.
• In Service, Normal—the line is operating normally.
• In Service, Trouble, Family Equipment Failure—a problem with the
eDVA subsystem is preventing the line from functioning properly. All
lines in this state may indicate that the eDVA failed to download its
firmware image.
• In Service, Trouble, Test Failed—the line failed diagnostics. The
‘‘Voice Line Diag Failed’’ log provides more details.
• In Service, Trouble, Diagnostics—the line is running diagnostics; if no
problems are discovered, the line will be placed in service when diag-
nostics are finished.
• In Service, Trouble, Line Card Protection—the line card is in an over-
current protection state. This state usually indicates either a short
between tip and ring, or a foreign voltage being applied to tip and ring.
• Out of Service, Normal, Unprovisioned—the line is not provisioned but
has no known problems.
• Out of Service, Normal—the line card is out of service and provisioned,
but has no known problems.
• Out of Service, Trouble—the line is out of service due to a detected
problem.
• Out of Service, Trouble, Diagnostics—the line is out of service, and is
running diagnostics.
• Out of Service, Trouble, Line Card Protection—the line card is in an
overcurrent protection state. This state usually indicates either a short
between tip and ring, or a foreign voltage being applied to tip and ring.
E-UE Battery The following is a list of valid battery states for E-UEs with battery backup.
States The value of the arrisMtaDevBatteryOperState object provides the current
battery state.
• The E-UE is operating on AC power. The battery is charged and in
good condition.
• The E-UE is operating on battery power.
• The E-UE is operating on AC power, but during a power outage has
drawn down the battery to the capacity indicated by the arrisMtaDev-
PwrSupplyLowBatteryThresh object.
eDVA Event The following is a list of ARRIS and PacketCable eDVA events that the
Summary TS7.5 firmware can generate. Go to the indicated page for further details on
each event.
Ent. ID Severity Log Text Page
4115 1 information(5) Voice Line Diag Failed 222
4115 2 information(5) Voice Line Diag Passed 223
4115 3 information(5) Voice Line State Change 223
4115 6 information(5) Voice Line Protection State Change 223
4115 14 information(5) Power Supply Telemetry Log 224
4115 16 information(5) MTA TFTP: Successful 224
4115 26 information(5) MTA PROV: Successful! 224
4115 65523 information(5) SIP General Failure 224
4115 65524 information(5) SIP Network Failure 225
4115 65526 information(5) SIP Authentication Failure 225
4115 65527 information(5) SIP Registration Timeout 225
4115 65528 information(5) SIP Proxy Loss of Communications 226
4115 1065562 information(5) MTA DHCP RENEW: Lease Renewal delay; Voice line offhook 229
4115 1065563 information(5) MTA DHCP REBIND: Lease Renewal delay; Voice line offhook 230
4115 65529 major(2) Power Supply Telemetry Alarm 230
4115 2417164301 information(5) SSH LOGIN ACCEPTED 226
4115 2417164302 information(5) SSH LOGIN REJECTED 226
4115 2417164303 information(5) SSH LOGIN REJECTED - MAX ATTEMPTS 227
4115 2417164296 information(5)
Touchstone SW Upgrade Failed Before Download Attempt 227
4115 2417164297 information(5)
Touchstone SW Upgrade Failed 228
4115 2417164298 information(5)
Touchstone SW Upgrade Successful 228
4115 2417164299 minor(3) Touchstone SW Upgrade Aborted due to Battery AC-FAIL Con- 229
dition
4115 2417164304 minor(3) Touchstone SW Upgrade Aborted due to Call in Progress 229
4115 2417164305 information(5) Touchstone SW Upgrade Reboot Delayed due to Call in Progress 229
4115 2417164308 information(5) Gateway has reset 230
4115 2417164309 information(5) Unit has been restored to factory defaults 231
4115 2417164311 information(5) Speedtest Results 231
4491 65528 minor(3) Battery Not Low 232
4491 65529 minor(3) Battery Low 232
4491 65530 minor(3) Battery Present 232
4491 65531 minor(3) Battery Missing 232
4491 65532 minor(3) Battery Good 232
4491 65533 minor(3) Replace Battery 232
4491 65534 minor(3) AC Restored 232
4491 65535 minor(3) AC Fail 232
ARRIS Events
The following are ARRIS eDVA-related events. ARRIS events use the enter-
prise number 4115.
Voice Line Diag The eDVA has failed manual diagnostics for the specified line.
Failed Format:
Voice Line Diag Failed, Line Number = line, Failure Reason = rea-
son
Fields:
The fields are as follows:
• line—The line number that failed diagnostics. The first line is
line 1.
• reason—one of the following:
– Line is Unprovisioned
– Invalid State to Init Diags
– Power/Clock Failure
– SLAC Revision Failure
– MPI Failure
– PCM Failure
– Standby Hook Failure
– Active Hook Failure
– VF Failure
– Ringing Failure
Action:
Use the reason code to determine the course of action as follows:
• Line is Unprovisioned—Provision the line and re-try the diagnos-
tics.
• Invalid State to Init Diags—Set the line state to oos and re-try the
diagnostics.
• others—Reset the eDVA and re-try diagnostics. If the problem
persists, replace the E-UE.
Voice Line Diag Indicates that the eDVA has successfully completed manual diagnostics on
Passed the specified line.
Format:
Voice Line Diag Passed, Line Number = line
Fields:
line indicates the line that passed diagnostics. The first line is
line 1.
Action:
None.
Voice Line State The eDVA received an operator-requested state change for the specified line.
Change Format:
Voice Line State Change, Line Number = line, Prev State =
old_state, New State = new_state
Fields:
The fields are as follows:
• line—the line number that changed state. The first line is line 1.
• old_state, new_state—the previous and current line states; see
‘‘eDVA Line States’’ on page 219 for details.
Action:
If the new state indicates a trouble condition, correct the problem.
Voice Line Protec- The specified line has detected or cleared a protection fault.
tion State Change Format:
Voice Line Protection State Change, Line Number = line, New State
= new_state
Fields:
The fields are as follows:
• line—the line number that changed state. The first line is line 1.
• new_state—the current protection state; one of:
– Fault DETECTED
– Fault CLEARED
Action:
Monitor the E-UE for service issues and possible replacement.
Power Supply The E-UE has detected a change in its battery telemetry state.
Telemetry Log Format:
Power Supply Telemetry - state
Fields:
The state field reflects the telemetry state; see ‘‘E-UE Battery
States’’ on page 220 for details. If a Replace Battery condition per-
sists for 24 hours, the E-UE generates another Power Supply
Telemetry log.
Action:
Replace the E-UE battery if indicated by the telemetry state.
MTA TFTP: Suc- The E-UE successfully downloaded its eDVA provisioning file.
cessful Format:
MTA TFTP: Successful
Action:
None.
MTA PROV: Suc- The E-UE successfully completed its eDVA provisioning.
cessful! Format:
MTA PROV: Successful!
Action:
None.
SSH LOGIN AC- A user has successfully logged into the Telephony Modem using SSH.
CEPTED Format:
SSH LOGIN ACCEPTED FROM IP [ipaddr] . USERNAME -
(name).
Fields:
The ipaddr is the IP address (e.g. 192.168.42.42) of the client log-
ging into the Telephony Modem. The name field is the user name
entered. The num field is the number of unsuccessful login attempts
since the last successful login.
Action:
None.
SSH LOGIN RE- A user has unsuccessfully attempted to log into the Telephony Modem using
JECTED SSH.
Format:
SSH LOGIN REJECTED FROM IP [ipaddr] . USERNAME -
(name).
Fields:
The ipaddr is the IP address (e.g. 192.168.42.42) of the client log-
ging into the Telephony Modem. The name field is the user name
entered.
Action:
None. However, a large number of unsuccessful login attempts may
indicate a potential intrusion attempt.
SSH LOGIN RE- A user unsuccessfully attempted to log in too many times. The session was
JECTED - MAX AT- disconnected.
TEMPTS Format:
REACHED SSH LOGIN REJECTED - MAX ATTEMPTS REACHED
Action:
Continue to monitor the logs for ‘‘SSH LOGIN REJECTED’’ mes-
sages. Blocking the IP addresses of any attempted intruders may be
necessary to protect your network.
Touchstone Touchstone Firmware Upgrade has failed. Standard DOCSIS download logs
Firmware Upgrade should also be present to further describe the exact download failure reason.
Failed Format:
Touchstone Firmware Upgrade Failed: type
Fields:
The type code is one of the following:
• Provisioned upgrade
Download initiated via configuration file has failed.
• Manual upgrade
Download initiated via remote SNMP browser has failed.
Action:
Make sure the upgrade table and the specified TFTP servers are con-
figured properly, then retry the download.
Touchstone SW Touchstone Firmware Upgrade has failed since the E-UE is running on bat-
Upgrade Aborted tery power.
due to Battery AC- Format:
FAIL condition Touchstone SW Upgrade Aborted due to Battery AC-FAIL condi-
tion
Fields:
None
Action:
Wait for AC power to be restored before attempting the firmware
upgrade again.
Touchstone SW Touchstone Firmware Upgrade has failed since one or more lines are off-
Upgrade Aborted hook and the arrisMtaDevSwDnldNoSvcImpact object is set to StrictEn-
due to Call in Pro- able(2).
gress Format:
Touchstone SW Upgrade Aborted due to Call in Progress
Fields:
None
Action:
Wait for all lines to go on-hook before attempting the firmware
upgrade again.
Touchstone SW Touchstone Firmware Upgrade has succeeded, but the E-UE has not rebooted
Upgrade Reboot since one or more lines are off-hook and the arrisMtaDevSwDnldNoSvc-
Delayed due to Impact object is set to enable(1).
Call in Progress Format:
Touchstone SW Upgrade Reboot Delayed due to Call in Progress
Fields:
None
Action:
None; the E-UE will reboot once all lines have been idle for at
least 30 seconds after the load has been accepted.
MTA DHCP RE- The eDVA DHCP RENEW sequence has been delayed because the arrisM-
NEW: Lease Re- taDevDhcpNoSvcImpact object is enabled (value is either dontSend or
newal delay; Voice sendIgnore) and one of the voice lines is offhook.
line offhook Format:
MTA DHCP RENEW: Lease Renewal delay; Voice line offhook
Action:
None; the eDVA will not RENEW its IP address until all voice lines
are on-hook.
MTA DHCP RE- The eDVA DHCP RENEW period has timed out, and the eDVA DHCP
BIND: Lease Re- REBIND sequence has been delayed, because the arrisMtaDevDhcp-
newal delay; Voice NoSvcImpact object is enabled (value is either dontSend or sendIgnore)
line offhook and one of the voice lines is offhook.
Format:
MTA DHCP REBIND: Lease Renewal delay; Voice line offhook
Action:
None; the eDVA will not RENEW its IP address until all voice lines
are on-hook.
Impact:
Data communications (Ethernet or wifi) may be disrupted for a few
seconds. Telephony is not affected.
Action:
None.
PacketCable Events
Battery Not Low The E-UE battery has recharged to over 25% of its maximum capacity.
Battery Low The E-UE battery charge is less than 25% of its maximum capacity.
Battery Missing The E-UE battery has been either removed or is undetectable. If the battery
is still installed, it may be defective.
If a large number of ‘‘Battery Missing’’ and ‘‘Battery Present’’ messages
appear in the logs for a single E-UE, this may indicate a problem with either
the battery or the E-UE.
Battery Good An E-UE battery that had previously shown a ‘‘Replace Battery’’ state is now
good. This may indicate that the battery has been replaced.
Replace Battery The E-UE battery has deteriorated to about 75% of its off-the-shelf capacity
and should be replaced.
AC Fail AC power has been removed from the E-UE, and the E-UE is running on bat-
tery power.
If a large number of ‘‘AC Restored’’ and ‘‘AC Fail’’ messages appear in the
logs for a single E-UE, this may indicate that the E-UE is connected to a
switched outlet or the power connection may be intermittent.
Recovery from Ex- In a situation where the downstream RF signal degrades to the point where
treme Plant Condi- the upstream transmit buffers are full, and the E-UE cannot send packets, an
tions automatic recovery feature:
• resets the DOCSIS layer
• restarts the DSP
• notifies Call Processing to restore dialtone functionality
The result is a cleaner recovery from extreme RF degradation.
Message Capacity The message log stores up to 250 messages. The buffer size is 25K bytes.
SIP loads generate larger messages, reducing the number of messages actu-
ally stored.
The DHCP log stores up to 50 CM messages and up to 50 eDVA DHCP mes-
sages. Each DHCP buffer is 5K bytes.
Note: The E-UE captures the original DHCP Discover-Offer exchange, and
all subsequent Renew exchanges.
The eDVA uses a circular buffer scheme to store messages. When a new
message exceeds the available buffer space, the eDVA deletes the oldest mes-
sages as needed.
SNMP Overview Log messages can be up to 4K bytes in length. Since an SNMP string is lim-
ited to 256 bytes, retrieving a message through SNMP requires breaking the
message up. The objects arrisMtaDevSignalingLastMsg1 through arris-
MtaDevSignalingLastMsg16 contain the selected message.
Enabling or Dis- Follow these steps to enable or disable message tracing using the CLI or
abling Message SNMP. Trace logs are enabled by default.
Tracing 1 To control message tracing using SNMP:
a Specify which message type that you want to enable or disable by
setting the following objects:
arrisMtaDevEnableDHCPLog
Set to enable(1) to enable DHCP messages.
arrisMtaDevEnableMGCPLog
Set to enable(1) to enable MGCP messages.
b Enable or disable message tracing for the selected message type
by setting the arrisMtaDevEnableLogging object: either dis-
able(0) or enable(1).
/ voice ↵
callp dsxEnblLog 1 ↵
Viewing Logs Us- Follow these steps to view message trace logs using the command-line inter-
ing the CLI face.
1 Access the CLI as described in ‘‘Enabling and Accessing the Trou-
bleshooting CLI’’ on page 435.
2 To view the eDVA DHCP logs:
/ mta mtaDispLog ↵
Viewing Logs Us- Follow these steps to read message logs using SNMP.
ing SNMP 1 Follow the steps in ‘‘Enabling or Disabling Message Tracing’’ on
page 235 to specify which message types that you want to view.
2 Set the arrisMtaDevEnableCallSigLastMsgRpt object to enable, to
enable message logging to the arrisMtaDevSignalingLastMsg1
through arrisMtaDevSignalingLastMsg16 objects.
3 Read the arrisMtaDevSignalingLastMsg1 through arrisMtaDevSig-
nalingLastMsg16 objects to view the last log of the selected type. If
the message does not require all 16 objects, the unused objects return
empty strings.
Viewing Logs Us- Follow these steps to view message logs using the web-based troubleshooting
ing the Web-based interface.
Interface 1 Use a web browser to access the web-based interface as described in
‘‘Accessing the Standard Pages’’ on page 457.
2 If you are currently viewing the Basic pages, click the Advanced link.
Enter the Password of the Day if necessary.
3 To view either CM or eDVA DHCP logs:
a Select the DHCP link at the top of any Advanced web page to
access the DHCP Parameters page.
b At the bottom of the DHCP Parameters page (scroll down to the
bottom of the page if necessary), select either the CM-DHCP or
MTA-DHCP link.
Controlling Logs Follow these steps to enable, disable, or clear message logs using the web-
Using the Web- based interface.
Based Interface 1 Access the Advanced web pages as described in ‘‘Accessing the
Advanced Pages’’ on page 457.
2 To work with DHCP logs:
a Click the DHCP link to access the DHCP page.
b Scroll down to the bottom of the screen to view the logging con-
trols:
c To clear the CM DHCP or eDVA DHCP logs, click the Clear but-
ton for the desired log.
d To enable or disable CM DHCP logs, click the Disable CM Log
button. This button changes to Enable CM Log when logging is
disabled.
e To enable or disable eDVA DHCP logs, click the Disable MTA
Log button. This button changes to Enable MTA Log when log-
ging is disabled.
3 To work with MGCP and DSX logs:
a Click the QoS link to access the Qos Statistics page:
b To clear the MGCP log, click the Clear button midway down the
screen.
c To enable or disable CallP logging, click the Disable Logging
button midway down the screen. This button changes to Enable
Logging when logging is disabled.
e To clear the DSX log, click the Clear button at the bottom of the
screen.
Clearing Message Follow these steps to clear message trace logs using the CLI.
Trace Logs Using 1 Access the CLI as described in ‘‘Enabling and Accessing the Trou-
the CLI bleshooting CLI’’ on page 435.
2 To clear the eDVA DHCP logs:
/ mta mtaClearLog ↵
CAUTION
Potential security breach
This feature allows NCS signaling messages to enter the network as clear
text. This breaks security as defined in the PacketCable Security specifica-
tion. IPsec is used to secure the message link between the eDVA and CMS
to, among other things, keep the voice keys exchanged between endpoints
secure. Unauthorized personnel may potentially be able to monitor a sub-
scriber’s voice traffic.
Touchstone firmware can generate a Syslog report that contains a full signal-
ing trace on a Touchstone E-UE. Individual signaling messages may be up to
4000 bytes in length. Since messages of this size would violate the maxi-
mum message size limitations of the Syslog server, long messages are broken
into blocks of 128 bytes, time stamped, and numbered for reassembly. The
eDVA then sends the blocks to the Syslog server IP address defined during
normal E-UE provisioning.
Signaling tracing is controlled using the arrisMtaDevEnableCallpSigTrace
MIB object. You can enable or disable message tracing output on an E-UE
using an SNMP manager.
Note: Touchstone firmware supports this feature only for capturing NCS sig-
naling traces. Support for capturing SIP signaling traces may be added in a
future release.
Controlling Signal- Use the arrisMtaDevEnableCallpSigTrace MIB object (part of the arrisMta-
ing Tracing DevBase MIB) to enable or disable signal tracing. The default value for this
object is disable(0).
CAUTION
Potential performance impacts
The number of messages expected as a result of enabling this feature can
affect the real-time performance of the E-UE, and may cause network con-
gestion.
Interpreting the The following is an example of a single part transmission from the E-UE to a
Signaling Trace NCS Call server:
Output Data Oct 21 10:55:04 10.1.61.17 Oct 21 10:55:03
2005 mta17.dev61 <44> <4115> <37> <00:13:11:23:23:E7>
<Xmit: (17: 1 of 1) - ’NTFY 8 aaln/[email protected] MGCP 1.0 NCS
1.0 X: 26002 O: hu ’>
The following is an example of a single part Receive from a NCS Call Server
to the E-UE:
Oct 21 10:55:04 10.1.61.17 Oct 21 10:55:03
2005 mta17.dev61 <45> <4115> <38> <00:13:11:23:23:E7>
<Rcv: (19: 1 of 1) - ’200 8 OK ’>
The following output is part of the Syslog header, and appears in both Trans-
mit and Receive trace messages.
Oct 21 10:55:04
Syslog server Date and Time.
10.1.61.17
The IP address of the eDVA that sent the message.
Oct 21 10:55:03 2005
The E-UE generated Data and Time.
mta17.dev61
The FQDN of the E-UE.
<44>
The Syslog message Event Number. It is incremented for each mes-
sage in the Syslog.
<4115>
The Arris Enterprise Number.
The following sections describe the transmit and receive data payloads.
The transmit message data can be broken down into two parts, the Header
and the signaling data itself. The header indicates that this is a transmitted
message from the E-UE; it provides the sequence number of the message, the
block number, total number of blocks in this message, and the payload of the
signaling message.
The following table shows the data payload that is part of the transmit mes-
sage trace. The first two parts comprise the header; the next two parts are the
actual message.
<37>
An Index number indicating that this is a transmitted message. All
transmitted messages are of type 37.
<00:13:11:23:23:E7>
The MAC address of the E-UE that transmitted the message.
Xmit: (17: 1 of 1) -
All transmitted messages start with Xmit. The 17 is a message
sequence number. All transmitted messages have a unique sequence
number that increases by one for each complete message transmit-
ted. This internal value is a 32-bit unsigned integer value that incre-
ments only when tracing is active. Sequence numbers start at zero.
The sequence numbers increment only when a message is sent to
the Syslog. The ‘‘1 of 1’’ indicates that this is part 1 of a one part
message. All parts of the same message have the same sequence
number.
’NTFY 8 aaln/[email protected]
MGCP 1.0 NCS 1.0 X: 26002 O: hu ’
The actual signaling message data. The data is surrounded by single
quotes. All signaling messages are NULL terminated strings.
The following is an example of a single part Receive from a NCS Call Server
to the eDVA:
Oct 21 10:55:04 10.1.61.17 Oct 21 10:55:03
2005 mta17.dev61 <45> <4115> <38> <00:13:11:23:23:E7>
<Rcv: (19: 1 of 1) - ’200 8 OK ’>
The receive message data can be broken down into two parts, the Header and
the signaling data. The header indicates that this is a signaling message
received by the eDVA; it provides the sequence number of the message, the
block number, total number of blocks in this message, and the signaling data
received.
The following table shows the data payload that is part of a receive message
trace:
<38>
An index number indicating that this is a received signaling mes-
sage. All received messages are type 38.
<00:13:11:23:23:E7>
The MAC address of the Message Destination.
Rcv: (19: 1 of 1)
All received messages start with Rcv:. The 19 is a message
sequence number. All received messages have a unique sequence
number that increases by one for every complete message received
by the eDVA. This internal value is a 32-bit unsigned integer value
and only increments when the tracing is active. Sequence numbers
start at zero. All messages have a unique sequence number. The ‘‘1
of 1’’ indicates that this is part 1 of a 1-part message. All parts of
the same message have the same sequence number.
’200 8 OK ’
The actual received signaling data. The data is surrounded by single
quotes.
Below is a small sample output for a typical off-hook and on-hook sequence
in NCS. In a real world situation on an actual network Syslog server, there
could be messages unrelated to this feature interleaved with these messages:
Oct 21 10:55:00 10.1.61.17 Oct 21 10:54:59
2005 mta17.dev61 <37> <4115> <37> <00:13:11:23:23:E7>
<Xmit: (14: 1 of 1) - ’NTFY 7 aaln/[email protected] MGCP 1.0 NCS
1.0 X: 25888 O: hd ’>
Oct 21 10:55:00 10.1.61.17 Oct 21 10:54:59 2005 mta17.dev61
<38> <4115> <38> <00:13:11:23:23:E7> <Rcv: (16:
1 of 1) - ’200 7 OK ’>
Oct 21 10:55:00 10.1.61.17 Oct 21 10:54:59 2005 mta17.dev61
<39> <4115> <38> <00:13:11:23:23:E7> <Rcv: (17:
1 of 1) - ’RQNT 3752 aaln/[email protected] MGCP 1.0 NCS 1.0 X: 26001
S: Q: loop R: hf(I), hu(N) ’>
Oct 21 10:55:01 10.1.61.17 Oct 21 10:54:59 2005 mta17.dev61
<40> <4115> <37> <00:13:11:23:23:E7> <Xmit: (15:
1 of 1) - ’200 3752 OK ’>
Oct 21 10:55:01 10.1.61.17 Oct 21 10:54:59 2005 mta17.dev61
<41> <4115> <38> <00:13:11:23:23:E7> <Rcv: (18:
Overview This procedure provides details on adding the necessary MIBs and TLVs to a
cable modem configuration file. See the Provisioning chapter for a listing of
the completed configuration file.
To configure the E-UE for coexistence mode, you must create a row entry in
the snmpCommunityTable, to map the community string to an SNMPv3
security name. You can optionally modify the following tables to provide
extended access control.
• vacmSecurityToGroupTable—two row entries, containing group name
information. One entry supports SNMPv1 access and the other entry
supports SNMPv2 access.
• vacmAccessTable—two row entries, which map the community name,
security name, and group name information to an SNMPv3 security
name. The DOCSIS-standard default security name for cable modems
is docsisManager. One entry supports SNMPv1 access and the other
entry supports SNMPv2 access.
In DOCSIS 2.0, SNMP access was enabled and open to all users until apply-
ing any restricted settings in the CM configuration file. TS7.0 and newer ver-
sions of Touchstone firmware disables SNMP access by default. The follow-
ing example fragment can be placed in a CM configuration file to enable
SNMP access:
SnmpMib = docsDevNmAccessCommunity.1 "public"
SnmpMib = docsDevNmAccessControl.1 read
SnmpMib = docsDevNmAccessInterfaces.1 hexstr: 40
SnmpMib = docsDevNmAccessStatus.1 createAndGo
SnmpMib = docsDevNmAccessCommunity.2 "private"
SnmpMib = docsDevNmAccessControl.2 readWrite
SnmpMib = docsDevNmAccessInterfaces.2 hexstr: 40
SnmpMib = docsDevNmAccessStatus.2 createAndGo
Note: TS7.5 allows read-only SNMP access to certain objects from the LAN
interfaces before the modem has ranged and registered, in accordance with
CM-SP-OSSIv3.0-I15-100115.
– IP Address: 10.1.50.80
– Trap Type: SNMPv2
Note: Change the trap IP address to the IP address of your specific trap server
in the configuration file.
This example starts with a basic DOCSIS 1.1 CM configuration file, contain-
ing enough information to allow a cable modem to range and register, and
then add the coexistence MIB elements to it. If you have a CM configuration
file that you are already using, start with that file and add the coexistence ele-
ments to it.
snmpCommunity- The following table shows the example row to add to the snmpCommunity-
Table Parameters Table. The index for this table is an octet string; the example uses the string
comm1 as the index value. You can use a different string if you desire. Itali-
cized values in the table are default values that are created automatically.
The following examples use the ARRIS PacketACE Configuration Editor to
create the configuration file, covering only the details needed to add the
desired functionality. See the PacketACE Configuration Tools User’s Guide
for more information about using PacketACE.
Object Name Value Required?
snmpCommunityName.comm1 my_password Yes
snmpCommunitySecurityName.comm1 rwAccess Yes
snmpCommunityContextEngineID.comm1 local snmpEngineID No
snmpCommunityContextName.comm1 (zero-length) No
snmpCommunityTransportTag.comm1 (zero-length) No
snmpCommunityStorageType.comm1 volatile (2) No
snmpCommunityStatus.comm1 createAndGo (4) Yes
Note: Avoid adding table index objects to the configuration file; the firmware
fills in the index object using the index value supplied with the object name
(.comm1 in this example). See ‘‘Adding the snmpCommunityTable’’ on
page 249 for the proper way to add rows.
Object order is not important.
vacmSecurity- The following table shows the example row to add to the vacmSecurity-
ToGroupTable Pa- ToGroupTable. This table has an index consisting of two objects:
rameters • vacmSecurityModel—corresponds to the SNMP version in use; in this
example, it takes the values 1 and 2 to allow support for both SNMPv1
and SNMPv2 requests.
• vacmSecurityName—corresponds to the snmpCommunitySecurity-
Name MIB object in the snmpCommunityTable (rwAccess in this
example).
vacmAccessTable The following table shows the example row to add to the vacmAccessTable.
Parameters This table has an index consisting of four objects:
• vacmGroupName—corresponds to the vacmGroupName object in the
vacmSecurityToGroupTable (rwAccess in our example). CM and
eDVA group names should be unique.
• vacmAccessContentPrefix—an octet string; in this example we use
an empty (zero length) string. This is shown as ‘‘’’ in the table below.
• vacmAccessSecurityModel—corresponds to the SNMP version in
use; in this example; it takes the values 1 and 2 to allow support for
both SNMPv1 and SNMPv2 requests.
• vacmAccessSecurityLevel—for SNMP coexistence, use a value of 1
(noAuthnoPriv). This means that the E-UE has no configured SNMPv3
USM security users/keys.
Object Name Value (row 1) Value (row 2)
GroupName (row index 1) rwAccess rwAccess
ContentPrefix (row index 2) ‘‘’’ ‘‘’’
SecurityModel (row index 3) 1 (SNMPv1) 2 (SNMPv2)
SecurityLevel (row index 4) 1 (noAuthnoPriv) 1 (noAuthnoPriv)
vacmAccessContextMatch exact (1) exact (1)
vacmAccessReadViewName docsisManagerView docsisManagerView
vacmAccessWriteViewName docsisManagerView docsisManagerView
vacmAccessNotifyViewName docsisManagerView docsisManagerView
vacmAccesssStorageType volatile (2) volatile (2)
vacmAccessStatus createAndGo (4) createAndGo (4)
Adding the snmp- Follow these steps to add coexistence MIB objects to a CM configuration file
CommunityTable using PacketACE.
1 Click the ‘‘Add SNMP MIB’’ icon or select Edit menu -> Add SNMP
MIB.
Note: The order of your MIB entries may be different than what is
shown above.
6 Proceed to ‘‘Adding the vacmSecurityToGroupTable.’’
Adding the vacm- Follow these steps to add coexistence MIB objects to a CM configuration file
SecurityToGroup- using PacketACE.
Table 1 Click the ‘‘Add SNMP MIB’’ icon or select Edit menu -> Add SNMP
MIB.
Note: The order of your MIB entries may be different than what is
shown above.
6 Proceed to ‘‘Adding the vacmAccessTable.’’
Adding the vacm- Follow these steps to add coexistence MIB objects to a CM configuration file
AccessTable using PacketACE.
1 Click the ‘‘Add SNMP MIB’’ icon or select Edit menu -> Add SNMP
MIB.
2 Locate the vacmAccessTable MIB. If you are not sure where the
MIB is located in the tree, enter the name of the MIB in the upper
field along the right side of the PacketACE window and then click
Find MIB by Name.
4 Enter indexes as follows, and the value from the table in step 3 in the
Value field.
Action 1 Click the ‘‘Add TLV parameter’’ icon or select Edit menu -> Add
TLV.
TR-069 Management
Supported Servers
The Touchstone TR-069 implementation has been tested with the following
TR-069 servers:
• Incognito
• OpenACS
TR-098 Objects The following objects are recognized but not supported. These objects
Recognized but always return the default value defined in the TR-098 specification.
not Supported
Object
PasswordRequired
InternetGatewayDevice.UserInterface.
PasswordUserSelectable
InternetGatewayDevice.LANDevice.{i}.LANHostConfigManagement. DHCPServerConfigurable
Enable
InternetGatewayDevice.LANDevice.{i}.LANHostConfigManagement.IPInterface.{i}.
IPInterfaceIPaddress
InternetGatewayDevice.LANDevice.{i}.LANHostConfigManagement.DHCPStaticAddress.{i}. Enable
InternetGatewayDevice.LANDevice.{i}.WLANConfiguration.{i}. MACAddressControlEnabled
PreSharedKey
InternetGatewayDevice.LANDevice.{i}.WLANConfiguration.{i}.PreSharedKey.{i}.
AssociatedDeviceMACAddress
AssociatedDeviceMACAddress
InternetGatewayDevice.LANDevice.{i}.WLANConfiguration.{i}.AssociatedDevice.{i}. AssociatedDeviceIPAddress
AssociatedDeviceAuthenticationState
References For more information about TR-069, see the following external references.
Links download the associated PDF or DOC file.
• [TR-069 Issue 3] 〈http://www.broadband-forum.org/
technical/download/TR-069_Amendment-3.pdf〉 —
TR-069 Amendment 3, CPE WAN Management Protocol
• [TR-098 Issue 2] 〈http://www.broadband-forum.org/
technical/download/TR-098_Amendment-2.pdf〉 —
TR-098 Internet Gateway Device Data Model for TR-069, Amendment
2
• Wi-Fi Provisioning Framework Specification 〈https://
www.cablelabs.com/doczone/wireless/requirements/
specs/current/wrspwifimgmti02101005.doc〉, WR-SP-
WiFi-MGMT-I02-101005
Most DOCSIS 3.0 CMTSs currently do not support all three partial service
signaling methods. Use the information in this procedure to configure the
Telephony Modem to work around the limitations of the CMTS, if necessary.
Consult the release notes for your CMTS firmware or software to determine
whether one of the following workarounds are needed.
Action Identify the workaround needed for your CMTS, if necessary, then use the
following tasks as needed.
Task Page
Identifying Partial Service Issues 267
If the CMTS does not Support CM-STATUS 268
If the CMTS does not Support REG-ACK 268
Identifying Partial Follow these steps to identify partial service issues on a Telephony Modem.
Service Issues 1 To identify partial service issues using an SNMP browser, read the
arrisCmDoc30ProvisionedChannelIDs object. This object displays
the channel IDs of the provisioned downstreams and upstreams. An
example display is:
DS: 8, 5, 6, (7) -- US: 5, 6, 7, 8
This example shows that the downstream channel DCID 7 is down
(enclosed in parentheses) and the modem thus has partial service.
2 To identify partial service issues using the web-based interface, access
the basic Status page. This page shows the provisioned downstreams
and upstreams in the ‘‘RF Parameters’’ section.
The Status page indicates down channels by replacing parameters
with dashes (----) for all but the provisioned frequency.
If the CMTS does If the CMTS supports the REG-ACK Partial Service Confirmation Code, but
not Support CM- not CM-STATUS message reporting, follow these steps.
STATUS 1 Set the arrisCmDoc30SetupSecDsLossReinitEnable object to
enable(1), using an SNMP manager or by changing the configuration
file.
2 If you made the change in the configuration file, reset the Telephony
Modem so the change takes effect.
3 If QAM or FEC lock is lost on a secondary downstream for 45 sec-
onds, the Telephony Modem re-initializes the downstream MAC; this
allows a REG-ACK to inform the CMTS which downstreams are
available.
4 When the secondary downstream becomes available, manually reset
the CM to restore full service.
If the CMTS does If the CMTS supports bonded channels, but does not support the REG-ACK
not Support REG- Partial Service Confirmation Code, follow these steps.
ACK 1 Set the arrisCmDoc30SetupPartServiceFallback20 object to
enable(1), using an SNMP manager or by changing the configuration
file.
2 If you made the change in the configuration file, reset the Telephony
Modem so the change takes effect.
3 If the Telephony Modem cannot acquire a secondary downstream, it
re-registers in DOCSIS 2.0 (non-bonded) mode. Every 15 minutes,
the Telephony Modem re-initializes the primary downstream DOCSIS
MAC until it can acquire all downstream channels. No further opera-
tor intervention is required.
Unless you are using synchronous upstreams, use the default setting maxbat-
tery(1) to maximize battery hold-up time during power outages.
CMTS Considera- For best results, the CMTS should fully support CM-STATUS partial service
tions messages. If the CMTS does not support CM-STATUS, add the arrisCm-
Doc30SetupPowerSaveMode object to the CM configuration file with a
value of reinitmac(1). This causes the CM to re-register in unbonded (1x1)
mode upon loss of AC power, and re-register to bonded mode when AC
power is restored.
arrisCmDoc30Ac- These objects control access to the CLI and web pages.
cess arrisCmDoc30AccessTelnetPassword
A string containing the password used to enable Telnet. Except for
TW loads, this object must be set to enable Telnet access.
arrisCmDoc30AccessTelnetEnable
Enables or disables access to the CLI using Telnet.
arrisCmDoc30AccessClientSeed
A string containing the seed used to generate the Password of the
Day. If you change this value, you must also change the value of
the seed used in the PacketACE Password of the Day generator.
arrisCmDoc30AccessHttpPwCtrl
Controls which web pages are password protected:
• none(0): no pages are protected
• advanced(1): advanced pages are protected (default)
• all(2): all pages are protected
arrisCmDoc30AccessSSHEnable
Enables or disables SSH access. To enable SSH, this object must be
enabled, and (except for TW loads) the arrisCmDoc30AccessTel-
netPassword object must also be set.
Example:
start=3/8/7/02;end=11/1/7/02
Implements the U.S. DST policy in effect since March 2007: DST
begins at 2 a.m. on the second Sunday in March and ends at 2 a.m.
on the first Sunday in November.
arrisCmDoc30SetupMddIpModeOverride
Specifies whether the CM honors or ignores the TLV5.1 message
from the CMTS. This object is deprecated in favor of the PacketCa-
ble-defined docsIf3CmMdCfgIpProvMode object. Use only one or
the other in the configuration file.
arrisCmDoc30SetupPacketCableRegion
Sets the region for MTA PacketCable provisioning: northAmeri-
can(0) or european(1).
arrisCmDoc30SetupTodDelaySecProv
Enables or disables delaying of secure provisioning when Time of
Day retrieval fails.
arrisCmDoc30SetupUdcAllowed
Allows or disallows upstream drop classifiers, overriding the REG-
RSP value. The settings are:
0: disallow UDC, regardless of what the CMTS sets
1: allow UDC
arrisCmDoc30SetupTODTimeOffset
Sets the CM ToD time offset from GMT, in seconds. Valid range:
−43200 (−12 hours) to 46800 (+13 hours). This value may be over-
written when the TOD offset option is received through DHCP.
arrisCmDoc30SetupDhcpRetries
The number of times the MTA ignores a non-Secure (BASIC or
HYBRID) DHCP OFFER while waiting for a SECURE flow DHCP
OFFER.
arrisCmDoc30SetupInvertMulticolorLEDs
Enables or disables inverted multicolor LED behavior. The setting
is stored to non-volatile memory and persists across reboots. The
settings are:
disable(0):
Original WBM3.2/TS7.1 LED color scheme:
Bonded DS = Green; non-bonded DS = Yellow
Bonded US = Green; non-bonded US = Yellow
GigE/USB2.0 = Green; 10/100/USB1.x = Yellow
enable(1):
Inverted LED color scheme:
Bonded DS = Yellow; non-bonded DS = Green
Bonded US = Yellow; non-bonded US = Green
GigE/USB2.0 = Yellow; 10/100/USB1.x = Green
arrisCmDoc30SetupTurboDoxEnable
Enables or disables TurboDox operation. Set to true(1) (default) to
enable TurboDox operation mode, or false(2) to disable TurboDox.
This object can be changed only in the configuration file.
arrisCmDoc30SetupMdfSupportOverride
Configures MDF override support:
disable(0): disables MDF override, using the value provided in the
REG-RSP from the CMTS
enable(1): force-disables MDF support
arrisCmDoc30SetupAdvancedWebPageAccess
Enables or disables access to the Advanced web page:
• To disable all access to the Advanced pages, set the value to
none(0).
arrisCmDoc30SetupIgnoreMddSymbolClockIndicator
When set to enable(1), the CM ignores the Symbol Clock Locking
Indicator TLV in the MDD message and always uses asynchronous
timing mode. In this mode, the cable modem does not lock to the
downstream symbol clock on its Primary Downstream Channel. It
acquires the synchronization timebase for upstream burst timing
from the SYNC messages.
When set to disable(0), the CM follows the timing mode specified
by the Symbol Clock Indicator TLV in the MDD message.
arrisCmDoc30SetupTCPAckSuppression
Enables or disables TCP Ack suppression. Default: true(1).
arrisCmDoc30SetupL2VPNPromiscuousMode
Enables or disables L2VPN promiscuous mode.
arrisCm- These objects provide DHCP status information. There are four groups
Doc30Dhcp under this MIB:
• arrisCmDoc30DhcpLeaseParameters
• arrisCmDoc30DhcpSvrParameters
• arrisCmDoc30DhcpCmParameters
• arrisCmDoc30DhcpMtaParameters
arrisCmDoc30DhcpLeaseParameters Objects
arrisCmDoc30DhcpSvrParameters Objects
These objects provide information about the DHCP server. All these objects
are read-only.
arrisCmDoc30DhcpState
The current CM DHCP state; one of:
• init-selecting(0)
• requesting(1)
• bound(2)
• renewing(3)
• rebinding(4)
• init-reboot(5)
• renew-requested(6)
• released(7)
arrisCmDoc30DhcpPrimaryDhcpServerIpAddr
Displays the primary DHCP server address.
arrisCmDoc30DhcpTftpSvrIpAddr
Displays the current TFTP server IP address in use.
arrisCmDoc30DhcpTimeSvrIpAddr
Displays the current Time server IP address in use.
arrisCmDoc30DhcpCmTimeOffset
Displays the current time offset being used by the CM.
arrisCmDoc30DhcpPrimaryTeleDhcpSvr
Displays the primary MTA DHCP server address.
arrisCmDoc30DhcpSecondaryTeleDhcpSvr
Displays the secondary MTA DHCP server address.
arrisCmDoc30DhcpCmParameters Objects
These objects provide information about the current CM DHCP lease. All
these objects are read-only.
arrisCmDoc30DhcpCmIpAddrType
Displays the type (IPv4 or IPv6) of the currently leased IP address.
arrisCmDoc30DhcpCmIpAddr
Displays the currently leased IP address.
arrisCmDoc30DhcpCmSubNetMask
Displays the current IP subnet mask in use.
arrisCmDoc30DhcpCmGatewayIpAddr
Displays the current IP gateway address in use.
arrisCmDoc30DhcpCmConfigFile
Displays the CM configuration file to be retrieved.
arrisCmDoc30DhcpMtaParameters Objects
These objects provide information and control over MTA DHCP operation.
arrisCmDoc30DhcpMtaOpt60Override
Enables or disables SIP advertisement in MTA DHCP Option 60.
The default is disabled. This object can be set only using the CM
configuration file.
arrisCm- These objects provide extended DHCP information. All these objects are
Doc30DhcpEx- read-only.
tended arrisCmDoc30DhcpExtendedProvisionedMode
Displays the CM provisioned mode:
• ipv4-only(0)
• ipv6-only(1)
• alternate-prov-mode(2)
• dual-prov-mode(3)
arrisCmDoc30DhcpExtendedPreferredMode
Displays the CM preferred IP mode: ipv4(0) or ipv6(1).
arrisCmDoc30DhcpExtendedActiveMode
Displays the CM active IP mode: ipv4(0) or ipv6(1).
arrisCmDoc30DhcpExtendedLeaseParametersTable Objects
arrisCmDoc30DhcpExtendedSvrParametersTable
arrisCmDoc30DhcpExtendedPrimaryTeleDhcpSvr
The primary MTA DHCP server address.
arrisCmDoc30DhcpExtendedSecondaryTeleDhcpSvr
The secondary MTA DHCP server address.
arrisCmDoc30DhcpExtendedCmParametersTable Objects
arrisCmDoc30Re- These objects contain the reset reason log. All these objects are read-only.
setReasonLog arrisCmDoc30LastHwResetReason
The last reset reason retrieved from the processor hardware. This
reason is used to determine if hardware or firmware caused the
reset.
arrisCmDoc30ResetReasonLogTable Objects
This table contains the last ten reset reasons. The valid index range is 1 to
10.
arrisCmDoc30ResetReasonLogText
The reported reset reason log text.
DOCSIS 3.0 MIB The following table shows how to map certain ARRIS DOCSIS 2.0 MIB
Object Mapping objects to their DOCSIS 3.0 counterparts.
DOCSIS 2.0 Object/OID DOCSIS 3.0 Object/OID
arrisCmProdResetToFactoryDefaults arrisCmDoc30ResetFactoryDefaults
1.3.6.1.4.1.4115.1.3.2.2.15 1.3.6.1.4.1.4115.1.3.4.1.1.6
arrisCmDevSwImageName arrisCmDoc30FwImageName
1.3.6.1.4.1.4115.1.3.1.1.1.2 1.3.6.1.4.1.4115.1.3.4.1.1.7
arrisCmDevSwImageBuildTime arrisCmDoc30FwImageBuildTime
1.3.6.1.4.1.4115.1.3.1.1.1.3 1.3.6.1.4.1.4115.1.3.4.1.1.8
arrisCmProdAccessPWD arrisCmDoc30AccessTelnetPassword
1.3.6.1.4.1.4115.1.3.2.2.2 1.3.6.1.4.1.4115.1.3.4.1.2.1
arrisCmDevTelnetEnable arrisCmDoc30AccessTelnetEnable
1.3.6.1.4.1.4115.1.3.1.1.2.3.23 1.3.6.1.4.1.4115.1.3.4.1.2.2
arrisCmDevHttpClientSeed arrisCmDoc30AccessClientSeed
1.3.6.1.4.1.4115.1.3.1.1.2.3.5.5 1.3.6.1.4.1.4115.1.3.4.1.2.3
arrisCmDevSinglePasswd arrisCmDoc30AccessSinglePassword
1.3.6.1.4.1.4115.1.3.1.1.2.3.22 1.3.6.1.4.1.4115.1.3.4.1.2.4
arrisCmDevHttpLanAccess arrisCmDoc30AccessHttpLan
1.3.6.1.4.1.4115.1.3.1.1.2.3.5.3 1.3.6.1.4.1.4115.1.3.4.1.2.5
arrisCmDevHttpWanAccess arrisCmDoc30AccessHttpWan
1.3.6.1.4.1.4115.1.3.1.1.2.3.5.4 1.3.6.1.4.1.4115.1.3.4.1.2.6
arrisCmDevSwTable arrisCmDoc30SwTable
1.3.6.1.4.1.4115.1.3.3.1.4.1 1.3.6.1.4.1.4115.1.3.4.1.5.1
arrisCmDevSwCustomerLoadId arrisCmDoc30SwCustomerLoadId
1.3.6.1.4.1.4115.1.3.3.1.4.1.1.2 1.3.6.1.4.1.4115.1.3.4.1.5.1.1.2
arrisCmDevSwHwModel arrisCmDoc30SwHwModel
1.3.6.1.4.1.4115.1.3.3.1.4.1.1.3 1.3.6.1.4.1.4115.1.3.4.1.5.1.1.3
arrisCmDevSwHwRev arrisCmDoc30SwHwRev
1.3.6.1.4.1.4115.1.3.3.1.4.1.1.4 1.3.6.1.4.1.4115.1.3.4.1.5.1.1.4
arrisCmDevSwFilename arrisCmDoc30SwFilename
1.3.6.1.4.1.4115.1.3.3.1.4.1.1.6 1.3.6.1.4.1.4115.1.3.4.1.5.1.1.5
arrisCmDevSwServerAddressType arrisCmDoc30SwServerAddressType
1.3.6.1.4.1.4115.1.3.3.1.4.1.1.7 1.3.6.1.4.1.4115.1.3.4.1.5.1.1.6
arrisCmDevSwServerAddress arrisCmDoc30SwServerAddress
1.3.6.1.4.1.4115.1.3.3.1.4.1.1.8 1.3.6.1.4.1.4115.1.3.4.1.5.1.1.7
ppCfgMtaFeatureSwitch
The eDVA Feature Switch. See ‘‘eDVA Feature Switch’’ on
page 84 for details.
ppCfgPortTable Objects
ppSurvPortTable Objects
ARRIS-MTA-MIB The following MIB objects from the ARRIS-MTA-MIB are supported. Bat-
(non-battery) tery-related objects are listed below.
arrisMtaDevControl Objects
arrisMtaDevEnableCallSigLastMsgRpt
Enables or disables reporting of the CallP signaling ‘‘last message’’
to the MIB objects arrisMtaDevSignalingLastMsg1 through arris-
MtaDevSignalingLastMsg16. Together the sixteen objects contain
a signaling message up to 4000 bytes long. Each object contains a
255-byte segment of the message. If the message does not require
all sixteen MIBs, then the empty objects display ‘‘Buffer is empty.’’
The default value is disable(0).
arrisMtaDevNsadSwDnldStatus
(read-only) Displays the current firmware download status:
download-Idle(0)
Indicates that the firmware download has completed. This
value is also set at startup.
download-Acceptance-In-Progress(1)
The unit is currently downloading the firmware in the back-
ground.
download-Application-Pending(2)
Indicates that the load has been downloaded and accepted but
is waiting to be applied.
This MIB object is only valid if the arrisMtaDevSwDnldNoSvc-
Impact object is set to enabled(1).
arrisMtaDevRestoreNvmFactoryDefault
Set this object to true(1) to reset the NVM to default values.
arrisMtaDevTrace Objects
arrisMtaDevRtpPercentPktsLostTotal
(read-only) This MIB object reports the percentage of RTP packets
lost since the MTA was last started up or reset. This value repre-
sents the total number of packets lost for all endpoints combined. It
is calculated from values obtained from the signaling end of call sta-
tistics. Set the arrisMtaDevResetCallStats object to true(1) to
clear this counter.
The value of this object is expressed in increments of 1/100 percent.
For example, a value of 1745 means that 17.45% of the packets
were lost.
arrisMtaDevProvState
(read-only) Reports the current provisioning state of the MTA:
• dhcpBound(1)
• dnsReqProvSvrIP(2)
• kdcHostNameDnsReq(3)
• kdcHostNameDnsRply(4)
• kdcIpDnsReq(5)
• kdcIpDnsRply(6)
• asReqSent(7)
• asRplyRcvd(8)
• tgsReqSent(9)
• tgsRplyRcvd(10)
• apReqSent(11)
• apRplyRcvd(12)
• enrollmentInform(13)
• cfgUrlSet(14)
• dnsReqTftpSvrIp(15)
• cfgFileReq(16)
• rcvCfgFile(17)
• syslogMsgProvComplete(18)
• statusInform(19)
• provcomplete(20)
arrisMtaDevSWUpgradeStatus
(read-only) Reports the current software upgrade status of the
device:
• inProgress(1)
• completeFromProvisioning(2)
• completeFromMgt(3)
• failed(4)
• other(5)
arrisMtaDevSignalingAvgLatency
(read-only) The average latency or delay, in milliseconds, for
responses to signaling messages. It is calculated from values
obtained from the signaling end of call statistics. Set the arrisMta-
DevResetCallStats object to true(1) to clear this counter.
arrisMtaDevSignalingTxSuccessfulMsgCnt
(read-only) Reports the total number of successful signaling mes-
sages sent from the eDVA. Set the arrisMtaDevResetCallStats
object to true(1) to clear this counter.
arrisMtaDevSignalingRxSuccessfulMsgCnt
(read-only) Reports the total number of successful signaling mes-
sages received by the MTA. Set the arrisMtaDevResetCallStats
object to true(1) to clear this counter.
arrisMtaDevSignalingTxNAKCnt
(read-only) Reports the total number of negative acknowledgement
signaling messages (NAKmessages) sent from the MTA. Set the
arrisMtaDevResetCallStats object to true(1) to clear this counter.
arrisMtaDevSignalingRxNAKCnt
(read-only) Reports the total number of negative acknowledgement
signaling messages (NAKmessages) received by the MTA. Set the
arrisMtaDevResetCallStats object to true(1) to clear this counter.
arrisMtaDevSignalingRxNoACKCnt
(read-only) Reports the total number of ’no acknowledgement’ sig-
naling messages received by the MTA. Set the arrisMtaDevReset-
CallStats object to true(1) to clear this counter.
arrisMtaDevSignalingLastMsg1–16
(read-only) These objects contain a 255-byte segment of the CallP
last signaling message sent or received. The sixteen objects
together can display a signaling message as large as 4000 bytes. If
the message does not require all sixteen objects, then the empty
objects display the value ‘‘Buffer is empty.’’
Use arrisMtaDevEnableCallSigLastMsgRpt to enable or disable
reporting of the CallP signaling last message.
arrisMtaDevRtpPktsLostTotal
(read-only) The number of RTP packets lost since the MTA was last
started up or reset. This value represents the total number of pack-
ets lost for all endpoints combined. It is calculated from values
obtained from the signaling end of call statistics. Set the arrisMta-
DevResetCallStats object to true(1) to clear this counter.
arrisMtaDevLastCallStartTime
(read-only) The last call start time from the eDVA.
arrisMtaDevLastCallEndTime
(read-only) The last call end time from the eDVA.
arrisMtaDevCallStatsTable
This table reports various end of call statistics. All objects in this table are
read-only, and are indexed by line number.
arrisMtaDevCallStatsRtpTxPkts
The total number of RTP packets sent from the endpoint during the
most recent call. This value is obtained from the signaling end-of-
call statistics.
arrisMtaDevCallStatsRtpRxPkts
The total number of RTP packets received by the endpoint during
the most recent call. This value is obtained from the signaling end-
of-call statistics.
arrisMtaDevCallStatsRtpPercentPktsLost
The percentage of RTP packets lost during the most recent call.
This value is obtained from the signaling end-of-call statistics.
The value of this object is expressed in increments of 1/100 percent.
For example, a value of 1745 means that 17.45% of the packets
were lost.
arrisMtaDevCallStatsAvgJitter
The average jitter measurement, in milliseconds, during the most
recent call. This value is obtained from the signaling end-of-call
statistics.
arrisMtaDevCallStatsMaxJitter
The maximum jitter measurement, in milliseconds, during the most
recent call. This value is obtained from DSP statistics.
arrisMtaDevCallStatsAvgLatency
The average latency, in milliseconds, observed during the most
recent call. This value is obtained from the signaling end-of-call
statistics.
arrisMtaDevCallStatsHookStatus
The hook status for each endpoint: onHook(0) or offHook(1).
Note: The disconnected state is not a valid return value for this MIB
object.
arrisMtaDevCallStatsSLICStatus
The over temperature condition of the SLIC chips: normal(0) or
overtemp(1).
arrisMtaDevCallStatsEndPntOpStatus
The current operational status for each endpoint. up(1) (ready to
pass packets), down(2), or testing(3) (in some test mode). This
object obtains its value from ifAdminOperStatus.
arrisMtaDevCallStatsLineSubState
The current sub-state for each line: normal(0), diagsPending(1),
diagsFailed(2), lcProtection(3), or dspFail(4). This object obtains
its value from the lineRec.
arrisMtaDevParameters
These objects provide information about E-UE and line parameters. All
objects in this group are read-only.
arrisMtaDevMaxCpeAllowed
Reflects the ‘‘MaxCpeAllowed’’ parameter in the CM config file.
arrisMtaDevNetworkAccess
Reflects the ‘‘NetworkAccess’’ parameter set in the CM config file:
no(0) or yes(1).
arrisMtaDevQosMode
Reflects the setting of the DSx DQoS bit (0x00004000) in the CallP
Feature Switch: bestEffort-FullDQos-PCMM(0) or dsxMode(1).
arrisMtaDevEventFormat
The PacketCable event format in use: pktc10(0) (PacketCable 1.0)
or pktc15(1) (PacketCable 1.5).
arrisMtaDevLineParameterTable
arrisMtaDevActiveConnections
The number of active connections for a particular line. Active con-
nections include receive-only, send-only, and send/receive; but not
inactive.
arrisMtaDevLineMWIActive
The MWI status for the line.
arrisMtaDevLineRTCPXR
Indicates whether or not RTCP-XR is configured: disabled(0) or
enabled(1). The setting is based on the value of the arrisMtaDev-
VqmEnableRemote and pktcEDVACodecRTCPXR objects accord-
ing to the following table:
arrisMtaDevLineRTCPXR
arrisMtaDevVqmEnableRemote pktcEDVACodecRTCPXR(1)
PC2.0 Legacy SIP NCS
normal true enabled disabled disabled
normal false disabled(2) disabled(2) disabled(3)
forceDisable true disabled disabled disabled
forceDisable false disabled disabled disabled
forceEnable true enabled enabled enabled
forceEnable false enabled enabled enabled
(1)The pktcEDVACodecRTCPXR object is applicable only to PC2.0.
(2)Though arrisMTADevLineRTCPXR is set to disabled, the remote may still request RTCP-XR to be transmitted which
will be honored.
(3) Though arrisMTADevLineRTCPXR is set to disabled, the Call Agent may instruct the MTA to request RTCP-XR
through NCS signaling.
arrisMtaDevLineRTCPXRNegotiatedConnectionA
The negotiation status of RTCP-XR for a particular line’s A (i.e.
first) connection. The status is one of the following:
callNotInProgress(0)
no active call is utilizing this connection/call leg.
notNegotiated(1)
RTCP-XR is not negotiated to be sent on this call leg.
negotiated(2)
RTCP-XR is negotiated to be sent on this call leg.
arrisMtaDevLineRTCPXRNegotiatedConnectionB
The negotiation status of RTCP-XR for a particular line’s B (i.e.
second) connection. The status is identical to the A connection
above.
arrisMtaDevUpSvcFlowParameterTable
This table reports various Upstream Service Flow parameters on the eMTA.
arrisMtaDevDocsQosParamUpSvcFlowSFID
The upstream service flow SFID for a valid service flow index.
arrisMtaDevDocsQosParamUpSvcFlowSchedulingType
The upstream service flow scheduling type for a valid service flow
index.
arrisMtaDevVqm Objects
arrisMtaDevVqmCallNumberTable
Voice Quality Metric history on a per call number basis. See ‘‘Man-
aging Voice Quality Monitoring’’ on page 371 for details.
arrisMtaDevVqmCallNumberIdentifier
Specifies the call number for Voice Quality Metrics reporting. Valid
IDs are obtained from arrisMtaDevVqmCallNumberIds.
arrisMtaDevVqmMetricTable
Voice Quality Metrics pertaining to a particular call number. See
‘‘Managing Voice Quality Monitoring’’ on page 371 for details.
arrisMtaDevVqmEnableRemote
Determines the policy to control Remote Voice Metrics (XR):
• normal(0) (default) — obey directives from the Call Server.
• forceDisable(1) — disables XR, overriding any directive from
the Call Server.
• forceEnable(2) — enables XR, overriding any directive from the
Call Server.
• default(3) — resets this object to the default and removes persis-
tence.
The value of this object is persistent if it is set after configuration.
arrisMtaDevVqmThresholdEnable
The maximum number of logs allowed to be sent in a report when a
threshold is exceeded. The more logs that are allowed, the more
metrics that can be reported. A value of 0 (default) disables thresh-
old reporting.
arrisMtaDevOperationalSetup Objects
arrisMtaDevVPNomJitterBuffer
The Voice Playout nominal jitter buffer size, in terms of packetiza-
tion rate: packetizationRatex1(1) (default), packetizationRa-
tex2(2), packetizationRatex3(3), or packetizationRatex4(4).
arrisMtaDevVPJitterBufferMode
The Voice Playout jitter buffer mode: adaptive(1) (default) or
fixed(2).
arrisMtaDevRTPTxQueueSize
Sets the RTP transmit queue size. Default: 2.
arrisMtaDevEchoCancellerTailLength
The length, in milliseconds, of the echo canceller tail: eightMs(1) or
thirtyTwoMs(2) (default). This object can be set only in the eDVA
configuration file.
arrisMtaDevDspHandleNonPhaseReversedTone
Configures handling of the DSP non-phase reversed tone detection:
off(1)
ignores tone detection.
onECANEnable(2)
(default) the non-phase reversed CED tone is handled with the
echo canceller enabled.
onECANDisabled(3)
the non-phase reversed CED tone is handled with the echo
canceller disabled.
arrisMtaDevProvMethodIndicator
The method used to provision the device. This object can be set
only in the configuration file. The following provisioning methods
are supported:
docsisOnly(0)
DOCSIS-only provisioning.
fullPacketCable(1)
PacketCable 1.5 flows. The arrisMtaDevPacketcableProvi-
sioningFlow object specifies which flow is in use.
packetCableMinusKDC(2)
same as full PacketCable, except with IPSEC and SNMPv3
disabled.
cps(3)
compatible with CPS2000 (SNMPv2; IPsec disabled).
gupi(4)
SNMPv2, with no SNMP Informs and IPsec disabled.
singleMAC(5)
single configuration file (SNMPv2, single IP address, single
MAC address, no SNMP Informs, IPsec disabled).
basic1(6)
Basic1 SNMPv2, without SNMP Enrollment, Status Informs,
or Hash.
basic2(7)
ARRIS Basic2 SNMPv2, without SNMP Enrollment Inform
or Hash.
gupiEncryptedMtaConfig(8)
Same as gupi(4), with the MTA config file encrypted using an
Arris-proprietary method.
gupiMacMta(9)
GUPI provisioning that uses the MTA MAC address as the
MTA configuration file name. Example: 1337c0ded00d.bin
gupiEncryptedMacMta(10)
GUPI encrypted MTA configuration provisioning that uses the
MTA MAC address as the MTA config file name.
gupiTftpSvrOverride(11)
GUPI provisioning, where the FQDN of the MTA TFTP
server is expected to be present in the arrisMtaDe-
vTFTPServerAddrOverrideFQDN object.
arrisMtaCfgRTPDynPortStart
The starting value for a range of ports that is used dynamically
when sending out SIP RTP voice packets. This object and arrisMta-
CfgRTPDynPortEnd define the port range.
Default: 49152.
arrisMtaCfgRTPDynPortEnd
The ending value for a range of ports that is used dynamically when
sending out SIP RTP voice packets. The value of this object must
be higher than arrisMtaCfgRTPDynPortStart.
Default: 65535.
arrisMtaDevVPMaxJitterBuffer
Indicates the Voice Playout maximum jitter buffer: packetization-
Ratex1(1), packetizationRatex2(2), packetizationRatex3(3)
(default), or packetizationRatex4(4).
arrisMtaDevPacketcableProvisioningFlow
(read-only) Indicates the PacketCable simplified provisioning flow
for PacketCable 1.5 compliance:
secure(0)
PacketCable 1.5 Secure Flow
hybrid2(1)
PacketCable 1.5 Hybrid 2 Flow
hybrid1(2)
PacketCable 1.5 Hybrid 1 Flow
basic2(3)
PacketCable 1.5 Basic 2 Flow
basic1(4)
PacketCable 1.5 Basic 1 Flow
none(5)
ARRIS non-PacketCable 1.5 Flow
arrisMtaDevEnableIndexTenEleven
Set to enable(1) to use 10 and 11 as the ifIndex for lines 1 and 2.
Default behavior uses 9 and 10 for the ifIndex.
arrisMtaDevDspCpsSetting
Enables or disables ECAN fast constant power signal detection.
The default value of on(2) makes the echo canceller disengage
immediately when a high level constant power signal is detected.
arrisMtaDevVbdOverwriteLineBitmap
A bitmask that defines which lines use the VbdOverwriteJitter-
Buffer values for fax/modem jitter buffer settings. A value of 0 (the
default) affects no lines; 0x01 enables line 1, and so on.
arrisMtaDevVbdOverwriteMinJitterBuffer
When arrisMtaDevVbdOverwriteLineBitmap is set for the line,
this value is used as the minimun jitter buffer setting in all
modem/fax calls. Default: 20.
arrisMtaDevVbdOverwriteNomJitterBuffer
When arrisMtaDevVbdOverwriteLineBitmap is set for the line,
this value is used as the nominal jitter buffer setting in all
modem/fax calls. Default: 20.
arrisMtaDevVbdOverwriteMaxJitterBuffer
When arrisMtaDevVbdOverwriteLineBitmap is set for the line,
this value is used as the maximum jitter buffer setting in all
modem/fax calls. Default: 20.
arrisMtaDevEventHideFQDNandIPAddress
Set to enable(1) to hide the MTA FQDN and IP address on the
Event Log web page. Logging into the Advanced pages allows an
operator to view this information.
arrisMtaDevDhcpOptionOverride
Set to on(2) to disable DHCP option code 122/177 sub-option 3
value enforcement.
The default value, off(1), enforces DHCP option 122/177 sub-
option 3 value comparison checking. Typically, the value received
in the DHCP OFFER should not change in the DHCP ACK. DHCP
RENEW/REBIND values should be consistent with the value
received in the DHCP OFFER.
arrisMtaDevTFTPServerAddrOverrideFQDN
The FQDN of the TFTP server that delivers the MTA configuration
file, overriding the default TFTP server.
This can be used only with the gupiTftpSvrOverride(11) provision-
ing method.
arrisMtaDevDefaultReasonNoCIDName
The reason sent to the CPE when the Caller ID Name is not
included in the signal request. The default value is unavailable(0).
The following table shows the reason sent for each setting.
Value Reason Description
unavailable(0) ‘O’ Out of area
private(1) ‘P’ Private caller
sendnothing(2) NULL No reason sent
sdmf(3) number Number in NA SDMF format
excludeName(4) nothing No name parameters or reason
arrisMtaDevSipConfigFileURL
The URL of the SIP configuration file for re-downloading provi-
sioning and configuration parameters to this device.
arrisMtaDevSipDwnldConfig
Set to on(2) to enable a re-download of the SIP configuration file
parameters specified in the configuration file URL obtained from the
arrisMtaDevSipConfigFileURL object.
arrisMtaDevSpecialConfigurationOverrideEnable
A bitfield that enables proprietary features of the Arris eDVA. Cur-
rently, only 0x80000000 is supported, to enable DHCP Option 60
sub-option 18 override. The default value is 0.
arrisMtaDevRtcpTosValue
The value used in the IP ToS byte for RTCP packets.
arrisMtaDevAutomaticOsiDelay
The time, in 100ms increments, to wait after a DLCX is received
before determining whether an automatic OSI should be generated
to force a line disconnect.
Default: 50 (5 seconds). Use a value of 0 to send OSI immediately
(if there are no other connections on the line).
Note: This object takes effect only if the ppCfgMtaCallpFea-
tureSwitch has bit 0x20000000 set.
arrisMtaDevCustomJitterBufferEnabled
Set to on(1) to customize jitter buffer settings. When this setting is
off (the default), the jitter buffer size is set using the arrisM-
taDevVPNomJitterBuffer and arrisMtaDevVPMaxJitterBuffer
objects.
The default jitter buffer range depends on the setting of this object:
• When off(0), the defaults are (in ms):
minimum = [(packet rate *1) + 5]
nominal = minimum
maximum = [(packet rate * 3) + 5]
• When on(1), the defaults are:
minimum: 5
nominal: 10
maximum: 60
arrisMtaDevCustomMinJitterBuffer
The customized voice playout minimum jitter buffer size to use
when the arrisMtaDevCustomJitterBufferEnabled object is
enabled. Valid range: 5 (default) to 160, in increments of 5.
arrisMtaDevCustomNomJitterBuffer
The customized voice playout nominal jitter buffer size to use when
the arrisMtaDevCustomJitterBufferEnabled object is enabled.
Valid range: 5 to 160, in increments of 5. Default: 10.
arrisMtaDevCustomMaxJitterBuffer
The customized voice playout maximum jitter buffer size to use
when the arrisMtaDevCustomJitterBufferEnabled object is
enabled. Valid range: 5 to 160, in increments of 5. Default: 60.
arrisMtaDevEnableDHCPLog
Enables or disables MTA DHCP logging.
arrisMtaDevEnableMGCPLog
Enable or disables CallP signaling logging.
arrisMtaDevClearDHCPLog
Set to clear(1) to clear the MTA DHCP Logs.
arrisMtaDevClearMGCPLog
Set to clear(1) to clear the MTA MGCP Logs.
arrisMtaDevTDDReportToCMS
Enables or disables reporting of TDD detection events to the CMS.
The default is enable(1).
arrisMtaDevAutomaticCallResourceRecovery
The time, in seconds, to delay after an on-hook event before detect-
ing whether resources acquired while a call was active need to be
recovered on a line in the idle state. Set to to disable this feature.
arrisMtaDevOffHookFskDelay
The time, in milliseconds, to delay before sending the FSK to the
CPE. The delay starts upon receiving the ACK (DTMF D) from the
CPE in response to the CAS tone for Call Waiting (or Type 2) Caller
ID.
arrisMtaDevT38Timeout
The T.38 timeout, in seconds. The audio is muted for this period
before reporting T.38 failure events to the CMS. Default: 15.
arrisMtaDevSuperG3FaxRelay
Set to enable(1) to allow SuperG3 fax processing upon detection of
the V.21 CM or V.8 data signal. When enabled, the MTA handles
the detection of SuperG3 signaling to start the T.38 process. The
negotiation during call setup determines whether or not T.38 can be
used to send the fax.
When disabled (the default), the MTA still detects signaling for
SuperG3 fax, and the signal is used to setup the endpoint for
SuperG3 pass-thru fax transmission via G.711.
arrisMtaDevDTMFEndEventForceAscending
Enables or disables RFC 2833 DTMF end event duration force
ascending. The default is disabled.
arrisMtaDevDspHandleBellModemTone
Set to enable(1) to detect the Bell Modem Tone (2225 kHz). The
Bell Modem Tone is frequently used by older data modems, usually
in low speed setups. When enabled. the DSP detects the Bell
Modem Tone from either the local or network end. When disabled
(the default), the tone will be ignored.
arrisMtaDevDhcpSubOpt3Immediate
Set to on(2) to enable immediate comparison and handling of MTA
DHCP Option 122 sub-option 3. SNMP notifications are sent to the
new Provisioning SNMP Entity.
The default value is off(1).
arrisMtaDevMaxCallPServiceFlows
Used to limit the number of active calls (service flows). Outgoing
calls, incoming calls, and conference call legs are included in this
count. The eDVA ports can call each other without this limitation.
The default value is 0.
arrisMtaDevEndPntTable Objects
arrisMtaDevGainControl Objects
arrisMtaDevGainControlTxVoice
The transmit digital gain adjustment, in dBm, for voice. This value
does not effect the levels of local tones or FSK. Default: 0.
Note: Use caution when changing this object. Increasing or
decreasing the voice level by the larger numbers allowed in the
range may compromise voice quality.
arrisMtaDevGainControlRxVoice
The receive digital gain adjustment, in dBm, for voice. Default: 0.
arrisMtaDevLevelControl Objects
arrisMtaDevLevelControlOffHookFSK
The transmit digital gain setting, in dBm, for MTA-generated FSK
tones (CID and VMWI) while the line is off-hook. Default: −15.
arrisMtaDevLevelControlOffHookCAS
The transmit digital gain setting, in dBm, for MTA-generated CAS
tones (CID and VMWI) while the line is off-hook. Default: −15.
arrisMtaDevDiagLoopTable Objects
• diagnostics-results-pending(9)
• not-started(10)
• unsupported(11)
• ringer-test-warning(12)
When complete, the status is either diagnostics-passed(1) or the
first test failed. During the test, the status is always diagnostics-
results-pending(9).
arrisMtaDevDiagLoopHazardousPotentialTest
(read-only) The Hazardous Potential Test result for the last time that
loop diags were run.
arrisMtaDevDiagLoopForeignEmfTest
(read-only) The Foreign EMF Test result for the last time that loop
diags were run.
arrisMtaDevDiagLoopResistiveFaultsTest
(read-only) The Resistive Faults Test result for the last time that
loop diags were run.
arrisMtaDevDiagLoopReceiverOffHookTest
(read-only) The Receiver Off-hook Test result for the last time that
loop diags were run.
arrisMtaDevDiagLoopRingerTest
(read-only) The Ringer Test result for the last time that loop diags
were run.
arrisMtaDevPwrSupplyBase Objects
arrisMtaDevPwrSupplyControl Objects
These objects provide control and status information for the charger system.
arrisMtaDevPwrSupplyEnableDataShutdown
Set to disabled(2) to allow CPE interfaces (Ethernet and wifi, if
equipped) to provide service during a power outage. This reduces
battery hold-up time.
arrisMtaDevPwrSupplyLowBatteryThresh
Sets the low battery threshold, in 10 watt*minutes increments. A
charge below this threshold indicates a low battery condition. The
initial default value is equivalent to 1 hour of holdup time.
arrisMtaDevPwrSupplyTypicalIdlePwr
(read-only) The typical idle power, in 50 mW increments. A nomi-
nal value is loaded when the modem powers up. This value is used
in conjunction with the Tested Battery Capacity, Low Battery
Threshold, and the Replace Battery Threshold to determine when to
raise the Replace Battery or Low Battery alarms.
arrisMtaDevPwrSupplyReplaceBatThresh
The minimum acceptable battery charge, in 10 watt*minutes incre-
ments, needed to achieve the desired End of Life hold-up time,
based on typical idle power. If the Tested Battery Capacity minus
the Charge Hysteresis loss (20%) is less than this value, the modem
raises the Replace Battery alarm. The initial default value provides
1 hour of holdup time.
arrisMtaDevPwrSupplyChargeState
The ‘‘full charge’’ state, in 10 watt*minutes increments. The initial
default value is 80% of the Rated Battery Capacity. Writing to this
object forces the charger to start a discharge/charge cycle, to charge
the battery to the specified level.
Be careful when changing this value. Specifying a higher charge
level may increase hold-up times, but can reduce overall battery life.
arrisMtaDevPwrSupplyBatteryTest
Controls the battery test schedule:
testScheduled(0)
Resumes the battery test scheduler at its current value. When
read, this value indicates that the battery test runs when the
scheduled time expires.
disableAutoTesting(1)
Freezes the battery test scheduler at its current value. When
read, this value indicates that the battery test is suspended.
Removing and replacing the battery forces the charger to run
the test one time. To resume normal operation, set the value to
testScheduled(0) or testInProgress(2).
testInProgress(2)
Starts the battery test cycle immediately, and resets the test
scheduler to its default value of 180 days. When read, this
value indicates a test in progress.
testPending(3)
(read-only) A battery test was in progress, and either AC
power was lost or a full charge was requested.
arrisMtaDevPwrSupplyConfigRunTime
The estimated battery hold-up time, in minutes, based on the typical
idle power and the programmed battery charge setting. The battery
hold-up time may be adjusted using this object. By setting the hold-
up time to a lower value, the total service life of the battery is
extended. Increasing the hold-up time decreases the total service
life of the battery.
Note: This value can only be set in multiples of 5 minutes. Setting a
value greater than arrisMtaDevPwrSupplyBatAvailableMinutes
does not extend the hold-up time beyond that specified by arrisMta-
DevPwrSupplyBatAvailableMinutes.
arrisMtaDevPwrSupplyConfigReplaceBatTime
The replace battery threshold, in terms of minutes of hold-up time.
If a battery’s capacity has degraded to a point where its hold-up time
is below this threshold, the Replace Battery condition becomes
active.
This value can only be set to multiples of 5 minutes. The default
value at power up is 60 minutes.
arrisMtaDevPwrSupplyConfigReplaceBatTime2
(currently unused) Same as arrisMtaDevPwrSupplyConfigRe-
placeBatTime, but for a second battery.
arrisMtaDevPwrSupplyOverTempAlarmControl
Set to enable(1) to issue an Over Temperature Alarm if the charger
exceeds the temperature specified in arrisMtaDevPwrSupply-
OverTempAlarmThreshold, and to shut down the charger if the
temperature exceeds 90°C.
arrisMtaDevPwrSupplyOverTempAlarmThreshold
The temperature threshold, in degrees C, for the Over Temperature
alarm.
arrisMtaDevPwrSupplyTemperature
(read-only) The current charger temperature, in degrees C. This is
available only when arrisMtaDevPwrSupplyOverTempAlarm-
Control is enabled.
arrisMtaDevPwrSupplyHiTempBatteryShutdownControl
Set to enable(1) to turn off the battery if the temperature reaches
75°C.
arrisMtaDevPwrSupplyHighestTemperature
(read-only) The highest recorded battery charger temperature, in
degrees C. This is available only when arrisMtaDevPwrSupply-
OverTempAlarmControl is enabled.
arrisMtaDevPwrSupplyHighestTemperatureTime
(read-only) The time and date when the highest temperature was
recorded.
arrisMtaDevPwrSupplyHighestTemperatureClear
Set to clear(1) to clear current values of arrisMtaDevPwrSupply-
HighestTemperature and arrisMtaDevPwrSupplyHighestTemper-
atureTime. These objects reset to current values within 4 seconds.
arrisMtaDevPwrSupplyControlChargerReset
Set to true(1) to reset the battery charger.
Note: Resetting the battery charger during an AC Fail condition
immediately shuts down the unit.
arrisMtaDevPwrSupplyTimers Objects
arrisMtaDevPwrSupplyStats Objects
These object provide battery and charger statistics. All objects in this group
are read-only.
arrisMtaDevPwrSupplyBatteryTestTime
The present value of the test timer scheduler, in days. If the value is
0xFF (255), the timer has been paused.
arrisMtaDevPwrSupplyRatedBatCapacity
The rated capacity, in 10 watt*minutes increments, of the battery.
arrisMtaDevPwrSupplyTestedBatCapacity
The measured battery capacity, in 10 watt*minutes increments, as
measured by the last battery test cycle.
arrisMtaDevPwrSupplyBatStateOfCharge
The present battery state of charge, in 10 watt*minutes increments.
This value is approximate and is re-calibrated following a battery
test cycle.
arrisMtaDevPwrSupplyReadBatteryPwr
The present load power, in 50mW increments, over an eight-second
moving average. This is the power being removed (when running
on battery power) or applied to the battery (when charging).
arrisMtaDevPwrSupplySecondsOnBattery
The time, in seconds, that the modem has been using battery power.
arrisMtaDevPwrSupplyBatRatedMinutes
The estimated rated hold-up time, in minutes, based on typical idle
power and the rated capacity of the battery when fully charged.
arrisMtaDevPwrSupplyBatAvailableMinutes
The estimated available hold-up time, in minutes, based on typical
idle power and the tested capacity of the battery when fully charged.
arrisMtaDevPwrSupplySecondsOnBattery2
Same as arrisMtaDevPwrSupplySecondsOnBattery, but for a sec-
ond battery.
arrisMtaDevPwrSupplyBatRatedMinutes2
Same as arrisMtaDevPwrSupplyBatRatedMinutes, but for a sec-
ond battery.
arrisMtaDevPwrSupplyBatAvailableMinutes2
Same as arrisMtaDevPwrSupplyBatAvailableMinutes, but for a
second battery.
arrisMtaDevPwrSupplyTelemetryValues
Power supply telemetry values, used by ARRIS technical support
when troubleshooting a battery issue.
arrisMtaDevBatteryStatusTable
The Power Supply telemetry table. All objects in this table are read-only.
arrisMtaDevBatteryOperState
The current operational state of the battery:
• unavailable(0)
• invalid(1)
• shutdownWarning(2)
• batteryReversedShorted(3)
• batteryLow-replaceBattery-acFail(4)
• batteryLow-replaceBattery(5)
• batteryLow-acFail(6)
• batteryLow(7)
• batteryMissing(8)
• acFail-replaceBattery(9)
• replaceBattery(10)
• acFail(11)
• normal(12)
• testInProgress(13)
• chargerFailure(14)
arrisMtaDevBatteryLastStateChange
The value of sysUpTime when the battery entered its current opera-
tional state.
arrisMtaDevBatteryOperSubState
The current sub-state of the battery. The sub-state is not designed to
match the arrisMtaDevBatteryOperState but to provide additional
information about the charger status.
arrisMtaDevBatteryOrderingCode
The ARRIS ordering code for the battery.
arrisMtaDevBatteryEprom
EPROM information for the battery.
ARRIS-ROUTER-MIB Objects
arrisRouterWan- The following objects configure and control the router’s WAN connection.
Config Objects arrisRouterWanConnType
The address type of the WAN connection; one of: unknown(0),
dynamic(1), static(2), l2tpStatic(5), l2tpDynamic(6).
arrisRouterWanConnHostName
The host name of the router.
arrisRouterWanConnDomainName
The domain name of the router.
arrisRouterWanMTUSize
The MTU size for the WAN connection.
Valid range: 256 to 1500, or 0 to use the negotiated MTU size.
arrisRouterWanStaticFreeIdx
(read-only) The lowest available index that can be used to create a
new row/instance in the arrisRouterWanStaticTable. A value of
zero indicates that there are no more rows available.
arrisRouterWanIFMacAddr
The MAC address of the WAN interface.
arrisRouterWanConnTypeV6
For IPv6 installations, the WAN connection type: unknown(0),
dynamic(1), or static(2).
arrisRouterWanIPProvMode
The gateway initialization mode: disabledBridge(0), ipv4(1),
ipv6(2), or dualStack(3).
arrisRouterWanCurrentTable Entries
This table contains information for each WAN IP address. In some environ-
ments, there may be both an IPv4 and IPv6 address or multiple IPv6
addresses. Up to four entries may appear. All objects in this table are read-
only
arrisRouterWanCurrentIPAddrType
The static IP address type.
arrisRouterWanCurrentIPAddr
The static IP address for the WAN connection.
arrisRouterWanCurrentPrefix
The netmask (prefix) for the WAN connection.
arrisRouterWanCurrentGWType
The gateway address type for the WAN connection.
arrisRouterWanCurrentGW
The gateway address for the WAN connection.
arrisRouterWanCurrentIPType
The IP address type: unknown(0), dynamic(1), or static(2).
arrisRouterWanCurrentNetMask
For IPv4 addresses, the netmask for the WAN connection.
arrisRouterWanCurrentPrefixDelegationV6
For IPv6 addresses, the prefix or initial bits of the address given to
the gateway to delegate to its attached CPEs.
arrisRouterWanCurrentPrefixDelegationV6Len
For IPv6 addresses, the length for the prefix to be delegated to
attached CPEs.
arrisRouterWanCurrentPreferredLifetimeV6
For IPv6 addresses, the preferred lifetime (in seconds) for the
assigned IPv6 address of the router.
arrisRouterWanCurrentValidLifetimeV6
For IPv6 addresses, the valid lifetime (in seconds) for the assigned
IPv6 address of the router.
arrisRouterWanStaticTable Entries
This table contains information for a specific static WAN IP address. This ta-
ble supports only a single entry.
arrisRouterWanStaticIPAddrType
The IP address type for the static WAN connection.
arrisRouterWanStaticIPAddr
The static IP address for the WAN connection.
arrisRouterWanStaticPrefix
The netmask (prefix) for the WAN connection.
arrisRouterWanStaticGatewayType
The gateway address type for the WAN connection.
arrisRouterWanStaticGateway
The gateway address for the WAN connection.
arrisRouterWanStaticRowStatus
The RowStatus object used to add or remove rows from the table.
arrisRouterWanDelegatedPrefixLength
For IPv6 static addresses, the length of IPv6 delegated prefix.
arrisRouterWanDelegatedPrefix
For IPv6 static addresses, the IPv6 delegated prefix.
arrisRouterWanTunnelObjects
arrisRouterWanTunnelAddrType
The address type (IPv4 or IPv6) of the L2TP server.
arrisRouterWanTunnelAddr
The IP address of the L2TP server. This object or arrisRouterWan-
TunnelHostName must be set.
arrisRouterWanTunnelHostName
The host name of the L2TP server. This object or arrisRouterWan-
TunnelAddr must be set.
arrisRouterWanEnableKeepAlive
Set to true(1) to enable keep-alive timeout.
arrisRouterWanKeepAliveTimeout
The L2TP keep-alive time, in seconds. Default: 30.
arrisRouterWanDNSObjects
These objects provide information about DNS services available to the WAN
interface.
arrisRouterWanUseAutoDNS
Set to true(1) to use automatic DNS servers as specified by DHCP.
arrisRouterWanStaticDNSFreeIdx
(read-only) The first free index available for adding a row to the
arrisRouterWanStaticDNSTable. A value of 0 means no rows are
available.
arrisRouterWanCurrentDNSTable Objects
This table contains the IP addresses of the current DNS servers. The servers
may be dynamically obtained from the WAN DHCP server, or statically con-
figured in the arrisRouterWanStaticDNSTable. Up to four entries are avail-
able; the lowest index is checked first for DNS lookups.
arrisRouterWanCurrentDNSIPAddrType
(read-only) The IP address type of the DNS server (IPv4 or IPv6).
arrisRouterWanCurrentDNSIPAddr
(read-only) The IP address of the DNS server.
arrisRouterWanStaticDNSTable Objects
arrisRouterWanStaticDNSIPAddrType
The IP address type of the DNS server (IPv4 or IPv6).
arrisRouterWanStaticDNSIPAddr
The IP address of the DNS server.
arrisRouterWanStaticDNSRowStatus
The RowStatus used to add and remove rows.
arrisRouterWanDHCPObjects
These objects provide information about the current DHCP lease for the
WAN interface.
arrisRouterWanRenewLease
Set to apply(1) to renew the primary public WAN DHCP lease.
arrisRouterWanReleaseLease
Set to apply(1) to release the primary public WAN DHCP lease.
arrisRouterWanDHCPDuration
(read-only) The time, in seconds, that the current WAN DHCP lease
is valid.
arrisRouterWanDHCPExpire
(read-only) The date and time when the current WAN DHCP lease
expires.
arrisRouterWanRenewLeaseV6
For IPv6 installations, set to apply(1) to renew the primary public
WAN DHCP lease.
arrisRouterWanReleaseLeaseV6
For IPv6 installations, set to apply(1) to release the primary public
WAN DHCP lease.
arrisRouterWanDHCPDurationV6
(read-only) The time, in seconds, that the current WAN DHCPv6
lease is valid.
arrisRouterWanDHCPExpireV6
(read-only) The date and time when the current WAN DHCPv6
lease expires.
arrisRouterDSLiteWanObjects
arrisRouterLan- The following objects configure and control the LAN interfaces.
Config Objects arrisRouterLanSettings
Applies LAN settings as follows:
doNothing(0)
No effect. Reading this object always returns doNothing(0).
applyPrimaryLan(1)
Applies settings for the Ethernet and subscriber wifi.
applyGuestLans(2)
Applies settings for the non-subscriber wifi LANs.
applyAllLans(3)
Applies settings for all networks. The network will be
restarted.
resetDefaults(11)
Resets all values in the arrisRouterLanTable and arris-
RouterWirelessCfg to their defaults.
restartWLAN(12)
Restarts only the wireless LAN interfaces.
revertSettings(10)
Clears all modifications, restoring the values from non-volatile
memory.
Note: If applying settings fails, the action can be retried. Modified
settings are kept until the gateway is rebooted or revertSettings(10)
is used.
arrisRouterLanSrvTable Entries
arrisRouterLanGatewayIp2Type
The IP address type of the Gateway for a specific network.
arrisRouterLanGatewayIp2
The IP address of the Gateway for a specific network.
arrisRouterLanVLanID
The VLAN ID to be used for this LAN. A value of zero disables
VLAN functionality on this LAN.
arrisRouterLanUseDHCP
Enables or disables the local DHCP server for this LAN.
arrisRouterLanStartDHCPType
The IP address type of the first address in the DHCP pool.
arrisRouterLanStartDHCP
The first IP address in the range of IP addresses assigned by the
DHCP server.
arrisRouterLanEndDHCPType
The IP address type of the last address in the DHCP pool.
arrisRouterLanEndDHCP
The last IP address in the range of IP addresses assigned by the
DHCP server.
arrisRouterLanLeaseTime
The lease time, in seconds, for addresses assigned by the DHCP
server.
arrisRouterLanDomainName
(optional) The domain name for this LAN.
arrisRouterLanRateLimit
Enables or disables rate limiting on this LAN.
arrisRouterLanDownRateLimit
The downlink limiting rate. Use zero for no rate limiting.
arrisRouterLanUpRateLimit
The uplink limiting rate. Use zero for no rate limiting.
arrisRouterLanRelayDNS
Controls DNS relay. In this version of Touchstone firmware, DNS
relay is always enabled.
arrisRouterLanIPv6Mode
The IPv6 setting: linkLocalOnly(1) or siteLocalOnly(2).
arrisRouterLanPassThru
The LAN routing mode:
passThru(1)
Puts the device into non-bridged mode with routing and NAT
disabled.
routedNAT(2)
Puts the device into bridged (routed) mode with Network
Address Translation (NAT) enabled.
routedNoNAT(3)
Puts the device into bridged (routed) mode with Network
Address Translation (NAT) disabled.
arrisRouterLanFirewallOn
Enables or disables the firewall for this LAN.
arrisRouterLanUPnPEnable
Enables or disables UPnP for this LAN.
arrisRouterLanCPEAging
The time, in seconds, for aging-out dynamically learned forwarding
information. The default value of zero disables aging-out entries.
arrisRouterLanOverrideDNS
Enables or disables DNS override. If DNS override is enabled, the
IP addresses in arrisRouterLanDNSTable are passed to LAN
clients using DHCP. Otherwise, the DNS servers received by the
WAN connection are passed to the LAN clients.
arrisRouterLanNatAlgsEnabled
A bitmask that specifies which NAT Application Layer Gateway
(ALG) supplements are enabled on this device. The following bits
are available:
Bit Direction Protocol Port
rsvp(0) US/DS IP 46
ftp(1) US/DS TCP 21
tftp(2) US UDP 17
kerb88(3) US UDP 88
netBiosDgm(4) US UDP 138
ike(5) US/DS UDP 500
rtsp(6) US/DS TCP 554
kerb1293(7) US UDP 1293
h225(8) US/DS TCP 1720
pptp(9) US/DS TCP 1723
msn(10) US/DS TCP 1863
sip(11) US UDP 5060
icq(12) US TCP 5190
irc666x(13) US TCP 6661–6669
icqTalk(14) US/DS UDP 6701
net2Phone(15) US/DS UDP 6801
irc7000(16) US TCP 7000
irc8000(17) US TCP 8000
arrisRouterLanLeaseTimeV6
For IPv6 configurations, the lease time for IP addresses provided by
the router’s DHCPv6 server.
arrisRouterLanLinkLocalAddressV6
For IPv6 configurations, the link local IPv6 address.
arrisRouterLanDNSRelayV6
For IPv6 configurations, enables or disables DNS relay.
arrisRouterLanDNSOverrideV6
For IPv6 configurations, enables or disables DNS override. When
DNS override is enabled, the IPv6 addresses in the arrisRouter-
LanDNSTable are passed to LAN clients using DHCPv6. Other-
wise, the DNS servers received by the WAN connection are passed
to the LAN clients.
arrisRouterLanDNSTable
This table provides DNS server information for a specific LAN. The table is
indexed by the ifIndex of the LAN and an internal index. The current imple-
mentation supports two DNS servers per interface.
arrisRouterLanDNSIPAddrType
The IP address type for the DNS server.
arrisRouterLanDNSIPAddr
The IP address of the DNS server.
arrisRouterLanDNSRowStatus
Use this object to add or remove DNS row entries.
arrisRouterLanEtherPortTable
This table provides configuration information for the physical Ethernet ports.
arrisRouterLanEtherPortIFIndex
(read-only) The ifIndex of this Ethernet interface.
arrisRouterLanEtherPortEnabled
Enables or disables this Ethernet port.
arrisRouterLanEtherPortDuplex
Configures the duplex setting for this Ethernet port: halfDuplex(0)
or fullDuplex(1). The device may need to be restarted to apply this
setting.
arrisRouterLanEtherPortSpeed
Configures the speed, in MB/sec, for this Ethernet port: 10, 100, or
1000. This object applies only if auto-negotiate is off.
To query the actual current speed of the interface, use the ifSpeed
object. The device may need to be restarted to apply this setting.
arrisRouterLanEtherPortAuto
Configures the auto-negotiate setting for this Ethernet port: manual-
Configure(0) or autoNegotiate(1).
arrisRouterClientObjects
These objects provide information about clients attached to the LAN inter-
faces.
arrisRouterLanClientCount
(read-only) The current number of clients on this LAN. This corre-
sponds to the number of active rows in the arrisRouterLanCurrent-
ClientTable.
arrisRouterLanCustomCount
(read-only) The number of custom maps of LAN clients to friendly
names and other attributes. This corresponds to the number of rows
in the arrisRouterLanClientCustomTable.
arrisRouterLanClientTable
arrisRouterLanClientType
(read-only) The type of IP address: dynamic(1) or static(5). When
creating or editing an entry, this object is always static(5).
arrisRouterLanClientLeaseStart
(read-only) The time and date when this lease started. For static
entries, this is the time and date when the row was created (if
known).
arrisRouterLanClientLeaseEnd
(read-only) The time and date when this lease expires. If the arris-
RouterLanClientType is static, this object returns an unspecified
time and date.
arrisRouterLanClientStatus
(read-only) The status of the IP interface: down(0) or up(1).
arrisRouterLanClientInfLease
(read-only) Returns true(1) if the lease is infinite, false(2) other-
wise. This applies only to dynamic leases. Rows for static items
always return notApplicable(0).
arrisRouterLanClientLeaseState
(read-only) The lease state: leaseStateAvailable(0), leaseS-
tateArping(1), leaseStateOffering(2), leaseStateUnavailable(3),
leaseStateReserved(4), leaseStateArpBlackListed(5), leaseS-
tateInactive(6), or leaseStateZombie(7).
arrisRouterLanClientRowStatus
The RowStatus, used to create or remove static clients. Rows that
correspond to dynamic IP addresses cannot be removed.
arrisRouterLanClientOnline
(read-only) The client connection state: offline(0) or online(1).
arrisRouterLanClientComment
An administrative comment field for the client.
arrisRouterLanClientCustom
(read-only) The client custom state: unknown(0) or custom(1).
arrisRouterDeviceUpDownTable
arrisRouterDeviceUpDownEnd
(read-only) Time when this client device was detected to be inacces-
sible.
arrisRouterDeviceUpDownStatus
RowStatus, used to remove rows from this table.
arrisRouterLanCustomTable
This table displays mapping of LAN clients to friendly names and other
attributes.
arrisRouterLanCustomMAC
The MAC address of the client.
arrisRouterLanCustomIPAddrType
The IP address type. This address is optional, but either the IP or
MAC address should be present.
arrisRouterLanCustomIPAddr
The IP address. This address is optional, but either the IP or MAC
address should be present.
arrisRouterLanCustomFriendName
The friendly name for this client. The default is the host name.
Users can change the host name in the web interface.
arrisRouterLanCustomHostName
The host name for the client.
arrisRouterLanCustomMACMfg
(read-only) The manufacturer of the hardware adapter.
arrisRouterLanCustomComments
An administrative comments field.
arrisRouterLanCustomRowStatus
Used to remove rows from the table.
arrisRouterLanCurrentClientTable
This table contains all current client devices on the LAN. Entries include:
• Primarily LAN devices that use DHCP to request an IP address from
the Gateway device.
• Any device that was statically configured with an IP address on the
same subnet as the Gateway device. These devices are usually discov-
ered through ARP.
• Any device added to the arrisRouterLanStaticClientTable.
arrisRouterLanCurrentClientHostName
(read-only) The host name for the client.
arrisRouterLanCurrentClientMAC
(read-only) The MAC address of the client.
arrisRouterLanCurrentClientMACMfg
(read-only) The manufacturer of the hardware adapter.
arrisRouterLanCurrentClientAdapterType
(read-only) The adapter type: unknown(0), ethernet(1), or wire-
less(2).
arrisRouterLanCurrentClientType
(read-only) The client type:
unknown(0)
The Router is unable to determine the client type.
dynamic(1)
DHCP clients.
staticDiscover(2)
Clients that are statically configured and discovered via ARP.
staticConfigure(3)
Clients that are configured in the arrisRouterLanStaticClient-
Table.
arrisRouterLanCurrentClientLeaseStart
(read-only) The time and date when this lease started. This only
applies to clients whose arrisRouterLanCurrentClientType is
dynamic(1).
arrisRouterLanCurrentClientLeaseEnd
(read-only) The time and date when this lease expires. This only
applies to clients whose arrisRouterLanCurrentClientType is
dynamic(1).
arrisRouterLanCurrentClientStatus
(read-only) The most recent known status of the LAN client:
unknown(-1), down(0), or up(1).
arrisRouterLanCurrentClientInfLease
(read-only) Returns true(1) if the lease is infinite. This only applies
to clients whose arrisRouterLanCurrentClientType is dynamic(1).
arrisRouterLanCurrentClientLeaseState
(read-only) The state of the lease: leaseStateAvailable(0), leaseS-
tateArping(1), leaseStateOffering(2), leaseStateUnavailable(3),
leaseStateReserved(4), leaseStateArpBlackListed(5), leaseS-
tateInactive(6), or leaseStateZombie(7). This only applies to
clients whose arrisRouterLanCurrentClientType is dynamic(1).
Static clients return leaseStateUnavailable(3).
arrisRouterLanCurrentClientFirstSeen
(read-only) The time, if known, when this client was first seen.
For dynamic clients, this is usually when the first DHCP lease was
given to this client since the last boot. This value does not necessar-
ily match arrisRouterLanCurrentClientLeaseStart, as several
DHCP renewals may have occurred.
For staticDiscover and staticConfigure clients, this is the time of the
first ARP response since the last boot.
arrisRouterLanCurrentClientLastSeen
(read-only) The time, if known, when this client was most recently
(last) seen. If the device is currently active, this time should within
one minute of the current system time.
arrisRouterLanCurrentClientConnectionInfo
(read-only) A string that may contain additional connection details.
For Ethernet clients, this may provide the connection port and con-
nection speed. For wireless clients, this may provide brief details
about the wireless connection. This field may also be blank.
arrisRouterLanCurrentClientLeaseTime
(read-only) The time, in seconds, of the DHCP lease. For static
LAN clients, this value is zero.
arrisRouterLanStaticClientTable
This table contains clients that are statically configured to maintain the same
IP address between reboots. The table supports up to 16 entries.
arrisRouterLanStaticClientIPAddrType
The IP address type of the statically configured address.
arrisRouterLanStaticClientIPAddr
The static IP address.
arrisRouterLanStaticClientHostName
An optional host name for the client device.
arrisRouterLanStaticClientMAC
The MAC address of the client device.
arrisRouterLanStaticClientRowStatus
The RowStatus, used to remove clients from the table.
arrisRouterRIPObjects
arrisRouterRIPReportTime
The RIP reporting interval, in seconds. Default: 30.
arrisRouterRIPAuthKeyString
The RIP authentication key.
arrisRouterRIPAuthKeyID
The RIP authentication key identifier.
arrisRouterRIPIPAddrType
The RIP destination IP address type.
arrisRouterRIPIPAddr
The RIP unicast reporting destination IP address. If this contains an
IP address other than 0.0.0.0, then RIP messaging (which is multi-
casted by default) is unicasted to this IP address.
arrisRouterRIPPrefixLen
The prefix for the routed subnet. The subnet can be specified by this
object or by arrisRouterRIPSubnetMask.
arrisRouterRIPAuthKeyChain
The RIP authentication key chain.
arrisRouterRIPRoutedSubnetIPType
The IP address type for arrisRouterRIPRoutedNetIP.
arrisRouterRIPRoutedSubnetIP
The specific network in the configured subnet that is advertised and
routed.
This allows configuration of a public LAN-side subnet of hosts
which is not necessarily on the same subnet as the CMTS HFC IP
address, CM IP address, or WAN-MAN IP address subnet. CPEs
belonging to this routed subnet have their IP addresses assigned
statically. The default gateway for these CPEs is one of the
addresses in the configured subnet. The gateway IP address speci-
fied becomes an actual secondary IP address on the device. The
arrisRouterRIPRoutedSubnetTable
arrisRouterWire- These objects provide configuration and monitoring of the wireless inter-
lessCfg Objects faces.
Note: TS7.5 and newer versions of Touchstone firmware use the ifIndex of
the wireless interface as the index; the interface numbers are 12 to 15 for
SSIDs 0 through 3. Earlier versions of Touchstone firmware used a range of
1 through 4.
arrisRouterWiFiCountry
(read-only) The country name configured for the wireless interface.
arrisRouterWiFiChannel
Sets the current channel number (802.11g) or control channel
(802.11n).
arrisRouterWiFiBGProtect
Sets the 54g protection state. When protection is enabled, the
access point uses RTS/CTS to improve 802.11g performance in
mixed 802.11g/802.11b networks. Disabling protection maximizes
802.11g throughput under most conditions.
arrisRouterWiFiBeaconInterval
The time, in milliseconds, between beacon transmissions.
arrisRouterWiFiDTIMInterval
The time, in milliseconds, between Delivery Traffic Indication Mes-
sages.
arrisRouterWiFiTxPreamble
Sets the transfer preamble length: long(0) or short(1).
arrisRouterWiFiRTSThreshold
The minimum packet (MPDU) size that uses RTS/CTS handshake.
Packets smaller than this threshold do not use RTS/CTS handshake.
A value of zero enables RTS/CTS handshake for all packets; a value
of 2347 effectively disables RTS/CTS handshake.
An RTS/CTS handshake is performed when all the following condi-
tions apply:
• The MPDU is of type Data or Management.
• The MPDU has an individual address in the Address field.
• The length of the MPDU is greater than the threshold value.
arrisRouterWiFiFragmentThresh
The maximum size of a packet before the packet data is fragmented
into two or more packets.
arrisRouterWiFiShortSlot
Enables or disables short slot timing mode. This is the amount of
time a device waits after a collision, before retransmitting a packet.
arrisRouterWiFiMulticastA
Sets the multicast rate for 802.11a: rate12mbps(12),
rate18mbps(18), rate24mbps(24), rate36mbps(36),
rate48mbps(48), rate72mbps(72), rate96mbps(96), or
rate108mbps(108).
arrisRouterWiFiMulticastBG
Sets the multicast rate for 802.11b/g: auto(0), bgMrate2mbps(2),
bgMrate4mbps(4), bgMrate11mbps(11), bgMrate12mbps(12),
bgMrate18mbps(18), bgMrate22mbps(22), bgMrate24mbps(24),
bgMrate36mbps(36), bgMrate48mbps(48), bgMrate72mbps(72),
bgMrate96mbps(96), or bgMrate108mbps(108).
arrisRouterWiFiBasicRateSet
Determines which rates are advertised as BASIC rates in the bea-
con. If set to default(1), the driver uses the defaults for the selected
54g mode. If set to all(2), all available rates are advertised as
arrisRouterWiFiResetDefaults
Resets Wifi settings to default values as follows:
• resetWifiDefaults(1) resets all wireless networks to their default
settings.
• resetWifiDefaultsPrimaryOnly(2) resets only the primary wire-
less network.
• resetWiFiDefaultGuestOnly(3) resets all the non-primary/guest
wireless networks.
The wireless drivers are immediately restarted, and any clients con-
nected to the wireless networks are disconnected.
arrisRouterWiFiEnableRadioNow
Enables or disables the WiFi radio, immediately applying the
change.
arrisRouterWiFiCustomSSIDStr
The default SSID prefix. The last four characters of the CM MAC
address are appended to this string to form the SSID. The default is
ARRIS.
arrisRouterWiFiRadioControlMode
Sets the radio control mode:
userControlled(0)
(default) All settings remain in effect as specified through
other means (web, SNMP, CLI).
msoControlled24bgnMode(1)
The current channel number and channel bandwidth selection
remain in effect, but all other wireless radio settings are set to
optimize support for a mixture of 802.11b/g/n devices using
2.4GHz channels and transmitting at full power. If concurrent
2.4GHz and 5.0GHz frequency bands are supported, only the
2.4GHz band is affected.
msoControlled24nMode(2)
The current channel number and channel bandwidth selection
remain in effect, but all other wireless radio settings are set to
optimize support for only 802.11n devices using 2.4GHz
channels and transmitting at full power. If concurrent 2.4GHz
and 5.0GHz frequency bands are supported, only the 2.4GHz
band is affected.
msoControlled50nMode(3)
Unsupported.
arrisRouterBSSTable Entries
arrisRouterBssNetworkIsolate
If set to true(1), this service set has restricted access to the local
area network. The default value of false(2) authorizes this service
set as a full member of the LAN.
arrisRouterBssMACAccessCount
(read-only) The number of entries in the arrisRouterMACAc-
cessTable.
arrisRouterBssMACAccessClear
Set to clear(1) to clear the entire list of MAC addresses in the arris-
RouterMACAccessTable.
arrisRouterWEPTable Entries
arrisRouterWEPPassPhrase
The passphrase used for WEP security. This can be used to auto-
matically generate the hex WEP keys.
arrisRouterWEP64BitKeyTable Entries
arrisRouterWEP128BitKeyTable Entries
arrisRouterWEP128BitKeyStatus
The RowStatus of this conceptual row. The following restrictions
apply:
• A newly created entry cannot be made active until the correspond-
ing instance of arrisRouterWEP128BitKeyValue has been set.
This object may not be set to a value of notInService(2) or
destroy(6) if the corresponding instance of arrisRouterWEPDe-
faultKey identifies this entry as the key in use.
arrisRouterWPATable Entries
arrisRouterWPAReAuthInterval
The WPA Group reauthentication interval, in seconds, for this ser-
vice set. A value of zero disables periodic reauthentication for this
service set.
arrisRouterWPAPreAuthEnable
Enables or disables WPA2 pre-authentication. When pre-authenti-
cation is enabled, a WPA2 wireless client can perform an 802.1X
authentication with other wireless access points in its range when it
is still connected to its current wireless access point.
arrisRouterRadiusTable Entries
This table configures settings related to the RADIUS security modes, includ-
ing WPA-Enterprise, WPA2-Enterprise and RADIUS-WEP. This table is
indexed by the ifIndex of the applicable wifi network.
arrisRouterRadiusAddressType
The type of internet address used for arrisRouterRadiusAddress.
arrisRouterRadiusAddress
The IP address of the RADIUS server.
arrisRouterRadiusPort
The UDP port used to communicate with the RADIUS server.
arrisRouterRadiusKey
The RADIUS key.
arrisRouterRadiusReAuthInterval
The network re-authentication interval, in seconds. A value of zero
disables re-authentication.
arrisRouterMACAccessTable Entries
A table of MAC addresses which defines the MAC address based access
restrictions for each wifi network. This table is indexed by the ifIndex of the
wireless network and by an internal index. Each network supports up to 32
entries.
arrisRouterMACAccessAddr
The MAC address of a client device. Client appearing in this table
are allowed or denied access based on the value of arrisRouterB-
ssAccessMode.
arrisRouterMACAccessStatus
Set to active(1) to enable this entry.
The arrisRouterMACAccessAddr object for this entry must be set
before making the entry active.
arrisRouterWMMCfg Objects
arrisRouterWMMEDCAAPTable
arrisRouterWMMEDCAAPCWmax
Sets the Maximum Contention Window (CWmax), in milliseconds.
This is the upper bound of the maximum random backoff time for
retrying a transmission. Valid settings are: 1, 3, 7, 15, 31, 63, 127,
255, and 511. The setting must be higher than the setting for arris-
RouterWMMEDCAAPCWmin.
arrisRouterWMMEDCAAPAIFSN
Sets the Arbitration Inter-Frame Spacing Number, in milliseconds.
This is the wait time for data frames.
arrisRouterWMMEDCAAPTxOpBLimit
Sets the Transmission Opportunity (TXDP) for 802.11b, in
microseconds. During this interval, a WMM AP has the right to ini-
tiate transmissions onto the wireless network.
arrisRouterWMMEDCAAPTxOpAGLimit
Sets the Transmission Opportunity (TXDP) for 802.11a/g, in
microseconds. During this interval, a WMM AP has the right to ini-
tiate transmissions on the wireless network.
arrisRouterWMMEDCAAPAdmitCont
Set to true(1) to enable admission control for specific category of
traffic.
arrisRouterWMMEDCAAPDiscardOld
Set to true(1) to enable ‘‘discard oldest packet first’’ mode.
arrisRouterWMMEDCASTATable
arrisRouterWMMEDCASTACWmax
Sets the Maximum Contention Window (CWmax), in milliseconds.
This is the upper bound of the maximum random backoff time for
retrying a transmission. Valid settings are: 1, 3, 7, 15, 31, 63, 127,
255, and 511. The setting must be higher than the setting for arris-
RouterWMMEDCASTACWmin.
arrisRouterWMMEDCASTAAIFSN
Sets the Arbitration Inter-Frame Spacing Number, in milliseconds.
This is the wait time for data frames.
arrisRouterWMMEDCASTATxOpBLimit
Sets the Transmission Opportunity (TXDP) for 802.11b, in
microseconds. During this interval, a WMM AP has the right to ini-
tiate transmissions onto the wireless network.
arrisRouterWMMEDCASTATxAGLimit
Sets the Transmission Opportunity (TXDP) for 802.11a/g, in
microseconds. During this interval, a WMM AP has the right to ini-
tiate transmissions on the wireless network.
arrisRouterWPSCfg Objects
arrisRouterWpsStatus
(read-only) The WPS subsystem status: wpsUnknown(-1), wpsIni-
tialState(0), wpsAssociatedStarted(1), wpsM2Sent(2),
wpsM7Sent(3), wpsTimedOut(4), wpsMsgDone(5), wpsSuc-
cessful(6), wpsMsgExchangeErr(7), wpsPushButtonOverlap(8),
wpsAssociating(9), or wpsPushButtonFindAP(10).
arrisRouterWpsConfigTimeout
Set to enabled(1) to enable WPS timeout.
arrisRouterWpsSTAPin
The WPS PIN for a new station/device, up to 8 characters. This is
the PIN from a client device.
arrisRouterWpsPushButton
The virtual WPS push-button:
activatePushButton(1)
Start the WPS push-button process, as if a user pushed the
WPS button.
activePINCfg(2)
Starts the WPS PIN process. The arrisRouterWpsSTAPin
object must have a value set before triggering the WPS
process.
cancelWPS(3)
Cancels an active WPS configuration.
arrisRouterWpsBoardNum
Sets the WPS Board serial number, up to 32 characters.
arrisRouterWpsModelNum
The WPS model number, up to 32 characters.
arrisRouterWpsUUID
The WPS Universal Unique Identifier, up to 16 characters.
arrisRouterWiFi80211NSettings Objects +
The following objects apply only when the router is using 802.11n. +
arrisRouterWiFi80211NBand +
If operating in 802.11n mode, this is either band24G(1) for 2.4GHz +
operation or band5G(2) for 5GHz operation. +
arrisRouterWiFiGuardInterval +
If operating in 802.11n mode, the interval between transmission of +
symbols (in nanoseconds): gi400(0) (400ns) or gi800(1) (800ns). +
arrisRouterWiFiHTMCS +
The 802.11n physical modulation coding scheme (MCS) rate. Set- +
ting this object forces the transmission rate for the AP to a particular +
speed. Each pair of rates corresponds to a 20 MHz or 40 MHz +
channel configuration. Use auto(0) to allow the router to choose a +
transmission rate. The value legacy(1) allows setting the transmis- +
sion rate using the normal parameters. +
arrisRouterWiFiChannelBW +
Determines the 802.11n bandwidth; one of: +
• width20MHz(0) +
• width40MHz(1) +
• width20and40Mhz(2) +
arrisRouterWiFi80211NSideBand +
When 40MHz mode is selected, determines which sideband the +
channel uses: upper(1) or lower(2). +
arrisRouterWiFiHTMode +
The 802.11n operating mode; one of mixed(0) (the default) or +
greenField(1). +
arrisRouterWiFiGuardInterval +
The time, in nanoseconds, between symbol transmissions. The +
choices are: +
arrisRouterWiFiAMSDUEnable +
Set to true(1) to aggregate MAC Service Data Units (MSDUs) at +
the top of the MAC-level frame. The default is false(2). +
arrisRouterWiFiDeclinePeerBA +
Set to true(1) to enable rejection of a peer BA-request. The default +
is false(2). +
arrisRouterWiFiBlockAck +
Set to true(1) to enable ACK blocking (BA) during data transfer. +
The default is false(2). +
arrisRouterWiFiNProtection +
The 802.11n protection setting, either off(0) or auto(1). This is for +
OFDM protection for MIMO frames. +
arrisRouterWiFiAllow40MHzOnlyOperation +
Set to true(1) to allow end-users to set 40 MHz-only Wifi operation. +
This adds a new selection to the Bandwidth menu in the configura- +
tion web pages. The default is false(2). +
arrisRouterFWSecurityLevel
(CT loads only) This variable can be used to set a generic firewall
level. The allowed levels are:
• minimum(1): allows all incoming and outgoing connections
except IDENT (port 113).
• medium(2): rejects all incoming connections and allows all out-
going connections except: IDENT (port 113), ICMP, Kazaa (port
1214), Bittorrent (Ports 6881-6999), Gnutella (6346), and Vuze
(49152-65534).
• maximum(3): rejects all incoming connections. Rejects all out-
going connections except: HTTP (80), HTTPS (443), DNS (53),
Email (25,110,143,465,587,993,995), NTP (119, 123), VPN (500,
1723), and iTunes (3689).
• custom(4): Uses operator- or subscriber-specified port filters and
triggers.
arrisRouterFWApplySettings
(CT loads only) Apply or reject changes made to the firewall config-
uration. Allowed values are:
• applySettings(1): applies all changes.
• revertSettings(2): rejects changes made since the last apply.
• resetDefaults(3): reverts firewall settings to their defaults.
arrisRouterFWAllowICMP
Enables or disables ICMP messages such as Ping and Traceroute.
arrisRouterFWResetDefaults
(CT loads only) Set to true(1) to reset firewall settings to their
default values.
arrisRouterFWBlockHTTP
(CT loads only) Enables or disables blocking of incoming HTTP
traffic.
arrisRouterFWBlockP2P
(CT loads only) Enables or disables blocking of peer-to-peer appli-
cations.
arrisRouterFWBlockIdent
(CT loads only) Enables or disables blocking of the IDENT proto-
col.
arrisRouterFWBlockICMP
(CT loads only) Enables or disables blocking of ICMP messages
such as Ping and Traceroute.
arrisRouterFWBlockMulticast
(CT loads only) Enables or disables blocking of multicast traffic.
arrisRouterFWVirtSrvTableEnabled
(CT loads only) Enables or disables Port Forwarding.
arrisRouterFWPortTrigTableEnabled
(CT loads only) Enables or disables port triggering.
arrisRouterFWAllowAll
Set to true(1) to allow all devices to connect to the network, except
those in the arrisRouterFWMACFilterTable. Set to false(2) to
block all devices from connecting to the network, except those in
the arrisRouterFWMACFilterTable.
arrisRouterFWVirtSrvTable Entries
This table defines virtual servers. This service allows incoming requests on
specific ports to reach servers behind the firewall. This allows access to
servers from the public network.
arrisRouterFWVirtSrvDesc
A text string (up to 16 characters), describing this entry.
arrisRouterFWVirtSrvPortStart
The beginning of the port range to forward to this virtual server.
Note that the arrisRouterFWVSSrcPortExclude object can disal-
low certain ports.
arrisRouterFWVirtSrvPortEnd
The end of the port range to forward to this virtual server.
arrisRouterFWVirtSrvProtoType
Specifies which protocol(s) are forwarded: udp(0), tcp(1), or
both(2).
arrisRouterFWVirtSrvIPAddrType
The destination IP address type on the private network.
arrisRouterFWVirtSrvIPAddr
The destination IP address on the private network.
arrisRouterFWVirtSrvTOD
(CT loads only) A 32-bit bitmask that sets the time of day and days
of the week when this virtual service is active. The bits are:
0 67 30
Day of Week Hours of Day
arrisRouterFWIPFilterTable
This table defines IP address filters. The filters block or allow Internet traffic
to or from specific IP address ranges.
arrisRouterFWIPFilterDesc
A text string, up to 32 characters, that describes this entry.
arrisRouterFWIPFilterStartType
The IP address type for the starting address in the range.
arrisRouterFWIPFilterStartAddr
The beginning IP address in the range. To filter all IP addresses, use
0.0.0.0 (IPv4 networks).
arrisRouterFWIPFilterEndType
The IP address type for the ending address in the range.
arrisRouterFWIPFilterEndAddr
The ending IP address in the range. To filter all IP addresses, use
0.0.0.0 (IPv4 networks).
arrisRouterFWIPFilterPortStart
The beginning of the port range to filter.
arrisRouterFWIPFilterPortEnd
The end of the port range to filter.
arrisRouterFWIPFilterProtoType
Specifies the protocols to filter: udp(0), tcp(1), or both(2).
arrisRouterFWIPFilterTOD
A 32-bit bitmask that sets the time of day and days of the week
when this IP filter is active. The bits are:
0 67 30
Day of Week Hours of Day
arrisRouterFWMACFilterTable
This table defines MAC addresses that are denied access to the gateway.
arrisRouterFWMACFilterAddr
The MAC address of a device on the local network that is blocked
by the firewall.
arrisRouterFWMACFilterTOD
A 32-bit bitmask that sets the time of day and days of the week
when this MAC filter is active. The bits are:
0 67 30
Day of Week Hours of Day
arrisRouterFWPortTrigTable
This table defines port triggers. Port triggers support special applications that
require specific port numbers with bi-directional traffic to function properly.
Applications such as video conferencing, voice, gaming, and some messeng-
ing program features may require port triggers.
arrisRouterFWPortTrigDesc
A text string, up to 16 character, describing the name for this port
trigger.
arrisRouterFWPortTrigPortStart
The beginning of the trigger port range.
arrisRouterFWPortTrigPortEnd
The end of the trigger port range.
arrisRouterFWPortTargPortStart
The beginning of the target port range.
arrisRouterFWPortTargPortEnd
The end of the target port range.
arrisRouterFWPortTrigProtoType
Specifies which protocol(s) are filtered: udp(0), tcp(1), or both(2).
arrisRouterFWPortTrigRowStatus
The RowStatus variable used to add, remove, or enable entries.
arrisRouterFWFilterRules
These objects control filtering. Except where noted, all filters are disabled by
default.
arrisRouterFWFilterProxy
Set to true(1) to enable HTTP proxy filtering.
arrisRouterFWFilterCookies
Set to true(1) to filter cookies.
arrisRouterFWFilterJavaApplets
Set to true(1) to filter Java applets.
arrisRouterFWFilterActiveX
Set to true(1) to filter ActiveX controls.
arrisRouterFWFilterPopupWnds
Set to true(1) to filter pop-up windows.
arrisRouterFWBlockFragIPPkts
Set to true(1) to block fragmented IP packets.
arrisRouterFWPortScanProtect
Set to true(1) to enable port scan protection.
arrisRouterFWIPFloodDetect
Set to true(1) (default) to enable detection of IP floods.
arrisRouterFWDDNSObjs
arrisRouterFWDDNSType
The DDNS service to use: unknown(0), dynDNS(1), or tzo(2).
arrisRouterFWDDNSUserHame
The user name (up to 64 characters) to log into the DDNS service.
arrisRouterFWDDNSPassword
The password (up to 64 characters) to log into the DDNS service.
arrisRouterFWDDNSDomainName
The domain name that the DDNS service associates with this router.
arrisRouterFWDDNSIPAddrType
(read-only) The IP address type (IPv4 or IPv6) for the DDNS IP
address.
arrisRouterFWDDNSIPAddr
(read-only) The DDNS IP address.
arrisRouterFWDDNSStatus
(read-only) The current status of the DDNS service.
arrisRouterFWFeatures
These objects control various router features. All these features are disabled
by default.
arrisRouterFWEnableWanBlocking
Set to true(1) to enable WAN blocking.
arrisRouterFWIPSecPassThru
Set to true(1) to enable IPsec pass-through.
arrisRouterFWPPTPPassThru
Set to true(1) to enable PPTP pass-through.
arrisRouterFWEnableMulticast
Set to true(1) to enable multicast support.
arrisRouterFWEnableRemoteMgmt
Set to true(1) to enable remote web management.
arrisRouterFWEnableRGPassThru
Set to true(1) to enable pass-through mode. Enabling this feature
automatically disables UPnP.
The router must be rebooted after enabling this feature.
arrisRouterFWL2TPPassThru
Set to true(1) to enable L2TP pass-through.
arrisRouterFWEnableWanSNMP
Set to true(1) to enable SNMP access (ports 161, 1161, 162) on the
eRouter WAN port. Changing this value takes affect without apply-
ing settings.
arrisRouterFWEnableWanSSH
Set to true(1) to enable SSH access (port 22) on the eRouter WAN
port. Changing this value takes affect without applying settings.
arrisRouterFWParentalControls
arrisRouterManagedSitesEnabled
Set to true(1) to enable parental control managed sites.
arrisRouterManagedServicesEnabled
Set to true(1) to enable parental control managed services.
arrisRouterManagedDevicesEnabled
Set to true(1) to enable parental control managed devices.
arrisRouterKeywordBlkTable
This table defines the block table. URLs that contain a keyword from this ta-
ble are blocked. The table supports up to 50 keywords.
arrisRouterKeywordBlkWord
The keyword to block, up to 32 characters.
arrisRouterKeywordBlkTOD
A 32-bit bitmask that sets the time of day and days of the week
when this keyword is blocked. The bits are:
0 67 30
Day of Week Hours of Day
arrisRouterBlackListTable
0 67 30
Day of Week Hours of Day
arrisRouterWhiteListTable
This table contains domain names that are never blocked, even if there are
matches in the keyword list or blacklist. The table supports up to 16
domains.
arrisRouterWhiteListDomain
The domain to whitelist, up to 64 characters.
arrisRouterWhiteListTOD
A 32-bit bitmask that sets the time of day and days of the week
when this domain is whitelisted. The bits are:
0 67 30
Day of Week Hours of Day
arrisRouterTrustedDeviceTable
arrisRouterTrustedDeviceManagedServicesTable
arrisRouterTrustedDeviceManagedServicesAddr
The IP address for the service.
arrisRouterName
(optional) The name of the gateway router.
arrisRouterSerialNumber
(read-only) The device serial number.
arrisRouterBootCodeVersion
(read-only) The device boot code version.
arrisRouterHardwareVersion
(read-only) The device hardware version.
arrisRouterFirmwareVersion
(read-only) The device firmware version.
arrisRouterLogLevel
The logging level for the Arris SNMP daemon: noLogging(0),
logError(1) (default), logWarn(2), or logInfo(3).
arrisRouterCustomSettings
A text string used for web interface settings.
arrisRouterCustomID
A customer-assigned ID.
arrisRouterCurrentTime
The current time on the router.
arrisRouterTACACSAddr
The FQDN or IP Address of the TACACS server.
arrisRouterTACACSPort
The TACACS server port. Default: 49.
arrisRouterTACACSSecretKey
The secret key used to communicate with the TACACS server.
arrisRouterXmlProvisioningFile
The fully qualified path to a provisioning file to load. The file may
be an URL using HTTP or TFTP.
Note: This value is not permanently stored in non-volatile memory,
and is cleared on reboot.
arrisRouterXmlProvisioningStatus
The download status of the gateway XML configuration file; one of:
• notSpecified(1)
• inProgress(2)
• downloadSuccess(3)
• serverError(4)
• fileNotFound(5)
• fileFormatError(6)
• downloadFromMgt(7)
Setting this object to downloadFromMgt(7) immediately starts
downloading the XML configuration file.
Note: This value is not permanently stored in non-volatile memory
and resets to notSpecified(1) when the gateway reboots.
arrisRouterSNTPSettings Sub-group
arrisRouterSNTPServerTable Entries
arrisRouterEmailSettings Sub-group
These objects define a mail drop for sending router logs and similar informa-
tion.
arrisRouterEmailServerName
The name of the email server to use.
arrisRouterEmailServerUser
The optional user ID used to log into the SMTP email server.
arrisRouterEmailServerPW
The optional password used to log into the SMTP email server.
arrisRouterEmailAddress
The email address that receives communications from the gateway.
arrisRouterEnableLogEmail
Enables or disables emailing router logs.
arrisRouterEmailApplySettings
Set to applySettings(1) to apply the email settings.
arrisRouterLogSettings Sub-group
The objects configure firewall logs and MSO change logs. They are sepa-
rated into two groups and a series of tables, defined below.
arrisRouterUserLogs Objects
arrisRouterFirewallLogTable
A read-only table of up to 30 firewall logs. The objects are:
arrisRouterFWLogTime
(read-only) The date and time when this event occurred.
arrisRouterFWLogInfo
(read-only) The log entry text.
arrisRouterParentalContLogTable
A read-only table of up to 30 parental control logs. The objects are:
arrisRouterPCLogTime
(read-only) The date and time when this event occurred.
arrisRouterPCLogInfo
(read-only) The log entry text.
arrisRouterChangeLogTable
A read-only table of up to 48 subscriber configuration change logs.
The objects are:
arrisRouterChangeLogTime
(read-only) The date and time when this event occurred.
arrisRouterChangeLogInfo
(read-only) The log entry text.
arrisRouterDebugLogTable
A read-only table of up to 100 debug logs. The objects are:
arrisRouterDebugLogTime
(read-only) The date and time when this event occurred.
arrisRouterDebugLogInfo
(read-only) The log entry text.
arrisRouterMSOLogs Objects
These objects display and control log entries based on MSO actions.
arrisRouterMSOChgLogTable
A table of up to 48 MSO change log entries. These entries are con-
figuration changes performed by a technician on-site or remotely
from the NOC. The objects are:
arrisRouterMSOChgLogTime
(read-only) The date and time when this event occurred.
arrisRouterMSOChgLogInfo
(read-only) The log entry text.
arrisRouterClearMSOLogs
Set to clearLogs(1) to clear the MSO logs.
arrisRouterAuthTable Entries
This table contains authorization information for web UI users, roles, and
passwords.
arrisRouterAuthUserName
The user name, up to 32 characters.
arrisRouterAuthPassword
The password for the user, up to 32 characters.
arrisRouterAuthType
A string describing the type of user. For example, ‘‘technician’’ or
‘‘subscriber.’’
arrisRouterInboundTrafficLogTable Entries
arrisRouter- These objects control access to router interfaces (web and CLI).
HostAccess Ob-
jects
arrisRouterWebAccessTable Entries
arrisRouterWebAccessRowStatus
The RowStatus object used to add or remove rows from the table.
arrisRouterPing- These objects control the Ping utility, allowing controlled testing of network
Mgmt Objects connectivity.
arrisRouterPingTargetAddrType
The IP address type for the target address.
arrisRouterTrac- These objects control the Traceroute utility, allowing controlled testing of
eRtMgmt Objects network connectivity.
arrisRouterTraceRtTargAddrType
The IP address type for the target address.
arrisRouterTraceRtTargetAddr
The IP address of the destination for the traceroute.
arrisRouterTraceRtMaxHops
The maximum number of hops for the traceroute.
arrisRouterTraceRtDataSize
The data size of the traceroute packet.
arrisRouterTraceRtResolveHosts
Specifies host name resolution: noResolve(0) or resolve(1)
(default).
arrisRouterTraceRtBasePort
The base port to use for traceroute.
arrisRouterTraceRtStart
Starts or stops the traceroute, or indicates the current traceroute sta-
tus: traceRouteNotRunning(0), traceRouteRunning(1), or start-
Trace(10).
arrisRouterTraceRtLog
(read-only) The most recent output log for the traceroute, up to 255
bytes.
The Speedtest MIB objects are collected in the arrisSpeedTestMib. The fol-
lowing objects are defined, separated into configuration, control, and results.
Configuration Ob- The uplink and downlink configurations are set using URL formatted strings.
jects arrisSpeedTestConfigEndUserGui
Set to true(1) to include the Speedtest web page in the Basic (sub-
scriber-accessible) pages.
arrisSpeedTestConfigSyslogReports
Set to true(1) to report results to Syslog and the event log.
arrisSpeedTestConfigCpeAccess
Set to true(1) to allow CPE access to the Internet while running a
speed test.
arrisSpeedTestConfigDownlinkURL
Defines the downlink configuration, in URL format (see below for
an example).
arrisSpeedTestConfigUplinkURL
Defines the uplink configuration, in URL format (see below for an
example).
Download Examples
The following examples show typical download URLs for FTP and HTTP
tests. In these examples, the user ID and password are both speedtest.
ftp://speedtest:[email protected]/movie.mpg
?ftpmode=passive&tcpwindow=2048&tcpmss=1460
&tcptimestamps=1&pmtud=1&cpeaccess=1
http://speedtest:[email protected]:80/movie.mpg
?tcpwindow=63&tcpmss=1460&tcptimestamps=1&pmtud=1
&cpeaccess=1
Upload Examples
The following examples show typical upload URLs for FTP and HTTP tests.
In these examples, the user ID and password are both speedtest.
ftp://speedtest:[email protected]:21/uptest.txt
?ftpmode=active&uploadsize=10&tcpwindow=63&tcpmss=1460
&tcptimestamps=1&pmtud=1&cpeaccess=1
http://speedtest:[email protected]:80/uptest.txt
?uploadsize=10&script=cgi-bin/upload.cgi&postfields
=ac˜upload;login˜admin;pass˜admin&filefield=file
&tcpwindow=63&tcpmss=1460&tcptimestamps=1&pmtud=1
&cpeaccess=1
Control Object Use the following object to start and stop the speed tests:
arrisSpeedTestConfigStartStopTest
One of the following:
• stopTest(0)
• startDownlinkTest(1)
• startUplinkTest(2)
Results Table Use the following object to retrieve speed test results:
arrisSpeedTestResultsStatus
Use an index of 1 to 3 to retrieve a test result. arrisSpeedTestRe-
sultsStatus.1 contains the latest result.
Administration Objects
System Descrip- The system objects can be used to identify a Touchstone product and find
tion Objects general information about it. Most of these objects are generic to all devices,
but those described below have values unique to ARRIS products.
sysDescr Object
sysObjectID Object
sysORTable Objects
dot1dBridge Objects
rip2 Objects
The rip2 MIB provides routing information when the E-UE is provisioned
for RIPv2 routing support. The following objects can be of use:
rip2IfStatTable
Statistics for each interface enabled for RIP routing.
rip2IfConfTable
RIP interface configuration for each interface enabled for RIP rout-
ing.
arrisRouterMib Objects
NCS Behavior Touchstone NCS loads make end-of-call connection statistics available
through proprietary MIB objects and Syslog messages. Touchstone firmware
supports the PacketCable-defined call connection statistics, with clarifications
as defined in ECN EC-MGCP-N-04.0175-7. Previously, 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 cur-
rent connection state of the call.
The E-UE 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.
SIP Behavior TS7.2 and newer versions of Touchstone SIP loads support end-of-call statis-
tics reporting through the SIP PUBLISH mechanism (defined in RFC 3903).
The content of the PUBLISH message uses the session report format.
To enable end-of-call statistics reporting, set the following MIB objects:
pktcEDVACodecPubRepAddrType
Specifies the IP address type (IPv4 or IPv6) of the device that
receives statistics reports.
pktcEDVACodecPubRepAddr
The IP address of the device that receives statistics reports. If this
object is not specified, end-of-call statistics are disabled.
pktcEDVACodecRTCPXR
Determines whether the eDVA includes far-end statistics in the
report. The default is true(1).
End-of-Call Statis- Touchstone firmware provides MIB objects for monitoring eDVA end-of-call
tics MIB Objects statistics.
The monitoring MIB is broken into groups under arrisMtaDevTrace:
• Objects that report on a per-call level (the counter values represent the
total count for the most recently completed call on an endpoint). These
objects are indexed by the endpoint number in the table arrisMtaDev-
CallStatsEntry.
• Objects that report on a device level (the counter values represent the
sum total for all endpoints), located under arrisMtaDevTrace.
• Objects that control and reset counters, located under the arrisMtaDev-
Control MIB tree.
Clearing Counters To clear the device-level end-of-call statistics counters, set the arrisMtaDev-
ResetCallStats MIB to true(1). Setting this object to a value of false(2) has
no effect. Reading this object always returns false(2).
This object clears the following counters:
• arrisMtaDevRtpTxPktsTotal
• arrisMtaDevRtpRxPktsTotal
• arrisMtaDevRtpPercentPktsLostTotal
• arrisMtaDevSignalingAvgLatency
• arrisMtaDevSignalingTxSuccessfulMsgCnt
• arrisMtaDevSignalingRxSuccessfulMsgCnt
• arrisMtaDevSignalingTxNAKCnt
• arrisMtaDevSignalingRxNAKCnt
• arrisMtaDevSignalingRxNoACKCnt
Device Level End- Device-level MIB objects represent combined end-of-call statistics for all
of-Call Statistics lines on the eDVA.
arrisMtaDevRtpTxPktsTotal
The total number of RTP packets sent from the eDVA since it was
last started up or reset. It is calculated from values obtained from
the signaling end of call statistics.
arrisMtaDevRtpRxPktsTotal
The total number of RTP packets received by the eDVA since it was
last started up or reset. It is calculated from values obtained from
the signaling end of call statistics.
arrisMtaDevRtpPercentPktsLostTotal
The percentage of RTP packets lost since the eDVA was last started
up or reset. It is calculated from values obtained from the signaling
end of call statistics. The value of this object is an integer, repre-
senting percentage divided by 100. For example, a value of 1745
represents 17.45% packet loss.
arrisMtaDevRtpPktsLostTotal
The total number of RTP packets lost, across all endpoints, since the
eDVA was started or reset. Set the arrisMtaDevResetCallStats
object to true(1) to clear this counter.
arrisMtaDevLastCallStartTime
The start time of the last call made from the eDVA.
arrisMtaDevLastCallEndTime
The end time of the last call made from the eDVA.
arrisMtaDevSignalingAvgLatency
The average latency/delay, in milliseconds, for responses to signal-
ing messages. This value is calculated from end-of-call signaling
statistics and is a running average during eDVA uptime. It is calcu-
lated from values obtained from the signaling end of call statistics.
arrisMtaDevSignalingTxSuccessfulMsgCnt
The total number of successful signaling messages sent from the
eDVA.
arrisMtaDevSignalingRxSuccessfulMsgCnt
The total number of successful signaling messages received by the
eDVA.
arrisMtaDevSignalingTxNAKCnt
The total number of negative acknowledgment signaling messages
(NAK messages) sent from the eDVA.
arrisMtaDevSignalingRxNAKCnt
The total number of negative acknowledgment signaling messages
(NAK messages) received by the eDVA.
arrisMtaDevSignalingRxNoACKCnt
The total number of ‘‘no acknowledgment’’ signaling messages
received by the eDVA.
Last Signaling To make a short trace of the last messages available at the end of the most
Message Sent recent call, Touchstone firmware allocates a 4K byte circular buffer to store
the last signaling messages sent on the most recent call. To enable collection
of signaling messages, set the arrisMtaDevEnableCallSigLastMsgRpt
object to enable(1). The default value is disable(0).
The following table shows the behavior of the buffer under certain condi-
tions.
arrisMtaDevEnable
CMS LoC Alarm Buffer Contents Stored
CallSigLastMsgRpt
Inactive None
Disable
Active Last messages sent/received
Inactive Last 4k of messages
Enable
Active Last 4k of messages
Since the maximum PDU size for a MIB object response is 256 bytes, the
message is split into 256-byte segments and stored in MIB objects arrisMta-
DevSignalingLastMsg1 through arrisMtaDevSignalingLastMsg16. Empty
objects in this group report ‘‘Buffer is empty.’’ When reading these objects,
the eDVA sets the arrisMtaDevEnableCallSigLastMsgRpt object to dis-
able(0) to prevent another message from overwriting these MIB objects
while reading the contents. After reading the objects, you must manually set
the arrisMtaDevEnableCallSigLastMsgRpt object to enable(1) to capture
the next message.
Line Level Status Line-level MIB objects report end-of-call statistics and general status for the
most recently-completed call on each line in the eDVA. Each MIB object
described in this section is indexed by the endpoint number (1 to N), where N
is the maximum number of lines supported by the eDVA; for example,
arrisMtaDevCallStatsAvgJitter.2 shows the average jitter for the second
line.
Other MIB objects in this table provide information about endpoint tempera-
ture, hook status, and operational status.
arrisMtaDevCallStatsRtpTxPkts
The total number of RTP packets sent from the endpoint during the
most recent call. This value is obtained from the signaling end of
call statistics.
arrisMtaDevCallStatsRtpRxPkts
The total number of RTP packets received by the endpoint during
the most recent call. This value is obtained from the signaling end
of call statistics.
arrisMtaDevCallStatsRtpPercentPktsLost
The percentage of RTP packets lost during the most recent call. It is
calculated from values obtained from the signaling end of call statis-
tics. The value of this object is an integer, representing percentage
divided by 100. For example, a value of 1745 represents 17.45%
packet loss.
arrisMtaDevCallStatsAvgJitter
The average jitter measurement, in milliseconds, during the most
recent call. This value is obtained from the signaling end of call sta-
tistics.
arrisMtaDevCallStatsMaxJitter
The maximum jitter measurement, in milliseconds, during the most
recent call. This value is obtained from DSP statistics.
arrisMtaDevCallStatsAvgLatency
The average latency, in milliseconds, observed during the most
recent call. This value is obtained from the RTCP signaling end of
call statistics.
arrisMtaDevCallStatsHookStatus
The hook status for each endpoint; one of:
• onHook(0)
• offHook(1)
The disconnected state is not a valid return value for this MIB.
arrisMtaDevCallStatsSLICStatus
The over-temperature condition of the endpoint’s SLIC (line inter-
face card) chips; one of:
• normal(0)
• overtemp(1)
arrisMtaDevCallStatsEndPntOpStatus
The current operational status for each endpoint. This object is a
direct copy from ifAdminOperStatus; its value is one of:
• up(1)
• down(2)
• testing(3)
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
buffer. The Syslog report can be configured to supply only statistical data, or
statistical data and signaling messages.
Enable or disable Syslog reporting using the arrisMtaDevEnableCallStats-
SyslogRpt object, which is part of the arrisMtaDevBase MIB. The default
value for this object is Disable(0); set to Enable(1) to enable reporting.
Enable or disable the signaling message buffer using the arrisMtaDev-
EnableCallSigLastMsgRpt object. The default value for this object is Dis-
able(0); set to Enable(1) to enable the buffer. The contents of the buffer
depends on the setting of this MIB, the arrisMtaDevEnableCallStatsSys-
logRpt object, and the state of the CMS LoC alarm.
The following table shows how the MIB settings interact with the Loss of
Comms alarm to affect the buffer contents.
arrisMtaDevEnable arrisMtaDevEnable Buffer contents
CMS LoC Alarm
CallStatsSyslogRpt CallSigLastMsgRpt contained in Syslog
Inactive None
Disable
Active None
Disable
Inactive None
Enable
Active None
Inactive None
Disable Active Last messages sent/
Enable received
Inactive Last 4k of messages
Enable
Active Last 4k of messages
Data Explanations:
• HW: Hardware Model Number
• SW: Firmware Rev Version Number
• Ttl Rx RTP: Total number of RTP packets received. This only reports
RTP packets and not data packets.
• Ttl Tx RTP: Total number of RTP packets sent. This only reports RTP
packets and not data packets.
• RTP Lost: Percentage of RTP packets lost. This only reports RTP pack-
ets and not data packets.
• Prov State: The step of the eDVA Provisioning Flow that the eDVA is
currently in.
• Avg Jtr: Average Jitter in milliseconds.
• Max Jtr: Maximum Jitter in milliseconds.
• Avg Ltc RTP: Average latency for RTP packets, in milliseconds.
• Avg Ltc Sig Msg: average latency for a response to signaling messages,
in milliseconds. This value is calculated from end-of-call signaling sta-
tistics and is a running average during eDVA uptime.
• No ACKs: Count of the number of ‘‘negative acknowledgment’’ mes-
sages received from the Call Agent.
• SNMP Traps: Battery Percentage; CMS LOC.
The following is an example Syslog report showing Send (Xmit) and Receive
(Rcv) Messages:
Nov 17 18:34:11 2005 mta161.dev35 <13>
<4115> <42> <00:00:CA:CB:22:FB> <Rcv: (3: 1 of 1) -
<010>Q: loop<010>R: hf(I), hu(N)’>
Nov 17 18:34:11 2005 mta161.dev35 <14> <4115> <41> <00:00:CA:CB:22:FB>
<Xmit: (3: 1 of 1) - ’200 31855 OK’>
See ‘‘Capturing Signaling Traces’’ on page 240 for a breakdown of send and
receive message formats.
About Voice Quali- The Voice Quality Monitoring (VQM) feature provides a per-line history of
ty 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.
Metrics are provided for both the near-end (eDVA) and far-end sides of the
call (the far-end eDVA must also support RTCP-XR). Remote VQM is dis-
abled by default.
Note: Touchstone firmware does not support reporting VQM data to the
CMS. The eDVA 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.
VQM Data The following list briefly describes the supported VQM metrics, noting met-
rics that are extensions of RFC 3611. See RFC 3611 for full descriptions of
those metrics.
Call Start Time (extension)
(ARRS02) A timestamp defining the time the call began.
Call End Time (extension)
(ARRS03) A timestamp defining the time the call ended.
Call Duration (extension)
(ARRS04) The total length of the call time, in hours, minutes, and
seconds.
Line Number (extension)
(ARRS05) The phone line used for this call.
Remote IP Address (extension)
(IPAD) The IP address of the destination endpoint.
CW Errors(extension)
(ARRS06) The number of codeword errors that occurred during the
call.
Discard Rate
(JDR) The fraction of RTP data packets from the source that have
been discarded 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 dis-
carded).
Burst Density
(BLD) 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
(GLD) 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
(BD) 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 and end of that period. If there have been no burst peri-
ods, the burst duration value is zero.
Gap Duration
(GD) 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 sub-
sequent 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
(RTD) The most recently calculated round trip time between RTP
interfaces, in milliseconds.
End System Delay
(ESD) The most recently estimated end system delay, in millisec-
onds. End system delay is the sum of the total sample accumulation
and encoding delay associated with the sending direction and the jit-
ter buffer, decoding, and playout buffer delay associated with the
receiving direction.
Gmin
(GMN) The gap threshold, the value used for this report to deter-
mine if a gap exists. The recommended value of 16 corresponds to
a burst period having a minimum density of 6.25% of lost or dis-
carded packets, which may cause noticeable degradation in call
quality. During gap periods, if packet loss or discard occurs, each
lost or discarded 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
(NSR) A voice quality metric describing the segment of the call that
is carried 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].
A value of 127 indicates that this parameter is unavailable.
External R Factor
(XSR) A voice quality metric describing the segment of the call that
is carried over a network segment external to the RTP segment. The
valid range and interpretation are the same as defined for the RTP R
factor described above. This metric includes the effects of delay,
consistent 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.
A value of 127 indicates that this parameter is unavailable.
A value of 0 indicates that no measurement was obtained.
Jitter Buf Adaptive
(JBA) 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.
Interpreting The following table describes the VQM metrics and (where applicable)
Results acceptable ranges. See RFC 3611 for full descriptions of those metrics.
Metric names marked with an asterisk (*) are extensions to RFC 3611.
Ranges
Metric Description
Allowed Good
CW Errors* Codeword error count n/a n/a
CW Error Rate* Errored codeword ratio n/a ≤ 9.0−7
SNR* Signal to noise ratio n/a ≥ 35 dB
Multiple echoes:
• −20 dBc @ ≤1.5 µsec
• −30 dBc @ ≥1.5 µsec
• −10 dBc @ ≤0.5 µsec
• −15 dBc @ ≥1.0 µsec
Microreflections* Microreflection powerNote 1 n/a
Single echo:
• −10 dBc @ ≤0.5 µsec
• −20 dBc @ ≤1.0 µsec
• −30 dBc @ >1.0 µsec
Downstream Power* Downstream power at the E-UE n/a −3 to 3
Upstream Power* Upstream power at the E-UE n/a 50 to 60
EQI Average* Average Echo Quality Index 0 to 1 > 0.6Note 2
EQI Minimum* Minimum measured EQI 0 to 1 > 0.3Note 2
EQI Maximum* Maximum measured EQI 0 to 1 > 0.7Note 2
EQI Instantaneous* Last measured EQI 0 to 1 > 0.6Note 2
MOS-LQ Listening Quality score 1.0 to 5.0 3.5+
MOS-CQ Conversational Quality score 1.0 to 5.0 3.5+
Echo Return
Residual echo return loss, in dB 0 to 255 40+
Loss
Signal Level Relative voice signal level, in dB, compared to dBm0 −128 to 127 −15 to −20
Silent period background noise level, in dB,
Noise Level −128 to 127 < −70
compared to dBm0
Loss Rate Fraction of RTP data packets lost 0 to 255 0
Pkt Loss
How the eDVA is concealing lost packets n/a n/a
Concealment
Discard Rate Fraction of RTP data packets discarded 0 to 255 0
Fraction of RTP data packets lost or discarded within
Burst Density 0 to 255 0
burst periods
Fraction of RTP data packets lost or discarded within
Gap Density 0 to 255 0
inter-burst gaps
Burst Duration Mean duration, in milliseconds, of burst periods 0 to 65535 0
Gap Duration Mean duration, in milliseconds, of gap periods 0 to 65535 near Call Duration
Most recently calculated round trip time between
Round Trip Delay 0 to 65535 0 to 60
RTP interfaces, in milliseconds
Ranges
Metric Description
Allowed Good
Most recently calculated end system delay, in
End System Delay 0 to 65535 0 to 120
milliseconds
Gmin Gap threshold 0 to 255 16
Voice: 90+
R Factor Voice quality of the call carried over this RTP session 0 to 100
Fax: 70–90
Voice quality of the call carried over network
External R Factor 0 to 100 90+
segments external to this RTP session
Voice calls: Adaptive
Jitter Buf Adaptive Jitter Buffer adaptation n/a
Fax calls: Fixed
Jitter Buf Rate The adjustment rate in adaptive mode 0 to 15 0 to 15
Voice: approx. 20ms
JB Nominal Delay Current nominal jitter buffer delay, in milliseconds 0 to 65535
Fax: approx. 70ms
JB Max Delay Current maximum jitter buffer delay, in milliseconds 0 to 65535 0 to 60
Absolute maximum jitter buffer delay, in
JB Abs Max Delay 0 to 65535 0 to 60
milliseconds
Tx Packets Number of RTP packets transmitted n/a n/a
Tx Octets Number of octets transmitted n/a n/a
Rx Packets Number of RTP packets received n/a n/a
Rx Octets Number of octets received n/a n/a
Packet Loss Percentage of packets lost 0 to 100 <1
Jitter Estimated jitter, in milliseconds n/a approx. 2 ms
Voice Quality Mon- The arrisMtaDevVqm MIB provides objects for controlling the Voice Qual-
itoring MIB Ob- ity Monitoring (VQM) feature and for retrieving VQM data. See ‘‘Managing
jects Voice Quality Monitoring’’ on page 371 for more information.
The following objects are available.
arrisMtaDevVqmLine
Specifies the line for Voice Quality Metrics reporting. Writing to
this object loads the arrisMtaDevVqmCallNumberTable with the
buffer IDs for the last 10 calls on the specified line.
arrisMtaDevVqmCallNumberIds
Provides the buffer numbers containing VQM data for the last 10
calls on the line specified by arrisMtaDevVqmLine. This object is
indexed starting with the most recent call; that is,
arrisMtaDevVqmMetricValues
The entries in the arrisMtaDevVqmMetricTable that contain the
call data. Walk the arrisMtaDevVqmMetricTable to retrieve the
data in the buffer.
arrisMtaDevVqmThresholdEnable
Enables VQM threshold monitoring. See ‘‘Setting VQM Thresh-
olds’’ on page 387 for details.
arrisMtaDevVqmHistorySize
Sets the size of the VQM history buffer. Valid range: 2 to 50
records. Default: 10.
arrisMtaDevVqmCallNumberIdentifierLastCall
Reading this object updates the arrisMtaDevVqmCallNumber-
Identifier object to point to the metrics for the last call. After read-
ing this object, walking the arrisMtaDevVqmMetricTable shows the
last call metrics.
arrisMtaDevVqmThresholds
A table of monitoring thresholds. The eDVA generates a Syslog
message if VQM data scores fall below the specified thresholds.
arrisMtaDevVqmEnableRemote
Controls remote collection of VQM data. Use normal(0) to use
PacketCable rules; forceDisable(1) to force-disable remote VQM;
or forceEnable(2) to force-enable remote VQM. When set through
SNMP, the setting persists across reboots.
Collecting Remote Touchstone firmware supports recording and display of far-end voice quality
Metrics metrics. The following conditions must be true for the eDVA to receive far-
end metrics:
• The remote eDVA must support the RTCP-XR protocol.
• The call must be up long enough to receive remote data (remote metrics
not received display a value of ‘‘Call too Short’’).
Touchstone NCS loads comply with PacketCable 1.5 NCS specifications
(PKT-SP-NCS1.5-I03-070412). SIP loads comply with IETF draft-ietf-sip-
ping-rtcp-summary-02 for enabling and sending remote VQM data. For NCS
loads and default operation, eDVAs send VQM data:
1 if the Call Server has not instructed the eDVA to disable remote
VQM; and
2 the remote eDVA requests VQM data.
For SIP operation, Touchstone eDVAs send remote VQM data upon request
from the far end.
Note: The arrisMtaDevVqmEnableRemote MIB object can force remote
metric data, either on or off, for all loads. In NCS operation, this object can
override directives from the Call Server.
Configuring Local Follow these steps to configure local Voice Quality Monitoring using SNMP
VQM Reporting or the CLI (the web-based interface does not support enabling or disabling
VQM). VQM is enabled by default with a history buffer size of 10.
1 To enable or disable VQM using SNMP:
a Set the arrisMtaDevVqmEnable object to control local collection
of VQM data. Use 0 to disable local VQM, or 1 to enable local
VQM.
b Set the arrisMtaDevVqmEnableRemote object to control remote
reporting of VQM data. Use normal(0) to use PacketCable rules;
forceDisable(1) to force-disable remote VQM; or forceEnable(2)
to force-enable remote VQM. When set through SNMP, the set-
ting persists across reboots.
c To set the size of the VQM buffer, set the arrisMtaDevVqmHis-
torySize object.
Retrieving the Last Follow these steps to retrieve data for the last completed call using SNMP.
Call Using SNMP See ‘‘Retrieving VQM Data Using SNMP’’ to retrieve arbitrary call data.
1 Read the arrisMtaDevVqmCallNumberIdentifierLastCall object.
The eDVA updates the arrisMtaDevVqmCallNumberIdentifier object
and loads the arrisMtaDevVqmMetricTable with the data for the last
call.
2 Walk the arrisMtaDevVqmMetricTable to read the metrics from the
specified buffer.
Retrieving VQM Retrieving arbitrary VQM data through SNMP is more complex than the CLI
Data Using SNMP or web-based methods, requiring a multi-step process. To retrieve data for
the last completed call, see ‘‘Retrieving the Last Call Using SNMP’’ above.
Follow these steps to retrieve VQM data through SNMP. See ‘‘Voice Quality
Monitoring MIB Objects’’ on page 378 for detailed descriptions of VQM-
related MIB objects.
1 Write the desired line number to the arrisMtaDevVqmLine object.
Valid range: 1 to the number of lines supported by the eDVA.
The eDVA loads the arrisMtaDevVqmCallNumberTable with pointers
to reports for up to the last 10 calls.
2 Walk the arrisMtaDevVqmCallNumberTable to read the buffer IDs:
***** SNMP QUERY STARTED *****
1: arrisMtaDevVqmCallNumberIds.1 (integer) 19
2: arrisMtaDevVqmCallNumberIds.2 (integer) 16
3: arrisMtaDevVqmCallNumberIds.3 (integer) 14
4: arrisMtaDevVqmCallNumberIds.4 (integer) 12
5: arrisMtaDevVqmCallNumberIds.5 (integer) 11
6: arrisMtaDevVqmCallNumberIds.6 (integer) 9
7: arrisMtaDevVqmCallNumberIds.7 (integer) 6
8: arrisMtaDevVqmCallNumberIds.8 (integer) 4
9: arrisMtaDevVqmCallNumberIds.9 (integer) 2
Retrieving VQM Follow these steps to retrieve VQM data using the command-line interface.
Data Using the CLI This procedure assumes you are already logged into the CLI at the top level.
1 Enter the Voice → VQM submenu:
Console> voice ↵
Voice> vqm ↵
where . . . is . . .
line The line number. Valid range: 1 to
the highest line on the E-UE.
call The call number. Valid range: 1 to
10 (where 1 is the most recent
call), or 0 to print all calls for the
specified line.
Retrieving Follow these steps to retrieve VQM data using the web-based interface.
VQM Data Using 1 Access the Advanced web pages as described in ‘‘Accessing the
the Web-based Advanced Pages’’ on page 457.
Interface
2 Select the VQM link from the menu bar.
The Voice Quality Metrics page displays. If there have been no calls
since the last reboot, the page displayed is blank as shown below.
3 Select the line number from the Line Number drop-down. Valid
range: 1 to the number of lines on the eDVA.
4 Select the call number from the Call Number drop-down. Valid
range: 1 to 10, or All to display all call data in a report format, or Ta-
ble to display all call data in a table format.
Examples:
Setting VQM Follow these steps to set threshold monitoring. The eDVA sends a Syslog
Thresholds notification if a call does not meet the specified thresholds.
1 Configure event reporting for the ‘‘VQ Threshold’’ log as described
in the Touchstone Telephony Provisioning Guide. The Event ID for
this log is 49.
2 To enable threshold monitoring, set the arrisMtaDevVqmThreshold-
Enable object to the maximum number of ‘‘VQ Threshold’’ logs
desired for reporting a threshold crossing.
In practice, a single call may send up to three logs to report metrics
for a threshold crossing. To minimize unnecessary network traffic,
Touchstone firmware only reports metrics for which values were
obtained (for example, if the eDVA does not receive remote metrics,
it does not report any).
3 Set the instances in the arrisMtaDevVqmThresholds table to moni-
tor VQM data as follows:
Index Parameter
.16 MOS-LQ score (0.1 to 5.0)
.17 MOS-CQ score (0.1 to 5.0)
4 If you have added these objects to the eDVA configuration file, reset
the eDVA to allow the changes to take effect.
Clearing VQM Follow these steps to clear VQM data for either a single line or all lines.
Data 1 To clear VQM data using SNMP:
a To clear a single line, set the arrisMtaDevVqmLine object to the
desired line number.
Note: You can skip this step if you want to clear all lines.
b Write one of the following values to the arrisMtaDevVqmClear
object:
0 — clear a single line
Requirements and Speedtest is supported only on Model 7 and Model 8 Telephony Modems and
Limitations Telephony Gateways. Specifically, the following models are supported:
• WBM760, CM820
• TM702, TM722
• TM802, TM804, TM822
• TG852, TG862
The WBM750 is specifically not supported.
Server Requirements
An HTTP server used for Uplink testing must meet the following require-
ments:
• HTTP 1.1 support
• Support for an upload submission form, with an input element of type
FILE
• The server must provide a script to process POST HTTP requests, in
accordance with RFC 1867
Testing Limitations
Running a Speed Follow these steps to use the Speedtest web page. Note that this requires
Test using the access to the Advanced web pages.
Web Pages 1 Access the Advanced web pages as described in ‘‘Enabling and
Accessing the Troubleshooting CLI’’ on page 435.
Filename
Enter the filename to transfer. For Download tests, the modem
discards the information received. For Upload tests, the
modem sends random data to the server.
Note: The following parameters are optional. You can accept the
defaults.
TCP Window
The size, in KB, of the receive buffer used in the transfer.
TCPMSS
The maximum TCP segment size, in bytes.
TCP Timestamps
Check this box to enable TCP timestamping.
Path MTU Discovery
Check this box to negotiate the MTU size for the transfer.
MTU
When Path MTU Discovery is not checked, specifies the size
(in bytes) for the MTU.
4 Click the Save button to save the settings.
5 Repeat steps 3 and 4 to configure test parameters for the other direc-
tion (download vs. upload), if desired.
6 To test both upload and download speeds, select Download / Upload
from the Test direction drop down menu.
7 Click the Start button to begin the speed test.
The Start button changes to Cancel.
8 Allow the test to run, or click the Stop button to end the test before
the transfer is complete.
The test results display in the upper section of the Speedtest page.
Running a Speed Follow these steps to run a speed test using SNMP.
Test using SNMP 1 To configure the download test, set the arrisSpeedTestConfig-
DownlinkURL object to the URL specifying the server and file used
for the transfer. The URL begins with either ftp:// or http://,
and is followed by:
[userID:password@]ipaddr/path[?param=value[¶m=value...]]
The userID and password are required for FTP transfers, and
optional for HTTP transfers. The param list may consist of any of
the following:
Parameter Description
tcpwindow The size, in KB, of the receive buffer used in the
transfer.
tcpmss The maximum TCP segment size, in bytes.
tcptimestamps Set to 1 to enable TCP timestamping.
pmtud Set to 1 to negotiate the MTU size for the trans-
fer.
mtu When pmtud is set to 0, specifies the size (in
bytes) for the MTU.
cpeaccess Set to 1 to allow CPE network access during the
speed test, or 0 to disable CPE access.
Example:
ftp://root:[email protected]/wolves_hockey.mpg?
tcpwindow=2048&tcpmss=1460&tcptimestamps=1
&pmtud=1&cpeaccess=1
2 To configure the upload test, set the arrisSpeedTestConfigUplink-
URL object to the URL specifying the server and file used for the
transfer. The format of the URL is the same as for the download
object described above.
3 To start the test, write startDownlinkTest(1) or startUplinkTest(2)
(or both) to the arrisSpeedTestConfigStartStopTest object as
needed.
4 Allow the test to complete, or write stopTest(0) to the arris-
SpeedTestConfigStartStopTest object to end the test early.
Running a Speed Follow these steps to run a speed test using the CLI. This task requires
Test using the CLI access to the CLI.
1 Access the CLI as described in ‘‘Enabling and Accessing the Trou-
bleshooting CLI’’ on page 435.
2 Enter Speedtest at the Console> prompt to enter the Speedtest sub-
menu.
3 (optional) Use the ShowConfig command to display the current con-
figuration.
4 To configure the test, enter the following commands:
Configure dir ↵
Mode protocol [mode] ↵
Address ipaddr ↵
File path ↵
where... is...
dir either up or down.
protocol either ftp or http, depending on the server.
mode for FTP tests only, either passive or active.
ipaddr the IP address or FQDN of the server.
path the path to the file to download.
CLI Access Levels The CLI may be accessed through either Telnet or SSH2. Each method (Tel-
and Defaults net or SSH2) can be individually enabled or disabled.
There are two access levels in Touchstone gateway products running TS7.5:
Technician level
Technician-level access is always available before the CM portion
of the gateway has ranged and registered, even if the CLI is dis-
abled through provisioning. Technician access is restricted to
router configuration.
The default password used for technician-level access is techni-
cian. This password can be changed through XML provisioning or
through TACACS-related CLI commands and SNMP MIB objects.
General level
General-level access allows access to all the commands listed in
this document. The arrisCmDoc30AccessTelnetEnable object
provides a master control over general-level access. Other objects,
described in ‘‘Enabling and Accessing the Troubleshooting CLI’’
on page 435, provide further control.
The Password of the Day (PWoD) is needed for access to the gen-
eral-level CLI. See ‘‘Using the Password of the Day Tool’’ on
page 431 for details.
WebGUI Access The WebGUI can be accessed from the WAN or LAN interfaces. It has two
Levels and De- levels of access:
faults Subscriber level
Subscriber level access is restricted to user-controlled settings, and
is only available at non-gateway LAN interfaces.
User name: admin
Default password: password (can be changed by the subscriber)
Technician level
Technician level access allows making changes to all settings avail-
able in the WebGUI. It is available at the WAN interface and non-
gateway LAN interfaces.
User name: technician
Default password: none (the ARRIS Password of the Day also
allows access)
LED Patterns
The Touchstone Telephony Modem has eight indicator lights to assist in trou-
bleshooting. Note that not all models have a Battery light.
Battery Mismatch If the Telephony Modem alternates flashing the Battery light and all other
lights, the installed battery is incompatible with the Telephony Modem.
Remove the battery and install a supported battery.
Wiring Problems If the Telephony Modem begins flashing all its lights for more than 10 sec-
onds, this indicates a problem with the telephone wiring—the tip and ring
(red and green) wires may be shorted (touching), or there may be undesired
voltage on the lines. If this pattern persists for more than 10 seconds, discon-
nect the telephone lines from the Telephony Modem, then call a wiring tech-
nician for assistance.
TM702 Normal Op- The following table shows LED patterns during normal operation.
eration
Tel. 1/
Mode Power DS US Online Link Battery
Tel. 2
AC Power On On = Con- On = Con- On = On = On = On- On = Bat-
Good nected to the nected to the Internet Computer hook tery good or
Internet Internet available connected low1
Flash = Off-
Flash = Not Flash = Not Off = Off = hook Off =
connected to connected to Internet not Computer Battery
the Internet the Internet available not con- Off = missing or
nected Disabled eDVA not
registered
Flash =
Computer Flash = Bat-
Activity tery bad
No AC Flash Off Off Off Off On = On- Off = Bat-
Power hook tery power
Battery
Installed Flash = Off- Flash = Bat-
hook tery bad or
low
Off = dis-
abled
No AC
Power No Off Off Off Off Off Off Off
Battery
Firmware (normal (normal (normal
On Flash Flash On
Upgrade operation) operation) operation)
Note 1: Loads with a .TW extension flash the Battery LED for the Battery
Low condition, regardless of the AC Power state, and turn off the Battery
LED for the Replace Battery state.
TM722/TM802/TM804/TM822
The following table shows LED patterns during normal operation.
Normal Operation
Tel. 1/
Mode Power DS US Online Link Battery
Tel. 2
AC Power On Green1, 3 = Green1, 3 = On = Inter- Green2, 3 = On = On- On = Bat-
Good Connected Connected net Avail- Connected hook tery good or
to the Inter- to the Inter- able (high-speed) low4
net (high- net (high- Flash = Off-
speed) speed) Off = Inter- Yellow2 = hook Off = Bat-
net not Connected tery missing
Yellow1 = Yellow1 = available (normal Off = or eDVA not
Connected Connected speed) Disabled registered
to the Inter- to the Inter-
net (normal net (normal Off = Com- Flash = Bat-
speed) speed) puter not tery bad
connected
Flash = Not Flash = Not
connected to connected to Flash =
the Internet the Internet Computer
activity
No AC Flash Off Off Off Off On = On- Off = Bat-
Power hook tery power
Battery
Installed Flash = Off- Flash = Bat-
hook tery bad or
low
Off = dis-
abled
No AC
Power No Off Off Off Off Off Off Off
Battery
Firmware (normal (normal (normal
On Flash Flash On
Upgrade operation) operation) operation)
Note 1: For the TM722 and Model 8 DS and US LEDs, ‘‘High-speed’’ means
2–4 bonded channels; ‘‘normal speed’’ is a single channel.
Note 2: For the TM722 and Model 8 Link LED, ‘‘High-speed’’ means no
10/100 BaseT Ethernet or USB 1.1 devices are connected directly to the
Telephony Modem; ‘‘normal speed’’ means at least one of the connected
devices are 10/100 BaseT or USB 1.1.
Note 3: You can configure the Telephony Modem to always display US, DS,
and Link LEDs in green, by setting the arrisCmDoc30SetupMultiColorLed-
Bitmap object to 0.
Note 4: Loads with a .TW extension flash the Battery LED for the Battery
Low condition, regardless of the AC Power state, and turn off the Battery
LED for the Replace Battery state.
TM702/TM722/TM802/TM804/TM822
The following tables show the Telephony Modem LED patterns during each
Startup Sequence phase of the startup sequence. There are two phases of startup: the Tele-
phony phase and the cable modem phase. Both are outlined below.
Note 1: When On, the TM722 and Model 8 Link LED color is green if all
connected devices are high-speed (1000BaseT Ethernet or USB 2.0), and yel-
low if any connected device is normal speed (10/100BaseT Ethernet or
USB 1.x).
TG852G Normal The following table shows LED patterns during normal operation.
Operation
Tel. 1/
Mode Power DS US Online Ethernet WiFi Secure Battery
Tel. 2
AC Power On Green1,3 Green1,3 On = Green2,3 On = On = On = On- On = Bat-
Good = Con- = Con- Internet = Con- Computer WPS con- hook tery good
nected to nected toAvailable nected connected nection or low4
the Inter- the Inter- (high- estab- Flash =
net (high- Off =
net (high- speed) Off = lished Off-hook Off = Bat-
speed) speed) Internet Computer tery miss-
not avail- Yellow2 = not con- Off = No Off = dis- ing or
1 1
Yellow = Yellow = able Con- nected WPS con- abled eDVA not
Con- Con- nected nection registered
nected to nected to (normal Flash = estab-
the Inter- the Inter- speed) Wifi activ- lished Flash =
net (nor- net (nor- ity Battery
mal mal Off = Flash = bad
speed) speed) Computer WPS
not con- search
Flash = Flash = nected active
Not con- Not con-
nected to nected to Flash =
the Inter- the Inter- Computer
net net activity
No AC Flash Off Off Off Off Off Off On = On- Off = Bat-
Power hook tery
Battery power
Installed Flash =
Off-hook Flash =
Battery
Off = dis- bad or low
abled
No AC
Power No Off Off Off Off Off Off Off Off Off
Battery
Firmware (normal (normal (normal (normal (normal
On Flash Flash On
Upgrade operation) operation) operation) operation) operation)
Note 1: For the DS and US LEDs, ‘‘High-speed’’ means 2–4 bonded chan-
nels; ‘‘normal speed’’ is a single channel.
Note 2: For the Link LED, ‘‘High-speed’’ means no 10/100 BaseT Ethernet
devices are connected directly to the Telephony Modem; ‘‘normal speed’’
means at least one of the connected devices are 10/100 BaseT.
Note 3: You can configure the Telephony Modem to always display US, DS,
and Link LEDs in green, by setting the arrisCmDoc30SetupMultiColorLed-
Bitmap object to 0.
Note 4: Loads with a .TW extension flash the Battery LED for the Battery
Low condition, regardless of the AC Power state, and turn off the Battery
LED for the Replace Battery state.
TG852G Startup The following tables show the Telephony Gateway LED patterns during each
Sequence phase of the startup sequence. There are two phases of startup; the Tele-
phony phase and the cable modem phase. Both are outlined below.
Note: The states of the WiFi and Secure LEDs are not relevant in the startup
sequence.
Note 1: When On, the Link LED color is green if all connected devices are
high-speed (1000BaseT Ethernet or USB 2.0), and yellow if any connected
device is normal speed (10/100BaseT Ethernet or USB 1.x).
TG852G/CT Nor- TG852G/CT models have single-color LEDs, and a single LED (DS/US)
mal Operation provides downstream and upstream indication as shown in the following ta-
ble.
Tel. 1/
Mode Power US/DS Online Wifi Battery
Tel. 2
AC Power On On = Con- On = Inter- On = Device On = On- On = Bat-
Good nected to the net Available connected hook tery good or
Internet low
Off = Inter- Off = No Flash = Off-
Flash/Off = net not avail- device con- hook Off = Bat-
Not con- able nected tery missing
nected to the Off = dis- or eDVA not
Internet Flash = abled registered
Computer
Activity Flash = Bat-
tery bad
No AC Flash Off Off Off On = On- Off = Bat-
Power Bat- hook tery power
tery Installed
Flash = Off- Flash = Bat-
hook tery bad or
low
Off = dis-
abled
No AC
Power No Off Off Off Off Off Off
Battery
Firmware (normal (normal (normal
On Flash On
Upgrade operation) operation) operation)
TG852G/CT Start- The following tables show the Telephony Gateway LED patterns during each
up Sequence phase of the startup sequence. There are two phases of startup; the Tele-
phony phase and the cable modem phase. Both are outlined below.
Power, Telephone
US/DS Link Battery Description
Online 1 2
Off Off Off Off Off Off No power to Cable
Modem
Flash Flash Flash Flash Flash Flash Power-on Self Test
See ‘‘Cable Modem Start Up Sequence’’ Below
On On On Flash Off Off Retrieving tele-
phone network
information
On On On Off Flash Off Retrieving tele-
phone line infor-
mation
On On On Flash Flash Off Activating tele-
phone service
SIP Concepts
The following are definitions and concepts useful for working with SIP.
Authorization SIP authentication currently uses the HTTP digest algorithm. Any request
can be authenticated. The authentication mechanism works as follows:
1 The P-CSCF challenges the request by rejecting it with a 401 or 407
response.
2 The eDVA re-sends the request with an authorization header.
The 401/407 message includes a nonce (number used once) that the eDVA
hashes with its username and password. This prevents an intruder from
snooping the session to re-use the communication to authenticate. The P-
CSCF periodically requires a new nonce to be used.
The list of authorization headers persist until the dialog is torn down. The
eDVA may modify this list to prevent the list from getting too long. Each
new 401/407 message typically adds a new authorization header to this list.
Note: PacketCable 2.0 requires more sophisticated authorization methods
which Touchstone firmware currently does not support.
Registration A SIP device must register with a registrar periodically. The registrar asso-
ciates the SIP URI (including the phone number) with the device and stores
this association in a database. This allows the P-CSCF to determine how to
locate the device to ring the phone on incoming calls.
Registration is not required for outbound calls. TS5.2 and earlier versions
would not play dial tone or allow outbound calls to be placed until the eDVA
had registered at least once. Current versions allows outbound calls before
registration, allowing emergency calls without registering first.
Each registration succeeds when the registrar responds with a 200 OK mes-
sage. This response includes an ‘‘expires’’ value in either the Expires:
header or the Contact: header. The eDVA attempts to re-register with the
registrar at a random time period between one-half and the full expiration
value. This expiration value is specified in seconds.
The eDVA can offer an expiration value to the P-CSCF. The eDVA’s offer is
the lower of the expiration value specified in the configuration file and the
expiration value specified in the registrar response. The P-CSCF is not
bound to accept the offer.
The sip_reg command in the CallP sub-mode allows tracing of SIP registra-
tion-related messages.
Implicit Subscriptions
A call transfer is initiated when the SIP endpoint sends a REFER message.
This REFER message creates an implicit subscription. The receiver of the
REFER message uses NOTIFY messages to inform the endpoint of the call
transfer status. The REFER message is either sent over the call’s existing
dialog or uses a Target Dialog: header. The Target Dialog method is used if
the far-end includes a ‘‘tdialog’’ item in its Supported: header.
Call Legs The eDVA initiates a call by sending an INVITE message. Touchstone
firmware includes an SDP with this INVITE message. The SDP informs the
far-end what types of CODECs are supported and where to send the audio.
The P-CSCF usually responds with a provisional response (100 Trying) to
indicate that it is in the process of reaching the far end.
After the far-end receives the INVITE, it usually responds with one of the
following codes:
180 The far-end is providing power ringing and the originator should pro-
vide local ringback tone.
183 The far-end is providing power ringing and providing remote ring-
back tone in the form of audio media.
• reINVITE:
To: <sip:[email protected]:5060>;tag=95490288-a013d1f-
13c4-50029-bb-6edc1cd1-bb
401 Unauthorized
ACK sip:[email protected]:5060
100 Trying
180 Ringing
180 Ringing
200 OK w/SDP
200 OK w/SDP
ACK sip:[email protected]:5060
ACK sip:[email protected]:5060
BYE sip:[email protected]:5060
BYE sip:[email protected]:5060
200 OK
200 OK
The following diagram shows signaling flows for a basic call using PRACK.
401 Unauthorized
ACK sip:[email protected]:5060
PRACK sip:[email protected]:5060
PRACK sip:[email protected]:5060
200 OK
200 OK
200 OK
200 OK
ACK sip:[email protected]:5060
ACK sip:[email protected]:5060
BYE sip:[email protected]:5060
BYE sip:[email protected]:5060
BYE sip:[email protected]:5060
200 OK
200 OK
200 OK
Forking
During a call, P-CSCFs can make flexible routing decisions to decide where
to send a request. A P-CSCF can send an INVITE to a number of locations
at the same time. This type of parallel search is known as forking.
Multiple 2xx responses may arrive at the UAC for a single INVITE request
due to a forking P-CSCF. Each response is distinguished by the tag parame-
ter in the To: header field, and each represents a distinct dialog, with a dis-
tinct dialog identifier.
CODEC negotiation in Call Leg forking is done per-dialog. This means that
if the offer is included in the initial INVITE, an answer can be in a response,
for example a 183, in one dialog. Another answer can be in a 200 in another
dialog. P-CSCFs may use this feature to negotiate an intermediate media
gateway for voice mail or other similar systems. Without Call Leg forking,
the only way to achieve this intermediate media gateway is to use a 183 with
SDP but without PRACK. This 183 contains a ‘‘hint’’ answer but does not
constitute a final answer in offer/answer terms. The eDVA communicates
with this ‘‘hinted’’ media gateway if it receives the 183, but it is not guaran-
teed.
The following diagram shows the signaling flow for call forking.
Proxy/
MTA
Sipp
200 OK w/SDP
200 OK
Offer/Answer The Offer/Answer RFC (RFC 3264) explains how negotiation is done to set
up a media path between two endpoints. In the basic version, the first SDP in
a transaction is the ‘‘Offer.’’ The second SDP in the final response (200) is
the ‘‘Answer.’’ If the offer is included in an INVITE request, the answer is
included in the 200 OK. If the offer is included in the response, the answer is
included in the ACK. If the offer is included in an INVITE message, a
‘‘hint’’ about the answer may be included in a 1xx message. If this is the
case, the answer must still be included in the final response. This changes if
PRACK is enabled.
PRACK
Session Timer SIP connections use a session timer to prevent calls from staying up indefi-
nitely because an endpoint was turned off or unplugged. This requires the
endpoint to ‘‘refresh’’ after a period of time. If the endpoint fails to refresh
the connection, the connection is destroyed.
There are two methods of refreshing the connection:
• UPDATE messages (preferred method). The eDVA looks at the
Allow: header of previous messages on the call to determine if the
UPDATE message is allowed. CODEC negotiation is optional in
UPDATE messages, which prevents QoS from being redone.
• reINVITE messages. If UPDATE messages are not allowed, or SIP
feature switch 0x00000200 is enabled, the endpoint uses a reINVITE
to refresh the session. CODEC selection and QoS are renegotiated.
SRV SRV is a type of DNS lookup that determines the TTL, priority, weight, and
port of a particular target. To query for a record, the eDVA must specify that
it would like to talk using SIP, and a specific transport (TCP or UDP) to a
particular name. The DNS server then responds with a record entry. This
record entry can be used to determine the port and target for communication.
The target is typically a FQDN that the eDVA uses in a subsequent standard
DNS lookup (A record) to get the IP address for communication.
Priority is used to specify a primary/secondary relationship for backup sce-
narios. The lower the number, the higher the priority.
Weight is used to load-balance between multiple P-CSCFs. The weight val-
ues are relative to other entries with the same priority value.
Example of SRV record:
_Service._Proto.Name TTL Class SRV Priority Weight Port Target
The UNIX dig command can be used to query a DNS server. Use the dig
man page to decipher all the options. The following is an example query and
response:
dig @10.1.63.10 SRV _sip._udp.ser.arris-i.org
;; QUESTION SECTION:
;_sip._udp.ser.arris-i.org. IN SRV
;; ANSWER SECTION:
_sip._udp.ser.arris-i.org. 120 IN SRV 10 10 5060 serc.arris-i.org.
_sip._udp.ser.arris-i.org. 120 IN SRV 30 10 5060 ser.arris-i.org.
_sip._udp.ser.arris-i.org. 120 IN SRV 10 10 5060 serb.arris-i.org.
;; AUTHORITY SECTION:
arris-i.org. 120 IN NS pc-alps.arris-i.org.
;; ADDITIONAL SECTION:
serb.arris-i.org. 120 IN A 10.1.63.12
serc.arris-i.org. 120 IN A 10.1.63.13
ser.arris-i.org. 120 IN A 10.1.63.10
pc-alps.arris-i.org. 120 IN A 10.1.63.10
Message When the transport is UDP, each request is retransmitted with an exponential
Retransmission backoff routine. This means that the interval between each retransmission
doubles after each retransmission. The initial interval is T1 seconds (.5 sec-
onds by default). Retransmissions stop when the originator receives a
response from the far-end. The final response will be retransmitted if it
receives a second copy of the original request.
For INVITE messages, retransmissions stop after Timer B expires (7 trans-
missions later by default).
Non-INVITE messages use a similar exponential backoff that doubles until
timer T2 expires. At this point, the interval remains at T2 until Timer F
expires.
SIP Message This section provides a brief description of SIP message types.
Overview
INVITE
CANCEL
A CANCEL message is used to terminate an outbound call that has not yet
been answered by the far end.
BYE
UPDATE
SUBSCRIBE
NOTIFY
REFER
The REFER message is currently used during Call Transfer. It is sent by the
transferrer towards the party being transferred. The receiver then looks at the
Refer-To: header to determine who to connect to and which active call to
replace.
The REFER message implicitly creates a subscription. For this reason,
REFER messages are printed out if the SIP subscription trace is used.
INFO
PRACK
Response Codes This section provides an abbreviated listing of SIP response codes. See
RFC 3261, section 21 for complete descriptions.
2XX - Successful
3XX - Redirection
3xx responses give information about the user’s new location, or about alter-
native services that might be able to satisfy the call.
4xx responses are definite failure responses from a particular server. The
client SHOULD NOT retry the same request without modification (for exam-
ple, adding appropriate authorization). However, the same request to a differ-
ent server might be successful.
5xx responses are failure responses given when a server itself has erred.
The called system was contacted successfully, but the callee is busy and does
not wish to take the call at this time. The response may indicate a better time
to call, in the Retry-After: header field.
If the callee does not wish to reveal the reason for declining the call, the
callee uses status code 603 (Decline). This status response is returned only if
the client knows that no other endpoint (such as a voice mail system) will
answer the request. Otherwise, 486 (Busy Here) should be returned.
References Touchstone SIP firmware loads fully or partially conform to the following
specifications:
• RFC 3261 — primary SIP specification
• RFC 3264 — Offer Answer
• RFC 3842 — VMWI: Voice Message Waiting Indicator
• RFC 2327 — SDP: Session Description Protocol
About Line Card Line card diagnostics check the following functionality:
Diagnostics • processor communication
• power/clock
• on-hook/off-hook functionality
• ring
Testing Overview Start line card diagnostics by using the diag or diagForce CLI commands.
Use the dresults command to show line card diagnostics results.
Action Follow these steps to run line card diagnostics from the CLI.
1 If necessary, access the CLI using the instructions in ‘‘Accessing the
CLI through Telnet’’ on page 437.
2 Enter the Line Card sub-menu:
[ 1]Console> voice ↵
[ 2]Voice> lc ↵
[ 3]Linecard>
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.
The failure types are shown below, with possible causes and symptoms:
Test Failure Possible Cause Possible Symptoms Normal Test
Data Limits
Tip-Grd Tip shorted to cable No dial tone, 60Hz buzz 150kΩ or
shield, moisture in cable, on line due to longitudi- greater
house line protection nal imbalance, no incom-
device shorted Tip to ing calls
Grd.
Ring-Grd Ring shorted to cable No dial tone, 60Hz buzz 150kΩ or
shield, moisture in cable, on line due to longitudi- greater
house line protection nal imbalance, no incom-
device shorted Ring to ing calls
Grd.
Ringers Test
Limitations
CAUTION
Service affecting
Performing loop diagnostics requires the line under test to be first taken out
of service. This must be done manually when using SNMP. The CLI and
web-based interfaces provide the option of forcing a line out of service. Note
that forcing a line out of service while a call is in progress, drops a call.
Perform loop diagnostics only during installation or a scheduled maintenance
window, unless the subscriber is unable to use the line.
Test Results You can examine the test results either by walking the arrisMtaDevDiag-
LoopTable entry that corresponds to the line under test, or by using the lpre-
sults CLI command (in the Linecard menu). Both SNMP- and CLI-based
tests display the date and time of the last test run, and the following possible
results for each test:
Result Meaning Action
Not Started No tests have been run Start (or re-start) the diagnostics.
since the modem was last
started.
In Progress Diagnostics are still run- Wait 10–20 seconds and try again.
ning
Invalid State The line must be out of Take the line out of service and
service (OOS) before retry the diagnostics.
starting loop diagnostics.
Aborted The test could not be Check the other tests for failures.
completed, possibly Correct any problems and re-try
because a higher order the diagnostics.
test failed.
Fail A test has failed. The results show the values
returned by the failing test. Cor-
rect any problems and re-try the
diagnostics.
Pass A test has passed. None.
Unsupported Loop diagnostics are not None.
supported on single-line
Telephony Modems.
If more than one a test failed, only the first failing test is shown.
The Telephony Modem stores the results of the last loop diagnostics run for
each line since the modem was started or rebooted. If the arrisMtaDevDiag-
LoopTime object is set to midnight on January 1, 1970, no loop diagnostics
have been run on that line since the modem was started or rebooted.
Running Loop Di- Follow these steps to run loop diagnostics from an SNMP network manage-
agnostics from an ment system.
SNMP Manager 1 Locate the eDVA and line you wish to test.
2 Use the following table to find the interface index number for the
line:
Line Interface
1 9
2 10
3 Take the desired line out of service by setting the associated ifAd-
minStatus MIB object to down(2). This object is indexed by the
interface number; use the interface number for the line found in
step 2. For example, ifAdminStatus.9 corresponds to line 1.
4 Set the arrisMtaDevDiagLoopRequest object for this line to
true(1). This object is indexed by the line number; that is,
arrisMtaDevDiagLoopRequest.1 corresponds to line 1.
The diagnostics begin running on the line. The tests require about 10
to 20 seconds to complete.
5 After 10 to 20 seconds, retrieve the diagnostics results from the
arrisMtaDevDiagLoopTable.
Running Loop Follow these steps to run loop diagnostics from the Telephony Modem CLI.
Diagnostics from 1 If necessary, access the CLI using the instructions in ‘‘Accessing the
the CLI CLI through Telnet’’ on page 437.
2 Enter the Line Card sub-menu:
[ 1]Console> voice ↵
[ 2]Voice> lc ↵
[ 3]Linecard>
Running Loop Di- Follow these steps to run loop diagnostics from the web-based troubleshoot-
agnostics from the ing interface.
Web-based Inter-
face
CAUTION
Service affecting
Performing loop diagnostics from the web-based interface give you the
option of taking the line under test out of service after confirmation.
If the chosen line is already running loop diagnostics, the E-UE dis-
plays the following warning. Wait for 10 to 20 seconds for the cur-
rent diagnostics run to complete before attempting to start another
(you can, however, start diagnostics on another line).
Failing:
Loopback Testing
Resetting the The TG852 Telephony Gateway provides an additional method of resetting
Router (TG852) the router to factory defaults without resetting the E-UE. To reset only the
router, use the ‘‘Reset/Reboot Gateway’’ web page under the Troubleshoot-
ing tab.
About the Pass- The PWoD tool, ARRISpwod.exe, is available through the Firmware Down-
word of the Day load Center. It is a Windows application, with the following requirements:
Tool • Windows 98, Windows NT, Windows 2000, Windows XP or Windows
7
• Microsoft.Net plus Service Pack 2. The installer provides this package
if required.
• Internet Explorer version 5.1 or newer. The newest version of Internet
Explorer is available at the Microsoft web site 〈http://
www.microsoft.com/windows/ie/default.asp〉.
The PWoD tool can create a single password, or a list of passwords for a
range of days (up to 365). For added security, you can also define a seed
value used to generate the passwords.
Before performing any of the tasks in this procedure, double-click the file to
start the PWoD tool. The following diagram shows the tool.
Changing the The PWoD tool can use a default seed to generate the password of the day.
Seed For added security, you can create a different seed to change the password
pattern. Follow these steps to change the seed.
1 Start the PWoD tool, if you have not done so already.
2 Enter a new seed value (4 to 8 ASCII characters) in the Seed field at
the top of the PWoD window. Make sure the Use Default Seed box
is not checked.
The encoded seed appears in the DES encoded field.
Note: The Touchstone E-UEs also need to have the changed seed so
that their internal PWoD generators remain in sync with the external
tool. Write the DES encoded seed to the arrisCmDevHttp-
ClientSeed MIB object in the eDVA configuration file.
SSH Login IDs The following SSH user accounts are supported:
• User name: root
Password: arris
After successfully logging in, the Telephony Modem displays the Password
of the Day prompt.
Enabling CLI Follow these steps to enable CLI access through the web-based interface.
Access Using the 1 Using any web browser, connect to the E-UE’s troubleshooting web
Web Pages pages using the CM IP address.
Note: You must use the CM IP address to enable CLI access.
2 Enable access to the Advanced web pages (see ‘‘Accessing the
Advanced Pages’’ on page 457 for details). Use the PacketACE
‘‘MSO Password of the Day’’ tool to generate the correct password.
The browser displays the URL in the form http://cm-
ipaddr/page.htm.
3 In the browser’s address line, replace the page name with
techsupport.htm and press Enter.
Note: If you see a ‘‘page not found’’ error, return to step 1 and try
again. Do not access any other Advanced pages before accessing the
Technical Support page.
4 Enter the password of the day (the same password you used to access
the Advanced pages) in the Arris Password field, set the Telnet Sta-
tus and SSH Status drop-downs to either disable or enable as
desired, then click the Submit Request button.
5 Proceed to ‘‘Accessing the CLI through Telnet.’’
Enabling CLI Follow these steps to enable CLI access using SNMP.
Access Using 1 Add the arrisCmDoc30AccessTelnetPassword object to the con-
SNMP figuration file, and set it to the MSO password of the day.
2 Reset the E-UE to apply the new settings.
3 Use an SNMP manager to set the following objects as desired.
arrisCmDoc30AccessTelnetEnable
Set to disable(0) to disable Telnet access, or enable(1) to
enable Telnet access.
arrisCmDoc30AccessSSHEnable
Set to disable(0) to disable SSH access, or enable(1) to enable
SSH access.
4 To enable CLI access through TACACS+ authentication, add the fol-
lowing objects:
arrisRouterTACACSAddr
The IP address or FQDN of the remote TACACS+ server.
arrisRouterTACACSPort
The port on which the TACACS+ server listens for connec-
tions.
arrisRouterTACACSServerKey
The authentication key used to access the TACACS+ server.
5 If you added these objects to the configuration files, reset the E-UE
to allow the settings to take effect.
Note: If you do not add the arrisCmDoc30AccessSSHEnable or
arrisCmDoc30AccessTelnetEnable objects to the CM configura-
tion file, you must add the arrisCmDoc30AccessTelnetPassword
object to the CM configuration file to prevent SNMP SET failures.
Setting the CLI You can configure a session timeout, that automatically terminates a CLI ses-
Timeout sion after a specified period of inactivity, through SNMP. Follow these steps
to set or disable the CLI timeout.
1 Set the arrisCmDoc30CLITimeout object to the time (in minutes)
the CLI may be idle until timeout. Valid range: 1 to 65535 minutes,
or use 0 to disable the timeout. Default: 1440.
Accessing the CLI Follow these steps to access the CLI through Telnet.
through Telnet 1 If you have not already done so, use ‘‘Enabling CLI Access Using
SNMP’’ on page 436 to make sure CLI access is enabled.
2 From a PC or workstation, start a Telnet program and connect to the
CM IP address of the E-UE.
The E-UE displays a banner message and an Enter Password>
prompt.
3 At the Enter Password> prompt, enter the MSO password of the day.
Use the PacketACE ‘‘MSO Password of the Day’’ tool to generate
the correct password.
If the password was entered correctly, the Telephony Modem displays
a login banner.
Accessing the CLI Follow these steps to access the CLI through SSH.
through SSH 1 If you have not already done so, use ‘‘Enabling CLI Access Using
the Web Pages’’ on page 435 to make sure CLI access is enabled.
2 From a PC or workstation, start an SSH program.
3 Connect to the CM IP address of the E-UE as follows:
• For graphical clients, set up the account with the correct account
based on ‘‘SSH Login IDs’’ on page 435.
• For command-line clients, enter the account on the command line
with the CM IP address. For example, Unix SSH clients use a
command similar to: ssh [email protected]
The E-UE displays a banner message and an Enter Password>
prompt.
4 At the Enter Password> prompt, enter the password for the account
as shown in ‘‘SSH Login IDs’’ on page 435. Use the PacketACE
‘‘MSO Password of the Day’’ tool to generate the correct password
of the day, if needed.
If the password was entered correctly, the Telephony Modem displays
a login banner.
Access Options You can access the troubleshooting screens through either the Touchstone
Telephony product RF or Ethernet interfaces.
Requirements You need the following equipment to access the troubleshooting pages:
• computer with an Ethernet interface and a web browser
• Ethernet cable (if using the E-UE Ethernet interface)
• (advanced pages only) the password of the day
Controlling The following MIB objects control access to the basic and advanced trou-
Access to the bleshooting pages.
Interface arrisCmDoc30AccessHttpLan
Values: disable(0), enable(1)
Determines which pages are available from the Ethernet port of the
E-UE. The value is stored in non-volatile memory.
arrisCmDoc30AccessHttpWan
Values: disable(0), enable(1)
Determines which pages are available from the network attached to
the CMTS. The value is stored in non-volatile memory.
arrisCmDoc30AccessHttpPwCtrl
Values:
none(0): No password is required for any screen;
advanced(1): The PWoD is required for Advanced screens;
all(2): The PWoD is required for all screens.
arrisCmDoc30AccessClientSeed
Changing the seed changes the results of the Password of the Day
(PWoD). See ‘‘Using the Password of the Day Tool’’ on page 431
for details about the PWoD. Store the seed value in the CM config-
uration file.
arrisCmDoc30AccessHttpTimeout
The time, in seconds, that the advanced pages are available before
the Telephony Modem requires password re-entry. Valid range: 1
to 1440 seconds, or 0 to disable the timeout.
arrisCmDoc30AccessSinglePassword
A DES-encoded password string, used to bypass the Password of
the Day mechanism. When this object is set, the Password of the
Day is disabled.
When using TACACS+ authentication, the following objects specify the
TACACS+ server to use and the password:
arrisRouterTACACSAddr
The IP address or FQDN of the remote TACACS+ server.
arrisRouterTACACSPort
The port on which the TACACS+ server listens for connections.
arrisRouterTACACSServerKey
The authentication key used to access the TACACS+ server.
Standard Screens Anyone can access the screens described in this section.
Status Screen
The status screen is the index page, and can also be selected by choosing the
Status link at any standard screen. The following is an example:
The Event Log screen displays a table of recent events. The E-UE stores the
event log in non-volatile memory. To display this screen, choose the Event
Log link.
The Registration Status screen shows the results of the E-UE registration
process and current battery telemetry state and serial number. To display this
screen, choose the CM State link.
Docsis-DHCP
Status of the CM DHCP phase. The Registration Status page also
displays the number of attempts required to obtain a CM IP
address.
Docsis-TFTP
Status of the CM configuration file download.
Docsis-Data Reg Complete
Shows whether the modem has completed DOCSIS data registra-
tion.
Telephony-ERR-LC Over Current Protection
Indicates that one or more phone lines are in protection mode. The
front panel LEDs indicate which lines are in protection mode.
Battery Mismatch
Indicates that the wrong battery has been inserted in the Telephony
Modem (see below).
If the Battery Part Number is ‘‘Contact ARRIS’’ as shown below, the battery
is either defective or the Telephony Modem has the wrong type of battery
installed.
The operational status is ‘‘No Status Reported’’ if the battery charger has
been disabled. Check the Event Log page for a ‘‘Battery Charger Disabled’’
alarm to verify. Power-cycle or reset the E-UE to re-enable the charger.
If you see this display, contact ARRIS Technical Support. Make a note of the
hexadecimal code and operational status before calling.
The following is a list of other messages that may appear in the Battery Serial
Number field:
Battery Serial Number Not Supported
The Telephony Modem does not read battery serial numbers.
Battery Missing
No battery is installed.
AC Failed. S/N Temporarily Unavailable
Appears when the Telephony Modem is running on battery power.
Unable to obtain Battery Serial Number(s)
Appears in cases where the serial number is missing or unreadable.
Wireless Screen
To return to the Basic pages from the Wireless page, click the HSD link at the
top of the page.
See the ARRIS Router Setup Web GUI User Guide for details about the wire-
less pages.
The Scanning Override screen allows a technician to force the cable modem
to look for a carrier on a specified downstream frequency.
This screen does not have a link from the other screens. See ‘‘Provisioning
Preset Downstream Frequencies’’ on page 118 for instructions on accessing
and using this screen.
Advanced Screens The following screens require a Password of the Day (see ‘‘Using the Pass-
word of the Day Tool’’ on page 431 for details). Use the Basic link on any
screen to return to the standard status pages.
Note: Advanced screens contain potentially sensitive information about the
network.
DHCP Parameters
The DHCP Parameters screen lists DHCP details for the cable modem and
eDVA portions of the E-UE, including IPv4 or IPv6 addresses as appropriate.
To access this screen, choose the DHCP link from any advanced screen.
The DHCP Parameters screen provides links to CM DHCP and eDVA DHCP
message trace logs.
The QoS Statistics screen shows the eDVA QoS statistics. To access this
screen, choose the QoS link from any advanced screen.
Note: Currently, the packet counts for the downstream service flows are not
incremented and always show 0.
At the bottom of the screen, the following controls provide control and dis-
play of the CallP signalling log:
• The Show Call Signalling Log button displays the Call Signalling
Log.
• The Disable Logging button disables CallP signal logging. When
logging is disabled, the button name becomes Enable Logging.
• The Clear button clears the CallP signalling log.
The Call Signalling Log screen shows the call signaling log.
The Technical Support screen allows an operator to set access parameters for
the CLI and web pages. This screen does not have a link from the other
screens. See ‘‘Enabling CLI Access Using the Web Pages’’ on page 435 for
details on accessing and using this screen.
Results Section
The top of the screen displays each of the three latest results. The Prev and
Next buttons allow the user to cycle through each of the stored results. In the
screen displayed above, the screen displays the latest result (Next is dis-
abled), and there are older results available (Prev is enabled).
Configuration Section
The configuration section can be used to change the test parameters. Two
sets of parameters are available, for Upload or Download. Select Upload or
Download from the ‘‘Test Direction’’ drop down to select which set of con-
figuration data to display. The default test configuration runs both download
and upload tests.
The following parameters are available. Unless noted, these apply to both
upload and download tests.
Test Direction
Choose Upload Only or Download only to configure the test. The
selection Download / Upload does not allow changing parameters,
but allows both tests to run.
Test Mode
Choose HTTP or FTP.
Server Address
The IP address or FQDN of the server to use for the speed test.
Server Port
The port number for the server. Default: 21 for FTP, 80 for HTTP.
Server Username
If required, the user ID used to log into the server.
Server Password
If required, the password used to log into the server.
Filename
(Download only) The file name to download from the server. The
file size should be at least 10MB.
Upload Size
(Upload only) The amount of data, in MB, to send to the server.
Scriptname
(Upload only) For HTTP servers, the name of the script used to
read the POST data sent to the server.
POST fields
(Upload only) For HTTP servers, any fields needed to pass to the
script. Fields have the format name˜value, and are separated by
ampersand (&) characters.
File Field
(Upload only) For HTTP servers, the name of the field in the
upload form that receives the uploaded file.
Use the Save button to save your configuration before switching to the other
set of parameters.
Accessing the Follow these steps to access the standard troubleshooting pages.
Standard Pages 1 Make sure the E-UE is configured to allow access to the pages (see
‘‘Controlling Access to the Interface’’ on page 439).
2 Obtain the cable modem IP address of the E-UE.
Note: If the E-UE has not registered, you can access the pages only
from the Ethernet interface. After registration, you can use either the
RF or Ethernet interfaces.
The Ethernet interface recognizes connections to the address
192.168.100.1, whether or not the modem has registered. To use this
address, set your computer’s IP address to an address in the same
subnet, such as 192.168.100.2.
3 Start your web browser and access the E-UE using the address
http://192.168.100.1/
Accessing the Follow these steps to access the advanced troubleshooting pages.
Advanced Pages 1 Perform steps 1 and 2 of ‘‘Accessing the Standard Pages’’ above.
2 Obtain the Password of the Day from the PWoD tool. See ‘‘Using
the Password of the Day Tool’’ on page 431 for details about the
PWoD tool.
3 Start your web browser and access the E-UE, using the address
http://192.168.100.1/cgi-bin/product_cgi (replace the IP address
shown with the cable modem IP address if desired).
The E-UE displays a web form that prompts you for the password.
4 Enter the Password of the Day in the web form and press Enter.
The E-UE displays the Product Details Screen shown on page 447.
Note: If the Password of the Day does not allow you to access the advanced
pages, verify that the date shown below the password entry field matches the
date associated with the Password of the Day.
Troubleshooting SIP
Use the information in this procedure to troubleshoot issues with SIP eDVAs.
Internal eDVA The following list describes internal eDVA states when running SIP firmware
States loads.
• IDLE — Phone is on-hook, no calls are active. A loopback call could
be taking place.
• PREDIAL — Phone is off-hook and dial tone is being played.
• DIALING — Phone is off-hook and at least one digit was placed. The
digits dialed have not matched a complete digitmap entry.
• CALLING — Phone is off-hook and an INVITE has been sent to the
far end. Digits have already been collected.
• RINGING — Phone is on-hook and ringing because of an incoming
call.
• CONNECTED — Phone is off-hook. The far-end is connected.
• CONNECTED_ALERTING — Phone is off-hook and has an active
connection. An inbound call was just received.
• CALL_WAITING — Phone is off-hook and has one active leg and one
held leg.
• THREE_WAY_CALLING — Phone is off-hook and has one active leg
and one held leg. This is pre-conference.
• CONFERENCE — Phone is off-hook and connected with two parties.
Media is mixed at the pivot.
• CONFERENCE_BEFORE_ANSWER — Phone is off-hook and con-
nected with a single party. The other outbound call is outstanding and
has not been answered. Media is mixed and both parties hear ring-
back. Will automatically move to CONFERENCE when the outbound
call answers.
• STRANDED_CALL — Phone is on-hook but an active call exists.
The phone is ringing.
Enabling SIP Log- Enable log types 65, 66, 67, 68, and 69 when troubleshooting any SIP issue.
ging 1 Move to the second console:
Console> co ↵
6 To enable tracing of SIP state and input, use the following com-
mands:
Console> co ↵
mainMenu> logger ↵
Logger> ModuleConfig 6 26 1 ↵
Loopback Support Touchstone SIP loads support the following loopback types:
• Media loopback—loopback passes through the DSP on the mirroring
side. This is analogous to MGCP netwtest (network continuity test).
• Packet loopback—re-encapsulates RTP data in IP, UDP, and RTP
headers. This is analogous to MGCP netwloop (network loopback).
These loopback types are initiated from the Call Agent.
SIP loads also support remote initiated loopback. Using remote initiated
loopback, the eDVA starts either media loopback or packet loopback when
receiving a call from a phone number provisioned in the sipCfgMediaLoop-
backNumber or sipCfgPacketLoopbackNumber MIB objects.
When running loopback tests, the eDVA automatically goes off-hook without
ringing and performs the desired loopback test.
3 After saving the configuration file, restart the eDVA to make the
changes take effect.
4 To start a loopback test, call any line on the eDVA from the numbers
specified in the above MIB objects.
North American The following ring cadences may be provisioned using the PacketCable NCS
Ring Cadences Signaling MIB (see PKT-SP-MIB-SIG1.5-I01-050128). The following table
shows the default ring cadences for North America.
Name Description Default
L/RG Standard Ringing 2 seconds on, 4 seconds off
L/R0 Distinctive Ringing #0 2 seconds on, 4 seconds off
L/R1 Distinctive Ringing #1 2 seconds on, 4 seconds off
L/R2 Distinctive Ringing #2 800 ms on, 400 ms off,
800 ms on, 4 seconds off
L/R3 Distinctive Ringing #3 400 ms on, 200 ms off,
400 ms on, 200 ms off,
800 ms on, 4 seconds off
L/R4 Distinctive Ringing #4 300 ms on, 200 ms off,
1 second on, 200 ms off,
300 ms on, 4 seconds off
L/R5 Distinctive Ringing #5 500 ms on, 5.5 seconds off
(not repeated)
L/R6 Distinctive Ringing #6 2 seconds on, 4 seconds off
L/R7 Distinctive Ringing #7 2 seconds on, 4 seconds off
L/RS Ring Splash 500 ms on, 5.5 seconds off
(not repeated)
L/RT Ringback Tone 2 seconds on, 4 seconds off
Touchstone firmware uses the default ring cadences shown above when the
country template is provisioned to be one of the following:
• northAmerica57
• northAmerica33
• northAmerica09
• northAmerica66
Netherlands/ The following table shows the default ring cadences for all Netherlands tem-
Netherlands09 plates.
Ring Cadences Name Description Default
RG Standard Ringing 1000 ms on, 4000 ms off
R0 Distinctive Ringing #0 1.3 seconds on, 300 ms
off, 300 ms on, 3.1 sec-
onds off
R1 Distinctive Ringing #1 1.3 seconds on, 300 ms
off, 1.3 seconds on, 2.1
seconds off
R2 Distinctive Ringing #2 800 ms on, 400 ms off,
800 ms on, 4 seconds off
R3 Distinctive Ringing #3 400 ms on, 200 ms off,
400 ms on, 200 ms off,
800 ms on, 4 seconds off
R4 Distinctive Ringing #4 300 ms on, 200 ms off, 1
second on, 200 ms off, 300
ms on, 4 seconds off
R5 Distinctive Ringing #5 500 ms on, 5.5 seconds off
(not repeated)
R6 Distinctive Ringing #6 2 seconds on, 4 seconds off
R7 Distinctive Ringing #7 2 seconds on, 4 seconds off
RS Ring Splash 450 ms on (not repeated)
RT Ringback Tone 1 second on, 4 seconds off
Provisioning European standard ring cadence and ring splash may be provisioned through
European Ring the PKTC-IETF-MTA-MIB objects pktcSigDevRgCadence (standard ring),
Cadences pktcSigDevR0Cadence through pktcSigDevR7Cadence, and pktcSigDev-
RsCadence (ring splash). These objects consist of the following fields:
Austria Ring The following table shows the default ring cadences for Austria.
Cadences
Name Description Default
RG Standard Ringing 1000 ms on, 5000 ms off
R0 Distinctive Ringing #0 2000 ms on, 4000 ms off
R1 Distinctive Ringing #1 2000 ms on, 4000 ms off
R2 Distinctive Ringing #2 800 ms on, 400 ms off,
800 ms on, 4000 ms off
R3 Distinctive Ringing #3 400 ms on, 200 ms off,
400 ms on, 200 ms off,
800 ms on, 4000 ms off
R4 Distinctive Ringing #4 300 ms on, 200 ms off,
1000 ms on, 200 ms off,
300 ms on, 4000 ms off
R5 Distinctive Ringing #5 500 ms on, 5500 ms off
R6 Distinctive Ringing #6 2000 ms on, 4000 ms off
R7 Distinctive Ringing #7 2000 ms on, 4000 ms off
RS Ring Splash 450 ms on
RT Ringback Tone 1000 ms on, 5000 ms off
Australia Ring The following table shows the default ring cadences for Australia.
Cadences
Name Description Default
RG Standard Ringing 400 ms on, 200 ms off, 400 ms on,
2000 ms off
R0 Distinctive Ringing #0 2000 ms on, 4000 ms off
R1 Distinctive Ringing #1 2000 ms on, 4000 ms off
R2 Distinctive Ringing #2 800 ms on, 400 ms off, 800 ms on,
4000 ms off
R3 Distinctive Ringing #3 400 ms on, 200 ms off, 400 ms on,
200 ms off, 800 ms on, 4000 ms off
R4 Distinctive Ringing #4 300 ms on, 200 ms off, 1000 ms on,
200 ms off, 300 ms on, 4000 ms off
R5 Distinctive Ringing #5 500 ms on, 5500 ms off (not repeated)
R6 Distinctive Ringing #6 2000 ms on, 4000 ms off
R7 Distinctive Ringing #7 2000 ms on, 4000 ms off
RS Ring Splash 650 ms on (not repeated)
RT Ringback Tone 2000 ms on, 4000 ms off
Belgium Ring The following table shows the default ring cadences for Belgium.
Cadences
Name Description Default
RG Standard Ringing 1 second on, 3 seconds off
R0 Distinctive Ringing #0 1 second on, 300 ms off,
250 ms on, 2450 ms off
R1 Distinctive Ringing #1 1 second on, 300 ms off, 1
second on, 1700 ms off
R2 Distinctive Ringing #2 800 ms on, 400 ms off,
800 ms on, 4 seconds off
R3 Distinctive Ringing #3 400 ms on, 200 ms off,
400 ms on, 200 ms off,
800 ms on, 4 seconds off
R4 Distinctive Ringing #4 300 ms on, 200 ms off, 1
second on, 200 ms off, 300
ms on, 4 seconds off
R5 Distinctive Ringing #5 500 ms on, 5.5 seconds off
(not repeated)
R6 Distinctive Ringing #6 2 seconds on, 4 seconds off
R7 Distinctive Ringing #7 2 seconds on, 4 seconds off
RS Ring Splash 300 ms on (not repeated)
RT Ringback Tone 1 second on, 3 seconds off
France Ring The following table shows the default ring cadences for France.
Cadences
Name Description Default
RG Standard Ringing 1500 ms on, 3500 ms off
R0 Distinctive Ringing #0 1350 ms on, 300 ms off, 350
ms on, 3 seconds off (see note)
R1 Distinctive Ringing #1 1350 ms on, 300 ms off, 1350
ms on, 2 seconds off (see note)
R2 Distinctive Ringing #2 800 ms on, 400 ms off, 800 ms
on, 4 seconds off
R3 Distinctive Ringing #3 400 ms on, 200 ms off, 400 ms
on, 200 ms off, 800 ms on, 4
seconds off
R4 Distinctive Ringing #4 300 ms on, 200 ms off, 1 sec-
ond on, 200 ms off, 300 ms
on, 4 second off
R5 Distinctive Ringing #5 500 ms on, 5.5 seconds off
(not repeated)
R6 Distinctive Ringing #6 2 seconds on, 4 seconds off
R7 Distinctive Ringing #7 2 seconds on, 4 seconds off
RS Ring Splash 700 ms on (not repeated)
RT Ringback Tone 1.5 seconds on, 3.5 seconds off
Germany/Ger- The following table shows the default ring cadences for Germany and Ger-
many2 Ring many2.
Cadences Name Description Default
RG Standard Ringing 1000 ms on, 4000 ms off
R0 Distinctive Ringing #0 2 seconds on, 4 seconds off
R1 Distinctive Ringing #1 2 seconds on, 4 seconds off
R2 Distinctive Ringing #2 800 ms on, 400 ms off,
800 ms on, 4 seconds off
R3 Distinctive Ringing #3 400 ms on, 200 ms off,
400 ms on, 200 ms off,
800 ms on, 4 seconds off
R4 Distinctive Ringing #4 300 ms on, 200 ms off, 1
second on, 200 ms off, 300
ms on, 4 seconds off
R5 Distinctive Ringing #5 500 ms on, 5.5 seconds off
(not repeated)
R6 Distinctive Ringing #6 2 seconds on, 4 seconds off
R7 Distinctive Ringing #7 2 seconds on, 4 seconds off
RS Ring Splash 450 ms on (not repeated)
RT Ringback Tone 1 second on, 4 seconds off
Hungary Ring The following table shows the default ring cadences for Hungary.
Cadences
Name Description Default
RG Standard Ringing 1250 ms on, 3750 ms off
R0 Distinctive Ringing #0 2 seconds on, 4 seconds off
R1 Distinctive Ringing #1 2 seconds on, 4 seconds off
R2 Distinctive Ringing #2 800 ms on, 400 ms off, 800 ms
on, 4 seconds off
R3 Distinctive Ringing #3 400 ms on, 200 ms off, 400 ms
on, 200 ms off, 800 ms on, 4 sec-
onds off
R4 Distinctive Ringing #4 300 ms on, 200 ms off, 1 second
on, 200 ms off, 300 ms on, 4 sec-
onds off
R5 Distinctive Ringing #5 500 ms on, 5.5 seconds off
(not repeated)
R6 Distinctive Ringing #6 2 seconds on, 4 seconds off
R7 Distinctive Ringing #7 2 seconds on, 4 seconds off
RS Ring Splash 450 ms on (not repeated)
RT Ringback Tone 1.25 seconds on, 3.75 seconds off
Israel Ring The following table shows the default ring cadences for Israel.
Cadences
Signal Description Default
RG Standard Ringing 1s on, 4s off
R0 Distinctive Ringing #0 2s on, 4s off
R1 Distinctive Ringing #1 2s on, 4s off
R2 Distinctive Ringing #2 800ms on, 400ms off,
800ms on, 4000ms off
R3 Distinctive Ringing #3 400ms on, 200ms off,
400ms on, 200ms off,
800ms on, 4000ms off
R4 Distinctive Ringing #4 300ms on, 200ms off,
1000ms on, 200ms off,
300ms on, 4000ms off
R5 Distinctive Ringing #5 500ms on, 5500ms off
R6 Distinctive Ringing #6 2s on, 4s off
R7 Distinctive Ringing #7 2s on, 4s off
RS Call Forward Ring Splash 650ms on (not repeated)
DR Delayed Ringing 1s on, 4s off
SR Special Ringing 1.65s on, 3.35s off
PR Precedence Ringing 0.3s on, 0.35s off, 0.65s
on, 0.3s off, 0.3s on, 0.35s
off, 0.65s on, 2s off
CR Continuous Ringing 6s on, 4s off
CAR CPE Activation Ring Splash 650ms on
TR1 Teen Ring 1s on, 0.65s off, 1s on,
2.35s off
Japan Ring The following table shows the default ring cadences for Japan.
Cadences
Name Description Default
RG Standard Ringing 1 second on, 2 seconds off
R0 Distinctive Ringing #0 1 second on, 2 seconds off
R1 Distinctive Ringing #1 800 ms on, 400 ms off,
800 ms on, 4 seconds off
R2 Distinctive Ringing #2 300 ms on, 300 ms off,
300 ms on, 2100 ms off
R3 Distinctive Ringing #3 300 ms on, 200 ms off, 1
second on, 200 ms off,
300 ms on, 4 seconds off
R4 Distinctive Ringing #4 500 ms on, 5.5 seconds off
R5 Distinctive Ringing #5 500 ms on, 5.5 seconds off
R6 Distinctive Ringing #6 1 second on, 2 seconds off
R7 Distinctive Ringing #7 1 second on, 2 seconds off
RS Ring Splash 500 ms on (not repeated)
RT Ringback Tone 1 second on, 4 seconds off
Mexico Ring The following table shows the default ring cadences for Mexico.
Cadences
Name Description Default
RG Standard Ringing 1 sec on, 4 sec off
R0 Distinctive Ringing #0 1300 ms on, 300 ms off,
300 ms on, 3100 ms off
R1 Distinctive Ringing #1 500 ms on, 250 ms off,
1000 ms on, 250 ms off,
500 ms on, 3500 ms off
R2 Distinctive Ringing #2 800 ms on, 400 ms off,
800 ms on, 4000 ms off
R3 Distinctive Ringing #3 400 ms on, 200 ms off,
400 ms on, 200 ms off,
800 ms on, 4000 ms off
R4 Distinctive Ringing #4 300 ms on, 200 ms off,
1000 ms on, 200 ms off,
300 ms on, 4000 ms off
R5 Distinctive Ringing #5 500 ms on, 5500 ms off
R6 Distinctive Ringing #6 2000 ms on, 4000 ms off
R7 Distinctive Ringing #7 2000 ms on, 4000 ms off
RS Ring Splash 250 ms on
RT Ringback Tone 1000 ms on, 4000 ms off
MexicoC Ring The following table shows the default ring cadences for MexicoC.
Cadences
Name Description Default
RG Standard Ringing 1 sec on, 4 sec off
R0 Distinctive Ringing #0 1000 ms on, 500 ms off,
1000 ms on, 3500 ms off
R1 Distinctive Ringing #1 500ms on, 500 ms off,
500 ms on, 500 ms off,
1000 ms on, 3000 ms off
R2 Distinctive Ringing #2 500 ms on, 500 ms off,
1000 ms on, 500 ms off,
500 ms on, 3000 ms off
R3 Distinctive Ringing #3 400 ms on, 200 ms off,
400 ms on, 200 ms off,
800 ms on, 4000 ms off
R4 Distinctive Ringing #4 300 ms on, 200 ms off,
1000 ms on, 200 ms off,
300 ms on, 4000 ms off
R5 Distinctive Ringing #5 500 ms on, 5500 ms off
R6 Distinctive Ringing #6 2000 ms on, 4000 ms off
R7 Distinctive Ringing #7 2000 ms on, 4000 ms off
RS Ring Splash 250 ms on
RT Ringback Tone 1000 ms on, 4000 ms off
Netherlands/ The following table shows the default ring cadences for all Netherlands tem-
Netherlands09 plates.
Ring Cadences Name Description Default
RG Standard Ringing 1000 ms on, 4000 ms off
R0 Distinctive Ringing #0 1.3 seconds on, 300 ms
off, 300 ms on, 3.1 sec-
onds off
R1 Distinctive Ringing #1 1.3 seconds on, 300 ms
off, 1.3 seconds on, 2.1
seconds off
R2 Distinctive Ringing #2 800 ms on, 400 ms off,
800 ms on, 4 seconds off
R3 Distinctive Ringing #3 400 ms on, 200 ms off,
400 ms on, 200 ms off,
800 ms on, 4 seconds off
R4 Distinctive Ringing #4 300 ms on, 200 ms off, 1
second on, 200 ms off, 300
ms on, 4 seconds off
R5 Distinctive Ringing #5 500 ms on, 5.5 seconds off
(not repeated)
R6 Distinctive Ringing #6 2 seconds on, 4 seconds off
R7 Distinctive Ringing #7 2 seconds on, 4 seconds off
RS Ring Splash 450 ms on (not repeated)
RT Ringback Tone 1 second on, 4 seconds off
Norway Ring The following table shows the default ring cadences for Norway.
Cadences
Name Description Default
RG Standard Ringing 1000 ms on, 4000 ms off
R0 Distinctive Ringing #0 1000 ms on, 4000 ms off
R1 Distinctive Ringing #1 1000 ms on, 4000 ms off
R2 Distinctive Ringing #2 800 ms on, 400 ms off,
800 ms on, 4000 ms off
R3 Distinctive Ringing #3 1000 ms on, 2000 ms off
R4 Distinctive Ringing #4 800 ms on, 200 ms off,
200 ms on, 200 ms off,
400 ms on, 1400 ms off
R5 Distinctive Ringing #5 200 ms on, 200 ms off,
400 ms on, 200 ms off,
200 ms on, 200 ms off,
400 ms on, 1400 ms off
R6 Distinctive Ringing #6 1000 ms on, 4000 ms off
R7 Distinctive Ringing #7 1000 ms on, 4000 ms off
RS Ring Splash 450 ms on
RT Ringback Tone 1000 ms on, 4000 ms off
Panama Ring The following table shows the default ring cadences for Panama.
Cadences
Name Description Default
RG Standard Ringing 1000 ms on, 4000 ms off
R0 Distinctive Ringing #0 1300 ms on, 300 ms off,
300 ms on, 3100 ms off
R1 Distinctive Ringing #1 1300 ms on, 300 ms off,
1300 ms on, 2100 ms off
R2 Distinctive Ringing #2 800 ms on, 400 ms off,
800 ms on, 4000 ms off
R3 Distinctive Ringing #3 400 ms on, 200 ms off,
400 ms on, 200 ms off,
800 ms on, 4000 ms off
R4 Distinctive Ringing #4 300 ms on, 200 ms off,
1000 ms on, 200 ms off,
300 ms on, 4000 ms off
R5 Distinctive Ringing #5 500 ms on, 5500 ms off
R6 Distinctive Ringing #6 2000 ms on, 4000 ms off
R7 Distinctive Ringing #7 2000 ms on, 4000 ms off
RS Ring Splash 650 ms on
RT Ringback Tone 1200 ms on, 4650 ms off
Poland/ The following table shows the default ring cadences for Poland and Slovakia.
Poland1010/Slo-
Name Description Default
vakia Ring
Cadences RG Standard Ringing 1 second on, 4 seconds off
R0 Distinctive Ringing #0 2 seconds on, 4 seconds off
R1 Distinctive Ringing #1 2 seconds on, 4 seconds off
R2 Distinctive Ringing #2 800 ms on, 400 ms off,
800 ms on, 4 seconds off
R3 Distinctive Ringing #3 400 ms on, 200 ms off,
400 ms on, 200 ms off,
800 ms on, 4 seconds off
R4 Distinctive Ringing #4 300 ms on, 200 ms off, 1
second on, 200 ms off, 300
ms on, 4 seconds off
R5 Distinctive Ringing #5 500 ms on, 5.5 seconds off
(not repeated)
R6 Distinctive Ringing #6 2 seconds on, 4 seconds off
R7 Distinctive Ringing #7 2 seconds on, 4 seconds off
RS Ring Splash 450 ms on (not repeated)
RT Ringback Tone 1 second on, 4 seconds off
Switzerland Ring The following table shows the default ring cadences for Switzerland.
Cadences
Name Description Default
L/RG Standard Ringing 1 seconds on, 4 seconds off
L/R0 Distinctive Ringing #0 2 seconds on, 4 seconds off
L/R1 Distinctive Ringing #1 2 seconds on, 4 seconds off
L/R2 Distinctive Ringing #2 800 ms on, 400 ms off,
800 ms on, 4 seconds off
L/R3 Distinctive Ringing #3 400 ms on, 200 ms off,
400 ms on, 200 ms off,
800 ms on, 4 seconds off
L/R4 Distinctive Ringing #4 300 ms on, 200 ms off, 1
second on, 200 ms off, 300
ms on, 4 seconds off
L/R5 Distinctive Ringing #5 500 ms on, 5.5 seconds off
(not repeated)
L/R6 Distinctive Ringing #6 2 seconds on, 4 seconds off
L/R7 Distinctive Ringing #7 2 seconds on, 4 seconds off
L/RS Ring Splash 450 ms on
Customizing Any of the above ring cadences may be customized in the eDVA configura-
Default Ring tion file. All MIB objects are eDVA based; therefore, the first cadence is
Cadences index 0.
The ring cadence is internally represented as a 64-bit string and provisioned
in hex format. The ring cadence representation starts with the first 1 in the
bit string pattern. Leading zeros are ignored, thus shortening the overall ring
cadence duration. Each bit represents 100 ms of ringing (or tone in the case
of L/RT); 1 is ring on, 0 is ring off.
All 64 bits must be provisioned. The least significant 4 bits are used for rep-
resenting repeatable characteristics: 0000 indicates that the ring cadence
repeats, and 1000 indicates a non-repeatable ring cadence. Therefore, only
the first 60 bits are used to represent the actual ring cadence for a maximum
duration of 6 seconds.
As mentioned earlier, shorter ring cadences may be provisioned by padding
the ring cadence with leading zeros. For example, a ring cadence of 0.5 sec-
onds on, 4 seconds off, repeatable, has a value of 0x0001F00000000000 and
would be provisioned in the eDVA configuration file as
00.01.F0.00.00.00.00.00.
The following tables show default tones for supported country templates.
The columns in each table are as follows:
type
The type of tone (busy, dial tone).
level
The tone level, in dB.
Freq. Type
Either 1 (first frequency modified by the second) or 2 (summation).
# Freq.
The number of frequencies used to generate the tone (1–4).
Frequencies
The frequencies used to generate the tone.
# on/off
The number of on/off cycles in the tone pattern (1–4).
1st tone – 4th tone
The duration, in milliseconds, of the on/off segments of each tone
cycle.
rep. count
The number of times the tone pattern is repeated.
tone steady
Which of the four tones, if any, are held indefinitely after the pat-
tern completes (used, for example, with stutter dial).
The server responds with an XML configuration file. The file provides con-
figuration information only for the router component of the Touchstone Gate-
way.
Note: If the returned URL is invalid in any way (for example, the site cannot
be reached or the specified file does not exist), the Gateway uses the last valid
configuration file it received. If the Gateway has no valid configuration, it
uses default settings.
<deviceConfig version="1.0">
<ethernet enabled="true">
<ip ipVersion="4">
<address>192.168.0.1</address>
<netmask>255.255.255.0</netmask>
</ip>
<dhcpServer enabled="true">
<addressRange ipVersion="4">
<start>192.168.0.10</start>
<end>192.168.0.70</end>
</addressRange>
</dhcpServer>
</ethernet>
<moca enabled="false">
</moca>
<wirelessConfig enabled="true">
<region>USA</region>
<txPower>75</txPower>
<channelSelection mode="auto"></channelSelection>
<maxDataRate>auto</maxDataRate>
<beaconInterval>2500</beaconInterval>
<fiftyFourGProtection>true</fiftyFourGProtection>
</radius>
</wpaEnterprise>
</ssid>
</wirelessConfig>
<gateway>
<ssh enabled="true">
<username>noc</username>
<password>noc@11+gty</password>
</ssh>
<timezone>US/Eastern</timezone>
<ntp>ntp1.example.com</ntp>
<ntp>ntp2.example.com</ntp>
<ntp>0.pool.ntp.org</ntp>
<nat>
<ipsecPassthru>true</ipsecPassthru>
<pptpPassthru>false</pptpPassthru>
<multicastPassthru>true</multicastPassthru>
<tcpSesWaitTimeout>300</tcpSesWaitTimeout>
<udpSesWaitTimeout>60</udpSesWaitTimeout>
<icmpSesWaitTimeout>30</icmpSesWaitTimeout>
</nat>
<firewall enabled="true">
<proxy>true</proxy>
<javaApp>true</javaApp>
<activeX>false</activeX>
<popUp>true</popUp>
<blockFragPackets>true</blockFragPackets>
<portScan>true</portScan>
<ipFloodDetect>true</ipFloodDetect>
</firewall>
<mediaServer enabled="false"></mediaServer>
</gateway>
When you enter the command-line interface (see ‘‘Enabling and Accessing
the Troubleshooting CLI’’ on page 435 for instructions), you receive a pass-
word prompt. Enter the Password of the Day to continue to the console
prompt:
Arris console is active
Command interface Copyright 2008, ARRIS Group, Inc.,
All rights reserved
Type ’help’ for available commands
[ 1] Console>
The following commands are common to all menus in the initial CLI.
Return Status: 0
Top-level Commands
The following commands are available from the initial console prompt:
tech Enters the Technician menu. See ‘‘Technician Commands’’ on page 508.
system Enters the System menu. See ‘‘System Menu’’ on page 502.
led Enters the LED menu. See ‘‘LED Menu’’ on page 506.
dhcp Enters the DHCP menu. See ‘‘DHCP Menu’’ on page 507.
tlm Enters the Telemetry menu. See ‘‘Telemetry Menu’’ on page 512.
database Enters the Database menu. See ‘‘Database Menu’’ on page 515.
co Enters the second console. See ‘‘MAIN Console Commands’’ on page 553.
voice Enters the eDVA console. See ‘‘Voice CLI Commands’’ on page 619.
speedtest Enters the Speedtest menu. See ‘‘Speedtest CLI’’ on page 547.
System Menu
Return Status: 0
lastreset Displays the ‘‘last reset reason’’ log, stored in non-volatile memory.
Example:
Return Status: 0
Return Status: 0
intrusive
Set to 0 to avoid intrusive actions, or 1 to allow intrusive actions.
intrusive
Set to 0 to avoid intrusive actions, or 1 to allow intrusive actions.
LED Menu
The LED menu commands allow manual control of the front panel LEDs for
testing.
all_on Turns on all the LEDs; the US, DS, and Link LEDs on TM722, WBM760,
and all Model 8 models are red.
all_on_green Turns on all the LEDs; the US, DS, and Link LEDs on TM722, WBM760,
and all Model 8 models are green.
DHCP Menu
Technician Commands
setWanIp dynamic
setWanDNS auto
Sets the IP address of the primary and (optional) secondary DNS servers, for
networks that do not provide this information using DHCP.
Specify the auto keyword to use DNS information provided by DHCP.
Telemetry Menu
chgrStatus Shows the status of the Model 5 or Model 6 battery charger. Not supported
in multi-line Telephony Modems.
Example:
[ 5] TLM> chgr
Failure Status: No Failures
Return Status: 1
tlmStatus Displays general battery telemetry status and active alarms, if any.
Example:
[ 7] TLM> tlmStatus
tlmStatus
-- Battery 1 --
BatteryStatus = BATTERY REPLACE
BatterySubStatus=
HexUpsValue = 0xd0
testInProgress = 0
testIsPending = 0
Active Battery Level Alarms: None
value
(optional) The value to write to the selected MIB object.
eprom Verifies the battery EPROM checksums (if a battery is installed) and displays
battery manufacturing data.
Example:
[ 6] TLM> eprom
eprom
EPROM Data Revision: A
PCB Assy Part Number: 00884
PCB Assembly Revision: C
PCB Assembly Test Code: ee
Cell Manufacturer: MI
Cell Manufacturer Factory Location: 1
Cell Lot: 018603
Cell Capacity: 6.6 ah
Pack Serial Number: 08065000715
PCB Assembly Test Code: ee
Return Status: 1
Database Menu
DB Contents:
Num Lines - 2
LC Type - 4
Ethernet - 1
USB - 1
Router - 0
Telemetry - 1
Tuner HW - 0
Market - 0 (NA)
MultiColor LEDs - 0
Ethernet HW - 0
Model Number - 0
NA Dual Mode - 0
HW Model - TM802G
HW Info - ARRIS DOCSIS 3.0 / PacketCable 1.5
Touchstone Telephony Modem
Image Name - TS07010X_091609_ARRIS_TM
HTTP PW Check - 1
HTTP Timeout - 0
CLI PID - 0
PTY PID - 20635
PTY interface - wan0
PTY owner - 1
Telnet/SSH timeout - 1440
App Mode Enabled - 1
Packet Processor Enabled - 1
MultiColor LED Bitmap - 0
Secondary DS Reinit - 0
Partial Service Fallback 2.0 - 0
PartServ Fallback 2.0 Active - 0
FLASH Manufacturer - SPANSION
Config File MIB Bitmap - 0x0
MAC and IP/FQDN event hiding flag - 0
Return Status: 0
RF Menu
Return Status: 0
Return Status: 0
Return Status: 0
Tuner 1:
-------------------------------------
Enabled: 1
Center freq: 0 Hz
Bandwidth: 96000000 Hz
Receivers [4]: 1 2 3 4
Tuner 2:
-------------------------------------
Enabled: 0
Center freq: 0 Hz
Bandwidth: 96000000 Hz
Receivers [4]: 5 6 7 8
Return Status: 0
Example:
[ 42] RF> dump 0
PHY Global Registers:
[C0] 0000
[C1] 0000 [C2] 0006 [C3] 0000 [C4] 0000
[C5] 0000 [C6] 0000 [C7] 0000 [C8] 0000
[C9] 01D0 [CA] 0003 [CB] 2115 [CC] 2121
[CD] 00FF [CE] 0000 [CF] 0000 [D0] 0004
[D1] 0000 [D2] 0000 [D3] 0000 [D4] 0000
[D5] 0000 [D6] 0000 [D7] 0000 [D8] 0000
[D9] 0000 [DA] 0000 [DB] 0000 [DC] 1004
[DD] 0000 [DE] 0000 [DF] 0000
Return Status: 0
Return Status: 0
US frequency db in NVRAM:
Return Status: 0
QAM Lock NO
FEC Sync NO
MPEG Sync NO
Return Status: 0
Time CER CORR_CER CORR UNCORR RECVD MER IF_AGC RF_AGC RF_Level
Return Status: 0
Table refChannel:
Pin - 1.013340
frIN - 541.866638
gcATTN - 200.000000
gcRL - 50.000000
frSAW - 1247.000000
gcDNC - 127.000000
frADC - 74.000000
bo_Ref - 20.009022
ifVGA - 0.000000
ifReg - 362.000000
Det - 34.994617
Table capTrimAvrg:
Pin - 1.013340
frIN - 541.866638
gcATTN - 200.000000
gcRL - 50.000000
frSAW - 1247.000000
gcDNC - 127.000000
frADC - 74.000000
bo_Ref - 20.009022
ifVGA - 0.000000
ifReg - 362.000000
Det - 34.994617
CapTrimAvg
127.849998
Table ifVga:
Pin - 1.013340
frIN - 541.866638
gcATTN - 200.000000
gcRL - 50.000000
frSAW - 1247.000000
gcDNC - 127.000000
frADC - 74.000000
bo_Ref - 20.009022
ifVGA - 0.000000
ifReg - 362.000000
Det - 34.994617
Table gcDnc:
Pin - 1.013340
frIN - 541.866638
gcATTN - 200.000000
gcRL - 50.000000
frSAW - 1247.000000
gcDNC - 127.000000
frADC - 74.000000
bo_Ref - 20.009022
ifVGA - 0.000000
ifReg - 362.000000
Det - 34.994617
Table aaf:
Pin - 1.013340
frIN - 541.866638
gcATTN - 200.000000
gcRL - 50.000000
frSAW - 1247.000000
gcDNC - 127.000000
frADC - 74.000000
bo_Ref - 20.009022
ifVGA - 0.000000
ifReg - 362.000000
Det - 34.994617
Table clearTune:
Pin - 1.013340
frIN - 541.866638
gcATTN - 200.000000
gcRL - 50.000000
frSAW - 1247.000000
gcDNC - 127.000000
frADC - 74.000000
bo_Ref - 20.009022
ifVGA - 0.000000
ifReg - 362.000000
Det - 34.994617
Table gcAttn:
Pin - 1.013340
frIN - 541.866638
gcATTN - 200.000000
gcRL - 50.000000
frSAW - 1247.000000
gcDNC - 127.000000
frADC - 74.000000
bo_Ref - 20.009022
ifVGA - 0.000000
ifReg - 362.000000
Det - 34.994617
Table gcRl:
Pin - 1.013340
frIN - 541.866638
gcATTN - 200.000000
gcRL - 50.000000
frSAW - 1247.000000
gcDNC - 127.000000
frADC - 74.000000
bo_Ref - 20.009022
ifVGA - 0.000000
ifReg - 362.000000
Det - 34.994617
Table saw:
Pin - 1.013340
frIN - 541.866638
gcATTN - 200.000000
gcRL - 50.000000
frSAW - 1247.000000
gcDNC - 127.000000
frADC - 74.000000
bo_Ref - 20.009022
ifVGA - 0.000000
ifReg - 362.000000
Det - 34.994617
Return Status: 0
Gateway Commands
commit Commits new settings to the WRM. This command must be used to update
the WRM with changes to the provisioned values. Use this command after
one or more set, create, or delete commands. Multiple commands can be
followed by a single commit.
Note: Using this command restarts the WRM.
!defaults Resets the WRM to factory defaults. This discards all user provisioning.
XML CONFIGURATION:
Status = (5)fileNotFound
Url Path = tftp://10.1.50.69/cm0015d13aa54a/loc_mib_format_sample2.x
Req CMD = ’/gw/usr/sbin/tftp
File Size = 0
DNS Servers(s)...
nameserver 10.1.50.69
Return Status: 0
Valid Variables This section defines the variables that are configurable using the Gateway
CLI commands.
WAN Variables
LAN Variables
The following variables apply to the general LAN (wireless and Ethernet)
interfaces.
ID Purpose Type Range / Example Default
lanIndex Index of LAN Numeric 0
Wireless Settings
The following variables apply to the wireless interface. The array identifier
[n] specifies the SSID (valid range: 0 to 3, where 0 is the subscriber’s SSID).
ID Purpose Type Range / Example Default
0: Auto
1: Africa
2: Asia
3: Australia
4: Canada
5: Europe
wifiRadioChannel Wireless channel ID Numeric 0
6: France
7: Israel
8: Japan
9: Mexico
10: South America
11: USA
0: B/G mixed
1: B Only
wifiHwmode Wireless mode Numeric 4: G Only 9
6: N Only
9: B/G/N mixed
0: Auto
wifiBGProtected Bgprotected mode Boolean 1: On 0
2: Off
wifiBeaconInterval Beacon interval Numeric 20–1024 100
wifiDtimInterval Dtim interval Numeric 1–255 1
0: Long
wifiTxPreamble Tx Preamble Numeric 0: Long
1: Short
wifiRTSThreshold RTS Threshold Numeric 1–2347 2347
wifiFragment Fragment Threshold Numeric 256–2346 2346
0: Disable
wifiShortSlot Short Slot Boolean 1
1: Enable
0: Disable
wifiBurst Frame Burst Boolean 1
1: Enable
0: Mixed
wifiOpMode HT Operation Mode Numeric 0
1: Greenfield
0: 20 MHz
wifiBandwidth Channel Bandwidth Numeric 0
1: 20/40 MHz
0: 400 ns
wifiGuard Guard Interval Numeric 0
1: 800 ns
Firewall Variables
fwVirtualServerStart
Beginning inbound port no. Numeric 1–65535 N/A
InPort[n]
fwVirtualServerEnd
Ending inbound port no. Numeric 1–65535 N/A
InPort[n]
1: TCP
fwVirtualServerProto[n] Protocol type Numeric 2: UDP N/A
3: BOTH
fwVirtualServerIp4[n] Private IP address IP addr xxx.xxx.xxx.xxx N/A
fwVirtualServerStart
Beginning private port no. Numeric 1–65535 N/A
PrivatePort[n]
fwVirtualServerEnd
Ending private port no. Numeric 1–65535 N/A
PrivatePort[n]
fwAclIndex[n] Index of ACL rule Numeric 0–29 0
Beginning IP address of
fwAclStartIp4[n] IP addr xxx.xxx.xxx.xxx N/A
a specific LAN client
Ending IP address of
fwAclEndtIp4[n] IP addr xxx.xxx.xxx.xxx N/A
a specific LAN client
Destination beginning port no.
fwAclStartPort[n] Numeric 1–65535 N/A
of a specific LAN client
Destination ending port no.
fwAclEndPort[n] Numeric 1–65535 N/A
of a specific LAN client
1: TCP
fwAclProto[n] Protocol type Numeric 2: UDP N/A
3: BOTH
1: All
fwAclBlocktime[n] Block time Numeric N/A
2: Pick
Beginning day of the 0: SUN
1: MON
2: TUE
fwAclStartDay[n] Numeric 3: WED 0
blocking schedule
4: THU
5: FRI
6: SAT
Ending day of the 0: SUN
1: MON
2: TUE
fwAclEndDay[n] Numeric 3: WED 0
blocking schedule
4: THU
5: FRI
6: SAT
Beginning time of the
fwAclStartTime[n] Numeric 0–24: o’clock 0
blocking schedule
Ending time of the
fwAclEndTime[n] Numeric 0–24: o’clock 0
blocking schedule
Speedtest CLI
General Information
Every command has two forms: full and short abbreviation (for example, typ-
ing tu is equivalent to typing the full command tuner). The console com-
mands are organized into a number of groups that differ in functionality.
Each group is called a submenu.
In a ‘‘help’’ display, submenus have a > (more) symbol following their name.
To navigate through the submenus, type the submenu name (without the ‘‘>’’
symbol) to enter the submenu. Type exit to return to the main menu. Type
exit at the main menu prompt to return to the Console commands.
Note that several submenus are not documented. For Voice submenu com-
mands, see ‘‘Voice CLI Commands’’ on page 619.
mainMenu> help
Console Commands for this level:
system - Go to system Menu.
docsis - Go to DOCSIS Menu.
pacm - Go to PACM Menu.
voice - Go to Voice Menu.
logger - Go to Logger Menu.
Common Commands
exit Exits the current sub-menu and return to the previous menu.
pp Enters the Packet Processor submenu. The following commands are avail-
able in this submenu.
enable
disable
deinit
setTimeout
resetTimeout
resetStats
dbg
nodbg
global
stats
pids
vpids
session
devs
brief
Displays global Packet Processor statistics, VPID counters, and a list of ses-
sions.
psm
nopsm
qos
noqos
setThreshold
thresholdDisable
sme Enters the State Machine Engine submenu. The following commands are
available in this submenu.
list
lshort
DSM_st_MddConnected
sme>
llong
SetModule
SetSeverity
version Prints the version of DOCSIS code running in the Telephony Modem. Note
that this version does not correspond to the supported DOCSIS version.
Example:
docsis> version
DOCSIS VERSION=1.1.1.140
docsis>
Show Enters the Show submenu. The following commands are available.
cpe
CPEs List
--------------------
Max CPEs 4
--------------------
Mac Name Learning Source Cpe Num
--- ---- -------- ------ -------
-> 00:15:cf:00:1d:3c esafe0 Static mta0 1
Show>
timeoverversion
Displays the date and time the firmware image was created.
cmstatusmasks
CM-STATUS masks:
===============:
Global mask (level-1) based on MDD TLV-11:
0x0000
Show>
Certification Enters the Certification submenu. The following commands are available.
status
accesstime
resetaccesstime
Syntax: resetaccesstime
Resets Access start times for CoSigner and Manufacturing certificates.
cmcert
mfgcert
rootpublickey
General Enters the General submenu. The following commands are available.
ucd
ipcable
goto
tune
next
rem
macaddr
hwcounters
Atp Enters the Atp submenu. The following commands are available.
addcpe
triggercmstatus
channel
The channel ID to check when generating the report.
suspendcmstatus
printcmstatusevents
overdsidholdoffovr
deldsidholdoff
version
mapperStats
Fw> mapperStats
MAPPER statistics:
==================
Legend:
State 0 = Disabled Mode: Map Processor is filtering all IE’s
State 1 = Ranging mode0: MAP processor processes only initial ranging (IUC 3)
State 2 = Normal mode: MAP processor processes all IUCs except IUC 3
State 3 = Ranging mode1: MAP processor processes only initial ranging (IUC 3)
Broadcast and Unicast transmit opportunities (IUC4)
isrStats
ISR statistics:
===============
preProcessing: 157
bestEffort: 153
ugsPackets: 0
managementPackets: 0
mapperFIFO: 525292
mapperUCD: 0
mapperMapLost: 0
mbxStats
Example:
Fw> mbxStats
Mailbox statistics:
===================
commands: 847
events: 84
illegalCommands: 0
illegalParams: 0
errStats
Error statistics:
=================
invalidSF: 0
invalidPHS: 0
shortGuardTime: 0
invalidIEs: 0
droppedPduPktsCounter: 0
droppedMgmtPktsCounter: 0
swQueueFull: 0
MbxIllegalCommands: 0
MbxIllegalParams: 0
sfStats
Displays statistics for the specified Service Flow. Valid range: 0 to 31.
Example:
Fw> sfStats 1
SF 1 statistics:
=================
totalPduPackets: 29
policedPduPackets: 0
outOfMemoryDropPackets: 0
expiredPackets: 0
mgmtPackets: 0
requestedPackets: 29
------------------------------
requestRetries: 0
requestExceeds: 0
totalPduBytes: 2776
requestedBytes: 3124
concat/segment Packets: 0
fragPackets: 0
dataPDUslots: 266
Legend:
totalPduPackets = number of PDUs packets forwarded to this Service
Flow, excluding policed dropped packets
policedPduPackets = number of packets dropped due to rate-limit/UGS
packet larger than unsolicitedGrantSizeBytes
outOfMemoryDropPackets = number of packets dropped due to lack of FW
resources
expiredPackets = number of packets dropped due to request retries
expiration
mgmtPackets = number of management packets forwarded to this
Service Flow
requestedPackets = number of packets requested to be transmitted
for this service flow
pduBytes = number of PDU octets forwarded in accordance to
pduPackets
requestedBytes = number of bytes requested to be transmitted for
this service flow
dataPDUslots = number of upstream mini-slots which have been
used to transmit data PDUs as a result of a unicast Data Grant
guardTimeStats
Fw> guardTimeStats
Legend:
maxGrantLatency = maximum time between FW reception of grant and
grant in FIFO
maxTxProcessingTime = maximum time between TX push and FW reception of
grant
minTimeTillTx = minimum time between TX push and actual TX time
(negative means need to increase guard time)
rtosStats
RTOS statistics:
================
heartBeat_IDLE: 3544838331
heartBeat_MBX: 1037
heartBeat_PreProc: 453
heartBeat_TxScheduler: 1896615
clusterSidTable
iucEnList
Fw> iucEnList
Enabled IUC’s:
==============
Channel 0 - 1 2 3 4 5 6 7
Channel 1 - disabled
Channel 2 - disabled
Channel 3 - disabled
backoffCounters
Backoff Counters:
=================
0 1 2 3 4 5 6 7
- - - - - - - -
count 0x3ffff 0x3ffff 0x3ffff 0x3ffff 0x3ffff 0x3ffff 0x3ffff 0x3ffff
bond 0x1 0x1 0x0 0x0 0x0 0x0 0x0 0x1
cppiStats
printAll
• guardTimeStats
• rtosStats
• clusterSidTable
• iucEnList
• backoffCounters
• cppiStats
gQosDbFwPrivateArray
SF 0 Private Array:
====================
state: DB_QOS_SF_ACTIVE
activeClusterIndex: 0
lastClusterIndex: 0
reqMultShift: 0
rxQueueHighId: 12
rxQueueHighAddr: 0x10600c0
rxQueueHighInfoAddr: 0x10640c0
rxQueueLowId: 13
rxQueueLowAddr: 0x10600d0
rxQueueLowInfoAddr: 0x10640d0
swDescQueue_NumOfPacketsInQueue: 1
swDescQueue_TotalBytesInQueue: 84
swDescQueue_Head: 0x402a88
swDescQueue_Tail: 0x402a88
headerSize: 12
mngHeaderSize: 10
boDataStart[0..1..2..3]: 2..0..0..0
boDataEnd [0..1..2..3]: 8..0..0..0
boRngStart: 0
boRngEnd: 0
bondingBitMap: 0x1
segmentSeqNum: 0
fragmentSeqNum: 0
isBackoffRunning: 0
rateLimit_tokensBits: 4294708552
rateLimit_remainderBits: 0
rateLimit_dividor: 1
rateLimit_prevReqTimestamp: 0x0
ugsPrms_qiFlag: 0
ugsPrms_NoActivityCounter: 0
ugsPrms_LastActiveGrantsValue: 0
ugsPrms_LastActiveGrantsCounter: 0
gQosDbHostConfigArray
gQosDbClusterArray
gQosDbPhsInfo
gUsChannelPrivateInfo
gUsChannelConfigInfo
gUpstreamBpiInfo
gUgsMaxQueueDepth
dsCounters
dsPdsp1Configuration
dsPdsp2Configuration
dsBpi
dsPhs
dsUnicast
tdoxStats
Qos Enters the Qos menu. The following submenus are available:
database
Enters the QOS database menu. The following commands are available:
Command Description
sid_cluster Displays all of the CM’s assigned SID clusters.
sf Displays all CM Service Flow parameters.
classifiers Displays all CM downstream and upstream classifiers.
phs Displays CM PHS parameters.
dsxstatistics Displays dynamic services transaction statistics.
servstatistics sfid Displays statistics for the specified Service Flow.
trafficflows Displays service flows carrying voice traffic.
cos Displays DOCSIS1.0 CoS parameters.
debug
Enters the QOS debug menu. The following commands are available:
Command Description
printsf index Displays short Service Flow internal data-
base info for the specified Service Flow
database index.
printcl index Displays internal classifier database info
for the specified classifier database index.
printfullsf index Displays full Service Flow internal data-
base info for the specified Service Flow
database index.
printactsf Displays full active upstream Service Flow
internal database info for the specified Ser-
vice Flow database index.
printactphs Displays full active PHS internal database
info for the specified PHS database index.
printta Displays DSX transaction database info.
printmsg index Displays DSX TA REQ/RSP/ACK message
buffers for the specified TA index.
Command Description
printusprimarysf Displays the upstream primary service flow.
senddsxevent index event Sends the specified DSX TA event.
sendeventlog type state code Sends the event log. The parameters are:
type
0: DSA
1: DSC
2: DSD
state
1: REQ
2: RSP
code
The confirmation code.
atp
Enters the ATP debug menu. The following commands are available:
Command Description
dsa100a grant us ds Initiates DSA with 1 or 2 Service Flows.
The parameters are:
grant
The grant size: 100 or 200.
us
The upstream port type:
0: UDP
1: TCP
ds
The downstream port type:
0: UDP
1: TCP
Command Description
dsc200a usf grant dsf dscls ds Initiates DSA with 1 or 2 Service Flows.
The parameters are:
usf
The upstream Service Flow ID.
grant
The grant size: 100 or 200.
dsf
The downstream Service Flow ID.
dscls
The downstream Classifier.
ds
The downstream port type:
0: UDP
1: TCP
dsa100_abc grant us1 us2 us3 Initiates DSA with 1 upstream Service
Flow. The parameters are:
grant
The grant size: 100 or 200.
us1
The first upstream port type:
0: UDP
1: TCP
us2
The second upstream port type:
0: UDP
1: TCP
us3
The third upstream port type:
0: UDP
1: TCP
dsa300a ipaddr port Initiates DSA with one UGS Service
Flow, two Classifiers, and one PHS.
The parameters are:
ipaddr
The upstream destination IP
address.
port
The upstream port.
Command Description
dsc300a sfid clsid phsid Initiates DSC to activate PHS of the
USF-300a Service Flow. The parame-
ters are:
sfid
The Service Flow ID.
clsid
The Classifier ID.
phsid
The PHS ID.
dsa300b ipaddr port Initiates DSA with one Best Effort Ser-
vice Flow and one classifier. The
parameters are:
ipaddr
The destination IP address.
port
The upstream port.
dsa_scn_4 portA portB Runs DSA with upstream and down-
portC portD stream Service Flows with SCN (test 4).
The four parameters specify each of the
four upstream ports.
dsc_scn_4 ussf portB portC Runs DSC for upstream and down-
dssf clsid portD stream Service Flows (test 4). The
parameters are:
ussf
The upstream Service Flow ID.
portB/C
Two upstream ports.
dssf
The downstream Service Flow ID.
clsid
The Classifier ID.
portD
The downstream port.
Debug Enters the Debug submenu. The following commands are available.
cerreset
equadump
equthresh
macread
macwrite
setequthresh
temptuner
adcdump
length
The length of the dump (in pairs).
dump
Syntax: dump 0
Displays all PHY registers.
read
tunerstatus
Example:
Debug> tunerstatus
IF AGC -60
RF AGC 4.000 [dB] ( ATTN = 0, RL = 5, DNC = 75 )
1st LO freq is 1986000256.000 [Hz] ˜ 1986.000 [MHz]
2nd LO freq is 1166999936.000 [Hz] ˜ 1167.000 [MHz]
Input center frequency is 741000000.000 [Hz] ˜ 741.000 [MHz]
Current 1st IF in use is 1245000192.000 [Hz] ˜ 1245.000 [MHz]
Output center frequency is 77500000.000 [Hz] ˜ 77.500 [MHz]
Output channel bandwidth is 89.000 [MHz]
Debug>
usstatus
dsstatus
write
mml
dml
phystatus
berstatus
isrmask
flag
Either 1 to set the mask, or 0 to unset the mask.
clearNvramDsUsFreqDb
clearNvramUsFreqDb
printNvramDsUsFreqDb
initDsUsFreqDb
allphystatus
Displays the PHY status for all active channels (DOCSIS 3.0 mode only).
ucdCollectStatus
SetDebugOption
SetAllDebugOptions
showDebugOptions
Syntax: showDebugOptions
Shows a list of debug options.
ForceT4Multiplier
ForceRngRspAbort
ForceRngRspFreq
ucid
The upstream channel ID. Use 0 to specify all upstreams.
timeout
The timeout period. Use 0 to disable timeout, or −1 to display the
current settings.
ForceRngRspDRW
value
Used with the Override action; specifies the override value.
ForceRngRspPowerOffset
RebootSimulate
SetMimo
CAUTION
Potentially service-affecting
Override settings can potentially prevent the eDVA from registering. For
example, setting this object to 2 (IPv6) when no DHCPv6 server is available
causes the eDVA to attempt to register as IPv6 only, ignoring any DHCPv4
servers. Since this setting is stored in non-volatile memory, you must either
change the value using SNMP or the CLI, or reset the Telephony Modem to
factory defaults to clear the setting.
SetMdCfgIpProvMode
DCC
DBC
ForceUsPSM
ForceDsPSM
Dsid Enters the Dsid submenu. The following commands are available.
mdfMode
dsidCounters
confCode
reseqDsids
mcastDsids
allDsids
DSID Information:
-----------------
printDsidDb
dbridgeMdfDb
dbridgeAlt
dbridgeListCpe
dbridgeCounters
Syntax: dbridgeCounters
Displays DOCSIS Bridge counters.
enableTdox
Enables TurboDox.
disableTdox
Disables TurboDox.
tdox
enableL2vpnPromMode
disableL2vpnPromMode
stats
if
tpPorts
filters
classifiers
Displays QoS Classifier match packet counters by SFID and classifier ID.
all
Psm Enters the Psm submenu. The following commands are available.
downstream
upstream
phy-mac
pp
Syntax: pp {flag}
Enables or disables PSM on the Packet Processor.
psm
wb-adc
pompt
get-pompt
provisioning Enters the Provisioning submenu. The following commands are available.
dhcpServersConfig
sendCMLinkUpEvent
sendMSMStartEvent
sendDHCPLeaseFailEvent
sendDHCPNewIPEvent
sendCMLinkDownEvent
sendCMFullScanNoQam
sendCMQamRegained
sendCMResetEvent
sendMTAResetEvent
sendVoiceRstDoneEvent
sendVoiceRstFailEvent
sendSecRstDoneEvent
sendSecRstFailEvent
configFile
hashBypassSet
provDBcontents
setVoiceLoopVoltage
tftpAlwaysOn
provStatus
provFlow
provDebug
security Enters the Security submenu. The following commands are available.
resetTickets
overrideCmsTtl
timersDisplay
smDataDisplay
mtaDisplay
displayDB
certificates
Command Description
certManufSet Syntax: certManufSet {mode} {mfrcert} {mfrkey}
Sets the manufacturer certificate files. The parameters
are:
mode: 1 for Euro, or 0 for North America.
mfrcert: The manufacturer certificate file name.
mfrkey: The encryption key used to validate the manu-
facturer certificate.
certIpteleSet Syntax: certIpteleSet {mode} {rootcert}
Sets the Intel root certificate file. The parameters are:
mode: 1 for Euro, or 0 for North America.
rootcert: The root certificate file name.
resetCertsToDefault Resets the manufacturer and Iptel root certificates to
the defaults specified in NVRAM.
displayCertContent Syntax: displayCertContent {mode} {type}
Displays the contents of the specified certificate. The
parameters are:
mode: 1 for Euro, or 0 for North America.
type: One of 1 (eDVA), 2 (Manufacturer), or 3 (Root).
setCertsRootType Syntax: setCertsRootType {zone} {type}
Forces selection of the specified root certificate. The
parameters are:
zone: 1 for Euro, or 0 for North America.
type: The root certificate type, 1 for Test Root or 2 for
Real Root.
displayCertsDir Displays the current root certificate.
CAUTION
Potentially service affecting
These commands change settings in NVRAM and may be service-affecting.
Use these commands only with the guidance of ARRIS Technical Support.
vendorSetDhcpServerAddr
vendorModifyDhcpAckParam
MTA24
Send events to a Syslog server: 0 to disable, 1 to enable.
MTA25
Send events using SNMP Inform: 0 to disable, 1 to enable.
download
Specify whether to download the configuration file: 0 to disable, 1
to enable.
local
A string specifying the local configuration file name.
syslog
The IP address of the Syslog server.
realm
A string containing the realm name.
vendorSetTftpData
vendorAddSnmpTarget
printVendorRegisteredEvents
VENDOR_STATUS_VENDOR_APP_set
VENDOR_AFTER_MSM_INIT_set
VENDOR_SET_DHCP_SERVER_ADDR_set
VENDOR_AFTER_DHCP_ACK_set
VENDOR_SET_TFTP_DATA_set
VENDOR_ADD_SNMP_TARGET_set
VENDOR_BEFORE_MTA_RESET_set
VENDOR_ENABLE_EVENTS_set
VENDOR_ENABLE_DHCP_PLUG_IN_set
VENDOR_ENABLE_CFM_PLUG_IN_set
VENDOR_DISABLE_CFM_SPEC_TREE_set
restore
save
show
CAUTION
Potentially service affecting
These commands change settings in NVRAM and may be service-affecting.
Use these commands only with the guidance of ARRIS Technical Support.
prodSet
PACM_CONFIG_EURO_set
PACM_CONFIG_MTA_NUM_LINES_set
PACM_CONFIG_IP_ADDR_set
PACM_CONFIG_HW_ADDR_set
PACM_CONFIG_MTA_TELE_ID_set
PACM_CONFIG_MTA_BBU_set
save
show
setDefaultMacAddress
dynamicConfig Enters the Dynamic Configuraion Menu. The following commands are avail-
able.
set
PACM_DYN_CONFIG_LOOPV_POLICY_set
PACM_DYN_CONFIG_LOOPV_STATUS_set
PACM_DYN_CONFIG_LOOPV_RESET_TIMER_set
PACM_DYN_CONFIG_LOOPV_MAINT_TIMER_CD_set
PACM_DYN_CONFIG_SNMP_ENGIN_BOOT_NUM_set
restore
save
show
event Enters the Event Menu. The following commands are available.
sendEvent
displayEventTable
printLogFile
resetLogFile
deleteLogFile
resetTables
debugMenu Enters the Debug Menu. The following commands are available.
debugSet
PACM_CONFIG_EURO_HASH_SIZE_20_set
PACM_CONFIG_MTA_RESET_WATCH_DOG_set
PACM_CONFIG_TICKETS_FLASH_SUPPORT_set
PACM_CONFIG_PROV_DHCP_RETRIES_set
PACM_CONFIG_IPSEC_ENABLE_set
PACM_CONFIG_PROVISION_FLOWS_SUPPORT_set
PACM_CONFIG_CERTIFICATION_MODE_set
PACM_CONFIG_SNMPV2_ACCESS_set
PACM_CONFIG_TLV38_SNMPV1_ENABLE_set
PACM_CONFIG_CFM_FILE_HASH_BYPASS_set
PACM_CONFIG_MAS_ROUTE_TO_LOGGER_set
ARRIS_PROVISIONING_set
restore
save
show
managerMenu Enters the Manager Menu. The following commands are available.
PACM_MANAGER_VOICE_SLIC_PSM_STATUS_set
PACM_MANAGER_VOICE_DECT_IF_set
PACM_MANAGER_VOICE_VLM_IF_set
PACM_MANAGER_SNMP_RESTRICT_CONFIG_VIEW_set
PACM_MANAGER_TOD_DELAY_SEC_PROV_set
PACM_MANAGER_HITLESS_SOFTWARE_DOWNLOAD_set
PACM_MANAGER_HITLESS_DHCP_set
PACM_MANAGER_RANDOM_USM_SPIN_LOCK_set
PACM_MANAGER_VENDOR_COMMUNITY_NAME_set
PACM_MANAGER_VENDOR_CMS_AS_IP_set
PACM_MANAGER_VENDOR_ENABLE_EVENTS_set
PACM_MANAGER_PSM_ENABLE_set
restore
save
show
componentsList Displays the components list and indicates the current status of each compo-
nent.
Example:
logger> componentsList
Logger Components List:
1 DOCSIS Disabled
2 PACM Disabled
3 COMMMON_COMPONENTS Disabled
4 VOICE Disabled
6 ARRIS Disabled
logger>
9 DMD Disabled
10 DMG Disabled
11 RCCDB Disabled
12 TCCDB Disabled
13 TCC_PARSER Disabled
14 EVENT_MGR Disabled
15 REGISTRATION Disabled
16 FLTR_CLASS Disabled
17 HAL Disabled
18 DS Disabled
19 SME Disabled
20 UCD Disabled
21 US Disabled
22 NVRAM_DB Disabled
23 IPP Disabled
24 QOS Enabled
25 PROD_DB Disabled
26 REINIT_MAC Disabled
27 DSID Disabled
28 UTILS Disabled
29 CMSTATUS Disabled
30 CMCONTROL Disabled
31 MDD Disabled
32 FREQ_SCAN Disabled
33 LEDD Disabled
34 DOCSIF Disabled
35 MNGT_FLOW Disabled
36 CHDB Disabled
37 SYSCFG_DB Disabled
38 DOCSISCFG_DB Disabled
severitiesList Displays the severities list and indicates the current status of each severity.
Example:
logger> severitiesList
Logger Severities List:
0 FATAL Enabled
1 ERROR Enabled
2 WARNING Enabled
3 INFO Enabled
4 INIT Enabled
5 STATISTICS Enabled
6 ENTER Enabled
7 EXIT Enabled
8 USER_DEFINED Enabled
9 DEBUG Enabled
10 FATAL_BUFFER Enabled
11 ERROR_BUFFER Enabled
12 WARNING_BUFFER Enabled
13 INFO_BUFFER Enabled
14 DEBUG_BUFFER Enabled
15 INFO_VERBOSE Enabled
logger>
logger>
targetsList Displays the target list and indicates the status for each target.
Example:
logger> targetsList
Logger Targets List:
0 Screen Enabled
1 File Disabled
2 UDP Disabled
logger>
socketShow Displays the IP address and port of the Logger UDP target. Use the Socket-
Config command to make changes.
Example:
logger> socketShow
UDP Target Settings:
Destination IP: 192.168.100.100
Destination Port: 4571
logger>
filenameShow Displays the name of the local log file. Use the FilenameConfig command
to set the log file name.
logger>
info Shows all logger information (severities, targets, queue, and so on).
must_text
vendor_text
The text message associated with the event.
ipaddr
The IP address of the Syslog server.
The Voice CLI provides commands to display and control the eDVA.
!reset Resets the Telephony Modem as if you pushed the Reset button on the back
of the unit.
Top-Level Commands
The following commands are available at the top Voice CLI level.
dsp Enters the DSP sub-menu. See ‘‘Voice DSP Commands’’ on page 620.
callp_cp Enters the Call Processing sub-menu. See ‘‘Voice CallP Commands’’ on
page 666.
mta Enters the MTA sub-menu. See ‘‘MTA Sub-Mode Commands’’ on page 693.
dimdbg opt
dimdbg ver
Example:
[ 3] DSP> dimdbg ver
dimdbg ver
Multimedia Application Services: 2.4.6(Build 1)
DSP 0: version = Cap 0xfc2c, AER tail len 0, Rel 2.4.6.1,
Build c21 , Id:0 Oct:22:2009 16:27:20, DSP Unknown Processor!,
Cap2 0x26fa,Cap3 0xb, Chans 8, Security info 0x0,
EC tail len 32, PCM only chans 4, Cap4 0x4120, Cap5 0xc44f,
Cap6 0x15, Cap7 0xae48, Cap8 0xc0, Audio None, frame size 10ms,
Max playout segments 35, Max conference chans 12
dimdbg stats
dimdbg dump
dimdbg silence
dimdbg cfg
dimdbg pt
dimdbg tcids
Return Status: 0
dimdbg set_poll
dimdbg set_voice_poll
dimdbg gsync
dimdbg msg
dimdbg sig
dimdbg ndu_stat
Return Status: 0
dimdbg prof_define
dimdbg lo_details
dimdbg hpi_details
DIM: ------------------------------------
DIM: ---- HPI Layout Details for DSP 0
DIM: ------------------------------------
DIM: ---- Version ID = 1.0 (Version C)
DIM: ---- DSP2MIC FIFOs = 3
DIM: ---- MIC2DSP FIFOs = 3
DIM: ---- ACS Start Address = 0x007b 8040
DIM: ---- HPI Alignment = 32-BIT ALIGNMENT, PADDING ENABLED
DIM: ------------------------------------
DIM: ---- DPS to MICRO FIFOs ------------
DIM: ------------------------------------
DIM: ---- FIFO Type = GENERAL
DIM: ---- Allowed Pkt Types = NORMAL PRIORITY MSG/LOW PRIORITY MSG
DIM: ---- FIFO Start = 0x007b a980
DIM: ---- FIFO Size = 0x0400 (1024)
DIM: ---- ACS Offset = 0x007b 8042
DIM: ------------------------------------
DIM: ---- FIFO Type = GENERAL
DIM: ---- Allowed Pkt Types = HIGH PRIORITY MSG
DIM: ---- FIFO Start = 0x007b a580
DIM: ---- FIFO Size = 0x0200 (512)
DIM: ---- ACS Offset = 0x007b 8046
DIM: ------------------------------------
DIM: ---- FIFO Type = GENERAL
DIM: ---- Allowed Pkt Types = VOICE/FAX/DATA
DIM: ---- FIFO Start = 0x007b 8100
DIM: ---- FIFO Size = 0x1140 (4416)
DIM: ---- ACS Offset = 0x007b 804a
DIM: ------------------------------------
DIM: ---- MICRO to DSP FIFOs ------------
DIM: ------------------------------------
DIM: ---- FIFO Type = GENERAL
DIM: ---- Allowed Pkt Types = NORMAL PRIORITY MSG/LOW PRIORITY MSG
DIM: ---- FIFO Start = 0x007b a780
DIM: ---- FIFO Size = 0x0200 (512)
Return Status: 0
dimdbg test_poll_period
dimdbg show_reflection_page
dimdbg power
dim mips_stat
dim set_status_req
dim reset_tdm
dadbg usage
dadbg dnld
dadbg image
dadbg base
dadbg chan
dadbg overlay_pcm_lbrc
dadbg chan_alloc_order
dadbg sec_alloc
dadbg sec_config
Syntax: dadbg sec_config {dsp | micro} [none | srtp | pktcbl | all] [none |
rtp | rtcp | all] [max_chan_rtp] [max_chan_rtcp]
Modifies the security configuration of the Micro portion of the DSP allocator.
dadbg sec_show
dsimdbg show
dsimdbg select
toNET
Starts or stops the tone toward the network (0 or 1).
toTELE
Starts or stops the tone toward the CPE (0 or 1).
Change voice playout settings only for a standing call. The parameters are:
tcid
The TCID to configure. Valid range: 0 to 3.
nom_delay
The nominal delay, in milliseconds. Valid range: the packetization
rate to 135 ms.
max_delay
The maximum delay, in milliseconds. Valid range: the packetiza-
tion rate to 135 ms.
min_delay
The minimum delay, in milliseconds. Valid range: the packetiza-
tion rate to 135 ms.
conceal
0: none
1: standard
2: G711A1
adap_po
0: fixed
1: silence
2: immediate
Example:
[ 57] DSP> nomjitter 2
11:00:00 RT 13 tCLI Nominal VP buffer set to 2x the packetization
rate.
Return Status: 0
Example:
[ 58] DSP> maxjitter 2
11:00:00 RT 13 tCLI Maximum VP buffer set to 2x the packetization rate.
Return Status: 0
Example:
[ 69] DSP> echotail 1
echotail 1
Return Status: 0
Example:
[ 14] DSP> rxtx_stat 1 0
rxtx_stat 1 1
Return Status: 0
[ 15] DSP> 10:25:16 RT 13 tMVX_C Rx/Tx Stats for 2
10:25:16 RT 13 tMVX_C Rx Voice Packets = 2875
10:25:16 RT 13 tMVX_C Tx Voice Packets = 2875
10:25:16 RT 13 tMVX_C Tx Silence Suppressed Frames = 0
10:25:16 RT 13 tMVX_C Rx Min Jitter = 0 (ms)
10:25:16 RT 13 tMVX_C Rx Max Jitter = 23 (ms)
10:25:16 RT 13 tMVX_C Rx RTP Avg Jitter = 0 (pcm samples)
10:25:16 RT 13 tMVX_C Tx Grant Sync Dropped Frames = 0
10:25:16 RT 13 tMVX_C Tx Octets = 460000
10:25:16 RT 13 tMVX_C Rx Octets = 460000
10:25:16 RT 13 tMVX_C DTMF Tx Packets = 0
10:25:16 RT 13 tMVX_C DTMF Rx Packets = 0
10:25:16 RT 13 tMVX_C SID Rx Packets = 0
10:25:16 RT 13 tMVX_C SID Tx Packets = 0
10:25:16 RT 13 tMVX_C Tx Last Timestamp = 459800
10:25:16 RT 13 tMVX_C Tx Extended Seq Number = 0
10:25:16 RT 13 tMVX_C Tx Last Seq Number = 2874
10:25:16 RT 13 tMVX_C Tx Last Pkt Type = 0
10:25:16 RT 13 tMVX_C Rx Last Timestamp = 459800
10:25:16 RT 13 tMVX_C Rx Last Ssrc = 123
10:25:16 RT 13 tMVX_C Rx Extended Seq Number = 0
10:25:16 RT 13 tMVX_C Rx Last Seq Number = 2874
10:25:16 RT 13 tMVX_C Rx Last Pkt Type = 0
10:25:16 RT 13 tMVX_C Pkt Lost by Network = 0
10:25:16 RT 13 tMVX_C Rx P2P Packets to Hosts = 0
10:25:16 RT 13 tMVX_C Rx P2P Filtered Packets = 0
10:25:16 RT 13 tMVX_C P2P Squelched Voice Packets = 0
10:25:16 RT 13 tMVX_C Rx Net Packets = 2875
10:25:16 RT 13 tMVX_C Tx Net Packets = 2875
10:25:16 RT 13 tMVX_C Rx Last Voice Prof Idx = 0
tcid
The channel number. Valid range: 0 to 3.
clear
0: do not clear statistics
1: clear statistics
Example:
[ 20] DSP> err_stat 1 0
err_stat 1 0
Return Status: 0
[ 21] DSP> 17:02:39 RT 13 tDSP Error Stats for 1
17:02:39 RT 13 tDSP invalid_header_count: 0
17:02:39 RT 13 tDSP to_micro_overflow_count: 0
17:02:39 RT 13 tDSP lost_enh_packet_count: 0
17:02:39 RT 13 tDSP no_core_packet_count: 0
17:02:39 RT 13 tDSP pkt_lost_by_network: 2
17:02:39 RT 13 tDSP invalid_mac_header_count: 0
17:02:39 RT 13 tDSP invalid ssrc count: 0
17:02:39 RT 13 tDSP invalid payload count: 0
17:02:39 RT 13 tDSP rx routing dropped: 0
17:02:39 RT 13 tDSP p2p invalid pkt count: 0
17:02:39 RT 13 tDSP rx seq num discont events: 7
17:02:39 RT 13 tDSP rx aal2 crc10 err count: 0
Example:
[107] DSP> level_stat 1 0
level_stat 1 0
Return Status: 0
[108] DSP> 14:26:29 RT 13 tDSP Tele levels for 1
14:26:29 RT 13 tDSP rx_level: -400
14:26:29 RT 13 tDSP tx_level: -420
14:26:29 RT 13 tDSP rx_mean: -2
14:26:29 RT 13 tDSP tx_mean: 0
14:26:29 RT 13 tDSP frame_underrun_count: 8
Example:
[113] DSP> vp_stat 1 0
vp_stat 1 0
Return Status: 0
[114] DSP> 14:31:02 RT 13 tDSP Voice Playout Delay Stats for 1
14:31:02 RT 13 tDSP Avg Playout Delay: 30
14:31:02 RT 13 tDSP Lost Segments: 88644
14:31:02 RT 13 tDSP Replayed Segments: 88644
14:31:02 RT 13 tDSP Idle Segments: 319931
14:31:02 RT 13 tDSP FIFO Dropped Segments: 406947
14:31:02 RT 13 tDSP Rx Segments: 16290412
14:31:02 RT 13 tDSP Rx Avg Pkt Jitter: 0 (pcm samples)
14:31:02 RT 13 tDSP Adpt PO Buf Delay Inc: 41867
14:31:02 RT 13 tDSP Adpt PO Buf Delay Dec: 52393
14:31:02 RT 13 tDSP Cell Starve Evt Cnt: 41914
14:31:02 RT 13 tDSP PO Buf Underflow Cnt: 0
Example:
[116] DSP> echo_stat 1 0
echo_stat 1 0
Return Status: 0
[117] DSP> 14:33:36 RT 13 tDSP Px Level: -41.6250
14:33:36 RT 13 tDSP Py Level: -39.0625
14:33:36 RT 13 tDSP Pe Level: -39.1250
14:33:36 RT 13 tDSP Estimated ERL: 32.8750
14:33:36 RT 13 tDSP Acom Estimate: 32.8750
14:33:36 RT 13 tDSP P[06,13] 0x0010 0x6dd0 0x0000 0x0000 0x0000 0x0000
0x000d 0x75ef
: 1 enable
Current setting: Enable
Return Status: 1
Return Status: 0
jitsim Sub-Mode These commands control the Jitter Simulator. In jitsim sub-mode, the prompt
is Jitter Simulator>.
enable
disable
settings
drop
delay
time
delay time in ms
Example:
[ 91] Jitter Simulator> delay 10
delay 10
Next packet delay: 10 ms
Return Status: 0
loss_off
loss_fixed
loss_random
jit_off
jit_fixed
jit_shift
jit_burst
jit_random
Return Status: 0
jit_random_win
jit_rolling
debug
setvp
adap_po
0: fixed
1: silence
2: immediate
vp_stat
Example:
[113] DSP> vp_stat 1 0
vp_stat 1 0
Return Status: 0
[114] DSP> 14:31:02 RT 13 tDSP Voice Playout Delay Stats for 1
14:31:02 RT 13 tDSP Avg Playout Delay: 30
14:31:02 RT 13 tDSP Lost Segments: 88644
14:31:02 RT 13 tDSP Replayed Segments: 88644
14:31:02 RT 13 tDSP Idle Segments: 319931
14:31:02 RT 13 tDSP FIFO Dropped Segments: 406947
14:31:02 RT 13 tDSP Rx Segments: 16290412
14:31:02 RT 13 tDSP Rx Avg Pkt Jitter: 0 (pcm samples)
14:31:02 RT 13 tDSP Adpt PO Buf Delay Inc: 41867
14:31:02 RT 13 tDSP Adpt PO Buf Delay Dec: 52393
14:31:02 RT 13 tDSP Cell Starve Evt Cnt: 41914
14:31:02 RT 13 tDSP PO Buf Underflow Cnt: 0
CAUTION
Potentially service affecting
Writing directly to memory can cause the Telephony Modem to reset or lose
communication with the headend.
CAUTION
Potentially service affecting
The provision and deprovision commands may disable telephone service if
used on a deployed Telephony Modem.
Responses:
Loop diags request sent for line n
The eDVA has started loop diagnostics on the specified line.
Warning: Action is Service Affecting. Use ’diagForce’ to force diagnos-
tics
The line is in service. You can take the line out of service manu-
ally, using the CallP oos command, or use the diagForce com-
mand to force the line out of service and start the diagnostics.
Loop diags request already in queue
A diagnostics test is already in progress for the specified line. Wait
10 to 20 seconds for the current tests to complete before starting
another test.
Loop diags test ended for line n
The loop diagnostics have completed for the specified line. Use
the dresults command to view the test results.
Return Status: 17
CAUTION
Potentially service affecting
Using the ring command may impact subscriber service.
flag
Select 0 for off or 1 for on.
Example:
[ 82] Linecard> ring 1 1 1
ring 1 1 1
Reverse ringing ON
Return Status: 0
CAUTION
Potentially service affecting
Using the polarity command may cause problems when used with subscriber
equipment.
Present Status:
Line 1 - Loop Current Setting is Boosted
Line 2 - Loop Current Setting is Normal
Return Status: 0
Example:
[ 34] Linecard> hook *
hook *
line 1 is offhook
line 2 is onhook
line 3 is onhook
line 4 is onhook
Return Status: 0
CAUTION
Potentially service affecting
Using the tone command on a subscriber line may cause undesired behavior.
CAUTION
Potentially service affecting
Using the xconnect command on a subscriber line may cause undesired
behavior. If you are using this command to diagnose a trouble call, remem-
ber to disable cross-connect after completing the testing.
Return Status: 0
Return Status: 0
1 : Chile
2 : Japan1
3 : Germany
4 : Netherlands
6 : Australia
7 : Austria/France/Hungary/Slovakia
9 : Netherlands09
10 : Israel
13 : Mexico/MexicoC
14 : Germany2
15 : NorthAmerica66
Note: Setting this object is not the same as setting the Country Template
value—it only changes the line card template.
Example:
[ 10] Linecard> template 1 0
template 1 0
Setting line 1 to template 0.
Return Status: 0
machineID
The machine ID to trace.
setting
Use 0 to disable printing or 1 to enable printing.
Example:
[ 3] Linecard> state
state
ID FSM Name State
-- -------- -----
1 Line 2 AMD Standby
2 Line 2 CallP CSCIdle
3 Line 1 AMD Standby
4 Line 1 CallP CSCIdle
5 LC Diags Diag Idle
Return Status: 0
CAUTION
Potentially service affecting
Using the vbat command may cause certain subscriber equipment to not
detect ring voltage.
Return Status: 0
Example:
[ 25] Linecard> ringfreq 2 1
ringfreq 2 1
line 2 set to index 1
Return Status: 0
Transmit/Receive Timeslot:
TX Timeslot: 0x00 Receive Timeslot: 0x00
Voicepath Gains: 0x00
Transmit Analog Gain: 0 dB gain
Receive Analog Loss: 0 dB loss
Digital Receive Loss: 0 dB loss in receive path
Transmit/Receive Timeslot:
TX Timeslot: 0x02 Receive Timeslot: 0x02
Voicepath Gains: 0x00
Transmit Analog Gain: 0 dB gain
Receive Analog Loss: 0 dB loss
Digital Receive Loss: 0 dB loss in receive path
...
----------------Other Linecard Parameters------------------
CAUTION
Potentially service affecting
Avoid using the batcal and polling commands unless instructed by ARRIS
Technical Support.
2: dump all call processing and non call processing (line card, DSP,
datapath) information related to the line
Example:
[ 19] Call Processing> dlr 1 0
dlr 1 0
Line Number (1-based) = 1
Endpoint State = In Service
Return Status: 0
dst Prints the call processing and administrative states of all lines. The state is
one of the following:
State Description
EP_IS In Service
EP_RST Restart in progress
EP_DISC Disconnected
EP_OOS Out of Service
Example:
[ 20] Call Processing> dst
Line State ifIndex ifAdminStatus operStatus
------------------------------------------------------------
1 2 (EP_RST ) 9 UP UP
2 2 (EP_OOS ) 10 UP DOWN
Value State
0 No state change
1 Out of Service
2 Intermediate state for taking In Service
3 Null (idle)
4 Call Init
5 Call Received
6 Call Inactive
7 Call Active
8 QoS Create
9 QoS Modify
10 Remote Disconnect
11 Local Disconnect
force
Use 1 to force the line to change to the new state, 0 otherwise.
r: hf(i), hd(n)
CAUTION
Loss of service
Enabling multiple traces during extremely high call volumes, such as bulk
call testing, can cause the E-UE to lock up. Contact ARRIS Technical Sup-
port before enabling tracing during call testing.
Value Description
0 Callp Connection FSM Trace
1 Japanese Caller ID State Trace
2 Traffic Debugging State Trace
3 Signals Processing State Trace
4 CMS-initiated VMWI State Trace
5 CMS-initiated Caller ID State Trace
6 Fax or Modem Detection State Trace
7 Quarantine Buffer Processing Trace
8 DSP Handling Trace
9 Echo Cancellation Processing Trace
10 Call Processing Message (i.e. NCS) Trace
11 Trace dialed digits
12 Trace RFC2833 event processing
13 Trace RTP/RTCP Statistics Gathering
14 Trace Ring Generation
15 Trace Gain Control Adjustments
16 Trace Signaling (SIP/NCS) Errors
17 Trace NCS Msg Round Trip Delay
18 Trace SIP/NCS Registration
19 Trace NCS Message History
20 Trace SIP Callleg Messages
21 Trace SIP Subscription Messages
22 Trace SIP Transaction Messages
23 Trace CallP Message Queue Processing
24 Trace SIP Error Messages
25 Trace SIP Publish Messages
26 Trace DSX [0]
27 Trace SIP DNS Records
28 Trace SIP P-CSCF Selection
99 ALL Traces
enable
0: off
1: on
Example:
[ 33] Call Processing> trace 1 1
trace 1 1
Japanese CID trace enabled
Return Status: 0
Example:
[ 37] Call Processing> mgcp 1
mgcp 1
MGCP message trace enabled
Return Status: 0
tone
One of the following:
• lt (local tones)
• nt (ringback and other network tones)
• fsk (CID and VMWI tones)
• cas (CAS tones)
• ldtmf (DTMF tones toward the CPE)
• ndtmf (DTMF tones toward the network)
• rx (receive audio)
• tx (transmitted audio)
val
The change to the tone, in dBm. Omit this parameter to show the
current gain setting for the specified tone.
Example:
[ 4] Call Processing> setgain nt
setgain nt
MIB value for nt is 0
Return Status: 0
Return Status: 0
dmon Displays information about event messages between the eDVA and the CMS.
Example:
[ 99] Call Processing> dmon
dmon
Call Agent Socket information:
callp_netifp_ca_open = 1
CPInitRetries = 0
CountofInitFailed = 0
CountofSuccessiveInitFailed = 0
RF Communications up = TRUE
MTA Registration Complete = TRUE
MTA IP Address Lost = FALSE
Total Potential IPDT No Alert Due To Wrong RFC2833 Message Received before Ring Request...
Line 1 = 0
Line 2 = 0
Line 1:
There is no data to display for line 1
Line 2:
There is no data to display for line 2
Return Status: 0
cum_delay : 0
est_jitter : 0
n_pkts_lost : 0
seq_num : 0
ts : 0
n_pkts_drop_cb : 0
n_pkts_drop_cb_rtcp : 0
n_pkts_drop_udp_send : 0
n_pkts_drop_lbt_send : 0
last count for p_sent : 0
last count for p_recv : 0
last count for b_sent : 0
last count for b_recv : 0
last ts : 0
last average jitter : 0
last max jitter : 0
last last_seq : 0
last count for lost : 0
stat_req_active : 0
ntp_sec : 0
ntp_fract : 0
other_ssrc : 0
other p_sent : 0
other b_sent : 0
other lost : 0
other jitter : 0
Return Status: 0
Value Description
1 Tone only
2 Pulse only
3 Tone and pulse
4 Pulse only with DTMF relay
5 Tone and pulse with DTMF relay
0, 0, 0
0, 0, 0
0, 0, 0
...
Return Status: 0
Example:
[ 70] Call Processing> parser 1
parser 1
Return Status: 0
Value State
0 CSC_OOS
1 CSC_Idle
2 CSC_Addr
3 CSC_Talk
5 CSC_FDisc
6 CSC_Ring
7 CSC_OnHookTx
8 CSC_TipOpen
11 CSC_TrunkC
12 CSC_Prot
13 CSC_Diags
14 CSC_PLO
is Syntax: is {line}
Puts the specified line in service by setting the ifAdminStatus MIB object.
The valid range for line is 1 to 2.
Example:
[ 63] Call Processing> is 2
is 2
Putting line 2 in-service (ifAdminStatus UP)
Return Status: 0
Return Status: 0
Displays ring cadences for the specified country. The parameters are:
country
One of the country code numbers listed in ‘‘Country Code Tem-
plates’’ on page 464, or a to display all ring cadences for the active
country template, or A to display all ring cadences for all countries.
default
Use 0 to read cadences from the current MIB values, or 1 to use the
default cadences. This may be useful for debugging purposes.
signal
Displays the selected signal instead of all cadences.
Note: Only the ring cadences that have names beginning with ‘‘l/’’ can be
changed through SNMP.
sip_callleg (SIP only) Toggles SIP callleg message tracing. Messages printed include
SIP Invite and INFO messages.
sip_error (SIP only) Toggles SIP error reporting. Messages printed include error mes-
sage responses.
sip_subs (SIP only) Toggles SIP subscription message (VMVI) tracing. This com-
mand requires the ‘‘RFC3842 handshake’’ SIP feature switch to be set.
sip_trans (SIP only) Toggles SIP transaction message (VMWI) tracing. This command
requires the ‘‘RFC3842 handshake’’ SIP feature switch to be cleared.
penalty_box (SIP only) Displays proxies listed in the SIP penalty box.
regevent_timer (SIP only) Sets the Registration Event Outgoing Expires Timer.
sip_impu (SIP only) Displays the primary and implicitly registered IMPU.
line
The line number to set, beginning with 1.
status
Either 0 to enable the line, or 1 to force-disable the line. This value
is stored in non-volatile memory and persists across reboots.
Return Status: 0
[ 55] Call Processing> [ERROR] [VOICE.XSPY(pid=494)]: 0001832377 - DQM: dqmapi: CNTXT_STATE IDL
[ERROR] [VOICE.XSPY(pid=494)]: 0001832377 - cntxt # 0 is in state 0, SHUTDOWN state count 0
[ERROR] [VOICE.XSPY(pid=494)]: 0001832377 - cntxt # 1 is in state 0, SHUTDOWN state count 0
[ERROR] [VOICE.XSPY(pid=494)]: 0001832377 - cntxt # 2 is in state 0, SHUTDOWN state count 0
[ERROR] [VOICE.XSPY(pid=494)]: 0001832377 - cntxt # 3 is in state 0, SHUTDOWN state count 0
[ERROR] [VOICE.XSPY(pid=494)]: 0001832377 - cntxt # 4 is in state 0, SHUTDOWN state count 0
[ERROR] [VOICE.XSPY(pid=494)]: 0001832377 - cntxt # 5 is in state 0, SHUTDOWN state count 0
[ERROR] [VOICE.XSPY(pid=494)]: 0001832377 - cntxt # 6 is in state 0, SHUTDOWN state count 0
[ERROR] [VOICE.XSPY(pid=494)]: 0001832377 - cntxt # 7 is in state 0, SHUTDOWN state count 0
[ERROR] [VOICE.XSPY(pid=494)]: 0001832377 - cntxt # 8 is in state 0, SHUTDOWN state count 0
[ERROR] [VOICE.XSPY(pid=494)]: 0001832377 - cntxt # 9 is in state 0, SHUTDOWN state count 0
[ERROR] [VOICE.XSPY(pid=494)]: 0001832377 - cntxt # 10 is in state 0, SHUTDOWN state count 0
dnsTools Debugging tools for CMS DNS lookup utilities. In dnsTools sub-mode, the
prompt is Debug tools for CMS DNS lookup utilities>.
requery_dns
force_lkup
pne_print
You can enter an MTA sub-mode command without entering MTA sub-mode
by preceding any of the following commands with / mta. In MTA sub-mode,
the prompt is MTA>.
"’[email protected]’"
SNMP_MIB_Object = 1.3.6.1.4.1.4491.2.2.10.4.1.1.3.1.6.1 4
SNMP_MIB_Object = 1.3.6.1.4.1.4491.2.2.10.4.1.1.2.1.2.1 6
SNMP_MIB_Object = 1.3.6.1.4.1.4491.2.2.10.4.1.1.2.1.3.1
0x273531323636363930313440696d732e766f69702e68726e6476612e72722e636f6d27
"’[email protected]’"
SNMP_MIB_Object = 1.3.6.1.4.1.4491.2.2.10.4.1.1.2.1.4.1 1
SNMP_MIB_Object = 1.3.6.1.4.1.4491.2.2.10.4.1.1.2.1.13.1 4
SNMP_MIB_Object = 1.3.6.1.4.1.4491.2.2.10.4.1.1.4.1.2.1.1 4491
SNMP_MIB_Object = 1.3.6.1.4.1.4491.2.2.10.4.1.1.4.1.3.1.1 1
SNMP_MIB_Object = 1.3.6.1.4.1.4491.2.2.10.4.1.1.4.1.4.1.1 1
SNMP_MIB_Object = 1.3.6.1.4.1.4491.2.2.10.4.1.1.4.1.9.1.1 4
SNMP_MIB_Object = 1.3.6.1.4.1.4491.2.2.8.2.1.1.2.1.3.1.3 3
SNMP_MIB_Object = 1.3.6.1.4.1.4491.2.2.8.2.1.1.2.1.4.1.3 1
SNMP_MIB_Object = 1.3.6.1.4.1.4491.2.2.8.2.1.1.2.1.5.1.3 1
SNMP_MIB_Object = 1.3.6.1.4.1.4491.2.2.8.2.1.1.2.1.9.1.3 4
SNMP_MIB_Object = 1.3.6.1.4.1.4491.2.2.8.2.1.2.1.2.1.13.1 26
SNMP_MIB_Object = 1.3.6.1.2.1.2.2.1.7.10 1
SNMP_MIB_Object = 1.3.6.1.2.1.2.2.1.7.9 1
Return Status: 0
[ 5] MTA>
Example:
[ 53] MTA> getSig R0Cadence
getSig R0Cadence
SigDevR0Cadence=ff ff f0 0 0 0 0 0
Arris Cadence=28 50 0 0 0 0 0 0 len=6000ms
Return Status: 0
Return Status: 0
codecs, Voice MTA commands 695 commands, deprovision, Voice Linecard 654
coexistence commands, diag, Voice Linecard 654
configuring SNMP 245 commands, diagForce, Voice Linecard 655
feature switch, MTA 84 commands, dresults, Voice Linecard 655
IPv6 SNMP 212 commands, enableidle, Voice Linecard 665
SNMP 245 commands, errors, Voice Linecard 660
SNMP, configuration for 246 commands, hook, Voice Linecard 659
color, controlling, LED 66 commands, idle, Voice Linecard 660
commands commands, lcstatus, Voice Linecard 664
accesstime, DOCSIS Certification 563 commands, loopc, Voice Linecard 658
adcdump, DOCSIS Debug 580 commands, lpdiag, Voice Linecard 656
addcpe, DOCSIS Atp 565 commands, lpdiagForce, Voice Linecard 656
all, DOCSIS Pp 591 commands, lpresults, Voice Linecard 657
all_off, LED 506 commands, objdump, Voice Linecard 654
all_on, LED 506 commands, polarity, Voice Linecard 658
all_on_green, LED 506 commands, provision, Voice Linecard 654
AllComponentsConfig, Logger 608 commands, read, Voice Linecard 653
AllDebugModulesConfig, Logger 609 commands, regdump, Voice Linecard 653
allDsids, DOCSIS Dsid 589 commands, ring, Voice Linecard 657
AllModulesConfig, Logger 608 commands, ringfreq, Voice Linecard 663
allocChannel, DSP 633 commands, rread, Voice Linecard 654
allphystatus, DOCSIS Debug 584 commands, state, Voice Linecard 662
AllSeveritiesConfig, Logger 608 commands, template, Voice Linecard 661
!appmode, RF 530 commands, tone, Voice Linecard 659
ARRIS_PROVISIONING_set, PACM Debug 605 commands, vbat, Voice Linecard 663
atp, DOCSIS Qos 576 commands, write, Voice Linecard 653
Atp, Main DOCSIS 565 commands, xconnect, Voice Linecard 660
auto_osi, Voice CallP 689 commit, Gateway sub-mode 533
backoffCounters, DOCSIS Fw 571 commit, Technician 512
batcal, Voice Linecard 666 ComponentConfig, Logger 608
berstatus, DOCSIS Debug 583 ComponentDisplay, Logger 609
brief, System PP 556 componentsList, Logger 610
buf_store, Voice CallP 686 confCode, DOCSIS Dsid 588
buffer, System sub-mode 504 config, DSP 633
byteget, Database 516 config, Voice MTA 693
cache, RF 521 configDocsisModule, Main DOCSIS 561
cal_dump, Voice Linecard commands 665 conn_rec, Voice CallP 676
callpClrLog, Voice CallP 669 cotdump, Voice CallP 690
callpDispLog, Voice CallP 668 cpe, DOCSIS Show 562
callpEnblLog, Voice CallP 668 cppiStats, DOCSIS Fw 571
ccudbg, DSP 629 cpq, Voice CallP 681
cerreset, DOCSIS Debug 579 cps, DSP 642
cerreset, Main DOCSIS 560 customjitter, DSP 643
cert, RF 522 custommax, DSP 644
certificates, PACM Security 596 custommin, DSP 643
Certification, Main DOCSIS 563 customnom, DSP 644
change_ne, Voice CallP 671 dadbg base, DSP 629
channelset, RF 523 dadbg chan, DSP 630
checkStackRes, Voice CallP 690 dadbg chan_alloc_order, DSP 630
chg_alink, Voice CallP 684 dadbg dnld, DSP 629
chg_dialing, Voice CallP 680 dadbg, DSP 629
chg_polarity, Voice CallP 684 dadbg image, DSP 629
chg_power, Voice CallP 684 dadbg overlay_pcm_lbrc, DSP 630
chg_state, Voice CallP 683 dadbg sec_alloc, DSP 630
chg_template, Voice CallP 680 dadbg sec_config, DSP 630
chgrStatus, Telemetry 512 dadbg sec_show, DSP 630
chst, Voice CallP 667 dadbg usage, DSP 629
cid, Voice CallP 685 database, DOCSIS Qos 575
classifiers, DOCSIS Pp 591 DBC, DOCSIS Debug 587
clearcw, RF 522 dbg, System PP 555
clearfreq, RF 518 dbridgeAlt, DOCSIS Dsid 589
clearNvramDsUsFreqDb, DOCSIS Debug 583 dbridgeCounters, DOCSIS Dsid 590
clearNvramUsFreqDb, DOCSIS Debug 583 dbridgeListCpe, DOCSIS Dsid 589
clusterSidTable, DOCSIS Fw 570 dbridgeMdfDb, DOCSIS Dsid 589
cmcert, DOCSIS Certification 563 DCC, DOCSIS Debug 587
cmClrLog, DHCP 507 ddly, Voice CallP 687
cmDispLog, DHCP 507 dds, Voice CallP 666
cmEnblLog, DHCP 507 debug, DOCSIS Qos 575
cmstatus, Main DOCSIS 561 debug, DSP jitsim 651
cmstatusmasks, DOCSIS Show 562 Debug, Main DOCSIS 578
codecs, Voice MTA 695 debugMenu, Main PACM 604
commands, cal_dump, Voice Linecard 665 DebugModulesConfig, Logger 609
W
Waiting Indicator, Message 85
warmline 199
waveform
ringing 67
sinusoidal ring 67
trapezoidal ring 67
wb-adc, DOCSIS Psm commands 592
wbdfreq, RF commands 518
WBM750 USB not supported 24
WebGUI
access levels 398
default passwords 398
TACACS+ 440
Wireless screen 446
with, RFC2833, DTMF interactions 83, 99
write
DOCSIS Debug commands 582
RF commands 521
Voice Linecard commands commands 653
wrmStatus, Gateway sub-mode commands 533
X
xconnect, Voice Linecard commands commands 660
XML configuration file 495
XML-based router provisioning 131
xmlLog, Database commands 534
xmlRestart, Database commands 534
xmlStatus, Database commands 533
Corporate Headquarters
ARRIS • Suwanee • Georgia • 30024 • USA
T: 1−678−473−2000 F: 1−678−473−8470
www.arrisi.com