Ubee DDW365 MSO Operations Guide Cox 091515

Ubee DDW365
Wireless Cable Modem

Firmware Version: 8.17.xxxx
MSO Operations Guide

Cox Communications
www.ubeeinteractive.com
8085 S. Chester Street, Suite 200
Englewood, CO 80112
1.888.390.8233
Sales (email): amsales@ubeeinteractive.com
Support (email): amsupport@ubeeinteractive.com
September 2015
Notices and Copyrights
Copyright 2015 Ubee Interactive. All rights reserved. This document contains proprietary information of Ubee and is not to be disclosed
or used except in accordance with applicable agreements. This material is protected by the copyright laws of the United States and other
countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Ubee), except in
accordance with applicable agreements, contracts, or licensing, without the express written consent of Ubee and the business
management owner of the material.
Ubee Interactive continuously improves its products and reserves the right to make changes to the product described in this document
without notice. Ubee Interactive does not assume any liability that may occur due to the use of the product described in this document.
All trademarks mentioned in this document are the property of their respective owners.
This device is Wifi Alliance Certified:

Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Understanding Safety and Regulatory Information . . . . . . . . . . . . . . . . . . . . . . . . . . .1
1.2 Understanding Connections and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
1.3 Requesting Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
1.4 Checking Device Package Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
1.5 Understanding the Device Panels, Connections and LEDs . . . . . . . . . . . . . . . . . . . .4
1.6 Understanding Specifications, Standards, and Firmware . . . . . . . . . . . . . . . . . . . . . .6
1.7 Understanding Default Values and Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
2 Installing the DDW365 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1 Setting Up and Connecting the DDW365 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
2.2 Connecting Devices to the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Troubleshooting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3 Using the Web User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.1 Accessing the Web User Interface Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2 Accessing the Web User Interface Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.3 Accessing Telnet Remotely. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.4 Password of the Day Tool (PoTD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
4 Understanding the Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.1 Using the Software Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2 Using the Connection Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.3 Using the Account Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.4 Using the Diagnostics Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.5 Using the Event Log Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.6 Using the Factory Default Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5 Understanding the Basic Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5.1 Using the Setup Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.2 Using the DHCP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.3 Using the DDNS Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.4 Using the Backup Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
6 Understanding the Advanced Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

6.1 Using the Options Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
6.2 Using the IP Filtering Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.3 Using the MAC Filtering Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.4 Using the Port Filtering Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.5 Using the Forwarding Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.6 Using the Port Triggers Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.7
May 2013
Using the Pass Through Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.8 Using the DMZ Host Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7 Understanding the Firewall Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

7.1 Using the Basic Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.2 Using the Local Log Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.3 Using the Remote Log Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
8 Understanding the Parental Control Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

8.1 Using the Parental Control User Setup Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
8.3 Using the ToD Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
8.4 Using the Local Log Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
9 Understanding the VPN Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

9.2 Using the IPsec Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
9.3 Using the Event Log Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
10 Understanding the Wireless Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

10.1 Using the Wireless Radio Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
10.2 Using the Primary Network Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
10.3 Using the Guest Network Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
10.4 Using the Advanced Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
10.5 Using the Access Control Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
10.6 Using the Wi-Fi Multimedia Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
10.7 Using the Bridging Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
10.8 Deploying and Troubleshooting the Wireless Network. . . . . . . . . . . . . . . . . . . . . . . 90
11 Understanding the USB Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

11.1 Using the USB Basic Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
11.2 Using the Approved Devices Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
11.3 Using the Storage Basic Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
11.4 Using the Storage Advanced Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
11.5 Using the Media Server Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
12 MIB Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

12.1 Ubee MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
13 Understanding the Telnet Command Line Interface . . . . . . . . . . . . . . . . . . . . 246

13.1 Accessing Telnet Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
13.2 Getting Help in Telnet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
13.3 Understanding Telnet Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
May 2013
1 Introduction
Welcome to the Ubee family of data networking products. This guide is specific to the
DDW365 and serves the following purposes:
 Provides multiple system operators (MSOs) with the information necessary to
operationally stage, deploy, and support the DDW365.
 Provides the technical details to locally and remotely manage deployed devices. This
involves setting up configuration files, downloading files to the device, and obtaining
information from the device for support and troubleshooting.
 Defines all relevant device compliance standards and physical specifications.
 Provides information used by the following MSO entity: Cox Communications
 Provides installation instructions and web user interface instructions to configure and
manage the device.
Topics
See the following topics:
 Understanding Safety and Regulatory Information on page 1

 Understanding Connections and Applications on page 3
 Requesting Support on page 3
 Checking Device Package Components on page 3
 Understanding the Device Panels, Connections and LEDs on page 4
 Understanding Specifications, Standards, and Firmware on page 6
 Understanding Default Values and Logins on page 7
1.1 Understanding Safety and Regulatory Information

Use the following information to better understand safety and regulatory standards to
install, maintain, and use the DDW365 Wireless Cable Modem.
1.1.1 Understanding Safety

WARNING: The following information provides safety guidelines for anyone
installing and maintaining the DDW365. Read all safety instructions in this
guide before attempting to unpack, install, operate, or connect power to this
product. Follow all instruction labels on the device itself. Comply with the
following safety guidelines for proper operation of the device.
Ubee DDW365 Wireless Cable Modem MSO Operations Guide • September 2015 1
Understanding Safety and Regulatory Information Ubee Interactive
Follow basic safety precautions to reduce the risk of fire, electrical shock, and
injury. To prevent fire or shock hazard, do not expose the unit to rain and
moisture or install this product near water. Never spill any form of liquid on or
into this product. Do not use liquid cleaners or aerosol cleaners on or close to
this product. Clean with a soft dry cloth.
Do not insert sharp objects into the product’s module openings or empty slots.
Doing so can accidentally damage its parts and/or cause electric shock.
Electrostatic discharge (ESD) can permanently damage semiconductor
devices. Always follow ESD-prevention guidelines for equipment handling and
storage.
Use only the power cable supplied with the device. Do not attach the power
supply cable to building surfaces or floorings.
 Rest the power cable freely without any obstacles. Do not place heavy items on top of
the power cable. Do not abuse, step, or walk on the cable.
 Do not place heavy objects on top of the device. Do not place the device on an
unstable stand or table; the device can fall and become damaged.
 Do not block the slots and openings in the module housing that provide ventilation to
prevent overheating the device. Do not expose this device to direct sunlight. Do not
place hot devices close to this device; it may degrade it or cause damage.
1.1.2 Understanding Eco-Environmental Statements

The following eco-environmental statements apply to the DDW365.
Packaging Collection and Recovery Requirements:

Countries, states, localities, or other jurisdictions may require that systems be established
for the return and/or collection of packaging waste from the consumer, or other end user,
or from the waste stream. Additionally, reuse, recovery, and/or recycling targets for the
return and/or collection of the packaging waste can be established. For more information
regarding collection and recovery of packaging and packaging waste within specific
jurisdictions, contact Ubee Interactive at www.ubeeinteractive.com.
1.1.3 Understanding Regulatory Statements

The following regulatory statements apply to the DDW365.
Industry North America Statement:

This device complies with RSS-210 of the Industry North America Rules. Operation is
subject to the following two conditions:
(1) This device may not cause harmful interference.
(2) This device must accept any interference received, including interference that may
cause undesired operation.
2 Ubee DDW365 Wireless Cable Modem MSO Operations Guide • September 2015
Ubee Interactive Understanding Connections and Applications
Radiation Exposure Statement:

This equipment complies with FCC radiation exposure limits set forth for an uncontrolled
environment. This equipment should be installed and operated with a minimum distance
of 20cm between the radiator & your body. This device has been designed to operate with
an antenna having a maximum gain of 2 dBi. This device must not be co-located with or
operating in conjunction with any other antenna or transmitter.
1.2 Understanding Connections and Applications

The following diagram illustrates the general connection topology and applications of the
DDW365.
1.3 Requesting Support

Subscribers must contact their service provider for direct support. Device documentation
support may be available at:
http://www.ubeeinteractive.com
1.4 Checking Device Package Components

The package for the DDW365 contains the following items:
Item Description
1 - RJ45 Cable (Ethernet)

Length ~ 6.0 ft RoHS & UL compliant
Sample image, actual appearance subject to change.
Understanding the Device Panels, Connections and LEDs Ubee Interactive
Item Description
1 - Power Cable
Input: 90-120VAC ~, 50-60Hz
CE and UL Certified
Sample image, actual appearance subject to change.
1.5 Understanding the Device Panels, Connections and LEDs
1.5.1 Understanding the Device Front and Rear Panels

The following images represent the device front and rear panels. Connection descriptions
are provided in section 1.5.2., and LED descriptions are provided in section 1.5.3.
Front Panel Rear Panel
Ubee Interactive Understanding the Device Panels, Connections and LEDs
1.5.2 Understanding the Device Connections

The following table describes the connections on the device.
Item Description
RESET Restores the settings of the device including wireless and custom
gateway settings. Use a pointed object to push down the reset
button. To power cycle the device, hold for less than 5 seconds. To
reset the device to factory defaults, hold for more than 12 seconds.
USB Connects to USB devices such as flash drives or hard disk drives.
ETH1 Connects to Ethernet devices such as computers, gaming consoles,

ETH2 and/or routers/hubs using an RJ45 cable. Each ETH port on the
ETH3 back panel of the device has an LED to indicate its status when an
ETH4 Ethernet device is connected.
CABLE Connects to the cable outlet (with the cable provided by your
service provider), or a cable splitter connected to the cable outlet.
POWER Connects the cable to the device. Use only the power cable
provided with the DDW365.
WPS Located on top of the cable modem, this button is used for the WiFi
Protected Setup (WPS) method to connect a PIN-protected WiFi
device to the cable modem. Refer to Understanding the Wireless
Menu on page 71 for more information.
1.5.3 Understanding LED Behavior

The following tables summarize the behavior of the LEDs on both the front and rear
panels of the DDW365.
FRONT PANEL
LED Color Description
POWER White On – Internal power-on completed successfully.

Flashes – Power-on failed. Note that the LED blinks briefly immediately after powering on the
device.
US/DS White Flashes – Once every second while scanning DS. Once locked on DS, flashes twice every
(upstream/ second while registering the US.
downstream)
On – Locked to US and DS channels and registered OK.
Flashes – When a firmware upgrade is in progress, and POWER LED and ONLINE LEDs are
ON solid.
ONLINE White Flashes – Obtaining an IP address and configuration file.

On – Configuration completed successfully.
WiFi White On – WiFi is enabled.

Off – WiFi is disabled.
WPS White If not used, the LED is off. When a user pushes the WPS button or triggers WPS via the
BUTTON device’s Web UI, an LED on the top-front of the device blinks for 4 minutes until a PIN is
(top of entered from the wireless client that wishes to connect (for example, a laptop computer). After
device) a WiFi client attaches successfully, the LED remains On for 5 minutes, then turns Off.
Understanding Specifications, Standards, and Firmware Ubee Interactive
REAR PANEL
LED Color Description
ETH1 Green/ On Green – An Ethernet device is connected to the device at 1000 Mbps speeds (Gigabit
ETH2 Orange Ethernet).
ETH3 On Orange – An Ethernet device is connected to the device at 10/100 Mbps speeds.
ETH4 Flashes (in Green or Orange) – When data is being passed between the cable modem and
the connected device.
The Ethernet ports are used to connect Ethernet devices such as computers, gaming
consoles, and/or routers/hubs to the DDW365 using RJ-45 cables. Each Ethernet port on the
back panel of the device has an LED to indicate its status when an Ethernet device is
connected.
1.6 Understanding Specifications, Standards, and Firmware

The following list provides the features and specifications of the DDW365.
Interfaces and Standards
 Cable: F-Connector, female
 LAN: 4 10/100/1000 Mbps RJ45 ports
 USB: 1 USB 2.0 host port
 DOCSIS 3.0 certified
 DOCSIS 1.0/1.1/2.0 certified
 CE/FCC Class B, ENERGY STAR® certified, WiFi Alliance certified
Downstream*
 Frequency Range: 88MHz ~ 1002MHz
 Modulation: 64 / 256 QAM
 Channel Bandwidth: 6 MHz
 Maximum Data Rate per Channel (up to 8 channels): DOCSIS = 30 Mbps (64
QAM), 42 Mbps (256 QAM),
 Total Max Bandwidth (8 Channels): DOCSIS = 343 (304) Mbps
 Symbol Rate: 6952 Ksps
 RF (cable) Input Power: -15 to +15dBmV (64 QAM), -15 to +15dBmV (256 QAM)
 Input Impedance: 75 Ω
Upstream*
 Frequency Range: 5MHz ~ 42MHz
Ubee Interactive Understanding Default Values and Logins
 Modulation A-TDMA: QPSK, 8, 16, 32, 64QAM, S-CMDA: QPSK, 8, 16, 32, 64,
128QAM
 Max Bandwidth of 4 Channels = 122.88 (108) Mbps, bandwidth per channel (up to
4 channels) = [QPSK 0.32 ~ 10.24 Mbps, 8 QAM 0.48 ~ 15.36 Mbps, 16 QAM 0.64
~ 20.48 Mbps, 32 QAM 0.80 ~ 25.60 Mbps, 64 QAM 0.96 ~ 30.72 Mbps, 128
QAM/TCM 30.72 Mbps]
 Symbol Rate: 160, 320, 640, 1280, 2560, 5120 Ksps
 RF (cable) Output Power: TDMA/ATDMA: +8dBmV to +54dBmV (32/64 QAM).
ATDMA Only: +8dBmV to +55dBmV (8/16 QAM), +8dBmV to +58dBmV (QPSK).
S-CDMA: +8dBmV to +53dBmV (all modulations)
*Actual speeds vary based on factors including network configuration and speed.
Security and Network
 Supports 8 SSIDs, 802.11b/g/n compliant with link speeds up to 450 Mbps, 3 Tx
and 3 Rx antennas with single radio
 DHCP Client/Server, Static IP network assignment, RIPv1/ v2, Ethernet
10/100/1000 BaseT, full-duplex auto-negotiate functionality, IPv4 and IPv6 support
 NAT Firewall, MAC/IP/port filtering, parental control, stateful packet inspection
(SPI), DoS attack protection, WPS/ WPA/ WPA2/ WPA-PSK & 64/128-bit WEP
encryption
 VPN pass-through and end-point support (IPSec/PPTP), TACACS or RADIUS
authentication
Device Management
 Supports IEEE 802.11e Wi-Fi Multimedia (WMM) and UAPSD (power savings)
 DOCSIS, Web-Based, and XML Configuration
 Telnet/SSH remote management
 Firmware upgrade via TFTP
 Configuration backup and restore
 SNMP support
 TR-069 capable
Physical and Environmental
 Dimensions: 220mm, 8.625” (W) x 220mm, 8.625” (H) x 42mm, 1.625” (D)
 Weight: 825g (1.8 lbs.) (Contains internal PSU)
 Input: 90-120VAC, 50-60Hz
 Output: 12V 2.17A
 Operating Temperature: 0°C ~ 40°C (32°F ~ 104°F)
 Humidity: 5~90% (non-condensing)
1.7 Understanding Default Values and Logins

The DDW365 is pre-configured with the default parameters for Cox Communications.
Some regions may change default values using the cable modem or XML configuration
file. Check with your provisioning team to determine the default values for your region.
Local Port Address: 192.168.100.1
Understanding Default Values and Logins Ubee Interactive
Web Interface: http://192.168.100.1

Operation Mode: NAT Mode
Subnet Mask: 255.255.255.0
Wireless Defaults:
 Primary SSID (subscriber-managed) = “DDW365” plus a period, plus the last 6
characters of the WLAN MAC address plus “-2.4G”.
Example for modem with MAC ID 08:3E:8E:44:28:02:
SSID: DDW365.442802-2.4G
If the subscriber changes the SSID, the device does not revert to this default
SSID when the device is reset, except when a manual reset is performed
through the Web UI.
The MAC address can be found on the device label or it can be found by
opening an Internet browser window to the device. Refer to Using the Software
Option on page 17 for instructions.
 Encryption Method = WPA2-PSK with TKIP+AES encryption
 WPA Pre-shared Key = Unique key for each device. Also called the network key.
The pre-shared key for the DDW365 is the last 13 characters of the modem’s
serial number. Refer to Using the Primary Network Option on page 74.
Example: B7Y3R11000049
 WPS PIN = The WPS PIN is a randomly-generated number found on the Wireless
Primary Network screen. Refer to Using the Primary Network Option on page 74.
 Device Name: UbeeAP
Login Default Values
 Standard User Web Interface Login
Username: user
Password: user
 MSO Web Interface Login
Username: admin
Password: cableroot
 For remote telnet access information, refer to Accessing Telnet Remotely on page
15.
2 Installing the DDW365
Use the information in this chapter to set up and connect the DDW365, connect additional
devices, and troubleshoot the installation.
Topics
 Setting Up and Connecting the DDW365 on page 9
 Connecting Devices to the Network on page 10
 Troubleshooting the Installation on page 12
2.1 Setting Up and Connecting the DDW365

Use the following instructions to set up and connect the DDW365. When the device is set
up and connected, refer to Accessing the Web User Interface Locally on page 13 to
configure the device.
Important: Subscribers contact your service provider to enable Internet access and
wireless networking.
Typically, the service provider initially configures and connects the device. The installation
steps are provided below if you wish to confirm the setup, or add devices to your network.
Refer to Connecting Devices to the Network on page 10.
Steps
To set up the device:
1. Remove the contents from the device packaging.
2. Place the DDW365 in the best location to connect to other devices, such as PCs or
gaming consoles.
 Place the wireless cable modem and wireless clients in open areas far away from
transformers, heavy-duty motors, microwave ovens, refrigerators, fluorescent
lights, and other manufacturing equipment. These items can impact wireless
signals. A wireless signal can become weaker after it has passed through metal,
concrete, brick, walls, or floors.
 Place the device in a location that has an operating temperature of 0˚ C to
40˚ C (32˚ F to 104˚ F). Refer to Understanding Safety and Regulatory Information
on page 1 for more safety information.
3. Power on your PC. The PC must have an Ethernet network adapter or Ethernet port
and an Internet browser installed, such as Netscape or Internet Explorer. The following
browsers are supported:
 For Windows 2000, XP, Vista, Windows 8, Windows 7, Google Chrome, Firefox
1.07 and higher, Internet Explorer v7 and above, Netscape.
Ubee Interactive Connecting Devices to the Network
 For MAC OS X, 10.2, and higher: Firefox 1.07 and higher, Safari 1.x and higher.
4. Connect the power cable included in the product package to the back of the cable
modem and plug the other end into the power outlet.
5. Connect the network cable included in the product package to your computer’s
Ethernet port. Connect the other end to the ETH1, ETH2, ETH3, or ETH4 port to the
cable modem.
6. Connect a coaxial cable from the CABLE port on the back of the device to the cable
wall outlet, or to a cable splitter connected to the wall outlet.
7. Validate the network connection using the device LEDs to confirm operations.
 The WiFi LED must be flashing or solidly lit.
 The PWR, US/DS, and ONLINE LEDs are solidly lit.
Refer to Understanding LED Behavior on page 5 for more information.
2.2 Connecting Devices to the Network

Use the instructions below to connect network devices and validate device functionality.
Topics
 Connecting an Ethernet Device on page 10
 Connecting a Wireless Device on page 11
2.2.1 Connecting an Ethernet Device

You can connect up to three additional Ethernet devices to the DDW365.
Steps
To connect another Ethernet device to the network:
1. Connect the Ethernet cable from the Ethernet device (for example, a PC or gaming
console) to an open Ethernet port on the back of the DDW365.
2. Use the device LEDs to confirm operations. Refer to Understanding LED Behavior on
page 5 for more information.
3. Open a Web browser and go to any Web site to validate network/Internet connectivity
(for example, http://www.wikipedia.org).
4. If the connected device is a gaming console, perform any online task supported by the
console (for example, log into the gaming server, play an online game, download
content).
Ubee Interactive Connecting Devices to the Network
Note
Refer to Troubleshooting the Installation on page 12 for troubleshooting information.
2.2.2 Connecting a Wireless Device

Use the following steps to connect a wireless device to the cable modem (for example, a
laptop computer).
Default values are shown in the steps below. Some regions may change default values
using the cable modem or XML configuration file.
Steps
To connect a wireless device to the cable modem:
1. Access the wireless networking feature on your wireless device. On a Windows
computer, for example, double-click the Wireless Network Connection icon in the
system tray (lower-right side of the Windows desktop).
2. Click View Wireless Networks. The device is shipped with a default SSID. The SSID
is the name of the wireless network broadcast from the device so that wireless clients
can connect to it.
 Double-click your SSID in the wireless networks window. The default SSID is
“DDW365” plus a period, plus the last 6 characters of the MAC address plus “-
2.4G”.
Example for modem with MACID 08:3E:8E:44:28:02:
SSID: DDW365.442802-2.4G
Notes: You can find the MAC address on the device label or by opening an Internet
browser window to the device. Refer to Using the Software Option on page 17 for
instructions. If the subscriber changes the SSID, the device does not revert to this
default SSID upon any reset of the device, except in the case of a manual reset using
the device’s Web UI. See Using the Account Option on page 21.
When prompted, enter the network key, also called the pre-shared key. This is a
unique key for each device. The pre-shared key for the DDW365 is the last 13
characters of the modem’s serial number. Refer to Using the Primary Network Option
on page 74.
Example pre-shared key: B7Y3R11000049

 If using WPS, enter the WPS personal identification number (PIN). The WPS PIN
is a randomly-generated number found on the Wireless Primary Network screen.
Refer to Using the Primary Network Option on page 74.
 WPA-WPA2 TKIP+AES is the default encryption method.
Ubee Interactive Troubleshooting the Installation
3. Confirm connectivity by opening a Web browser and going to any Web site
(for example, http://www.wikipedia.org) or access the Web interface for the DDW365.
Note
The Web interface allows you to customize the configurations and capabilities for the
device. For a full explanation of all Web interface functions, refer to Using the Web
User Interface on page 13.
If you have wireless issues or questions, refer to Deploying and Troubleshooting the
Wireless Network on page 90.
2.3 Troubleshooting the Installation

Use the following tips to troubleshoot the installation.
 None of the LEDs are on when I power on the DDW365.
 Check the connection between the power outlet and the power cord. Verify the
power outlet is energized and the power cord is connected to the power outlet.
 Check the connection between the power cord and the cable modem. Power off
the cable modem and wait for 5 seconds and power on the modem again. If the
problem still exists, there may be a hardware problem.
 The ETH1, ETH2, ETH3, or ETH4 LEDs on the back of the modem are not lit
where Ethernet cables are connected.
 Restart the computer so that it can re-establish a connection with the cable
modem.
 Check for a resource conflict (Windows users only):
1. Right-click My Computer on your desktop and choose Properties.
2. Choose the Device Manager tab and look for a yellow exclamation point or red X over the
network interface card (NIC) in the Network Adapters field. If you see either one, you may
have an interrupt request (IRQ) conflict. Refer to the manufacturer’s documentation or ask
your service provider for further assistance.
 Verify that TCP/IP is the default protocol for your network interface card.
 Power cycle the cable modem by removing the power cord from the electrical
outlet and plugging it back in. Wait for the cable modem to re-establish
communications with your cable service provider.
 Check General Connectivity Issues:
 If your PC is connected to a hub or gateway, connect the PC directly into an
Ethernet port on the cable modem.
 If you are using a cable splitter, remove the splitter and connect the cable modem
directly to the cable wall outlet. Wait for the cable modem to re-establish
communications with the cable service provider.
 Try a different cable. The Ethernet cable may be damaged.
 If none of these suggestions work, contact your service provider’s tier II support for
further assistance.
3 Using the Web User Interface
The Web user interface (UI) for the DDW365 is easy to use and allows you to view and
configure several settings for your wireless gateway device. You can validate the
installation by accessing the Web user interface on the device.
Topics
 Accessing the Web User Interface Locally on page 13
 Accessing the Web User Interface Remotely on page 15
 Accessing Telnet Remotely on page 15
 Password of the Day Tool (PoTD) on page 16
3.1 Accessing the Web User Interface Locally

Access the Web user interface for the DDW365 from a Web browser, such as Internet
Explorer on a Windows computer.
Default values are shown in the steps below. Some regions may change default values
using the cable modem or XML configuration file. Check with your provisioning team to
determine the default values for your region.
Steps
To access the Web user interface:
1. Launch an Internet browser, such as Internet Explorer, from your computer.
2. Enter the following IP address in the address bar of the browser window and press the
Enter key.
http://192.168.100.1
3. Enter the username and password in the authentication dialog box.

 Standard User Web Interface Login:
Username: user
Password: user
Ubee Interactive Accessing the Web User Interface Locally
 MSO Web Interface Login:

Username = admin
Password = cableroot
The Status screen displays software information about the DDW365.
Ubee Interactive Accessing the Web User Interface Remotely
3.2 Accessing the Web User Interface Remotely

The DDW365 web user interface can also be accessed remotely. The MSO must obtain
the Cable-RF IP address (for the specific cable modem) from the provisioning system for
access. Remote web access is disabled by default, but can be enabled using the Ubee
remote web access MIB.
Steps
To remotely access the web user interface:
1. Launch an Internet browser, such as Internet Explorer, from your computer.
2. Enter the following IP address in the address bar of the browser window and press the
Enter key.
http://Cable-RF-IP-address
(the service provider should have this information in the provisioning system)
3. Enter the username and password in the authentication dialog box.

 Standard User Web Interface Login:
Username: user
Password: user
 MSO Web Interface Login:
Username: admin
Password: cableroot
3.3 Accessing Telnet Remotely

The MSO must obtain the Cable-RF IP address (for the specific cable modem) from the
provisioning system to use for remote Telnet access. Refer to Understanding the Telnet
Command Line Interface on page 246 for more information.
Steps
To remotely access the Telnet interface:
1. Open a command or other terminal window.
2. Enter the following command:
telnet Cable-RF-IP-address
3. At the Telnet login prompt, enter:

Username: admin
Ubee Interactive Password of the Day Tool (PoTD)
Password: “password of the day.” Refer to the next section for information about the
password of the day (PoTD).
3.4 Password of the Day Tool (PoTD)

Run the application POTD.exe from a windows DOS command line. Field descriptions are
listed below the screen example.
Label Description
Seed Enter the passphrase in the Seed field. For Cox

Communications, the passphrase is coxcablemodem.
Use Default Seed Do not use the default seed for Cox Communications, use the
passphrase coxcablemodem.
Start Date If you want a PoTD for more than one day, enter the desired
start date in this field.
End Date If you want a PoTD for more than one day, enter the desired
end date in this field.
Default Date The default date is set to 1/1/2003.
Today To retrieve today’s PoTD only, click Today. The Start and End
Date fields will reflect the current date.
Generate PoTD Generates the desired PoTD(s).
Encrypt Seed Displays the encrypted seed.
The Password of the Day can then be copied and pasted into the Password field at the
Telnet prompt.
4 Understanding the Status Menu
The Status menu of the Web user interface allows you to access information about the
modem, such as software, connection (downstream and upstream), diagnostics, and
event log.
Topics
 Using the Software Option on page 17
 Using the Connection Option on page 18
 Using the Account Option on page 21
 Using the Diagnostics Option on page 22
 Using the Event Log Option on page 24
 Using the Factory Default Option on page 25
Steps
To access status options:
1. Access the Web user interface. Refer to Accessing the Web User Interface Locally on
page 13.
2. Click Status from the main menu.
4.1 Using the Software Option

The Software option displays the device’s internal software and hardware configuration.
Steps
To view software information:
2. Click Software from the left side menu. Field descriptions are listed below the screen
example.
Ubee Interactive Using the Connection Option
Label Description
Information
Standard Specification Compliant Defines the current DOCSIS standard of the device.
Hardware Version Defines the internal version number that identifies the
hardware design.
Software Version Defines the general software version of the device.
Cable Modem MAC Address Defines the unique media access control (MAC) hardware
address of the cable modem.
Cable Modem Serial Number Defines the unique manufacturer serial number of the device.
CM certificate Indicates if the cable modem certificate is installed.
Status
System Up Time Displays how long the device has been connected.
Network Access Defines if network access is enabled. When enabled, the

user is allowed to access the network.
Cable Modem IP Address Displays the IP address for the cable modem.
4.2 Using the Connection Option

The Connection screen displays information about the device’s connection status and
downstream and upstream channel bonding statistics.
 Downstream displays detailed information on the network traffic from the service
provider to the local computer (downstream channels).
 Upstream displays detailed information on the network traffic from the computer
to the remote destination (upstream channels).
Steps
To view connection information:
2. Click Connection from the left side menu. Field descriptions are listed below the
screen example.
Label Description
Startup Procedure (Procedure, Status, Comment)
Acquire Downstream Channel Displays the Downstream channel status and if the modem
has locked to a channel.
Connectivity State Displays connection status and if the modem is operational.
Boot State Displays the status on boot up and if the modem is

operational.
Configuration File Provides the status and file name of the configuration file
currently used by the modem.
Security Displays the status of the security settings: enabled/disabled.
Downstream Bonded Channels
Channel Numbers the downstream channels.
Lock Status Displays if the cable modem is locked successfully to a

downstream channel.
Modulation Displays the modulation method required for the downstream

channel to lock on to by the cable modem. This method is
determined by the service provider.
Channel ID Displays the downstream channel ID.
Frequency Displays the downstream channel frequency on which the

cable modem is scanning.
Power Level Displays the receiver power level in decibel millivolts (dBmV)
after ranging process.
SNR Displays the signal-to-noise ratio, the desired signal level to

the background noise level.
Correctables Displays the quantity of codewords which are correctable.
Uncorrectables Displays the quantity of codewords which are not correctable.
Upstream Bonded Channels
Channel Numbers the upstream channels.
Lock Status Displays if the cable modem succeeded in locking to an

upstream channel.
US Channel Type Displays the channel type.
Channel ID Displays the current cable modem upstream channel ID.
Symbol Rate Displays the symbol rate in 1000 symbols per second.
Frequency Displays the current cable modem upstream frequency in

hertz.
Power Displays the current cable modem upstream transmit power in

decibel millivolts (dBmV).
Ubee Interactive Using the Account Option
Label Description
CM IP Address Displays the cable modem’s IP address.
Duration Displays the time the modem has been active.
Expires Displays when the cable modem’s certificate expires.
4.3 Using the Account Option

Use the Account option to change the Admin password and the User username and
passwords.
Steps
To reset the modem’s usernames and passwords:
2. Click Account from the left side menu. Field descriptions are listed below the screen
example.
Label Description
Admin
New Password Enter the new Admin password.
Confirm Password Confirm the new Admin password.
User
New Username Enter the new User username.
New Password Enter the new User password.
Confirm Password Confirm the new User password.
Apply Saves the changes.
Ubee Interactive Using the Diagnostics Option
4.4 Using the Diagnostics Option

Use the Diagnostics option to test network connectivity. Two utilities are available: Ping
and Traceroute.
Topics
 Using the Ping Option on page 22
 Using the Traceroute Option on page 23
4.4.1 Using the Ping Option

Use the Ping utility to test network connectivity between devices by sending a test
message to a specific device. You can also confirm the size of data sent is the same as
the size of data received.
Steps
To test connectivity between devices:
1. Click Status from main menu.
1. Click Diagnostics from the left side menu.
2. Choose Ping from the Utility drop-down menu.
3. Enter new parameter values or accept the default values.
4. Click Start Test. Field descriptions are listed below the screen example.
Ubee Interactive Using the Diagnostics Option
Label Description
Utility Provides a drop-down menu to choose Ping or Traceroute.
Ping Test Parameters
Target Defines the IP address to which you want to send a ping.
Ping Size Defines the packet size (bytes of data) to send for the ping
operation. Default is 64.
No. of Pings Defines the number of ping commands to send to the ping
target. Default is 3 pings.
Ping Interval Defines the interval between ping operations in milliseconds.
Start Test Defines what action to take.

Abort Test  Start Test begins the ping.
Clear Results  Abort Test stops the ping.
 Clear Results deletes previous test results in the Results
table.
Results Displays the results of the ping test.
4.4.2 Using the Traceroute Option

The Traceroute utility determines the IP addresses of hosts in the network path. By
checking the Resolve Host names box, Traceroute tries to find which name matches the
address. Some hosts have no names, and might still be shown as IP addresses, even if
this option is active.
Steps
To trace host IP addresses along a route:
1. Click Status from main menu.
2. Click Diagnostics from the left side menu.
3. Choose Traceroute from the Utility drop-down menu.
4. Enter new parameter values or accept the default values.
5. Click Start Test. Field descriptions are listed below the screen example.
Ubee Interactive Using the Event Log Option
Utility Provides a drop-down menu to choose Ping or Traceroute.
Traceroute Parameters
Target Defines the specific IP address or domain (for example,

ubeeinteractive.com) to which you want to trace a route.
Max Hops Defines the maximum number of hops. Hops are the number
of routers the traceroute traverses. Default is 30.
Data Size Defines the data size to send for the traceroute operation.
Default is 64.
Base Port Defines the destination port number. Default is 33434.
Resolve Host Enable (on) or disables (off) this option. When checked,
traceroute tries to find the name that matches the IP address.
Default is Off.
Start Test/Clear Results Defines what you want to do.

 Start Test begins the ping.
 Clear Results deletes previous test results in the Results
table.
Results Displays the results of the trace.
4.5 Using the Event Log Option

The Event Log screen displays log information that may be useful to diagnose
operational issues with the device.
Ubee Interactive Using the Factory Default Option
Steps
To view event log information:
2. Click Event Log from the left side menu. Field descriptions are listed below the screen
example.
Label Description
Time Displays the time the event started.
Priority Displays the event log severity.
Description Displays a detailed description of the event log.
Clear Log Removes the contents of the log when Clear Log is clicked.
4.6 Using the Factory Default Option

The Factory Default option allows you to restore the modem to the factory default values.
Steps
To restore factory defaults:
2. Click Factory Default from the left side menu. Field descriptions are listed below the
screen example.
Ubee Interactive Using the Factory Default Option
Label Description
Restore Factory Defaults Restores settings to factory defaults. Select Yes to have the
device reset all configured options in the device to factory
default settings. The device reboots if Reset The System is
also selected.
Restore User Factory Defaults Restores settings to factory defaults. Select Yes to restore the
device to default settings for the firewall and content filter
settings. This operation does not require a reset of the system.
Reset The System Resets the system. Select Yes to power cycle the device.
Apply Applies the options selected on this screen.
5 Understanding the Basic Menu
Basic gateway options provide the majority of configuration for the device including WAN
IP addresses, LAN IP addresses, and DHCP. Advanced gateway options provide settings
like MAC filtering and port forwarding.
Topics
 Using the Setup Option on page 27
 Using the DHCP Option on page 29
 Using the DDNS Option on page 31
 Using the Backup Option on page 32
Steps
To access the basic menu:
page 13.
2. Click Basic from the main menu.
5.1 Using the Setup Option

Use the Setup option to configure common gateway parameters.
Steps
To configure setup options:
2. Click Setup from the left side menu. Field descriptions are listed below the screen
example.
Ubee Interactive Using the Setup Option
Label Description
LAN
IP Address Defines the local IP address, which is the default gateway

address for all wired LAN hosts that connect to the DDW365.
MAC Address Displays the LAN interface’s hardware address.
Interface/Prefix
None Specified Indicates no interface or prefix has been specified.
WAN
IP Address Displays the current WAN public IP address obtained from the
service provider.
MAC Address Displays the WAN interface’s hardware address.
Duration Displays the accumulated time since successfully acquiring a

WAN public IP address.
Expires Displays the remaining time before the WAN IP address

expires, if applicable.
IPv4 DNS Servers Lists the DNS servers available on the network.
Release WAN Lease Releases the WAN public IP address when clicked.
Renew WAN Lease Renews the WAN IP address when clicked.
Ubee Interactive Using the DHCP Option
Label Description
WAN Connection Type Selects the WAN connection type. For each type, different data
entry is required, as explained below:
 DHCP: The WAN interface is set to a DHCP client, and
the IP address is assigned by the service provider’s DHCP
server.
 Static IP: For Static IP, you must manually enter the IP
address for the WAN interface.
 PPTP (dhcp): For Point to Point Tunneling Protocol
(PPTP), you must enter a username, password, and the
PPTP server’s IP address.
 PPTP (static):
 L2TP (dhcp):
 L2TP (static):
Host Name Defines the host name for the router. This may be required by
some service providers.
Domain Name Defines the domain for the router. This may be required by
some service providers.
IPv4 MTU Size Defines the maximum transmission unit (MTU) size. MTU
defines the largest size of the packet or frame that the device
can transfer (256-1500). If this is not given by your service
provider, use 0 for the default.
Spoofed MAC Address You can give a spoofed MAC address to hide your modem’s
real MAC address. This is not recommended, as this could
cause an address conflict, causing your connection to the
network to be rejected.
Apply Saves changes.
5.2 Using the DHCP Option

Use the DHCP option to configure dynamic host configuration protocol-specific behavior
on the device.
Steps
To configure DHCP settings:
2. Click DHCP from the left side menu. Field descriptions are listed below the screen
example.
Ubee Interactive Using the DHCP Option
Label Description
DHCP Server Enables (Yes) or disables (No) DHCP on the device. If No is

selected, all the static DHCP rules in this screen are ignored.
Starting Address Set
Private Starting Address Defines the starting private IP address for the pool of IP
addresses that can be used by connecting clients. Private
addresses are translated to public IPs to be used on the
network.
Public Starting Address Defines the starting public IP address. Public addresses can
be recognized on the network.
Number of CPEs Defines the maximum number of customer premises

equipment devices (CPE) that can connect to the network
through the DDW365.
Lease Time Defines the DHCP lease time duration in minutes between 1
and 71582788. A DHCP user's PC gets an IP address with a
lease time. When the lease time expires, the PC must connect
to the DHCP server and be issued a new unused IP address.
Note: The default DHCP lease time is 3600 seconds and
should be changed to 86400 seconds (24 hours). This helps
resolve connectivity issues with some iMAC and Windows 7
devices that turn off the network interface when they go into
standby mode. This results in slow Web browsing until the
device gets a new IP address via DHCP.
Ubee Interactive Using the DDNS Option
Label Description
DHCP Clients Lists all DHCP clients currently connected to the device, either
via an Ethernet link, or via a wireless connection. Each client
is listed with the following information:
 MAC Address / IP Address / Subnet Mask
 Duration: Duration displays the accumulated time since
the client acquired the IP address.
 Expires: Expires is the time until the IP expires and must
be recycled. If the IP address is reserved to a certain
host, it shows STATIC IP ADDRESS.
 Select: Reserves the current private IP address to be
assigned to this host statically when selected.
Current System Time Displays the current system time.
Force Available Activates a selected rule in the DHCP Clients list and assigns
IP addresses. Note: The Select button must be activated in the
DHCP list.
5.3 Using the DDNS Option

Use the dynamic domain name system (DDNS) to assign a changing IP address to a
constant pre-defined host name. The host can then be contacted by other hosts on the
Internet, even if its IP address changes.
The DDNS service for the DDW365 is provided through a third-party and can be
purchased from Dynamic Network Services Inc. at www.dynDNS.com.
Steps
To use the DDNS option:
2. Click DDNS from the left side menu. Field descriptions are listed below the screen
example.
Ubee Interactive Using the Backup Option
Label Description
DDNS Service Enables or disables the DDNS service. When enabled, this
service is available from www.dynDNS.org.
User Name Defines the user name for the DDNS account.
Password Defines the password for the DDNS account.
Host Name Defines the host name for the DDNS account.
IP Address Displays the IP address for the DDNS account.
Status Displays if the DDNS service is enabled or disabled.
5.4 Using the Backup Option

The Backup option lets you backup your gateway configuration or restore the modem to a
previously saved configuration.
Steps
To use the backup option:
2. Click Backup from the left side menu.
5.4.1 Backing Up the Current Modem Configuration

To backup and save the current modem configuration, click the Backup button.
A pop-up window appears instructing you to select ‘Save’ when prompted. Click ‘OK’.
The following window appears, giving you the option to save the file. Click the ‘Save File’
option and click ‘OK’.
The file will be saved to your Downloads folder as a binary file (.bin) titled
‘GatewaySettings.bin.’
5.4.2 Restoring the Modem to a Previously Saved Configuration

To restore the modem to a previously saved configuration, click the Browse button.
The File Upload dialog box appears and allows you to select the previously saved backup
file. Highlight the file and click ‘Open’.
The location for the backed up file appears in the box to the left of the Browse button.
Click the Restore button.
You are advised that you will be required to reboot the modem. Click ‘OK’.
You are then notified that the device has been reset. Click ‘RELOAD’.
You are then presented with the login screen for the modem. Enter the Username and
Password to return to the modem User Interface.
6 Understanding the Advanced Menu
Advanced options provide settings to configure your gateway, such as MAC filtering and
port forwarding.
Topics
 Using the Options Option on page 36
 Using the IP Filtering Option on page 39
 Using the MAC Filtering Option on page 40
 Using the Port Filtering Option on page 41
 Using the Forwarding Option on page 43
 Using the Port Triggers Option on page 47
 Using the Pass Through Option on page 49
 Using the DMZ Host Option on page 50
Steps
To access the advanced menu:
page 13.
2. Click Advanced from the main menu.
6.1 Using the Options Option

Use the Options option to define which networking protocols are enabled or disabled on
the device. The network address translation application-level gateway (NAT ALG) settings
provide additional security beyond the firewall.
Steps
To enable or disable network protocols:
2. Click Options from the left side menu. Field descriptions are listed below the screen
example.
Ubee Interactive Using the Options Option
Label Description
WAN Blocking Blocks connection requests initialized from Internet users

when enabled. WAN Blocking must be disabled to be able to
PING the WAN gateway IP.
Ipsec PassThrough Forces the router to redirect the IPSec request to the local
host when enabled. NAT fails this attempt if Internet users
initialize an IPSec VPN request to a host located behind the
router.
PPTP PassThrough Forces the router to redirect the PPTP request to the local host
when enabled. NAT fails this attempt if Internet users initialize
a PPTP VPN request to a host located behind the router.
Remote Config Management Enables or disables access to the device from a remote
system in order to configure settings. Remote management
can be achieved by using SNMP, web/HTTP or telnet.
Multicast Enable Optimizes the bandwidth utilization compared with unicast

(especially video streaming applications).
Ubee Interactive Using the Options Option
Label Description
UPnP Enable Activates Universal Plug and Play (UPnP) when enabled. A
UPnP device can dynamically join a network, obtain an IP
address, convey its capabilities, and learn about other devices
on the network. In turn, a device can leave a network smoothly
and automatically when it is no longer in use. Gaming
consoles and Web cameras are examples of devices that can
use UPnP.
Primary Network Bridged When enabled, all wireless traffic sourced from the primary
SSID will be bridged.
NAT ALG Status – Filters to allow (enable) or disallow (disable) protocols to pass through the
DDW365 to connected devices (computers, game consoles, and so on).
RSVP Enables or disables resource reservation protocol (RSVP).

RSVP defines how applications reserve resources and how
they free the reserved resources once they are no longer
needed.
FTP Enables or disables the file transfer protocol (FTP) used to

transfer files from one host to another.
TFTP Enables or disables the trivial file transfer protocol (TFTP) – a

simpler protocol generally used for automated file transfers.
Kerb88 Enables or disables the Kerberos network authentication

protocol which allow nodes to communicate over a non-secure
network using “tickets” on port 88 to prove their identity to one
another.
NetBios Enables or disables the network basic input/output system

(NetBIOS) services related to the OSI session layer. NetBIOS
allows applications on separate computers to communicate
over a LAN.
IKE Enables or disables the network key exchange (IKE) protocol

used to set up a security association (SA) in the IPsec protocol
suite.
RTSP Enables or disables the real time streaming protocol (RTSP)

network control protocol used to establish and control media
sessions between end points.
Kerb1293 Enables or disables the Kerberos network authentication

protocol which allows nodes to communicate over a non-
secure network using “tickets” on port 1293.
H225 Enables or disables the H.225 protocol used to define

messages and procedures for call signalling, media
packetization, and registration, admission, and status (RAS)
functions.
PPTP Enables or disables the point-to-point tunneling protocol

(PPTP) used to implement a virtual private network.
MSN Enables or disables the Microsoft network protocol used for

instant messaging.
Ubee Interactive Using the IP Filtering Option
Label Description
SIP Enables or disables the session initiation protocol application

layer gateway (SIP ALG). SIP ALG inspects protocol
packets and formats SIP message headers and SDP
body to ensure proper signaling. Note: Some hosted VoIP
services prefer this function to be performed by their own
session border controller (SBC) and require the SIP ALG to be
disabled. Some IP-PBXs may require SIP ALG enabled.
ICQ Enables or disables the ICQ instant messaging program.
IRC666x Enables or disables the Internet relay chat (IRC) protocol used
for text messaging.
ICQTalk Enables or disables the ICQTalk instant messaging program.
Net2Phone Enables or disables Net2Phone SIP- and PacketCable-based

VoIP.
IRC7000 Enables or disables the Internet relay chat protocol on TCP

port TCP 7000 used for text messaging and group forums.
IRC8000 Enables or disables the Internet relay chat protocol on UDP

port 8000 used for text messaging and group forums.
6.2 Using the IP Filtering Option

Use the IP Filtering option to filter IP addresses to block Internet traffic to specific
network devices on the LAN. Any host on this list is not accessible to Internet traffic.
Note
You may also filter by the MAC address which does not require setting a static lease.
Refer to Using the MAC Filtering Option on page 40.
Steps
To filter IP addresses:
1. Make sure a PC is connected to the cable modem and both devices are powered on
and functioning.
2. Log in to the cable modem’s Web user interface. Refer to Accessing the Web User
Interface Locally on page 13.
4. Click IP Filtering from the left side menu. Field descriptions are listed below the
screen example.
Ubee Interactive Using the MAC Filtering Option
Label Description
Start Address Defines the starting IP address to block.
End Address Defines the ending IP address to block.
Enabled Activates the rule when enabled is checked.
6.3 Using the MAC Filtering Option

The MAC Filtering option allows you to filter MAC addresses to block Internet traffic from
specific network devices on the LAN. MAC filtering establishes a list and any host on this
list is not able to access the network through the DDW365.
Steps
To filter MAC addresses:
1. Note the MAC address of the devices that you want to deny Internet access.
Be sure all devices to which you potentially deny Internet access are connected to the
DDW365 network.
3. Click MAC Filtering from the left side menu.
4. Enter the MAC address to block in the text box to the left of the Add MAC Address
button.
Ubee Interactive Using the Port Filtering Option
5. Click the Add MAC Address button. The MAC address is displayed in the filtered
MAC address list. Field descriptions are listed below the screen example.
Label Description
MAC Addresses Defines the MAC address to block. Enter the MAC address in
the field.
Add MAC Address Adds the MAC address to the list of addresses to block.
Addresses entered: n/20 Displays the MAC addresses to be blocked. The number of
MAC addresses entered is shown as 1/20 where 1 is the
number of addresses in the list. You can filter up to twenty
MAC addresses at one time.
Remove MAC Address Deletes the selected MAC address from the list of addresses
to be blocked.
Clear All Removes all MAC addresses from the list.
6.4 Using the Port Filtering Option

Use the Port Filtering option to configure port filters to block to all devices on the LAN
Internet services that use the ports specified.
Steps
To configure port filters:
2. Click Port Filtering from the left side menu. Field descriptions are listed below the
screen example.
Ubee Interactive Using the Port Filtering Option
For example:
To prevent all Telnet access into and across your LAN:

1. Enter the Start and End ports to be 23.
2. Select Both for Protocol to include TCP and UDP.
3. Check Enabled.
4. Click Apply. Field descriptions are listed below the screen example.
Caution
Use caution when assigning port filtering by port range. You may accidentally prevent
traffic that should pass through your network, such as http or email. Pre-assigned
application ports are displayed on the Forwarding screen. Refer to Using the Forwarding
Option on page 43.
edffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff.l
Label Description
Start Port Defines the starting port number
End Port Defines the ending port number.
Protocol Selects the protocol type. Options are UDP, TCP, or Both.
Enabled Activates the rule and filters out all traffic on the specified
ports.
Ubee Interactive Using the Forwarding Option
6.5 Using the Forwarding Option

Forwarding tells the cable modem to which computer on the local area network to send
data. If your host systems or applications have communications issues with the Internet,
you can use forwarding to resolve the following issues:
 Data is sent from a local host to the Internet, but the return path of expected data is
not received by your local host.
 An application or service running on your local network (on local host) cannot be
accessed from the Internet directly (for example, a request to a local audio server).
Examples are:
 Xbox/PlayStation – Games/applications
 Home Security Systems – Security systems that use the Internet
 Audio Servers/VoIP – Audio and VoIP applications and services
Topics
 Before Setting Up Forwarding on page 43
 Setting Up Forwarding on page 44
 Setting Up Forwarding for an Xbox Example on page 46
6.5.1 Before Setting Up Forwarding

Try the following options before you assign forwarding rules:
1. Enable Universal Plug and Play (UPnP). This may resolve the issue you have without
setting up forwarding rules.
a. Access the Web interface of the cable modem, see Accessing the Web User
Interface Locally on page 13.
b. Click Advanced from the main menu.
c. Click Options from the left menu.
d. Check the Enable UPnP box
.
e. Click Apply.
f. Test your local host or application such as your Xbox to see if it is functioning
properly. Continue with port forwarding if the host or application is not
communicating correctly.
2. Assign a Static IP lease to the client/host to which you are setting up forwarding. This
way, the IP does not change and disrupt your forwarding rules. For example, if you are
hosting a Web server in your internal network, and you wish to setup a forwarding rule
for it, assign a static IP lease to that system to keep the IP from renewing and
disrupting the forwarding rule.
6.5.2 Setting Up Forwarding

If the suggestions in Before Setting Up Forwarding on page 43 did not correct your
communication problem, use port forwarding.
You need the following information to set up port forwarding:
 IP address of each local host system (for example, Xbox) for which you need to setup
a port forwarding rule.
 Port numbers the local host’s application listens to for incoming requests/data (for
example, a game or other service). These port numbers should be available in the
documentation associated with the application.
Note
For detailed information on port forwarding, including how to set it up for specific
applications using specific network devices (for example, cable modems), refer to:
http://portforward.com or consult your host device or application user manual.
Steps
To set up forwarding:
1. Access the Web interface of the cable modem, see Accessing the Web User Interface
Locally on page 13.
3. Click Forwarding from the left menu.
4. Click Create IPv4 and enter information in the forwarding fields as shown in the
screenshot below. Field descriptions follow.
Label Description
Local IP Defines the IP address of the local LAN device to which the
forwarding rule applies. For example, an Xbox or PC.
Local Start Port Defines the starting port number listened to by the server host
located in your LAN.
Local End Port Defines the ending port number listened to by the server host
located in your LAN.
External IP Designates the IP address of another router on the network

through which to forward data.
External Start Port Defines the port number to start the range of ports to publish
to the Internet.
External End Port Defines the port number to end the range of ports published to
Internet.
Note: Be very careful with ranges. Ports within a range are not
usable by other applications that may require them. It is
common and safer to enter the same port number as the start
and end of the range.
Protocol Selects the protocol type. Options are UDP, TCP, or BOTH.
Description Names the forwarding rule.
Enabled Disables (Off) or enables (On) the forwarding rule.
Cancel Stops creating the forwarding rule and returns you to the
previous Forwarding screen.
Port Map Shows a list of common applications and their ports.
Forwarding Table – Lists existing forwarding rules.
Remove All Deletes all entries in the forwarding table.
Remove Deletes the rule selected.
5. Click Apply. The forwarding rule is created and displayed in the table as shown
below. Additional field descriptions follow.
Label Description
Edit Displays fields for the rule selected in order to change values.
Remove Deletes the rule selected.
6.5.3 Setting Up Forwarding for an Xbox Example

Following is an example of how you would set up a single Xbox running Modern
Warfare 2. Since multiple ports are used for the Xbox and the Modern Warfare 2 game, a
separate forwarding rule is set for each port. Multiple ports and forwarding rules may not
be required for other applications.
Steps
To set up port forwarding for an Xbox:
2. Click Forwarding from the left side menu.
3. Enter the Xbox IP address in the Local IP field.
4. Define ports used by the Xbox in the Local Start Port and Local End Port fields.
Define the same ports used by the Xbox in the External Start Port and External End
Port fields.
Ubee Interactive Using the Port Triggers Option
5. Create Port Forwarding rules per port. A rule set up for port 53 works for port 53. A
port can be used only by one program at a time.
Note
You can set up applications/services to listen on one internal port. External Internet
users who want to access that application, address it using an external port, such as
an Audio server. Internal Ports are the ports to which local servers listen. External
Ports are the ports that the cable modem listens to from the WAN.
6.6 Using the Port Triggers Option

Port Triggers define dynamic triggers to specific devices on the LAN. This allows special
applications that require specific port numbers with bi-directional traffic to function
properly. Applications such as video conferencing, voice, gaming, and some messaging
program features may require these special settings.
Some services use a dedicated range of ports on the client side and a dedicated range of
ports on the server side. The difference between port forwarding and triggering is:
 Port forwarding sets a rule to send a service to a single LAN IP address.
 Port triggering defines two kinds of ports: trigger port and target port. The trigger
port sends a service request from a LAN host to a specific destination port number.
The port the LAN host is required to listen to by the application is called the target
port. The server returns responses to these ports.
For example:
1. John requests a file from the Real Audio server (port 7070). Port 7070 is a “trigger”
port and causes the device to record John’s computer IP address. The DDW365
associates John's computer IP address with the “target” port range of 6970-7170.
2. The Real Audio server responds to a port number ranging between 6970-7170.
3. The DDW365 forwards the traffic to John’s computer IP address.
Ubee Interactive Using the Port Triggers Option
4. Only John can connect to the Real Audio server until the connection is closed or
expires.
Steps
To set up port triggering:
2. Click Port Triggers from the left side menu.
3. Click Create and enter information in the trigger fields.
4. Click Apply. The port trigger rule is created and displayed in the table. Field
descriptions are listed below the screen example.
Note
The following example shows the Port Triggering option set up for a dual Xbox
configuration.
Ubee Interactive Using the Pass Through Option
Label Description
Trigger Start Port Defines a port number or the starting port number in a range
of port numbers.
Trigger End Port Defines a port number or the ending port number in a range of
port numbers.
Target Start Port Defines a port number or the starting port number in a range
of port numbers.
Target End Port Defines a port number or the ending port number in a range of
port numbers.
Protocol Defines the protocol type for this rule, UDP, TCP, or Both.
Description Names the triggering rule.
Enabled Enables (on) or disables (off) the triggering rule.
6.7 Using the Pass Through Option

Use the Pass Through option to configure a pass through table. Devices in the pass
through table are treated as bridge devices, storing and forwarding data between LAN
interconnections.
Steps
To configure a pass through table:
2. Click Pass Through from the left side menu. The pass through fields are explained
following this screen example.
Ubee Interactive Using the DMZ Host Option
Label Description
Pass Through MAC Addresses Defines the input host’s MAC address.
Add MAC Address Adds the input host’s MAC address.
Addresses entered: n/32 Displays the MAC addresses to be blocked. The number of
MAC addresses is shown as 0/32 where 0 is the number of
addresses in the list. You can add up to 32 MAC addresses at
one time.
Remove MAC Address Removes the input host’s MAC address.
Clear All Removes all of the input host’s MAC addresses.
6.8 Using the DMZ Host Option

Use the DMZ Host option to expose a host IP address to the WAN (public Internet). You
can use this option when applications do not work with port triggers or other networking
strategies.
Steps
To set up a DMZ host:
1. Connect a PC to an Ethernet port on the DDW365. Make sure both devices are
powered on and functioning.
2. Connect a Home Gateway (or other device you wish to be in the DMZ) to an Ethernet
port on the DDW365.
3. Log in to the DDW365 Web user interface.
5. Click DMZ Host from the left side menu.
6. Enter the IP address you just configured in the Static Lease section.
Ubee Interactive Using the DMZ Host Option
7. Test the device to ensure Internet access is available and the device is functional. For
example, connect to the Internet from a PC connected to the Home Gateway, or make
calls from a VoIP phone.
Label Description
DMZ Address Defines the IP address of the host to be exposed.
7 Understanding the Firewall Menu
Use these instructions to configure the DDW365 firewall settings to control what types of
traffic are allowed on your network. The firewall can block certain Web-oriented cookies,
java scripts, and pop-up windows. It is highly recommended the Firewall is left enabled at
all times to protect against denial of service (DoS) attacks. Refer to Using the Basic Option
on page 52 to block Internet access to specific sites.
Note: Firewall menu options are not available when the device is in Bridge mode.
Topics
 Using the Basic Option on page 52
 Using the Local Log Option on page 53
 Using the Remote Log Option on page 54
Steps
To access the firewall menu:
page 13.
2. Click Firewall from the main menu.
7.1 Using the Basic Option

Use the Basic option to filter Web content to block certain Web-oriented cookies, java
scripts, and pop-up windows.
Steps
To filter Web content:
2. Click Basic from the left side menu. Field descriptions are listed below the screen
example.
Ubee Interactive Using the Local Log Option
Label Description
IPv4 Firewall Protection Defines the level of protection. Choices are Off, Low, Medium,
and High. Services are based on the protection level and
displayed in the Allowed Services window.
Block Fragmented IP Packets Detects fragmented IP packets and blocks them.
Port Scan Detection Detects port scans that probe for available ports and
potentially use these ports to detect weakness in the network.
IP Flood Detection Detects IP flood attacks that send excessive information to the
device, using up bandwidth.
7.2 Using the Local Log Option

Use the Local Log to define firewall event log reporting through email alerts and report on
possible attacks on the system.
Steps
To define local log reporting:
2. Click Local Log from the left side menu. Field descriptions are listed below the screen
example.
Ubee Interactive Using the Remote Log Option
Label Description
Contact Email Address Defines the email address where you want to send the log.
SMTP Server Name Defines the name of the SMTP server, such as
smtp.example.com.
SMTP Username Defines the username for the email address, such as
contact@company.com.
SMTP Password Defines the password for the email address.
E-mail Alerts Enables or disables log reporting.
Apply Saves the settings and completes the setup.
E-mail Log Sends the log to the specified email address.
Clear Log Deletes the log.
7.3 Using the Remote Log Option

Use the Remote Log option to define events and send the log to a local SysLog server.
Steps
To configure the firewall remote log:
1. Click Firewall the main menu.
2. Click Remote Log from the left side menu. The Remote Log fields are explained
Ubee Interactive Using the Remote Log Option
Label Description
Permitted Connections Logs all access attempts that are allowed by the firewall.
Blocked Connections Logs all access attempts that are blocked by the firewall.
Known Internet Attacks Logs all known attacks from the Internet.
Product Configuration Events Logs when the DDW365 is configured/modified by a user or

administrator.
to SysLog server at 192.168.0. Defines the IP address of the Syslog server.
8 Understanding the Parental Control Menu
Parental Controls allow you to control Internet access for users on the DDW365 network.
Parental Controls provides the following features:
 Define user/password access.
 Block specific Web sites and Web sites based on keywords.
 Define the times users are allowed to access the Internet.
 View a local log to view Internet activity.
Topics
 Using the Parental Control User Setup Option on page 56
 Using the ToD Filter Option on page 60
 Using the Local Log Option on page 61
Steps
To access the parental control menu:
1. Access the Web interface. Refer to Accessing the Web User Interface Locally on page
13.
2. Click the Parental Control link from the top of the screen.
8.1 Using the Parental Control User Setup Option

The User Setup option allows you to configure which user accounts can or cannot
connect to your wireless or wired network, and the parameters of each connection.
Steps
To configure user accounts:
2. Click User Setup from the left side of the screen. The User Setup fields are explained
following the screen example.
Note: To enable Parental Control, refer to Using the Basic Option on page 58.
Ubee DDW365 Wireless Cable Modem Subscriber User Guide • September 2015 56
Ubee Interactive
Label Description
Add User Defines user accounts.

Remove User  To select an existing user, choose the user from the User
Enable Settings pop-up menu.
 To add a new user, add the user name and click Add.
 To activate the user, check Enable.
 To remove a user, select the user from the pop-up menu
and click Remove User.
Password Defines the password for this user. It is required when this
user tries to access the Internet via the device.
Re-Enter Password Confirms the password with the re-entered password.
Trusted User Defines the selected user as a trusted user when enabled is
checked. The user is limited to timing and content when
visiting the Internet, as defined in the following fields.
Content Rule Selects from the pop-up menu an existing content rule that
defines what kind of Websites the user can visit or not.
White List Access Only Selects the White List Access option. If you have created a
content rule that defines a black list and white list, select the
White List Access Only checkbox to force the wireless modem
to execute the policy for the selected user.
Time Access Rule Selects a defined time access rule to apply to the selected
user.
Ubee Interactive
Label Description
Session Duration Allows you to enter a time in minutes for the user’s session to
expire. When the session expires, the user can log in again for
the same session duration.
Inactivity Time Allows you to enter the time out value when a user has no
activity on the Internet. When the time expires, the user
interface to the Internet is cancelled.
Apply Saves all changes when clicked.
Trusted Computers Defines the trusted hosts that can bypass the Parental Control
Process.
Add Adds the trusted host’s MAC address entered in the given
area and Add is clicked.
Remove Removes a trusted computer from the list when it is

highlighted and Remove is clicked.

The Basic option allows you to select rules to block certain Internet content and Web
sites. After you change your Parental Control settings, click the appropriate Apply, Add, or
Remove button for your new settings to take effect. Refresh your browser’s display to see
the currently active settings.
Steps
To filter Internet content and Web sites:
2. Click Basic from the left side of the screen. The Basic fields are explained following
this screen example.
Ubee Interactive
Label Description
Enable Parental Control Activates the Parental Control feature when checked.
Apply Saves all changes in the screen and activates Parental

Control, if enabled.
Content Policy Configuration
Add New Policy Adds a policy to the Policy List. Enter the policy name and
click Add New Policy.
Content Policy List Lists existing policies you can choose to use.
Remove Policy Deletes a policy from the list. Select the policy from the list and
click Remove Policy.
Keyword List Displays keywords you can use to block Web site addresses
(URLs) containing those words.
Add Keyword Adds a keyword to the keyword list. Enter the word in the field
next to the Add Keyword button and click Add Keyword. The
keyword is added to the list.
Ubee Interactive
Label Description
Remove Keyword Removes a keyword from the keyword list. Select the keyword
from the list, and click Remove Keyword.
Blocked Domain List Displays Web domains (for example, unwanted.com) you can
use to block access to those domains.
Add Domain Adds a domain to the Allowed Domain List. Enter a domain,
and click Add Domain.
Remove Allowed Domain Removes a domain from the Allowed Domain List. Select the
domain from the list, and click Remove Domain.
Allowed Domain List Displays domains you can assign to users to visit only the
sites allowed.
Add Allowed Domain Adds allowed domains to the list. Enter the name and click
Add Allowed Domain.
Remove Allowed Domain Removes domain names from the list. Highlight the domain
from the list and click Remove Allowed Domain.
Override Password If you encounter a blocked website, you can override the block
by entering a password.
Password Enter a password for overriding blocked websites.
Re-Enter Password Re-enter the password.
Access Duration Set a time duration (in minutes) for access to the blocked site
when the block has been overridden by entering the password.
Apply Saves the password and access duration time.
8.3 Using the ToD Filter Option

The ToD (Time of Day) Filter option allows the configuration of time-based access
policies to block all Internet traffic at specified times.
Steps
To configure ToD filters:
2. Click ToD Filter from the left side of the screen. The ToD Filter fields are explained
Ubee Interactive
Label Description
Add New Policy Adds a new policy. Enter a policy name and click the Add New
Policy button.
Time Access Policy List Lists the existing policies in a drop-down list.
Enabled Activates a policy. Select the policy from the drop-down list
and check Enabled.
Remove Deletes a policy. Select the policy from the drop-down list and
click Remove.
Days to Block Selects the days to block Internet access.
Time to Block: Defines the time to block.

All Day or a specific time frame  To block all day, check All Day to eliminate all access
during the days selected.
 To block a specific time frame for the days selected, enter
the Start time and the End time. Select AM or PM for
each.
Ports to Block Defines a port range to block if the Enabled box is checked.
 Port Start: Enter the starting port number to be blocked.
 Port End: Enter ending port number to be blocked.
 Protocol: Select the protocol type. Options are UDP, TCP,
or Both.
Apply Saves all changes when clicked.
8.4 Using the Local Log Option

The Local Log option displays Parental Control event log reporting.
Ubee Interactive
Steps
To view the parental control local log:
2. Click Local Log from the left side of the screen. The Local Log fields are explained
Label Description
Last Occurrence Displays the time when the last event occurred.
Action Displays what is done by parental control, including dropping

or permitting access requests.
Target Displays the destination IP address of a certain access

request.
User Displays the user who triggered this event log.
Source Displays the source IP address of this event.
Clear Log To empty the displayed log entries, click Clear Log.
9 Understanding the VPN Menu
Use the VPN menu to configure a virtual private network (VPN) for the DDW365.
A VPN is a computer network that carries links between nodes by open connections over
the Internet or virtual circuits instead of by physical wires. A common use of a VPN is
when you want to connect to a computer at a remote location, such as from a branch
office to a corporate office to share private data.
 Internet Protocol Security (IPsec) – A standards-based protocol suite used to
secure IP communications. IPsec operates in the Internet layer (TCP/IP) to
authenticate and encrypt each IP packet in a communication session.
 VPN Tunnel – A way to transmit data through a public network intended for use in a
private network. Data is transmitted so that the routing points on the public network
are unaware the transmission is part of a private network.
A VPN tunnel is established in two phases:

 Phase One – Establish an Internet key exchange (IKE) security association (SA)
between the device and the remote IPsec router.
 Phase Two – Use the IKE SA to establish an IPsec SA through which the device
and the remote IPsec router can send data securely between computers on the
local and remote networks.
 SA – A security association is a contract that indicates what security parameters the
device and the remote IPSec router use for each phase. An SA is the foundation of an
IPsec VPN configuration.
 IPsec Algorithms – The AH and ESP protocols provide the authentication used to
create a security association. Once the SA is established, you can begin to transport
data securely.
 AH – The authentication header protocol (RFC 2402) is designed for integrity,
authentication, and resisting replays. In applications where confidentiality is not
required or not sanctioned by government encryption restrictions, an AH can be
used to ensure integrity. AH verifies information integrity and authenticates the
originator, but does not protect against dissemination.
 ESP – The encapsulating security payload protocol (RFC 2406) provides
encryption, as well as the services offered by AH. ESP authenticating properties
do not include IP header information during the authentication process, whereas
the AH protocol does. ESP is sufficient if only the upper layer protocols need to be
authenticated. ESP also features payload padding which conceals the size of the
packet being transmitted to further protect communications.
Topics
 Using the IPsec Option on page 65
Ubee Interactive Using the Basic Option
 Using the Event Log Option on page 70
Steps
To access the VPN menu:
13.
2. Click VPN from the main menu.

Use the Basic option to display an overview of the VPN settings. From this screen, you
can access configuration options for the selected tunnel.
Steps
To view a summary of VPN tunnels:
1. Click the VPN link from the top of the screen.
2. Click Basic from the left side menu. Field descriptions are listed below the screen
example.
Label Description
IPsec
IPsec Endpoint Enables or Disables Internet protocol security (IPsec) for the
VPN service.
# Displays an ID number for existing IPsec VPN tunnels.
Name Displays the name of the IPsec VPN tunnel.
Status Displays the status of the IPsec. Once an IPsec VPN connects
successfully, the Status is Connected. Otherwise, it is set to
NOT connected.
Ubee Interactive Using the IPsec Option
Control Displays when the user manually triggers an IPsec VPN

connection request to the remote VPN gateway.
Configure Allows you to edit or delete the IPsec configuration.

 Edit – Allows you to modify IPsec VPN parameters of this
tunnel.
 Delete – Allows you to remove this IPsec VPN tunnel.
Add New Tunnel Creates a new IPsec VPN tunnel and adds it to the IPsec list.
Click Edit to modify its parameters.
9.2 Using the IPsec Option

The IPsec option allows you to configure a complete VPN.
Steps
To configure a VPN:
1. Click the VPN link from the main menu.
2. Click IPsec from the left side menu. Field descriptions are listed below the screen
example.
Label Description
Tunnel Lists the number of the VPN tunnels available to edit. If not
tunnels exist, the list shows, Tunnel list is EMPTY.
Name Displays the name for the tunnel.
Enabled/Disabled Enables or disables the VPN tunnel.
Delete Tunnel Removes the selected VPN tunnel.
Add New Tunnel Adds the new tunnel after a name is entered.
Apply Enables or Disables the tunnel when you click Apply to save
your changes.
Local endpoint settings
Label Description
Address group type Configures the local network that will be protected by the
IPsec VPN located on your device’s LAN side. Choose the
local address type:
 IP Subnet, to protect the whole subnet.
 Single IP address, to protect a single PC.
 IP address range, to protect several PCs.
Subnet Defines the subnet.
Mask Defines the subnet mask.
Identity type Defines the identity type for this device:

 Automatically use WAN IP address
 IP address
 Fully qualified domain name (FQDN)
 Email address (USER FQDN)
In Main mode (see IKE negotiation mode on page 69), the
identity type and content are encrypted to provide identity
protection. The VPN concentrator can distinguish up to 30
different incoming SAs that have dynamic WAN IP addresses
and connect from remote IPsec routers. You can select
between five encryption algorithms (DES, 3DES, AES-128,
AES-192 and AES-256), two authentication algorithms (MD5
and SHA1) and three key groups (DH1 and DH2, DH5) when
you configure a VPN rule. The identity type and content act as
an extra level of identification for incoming SAs.
In Aggressive mode (see IKE negotiation mode on page 69),

the VPN concentrator identifies incoming SAs by identity type
and content (which are not encrypted) to distinguish between
multiple rules for SAs that connect from remote IPsec routers
that have dynamic WAN IP addresses.
Identity Defines the value corresponding to the selected Identity type.
Remote endpoint settings
Address group type Defines the address group type:

 IP Subnet – protects the entire subnet.
 Single IP address – protects a single PC.
 IP address range – protects several PCs.
Subnet Defines the subnet.
Mask Defines the subnet mask.
Identity type Defines the identity type to identity this device by:
 Automatically use WAN IP address
 IP address
 Fully qualified domain name (FQDN)
 Email address (USER FQDN)
Identity Defines the value corresponding to the selected identity type.
Label Description
Network address type Defines the network address type:

 IP address, usually suitable for static public IP address.
 Fully Qualified Domain Name (FQDN), usually suitable for
dynamic public IP address.
Remote address Identifies the specific remote IPsec VPN gateway to which
your device will initiate the IPsec VPN connection:
 Use the IP address value when an IP address is the
Network Address Type.
 Use the FQDN if FQDN is selected.
IPsec settings
Pre-shared key Defines your pre-shared key. A pre-shared key identifies a

communicating party during a phase 1 IKE negotiation. It is
called “pre-shared” because you have to share it with the
other party before you can communicate with them over a
secure connection.
Phase 1 DH group Defines which Diffie-Hellman key group (DHx) you want to use
for encryption keys:
 DH1 – a 768-bit random number
Phase 1 encryption Defines which key size and encryption algorithm to use for
data communications:
 DES – a 56-bit key with the DES encryption algorithm.
 3DES – a 168-bit key with the DES encryption algorithm.
The DDW365 and the remote IPsec router must use the
same algorithms and key, used to encrypt and decrypt the
messages or to generate and verify a message
authentication code. Longer keys require more
processing power, resulting in increased latency and
decreased throughput.
 AES – the Advanced Encryption Standard method of data
encryption also uses a secret key. This implementation of
AES applies a 128-bit key to 128-bit blocks of data. AES
is faster than 3DES. You can choose AES-128, AES-192,
AES-256.
Phase 1 authentication Defines which hash algorithm to use to authenticate packet

data in the IKE SA.
 MD5 (message digest 5) produces a 128-bit digest to
authenticate packet data.
 SHA1 (secure hash algorithm) produces a 160-bit digest
to authenticate packet data. SHA1 is generally considered
stronger than MD5, but it is also slower.
Phase 1 SA lifetime Defines the length of time (from 120 to 86400 seconds) before
an IKE SA process renegotiates a key. A short SA lifetime
increases security by forcing the two VPN gateways to update
the encryption and authentication keys. However, every time
the VPN tunnel renegotiates the keys, remote users are
temporarily disconnected.
Label Description
Phase 2 encryption Defines the key size and encryption algorithm to use for data
communications:
 Null – No data encryption in IPsec SA. Not suggested.
 DES – A 56-bit key with the DES encryption algorithm.
 3DES – A 168-bit key with the DES encryption algorithm
device and the remote IPsec router must use the same
algorithms and key, which can be used to encrypt and
decrypt the message or to generate and verify a message
authentication code. Longer keys require more
processing power, resulting in increased latency and
decreased throughput.
 AES – The advanced encryption standard method of data
encryption also uses a secret key. This implementation of
AES applies a 128-bit key to 128-bit blocks of data. AES
is faster than 3DES. You can choose AES-128, AES-192,
AES-256.
Phase 2 authentication Defines the hash algorithm to use to authenticate packet data
in the IKE SA. Choices are Null, SHA1 and MD5. SHA1 is
generally considered stronger than MD5, but it is also slower.
Phase 2 SA lifetime Defines the length of time (from 120 to 86400 seconds) before
an IPsec SA process renegotiates keys.
Advanced Settings
Key management Defines the Auto (IKE) or Manual key configuration to set up a
VPN.
IKE negotiation mode Determines how the security association (SA) is established
for each connection through IKE negotiations. The choices
are:
 Main Mode – Ensures the highest level of security when
the communicating parties are negotiating authentication
(phase 1).
 Aggressive Mode – Eliminates several steps when the
communicating parties are negotiating authentication
(phase 1). Quicker than Main Mode.
Perfect forward secrecy (PFS) Enables or disables the perfect forward secret (PFS) option.
This option is disabled by default in phase 2 IPsec SA setup
to provide a faster IPsec setup, but is not very secure. Select
DH1, DH2 or DH5 to enable PFS.
Phase 2 DH group Defines which Diffie-Hellman key group (DHx) you want to use
for encryption keys:
Replay detection Enables or disables replay detection. As VPN setup is
processing, the system can be vulnerable to denial of service
(DOS) attacks. The IPsec receiver can detect and reject old or
duplicate packets to protect against replay attacks.
Ubee Interactive Using the Event Log Option
Label Description
NetBIOS broadcast forwarding Provides the option to send NetBIOS packets through the
VPN connection. NetBIOS (Network Basic Input/Output
System) are TCP or UDP packets that enable a computer to
find other computers. It may sometimes be necessary to allow
NetBIOS packets to pass through VPN tunnels to allow local
computers to find computers on the remote network and vice
versa.
Dead peer detection Enables or disables dead peer detection. When enabled the
device is forced to periodically detect if the remote IPsec
gateway is available.
9.3 Using the Event Log Option

Use the Event Log option to view the events related to VPN activity.
Steps
To view the event log:
1. Click the VPN link from the main menu.
2. Click Event Log from the left side menu. Field descriptions are listed below the screen
example.
Label Description
Time Displays the local time of a certain log event.
Description Displays detailed information of a log.
Refresh Refreshes the current page to view new log events.
Clear Clears all the VPN event logs.
10 Understanding the Wireless Menu
Use the Wireless menu to configure a wireless network.
Topics
 Using the Wireless Radio Option on page 71
 Using the Primary Network Option on page 74
 Using the Guest Network Option on page 78
 Using the Advanced Option on page 83
 Using the Access Control Option on page 84
 Using the Wi-Fi Multimedia Option on page 86
 Using the Bridging Option on page 89
 Deploying and Troubleshooting the Wireless Network on page 90
Steps
To access the wireless menu:
13.
2. Click Wireless from the main menu.
10.1 Using the Wireless Radio Option

The Radio option is used to configure the wireless radio, including channel number, and
bandwidth control.
Steps
To configure wireless operations:
2. Click Radio from the left side menu. Field descriptions are listed below the screen
example.
Ubee Interactive Using the Wireless Radio Option
Label Description
Wireless Interfaces Displays the wireless name and MAC address.
Wireless Displays the wireless radio’s status, Enabled or Disabled.
Country Defines the country where this device is located. Set by

default to Q1.
Output Power Output power setup can be one of the following 4 options:
25%, 50%, 75%, or 100%.
802.11 Band Displays the 802.11 band (2.4GHz).
802.11 n-mode Sets the wireless networking standard.
By default it is set to Auto for 802.11n mode. This mode has a

significant increase in the maximum raw OSI physical layer
data rate from 54 Mbit/s to a maximum of 600 Mbit/s with the
use of four spatial streams when at a channel width of 40
MHz.
One spacial stream at 20 MHz wide channel enables

72.2Mbps maximum data rate in 802.11n mode.
802.11 N Support Required Defines whether 802.11n support is required (on) or not (off).
On forces the gateway to 802.11n mode and clients must
support 802.11n.
Bandwidth Sets the bandwidth to 20Mhz or 40Mhz. For 40 MHz, set the
sideband to lower or upper 20Mhz. 40 MHz channels double
the channel width. This allows doubling the PHY data rate
over a single 20 MHz channel.
Sideband for Control Channel Only when using 40MHz Bandwidth should you choose the
(40MHz only) Lower or Upper 20MHz.
Ubee Interactive Using the Wireless Radio Option
Label Description
Control Channel Set to Auto by default, the Control Channel selects a specific
channel to deploy the wireless network. This allows you to set
the operating frequency/channel depending on your particular
region. Channel selection can have an impact on wireless
networking performance. For more information, refer to
Selecting a Wireless Channel on page 93
Regulatory Mode Defines whether Regulatory Mode is set to off, 802.11d, or

802.11h.
TPC Mitigation (dB) Defines the transmitter power control (TPC) mitigation setting
as 0 (off), 2,3, or 4.
OBSS Coexistence Enables or disables overlapping BSS coexistence.
STBC Tx Sets the space-time block codes (STBCs) for the transmitting
antenna.
Apply Saves all screen changes when clicked.
Restore Wireless Defaults Restores the factory default settings for wireless
configurations when clicked.
Scan Wireless APs Scans for other wireless access points and displays channel,
encryption, SSID, RSSI levels, and other information. See the
section below for more information.
10.1.1 Scanning for Wireless Access Points (APs)

You can search for wireless access points and display the results in a new window.
Steps
To search for wireless access points:
1. Click Scan Wireless APs at the bottom of the Wireless Radio screen. Results are
displayed in a new window.
2. Click Refresh to update the results.
Ubee Interactive Using the Primary Network Option
Label Description
Network Name Displays the name of the wireless network (SSID) broadcast
by the access point.
Security Mode Displays the encryption method used.
Mode Displays the mode of the wireless access point: Possible

modes are:
 Master – Communicates with associated wireless cards
that are in managed mode. Appears as a normal access
point with an SSID and channel. Network
communications, such as authentication, conflict, and
duplicate packets are managed by the wireless card.
 Managed – Communicates with an associated master,
not directly with another managed AP. Wireless cards
connect to the master network and change their channel
to match. The master must accept the credentials of the
managed network for it to be associated.
 Ad-hoc – Communicates directly with another wireless
network. Network cards must be in range and use the
same name and channel.
 Monitor – Communicates in observation mode and does
not transmit. Can be used for troubleshooting wireless
links or checking bandwidth usage in the area.
PHY Mode Displays the physical transceivers (PHY) layer method used.
RSSI Displays the received signal strength (RSSI) of the wireless

access points in range of the device. Lower negative numbers
(for example, -1 to -65) indicate the access point is closer.
Greater negative numbers (for example, -66 to -95) indicate
the access point is farther away.
Channel Displays the channel on which the wireless cable modem is

operating.
BSSID Displays the MAC address for the nearby wireless access
points.
10.2 Using the Primary Network Option

Use the Primary Network option to configure a variety of wireless security settings.
Steps
To configure wireless security options:
2. Click Primary Network from the left side menu. Field descriptions are listed below the
screen example. This example shows the settings when the modem is in the 2.4GHz
band.
Wireless default values are discussed in Understanding Default Values and Logins on
page 7.
Label Description
Primary Network Enables or disables the primary network. This field is enabled
by default.
Network Name (SSID) Defines the wireless primary network name (SSID) to which
client devices connect. (Example: DDW365.442802-2.4G).
Refer to Understanding Default Values and Logins on page 7
for more information on the SSID.
Closed Network Hides the selected SSID when enabled so it is not visible to
wireless clients. When disabled, the SSID is visible. Closed
Network is disabled by default to allow broadcasting the
primary network name (SSID). Refer to Enabling a Closed
Network on the Primary Network on page 78 to set up a
closed network.
AP Isolate Disabled by default. When enabled, it prevents wireless client

stations from communicating with each other.
Label Description
WPA Enables or disables the Wi-Fi Protected Access (WPA)

security protocol. WPA is a subset of the IEEE 802.11i
standard. Key differences between WPA and WEP are user
authentication and improved data encryption. Setting WPA
alone with a pre-shared key requires a RADIUS or TACACS
server for authentication. This method is mostly used in large
enterprise implementations.
WPA-PSK Enables or disables WPA Pre-Shared Key (WPA-PSK). If you

do not have an external RADIUS server, use WPA-PSK,
which requires a single (identical) password entered into
wireless gateway and wireless client. As long as the
passwords match, a client is granted access to the wireless
LAN. This is the default residential subscriber setting and
uses TKIP encryption.
WPA2 Enables or disables WPA2. This advanced protocol is

certified through Wi-Fi Alliance's WPA2 program and
implements the mandatory elements of 802.11i. In particular,
it has an AES-based algorithm (CCMP) that is considered
fully secure. Setting WPA2 alone with a pre-shared key
requires a RADIUS or TACACS server for authentication.
This method is mostly used in large enterprise
implementations.
WPA2-PSK Enables or disables WPA2-PSK. If you do not have an

external RADIUS server, use WPA2-PSK, which requires a
single (identical) password entered into wireless gateway and
wireless client. As long as the passwords match, a client is
granted access to the wireless LAN. This is the
recommended residential subscriber option. It is more secure
than WPA-PSK and uses AES encryption.
WPA/WPA2 Encryption Sets WPA/WPA2 encryption to AES or TKIP+AES. The

default is AES.
WPA Pre-Shared Key Displays (checked) or hides (unchecked) the WPA key. The
encryption mechanisms for WPA and WPA-PSK are the
same, except that WPA-PSK uses a simple common
password instead of user-specific credentials.
Show Key Displays the pre-shared key when checked.
RADIUS Server Defines the IP address of the RADIUS server, if used.
RADIUS Port Defines a RADIUS port number when WPA or 802.1x network
authentication is selected.
RADIUS Key Defines the RADIUS Key when WPA or 802.1x network
Group Key Rotation Interval Allows the device to generate the best possible random
group key and update all the key-management capable
stations periodically. This field is set to 0 by default.
Label Description
WPA/WPA2 Re-auth Interval Sends a new group key to all clients at the specified interval
for a wireless router (if using WPA-PSK key management) or
RADIUS server (if using WPA key management). The re-
keying process is the WPA equivalent of automatically
changing the WEP key for a wireless access point and all
stations in the WLAN on a periodic basis. Setting the WPA
Group Key Update Timer is also supported in WPA-PSK
mode.
WEP Encryption Enables or disables WEP encryption. If you do not have

wireless clients that can use WPA or WPA2, you can use WEP
key encrypting. A higher bit key offers better security. WEP
encryption scrambles the data transmitted between the wireless
stations and the DDW365 to keep network communications
private. It encrypts unicast and multicast communications in a
network. Both the wireless stations and the DDW365 must use
the same WEP key. Data Encryption can be set to WEP 128-
bit, 64-bit, or Disable.
Shared Key Authentication Defines Shared Key Authentication as optional or required.

Shared Key is an authentication method used by wireless
LANs, which follow the IEEE 802.11 standard. Wireless
devices authenticate each other by using a secret key that is
kept by both devices.
802.1x Authentication Enables or disables 802.1x to authenticate wireless clients.
Network Key 1-4 Pre-defines up to 4 keys for 64-bit or 128-bit (64-bit keys
require 10 hexadecimal digits) (128-bit key require 26
hexadecimal digits).
Current Network Key Selects one of the four pre-defined keys as the current
network key.
Passphrase Sets the WEP encryption key by entering a word or group of

printable characters in the Passphrase box and clicking
Generate WEP keys. These characters are case sensitive.
Generate WEP Keys Forces the device to generate 4 WEP keys automatically.
Automatic Security Configuration — Sets up WPS (Wi-Fi Protected Setup) for devices connecting
to the wireless network.
WPS/Disabled Enables or disables WPS option. When enabled, the

following fields are available:
WPS Config State Defines if the WPS has been configured or not.
Device Name Defines a name for this wireless cable modem for WPS.
WPS Setup AP
UUID Defines the universal unique identifier (UUID) for this access
point.
PIN Defines the Personal Identification Number for this access

point.
Ubee Interactive Using the Guest Network Option
Label Description
Generate AP PIN Creates a new PIN for this access point.
WPS Add Client
Add a client Activates wireless protected setup (WPS) security on the

device.
To add a client:
1. Click Add a client. The WPS Add Client screen is
displayed.
2. Click PUSH on the WPS Add Client screen.The WPS
button is activated on the device, indicated by a flashing
white light on top of the unit.
3. Press the WPS button on the device.
Client PIN Defines a PIN number for client access.
Authorized Client MAC Defines the MAC address of the authorized client.
10.2.1 Enabling a Closed Network on the Primary Network

You can enable the Closed Network option so the SSID cannot be broadcast or seen by
others.
Steps
To enable a closed network:
1. Access the pull down menu for the Closed Network.
2. Choose Enabled to enable a closed network. Automatic Security Configuration is
disabled.
10.3 Using the Guest Network Option

Use the Guest Network option to configure a variety of wireless security settings to allow
guests to access your network.
Steps
To configure guest network security options:
2. Click Guest Network from the left side menu. Field descriptions are listed below the
screen example. This example shows the settings when the modem is in the 2.4GHz
band.
Wireless default values are discussed in Understanding Default Values and Logins on
page 7.
Label Description
Guest Network Names the guest network and the wireless LAN (WLAN)
MAC address assigned to the SSID. There are up to seven
Guest SSIDs per radio (2.4GHz) that can be individually
enabled and renamed by specifying the “Guest Network
Name (SSID)” for the appropriate network.
Guest WiFi Security Settings
Guest Network Enables or disables the guest network.
Guest Network Name (SSID) Defines a unique SSID for the cable modem or uses the
default. (Example: UBEE_GUEST_0_0).
Closed Network Hides the selected SSID when enabled so it is not visible to
wireless clients unless manually set up on the client. If
disabled, the SSID is visible. Refer to Enabling a Closed
Network on the Primary Network on page 78 to set up a
closed network.
AP Isolate Prevents wireless client stations from communicating with

each other when enabled.
WPA Enables or disables the Wi-Fi Protected Access (WPA)

security protocol. WPA is a subset of the IEEE 802.11i
standard. Key differences between WPA and WEP are user
authentication and improved data encryption. Setting WPA
alone with a pre-shared key requires a RADIUS or TACACS
server for authentication. This method is mostly used in large
enterprise implementations.
WPA-PSK Enables or disables WPA Pre-Shared Key (WPA-PSK). If you

do not have an external RADIUS server, use WPA-PSK,
which requires a single (identical) password entered into
wireless gateway and wireless client. As long as the
passwords match, a client is granted access to the wireless
LAN. This is the default residential subscriber setting and
uses TKIP encryption.
WPA2 Enables or disables WPA2. This advanced protocol is

certified through Wi-Fi Alliance's WPA2 program and
implements the mandatory elements of 802.11i. In particular,
it has an AES-based algorithm (CCMP) that is considered
fully secure. Setting WPA2 alone with a pre-shared key
requires a RADIUS or TACACS server for authentication.
This method is mostly used in large enterprise
implementations.
WPA2-PSK Enables or disables WPA2-PSK. If you do not have an

external RADIUS server, use WPA2-PSK, which requires a
single (identical) password entered into wireless gateway and
wireless client. As long as the passwords match, a client is
granted access to the wireless LAN. This is the
recommended residential subscriber option. It is more secure
than WPA-PSK and uses AES encryption.
WPA/WPA2 Encryption Sets WPA/WPA2 encryption to AES or TKIP+AES. The

default is AES.
Label Description
WPA Pre-Shared Key Displays (checked) or hides (unchecked) the WPA key. The
encryption mechanisms for WPA and WPA-PSK are the
same, except that WPA-PSK uses a simple common
password instead of user-specific credentials.
Show Key Displays the pre-shared key when checked.
RADIUS Server Defines the IP address of the RADIUS server, if used.
RADIUS Port Defines a RADIUS port number when WPA or 802.1x network
RADIUS Key Defines the RADIUS Key when WPA or 802.1x network
Group Key Rotation Interval Allows the device to generate the best possible random
group key and update all the key-management capable
stations periodically.
WPA/WPA2 Re-auth Interval Sends a new group key to all clients at the specified interval
for a wireless router (if using WPA-PSK key management) or
RADIUS server (if using WPA key management). The re-
keying process is the WPA equivalent of automatically
changing the WEP key for a wireless access point and all
stations in the WLAN on a periodic basis. Setting the WPA
Group Key Update Timer is also supported in WPA-PSK
mode.
WEP Encryption Enables or disables WEP encryption. If you do not have

wireless clients that can use WPA or WPA2, you can use WEP
key encrypting. A higher bit key offers better security. WEP
encryption scrambles the data transmitted between the wireless
stations and the DDW365 to keep network communications
private. It encrypts unicast and multicast communications in a
network. Both the wireless stations and the DDW365 must use
the same WEP key. Data Encryption can be set to WEP 128-
bit, 64-bit, or Disable.
Shared Key Authentication Defines Shared Key Authentication as optional or required.

Shared Key is an authentication method used by wireless
LANs, which follow the IEEE 802.11 standard. Wireless
devices authenticate each other by using a secret key that is
kept by both devices.
802.1x Authentication Enables or disables 802.1x to authenticate wireless clients.
Network Key 1-4 Pre-defines up to 4 keys for 64-bit or 128-bit (64-bit keys
require 10 hexadecimal digits) (128-bit key require 26
hexadecimal digits).
Current Network Key Selects one of the four pre-defined keys as the current
network key.
Passphrase Sets the WEP encryption key by entering a word or group of

printable characters in the Passphrase box and clicking
Generate WEP keys. These characters are case sensitive.
Generate WEP Keys Forces the device to generate 4 WEP keys automatically.
Label Description
Guest LAN Settings
Network Defines the type of network: LAN or Guest.When Guest is

selected, the additional options are available.
IP Address Defines the default gateway address for clients connected to

this guest network.
Subnet Mask Defines the subnet mask value.
Lease Pool Start Defines the start IP address of this DHCP address pool.
Lease Pool End Defines the last IP address of this DHCP address pool.
Lease Time Defines the lease time for DHCP client. Before expiration,
DHCP client will resend DHCP request. Max value is 86400
seconds.
UPnP Enable Enables or disables UPnP settings for the guest network.
Firewall Enable Enables or disables firewall settings for the guest network.
DHCPv6 Server Enables or disables DHCPv6 Server settings for the guest
network.
Restore Guest Network Defaults Resets the device to factory default values for the guest
network settings only.
10.3.1 Enabling a Closed Network on the Guest Network

You can enable the Closed Network option so the SSID cannot be broadcast or seen by
others.
Steps
To enable a closed network:
1. Access the pull down menu for the Closed Network.
2. Choose Enabled to enable a closed network. Automatic Security Configuration is
disabled.
Ubee Interactive Using the Advanced Option
10.4 Using the Advanced Option

Use the Advanced option to configure data rates and Wi-Fi thresholds.
2. Click Advanced from the left side menu. Field descriptions are listed below the screen
example.
Label Description
54g™ Mode Selects the network mode in which to run the DDW365. The
options are:
 54g auto – self adaptive connection
 54g performance – highest speed
 54g LRS – limited speed
 802.11b – connections to 11b clients only.
This field can be set only if 802.11-n Mode is set to Off in the
Radio screen as discussed on Using the Wireless Radio Option
on page 71.
XPress™ Technology Enables or disables the XPress feature. XPress™ is a

standards-based frame-bursting approach to improve 802.11g
wireless LAN performance developed by Broadcom. When
Xpress enabled, aggregate throughput can improve up to 27%
in 802.11g-only networks, and up to 75% in mixed networks
comprised of 802.11g and 802.11b standard equipment.
802.11n Protection Defines the 802.11n Protection setting.

 Auto - the DDW365 uses Request to Send/Clear to Send
(RTS/CTS) to improve the performance in 802.11 mixed
environments.
 Off - the 802.11 performance is maximized under most
conditions, while the other 802.11 modes (802.11b, etc.) are
secondary.
Short Guard Interval Defines a transmission interval so data transmissions do not

interfere with each another.
Ubee Interactive Using the Access Control Option
Label Description
Basic Rate Set Selects the rate that all wireless clients must support to connect
to the DDW365. The options are All and Default.
Multicast Rate Specifies the rate at which multicast packets are transmitted and
received on your wireless network.
NPHY Rate Sets the Physical Layer (NPHY) rate. Choose Legacy Rate to
use 802.11a or 802.11g modes, and then choose the rate in the
Legacy Rate field.
Legacy Rate Sets the wireless rate to the chosen 802.11a or 802.11g legacy
rate.
Beacon Interval Specifies the Beacon Interval from 100 to 6553 5ms. This value
indicates the frequency interval of the beacon. A beacon is a
packet broadcast by the DDW365 to keep the network
synchronized. A beacon includes information regarding the
wireless networks service area, the access point address, the
broadcast destination addresses, a time stamp, delivery traffic
indicator maps, and the Traffic Indicator Message (TIM).
DTIM Interval Specifies the DTIM interval from 3 to 255ms. This value
indicates how often the DDW365 sends out a Delivery Traffic
Indication Message (DTIM). Lower settings result in more
efficient networking, while preventing your wireless clients from
dropping into power-saving sleep mode. Higher settings allow
your wireless clients to enter sleep mode, thus saving power,
but interferes with wireless transmissions.
Fragmentation Specifies the fragmentation threshold packet size between 256-

Threshold 2346 bytes. Fragmentation takes place when a packet’s size
exceeds the fragmentation threshold.
RTS Threshold Specifies the RTS threshold from 0 to 2347ms. This setting
determines how large a packet can be before the DDW365
coordinates transmission and reception to ensure efficient
communication. This value should remain at its default setting of
2347 bytes. If you encounter inconsistent data flow, minor
modification to this setting is recommended.
10.5 Using the Access Control Option

Use the Access Control option to configure which clients can access your wireless
network.
Steps
To configure client access:
2. Click Access Control from the left side menu. Field descriptions are listed below the
screen example.
Ubee Interactive Using the Access Control Option
Label Description
Wireless Interface Defines the network name and MAC address for which you
are setting access control parameters: primary or guest
network.
MAC Restrict Mode Controls wireless access to your network by MAC address.
 Disabled turns off MAC restrictions and allows any
wireless client to connect to this device. However, if you
use other security mechanisms for access to the wireless
network, clients must still adhere to those restrictions.
 Allow creates a list of wireless clients that can connect to
the wireless network. Enter the MAC addresses of these
clients in the MAC Addresses fields. MAC addresses not
on the list, are not allowed access to your wireless
network.
 Deny creates a list of wireless clients that you do not
want to have access to your wireless network. Enter the
MAC addresses of these clients in the MAC Addresses
fields.
Ubee Interactive Using the Wi-Fi Multimedia Option
Label Description
MAC Addresses Defines the MAC addresses. Note: You may cut and paste
MAC addresses from the connected clients list at the bottom
of the screen.
Apply Saves changes when clicked.
Connected Clients Lists wireless clients currently connected listed by MAC

address.
 MAC Address – Displays the MAC addresses entered in
the MAC Addresses field (see above).
 Age(s) – Displays the duration since the wireless client’s
polled values were sent to the device. The values include
all information shown on this screen. The lower the
number, the more current its data.
 RSSI(dBm) – Displays the received signal strength from
the device to the wireless cable modem. This value is
commonly used to assist in troubleshooting wireless
performance issues. A signal strength between 0dBm
and -65dBm is considered optimal. Levels of -66dBm and
lower (for example, -70, -80, etc.) have a downward
impact on wireless data throughput. Refer to
Understanding Received Signal Strength on page 90 for
more information.
 IP Address – Displays the IP address assigned to this
wireless client.
 Host Name – Displays the host name of the wireless
client.
 Mode – Indicates the applicable 802.11a/b/g/n standard
used by the connected client device.
 Speed (kbps) – Displays the maximum theoretical link
speed negotiated between the wireless gateway and the
client, not including the overhead associated with
encryption, and so on. For example, actual speeds with
WEP encryption enabled are typically less than half of the
negotiated link speed. TKIP encryption can also affect
performance. AES is the most efficient and secure with
the highest throughput possible. You can disable WMM if
throughput on some client adapters is adversely affected.
10.6 Using the Wi-Fi Multimedia Option

Use the Wi-Fi Multimedia option to configure the quality of service (QoS) to ensure the
best service in your wireless networks.
 Controls WLAN transmission priority on packets transmitted over the wireless network.
 Wi-Fi Multi-Media Quality of Service (WMM QoS) is a part of the IEEE 802.11e QoS
enhancement to certified Wi-Fi wireless networks.
 WMM QoS prioritizes wireless traffic according to the delivery requirements of the
individual user and applications. On wireless access points without WMM QoS, all
traffic streams are given the same access priority to the wireless network. If a new
traffic stream creates a data transmission demand that exceeds the current network
capacity, the new traffic stream reduces the throughput of the other traffic streams.
 WMM QoS capability allows you to assign access categories (ACs) to various packet
streams. The assigned AC of a packet stream depends on the packet’s priority, such
as a priority assigned by an application (also referred to as a user priority (UP). An AC
may include a common set of enhanced distributed channel access (EDCA)
parameters used by QoS to contend for a channel to transmit packets with certain
priorities.
Different ACs can be associated with different power saving parameters. For example,
one power saving parameter might be the delivery mechanism used by an access
point (AP) to deliver packets to a station (STA) that is operating in a reduced power
mode.
 WMM transmit opportunity (TXOP) is assigned to each access point. The bounded
time interval during which a station can send as many frames as possible as long as
the transmission time does not extend past the maximum duration of the TXOP. If a
frame is too large to be transmitted in a single TXOP, it should be fragmented into
smaller frames. Using TXOP reduces the problem of low rate stations gaining too
much channel time in the legacy 802.11 DCF MAC. A TXOP time interval of 0 means
it is limited to a single MAC service data unit (MSDU) or MAC management protocol
data unit (MMPDU).
Note
WMM may need to be disabled to avoid throughput impacts to other wireless devices.
Steps
To configure the multimedia wireless option:
2. Click WMM (Wi-Fi Multimedia) from the left side menu. Field descriptions are listed
below the screen example.
Label Description
WMM Support Enables (On) or disables (Off) WMM support.
No-Acknowledgement Enables (On) or disables (Off) acknowledging data frames. In

QoS mode, frames to send can have two values: QosAck and
QosNoAck. Frames with QosNoAck are not acknowledged,
avoiding the retransmission of highly time-critical data.
Power Save Support Enables (On) or disables (Off) power savings. WMM Power
Save increases the efficiency and flexibility of data transmission.
The wireless client device can “doze” between packets to save
power, while the wireless access point buffers downlink frames.
The application chooses the time to wake up and receive data
packets to maximize power conservation without sacrificing
quality of service.
Apply Saves changes to the WMM settings above.
EDCA AP Parameters Allows you to prioritize wireless network traffic. Enhanced

Distributed Channel Access – Access Point (EDCA-AP)
provides four access categories (ACs):
 AC_BE – Best Effort, medium throughput and delay. Most
traditional IP data is sent to this queue.
 AC_BK – Background, high throughput. Bulk data that
requires maximum throughput and is not time-sensitive is
sent to this queue (for example, FTP data).
 AC_VI – Video
 AC_VO – Voice
Ubee Interactive Using the Bridging Option
CWmin Sets the time for the following fields:

CWmax  CWmin – Contention window minimum
AIFSN  CWmax – Contention window maximum
TXOP (b) Limit (usec)  AIFS – Arbitration inter-frame space
TXOP (a/g) Limit (usec)  TXOP – Transmit opportunity
Discard Oldest First  Discard Oldest First – Removes oldest frame when set to
On.
EDCA STA Parameters Allows you to prioritize wireless network traffic for receiving
terminals. Access categories are:
 AC_VI – Video
 AC_VO – Voice
WMM TXOP Parameters Allows you to prioritize wireless network traffic for wireless
multimedia transmit opportunities. Access categories are:
 AC_VI – Video
 AC_VO – Voice
Short Retry Limit Defines how many times the MAC retries to send different types
Short Fallbk Limit of packets. If the number of retries reach their limit, the frame is
Long Retry Limit discarded.
Long Fallbk Limit  Short Retry – Increments when a short packet frame is
Max Rate in 500kbps retransmitted.
 Short Fallbk –
 Long Retry – Increments when a long packet frame is
retransmitted.
 Long Fallbk –
 Max rate in 500kbps –
Apply Saves all changes.
10.7 Using the Bridging Option

Use the Bridging option to configure the DDW365 to act as a wireless network bridge
and establish wireless links with other wireless access points. To establish a bridge, you
need to know the MAC address of the peer device, that must be in wireless bridging mode
as well. The DDW365 can establish up to four wireless links with other wireless access
points. When wireless devices are in wireless bridging mode, they form a wireless
distribution system that allows computers in one LAN to connect to the computers in the
other LAN.
Caution
Avoid bridge loops when you enable bridging devices. Bridge loops cause broadcast traffic to
circle the network endlessly. This can degrade throughput and disrupt communications.
Ubee Interactive Deploying and Troubleshooting the Wireless Network
Steps
To configure the modem as a bridge:
2. Click Bridging from the left side menu. Field descriptions are listed below the screen
example.
Label Description
Wireless Bridging Enables or disables bridging.
Remote Bridges Defines the MAC addresses of other wireless access points that
you want to establish a bridge to and from. These access points
must also have bridging enabled.
Apply Saves all changes.
10.8 Deploying and Troubleshooting the Wireless Network

Use the information in this section to help you understand, deploy, and troubleshoot your
wireless environments:
 Understanding Received Signal Strength on page 90
 Estimating Wireless Cable Modem to Wireless Client Distances on page 91
 Selecting a Wireless Channel on page 93
Understanding Received Signal Strength

Received signal strength (RSSI) is measured from connected wireless client devices to
the wireless cable modem. This value can significantly impact wireless
speeds/performance. It is determined by:
 Materials (for example, open air, concrete, trees)
 Distance between wireless clients and the wireless cable modem
 Wireless capabilities of the client devices
To determine the received signal strength, refer to Using the Access Control Option on
page 84 and review the RSSI value. A receive signal strength indicator between 0 to -64
dBm is considered optimal. Levels of -67dBm and lower (for example, -70, -80, etc.) have
a downward impact on wireless data throughput.
Estimating Wireless Cable Modem to Wireless Client Distances

The information in this section helps you to determine how far a wireless cable modem
can be placed from wireless client devices. Environmental variances include the
capabilities of wireless clients and the types of material through which the wireless signal
must pass. When the wireless cable modem and wireless clients reach the distance
threshold between each other, network performance degrades.
Steps
To determine wireless cable modem placement:
1. Connect a wireless client to the wireless cable modem. Refer to Connecting Devices to
the Network on page 10 if needed.
2. Place the wireless client at around one meter (three feet) away from the wireless cable
modem.
3. Obtain the RSSI value for the connected client. Refer to Using the Access Control
Option on page 84. This value is used in the formula further below.
4. Use the following table to determine what materials the wireless signal must travel
through to reach the desired wireless coverage distance.
Attenuation Considerations at 2.4GHz
Material Attenuation
Connector/Cable 3.5dB
Free Space 0.24dB / foot
Interior Drywall 3dB to 4dB
Cubicle Wall 2dB to 5dB
Wood Door (Hollow/Solid) 3dB to 4dB
Brick, Concrete Wall (Note 1) 6dB to 18dB
Glass Window (not tinted) 2dB to 3dB
Double Pane Coated Glass 13dB
Bullet Proof Glass 10dB
Steel / Fire Exit Door 13dB to 19dB
Attenuation Considerations at 2.4GHz
Material Attenuation
Human Body 3dB
Trees (Note 2) 0.15dB / foot
Note 1: Different types of concrete materials are Note 2: The attenuation caused by trees
used in different parts of the world and the thickness varies significantly depending upon the shape
and coating differ depending on whether it is used in and thickness of the foliage.
floors, interior walls, or exterior walls.
5. Use the attenuation value from the materials table above in the following formula:
Formula:
(Transmit Power, use -30dBm) – (Receiver Sensitivity, use RSSI value) =
Allowable Free Space Loss
Allowable Free Space Loss ÷ Materials Attenuation Value =
Optimal Distance in Feet Between the Cable Modem and a Wireless Client
Example:
(-30dBm) - (-67dBm) = 37dBm (allowable free space loss for a 54Mbps
connection)
37dBm ÷.24db/foot (for open space) = 154.16 feet
6. Once you know the optimal feet distance between individual wireless clients and the
wireless cable modem, you may resolve and prevent some performance issues.
7. To check the wireless signal strength and speed, use the following steps for a
Windows computer connected wirelessly to the wireless cable modem. If the wireless
computer is not connected, refer to Connecting a Wireless Device on page 11.
a. Click the Wireless networking icon in the system tray to display a list of available
wireless networks.
b. Click the Wireless networking icon, click “Open Network and Sharing Center,” then
click “Wireless Network Connection.”
c. Review the speed and signal strength in the Status window.
Selecting a Wireless Channel

You may need to change the wireless channel on which the wireless cable modem
operates when you are in computing, test, and other environments where several wireless
access points may be operating in the 2.4GHz range.
In some cases, you may want to segment your wireless traffic where a group of devices
operates on one channel and another group operates on another channel, and so on. This
is done by configuring the channel on each wireless access point individually (if you have
multiples). If you have control over only one wireless device in an environment where
there may be several, you can change the wireless channel on your device to one that is
not heavily used.
Note
To change the wireless broadcast channel, refer to Using the Wireless Radio Option on
page 71.
The following diagram displays the channels available in the Americas. Each available
channel is 22MHz wide. Since channels overlap, it is best to choose channels that have
the least overlap (typically 1, 6, and 11 in the Americas, and 1, 5, 9, and 13 in Europe).
Overlapping channels can cause wireless network performance issues.
Source: Wikipedia.org, and IEEE article IEEE 802.11n-2009
11 Understanding the USB Menu
The USB menu of the Web user interface allows you to configure USB storage devices
and media file scanning.
Topics
 Using the USB Basic Option on page 94
 Using the Approved Devices Option on page 95
 Using the Storage Basic Option on page 97
 Using the Storage Advanced Option on page 98
 Using the Media Server Option on page 100
Steps
To access USB options:
1. Access the Web user interface. Refer to Using the Web User Interface on page 13.
2. Click USB from the main menu.
11.1 Using the USB Basic Option

The USB Basic option allows you to configure Linux based servers. The buttons on the
right side of the page are short cuts to the options on the left side of the page.
Steps
To view USB basic information:
1. Click USB Basic from the left side menu. Field descriptions are listed below the
screen example.
Ubee Interactive Using the Approved Devices Option
Label Description
Enable USB Devices connected to Allows you to enable USB devices that are plugged in to the
the USB port USB port. Options are All, Approved, or None. The default
setting is All.
Approved Devices Takes you to the Approved Devices page.
Enable USB Devices to be Shared Allows you to designate USB devices to be shared storage.
Storage
Storage Configuration Takes you to the Storage Basic page.
Enable the Media Server (DLNA) Allows you to enable the media server. The media server
must be DLNA-certified. The DLNA (Digital Living Network
Alliance) defines standards that enable devices to share
information such as photos, videos, and music.
Media Server Configuration Takes you to the Media Server page.
11.2 Using the Approved Devices Option

The Approved Devices option allows you to choose if any storage device plugged into
the modem can be used or only approved devices. If “Approved” is selected, each device
must be manually approved on this page.
Steps
To view approved devices information:
1. Click Approved Devices from the left side menu. Field descriptions are listed below
the screen example.
Ubee Interactive Using the Approved Devices Option
Label Description
Enable USB devices connected Allows you to enable USB devices that are connected to the
to the USB port USB port. Options are All, Approved, or None.
Apply Changes Saves changes.
Approved USB Devices Displays information about currently approved USB devices.
Select Allows you to select the device by checking the box.
Volume Name Displays the name of the USB device.
Manufacturer Displays the manufacturer of the USB device.
Product Indicates the type of the USB device.
Free Space Displays the free space available on the USB storage device.
Used Space Displays the space that has been used on the USB storage
device.
Total Space Displays the total space on the USB storage device.
SMART Status Displays the SMART (Self-Monitoring, Analysis, and Reporting

Technology) status of the USB drive.
Remove To remove a device from the list of approved USB devices,

select the device and click Remove.
Available USB Devices Displays USB devices that are available to be added to the
approved USB devices list. The individual field listings are the
same as those under the Approved Devices heading.
Ubee Interactive Using the Storage Basic Option
Label Description
Add To add an available USB device to the Approved USB Devices

list, select the device and click Add.
Refresh List Allows you to refresh the lists of approved and available USB
devices.
Safely Remove Device Allows you to safely remove a USB device. Click Safely
Remove Device. The following window pops up. Select the
device you want to remove from the drop down menu, and
click “Remove Selected Device.”
11.3 Using the Storage Basic Option

The Storage Basic page allows you to configure the device name and designate what
folders should be shared.
Steps
To view basic storage information:
1. Click Storage Basic from the left side menu. Field descriptions are listed below the
screen example.
Ubee Interactive Using the Storage Advanced Option
Label Description
Network/Device Name Allows you to define the network and device name.
Default Sharing Allows you to set the default sharing option for the device.
Options are:
1. Share specified folders and all approved devices
2. Only share specified folders
Apply Saves changes to default sharing settings.
Shared Network Folders Shows information about shared network folders.
Edit Select Edit to open the Storage Advanced screen which

allows you to edit shared network folders.
Refresh Allows you to refresh the lists of shared network folders.
11.4 Using the Storage Advanced Option

The Storage Advanced page allows you to configure the device name and the workgroup
name, as well as enable or disable Windows Network and FTP support.
Steps
To view advanced storage information:
1. Click Storage Advanced from the left side menu. Field descriptions are listed below
the screen example.
Ubee Interactive Using the Storage Advanced Option
Label Description
Network/Device Name Allows you to define the network and device name.
Workgroup Name If you are using a Windows workgroup rather than a domain,
the workgroup name is displayed here.
Set Admin Name/Password Enter the NAS (network attached storage) administrator name
and password, then you will be allowed to change the user
name and password.
Protocols Allows you to enable or disable access methods. The

Windows Network Connection access method is enabled by
default. The FTP access method is disabled by default. If you
enable this setting, remote users can access the USB drive
through FTP over the Internet. The IP address displayed in the
link field is the Linux IP stack address that should be used for
the FTP server address in the FTP clients.
Ubee Interactive Using the Media Server Option
Label Description
Available Network Folders Displays information about available network folders.
Actions Displays Edit and Remove buttons for the folder.
Share Name Displays the shared name the folder was given during “Create
New Folder.”
Device Displays the device type and name.
Folder Displays the full path of the folder.
Read Access Shows the permissions and access controls assigned to the
folder.
Write Access
 “All - no password” is displayed if all users are allows to
access the folder.
 “Admin only” is displayed if a password is required to
access the folder.
Free Space Displays the free space available on the USB storage device.
Used Space Displays the space that has been used on the USB storage
device.
Total Space Displays the total space on the USB storage device.
Create Network Folder Allows you to create a network folder. Enter the appropriate
information in the following pop up window.
After clicking Apply, the information entered here will be

displayed in the Available Network Folders table.
Refresh List Allows you to refresh the list of shared network folders.
11.5 Using the Media Server Option

The Media Server page allows you to configure the DLNA media server. The media
server must be DLNA-certified. The DLNA (Digital Living Network Alliance) defines
standards that enable devices to share information such as photos, videos, and music.
The media server name and the file names that will be scanned on the USB storage
devices are configured using this option.
Steps
To view media server information:
1. Click Media Server from the left side menu. Field descriptions are listed below the
screen example.
Label Description
Basic Settings
Media Server Displays whether the media server is enabled or disabled.
Media Server Name The media server name, the name that will show up on media
players.
Test Mode Allows you to select the test mode. Options are:
1. Normal Operation
2. UPnP Certification
3. DLNA Certification
Apply Basic Settings Applies the basic settings that have been selected.
Scan Settings
Scanning Method Allows you to select the preferred scanning method, either
Scan All Files or Scan Files By Type.
Available File Types Lists all of the available file types on the media server.
Available file categories include Video, Audio, Image, and

Other.
Beneath each file category, you can select specific file types to
scan for, or scan all the file types in that category. Once
selected, theses files types will appear in the Selected File
Types section.
Selected File Types Displays the file types that were selected in the Available File
Types section.
Enable scheduled scanning Click the box to enable regularly-scheduled scans. Enter the
every X minutes scan interval in minutes.
Apply Scan Settings Applies the scan settings that have been set.
Scan Now Click this button to begin a scan of the media server.
12 MIB Reference
This section lists the key MIBS used to configure the DDW365. Please use this section for
reference only.
Note: MIBs are usually set and updated in the device’s configuration file.
Topics
 Ubee MIBs on page 103
12.1 Ubee MIBs
12.1.1 UBEE-80211-MGMT-MIB
ifIndex
Type: OBJECT-TYPE
OID: 1.3.6.1.2.1.2.2.1.1
Module: IF-MIB
Parent: ifEntry
Numerical syntax: Integer (32 bit)
Base syntax: Integer32
Composed syntax: InterfaceIndex
Status: current
Max access: read-only
Description: A unique value, greater than zero, for each interface. It is
recommended that values are assigned contiguously starting from 1.
The value for each interface sub-layer must remain constant at
least from one re-initialization of the entity's network
management system to the next re-initialization.
12.1.2 UBEE-CABLEDATAINTERFACE-SMI-MIB
cableDataInterface
Type: MODULE-IDENTITY
OID: 1.3.6.1.4.1.4684.38
Module: UBEE-CABLEDATAINTERFACE-SMI
Parent: ubee
Last updated: 5/20/2009 at 00:00 GMT (200905200000Z)
Organization: Ubee Interactive Corporation
Contact: Ubee Interactive Global Headquarters
Postal: 6F-9, No.38, Taiyuan St.
Jhubei City Hsinchu County 302
Taiwan, R.O.C.
Tel: +886-3-560-0010
E-mail: asupport@ubeeinteractive.com
Description: The Structure of Management Information for the Ubee enterprise
dealing with Cable Modems, Cable Modem Termination Systems, and
related data-over-CATV systems.
Ubee Interactive
12.1.3 UBEE-CABLEDATA-MGMT-MIB
cableDataMgmt
Type: OBJECT-IDENTITY
OID: 1.3.6.1.4.1.4684.38.2.2
Module: UBEE-CABLEDATA-SMI
Parent: cableData
Status: current
Description: cableDataMgmt is the main subtree for new mib development.
12.1.4 UBEE-CABLEHOME-MGMT-MIB
chCsaOperMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.3.1.1
Module: UBEE-CABLEHOME-MGMT-MIB
Parent: chMgmtBase
Base syntax: INTEGER
Composed syntax: INTEGER
Status: current
Max access: read-write
Value list: 1: disabled(0)
2: csa10(1)
Description: Sets the operational mode of the device with regards to CSA
(Commercial Services Annex) support. Note that CSA is defined as
an annex to the CableHome 1.1 specification, so rgOperMode must be
set to cableHome11(4) for this object to be meaningfully set to
any value other than disabled(0).
12.1.5 UBEE-CM-EMTA-MGMT-MIB
cmEmtaBasicFlowDhcpAccept
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.98.1.1.1.1
Module: UBEE-CM-EMTA-MGMT-MIB
Parent: cmEmtaBase
Next sibling: cmEmtaNonSecureFlowDefaultReadCommunity
Composed syntax: TruthValue
Status: current
Default values: 1: false (name)
Reference: PacketCable 1.5 Specification MTA Device Provisioning PKT-SP-
PROV1.5-I03-070412, section 7.2.1, initialization flow MTA2
Description: This object may be used to expedite the acceptance of the EMTA DHCP
offer when option 122.6 of the offer indicates basic or hybrid
provisioning flow.
If set to true(1), DHCP offer rule (b) from MTA initialization flow
MTA2 will not be enforced. This means that the EMTA will not retry
the DHCP discover process in search of an offer which specifies
the secure flow, thus resulting in the EMTA becoming operational
more quickly.
It is important to note that in this configuration the CM is in
violation of the PacketCable provisioning specification.
Ubee Interactive
cmEmtaNonSecureFlowDefaultReadCommunity
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.98.1.1.1.2
Parent: cmEmtaBase
Prev sibling: cmEmtaBasicFlowDhcpAccept
Next sibling: cmEmtaNonSecureFlowDefaultWriteCommunity
Numerical syntax: Octets
Base syntax: OCTET STRING
Composed syntax: OCTET STRING
Status: current
Default values: 1: private (char-str)
Description: The default community string which will be used for read-only
access in the EMTA non-secure provisioning flow. When read, this
object will always return an empty string.
cmEmtaNonSecureFlowDefaultWriteCommunity
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.98.1.1.1.3
Parent: cmEmtaBase
Prev sibling: cmEmtaNonSecureFlowDefaultReadCommunity
Next sibling: cmEmtaRegistrationState
Status: current
Default values: 1: private (char-str)
Description: The default community string which will be used for read-write
access in the EMTA non-secure provisioning flow. When read, this
object will always return an empty string.
cmEmtaRegistrationState
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.98.1.1.1.4
Parent: cmEmtaBase
Prev sibling: cmEmtaNonSecureFlowDefaultWriteCommunity
Next sibling: cmEmtaSafeReset
Status: current
Value list: 1: cmScanning(1)
2: cmRanging(2)
3: cmDhcp(3)
4: cmTftp(4)
5: cmRegistered(5)
6: mtaDhcp(6)
7: mtaTftp(7)
8: mtaProvisioned(8)
9: mtaRsip(9)
10: mtaOperational(10)
11: mtaRejected(11)
Description: Indicates the current state of the CM and EMTA provisioning and
registration process.
cmEmtaSafeReset
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.98.1.1.1.5
Parent: cmEmtaBase
Prev sibling: cmEmtaRegistrationState
Next sibling: cmEmtaPingTestInterval
Ubee Interactive

Status: current
Description: Setting this object to true(1) will cause the device to reset only
when all telephony lines are on-hook. If one or more lines are off-
hook when the reset is invoked then the reset will be queued and
will occur once all lines are on-hook. Reading this object returns
false(2) unless a reset is pending, in which case it returns
true(1). A pending reset may be canceled by setting this object to
false(2).
Note that the behavior of this object is also affected by the
values of objects emtaPostCallCompletionResetDelay and
emtaMaxResetDelay as described in the BRCM-EMTA-MGMT-MIB.
cmEmtaPingTestInterval
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.98.1.1.1.6
Parent: cmEmtaBase
Prev sibling: cmEmtaSafeReset
Next sibling: cmEmtaPingTestFailEMTAThreshold
Numerical syntax: Gauge (32 bit)
Base syntax: Unsigned32
Composed syntax: Unsigned32
Status: current
Default values: 1: 0 (int)")
Units: minutes
Description: This object identifies the time interval, in minutes, that the Emta
should perform a ping test from the eMTA stack to the default
gateway. If set to 0, this feature will be disabled.
cmEmtaPingTestFailEMTAThreshold
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.98.1.1.1.7
Parent: cmEmtaBase
Prev sibling: cmEmtaPingTestInterval
Next sibling: cmEmtaPingTestFailCMThreshold
Status: current
Description: This object identifies the number of consecutive failed ping tests
to trigger an eMTA reset. If set to 0, this feature will be
disabled.
cmEmtaPingTestFailCMThreshold
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.98.1.1.1.8
Parent: cmEmtaBase
Prev sibling: cmEmtaPingTestFailEMTAThreshold
Next sibling: cmEmtaCmSnmpAuthFallbackEnable
Status: current
Description: This object identifies the number of consecutive failed ping tests
to trigger a CM reset and eMTA reset. If set to 0, this feature
will be disabled.
Ubee Interactive
cmEmtaCmSnmpAuthFallbackEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.98.1.1.1.9
Parent: cmEmtaBase
Prev sibling: cmEmtaPingTestFailCMThreshold
Status: current
Description: Setting this object to true(1) will cause SNMP transactions with
the EMTA to be authenticated by the CM's authentication settings
if authentication by EMTA settings fails. This allows use of the
CM's docsDevNmAccessTable, snmpCommunityTable, or SNMPv3 settings
to be applied for EMTA SNMP authentication if desired.
cmEmtaConfigFileEvent
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.98.1.1.2.1
Parent: cmEmtaBfcEvents
Next sibling: cmEmtaLineOutOfServiceEvent
Status: current
Description: An event giving details regarding the EMTA config file. At a
minimum, this event will contain the IP address and path from which
the config file was downloaded.
cmEmtaLineOutOfServiceEvent
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.98.1.1.2.2
Prev sibling: cmEmtaConfigFileEvent
Next sibling: cmEmtaLoopDiagnosticsEvent
Status: current
Description: An event giving details regarding the EMTA config file. At a
minimum, this event will contain the IP address and path from which
the config file was downloaded.
cmEmtaLoopDiagnosticsEvent
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.98.1.1.2.3
Prev sibling: cmEmtaLineOutOfServiceEvent
Status: current
Description: An event indicating the beginning or end of a loop diagnostics
session.
12.1.6 UBEE-CM-MGMT-EXT-MIB
cmMgmtExtBaseStandbySwitchStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.99.4684.2.1.1
Module: UBEE-CM-MGMT-EXT-MIB
Parent: cmMgmtExtBase
Status: current
Value list: 1: on(1)
Ubee Interactive
2: off(2)
Description: Reports/Sets the position of the standby switch.
A GET on this object returns the current state of the standby
switch.
A SET to a value of 'on(1)' enables standby mode for the device.
A SET to a value of 'off(2)' disables standby mode for the device.
When standby-mode is enabled 'on(1)', the device blocks WAN data
traffic to/from the CPEs.
cmScanPushFrequency
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.99.4684.2.2.1
Parent: cmMgmtExtScan
Next sibling: cmScanTable
Composed syntax: Integer32
Status: current
Size list: 1: 0..1000000000
Units: hertz
Description: Setting this object will add a new entry to the cmScanTable. The
new entry will have a cmScanFrequency value equal to the value set
to this object. The index (cmScanIndex) of the new entry will be
1. Any existing entries will be re-indexed starting at 2. If the
table is full, the last entry in the table will be dropped. If the
value set here already exists in the table, it will be moved from
its current position in the table to become entry 1 (a duplicate
entry will not be added). Setting this object to a value of 0 will
flush the cmScanTable. When read, this object always returns 0.
cmScanIndex
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.99.4684.2.2.2.1.1
Parent: cmScanEntry
Next sibling: cmScanFrequency
Status: current
Max access: not-accessible
Size list: 1: 1..128
Description: Identifies the instance of this scan entry.
cmScanFrequency
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.99.4684.2.2.2.1.2
Parent: cmScanEntry
Prev sibling: cmScanIndex
Status: current
Units: hertz
Reference: docsIfDownChannelFrequency from DOCS-IF-MIB
Description: A downstream frequency to which the CM has recently successfully
registered, or which has been provisioned by way of a set to
cmScanPushFrequency.
12.1.7 UBEE-CM-MGMT-MIB
Ubee Interactive
cmNumLLCFiltersSupported
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.1.1
Module: UBEE-CM-MGMT-MIB
Parent: cmMgmtBase
Next sibling: cmNumIpFiltersSupported
Status: current
Reference: docsDevFilterLLCTable from DOCS-CABLE-DEVICE-MIB
Description: Indicates the number of entries in the docsDevFilterLLCTable which
can be supported on this particular device under current operating
conditions. Note that this is a conservative estimate and that the
device will generally be able to support more filters than this
number returns. Further note that this number reflects the number
of filters supported if the docsDevFilterIpTable is also
simultaneously populated with the number of filters returned by
cmNumIpFiltersSupported. If no IP filters are configured then the
device can be expected to support double the number of LLC filters
indicated by this object.
cmNumIpFiltersSupported
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.1.2
Parent: cmMgmtBase
Prev sibling: cmNumLLCFiltersSupported
Next sibling: cmMiniFirewallEnable
Status: current
Reference: docsDevFilterIpTable from DOCS-CABLE-DEVICE-MIB
Description: Indicates the number of entries in the docsDevFilterIpTable which
can be supported on this particular device under current operating
conditions. Note that this is a conservative estimate and that the
device will generally be able to support more filters than this
number returns. Further note that this number reflects the number
of filters supported if the docsDevFilterLLCTable is also
simultaneously populated with the number of filters returned by
cmNumLLCFiltersSupported. If no LLC filters are configured then
the device can be expected to support double the number of IP
filters indicated by this object.
cmMiniFirewallEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.1.3
Parent: cmMgmtBase
Prev sibling: cmNumIpFiltersSupported
Next sibling: cmDsdExtendedRetryEnable
Status: current
Description: Specifies whether the CM mini-firewall will be enabled, provided
the mini-firewall feature is supported. If the feature is not
supported, this object will always report false(2) and an attempt
to set it to true(1) will be rejected with an inconsistentValue
error.
cmDsdExtendedRetryEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.1.4
Ubee Interactive
Parent: cmMgmtBase
Prev sibling: cmMiniFirewallEnable
Next sibling: cmCpeInterface
Status: current
Description: Specifies the behavior of the CM with regards to retrying DSD
requests when no reply is received. If set to true(1), the CM will
continue to retry the request until a reply is received or roughly
one hour of time has passed. If set to false(2), the CM will stop
retrying after three retries as required by the DOCSIS
specification. Note that this setting is not persistent across
reboot.
cmCpeInterface
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.1.5
Parent: cmMgmtBase
Prev sibling: cmDsdExtendedRetryEnable
Next sibling: cmResetFactoryDefaults
Composed syntax: IANAifType
Status: current
Description: For designs which are not capable of supporting multiple CPE
interfaces simultaneously, this object specifies the interface
which will be used as a CPE interface. Typical settings for such
a design would include ethernet(6) and usb(160). For designs which
are capable of supporting multiple CPE interfaces, this object
will always return other(1).
cmResetFactoryDefaults
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.1.6
Parent: cmMgmtBase
Prev sibling: cmCpeInterface
Next sibling: cmTodRefreshInterval
Status: current
Description: Setting this object to true(1) will cause the device to reset all
non-volatile settings to their factory default state, and the
device to be rebooted. Note that only dynamic settings will be
affected; permanent settings (MAC addresses, etc) will remain
unchanged. When read, this object always returns false(2).
cmTodRefreshInterval
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.1.7
Parent: cmMgmtBase
Prev sibling: cmResetFactoryDefaults
Next sibling: cmDownstreamChannelInfoTable
Status: current
Units: hours
Reference: Time Protocol (RFC-868)
Ubee Interactive
Description: This object controls the length of time between periodic updates
of system time by way of a Time of Day (ToD) refresh. If set to 0,
time of day will not be refreshed. Note that in order to comply
with the DOCSIS requirements for ToD periodicity, a value of 0
should be used for this object.
cmHostIpFilterIndex
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.2.1.1.1
Parent: cmHostIpFilterEntry
Next sibling: cmHostIpFilterStatus
Status: current
Size list: 1: 1..2147483647
Description: Identifies the instance number of this conceptual row.
cmHostIpFilterStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.2.1.1.2
Prev sibling: cmHostIpFilterIndex
Next sibling: cmHostIpFilterStorageType
Composed syntax: RowStatus
Status: current
Max access: read-create
Description: The status of this conceptual row.
To create a row in this table, a manager must set this object to
either createAndGo(4) or createAndWait(5).
Until instances of all corresponding columns are appropriately
configured, the value of the corresponding instance of the
cmHostIpFilterStatus column is 'notReady'.
In particular, a newly created row cannot be made active until the
corresponding instances of cmHostIpFilterDestPortLow and
cmHostIpFilterDestPortHigh have been set.
Only filters with a status of active(1) will be applied.
cmHostIpFilterStorageType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.2.1.1.3
Prev sibling: cmHostIpFilterStatus
Next sibling: cmHostIpFilterMatches
Composed syntax: StorageType
Status: current
Default values: 1: volatile (name)
Description: The storage type for this conceptual row. Conceptual rows having
the value 'permanent' need not allow write-access to any columnar
objects in the row.
cmHostIpFilterMatches
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.2.1.1.4
Ubee Interactive
Prev sibling: cmHostIpFilterStorageType
Next sibling: cmHostIpFilterInterfaces
Numerical syntax: Counter (32 bit)
Base syntax: Counter32
Composed syntax: Counter32
Status: current
Description: Counts the number of times this filter was matched.
cmHostIpFilterInterfaces
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.2.1.1.5
Prev sibling: cmHostIpFilterMatches
Next sibling: cmHostIpFilterDirection
Base syntax: BITS
Composed syntax: BITS
Status: current
Value list: 1: cpe(0)
2: cm(1)
Default values: 1: cpe (name)
Description: Identifies the interfaces to which this filter applies.
cmHostIpFilterDirection
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.2.1.1.6
Prev sibling: cmHostIpFilterInterfaces
Next sibling: cmHostIpFilterDestPortLow
Status: current
Value list: 1: inbound(1)
2: outbound(2)
3: both(3)
Default values: 1: inbound (name)
Description: Determines whether the filter is applied to inbound(1) traffic,
outbound(2) traffic, or traffic in both(3) directions.
cmHostIpFilterDestPortLow
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.2.1.1.7
Prev sibling: cmHostIpFilterDirection
Next sibling: cmHostIpFilterDestPortHigh
Status: current
Size list: 1: 0..65535
Description: The inclusive lower bound of the transport-layer destination port
range that is to be matched.
cmHostIpFilterDestPortHigh
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.2.1.1.8
Prev sibling: cmHostIpFilterDestPortLow
Ubee Interactive

Status: current
Size list: 1: 0..65535
Description: The inclusive upper bound of the transport-layer destination port
range that is to be matched.
cmChannelBondingPowerSaveStrategy
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.3.1
Parent: cmChannelBonding
Next sibling: cmChannelBondingUpstreamTable
Status: deprecated
Value list: 1: disabled(-1)
2: cmStatus(0)
3: autonomous1x1(1)
4: cmStatusWith1x1Fallback(2)
Default values: 1: cmStatusWith1x1Fallback (name)
Description: This object has been deprecated in favor of the
powerMgmtCmChannelBondingStrategy object from the UBEE-POWER-
MGMT-MIB.
Determines the channel bonding transition strategy used when the
CM enters reduced power mode due to transition to battery power or
thermal event.
For the purposes of this MIB description, 'reduced power mode'
means a mode of operation in which modem features are intentionally
disabled as a response to a trigger event. It is not related to
measures which may be employed during normal operation with the
goal of improving overall energy efficiency.
When set to a value of disabled(-1), the modem will not change the
channel bonding configuration in response to a transition to
reduced power mode. The device will continue to operate in the
bonding configuration that was in effect at the time the modem
entered reduced power mode.
When set to cmStatus(0), the CM will conform to DOCSIS 3.0
requirements by dispatching a CM-STATUS message to the CMTS with
a type code of 9, 'CM operating on battery backup', indicating a
transition to battery mode. The CMTS is then expected to initiate
a DBC transaction which will reduce the number of channels used by
the CM.
Note that the 'battery backup' event code is used for either type
of trigger, because the CM-STATUS event set does not include
message codes for other reduced power events.
The value of autonomous1x1(1) is used when the CM is operating in
an environment in which the CMTS does not respond to CM-STATUS
messaging for type code 9.
In this mode, upon transition to reduced power mode, the CM will
re-initialize the MAC and re-register, reporting a value of 0 for
the Multiple Transmit Channel Support modem capability and a value
of 0 for the Multiple Receive Channel Support modem capability.
This disables both downstream channel bonding and Multiple
Transmit Channel Mode. The CM will then register in DOCSIS 2.0 1x1
mode, resulting in reduced power consumption.
Note that if a critical data service (such as a telephone call in
the case of a device which includes an eMTA) is in progress, the
MAC re-init will be deferred until the critical operation
Ubee Interactive
completes. Upon transition back to full power mode, the CM will

again re-init the MAC, this time advertising Multiple Transmit
Channel support and Multiple Receive Channel Support to the extent
that the device is capable. Again, the re-init may be deferred if
necessary to avoid interruption of a critical data service.
The default value of cmStatusWith1x1Fallback(2) combines the
cmStatus mode with a fallback to autonomous1x1 mode. Upon
transition to reduced power mode, the CM will dispatch a CM-STATUS
message to the CMTS in an attempt to change to 1x1 mode according
to standard DOCSIS mechanisms. If, after 30 seconds, the CM has
not transitioned to 1x1 mode then the CM will re initialize the
MAC and re-register in 1x1 mode as described above.
cmBondedUsDRWTop
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.3.2.1.1
Parent: cmChannelBondingUpstreamEntry
Next sibling: cmBondedUsDRWBottom
Composed syntax: TenthdBmV
Status: current
Reference: DOCSIS 3.0 MAC and Upper Layer Protocols Interface Specification
CM-SP-MULPIv3.0-I19-120809, sections 8.3.3 'Dynamic Range Window'
and
C.1.5.1.9 'Dynamic Range Window'
Description: This object reports an absolute power level which is the top of
the dynamic range window for this upstream channel.
This value is calculated by applying the value for
Pload_min_set,as specified by the dynamic range window upper edge
TLV in the RNG-RSP or TCC encodings, to the max allowable power
level (Phi) of this particular channel.
This object will return zero if no dynamic range window upper edge
TLV has been specified in either the RNG-RSP or TCC encodings.
cmBondedUsDRWBottom
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.3.2.1.2
Prev sibling: cmBondedUsDRWTop
Next sibling: cmBondedUsDRWViolations
Composed syntax: TenthdBmV
Status: current
CM-SP-MULPIv3.0-I19-120809, sections 8.3.3 'Dynamic Range Window'
and
C.1.5.1.9 'Dynamic Range Window'
Description: This object reports an absolute power level which is the bottom of
the dynamic range window for this upstream channel.
This value is calculated by applying the value for
Pload_min_set,as specified by the dynamic range window upper edge
TLV in the RNG-RSP or TCC encodings, and the fixed 12dB range of
transmit power levels defined by the DRW, to the max allowable
power level (Phi) of this particular channel.
This object will return zero if no dynamic range window upper edge
TLV has been specified in either the RNG-RSP or TCC encodings.
Ubee Interactive
cmBondedUsDRWViolations
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.3.2.1.3
Prev sibling: cmBondedUsDRWBottom
Status: current
CM-SP-MULPIv3.0-I19-120809, section 8.3.3.5 'Power Offset in RNG-
RSP Causing Dynamic Range Window Violation'.
Description: This object counts the number of RNG-RSP power adjustments made by
the CMTS which would cause the CM to violate the constraints of
the dynamic ranging window. Such adjustments (if any) will have
been ignored by the CM in compliance with DOCSIS 3.0 requirements.
cmUcastDsidAllowNonZeroInitialPsn
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.3.3
Prev sibling: cmChannelBondingUpstreamTable
Next sibling: cmStartDsidLearningWhenDccRspArriveSent
Status: current
CM-SP-MULPIv3.0-I19-120809, section 8.2.3 'Sequenced Downstream
Packets'.
Description: Setting this object to true(1) allows the CM to disregard the
requirement that the packet sequence number for a newly created
unicast resequencing DSID must begin at zero. This allows the CM
to recover more quickly when an invalid initial PSN is received
for a unicast DSID.
Note that in order to comply with DOCSIS 3.0 requirements, this
object MUST be set to a value of false(2).
cmStartDsidLearningWhenDccRspArriveSent
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.3.4
Prev sibling: cmUcastDsidAllowNonZeroInitialPsn
Next sibling: cmChannelBondingCapability
Status: current
CM-SP-MULPIv3.0-I19-120809, sections 8.2.3.1 'Downstream
Sequencing'
Description: Setting this object to true(1) causes the CM to discard the next
expected sequence number for all DSIDs when a DCC-RSP (arrive)
message is sent, in case the PSNs are reset by the CMTS at this
time. This allows the CM to bypass the two minute out of range PSN
window and reset the next expected sequence numbers immediately.
Note that in order to comply with DOCSIS 3.0 requirements, this
object MUST be set to a value of false(2).
Ubee Interactive
cmChannelBondingCapability
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.3.5
Prev sibling: cmStartDsidLearningWhenDccRspArriveSent
Next sibling: cmDownstreamNumChannels
Base syntax: BITS
Status: current
Value list: 1: downstream(0)
2: upstream(1)
Default values: 1: downstream,upstream (name)
CM-SP-MULPIv3.0-I19-120809, section C.1.3.1 'Modem Capabilities
Encoding'
Description: This object controls the channel bonding capability of the modem
as advertised in the Multiple Transmit Channel Support (5.24) and
Multiple Receive Channel Support (5.29) fields of the CM's modem
capabilities message.
If the downstream(0) and/or upstream(1) bits are set, then the
modem will advertise the corresponding bonding capability
accurately to the extent supported by the hardware.
If either or both bits are clear, then the modem will advertise
that the corresponding bonding capability is unsupported by using
a value of 0 in the corresponding field.
cmDownstreamNumChannels
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.3.6
Prev sibling: cmChannelBondingCapability
Next sibling: cmUpstreamNumChannels
Status: current
Size list: 1: 0..16
Description: This object reports the number of downstream channels which are
currently in use. The value reported by this object corresponds to
the number of entries in the ifTable with an ifType value of
docsCableDownstream(128)
cmUpstreamNumChannels
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.3.7
Prev sibling: cmDownstreamNumChannels
Next sibling: cmUpstreamMtcMode
Status: current
Size list: 1: 0..16
Description: This object reports the number of upstream channels which are
currently in use. The value reported by this object corresponds to
the number of entries in the ifTable with an ifType value of
docsCableUpstream(129)
Ubee Interactive
cmUpstreamMtcMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.3.8
Prev sibling: cmUpstreamNumChannels
Status: current
CM-SP-MULPIv3.0-I19-120809, sections 8.3 'Upstream Channel
Bonding'
Description: This object reports whether the CM is currently operating in
multiple transmit channel mode as described in the DOCSIS 3.0 MULPI
specification.
Note that it is possible for the CM to be operating in MTC mode
even if only a single upstream channel is in use.
cmConfigFileEvent
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.4.1
Parent: cmBfcEvents
Status: current
Description: An event giving details regarding the CM config file. At a minimum,
this event will contain the IP address and path from which the
config file was downloaded.
cmSpectrumAnalysisFrequency
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.5.1.1.1
Parent: cmSpectrumAnalysisMeasurementEntry
Next sibling: cmSpectrumAnalysisAmplitudeData
Status: current
Description: This object indicates the center frequency of the spectral
analysis segment.
cmSpectrumAnalysisAmplitudeData
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.5.1.1.2
Parent: cmSpectrumAnalysisMeasurementEntry
Prev sibling: cmSpectrumAnalysisFrequency
Composed syntax: AmplitudeData
Status: current
Description: This object provides a list of the measured spectral amplitudes
for the segment corresponding to the center frequency specified by
the cmSpectrumAnalysisFrequency object.
The frequency bins are ordered from lowest to highest frequencies
covering the frequency span of the segment. Information about the
center frequency, frequency span, number of bins and resolution
bandwidth are included to provide context to the measurement
point.
Bin Amplitudes are reported in units of 0.01dB.
Ubee Interactive
cmSpectrumAnalysisEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.5.2
Parent: cmSpectrumAnalysis
Prev sibling: cmSpectrumAnalysisMeasurementTable
Next sibling: cmSpectrumAnalysisInactivityTimeout
Status: current
Description: This object is used to enable or disable the spectrum analyzer
feature. By default, the feature is disabled unless explicitly
enabled. Note that the feature may be disabled by the system under
certain circumstances if the spectrum analyzer would affect
critical services. In such a case, the object will return 'false'
when read, and will reject sets to 'true' with an
'inconsistentValue' error.
cmSpectrumAnalysisInactivityTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.5.3
Prev sibling: cmSpectrumAnalysisEnable
Next sibling: cmSpectrumAnalysisDiagnosticMode
Status: current
Size list: 1: 0..86400
Units: seconds
Description: This object controls the length of time after the last spectrum
analysis measurement before the feature is automatically disabled.
If set to a value of 0, the feature will remain enabled until it
is explicitly disabled.
cmSpectrumAnalysisDiagnosticMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.5.4
Prev sibling: cmSpectrumAnalysisInactivityTimeout
Next sibling: cmSpectrumAnalysisFirstSegmentCenterFrequency
Status: current
2: squareWave(1)
3: lockData(2)
Default values: 1: disabled (name)
Description: This object may be used to enter a diagnostic mode of operation
for the spectrum analyzer. When set to disabled (0), diagnostic
mode is disabled and the spectrum analyzer will operate normally.
When operating in one of the diagnostic modes, no actual
measurements will be performed. Instead, a test pattern will be
returned.
squareWave(1): a square wave will be generated with a period of
20MHz and a 50% duty cycle.
Ubee Interactive
lockData(2): actual spectrum measurement will be suspended, and

data returned will be that which was collected by the most recent
measurement.
cmSpectrumAnalysisFirstSegmentCenterFrequency
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.5.5
Prev sibling: cmSpectrumAnalysisDiagnosticMode
Next sibling: cmSpectrumAnalysisLastSegmentCenterFrequency
Status: current
Size list: 1: 0..1070000000
Units: hertz
Description: This object controls the center frequency of the first segment for
the spectrum analysis measurement. The frequency bins for this
segment lie symmetrically to the left and right of this center
frequency. If the number of bins in a segment is odd, the segment
center frequency lies directly on the center bin. If the number of
bins in a segment is even, the segment center frequency lies
halfway between two bins. Changing the value of this object may
result in changes to the cmSpectrumAnalysisMeasurementTable, as
described in the description field for the table. Note that if this
object is set to an invalid value, the device may return an error
of inconsistentValue, or may adjust the value of the object to the
closest valid value.
cmSpectrumAnalysisLastSegmentCenterFrequency
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.5.6
Prev sibling: cmSpectrumAnalysisFirstSegmentCenterFrequency
Next sibling: cmSpectrumAnalysisSegmentFrequencySpan
Status: current
Size list: 1: 0..1070000000
Units: hertz
Description: This object controls the center frequency of the last segment for
the spectrum analysis measurement. The frequency bins for this
segment lie symmetrically to the left and right of this center
frequency. If the number of bins in a segment is odd, the segment
center frequency lies directly on the center bin. If the number of
bins in a segment is even, the segment center frequency lies
halfway between two bins. Changing the value of this object may
result in changes to the cmSpectrumAnalysisMeasurementTable, as
described in the description field for the table. Note that if this
object is set to an invalid value, the device may return an error
of inconsistentValue, or may adjust the value of the object to the
cmSpectrumAnalysisSegmentFrequencySpan
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.5.7
Prev sibling: cmSpectrumAnalysisLastSegmentCenterFrequency
Next sibling: cmSpectrumAnalysisBinsPerSegment
Ubee Interactive

Status: current
Size list: 1: 0
2: 1000000..1070000000
Units: hertz
Description: This object controls the frequency span of each segment (row) in
the cmSpectrumAnalysisMeasurementTable. If set to a value of 0,
then a default span will be chosen based on the hardware
capabilities of the device. Segments are contiguous from the
FirstSegementCenterFrequency to the LastSegmentCenterFrequency
and the center frequency for each successive segment is
incremented by the SegmentFequencySpan. The number of segments may
be calculated as (LastSegmentCenterFrequency -
FirstSegmentCenterFrequency) / (SegmentFrequencySpan + 1) Each
segment is represented by a row in the
cmSpectrumAnalysisMeasurementTable. Changing the value of this
object may result in changes to the
cmSpectrumAnalysisMeasurementTable, as described in the
description field for the table. Note that if this object is set
to an invalid value, the device may return an error of
inconsistentValue, or may adjust the value of the object to the
cmSpectrumAnalysisBinsPerSegment
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.5.8
Prev sibling: cmSpectrumAnalysisSegmentFrequencySpan
Next sibling: cmSpectrumAnalysisWindowFunction
Status: current
Size list: 1: 0
2: 2..2048
Description: This object controls the number of bins collected by the
measurement performed for each segment (row) in the
cmSpectrumAnalysisMeasurementTable. If set to a value of 0, then
an optimal number of bins will be chosen based on the hardware
capabilities of the device. Note that if this object is set to an
invalid value, the device may return an error of
inconsistentValue, or may adjust the value of the object to the
cmSpectrumAnalysisWindowFunction
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.5.9
Prev sibling: cmSpectrumAnalysisBinsPerSegment
Next sibling: cmSpectrumAnalysisEquivalentNoiseBandwidth
Status: current
Value list: 1: other(0)
2: hann(1)
3: blackmanHarris(2)
4: rectangular(3)
5: hamming(4)
6: flatTop(5)
7: gaussian(6)
8: chebyshev(7)
Default values: 1: hann (name)
Ubee Interactive
Reference: Harris, Fredric J. (Jan 1978). 'On the use of Windows for Harmonic
Analysis with the Discrete Fourier Transform'. Proceedings of the
IEEE 66 (1): 51?3. doi:10.1109/PROC.1978.10837
Description: This attribute controls the window function which will be used when
performing the discrete Fourier transform for the analysis. The
equivalent noise bandwidth for the function which is in use will
be reported by the cmSpectrumAnalysisEquivalentNoiseBandwidth
object. Note that all window functions may not be supported by all
devices. If an attempt is made to set the object to an unsupported
window function, an error of inconsistentValue will be returned.
cmSpectrumAnalysisEquivalentNoiseBandwidth
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.5.10
Prev sibling: cmSpectrumAnalysisWindowFunction
Status: current
Size list: 1: 100..225
Units: hundredth bins
Reference: Harris, Fredric J. (Jan 1978). 'On the use of Windows for Harmonic
Analysis with the Discrete Fourier Transform'. Proceedings of the
IEEE 66 (1): 51?3. doi:10.1109/PROC.1978.10837
Description: This object allows the user to request an equivalent noise
bandwidth for the resolution bandwidth filter used in the spectrum
analysis. This corresponds to the spectral width of the window
function used when performing a discrete Fourier transform for the
analysis. A list of equivalent noise bandwidth values for common
window functions may be found in Table 1 of the paper identified
in the reference clause of this object. The window function which
corresponds to a value written to this object may be obtained by
reading the value of cmSpectrumAnalysisWindowFunction. If an
unsupported value is requested, the device may return an error of
inconsistentValue, or choose the closest valid value to the one
which is requested. If the closest value is chosen, then a
subsequent read of this object will return the actual value which
is in use.
cmBaseGroup
Type: OBJECT-GROUP
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.100.2.1
Parent: cmGroups
Next sibling: cmFilterGroup
Status: current
Objects: 1: cmNumLLCFiltersSupported
2: cmNumIpFiltersSupported
3: cmMiniFirewallEnable
4: cmDsdExtendedRetryEnable
5: cmCpeInterface
6: cmResetFactoryDefaults
7: cmTodRefreshInterval
8: cmDsChanInfoCodewordErrorRate
9: cmDsChanInfoMeanSquareError
10: cmIpProvisioningMode
11: cmServiceQueueId
12: cmServiceQueueMaxQueueDepth
13: cmServiceQueueCurrentQueueDepth
14: cmForwardingHwAssistEnable
15: cmOverrideUcdMaxBurst
16: cmExtendedUsTxPowerCapability
Description: A set of objects supported by all agents which implement this MIB.
Ubee Interactive
cmFilterGroup
Type: OBJECT-GROUP
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.100.2.2
Parent: cmGroups
Prev sibling: cmBaseGroup
Next sibling: cmChannelBondingGroup
Status: current
Objects: 1: cmHostIpFilterStatus
2: cmHostIpFilterStorageType
3: cmHostIpFilterMatches
4: cmHostIpFilterInterfaces
5: cmHostIpFilterDirection
6: cmHostIpFilterDestPortLow
7: cmHostIpFilterDestPortHigh
Description: A set of objects supported by agents which support CM extended
filtering as described by this MIB.
cmChannelBondingGroup
Type: OBJECT-GROUP
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.100.2.3
Parent: cmGroups
Prev sibling: cmFilterGroup
Next sibling: cmSpectrumAnalysisGroup
Status: current
Objects: 1: cmChannelBondingPowerSaveStrategy
2: cmBondedUsDRWTop
3: cmBondedUsDRWBottom
4: cmBondedUsDRWViolations
5: cmUcastDsidAllowNonZeroInitialPsn
6: cmStartDsidLearningWhenDccRspArriveSent
7: cmChannelBondingCapability
Description: A set of objects supported by agents for products which support
channel bonding.
cmSpectrumAnalysisGroup
Type: OBJECT-GROUP
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.100.2.4
Parent: cmGroups
Prev sibling: cmChannelBondingGroup
Next sibling: cmNotificationGroup
Status: current
Objects: 1: cmSpectrumAnalysisFrequency
2: cmSpectrumAnalysisAmplitudeData
3: cmSpectrumAnalysisEnable
4: cmSpectrumAnalysisInactivityTimeout
Description: A set of objects supported by agents for products which support
spectrum analysis capability.
cmNotificationGroup
Type: NOTIFICATION-GROUP
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.2.100.2.99
Parent: cmGroups
Prev sibling: cmSpectrumAnalysisGroup
Status: current
Notifications: 1: cmDocsDevEventTrap
2: cmMDDTimeoutTrap
Description: CM notifications
Ubee Interactive
12.1.8 UBEE-EMTA-MGMT-MIB
emtaInhibitSwDownloadDuringCall
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.1
Module: UBEE-EMTA-MGMT-MIB
Parent: emtaMgmtBase
Next sibling: emtaFirewallEnable
Status: current
Description: This object controls the processing logic of software downloading
requests when there are specific telephony related EMTA
activities. If this object has a value of true(1), DOCSIS software
download by way of the docsDevSwAdminStatus MIB object will be
inhibited if the value of esafeDevServiceIntImpact for the eMTA
entry has a value of significant(1), indicating a call in progress.
If docsDevSwAdminStatus is set to upgradeFromMgt(1) under these
conditions, an error code of resourceUnavailable(13) will be
returned and an appropriate event logged to the CM event log.
emtaFirewallEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.2
Prev sibling: emtaInhibitSwDownloadDuringCall
Next sibling: emtaRingWithDCOffset
Status: current
Default values: 1: true (name)
Description: This object specifies whether the eMTA lightweight firewall is
enabled or disabled
emtaRingWithDCOffset
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.3
Prev sibling: emtaFirewallEnable
Next sibling: emtaIncludedInCmMaxCpe
Status: current
Description: This object specifies whether the ring with DC offset option is
enabled. Note that in order for the EMTA to be able to apply DC
offset to ring signal it must support high voltage ring
(emtaHighVoltageRingEnabled is true(1). An attempt to set this
object to true while emtaHighVoltageRingEnabled is false(2) will
result in an 'inconsistent value' error.
emtaIncludedInCmMaxCpe
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.4
Prev sibling: emtaRingWithDCOffset
Next sibling: emtaDhcpOption
Ubee Interactive

Status: current
Reference: CM-SP-eDOCSIS-I05-050408 section 5.2.2
Description: This object specifies whether the EMTA MAC address will be included
when calculating the number of CPEs allowed by the CM as specified
in the CM configuration file. Setting of the MIB takes effect on
the next re-boot. Note that the eDOCSIS specification requires the
value of this object to be true(1) and setting it to false(2) will
violate the spec and render the device uncertifiable.
emtaDhcpOption
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.5
Prev sibling: emtaIncludedInCmMaxCpe
Next sibling: emtaUseAlternateTelephonyRootCert
Status: current
Value list: 1: cableLabsClientConfiguraton(122)
2: packetCableAndCableHomeObsolete(177)
Default values: 1: cableLabsClientConfiguraton (name)
Reference: http://www.iana.org/assignments/bootp-dhcp-parameters; RFC 3495,
DHCP Option for CableLabs Client Configuration.
Description: This object specifies the value of the PacketCable DHCP option
which will be used in MTA provisioning. Current PacketCable 1.x
Provisioning Specification requires value 122, but certain legacy
systems still use the currently obsolete value of 177.
emtaUseAlternateTelephonyRootCert
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.6
Prev sibling: emtaDhcpOption
Next sibling: emtaEnableDQoSLite
Status: current
Description: This object controls which telephony root certificate the MTA will
be using during its authentication phases. As per PacketCable 1.x,
the telephony root certificate should be used so that it can be
modified by way of a firmware upgrade if necessary. However, the
alternate certificate may sometimes be required for testing,
development, or other special situations. If set to true(1), the
EMTA will use the alternate telephony root certificate as
provisioned in non-volatile storage. If set to false(2), the EMTA
will use the telephony root certificate which is embedded in the
firmware image.
emtaEnableDQoSLite
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.7
Prev sibling: emtaUseAlternateTelephonyRootCert
Next sibling: emtaInhibitNcsSyslog
Ubee Interactive
Status: current
Description: This object specifies whether DQoS Lite is enabled. When enabled,
gateid enforcement is disabled, which makes the EMTA use
serviceflows (lite DQoS) even in absence of gate IDs. When DQoS
lite is disabled, gate ID enforcement on the EMTA is enabled, which
makes the EMTA use real DQoS (no lite DQoS).
emtaInhibitNcsSyslog
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.8
Prev sibling: emtaEnableDQoSLite
Next sibling: emtaVoiceThreadState
Status: current
Description: This object controls the logging of the NCS messages to Syslog.
Generally, reporting of the events with NCS messages is following
the PacketCable 1.x MEM Specificaition and Event MIB
Specificaition. However, if this object has a value of true(1),
logging of the NCS messages to syslog is inhibited. Otherwise, NCS
logging control logic follows the requirements of the PacketCable
1.x Event MIB. The MTA must not persist this MIB object.
emtaVoiceThreadState
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.9
Prev sibling: emtaInhibitNcsSyslog
Next sibling: emtaPhsConfiguration
Status: current
Value list: 1: initializing(1)
2: notStarted(2)
3: runningOk(3)
4: runTimeError(4)
Description: This object indicates the state of the MTA's voice processing.
initializing(1) - the voice processing is in the process of
initializing.
notStarted(2) - the voice processing thread did not start
correctly. An MTA reset may be necessary.
runningOk(3) - the voice processing has been initialized, and is
operating normally.
runTimeError(4)- indicates there was an error in the operation of
the voice processing,and the MTA is unable to perform voice
processing.
emtaPhsConfiguration
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.10
Prev sibling: emtaVoiceThreadState
Next sibling: emtaMaxResetDelay
Ubee Interactive

Status: current
Value list: 1: enabled(1)
2: disabled(2)
Description: This object controls the application of Payload Header Suppression
(PHS) to voice RTP traffic. When disabled(2), PHS is applied to
neither upstream nor downstream RTP traffic. When enabled(1), PHS
is applied to both upstream and downstream RTP traffic. Note that
if this object is set to enabled(1), specific fields may be
selected for supression by use of the emtaPhsUpstreamMask and
emtaPhsUpstreamMask objects.
emtaMaxResetDelay
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.11
Prev sibling: emtaPhsConfiguration
Next sibling: emtaPostCallCompletionResetDelay
Status: current
Size list: 1: 0..86400
Units: seconds
Description: This object, along with emtaPostCallCompletionResetDelay,
controls the behavior of the device when one or more voice lines
is off-hook, and a reset becomes pending due to completion of
software download or due to a set of cmEmtaSafeReset from the BRCM-
CM-EMTA-MGMT-MIB.
The object emtaPostCallCompletionResetDelay is used to prevent
interruption of an active voice call due to either of these reset
conditions, as described in that object's description clause.
This object provides a safeguard against the possibility of a reset
being postponed indefinitely should a voice line remain off-hook
for an extended period of time. It may also be used to cause the
reset to occur immediately regardless of hook state, as required
by DOCSIS.
When a software download completes or a reset is invoked via
cmEmtaSafeReset, a timer will begin to run for the duration
specified by the value of this object. Note that the timer begins
to run when the reset becomes pending, not when all voice lines
return to hook.
When the timer expires, an event will be logged (and possibly a
syslog message dispatched) which indcates that a reset is pending.
At that time the timer will be started a second time, and when the
timer expires a second time the device will be reset regardless of
voice line hook state.
Note that, because the timer must expire two times before the
device is reset, the reset will not occur until twice the number
of seconds specified by this object have elapsed (unless the
conditions set by emtaPostCallCompletionResetDelay are met first).
When this object has the default value of 0, the functionality of
the emtaPostCallCompletionResetDelay object is effectively
disabled and the device will reboot immediately following a
software upgrade, as required by DOCSIS. The use of the default
value of 0 for this object also causes the cmEmtaSafeReset object
behave exactly as the docsDevResetNow object.
Ubee Interactive
emtaPostCallCompletionResetDelay
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.12
Prev sibling: emtaMaxResetDelay
Next sibling: emtaDhcpRebindRule
Status: current
Size list: 1: 0..3600
Units: seconds
Description: This object, along with emtaMaxResetDelay, controls the behavior
of the device when one or more voice lines is off-hook, and a reset
is pending due to completion of software download or due to a set
of cmEmtaSafeReset from the BRCM-CM-EMTA-MGMT-MIB.
This object prevents an active voice call from being interrupted
due to either of these reset conditions occuring when a call is in
progress.
If a reset for one of these reasons becomes pending when a voice
line is off-hook, the reset will not take place until all lines
have returned to hook and the number of seconds specified by this
object have elapsed. If a voice line goes off-hook before the timer
expires, the timer will be reset and will begin to run again when
all lines have returned to hook.
Use of the default value of 0 seconds means that the device will
reset immediately once all voice lines have returned to hook.
The length of time that a reset which is pending may be delayed by
the value of this object is limited by the value of
emtaMaxResetDelay, as described in the description clause for that
object. If the value of emtaMaxResetDelay has the default value of
0 then the functionality of this object is effectively disabled.
emtaDhcpRebindRule
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.13
Prev sibling: emtaPostCallCompletionResetDelay
Next sibling: emtaDhcpIgnoreNaks
Status: current
Value list: 1: strict(1)
2: relaxed(2)
Default values: 1: strict (name)
Reference: RFC 2131 Dynamic Host Configuration Protocol
Description: This object is used to control the DHCP client behaviour for the
MTA when a DHCP REBIND (T2 timeout) occurs. The value strict will
only allow the MTA to accept a valid DHCP ACK only from the DHCP
server that provided the initial lease. The value relaxed will
allow the MTA to accept a valid DHCP ACK from any DHCP server.
emtaDhcpIgnoreNaks
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.14
Prev sibling: emtaDhcpRebindRule
Next sibling: emtaCountryCode
Ubee Interactive

Status: current
2: disabled(2)
Description: Controls client behavior regarding DHCP NAKs. If set to
enabled(1), the DHCP client will handle NAKs from the server by
entering a special state where renewing/rebinding stops, but the
IP address continues to be used until the lease expires. If set to
disabled(2), the DHCP client will handle NAKs per the requirements
from RFC-2131.
emtaCountryCode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.15
Prev sibling: emtaDhcpIgnoreNaks
Next sibling: emtaPhsUpstreamMask
Composed syntax: SnmpAdminString
Status: current
Size list: 1: 2
Reference: ISO 3166-1
Description: This object contains the country code according to ISO Country Code
Standard (eg. the code for United States is 'us'). Two additional
codes not part of the ISO standard are supported: 'ei' for ETSI
and '57' for TR-57. This object must only be provided via the
configuration file during the provisioning process. If the country
code is set to an unsupported country in the image, MTA will use
the default country code based on build specific options for the
image.
emtaPhsUpstreamMask
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.16
Prev sibling: emtaCountryCode
Next sibling: emtaPhsDownstreamMask
Base syntax: BITS
Status: current
Value list: 1: ethDA(0)
2: ethSA(1)
3: ethEthertype(2)
4: ipVersionIHL(3)
5: ipTOS(4)
6: ipTotalLength(5)
7: ipIdent(6)
8: ipFlagsFragOffset(7)
9: ipTTL(8)
10: ipProtocol(9)
11: ipHeaderChecksum(10)
12: ipSA(11)
13: ipDA(12)
14: udpSourcePort(13)
15: udpDestPort(14)
16: udpLength(15)
17: udpChecksum(16)
Ubee Interactive
Description: This object sets the PHS mask for upstream voice DQoS flows using
IPv4 addressing. Setting a bit to '1' will cause the MTA to
suppress this field for upstream voice flows. The default
configuration is all bits set except for ipTotalLength(5),
ipHeaderChecksum(10), and udpLength(15) since these fields are
required to properly handle connections using silence suppression.
If silence supression will never be enabled, all bits may be set.
Note that this setting only applies if emtaPhsConfiguration is set
to enabled(1). If emtaPhsConfiguration is set to disabled(2), then
the value of this object will be ignored.
emtaPhsDownstreamMask
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.17
Prev sibling: emtaPhsUpstreamMask
Next sibling: emtaPhsDownstreamVerification
Base syntax: BITS
Status: current
Value list: 1: ethEthertype(0)
2: ipVersionIHL(1)
3: ipTOS(2)
4: ipTotalLength(3)
5: ipIdent(4)
6: ipFlagsFragOffset(5)
7: ipTTL(6)
8: ipProtocol(7)
9: ipHeaderChecksum(8)
10: ipSA(9)
11: ipDA(10)
12: udpSourcePort(11)
13: udpDestPort(12)
14: udpLength(13)
15: udpChecksum(14)
Description: This object sets the PHS mask for downstream voice DQoS flows using
IPv4 addressing. Setting a bit to '1' will cause the CMTS to
suppress this field for downstream voice flows.
The default configuration is the ethEthertype(0), ipVersionIHL(1),
ipIdent(4), ipFlagsFragOffset(5), ipProtocol(7), ipSA(9),
ipDA(10), and udpDestPort(12) bits are set.
If silence supression will never be enabled, ipTotalLength(3)and
udpLength(13) may also be set.
If silence supression will never be enabled and
emtaPhsDownstreamVerification is set to either disabled(2) or
auto(3), all bits may be set.
emtaPhsDownstreamVerification
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.18
Prev sibling: emtaPhsDownstreamMask
Next sibling: emtaUgsAdControl
Status: current
Ubee Interactive
2: disabled(2)
3: auto(3)
Description: This object controls whether or not the MTA requests PHS
verification (PHSV) by the CMTS on downstream PHS operations. The
default is auto(3).
When set to auto(3), the MTA will automatically disable PHSV if
the ipTOS(2), ipTTL(6), ipHeaderChecksum(8) or udpChecksum(14)
bits are set in emtaPhsDownstreamMask.
When set to disabled(2), the MTA will disable PHSV at all times.
When set to enabled(1), the MTA will enable PHSV at all times.
This setting should be used with caution as it is possible to
create a non-working configuration if verification is enabled and
a non-predictable downstream field (eg ipTTL) is suppressed.
emtaUgsAdControl
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.19
Prev sibling: emtaPhsDownstreamVerification
Next sibling: emtaDnsBaseTimeout
Status: current
Description: This object specifies whether the UGS-AD scheduling type is
enabled. When set to true(1), if silence suppression is on, UGS-
AD will be selected. When set to false(2), the UGS-AD is disabled,
meaning UGS will be selected regardless of the silence suppression
parameter. If the UGS-AD control is changed through SNMP, then this
change will take effect starting with the next phone call (in
process calls are not affected). The default value of this object
is true(1) for UGS-AD enabled, which corresponds to the
functionality compliant with the PacketCable requirements (DQoS
PC1.5 specification section 6.1.2.1).
emtaDnsBaseTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.20
Prev sibling: emtaUgsAdControl
Next sibling: emtaDnsMaxRetry
Status: current
Size list: 1: 100..30000
Units: milliseconds
Description: This object controls the base timeout value for DNS queries. The
DNS client DNS query times out due to no response from the DNS
server. The EMTA DNS resolver waits this period of time before
sending the next DNS Query if no response is received from the DNS
server. This is exponentially increased on subsequent DNS queries
for the same transaction.
Ubee Interactive
emtaDnsMaxRetry
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.21
Prev sibling: emtaDnsBaseTimeout
Next sibling: emtaDnsNegativeCacheTTL
Status: current
Size list: 1: 1..8
Description: This object controls the maximum retry value for a DNS query. When
a DNS query times out due to no response from the DNS server, this
is the maximum number of times that a DNS query is re-sent.
emtaDnsNegativeCacheTTL
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.22
Prev sibling: emtaDnsMaxRetry
Next sibling: emtaEmSvcTrafficPriority
Status: current
Size list: 1: 10..4294967295
Units: seconds
Description: This object controls the maximum TTL value for DNS negative cache
PRs. When a DNS query results in a response of NXDOMAIN, NODATA or
SRVFAIL, and no SOA RR is included in the response, or due to a
non-responsive DNS server, the EMTA DNS resolver caches the
negative RR with this TTL value.
emtaEmSvcTrafficPriority
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.23
Prev sibling: emtaDnsNegativeCacheTTL
Next sibling: emtaDevHDAudioEnabled
Status: current
Size list: 1: 5..6
Description: This object controls the DOCSIS Traffic Priority used in the
service flow for outgoing calls to an emergency service provider.
Note that the default value of this object may change based on
build specific options.
emtaDevHDAudioEnabled
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.24
Prev sibling: emtaEmSvcTrafficPriority
Next sibling: emtaDevG72264PayloadType
Ubee Interactive
Status: current
Description: This MIB is used to enabled or disable HD Audio functionality
across the entire device. A value of false will cause the device,
across all lines, to suppress any indication during call
negotiation that the device supports HD audio and takes precedence
over all other MIBs that have the ability to enable and/or disable
HD voice functionality. When this MIB is set to true, then the
device will allow HD audio functionality to be advertised during
call negotiation according to other MIBs that have the ability to
enabled or disable HD voice functionality.
emtaDevG72264PayloadType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.1.25
Prev sibling: emtaDevHDAudioEnabled
Status: current
Value list: 1: g722StaticPayloadType(1)
2: g722DynamicPayloadType(2)
Default values: 1: g722StaticPayloadType (name)
Description: This MIB controls the mode of interpretation of the label 'G722-
64' in the Local Connection Options (LCO's) of any message from a
NCS based switch (where LCO is permitted by the Packet Cable 1.5
spec and where codec labels are permitted in the LCO). The
following modes are supported:
g722StaticPayloadType(1): the device interprets 'G722-64' as a
request for the G722 static codec (64 kb/s) and responds with
static codec '9' in the SDP.
g722DynamicPayloadType(2): the device interprets 'G722-64' as a
request for the G722 dynamic codec (64 kb/s) and responds with the
appropriate dynamic codec entries in the SDP.
emtaMaintenanceWindowBegin
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.2.1
Parent: emtaMgmtMaintenance
Next sibling: emtaMaintenanceWindowDuration
Composed syntax: DateAndTime
Status: current
Description: This object identifies the start of an eMTA maintenance window. A
maintenance window is a period of time during which the ISP may
perform network maintenance operations and network outages or
software resets may occur. During a maintenance window, the eMTA
will maintain the line voltage of an MTA regardless of CM resets,
MTA resets, or RF losses. If any of these conditions occurs or
persists outside of the scheduled maintenance window then the line
voltage will be dropped unless the corresponding bit for the
condition in question is set in the emtaMaintenanceControlMask
MIB. If this object has never been set, it will have the value of
midnight, January 1, 1970. Note that the time value used here is
the local time as known by the device, as opposed to UTC. Also note
that the value of this object will persist across a system reboot.
Note that in order to be compliant with (E)PC 1.5 Certification,
PacketCable 1.5 builds will use the MIBs in
pktcEnNcsEndPntLVMgmtTable instead of the emtaMaintenance MIBs by
default.
Ubee Interactive
emtaMaintenanceWindowDuration
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.2.2
Prev sibling: emtaMaintenanceWindowBegin
Next sibling: emtaMaintenanceControlMask
Status: current
Units: seconds
Description: This object identifies the duration, in seconds, of an eMTA
maintenance window. Setting the value of this object to the default
value of zero will cancel the maintenance window. Note that the
value of this object will persist across a system reboot. Note that
in order to be compliant with (E)PC 1.5 Certification, PacketCable
1.5 builds will use the MIBs in pktcEnNcsEndPntLVMgmtTable instead
of the emtaMaintenance MIBs by default.
emtaMaintenanceControlMask
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.2.3
Prev sibling: emtaMaintenanceWindowDuration
Next sibling: emtaMaintenanceQuarantineTimeout
Base syntax: BITS
Status: current
Value list: 1: maintenanceOnCmReset(0)
2: maintenanceOnRFLoss(1)
3: maintenanceOnMtaReset(2)
4: maintenanceOnCMSLoss(3)
Description: This object identifies the bit mask to control the line voltage
behavior of the eMTA in various scenarios:
maintenanceOnCmReset(0) - if this bit is set to 1 it requires the
line voltage be maintained in the case when the CM has been reset,
regardless of the reason (reset after downloading a new firmware,
or hard reboot, or SNMP induced CM reset), and regardless of
whether the MTA is in a valid maintenance window
maintenanceOnRFLoss(1) - if this bit is set to 1 it requires the
line voltage be maintained in the case when RF communication is
lost, regardless of the reason, and regardless of whether the MTA
is in a valid maintenance window
maintenanceOnMtaReset(2) - if this bit is set to 1 it requires the
line voltage be maintained in the case when the eMTA is being
reset, regardless of the reason (e.g. SNMP induced eMTA
reset,etc), and regardless of whether the MTA is in a valid
maintenance window
maintenanceOnCMSLoss(3) - if this bit is set to 1 it requires the
line voltage be maintained in the case when communication is lost
with the CMS, regardless of the reason (e.g. endpoint
disconnected, etc), and regardless of whether the duration of the
communication loss has exceeded the value in the MIB
emtaMaintenanceQuarantineTimeout and/or
emtaMaintenanceDisconnectedTimeout
The default value of this object may change based on build specific
options. However, it's highly recommended that the default value
in the image submitted for (E)PC 1.x Certification be chosen in
Ubee Interactive
such a way that it will correspond to the functionality compliant

with the PacketCable requirements and will preserve the backward
compatibility with the previously certified behaviour.
Note that to satisfy the latter, 'maintenanceOnCMSLoss(3)' bit
should be set by default.
Also, note that in order to be compliant with (E)PC 1.5
Certification, PacketCable 1.5 builds will use the MIBs in
default.
emtaMaintenanceQuarantineTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.2.4
Prev sibling: emtaMaintenanceControlMask
Next sibling: emtaMaintenanceDisconnectedTimeout
Status: current
Units: seconds
Description: This object identifies the length of time, in seconds, that the
MTA should maintain the line voltage after any of the endpoints
enters the quarantine state. If any of the endpoints remains in
the quarantine state for longer than this period the line voltage
is dropped unless the maintenanceOnCMSLoss bit is set in the
emtaMaintenanceControlMask MIB. Note that the value of this object
will persist across a system reboot. Note that in order to be
compliant with (E)PC 1.5 Certification, PacketCable 1.5 builds
will use the MIBs in pktcEnNcsEndPntLVMgmtTable instead of the
emtaMaintenance MIBs by default.
emtaMaintenanceDisconnectedTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.2.5
Prev sibling: emtaMaintenanceQuarantineTimeout
Next sibling: emtaMaintenanceRFDisconnectTimeout
Status: current
Units: seconds
MTA should maintain the line voltage after any of the endpoints is
disconnected. If any of the endpoints remains disconnected for
longer than this period the line voltage is dropped unless the
maintenanceOnCMSLoss bit is set in the emtaMaintenanceControlMask
MIB. Note that the value of this object will persist across a
system reboot. Note that in order to be compliant with (E)PC 1.5
default.
emtaMaintenanceRFDisconnectTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.2.6
Prev sibling: emtaMaintenanceDisconnectedTimeout
Ubee Interactive

Status: current
Size list: 1: 0..3600
Units: seconds
MTA should maintain the line voltage after the RF lock with the
CMTS is lost. If the MTA remains disconnected from the CMTS for
longer than this period the line voltage is dropped unless the
maintenanceOnRFLoss bit is set in the emtaMaintenanceControlMask
MIB. Note that the value of this object will persist across a
system reboot. Note that in order to be compliant with (E)PC 1.5
default.
emtaBattReplaceCtrl
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.3.1
Parent: emtaMgmtBatteryControl
Status: deprecated
Units: percent
Description: This object contains the value which controls the nominal load
percentage triggering a 'Replace Battery' Telemetry Signal.
Default valule of the MIB Object is 55%.
emtaSignalingEndptCtrlAnalogLoopback
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.1
Parent: emtaSignalingEndptCtrlEntry
Next sibling: emtaSignalingEndptCtrlLineReset
Status: current
Description: This oject controls the implementation of the analog loopback by
the MTA. When the object is set to true(1), the MTA MUST implement
an analog loopback operations. When the object is set to false(2),
the MTA MUST stop loopback operations immediately. The default
value of this object corresponds to the functionality compliant
with the PacketCable requirements.
emtaSignalingEndptCtrlLineReset
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.2
Prev sibling: emtaSignalingEndptCtrlAnalogLoopback
Next sibling: emtaSignalingEndptCtrlDiagTestsStart
Status: current
Ubee Interactive
Description: This object congrols the resetting the telephone line. Setting
this object to true(1) causes the eMTA to reset the telephone line
of the corresponding endpoint. Setting this object to false(2)
does not have any affect. Reading this object always returns
'false(2)'.
emtaSignalingEndptCtrlDiagTestsStart
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.3
Prev sibling: emtaSignalingEndptCtrlLineReset
Next sibling: emtaSignalingEndptCtrlDiagTestsStop
Base syntax: BITS
Status: current
Value list: 1: startTipToGroundShortDetection(0)
2: startRingToGroundShortDetection(1)
3: startTipToRingShortDetection(2)
4: startRingerEquivalenceNetwork(3)
5: startSelfTestNoReboot(4)
6: startOffHookSimulationTest(5)
7: startTip1ToRing2Short(6)
8: startTip2ToRing1Short(7)
9: startHazardousPotentialsTest(8)
10: startstartForeignElectromotiveForceTest(9)
11: startReceiverOffhook(10)
12: startPtcFaultDetection(11)
13: test12NotImplemented(12)
32: startForceTestExecution(31)
Description: This object is used to start one or more diagnostic tests
associated with a corresponding endpoint. Thus, whenever one or
more BITS corresponding to diagnostic test are set to a value of
'1', the MTA MUST start those tests. Before starting the test, the
MTA MUST clear the BITS of the objects
'emtaSignalingEndptCtrlDiagTestValid',
'emtaSignalingEndptCtrlDiagTestResult', and
'emtaSignalingEndptCtrlDiagTestsStop'. Once the tests are
executed, the MTA MUST:
- set the corresponding bits to a value of '0'
- update the corresponding BITS in the MIB Objects
'emtaSignalingEndptCtrlDiagTestValid' and
'emtaSignalingEndptCtrlDiagTestResult'.
Whenever a test is being run on an endpoint the MTA MUST set the
corresponding 'ifOperStatus' MIB Object to a value of 'testing(3)'
for the whole duration of the test. When the test is completed,
the MTA MUST set the ifOperStatus to the value corresponding to
the current state of the line. The selected tests will not run if
the corresponding endpoint is offhook. Any attempt to set the
testnnNotImplemented bits (bit 12 to 30) will result in an
Ubee Interactive
'inconsistentValue' error. To force execution of the selected

tests regardless of the endpoint status set the corresponding
startForceTestExecution(31) BIT.
emtaSignalingEndptCtrlDiagTestsStop
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.4
Prev sibling: emtaSignalingEndptCtrlDiagTestsStart
Next sibling: emtaSignalingEndptCtrlDiagTestValid
Base syntax: BITS
Status: current
Value list: 1: stopTipToGroundShortDetection(0)
2: stopRingToGroundShortDetection(1)
3: stopTipToRingShortDetection(2)
4: stopRingerEquivalenceNetwork(3)
5: stopSelfTestNoReboot(4)
6: stopOffHookSimulationTest(5)
7: stopTip1ToRing2Short(6)
8: stopTip2ToRing1Short(7)
9: stopHazardousPotentialsTest(8)
10: stopForeignElectromotiveForceTest(9)
11: stopReceiverOffhook(10)
12: stopPtcFaultDetection(11)
Description: This object is used to stop the test corresponding to the bit being
set if the test is not complete yet by the time when the bit is
set. Any attempt to set bits other than bit 0 to bit 11 will result
in an 'inconsistentValue' error.
emtaSignalingEndptCtrlDiagTestValid
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.5
Prev sibling: emtaSignalingEndptCtrlDiagTestsStop
Next sibling: emtaSignalingEndptCtrlDiagTestResult
Base syntax: BITS
Status: current
Value list: 1: validTipToGroundShortDetection(0)
2: validRingToGroundShortDetection(1)
3: validTipToRingShortDetection(2)
4: validRingerEquivalenceNetwork(3)
5: validSelfTestNoReboot(4)
6: validOffHookSimulationTest(5)
7: validTip1ToRing2Short(6)
8: validTip2ToRing1Short(7)
9: validHazardousPotentialsTest(8)
10: validForeignElectromotiveForceTest(9)
11: validReceiverOffhook(10)
12: validPtcFaultDetection(11)
Description: This object indicates the validity of the corresponding test case
that was initiated using the MIB Object
'emtaSignalingEndptCtrlDiagTestsStart'.
An MTA MUST:
- set corresponding bit if the MTA was able to run the test, and
the test result is valid.
- clear a corresponding bit if the MTA was not able to run the
test, or the test was not initiated, or the test was not complete
for any reason and, hence, the result is invalid.
emtaSignalingEndptCtrlDiagTestResult
Type: OBJECT-TYPE
Ubee Interactive
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.6
Prev sibling: emtaSignalingEndptCtrlDiagTestValid
Next sibling: emtaSignalingEndptCtrlDiagTestValue
Base syntax: BITS
Status: current
Value list: 1: resTipToGroundShortDetection(0)
2: resRingToGroundShortDetection(1)
3: resTipToRingShortDetection(2)
4: resRingerEquivalenceNetwork(3)
5: resSelfTestNoReboot(4)
6: resOffHookSimulationTest(5)
7: resTip1ToRing2Short(6)
8: resTip2ToRing1Short(7)
9: resHazardousPotentialsTest(8)
10: resForeignElectromotiveForceTest(9)
11: resReceiverOffhook(10)
12: resPtcFaultDetection(11)
Description: This object indicates the result of the corresponding test that
was initiated using the MIB Object
'emtaSignalingEndptCtrlDiagTestsStart'.
An MTA MUST:
- set the bit if the corresponding test completed successfully.
- clear the bit if the corresponding test completed and failed the
test.
emtaSignalingEndptCtrlDiagTestValue
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.7
Prev sibling: emtaSignalingEndptCtrlDiagTestResult
Next sibling: emtaSignalingEndptCtrlBoostedLoopCurrent
Status: current
Description: This object contains the value which represents the results of the
corresponding test. Each value of the result is represented as a
human readable string indicating the value of the particular
parameter used to evaluate the testing results. The format of the
string with the value must be as follows: [P=<param>,V=<value>,U=
<unit>] where: <param> - is the name of the particular parameter
evaluated during the test, <value> - is the human readable
representation of the testing result of the particular parameter
(e.g. '3.5', 'state is on-hook', etc), <unit> - is the human
readable representation of the unit describing the <value>. If
there are several parameters constituting the result of the
individual test, then all values must be presented in the MIB
Object in the following format: [P=<param-1>,V=<value-1>,U=<unit-
1>][P=<param 2>,V=<value-2>,U=<unit-2>]..... If the test is not
represented by the measurable value, or the test has not been
complete for any reason, then the object must contain zero-length
string.
emtaSignalingEndptCtrlBoostedLoopCurrent
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.8
Prev sibling: emtaSignalingEndptCtrlDiagTestValue
Next sibling: emtaSignalingEndptCtrlTxGain
Ubee Interactive
Status: current
Description: This object indicates whether the the loop current should be
boosted (true(1)) or not (false(2)). The particular value for the
loop current depends on the particular hardware (SLIC) being used.
emtaSignalingEndptCtrlTxGain
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.9
Prev sibling: emtaSignalingEndptCtrlBoostedLoopCurrent
Next sibling: emtaSignalingEndptCtrlRxGain
Status: current
Size list: 1: -16..16
Units: dB
Description: This Object represents the per line transmitter (A/D) gain. A
positive number reflects a signal gain, a negative number reflects
a signal loss. This Object does not reflect the desired level at
the Telco (POTS) a-b (T/R) terminals as it does not include the
affects of the gain settings on the analog interfaces which are
pre-configured for a given country specification. The gain setting
specified in this MIB object will be applied on top of the
preconfigured settings and therefore represents a relative level.
The default value of this object may change based on build specific
options.
emtaSignalingEndptCtrlRxGain
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.10
Prev sibling: emtaSignalingEndptCtrlTxGain
Next sibling: emtaSignalingEndptCtrlDialToneMsecTO
Status: current
Size list: 1: -16..16
Units: dB
Description: This Object represents the per line receiver (D/A) gain. A positive
number reflects a signal gain, a negative number reflects a signal
loss. This MIB Object does not reflect the desired level at the
Telco (POTS) a-b (T/R) terminals as it does not include the affects
of the gain settings on the analog interfaces which are pre-
configured for a given country specification. The gain setting
specified in this MIB will be applied on top of the preconfigured
settings and therefore represents a relative level. The default
value of this object may change based on build specific options.
emtaSignalingEndptCtrlDialToneMsecTO
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.11
Prev sibling: emtaSignalingEndptCtrlRxGain
Next sibling: emtaSignalingEndptCtrlToneDetectionControl
Status: current
Ubee Interactive

Size list: 1: 0
2: 100..16000
Units: Milliseconds
Description: This Object contains the timeout value for dial tone that provides
millisecond resolution. If the value of the object is modified by
the SNMP Management Station to a non zero value, the MTA MUST use
the new value as a default only for a new signal requested by the
NCS message. If the value of this object is set to 0, then
'pktcNcsEndPntConfigDialToneTO' from PKTC-SIG-MIB MUST be used,
and not this value. If set to a non-zero value this object takes
precedence over 'pktcNcsEndPntConfigDialToneTO' object. Only
increments of 100ms are allowed. Note that the value of this object
will persist across a system reboot.
emtaSignalingEndptCtrlToneDetectionControl
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.12
Prev sibling: emtaSignalingEndptCtrlDialToneMsecTO
Next sibling: emtaSignalingEndptCtrlRingWaveform
Status: deprecated
Value list: 1: allDetectorsEnabled(1)
2: allDetectorsDisabled(2)
3: v18-AlarmPOSDisabled(3)
4: alarmPOSDisabled(4)
5: undefined(5)
Default values: 1: alarmPOSDisabled (name)
Description: This MIB object is used to provide enhanced tone detection control
on an EMTA endpoint.
When set to AllDetectorsEnabled(1), the EMTA must enable all the
tone detectors on the specific endpoint. This includes the
following detectors:
- fax/modem tones (1100, 2100Hz)
- V18/TDD tones (980,1400,1650Hz)
- Alarm panel and Point of Sale terminal (POS) tones
(1275,2225,2250Hz)
When set to AllDetectorsDisabled(2), the EMTA must disable all the
tone detectors on the specific endpoint. Note that this mode would
make the EMTA non compliant with the PacketCable requirements.
When set to V18-AlarmPOSDisabled(3), the EMTA must disable the
V18, Alarm panel and POS portion of tone detection. This includes
disabling Baudot (1400Hz), Preamble (980&1650Hz), Ascii/Bell103
(1275,2225) and V.22bis (2250Hz) detection on the specific
endpoint. Note that this mode would make the EMTA non compliant
with the PacketCable requirements.
When set to AlarmPOSDisabled(4), the EMTA must disable the Alarm
panel and POS portion of tone detection on the specific endpoint.
This includes disabling the Bell103 (1275,2225) and V.22bis
(2250Hz) but leaving the other detectors enabled.
The value undefined(5) indicates a combination of tone detection
control not supported by this MIB, but supported by
emtaSignalingEndptCtrlToneDetectionControlExt. Setting to
undefined(5) will result in an 'inconsistentValue' error.
If a configuration file contains both
emtaSignalingEndptCtrlToneDetectionControl and
emtaSignalingEndptCtrlToneDetectionControlExt, the mib that is
processed last will take precedence.
Ubee Interactive
If a connection already exists on the endpoint when this MIB Object

is modified, then the setting needs to take effect on the next
connection.
emtaSignalingEndptCtrlRingWaveform
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.13
Prev sibling: emtaSignalingEndptCtrlToneDetectionControl
Next sibling: emtaSignalingEndptCtrlPowerMgmtDelay
Status: current
Value list: 1: sinusoidal(1)
2: trapezoidal(2)
Default values: 1: sinusoidal (name)
Description: This MIB object is controls the shape of the ring waveform.
The setting of sinusoidal(1) would result in a sinusoidal ring
waveform with crest factor of 1.414, while the setting of
trapezoidal(2) would result in a trapezoidal ring waveform with
crest factor of 1.25.
emtaSignalingEndptCtrlPowerMgmtDelay
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.14
Prev sibling: emtaSignalingEndptCtrlRingWaveform
Next sibling: emtaSignalingEndptCtrlToneDetectionControlExt
Status: current
Size list: 1: -1..2147483647
Default values: 1: -1 (int)")
Units: seconds
Description: Specifies the number of seconds following transition to battery
power before the endpoint interface will enter power management
mode. If set to -1, the interface will never enter power management
mode and will remain at full power until utility power is restored
or battery charge is depleted. If a call is active (off-hook) when
the timer expires, the timer will be restarted after hang-up (line
goes on-hook).
emtaSignalingEndptCtrlToneDetectionControlExt
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.15
Prev sibling: emtaSignalingEndptCtrlPowerMgmtDelay
Next sibling: emtaSignalingEndptCtrlPulseDialEnable
Base syntax: BITS
Status: current
Value list: 1: faxDetectionDisabled(0)
2: modemDetectionDisabled(1)
3: v18BaudotDisabled(2)
4: v18PreambleDissabled(3)
5: v18AsciiBell103V22bisDisabled(4)
Description: This MIB object is used to control individual tone detectors on an
EMTA endpoint.
Ubee Interactive
If bit faxDetectionDisabled(0) is set, the EMTA must disable the

fax portion of tone detection (1100Hz CNG tone) on the specific
endpoint.
If bit modemDetectionDisabled(1) is set, the EMTA must disable the
modem portion of tone detection (2100Hz CED tone) on the specific
endpoint.
If bit V18BaudotDisabled(2) is set, the EMTA must disable V18
Baudot (1400 Hz) detection on the specific endpoint.
If bit V18PreambleDisabled(3) is set, the EMTA must disable V18
Preamble (980, 1650 Hz) detection on the specific endpoint.
If bit V18AsciiBell103V22bisDisabled(4) is set, the EMTA must
disable V18 Ascii/Bell103 (1275, 2225 Hz) and V22bis (2250 Hz)
detection on the specific endpoint (mostly used for Alarm Panels
and Point of Sale terminals).
If a connection already exists on the endpoint when this MIB Object
is modified, then the setting needs to take effect on the next
connection.
The default value of this object has the
v18AsciiBell103V22bisDisabled(4) bit set, which is compliant with
PacketCable requirements.
Note that the default value of this object may change based on
build specific options, which could be PacketCable non-compliant.
If a configuration file contains both
emtaSignalingEndptCtrlToneDetectionControl and
emtaSignalingEndptCtrlToneDetectionControlExt, the mib that is
processed last will take precedence.
emtaSignalingEndptCtrlPulseDialEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.16
Prev sibling: emtaSignalingEndptCtrlToneDetectionControlExt
Next sibling: emtaSignalingEndptCtrlVBDTxGain
Status: current
Description: This oject controls pulse dialing detection for the Endpoint. When
set to 'true(1)', pulse and tone dialing detection is enabled. When
set to 'false(2)', only tone detection is enabled.
emtaSignalingEndptCtrlVBDTxGain
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.17
Prev sibling: emtaSignalingEndptCtrlPulseDialEnable
Next sibling: emtaSignalingEndptCtrlVBDRxGain
Status: current
Size list: 1: -5..5
Units: dB
Ubee Interactive
Description: This Object is added to the default VBD Tx gain to be used when
operating in voiceband dcata mode. Note that the value of this
object will persist across a system reboot.
emtaSignalingEndptCtrlVBDRxGain
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.18
Prev sibling: emtaSignalingEndptCtrlVBDTxGain
Next sibling: emtaSignalingEndptCtrlPulseToDtmfConvert
Status: current
Size list: 1: -5..5
Units: dB
Description: This Object is added to the default VBD Rx gain to be used when
operating in voiceband dcata mode. Note that the value of this
object will persist across a system reboot.
emtaSignalingEndptCtrlPulseToDtmfConvert
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.19
Prev sibling: emtaSignalingEndptCtrlVBDRxGain
Next sibling: emtaSignalingEndptCtrlCustomCWCIDCfgEnable
Status: current
Description: This object controls the in-call pulse dial to dtmf tone
conversion. When set to 'true(1)', in-call pulse-to-dtmf
conversion is enabled and pulse dial events are converted to
corresponding dtmf tones. When set to 'false(2)', in-call pulse-
to-dtmf conversion is disabled. The value of this object must be
set via the MTA config file for persistence.
emtaSignalingEndptCtrlCustomCWCIDCfgEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.20
Prev sibling: emtaSignalingEndptCtrlPulseToDtmfConvert
Next sibling: emtaSignalingEndptCtrlCASLevelCfg
Status: current
Description: This object controls whether MTA uses user-defined values for CAS
tone and FSK signal for Call Waiting Caller ID. When set to
'true(1)', user-defined values for CAS tone (as specified in
emtaSignalingEndptCtrlCASLevelCfg) and FSK signal (as specified in
emtaSignalingEndptCtrlFSKLeveCfg) will be used. When set to
'false(2)', values defined in Telcordia GR-30 will be used.
emtaSignalingEndptCtrlCASLevelCfg
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.21
Ubee Interactive
Prev sibling: emtaSignalingEndptCtrlCustomCWCIDCfgEnable

Next sibling: emtaSignalingEndptCtrlOffhookCIDFSKLevelCfg
Status: current
Size list: 1: -200..-100
Units: TenthdBm
Description: This Object controls the user-defined level of the CPE Alerting
Signal (CAS) during Call Waiting Caller ID delivery procedure. In
order for this object to take effect, the
emtaSignalingEndptCtrlCustomCWCIDCfgEnable object must be set to
true(1). This object must be changed in increments and decrements
of 5 TenthdB. An attempt to set this object to a value that does
not fall on the increment boundaries will result in an
'inconsistent value' error.
emtaSignalingEndptCtrlOffhookCIDFSKLevelCfg
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.22
Prev sibling: emtaSignalingEndptCtrlCASLevelCfg
Next sibling: emtaSignalingEndptCtrlOnhookCIDFSKLevelCfg
Status: current
Size list: 1: -200..-100
Units: TenthdBm
Description: This Object controls the user-defined level of the FSK data
transmission during Call Waiting Caller ID delivery procedure. In
order for this object to take effect, the
emtaSignalingEndptCtrlCustomCWCIDCfgEnable objects must be set to
emtaSignalingEndptCtrlOnhookCIDFSKLevelCfg
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.23
Prev sibling: emtaSignalingEndptCtrlOffhookCIDFSKLevelCfg
Next sibling: emtaSignalingEndptCtrlVMWIOSIDuration
Status: current
Size list: 1: -200..-100
Units: TenthdBm
Description: This Object controls the user-defined level of the FSK data
transmission during Onhook Caller ID delivery procedure. This also
applies to FSK data transmission during the VMWI delivery
procedure. In order for this object to take effect, the
emtaSignalingEndptCtrlCustomCWCIDCfgEnable objects must be set to
Ubee Interactive
emtaSignalingEndptCtrlVMWIOSIDuration
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.24
Prev sibling: emtaSignalingEndptCtrlOnhookCIDFSKLevelCfg
Next sibling: emtaSignalingEndptCtrlMgcpQuarantineMode
Status: current
Size list: 1: 100..1000
Units: Milliseconds
Description: This object specifies the duration of the Open Switch Interval
(OSI) used as an alerting signal method during Visual Message
Waiting Indicator (VMWI) signaling. This object is only used when
OSI is the current alerting signal method for VMWI signaling.
emtaSignalingEndptCtrlMgcpQuarantineMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.25
Prev sibling: emtaSignalingEndptCtrlVMWIOSIDuration
Next sibling: emtaSignalingEndptCtrlOSIDuration
Status: current
Value list: 1: step(1)
2: loop(2)
Default values: 1: step (name)
Description: This object contains the value which controls the MGCP Quarantine
mode for an endpoint. Setting this object to step(1)' causes the
endpoint to use the step mode as per RFC2705, allowing the MTA to
send one NTFY message for each received RQNT message. Setting this
object to loop(2)' causes the MTA to use loop mode as per RFC2705,
allowing the MTA to send multiple NTFY message with one received
RQNT message. If emtaSignalingMgcpLockstepActivation is currently
false(2), MTA is currently operating in loop mode only and any
attempt to set this object to step(1), will result in an
'inconsistentValue' error.
emtaSignalingEndptCtrlOSIDuration
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.26
Prev sibling: emtaSignalingEndptCtrlMgcpQuarantineMode
Next sibling: emtaSignalingEndptCtrlPulseDialMinMakeTime
Status: current
Size list: 1: 50..30000
Units: Milliseconds
Description: This object specifies the duration of the Open Switch Interval
(OSI). The default value of this object corresponds to the
functionality compliant with the PacketCable requirements. Note
that this default value may change based on build specific options.
emtaSignalingEndptCtrlPulseDialMinMakeTime
Type: OBJECT-TYPE
Ubee Interactive
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.27
Prev sibling: emtaSignalingEndptCtrlOSIDuration
Next sibling: emtaSignalingEndptCtrlPulseDialMaxMakeTime
Status: current
Size list: 1: 10..200
Units: Milliseconds
Description: This is the minimum make pulse width for the dial pulse. The value
of emtaSignalingEndptCtrlPulseDialMinMakeTime MUST be less than
emtaSignalingEndptCtrlPulseDialMaxMakeTime. This object MUST only
be set via the configuration file during the provisioning process.
This MIB object does not apply if the device supports
pktcNcsEndPntConfigPulseDialMinMakeTime from the PKTC-EXCENTIS-
SIG-MIB or PKTC-IETF-SIG-MIB.
emtaSignalingEndptCtrlPulseDialMaxMakeTime
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.28
Prev sibling: emtaSignalingEndptCtrlPulseDialMinMakeTime
Next sibling: emtaSignalingEndptCtrlPulseDialMinBreakTime
Status: current
Size list: 1: 10..200
Units: Milliseconds
Description: This is the maximum make pulse width for the dial pulse. The value
of emtaSignalingEndptCtrlPulseDialMaxMakeTime MUST be greater
than emtaSignalingEndptCtrlPulseDialMinMakeTime. This object MUST
only be provided via the configuration file during the
provisioning process. This MIB object does not apply if the device
supports pktcNcsEndPntConfigPulseDialMaxMakeTime from the PKTC-
EXCENTIS-SIG-MIB or PKTC-IETF-SIG-MIB.
emtaSignalingEndptCtrlPulseDialMinBreakTime
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.29
Prev sibling: emtaSignalingEndptCtrlPulseDialMaxMakeTime
Next sibling: emtaSignalingEndptCtrlPulseDialMaxBreakTime
Status: current
Size list: 1: 10..200
Units: Milliseconds
Description: This is the minimum break pulse width for the dial pulse. The value
of emtaSignalingEndptCtrlPulseDialMinBreakTime MUST be less than
emtaSignalingEndptCtrlPulseDialMaxBreakTime. This object must
only be provided via the configuration file during the
supports pktcNcsEndPntConfigPulseDialMinBreakTime from the PKTC-
emtaSignalingEndptCtrlPulseDialMaxBreakTime
Type: OBJECT-TYPE
Ubee Interactive
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.30
Prev sibling: emtaSignalingEndptCtrlPulseDialMinBreakTime
Next sibling: emtaSignalingEndptCtrlRtpTelEvtPayload
Status: current
Size list: 1: 10..200
Units: Milliseconds
Description: This is the maximum break pulse width for the dial pulse. The value
of emtaSignalingEndptCtrlPulseDialMaxBreakTime MUST be greater
than emtaSignalingEndptCtrlPulseDialMinBreakTime. This object
MUST only be provided via the configuration file during the
supports pktcNcsEndPntConfigPulseDialMaxBreakTime from the PKTC-
emtaSignalingEndptCtrlRtpTelEvtPayload
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.31
Prev sibling: emtaSignalingEndptCtrlPulseDialMaxBreakTime
Next sibling: emtaSignalingEndptCtrlPrefCodecList
Status: current
Size list: 1: 96..127
Description: This object configures the dynamic RTP payload number for
telephone events (e.g. DTMF Relay events).
emtaSignalingEndptCtrlPrefCodecList
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.32
Prev sibling: emtaSignalingEndptCtrlRtpTelEvtPayload
Next sibling: emtaSignalingEndptCtrlHDAudioEnabled
Status: current
Description: This MIB Object contains the list of the voice and/or video
codecs preferred by the network. The value in this object is formed
as a comma-separated list of the well-known literal voice/video
codec names. The MTA MUST use the literal voice and/or video codec
name as per RTP AV Profile [RFC 3551], or per encoding names
registered with the IANA, or per encoding names referenced or
defined in the PacketCable Codec-Media specification. Unknown or
non-supported codecs are ignored. The zero-length string indicates
the preferred codec list is vendor specific starting with G711
codecs. The default value of this object is a zero-length string.
Note that the default value of the object may change based on build
specific options.
emtaSignalingEndptCtrlHDAudioEnabled
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.33
Prev sibling: emtaSignalingEndptCtrlPrefCodecList
Ubee Interactive
Next sibling: emtaSignalingEndptCtrlHDAudioStatus

Status: current
Description: This MIB object will enable or disable the inclusion of HD Audio
during codec negotiation. If HD Audio is supported by the device
a value of true will cause HD Audio to be advertised during codec
negotiation. A value of false will prevent HD audio from being
advertised during codec negotiation. HD Audio codecs in
emtaSignalingEndptCtrlPrefCodecList are ignored based on the value
of emtaSignalingEndptCtrlHDAudioEnabled.
This MIB has the following interaction with other MIB objects when
it comes to reporting HD Audio during codec negotiation:
emtaDevHDAudioEnabled emtaSignalingEndptCtrl HD Audio
HDAudioEnabled Reported
----------------------------------------------------------
true true yes
true false no
false true no
false false no
emtaSignalingEndptCtrlHDAudioStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.1.1.34
Prev sibling: emtaSignalingEndptCtrlHDAudioEnabled
Base syntax: BITS
Status: current
Value list: 1: g722(0)
2: aMR-WB(1)
3: bV32(2)
Description: This MIB object reflects the status of the corresponding HD Audio
codec for each line. When the HD Audio codec is provided and
available on that line, the corresponding bit will be set. When
the HD Audio codec is not provided or available for that line, the
corresponding bit will be cleared. Note this MIB derives the
availability of the HD Audio codec based on the MIBs
emtaDevHDAudioEnabled, emtaSignalingEndptCtrlHDAudioEnabled, and
emtaSignalingEndptCtrlPrefCodecList, as well as whether the codec
is supported by the DSP image.
The corresponding bit will be set if the following are true:
- emtaDevHDAudioEnabled is set to true, and
- emtaSignalingEndptCtrlHDAudioEnabled is set to true, and
- DSP image supports the codec, and
- for SIP, if sipEndPntConfigUserUseCodecTable is set to true and
the HD Audio Codec is included in the sipEndPntConfigCodecType
For example:
If emtaDevHDAudioEnabled and emtaSignalingEndptCtrlHDAudioEnabled
are set to true, and the DSP image supports G722, then the G722(0)
bit will be set and the MIB will be 0x80 for NCS. For SIP, there
is an additional condition: if sipEndPntConfigUserUseCodecTable is
set to true, and one of the sipEndPntConfigCodecType entries
includes G722, then the MIB will be 0x80 for SIP.
If emtaDevHDAudioEnabled and emtaSignalingEndptCtrlHDAudioEnabled
are set to true, and the DSP image supports G722 and BV32, then
the G722(0) and BV32(2) bits will be set and the MIB will be 0xA0.
For SIP, there is an additional condition: if
sipEndPntConfigUserUseCodecTable is set to true, and two of the
sipEndPntConfigCodecType entries includes G722 and BV32, then the
MIB will be 0xA0 for SIP.
Ubee Interactive
emtaSignalingAnnouncementCtrl
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.2
Parent: emtaMgmtSignalingControl
Prev sibling: emtaSignalingEndptCtrlTable
Next sibling: emtaSignalingVoiceJitterBufferType
Base syntax: BITS
Status: current
Value list: 1: announcementOnRfLoss(0)
2: announcementOnEndptDisabled(1)
3: announcementOnEndptDisconnected(2)
4: announcementOnACLoss(3)
5: announcementOnLowBatt(4)
6: announcementOnBadBatt(5)
7: announcementOnBattOverTemp(6)
Description: This object contains the value controlling the announcements being
played by the MTA in case of service interruption or UPS battery
condition. The service interruptions announcements are required to
be played if the phone is off-hook.
If bit announcementOnRfLoss(0) is set, the MTA MUST play an
Announcement on all endpoints upon the RF loss. Otherwise (the bit
is cleared) - the MTA MUST NOT play the announcement.
If bit announcementOnEndptDisabled(1) is set, the MTA MUST play
the announcement on the end-point which is not in an active
signaling state.
If bit announcementOnEndptDisconnected(2) is set, the MTA MUST
play the announcement on the end-point which becomes NCS
disconnected (pktcNcsEndPntStatusError is in disconnected(3)
state). Otherwise – the the MTA MUST NOT play the announcement.
The UPS battery condition announcements are required to be played
if the phone is off-hook and before dialtone: If bit
announcementOnACLoss(3) is set, the MTA MUST play an audible tone
announcement upon detecting the loss of AC Power. The
announcements are required to be played if the phone is off-hook
and before dial tone. Otherwise (the bit is cleared) - the MTA MUST
NOT play the announcement.
If bit announcementOnLowBatt(4) is set, the MTA MUST play an
audible tone announcement upon detecting the low battery
condition. The announcements are required to be played if the phone
is off-hook and before dial tone. Otherwise (the bit is cleared)
- the MTA MUST NOT play the announcement.
If bit announcementOnBadBatt(5) is set, the MTA MUST play an
audible tone announcement upon detecting the bad battery
condition. The announcements are required to be played if the phone
is off-hook and before dial tone. Otherwise (the bit is cleared)
- the MTA MUST NOT play the announcement.
If bit announcementOnBattOverTemp(6) is set, the MTA MUST play an
audible tone announcement upon detecting the battery over
temperature condition. The announcements are required to be played
if the phone is off-hook and before dial tone. Otherwise (the bit
is cleared) - the MTA MUST NOT play the announcement.
The default value of this object corresponds to the functionality
compliant with the PacketCable requirements - all bits are
cleared.
emtaSignalingVoiceJitterBufferType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.3
Ubee Interactive
Prev sibling: emtaSignalingAnnouncementCtrl
Next sibling: emtaSignalingVoiceJitterNomValue
Status: current
Value list: 1: jitterBufferTypeFixed(1)
2: jitterBufferTypeAdaptive(2)
Default values: 1: jitterBufferTypeAdaptive (name)
Description: This object contains the type of the jitter buffer. Setting this
object to jitterBufferTypeFixed(1) causes the eMTA to employ a
fixed jitter buffer. Setting this object to
jitterBufferTypeAdaptive(2) causes the eMTA to use an adaptive
jitter buffer. If the jitter buffer type value is changed through
SNMP, then those changes take affect starting with the next phone
call (in process calls are not affected). When the voice jitter
buffer is frozen it uses the emtaSignalingVoiceJitterNomValue for
the fixed size of the jitter buffer.
emtaSignalingVoiceJitterNomValue
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.4
Prev sibling: emtaSignalingVoiceJitterBufferType
Next sibling: emtaSignalingVoiceJitterMinValue
Status: current
Units: milliseconds
Description: If the voice jitter buffer value is changed through SNMP, then
those changes take affect starting with the next phone call (in
process calls are not affected). This MIB sets the target hold time
for the voice jitter buffer in milliseconds. This is the initial
hold time for the adaptive jitter buffer. The actual target holding
time will adapt above or below this in response to observed network
jitter. The MTA will reject all attempts to set the value which is
not within the interval defined by the
emtaSignalingVoiceJitterMinValue and
emtaSignalingVoiceJitterMaxValue MIB Objects. When the jitter
buffer is frozen, this MIB controls the static size of the voice
jitter buffer. The default value is 0ms.
emtaSignalingVoiceJitterMinValue
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.5
Prev sibling: emtaSignalingVoiceJitterNomValue
Next sibling: emtaSignalingVoiceJitterMaxValue
Status: current
Units: milliseconds
process calls are not affected). This MIB sets the minimum hold
time for the voice jitter buffer in milliseconds. The target hold
time cannot take on a value below the minimum either through a MIB
setting or through adaptation. That is, packets will be held in
Ubee Interactive
the jitter buffer for at least this duration (on average). When a
packet is received late it may be held for less than this time.
The default is 0ms.
emtaSignalingVoiceJitterMaxValue
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.6
Prev sibling: emtaSignalingVoiceJitterMinValue
Next sibling: emtaSignalingDataJitterNomValue
Status: current
Units: milliseconds
process calls are not affected). This MIB sets the maximum hold
time for the voice jitter buffer in milliseconds. The maximum size
of the jitter buffer is only relevant for an adaptive jitter
buffer. The target hold time cannot take on a value greater than
the maximum either through a MIB setting or through adaptation. On
average, packets will not be held longer than this time. However,
if a packet is received quite early it may be held longer than the
max hold time. The default value is 0 which is interpreted as the
maximum jitter buffer size for the product.
emtaSignalingDataJitterNomValue
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.7
Prev sibling: emtaSignalingVoiceJitterMaxValue
Next sibling: emtaSignalingDtmfToneRelayRFC2833Support
Status: current
Units: milliseconds
Description: If the jitter buffer value is changed through SNMP, then those
changes take affect starting with the next phone call (in process
calls are not affected). This object controls the hold time for
fixed VBD jitter buffer. The jitter buffer always fixes itself when
VBD is detected and never adapts below this level, so this value
serves as a minimum too. The default value is 60 milliseconds.
emtaSignalingDtmfToneRelayRFC2833Support
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.8
Prev sibling: emtaSignalingDataJitterNomValue
Next sibling: emtaSignalingNumOfCallsTotal
Status: current
2: disabled(2)
3: subtract(3)
Default values: 1: enabled (name)
Ubee Interactive
Description: This object contains the value which controls the usage of the DTMF
Relay. Setting this object to 'enabled(1)' causes the MTA to use
the DTMF Tone Relay as per RFC2833. Setting this object to
'disabled(2)' causes the eMTA to pass DTMF tones inband. Setting
this object to 'subtract(3)' causes eMTA to mute DTMF tones from
the encoded audio and pass DTMF as signaling events.
emtaSignalingNumOfCallsTotal
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.9
Prev sibling: emtaSignalingDtmfToneRelayRFC2833Support
Next sibling: emtaSignalingMaxNumberQueuedNcsEvents
Status: current
Description: This object contains the total number of calls originated and
terminated by the MTA since reset.
emtaSignalingMaxNumberQueuedNcsEvents
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.10
Prev sibling: emtaSignalingNumOfCallsTotal
Next sibling: emtaSignalingRtpBaseReceiveUdpPort
Status: current
Description: This object contains the max number of the queued NCS events the
MTA can store during the lock step.
emtaSignalingRtpBaseReceiveUdpPort
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.11
Prev sibling: emtaSignalingMaxNumberQueuedNcsEvents
Next sibling: emtaSignalingEndptConnectionCleanupTimeout
Composed syntax: InetPortNumber
Status: current
Size list: 1: 1026..65534
Description: This object contains the UDP Port Number used by the EMTA for RTP
connection. RTP (and RTCP) ports for all connections will be based
on this port. This object must be an even value. Attempt to set
this object to an odd value will result in an 'inconsistent value'
error. Note that the maximum port number that can be set is based
on the maximum number of connections supported, ie. maximum port
number is 65534 subtracted by two times the maximum number of
connections. For example, for an MTA with two endpoints and two
connections per endpoint, the maximum port number would be 65534
subtracted by 2 * 4 (for RTP and RTCP ports for 4 connections),
which is 65526.
emtaSignalingEndptConnectionCleanupTimeout
Type: OBJECT-TYPE
Ubee Interactive
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.12
Prev sibling: emtaSignalingRtpBaseReceiveUdpPort
Next sibling: emtaSignalingEmtaResetCleanupTimeout
Status: current
Size list: 1: 0..64000
Units: seconds
Description: If set this object causes the EMTA to tear down and clean up
connections and the associated service flows on any endpoint that
detects a transition from off-hook to on-hook, remains onhook for
a period longer than the value set in this MIB object, and has
connections that were active prior to the endpoint going onhook.
If the MIB object is set to 0 then this function is disabled. If
the MIB is set from 1 to 64000 seconds then the feature is enabled
and this value is used for the timeout. Note that the default value
of this object may change based on build specific options.
emtaSignalingEmtaResetCleanupTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.13
Prev sibling: emtaSignalingEndptConnectionCleanupTimeout
Next sibling: emtaSignalingT38FaxRelaySupport
Status: current
Size list: 1: 0..64000
Units: minutes
Description: If set this object causes the entire EMTA to reset if voice
connections have been active and both voice lines have been on-
hook for a period greater than the value defined via this MIB
object. This will guarantee that orphaned connections and/or
service flows are properly cleaned up and freed when the CMTS and
CMS fail to perform the correct clean up operations. It will also
ensure that the EMTA state machine, DSP voice channels, NCS
connection handling, etc. are also restored to a default state.
This protects against any unknown case that could possibly cause
stuck service flows and/or connections. If the MIB object is set
to 0 then this function is disabled. If the MIB is set from 1 to
64000 minutes then the feature is enabled and this value is used
for the timeout.
emtaSignalingT38FaxRelaySupport
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.14
Prev sibling: emtaSignalingEmtaResetCleanupTimeout
Next sibling: emtaSignalingEcanTailLength
Status: current
Description: This object contains the value which controls the usage of the T38
Fax Relay. Setting this object to 'true(1)' causes the EMTA to use
the T38 Fax Relay if supported by the DSP image. Setting this
object to 'false(2)' causes the EMTA not to use T38 Fax Relay, but
to use voice-band data mode for fax transmission instead.
Ubee Interactive
emtaSignalingEcanTailLength
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.15
Prev sibling: emtaSignalingT38FaxRelaySupport
Next sibling: emtaSignalingDQoSActivationModel
Status: current
Value list: 1: ecanTail8ms(1)
2: ecanTail16ms(2)
3: ecanTail24ms(3)
4: ecanTail32ms(4)
Default values: 1: ecanTail32ms (name)
Description: This object specifies the echo cancellation tail length. If the
echo cancellation tail length is changed through SNMP, then those
changes take effect starting with the next phone call (in process
calls are not affected). Also note that the value of this object
will persist across a MTA reset.
emtaSignalingDQoSActivationModel
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.16
Prev sibling: emtaSignalingEcanTailLength
Next sibling: emtaSignalingGR303Support
Status: current
Value list: 1: singlePhase(1)
2: twoPhase(2)
Default values: 1: twoPhase (name)
Description: This object controls the DQoS activation model.
Setting this object to singlePhase(1) causes the eMTA to employ
the single phase model where both reservation and commitment occur
as a single autonomous operation.
Setting this object to twoPhase(2) causes the eMTA to employ the
two-phase model where the application reserves the resource, and
later commits it.
This object should only be changed by the configuration file.
emtaSignalingGR303Support
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.17
Prev sibling: emtaSignalingDQoSActivationModel
Next sibling: emtaSignalingPowerRingFrequency
Status: current
2: disabled(2)
Ubee Interactive
Description: This object controls the GR303 mode. Setting this object to
enabled(1) causes the eMTA to switch to GR303mode. The MTA will
generate RTP on-hook event packets in the media stream until off-
hook is detected or the connection is deleted. Also MTA will treat
flash hook as separate on-hook and off-hook events, and send each
event triple redundantly, replacing voice packets in the RTP
stream. Setting this object to disabled(2) causes the eMTA not to
use GR303 mode. This object should only be changed by the
configuration file.
emtaSignalingPowerRingFrequency
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.18
Prev sibling: emtaSignalingGR303Support
Next sibling: emtaSignalingDataJitterMaxValue
Status: current
Value list: 1: f20Hz(1)
2: f25Hz(2)
3: f33Point33Hz(3)
4: f50Hz(4)
5: f15Hz(5)
6: f16Hz(6)
7: f22Hz(7)
8: f23Hz(8)
9: f45Hz(9)
10: f17Hz(10)
Default values: 1: f20Hz (name)
Units: Hertz
Description: This object must only be provided via the configuration file during
the provisioning process. The power ring frequency is the
frequency at which the sinusoidal voltage must travel down the
twisted pair to make terminal equipment ring. Different countries
define different electrical characteristics to make terminal
equipment ring.
The f20Hz setting corresponds to a power ring frequency of 20
Hertz.
Hertz.
The f33Point33Hz setting corresponds to a power ring frequency of
33.33 Hertz.
Hertz.
Hertz.
Hertz.
Hertz.
Hertz.
Hertz.
Hertz.
emtaSignalingDataJitterMaxValue
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.19
Prev sibling: emtaSignalingPowerRingFrequency
Next sibling: emtaSignalingRingWaveform
Ubee Interactive

Status: current
Units: milliseconds
Description: If the voice buffer value is changed through SNMP, then those
changes take affect starting with the next phone call (in process
calls are not affected). This MIB sets the maximum hold time for
the fixed VBD jitter buffer and is only relevant when
emtaSignalingVoiceJitterBufferType is set to
'jitterbufferTypeFixed(1)'. the default value is 0 which is
interpreted as the maximum jitter buffer size for the product.
emtaSignalingRingWaveform
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.20
Prev sibling: emtaSignalingDataJitterMaxValue
Next sibling: emtaSignalingDefRtcpDSCP
Status: deprecated
Value list: 1: sinusoidal(1)
2: trapezoidal(2)
Default values: 1: sinusoidal (name)
Description: This MIB object is controls the shape of the ring waveform. The
setting of sinusoidal(1) would result in a sinusoidal ring
waveform with crest factor of 1.414, while the setting of
trapezoidal(2) would result in a trapezoidal ring waveform with
crest factor of 1.25.
emtaSignalingDefRtcpDSCP
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.23
Prev sibling: emtaSignalingRingWaveform
Next sibling: emtaSignalingDevToneTable
Status: current
Size list: 1: 0..63
Description: This object contains the default value used in the IP header for
setting the DSCP for RTCP packets. When the value of this object
is updated by SNMP, the MTA MUST use the new value as a default
starting from the new connection. Existing connections are not
affected by the value's update. Note that the default value of this
object may change based on build specific options.
emtaSignalingDevToneType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.24.1.1
Parent: emtaSignalingDevToneEntry
Next sibling: emtaSignalingDevToneWholeToneRepeatCount
Status: current
Value list: 1: rfLoss(1)
2: endptDisabled(2)
Ubee Interactive
3: endptDisconnected(3)
4: acLoss(4)
5: battLow(5)
6: battBad(6)
7: battOverTemp(7)
Description: Unique value that will correspond to the different tone types for
service interruption or battery conditions. This object defines
the type of tone being accessed.
emtaSignalingDevToneWholeToneRepeatCount
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.24.1.2
Prev sibling: emtaSignalingDevToneType
Next sibling: emtaSignalingDevToneSteady
Status: current
Size list: 1: 0..5000
Description: This is the repeat count, which signifies how many times to repeat
the entire on-off cadence sequence. Setting this object may result
in a cadence duration longer or shorter than the overall signal
duration specified by the time out (TO) object for a particular
signal. If the repeat count results in a longer tone duration than
the signal duration specified by the TO, the tone duration defined
by the TO object for a particular signal always represents the
overall signal duration for a tone. In this case, the tone duration
repeat count will not be fully exercised and the desired tone
duration will be truncated per the TO setting. If the repeat count
results in a shorter tone duration than the signal duration
specified by the TO, the tone duration defined by the repeat count
takes precedence over the TO and will end the signal event. In this
case, the TO represents a time not to be exceeded for the signal.
It is recommended to ensure proper telephony signaling that the TO
duration setting should always be longer than the desired repeat
count time duration.
emtaSignalingDevToneSteady
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.24.1.3
Prev sibling: emtaSignalingDevToneWholeToneRepeatCount
Status: current
Description: This is the steady tone. Device must play out the on-off cadence
sequence for pktcSigDevToneWholeRepeatCount times and then apply
the last tone forever. Setting this object may result in a tone
duration longer or shorter than the overall signal duration
specified by the time out (TO) object for a particular signal. If
the repeat count results in a longer tone duration than the signal
duration specified by the TO, the tone duration defined by the TO
object for a particular signal always represents the overall
signal duration for a tone. In this case, the tone duration repeat
count will not be fully exercised and the desired tone duration
will be truncated per the TO setting. If the repeat count results
in a shorter tone duration than the signal duration specified by
the TO, the tone duration defined by the repeat count takes
precedence over the TO and will end the signal event. In this case,
the TO represents a time not to be exceeded for the signal. It is
Ubee Interactive
recommended to ensure proper telephony signaling that the TO

count time duration plus the desired maximum steady tone period.
emtaSignalingDevToneNumber
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.25.1.1
Parent: emtaSignalingDevMultiFreqToneEntry
Next sibling: emtaSignalingDevToneFirstFreqValue
Status: current
Size list: 1: 1..4
Description: This MIB Object represents the frequency reference of a multi-
frequency tone.
emtaSignalingDevToneFirstFreqValue
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.25.1.2
Prev sibling: emtaSignalingDevToneNumber
Next sibling: emtaSignalingDevToneSecondFreqValue
Status: current
Size list: 1: 0..4000
Description: This MIB Object represents the value of the first frequency of a
tone type. A value of Zero implies absence of the referenced
frequency.
emtaSignalingDevToneSecondFreqValue
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.25.1.3
Prev sibling: emtaSignalingDevToneFirstFreqValue
Next sibling: emtaSignalingDevToneDbLevel
Status: current
Size list: 1: 0..4000
Description: This MIB Object represents the value of the second frequency of a
tone type. A value of Zero implies absence of the referenced
frequency.
emtaSignalingDevToneDbLevel
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.25.1.4
Prev sibling: emtaSignalingDevToneSecondFreqValue
Next sibling: emtaSignalingDevToneFreqOnDuration
Composed syntax: TenthdBm
Status: current
Size list: 1: -250..-30
Ubee Interactive
Description: This MIB Object contains the decibel level for each analog signal
(tone) that is locally generated (versus in band supervisory
tones) and sourced to the a-b terminals (TE connection point). Each
tone in itself may consist of multiple frequencies as defined by
the MIB table 'emtaSignalingDevMultiFreqToneTable'. This MIB
Object MUST reflect the desired level at the Telco (POTS) a-b (T/R)
terminals including the affect of any MTA receiver gain (loss).
This is required so that locally generated tones are consistent
with remotely generated in band tones at the a-b terminals,
consistent with user expectations. This MIB Object must be set for
each tone. When tones are formed by combining multi-frequencies,
the level of each frequency shall be set so as to result in the
tone level specified in this object at the a-b (T/R) terminals.
The wide range of levels for this Object is required to provide
signal generator levels across the wide range of gains (loss) -
but does not imply the entire range is to be achievable given the
range of gains (loss) in the MTA.
emtaSignalingDevToneFreqOnDuration
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.25.1.5
Prev sibling: emtaSignalingDevToneDbLevel
Next sibling: emtaSignalingDevToneFreqOffDuration
Status: current
Size list: 1: 0..5000
Units: Milliseconds
Description: This MIB Object represents the duration for which the frequency
reference corresponding to the tone type is turned on.
emtaSignalingDevToneFreqOffDuration
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.25.1.6
Prev sibling: emtaSignalingDevToneFreqOnDuration
Next sibling: emtaSignalingDevToneFreqRepeatCount
Status: current
Size list: 1: 0..5000
Units: Milliseconds
Description: This MIB Object represents the duration for which the frequency
reference corresponding to the tone type is turned off.
emtaSignalingDevToneFreqRepeatCount
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.25.1.7
Prev sibling: emtaSignalingDevToneFreqOffDuration
Status: current
Size list: 1: 0..5000
Description: This MIB Object indicates the number of times to repeat the cadence
cycle represented by the on/off durations (refer to the MIB objects
emtaSignalingDevToneFreqOnDuration
Ubee Interactive
emtaSignalingDevToneFreqOffDuration). Setting this object may

result in a tone duration longer or shorter than the overall signal
duration specified by the time out (TO) object for the
corresponding tone type. If the value of this MIB Object indicates
a longer duration than the specified by the TO, the latter
overrules the former and the desired tone duration will be
truncated according to the TO. However, if the repeat count results
in a shorter tone duration than the signal duration specified by
the TO, the tone duration defined by the repeat count takes
precedence over the TO and will end the signal event. In this case,
the TO represents a time not to be exceeded for the signal. It is
recommended to ensure proper telephony signaling that the TO
count time duration. A value of zero means the tone sequence is to
be played once but not repeated.
emtaSignalingChatterLineMonitorInterval
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.26
Prev sibling: emtaSignalingDevMultiFreqToneTable
Next sibling: emtaSignalingChatterLinePulseDialRejectThreshold
Status: current
Units: minutes
Description: This object specifies the monitoring interval for the conditions
of interest when detecting a chattering line fault. If the
specified threshold for a given error condition is reached or
exceeded over this monitoring interval, the EMTA will log a vendor-
defined PacketCable event to alert the operator of the fault
condition. The value of this object must be set via the MTA config
file for persistence.
emtaSignalingChatterLinePulseDialRejectThreshold
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.27
Prev sibling: emtaSignalingChatterLineMonitorInterval
Next sibling: emtaSignalingChatterLineDigitMapMismatchThreshold
Status: current
Description: This object specifies the rejected dial pulse error threshold. If
this threshold is reached or exceeded over the monitoring interval
as configured via emtaSignalingChatterLineMonitorInterval, the
EMTA will log a vendor-defined PacketCableevent to alert the
operator of the fault condition. The value of this object must be
emtaSignalingChatterLineDigitMapMismatchThreshold
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.28
Prev sibling: emtaSignalingChatterLinePulseDialRejectThreshold
Next sibling: emtaSignalingChatterLineLoopOpenCloseThreshold
Ubee Interactive
Status: current
Description: This object specifies the digit map mismatch error threshold. If
this threshold is reached or exceeded over the monitoring interval
as configured via emtaSignalingChatterLineMonitorInterval, the
EMTA will log a vendor-defined PacketCableevent to alert the
operator of the fault condition. The value of this object must be
emtaSignalingChatterLineLoopOpenCloseThreshold
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.29
Prev sibling: emtaSignalingChatterLineDigitMapMismatchThreshold
Next sibling: emtaSignalingChatterLineROHEnable
Status: current
Description: This object specifies the valid line activity threshold. If this
threshold is reached or exceeded over the monitoring interval as
configured via emtaSignalingChatterLineMonitorInterval, the EMTA
will log a vendor-defined PacketCableevent to alert the operator
of the fault condition. The value of this object must be set via
the MTA config file for persistence.
emtaSignalingChatterLineROHEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.30
Prev sibling: emtaSignalingChatterLineLoopOpenCloseThreshold
Next sibling: emtaSignalingMaxNumberCallStatsStored
Status: current
Description: This oject controls the automatic ROH test run resulting from
potential chattering line failures. When set to 'true(1)', the
automatic chatter line ROH test is enabled, and the EMTA will
automatically run the ROH line test whenever a threshold for a
monitored chattering line conditions (as configured by
emtaSignalingChatterLinePulseDialRejectThreshold,
emtaSignalingChatterLineDigitMapMismatchThreshold, and
emtaSignalingChatterLineLoopOpenCloseThreshold) has been reached
or exceeded indicating potential trouble on the line. When set to
'false(2)', the automatic chatter line ROH test is disabled, and
the ROH status shown in the vendor-defined PacketCable event
logged will indicate that ROH is disabled. The value of this object
must be set via the MTA config file for persistence.
emtaSignalingMaxNumberCallStatsStored
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.31
Prev sibling: emtaSignalingChatterLineROHEnable
Next sibling: emtaSignalingAdjustedFskTransmissionLevel
Status: current
Ubee Interactive

Description: This object contains the max number of calls for which the eMTA
stores statistics in the emtaStatsCallTable. The maximum number of
calls stored is based on the number of ports supported by the MTA:
1 port device: 2 - 10 calls
More than 4 port device: 2 - 50 calls
emtaSignalingAdjustedFskTransmissionLevel
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.32
Prev sibling: emtaSignalingMaxNumberCallStatsStored
Next sibling: emtaSignalingSdpSuppression
Status: current
Description: This object controls whether the MTA sets the FSK generation based
on the desired open circuit output voltage or the desired output
power level.
When set to 'true(1)', the FSK generation is generated based on
voltage and the unterminated voltage measured at tip and ring in
the onhook state will be the same as the terminated voltage in the
offhook state.
When set to 'false(2)', the FSK generation is generated based on
power levels and the terminated voltage measured at tip and ring
will be the same for both the onhook and offhook states. In this
mode, if measured into no termination, the voltage level in the
onhook state will be approximately 6dB higher than the terminated
voltage in the offhook state.
emtaSignalingSdpSuppression
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.33
Prev sibling: emtaSignalingAdjustedFskTransmissionLevel
Next sibling: emtaSignalingRSIPResponseTimer
Base syntax: BITS
Status: current
Value list: 1: rFC3407BasicSuppressed(0)
2: rFC3407T38Suppressed(1)
3: t38AttributeSuppressed(2)
4: xPCAttributeSuppressed(3)
Description: This MIB object is used to suppress individual SDP attributes sent
from the MTA.
If bit RFC3407BasicSuppressed(0) is set, the EMTA suppresses the
basic set of RFC3407 simple SDP capability parameters and
descriptions not needed in negotiation.
If bit RFC3407T38Suppressed(1) is set, the EMTA suppresses the
RFC3407 simple SDP capability parameters and descriptions for T.38
negotiation if T.38 strict is not used.
If bit T38AttributeSuppressed(2) is set, the EMTA suppresses the
T.38 attributes in the SDP.
If bit XPCAttributeSuppressed(3) is set, the EMTA suppresses the
X-PC attributes in the SDP if no RTP/RTCP authentication and
encryption is used.
The default value of this object is to have no suppression of the
SDP. The default value of this object corresponds to the
functionality compliant with the PacketCable requirements - all
Ubee Interactive
bits are cleared. Setting any bits other than the RFC3407Basic bit
would be PacketCable non-compliant. Note that this default value
may change based on build specific options
emtaSignalingRSIPResponseTimer
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.34
Prev sibling: emtaSignalingSdpSuppression
Next sibling: emtaSignalingMgcpLockstepActivation
Status: current
Size list: 1: 0..36000
Units: seconds
Description: This objects identifies the length of time, in seconds, after
provisioning is complete that the eMTA should wait for RSIP
exchange to complete before reprovisioning. This timer starts at
PacketCable provisioning complete (PacketCable MTA-25). If the
eMTA has not received a response to the RSIP sent for the
configured time period following provisioning complete, then the
eMTA will restart provisioning (go back to PacketCable MTA-1).
This object should only be changed by the configuration file.
emtaSignalingMgcpLockstepActivation
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.35
Prev sibling: emtaSignalingRSIPResponseTimer
Next sibling: emtaSignalingMgcpQuarantineModeOverrideBehavior
Status: current
Description: This object contains the value which activates/deactivates MGCP
lockstep mode. Setting this object to true(1) causes the MTA to
activate lockstep mode, allowing MTA to use either lockstep or loop
mode as per RFC2705. Setting this object to false(2) causes the
MTA to deactivate lockstep mode, allowing MTA to use only loop mode
as per RFC2705. In this configuration, MTA will only operate in
loop mode, 'step' mode is disallowed. Any future 'step' mode
request from CallAgent, SNMP or CLI command, will either be ignored
or result in an 'inconsistentValue' error. The
emtaSignalingEndptCtrlMgcpQuarantineMode for each endpoint is
updated to loop(2) at the time this MIB is set to false(2).
emtaSignalingMgcpQuarantineModeOverrideBehavior
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.36
Prev sibling: emtaSignalingMgcpLockstepActivation
Next sibling: emtaSignalingMgcpStepToLoopModeBehavior
Status: current
Value list: 1: emtaPreferred(1)
2: callAgentPreferred(2)
Default values: 1: CallAgentPreferred (name)
Ubee Interactive
Description: This object contains the value which decribes the MTA behavior when
Call Agent explicitly requests a quarantine mode that conflicts
with MTA current setting in
emtaSignalingEndptCtrlMgcpQuarantineMode. Setting this object to
emtaPreferred(1) causes MTA current setting in
emtaSignalingEndptCtrlMgcpQuarantineMode, having preference over
the Quarantine mode requested by Call Agent. Any quarantine mode
request in the MGCP message is ignored. Setting this object to
callAgentPreferred(2) causes Quarantine mode requested by Call
Agent having preference over MTA current setting in
emtaSignalingEndptCtrlMgcpQuarantineMode. In this configuration,
emtaSignalingEndptCtrlMgcpQuarantineMode value will be updated to
the mode requested by Call Agent if the requested Quarantine mode
is supported. However, the quarantine mode is ignored if the
requested quarantine mode is not supported. (Call Agent requests
step mode when step mode is deactivated by
emtaSignalingMgcpLockstepActivation)
emtaSignalingMgcpStepToLoopModeBehavior
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.37
Prev sibling: emtaSignalingMgcpQuarantineModeOverrideBehavior
Next sibling: emtaSignalingMediaSecurity
Status: current
Value list: 1: processAllQuarantinedEvents(1)
2: flushQuarantinedEvents(2)
Default values: 1: ProcessAllQuarantinedEvents (name)
Description: This object contains the value which decribes the EMTA behavior
for the stored quarantined events when EMTA changes from 'step' to
'loop' quarantine mode in
emtaSignalingEndptCtrlMgcpQuarantineMode. Setting this object to
processAllQuarantinedEvents(1) causes the MTA to send NTFY
messages for all quarantined events stored during lockstep.
Setting this object to flushQuarantinedEvents(2) causes the MTA to
flush the Quarantined Event buffer. All stored quarantined events
are discarded.
emtaSignalingMediaSecurity
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.38
Prev sibling: emtaSignalingMgcpStepToLoopModeBehavior
Next sibling: emtaSignalingIPSecOnCMSRedirection
Status: current
Description: This object controls the MTA advertisement of the RTP security
ciphersuites.
Setting this object to true(1) enables the MTA to advertise the
full list of supported RTP security ciphersuites as required by
PacketCable specification.
Setting this object to false(2) causes the MTA to only advertize
the NULL authentication and encryption algorithms (ciphersuite
sets 60/50, 80/70) which essentially disables the RTP security
functionality on the MTA. Setting this MIB to disabled would be
PacketCable non-compliant.
Ubee Interactive
Note that, setting this object to false(2), along with the

XPCAttributeSuppressed(3) bit of emtaSignalingSdpSuppression MIB,
would cause the MTA to not advertise any security parameters at
all in the SDP.
The default value of this object corresponds to the functionality
compliant with the PacketCable requirements when security
advertising is enabled. Setting this MIB to disabled would be
PacketCable non-compliant. Note that this default value may change
based on build specific options.
emtaSignalingIPSecOnCMSRedirection
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.39
Prev sibling: emtaSignalingMediaSecurity
Next sibling: emtaSignalingDlcxOsiDelay
Status: current
Value list: 1: iPSecOn(1)
2: iPSecOff(2)
3: iPSecSame(3)
Default values: 1: IPSecOn (name)
Description: This object specifies the IPSec Setting of the redirected CMS
server when the redirected CMS server does not exist in the
pktcMtaDevCmsTable MIB database. A new entry duplicating the
setting of the previous CMS is created in the pktcMtaDevCmsTable.
The CMS FQDN of the newly created entry is updated to be the FQDN
of the redirected CMS. Depending on the value of this MIB, the
pktcMtaDevCmsIpsecCtrl of the redirected CMS is set to true or
false, enabling or disabling IPSec of the redirected CMS.
Setting this object to IPSecOn(1) enables the IPsec of the
redirected CMS. Setting this object to IPSecOff(2) disables the
IPsec of the redirected CMS. Setting this object to IPSecSame(3)
causes the IPsec setting of the previous CMS to be copied over and
applied to the redirected CMS.
Note that when the value is not 'IPSecOn', IPSec of a redirected
CMS may become disabled. PacketCable Security specification (PKT-
SP-SEC1.5-I02-070412.doc, section 6.5.3 Kerberized IPSec,
REQ2992.2.5, TC 790) specified that IPSec MUST be enabled. Thus,
this MIB may violate PacketCable specification.
emtaSignalingDlcxOsiDelay
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.40
Prev sibling: emtaSignalingIPSecOnCMSRedirection
Next sibling: emtaSignalingPlayZeroDurationPkt
Status: current
Size list: 1: 0..15
Description: This object configures the delay in seconds between the completion
of the processing of a DLCX message and the automatic application
of an OSI signal to the analog line associated with the deleted
connection. Setting a value of 0 disables this feature. Note that
the default value of the object may change based on build specific
options.
Ubee Interactive
emtaSignalingPlayZeroDurationPkt
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.4.41
Prev sibling: emtaSignalingDlcxOsiDelay
Status: current
Description: This object configures whether an endpoint should transmit a DTMF
telephone-event packet containing a duration field of value zero.
If this object is set to false, MTA will ignore the DTMF packet
which has a duration coded to zero. If this object is set to true,
MTA shall not ignore the packet and shall continue playing the tone
until an explicit end of tone conditions occurs. End of Tone
conditions occur when Tone has been played for at least 50
milliseconds and when either of the following conditions occurs:
an explicit end of tone packet has been received, tone has exceeded
100 milliseconds, or the packet for start of another tone has
arrived. Note that the default value of the object may change based
on build specific options.
emtaStatsEndptHookState
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.1.1.1
Parent: emtaStatsEndptEntry
Next sibling: emtaStatsEndptQuarantineState
Status: current
Value list: 1: onHook(1)
2: offHook(2)
3: disconnected(3)
4: onHookPlusNCSActivity(4)
5: busyTalking(5)
Description: This object reflects the 'hook state' of a MTA endpoint. The
onHook(1) state indicates that the endpoint is 'on hook'. The
offHook(2) state indicates that the endpoint is 'off hook'. The
disconnected(3) state indicates that the physical connection of
the phone to a port is disconnect. onHookPlusNCSActivity (4) state
indicates that the end point is 'on hook' and the presence of 'NCS
Activity' on the line. 'NCS Activity' by definition includes: an
active timeout signal, brief signal, or existence of an NCS
connection. busyTalking (5) state indicates that the end point is
'off hook' and the presence of voice connection on the line. Note
that the state of this object does not depend on the provision
state of the endpoint.
emtaStatsEndptQuarantineState
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.1.1.2
Prev sibling: emtaStatsEndptHookState
Next sibling: emtaStatsEndptSlicOverTempStatus
Status: current
Value list: 1: normal(1)
2: notification(2)
3: lockstep(3)
Ubee Interactive
4: extendedlockstep(4)
Description: This object reflects the state of Endpoint. When the endpoint is
in 'notification', 'lockstep', or 'extended lockstep' states, the
E-MTA reports the values of 'notification(2)', 'lockstep(3)', or
'extendedlockstep(4)', respectively. Else, the endpoint reports a
value of 'normal(1)'. 'Extended lockstep' is defined as the state
when the E-MTA is in the lockstep state for longer than 2 minutes.
For more description about the states, refer to the PacketCable
Network Based Call signaling specification.
emtaStatsEndptSlicOverTempStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.1.1.3
Prev sibling: emtaStatsEndptQuarantineState
Next sibling: emtaStatsEndptOverCurrentStatus
Status: current
Description: This object reflects the SLIC status for the line regarding Over
Temperature condition. If this object has a value of true(1), it
indicates that the SLIC for this line is in Over Temperature
condition. Otherwise, the SLIC is operating under normal
Temperature conditions.
emtaStatsEndptOverCurrentStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.1.1.4
Prev sibling: emtaStatsEndptSlicOverTempStatus
Status: current
Description: This object reflects the status for the line regarding over-
current condition. If this object has a value of true(1), it
indicates that the line is in over-current condition. Otherwise,
the line is operating under normal current conditions.
emtaStatsRTPPktTxTotal
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.2
Parent: emtaMgmtStatistics
Prev sibling: emtaStatsEndptTable
Next sibling: emtaStatsRTPPktRxTotal
Status: current
Description: This object contains the total number of RTP packets sent for the
device since it was last started up (across all endpoints).
emtaStatsRTPPktRxTotal
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.3
Prev sibling: emtaStatsRTPPktTxTotal
Next sibling: emtaStatsRTPPktLostTotal
Ubee Interactive

Status: current
Description: This object contains the total number of RTP packets received for
the device since it was last started up (across all endpoints).
emtaStatsRTPPktLostTotal
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.4
Prev sibling: emtaStatsRTPPktRxTotal
Next sibling: emtaStatsRTPPktTxRecent
Status: current
Description: This object contains the total number of RTP packets lost for the
device since it was last started up (across all endpoints).
emtaStatsRTPPktTxRecent
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.5
Prev sibling: emtaStatsRTPPktLostTotal
Next sibling: emtaStatsRTPPktRxRecent
Status: current
Description: This object contains the total number of RTP packets sent for the
most recent call.
emtaStatsRTPPktRxRecent
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.6
Prev sibling: emtaStatsRTPPktTxRecent
Next sibling: emtaStatsRTPPktLostRecent
Status: current
Description: This object contains the total number of RTP packets received for
the most recent call.
emtaStatsRTPPktLostRecent
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.7
Prev sibling: emtaStatsRTPPktRxRecent
Next sibling: emtaStatsAvgJitterMeasurement
Status: current
Description: This object contains the percentage (%) of RTP packets lost for
the most recent call.
Ubee Interactive
emtaStatsAvgJitterMeasurement
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.8
Prev sibling: emtaStatsRTPPktLostRecent
Next sibling: emtaStatsMaxJitterMeasurement
Status: current
Description: This objects contains the average jitter measurements for the last
24 hours.
emtaStatsMaxJitterMeasurement
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.9
Prev sibling: emtaStatsAvgJitterMeasurement
Next sibling: emtaStatsRTPAvgLatency
Status: current
Description: This objects contains the maximum jitter measurements for the last
24 hours.
emtaStatsRTPAvgLatency
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.10
Prev sibling: emtaStatsMaxJitterMeasurement
Next sibling: emtaStatsMGCPResponseAvgLatency
Status: current
Units: milliseconds
Description: This objects contains the average latency/delay for RTP Packets
for the last 24 hours.
emtaStatsMGCPResponseAvgLatency
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.11
Prev sibling: emtaStatsRTPAvgLatency
Next sibling: emtaStatsSuccessfulMsgCount
Status: current
Units: milliseconds
Description: This objects contains the average latency/delay for MGCP Response
messages for the last 24 hours.
emtaStatsSuccessfulMsgCount
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.12
Ubee Interactive
Prev sibling: emtaStatsMGCPResponseAvgLatency

Next sibling: emtaStatsNegAckCount
Status: current
Description: This object contains the count of successful MGCP messages
transmitted to and received from Call Agent for the last 24 hours.
emtaStatsNegAckCount
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.13
Prev sibling: emtaStatsSuccessfulMsgCount
Next sibling: emtaStatsNoNTFYAckCount
Status: current
Description: This object contains the number of MGCP error responses sent to
and received from Call Agent for the last 24 hours.
emtaStatsNoNTFYAckCount
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.14
Prev sibling: emtaStatsNegAckCount
Next sibling: emtaStatsLastNCSMsgTx
Status: current
Description: This object contains the number of times no MGCP response was
received for a sent NTFY in the last 24 hours.
emtaStatsLastNCSMsgTx
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.15
Prev sibling: emtaStatsNoNTFYAckCount
Next sibling: emtaStatsLastNCSMsgRx
Status: current
Description: This object contains the last NCS message sent to Call Agent.
emtaStatsLastNCSMsgRx
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.16
Prev sibling: emtaStatsLastNCSMsgTx
Next sibling: emtaStatsRTPPktLostRatio
Status: current
Description: This object contains the last NCS message received from Call Agent.
Ubee Interactive
emtaStatsRTPPktLostRatio
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.17
Prev sibling: emtaStatsLastNCSMsgRx
Next sibling: emtaStatsCallTable
Status: current
Units: percent
Description: This object contains the packet loss ratio, derived from the total
number of packets reported lost, divided by the total number of
packets sent and received, expressed as a percentage.
emtaStatsCallIndex
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.1
Parent: emtaStatsCallEntry
Next sibling: emtaStatsCallMOSCQScore
Status: current
Size list: 1: 1..50
Description: This object provides the sequencing of per call measurements. The
number of measurements stored in this table is dependent on
emtaSignalingMaxNumberCallStatsStored. The most recent call will
always be indexed 1, the next most recent call will be indexed 2,
and so on. The index for each call entry will increase with each
new call entry. The index of the least recent call will not be
greater than the value stored in
emtaSignalingMaxNumberCallStatsStored.
emtaStatsCallMOSCQScore
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.2
Prev sibling: emtaStatsCallIndex
Next sibling: emtaStatsCallRFSignalToNoiseLevel
Status: current
Value list: 1: bad(1)
2: poor(2)
3: fair(3)
4: good(4)
5: excellent(5)
Description: This object reports the numerical indication of the perceived
quality of received media after compression and/or transmission.
The MOS score is expressed as a single number in the range of 1 to
5. The associated quality characteristics defined for each MOS
score:
bad(1) - Very annoying
poor(2) - Annoying
fair(3) - Slightly annoying
good(4) - Perceptible, but not annoying
excellent(5) - Imperceptible
Ubee Interactive
emtaStatsCallRFSignalToNoiseLevel
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.3
Prev sibling: emtaStatsCallMOSCQScore
Next sibling: emtaStatsCallResidualEchoRetLoss
Status: current
Description: This object reports the general measurement of the ratio of RF
signal power to noise power.
emtaStatsCallResidualEchoRetLoss
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.4
Prev sibling: emtaStatsCallRFSignalToNoiseLevel
Next sibling: emtaStatsCallDestEndpntInfo
Status: current
Units: dB
Description: This object reports the residual echo return loss, which relates
to the effective echo level that a user would hear. It is the ratio
between the transmitted signal level and the received echo level
expressed in dB.
emtaStatsCallDestEndpntInfo
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.5
Prev sibling: emtaStatsCallResidualEchoRetLoss
Next sibling: emtaStatsCallTotalPktSent
Composed syntax: DisplayString
Status: current
Description: This object reports the IP address for the terminating end point
of each call originated from the eMTA.
emtaStatsCallTotalPktSent
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.6
Prev sibling: emtaStatsCallDestEndpntInfo
Next sibling: emtaStatsCallTotalOctSent
Status: current
Description: This object reports the total number of packets transmitted by the
sender since starting transmission on the connection.
emtaStatsCallTotalOctSent
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.7
Ubee Interactive
Prev sibling: emtaStatsCallTotalPktSent
Next sibling: emtaStatsCallTotalPktRecvd
Status: current
Description: This object reports the total number of payload octets transmitted
in RTP packets by the sender since starting transmission on the
connection.
emtaStatsCallTotalPktRecvd
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.8
Prev sibling: emtaStatsCallTotalOctSent
Next sibling: emtaStatsCallTotalOctRecvd
Status: current
Description: This object reports the total number of packets received by the
sender since starting transmission on the connection.
emtaStatsCallTotalOctRecvd
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.9
Prev sibling: emtaStatsCallTotalPktRecvd
Next sibling: emtaStatsCallTotalPktLost
Status: current
Description: This object reports the total number of payload octets received in
RTP packets by the sender since starting transmission on the
connection.
emtaStatsCallTotalPktLost
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.10
Prev sibling: emtaStatsCallTotalOctRecvd
Next sibling: emtaStatsCallIntervalJitter
Status: current
Description: This object reports the total number of RTP data packets that have
been lost since the beginning of reception. This number is defined
as the number of packets less the number of packets actually
received, where the number of packets received includes any which
are late or duplicates.
emtaStatsCallIntervalJitter
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.11
Prev sibling: emtaStatsCallTotalPktLost
Ubee Interactive
Next sibling: emtaStatsCallAvgTxDelay

Status: current
Units: Milliseconds
Description: This object reports an estimate of the statistical variance of the
RTP data packet inter-arrival time.
emtaStatsCallAvgTxDelay
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.12
Prev sibling: emtaStatsCallIntervalJitter
Next sibling: emtaStatsCallJBDiscardRate
Status: current
Units: Milliseconds
Description: This object reports an estimate of the network latency. The is the
average value of the difference between the NTP time stamp
indicated by the senders of the RTCP messages and the NTP time
stamp of the receivers, measured when the messages are received.
emtaStatsCallJBDiscardRate
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.13
Prev sibling: emtaStatsCallAvgTxDelay
Next sibling: emtaStatsCallJBAdjRate
Status: current
Description: This object reports the number of packets discarded by the eMTA's
jitter buffer.
emtaStatsCallJBAdjRate
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.14
Prev sibling: emtaStatsCallJBDiscardRate
Next sibling: emtaStatsCallJBMaxSize
Status: current
Units: Milliseconds
Description: This object reports the jitter buffer's adjustment rate.
emtaStatsCallJBMaxSize
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.15
Prev sibling: emtaStatsCallJBAdjRate
Next sibling: emtaStatsCallNetRdTripDelay
Ubee Interactive

Status: current
Units: Milliseconds
Description: This object reports the maximum size of the jitter buffer, in
milliseconds.
emtaStatsCallNetRdTripDelay
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.16
Prev sibling: emtaStatsCallJBMaxSize
Next sibling: emtaStatsCallSignalLevel
Status: current
Units: Milliseconds
Description: This object reports the round trip delay (latency) for a packet to
travel from the originating end of a call to the terminating end
of a call, and back to the originating end of a call.
emtaStatsCallSignalLevel
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.17
Prev sibling: emtaStatsCallNetRdTripDelay
Next sibling: emtaStatsCallNoiseLevel
Status: current
Units: dB
Description: This object reports the audio signal levels.
emtaStatsCallNoiseLevel
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.18
Prev sibling: emtaStatsCallSignalLevel
Next sibling: emtaStatsCallRfTxLevel
Status: current
Units: dB
Description: This object reports the audio noise levels.
emtaStatsCallRfTxLevel
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.19
Prev sibling: emtaStatsCallNoiseLevel
Next sibling: emtaStatsCallRfRxLevel
Status: current
Units: dBmV
Description: This object reports the RF transmit level.
Ubee Interactive
emtaStatsCallRfRxLevel
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.20
Prev sibling: emtaStatsCallRfTxLevel
Next sibling: emtaStatsCallCallTrace
Status: current
Units: dBmV
Description: This object reports the RF receive level.
emtaStatsCallCallTrace
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.21
Prev sibling: emtaStatsCallRfRxLevel
Next sibling: emtaStatsCallStartTime
Status: current
Description: This object reports the capture of MGCP/NCS or SIP message series
used to establish and terminate call.
The MGCP/NCS call trace information include the following
information:
(1) The NCS command/message (CRCX, DLCX, MDCX, etc.)
(2) The transaction identifier (transaction number)
(3) Any applicable command parameters (CallID, DigitMap,
DetectEvents, etc)
(4) The destination for the command/message (eg
aaln/1@ubeeinteractive.com)
(5) The protocol version numbers for both MGCP and NCS
The SIP call trace information include the following information:
(1) The SIP command/message (INVITE, ACK, BYE etc.)
(2) The transaction identifier (Call-ID)
(3) Any applicable command parameters
(4) The destination for the command/message (eg
sip:xxxx@ubeeinteractive.com)
(5) The protocol version numbers for SIP
emtaStatsCallStartTime
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.22
Prev sibling: emtaStatsCallCallTrace
Next sibling: emtaStatsCallEndTime
Status: current
Description: This object reports the time stamp indicating the beginning of the
last call made from the MTA.
emtaStatsCallEndTime
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.23
Ubee Interactive
Prev sibling: emtaStatsCallStartTime

Next sibling: emtaStatsCallPhoneNumber
Status: current
Description: This object reports the time stamp indicating the end of the last
call made from the MTA.
emtaStatsCallPhoneNumber
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.24
Prev sibling: emtaStatsCallEndTime
Next sibling: emtaStatsCallLine
Status: current
Description: This object reports the phone number of the remote party.
emtaStatsCallLine
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.25
Prev sibling: emtaStatsCallPhoneNumber
Next sibling: emtaStatsCallDirection
Status: current
Description: This object reports the line on which the call is being made or
being received.
emtaStatsCallDirection
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.26
Prev sibling: emtaStatsCallLine
Next sibling: emtaStatsCallMOSLQScore
Status: current
Value list: 1: incoming(1)
2: outgoing(2)
Description: This object reports the direction of the call.
emtaStatsCallMOSLQScore
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.27
Prev sibling: emtaStatsCallDirection
Next sibling: emtaStatsCallDialMode
Status: current
Ubee Interactive

Value list: 1: bad(1)
2: poor(2)
3: fair(3)
4: good(4)
5: excellent(5)
Description: This object reports the numerical indication of the perceived
listening quality. The MOS score is expressed as a single number
in the range of 1 to 5. The associated quality characteristics
defined for each MOS score:
bad(1) - Very annoying
poor(2) - Annoying
fair(3) - Slightly annoying
good(4) - Perceptible, but not annoying
excellent(5) - Imperceptible
emtaStatsCallDialMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.6.5.18.1.28
Prev sibling: emtaStatsCallMOSLQScore
Status: current
Value list: 1: unknown(0)
2: pulseDial(1)
3: dtmfToneDial(2)
Description: This object reports the dial mode of the call.
12.1.9 UBEE-FTP-MGMT-MIB
ftpIpStackInterface
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.1
Module: UBEE-FTP-MGMT-MIB
Parent: ftpMgmt
Next sibling: ftpServerAddressType
Status: current
Size list: 1: 1..8
Description: Specifies the IP stack which will be used for FTP transfers.
ftpServerAddressType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.2
Parent: ftpMgmt
Prev sibling: ftpIpStackInterface
Next sibling: ftpServerAddress
Composed syntax: InetAddressType
Status: current
Description: The type of Internet address used for ftpServerAddress.
Ubee Interactive
ftpServerAddress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.3
Parent: ftpMgmt
Prev sibling: ftpServerAddressType
Next sibling: ftpServerPort
Composed syntax: InetAddress
Status: current
Description: The Internet address of the FTP server used for FTP transfers.
ftpServerPort
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.4
Parent: ftpMgmt
Prev sibling: ftpServerAddress
Next sibling: ftpUserName
Status: current
Size list: 1: 1..65535
Description: The TCP port on the FTP server to which the client will attempt to
connect.
ftpUserName
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.5
Parent: ftpMgmt
Prev sibling: ftpServerPort
Next sibling: ftpPassword
Status: current
Default values: 1: <empty> (char-str)
Description: The user name to be used when logging in to the FTP server.
ftpPassword
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.6
Parent: ftpMgmt
Prev sibling: ftpUserName
Next sibling: ftpFilename
Status: current
Description: The password to be used when logging in to the FTP server.
ftpFilename
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.7
Ubee Interactive
Parent: ftpMgmt
Prev sibling: ftpPassword
Next sibling: ftpCommand
Status: current
Description: The path to the file to be transferred.
ftpCommand
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.8
Parent: ftpMgmt
Prev sibling: ftpFilename
Next sibling: ftpTransferStatus
Status: current
Value list: 1: cancel(0)
2: get(1)
3: put(2)
Description: Used to invoke an FTP command, or cancel a command which is in
progress. When read, indicates the most recent command. Note that
the value of this object does not indicate the current transfer
status. Current status should be read from ftpTransferStatus.
ftpTransferStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.9
Parent: ftpMgmt
Prev sibling: ftpCommand
Next sibling: ftpTransferPayloadBytes
Status: current
Value list: 1: idle(0)
2: fileStatusOk(150)
3: serviceReady(200)
4: sessionReady(221)
5: transferComplete(226)
6: passwordOk(230)
7: userNameOk(331)
8: serviceNotAvail(421)
9: invalidLogin(530)
10: fileNotFound(550)
11: socketConnectFailure(600)
Description: Indicates the status of the file transfer which is currently in
progress, or which most recently completed. If no file transfer
has been initiated, this object returns a value of idle(0).
ftpTransferPayloadBytes
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.10
Parent: ftpMgmt
Prev sibling: ftpTransferStatus
Next sibling: ftpTransferTotalBytes
Ubee Interactive
Status: current
Description: Indicates the number of file data payload bytes transferred during
the file transfer which is currently in progress, or which most
recently completed. For transfers which complete successfully, the
value of this object will be equal to the size of the file
transferred.
ftpTransferTotalBytes
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.11
Parent: ftpMgmt
Prev sibling: ftpTransferPayloadBytes
Next sibling: ftpTransferElapsedTime
Status: current
Description: Indicates the total number of bytes transferred during the file
transfer which is currently in progress, or which most recently
completed. This value includes file data payload as well as FTP
framing data and all IP and layer 2 headers. This value should be
used when calculating transfer throughput.
ftpTransferElapsedTime
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.12
Parent: ftpMgmt
Prev sibling: ftpTransferTotalBytes
Next sibling: ftpTransferThroughput
Status: current
Units: milliseconds
Description: Indicates the total elapsed time of the file transfer which is
currently in progress, or which most recently completed.
ftpTransferThroughput
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.13
Parent: ftpMgmt
Prev sibling: ftpTransferElapsedTime
Next sibling: ftpPutFileSize
Status: current
Units: bits per second
Description: Indicates the calculated throughput during the file transfer which
is currently in progress, or which most recently completed. This
value is calculated by dividing ftpTransferTotalBytes by
ftpTransferElapsedTime.
ftpPutFileSize
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.14
Parent: ftpMgmt
Prev sibling: ftpTransferThroughput
Next sibling: ftpPutFilenamePath
Ubee Interactive

Status: current
Size list: 1: 1..50000
Units: kBytes
Description: The number of data bytes to send for a FTP PUT (upload) operation.
The PUT data is internally generated random data of the size
specified by this object. The filesize is specified in kilobytes.
ftpPutFilenamePath
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.17.15
Parent: ftpMgmt
Prev sibling: ftpPutFileSize
Status: current
Description: The FTP PUT (upload) operation uses a unique (internally
generated) upload filename. This object specifies the path to be
prepended to the upload filename. The location, specified by this
path, should have write/delete access on the server. If not
specified, no path is prepended to the filename. If specified the
path value should end with the appropriate separator e.g., \ or /.
12.1.10 UBEE-HOST-SEC-MIB
ubeeHostSecIndex
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.16.1.1.1
Module: UBEE-HOST-SEC-MIB
Parent: ubeeHostSecurityEntry
Next sibling: ubeeHostSecUsername
Status: current
Size list: 1: 0..32
Description: This object uniquely identifies the security information that
pertains to this row in the ubeeHostSecurityTable. The value of
this object is context sensitive, that is, this value has meaning,
but that meaning is known by the managed system and is outside the
scope of this document.
ubeeHostSecUsername
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.16.1.1.2
Prev sibling: ubeeHostSecIndex
Next sibling: ubeeHostSecPassword
Status: current
Size list: 1: 0..16
Description: A user name.
Ubee Interactive
ubeeHostSecPassword
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.16.1.1.3
Prev sibling: ubeeHostSecUsername
Next sibling: ubeeHostSecLevel
Status: current
Description: The password associated with this row. If the value of this object
is the zero-length string, then no password is required on the host
system for this user.
ubeeHostSecLevel
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.16.1.1.4
Prev sibling: ubeeHostSecPassword
Next sibling: ubeeHostSecStatus
Status: current
Description: The security level of ubeeHostSecUsername. Note that the meaning
of this value is system dependent.
ubeeHostSecStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.16.1.1.5
Prev sibling: ubeeHostSecLevel
Status: current
Description: Controls and reflects the status of rows in this table. Rows in
this table may be created by either the create-and-go or create-
and-wait paradigms. Setting the value of this object to active,
either directly or indirectly via create-and-go, will cause the
row to be written to the host security system. It is expected that
as soon as the row is written to the host security system, the row
may be made unavailable to management. This may be done by removing
the entry from the table, removing the entry from all views, or
rendering the entry inaccessible via some other mechanism.
12.1.11 UBEE-HTTP-MGMT-MIB
httpAdminId
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.3.1
Module: UBEE-HTTP-MGMT-MIB
Parent: httpMgmt
Next sibling: httpAdminPassword
Ubee Interactive
Status: current
Description: Controls and reflects the user name for admin level HTTP
priveleges.
httpAdminPassword
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.3.2
Parent: httpMgmt
Prev sibling: httpAdminId
Next sibling: httpUserId
Status: current
Description: Controls and reflects the password for admin level HTTP
priveleges.
httpUserId
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.3.3
Parent: httpMgmt
Prev sibling: httpAdminPassword
Next sibling: httpUserPassword
Status: current
Description: Controls and reflects the user name for user level HTTP priveleges.
httpUserPassword
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.3.4
Parent: httpMgmt
Prev sibling: httpUserId
Next sibling: httpIpStackInterfaces
Status: current
Description: Controls and reflects the password for user level HTTP priveleges.
httpIpStackInterfaces
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.3.5
Parent: httpMgmt
Prev sibling: httpUserPassword
Next sibling: httpAdvancedAccessEnabled
Base syntax: BITS
Status: current
Value list: 1: interface1(0)
2: interface2(1)
3: interface3(2)
4: interface4(3)
Ubee Interactive
5: interface5(4)
6: interface6(5)
7: interface7(6)
8: interface8(7)
Description: Controls and reflects the IP stack interfaces on which an HTTP
server is active. By default, the HTTP server is enabled only on
the private IP stack interface.
httpAdvancedAccessEnabled
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.3.6
Parent: httpMgmt
Prev sibling: httpIpStackInterfaces
Next sibling: httpPasswordOfTheDaySeed
Base syntax: BITS
Status: current
2: interface2(1)
3: interface3(2)
4: interface4(3)
5: interface5(4)
6: interface6(5)
7: interface7(6)
8: interface8(7)
Description: Controls and reflects the IP stack interfaces on which advanced
access is allowed. By default, advanced access is allowed only on
remote stack interfaces.
httpPasswordOfTheDaySeed
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.3.7
Parent: httpMgmt
Prev sibling: httpAdvancedAccessEnabled
Next sibling: httpLoginTimeout
Status: current
Description: Controls and reflects the seed used to generate the password of
the day.
httpLoginTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.3.8
Parent: httpMgmt
Prev sibling: httpPasswordOfTheDaySeed
Next sibling: httpWanAccessTimeout
Status: current
Units: seconds
Description: Controls the timeout of the webpage login in seconds.
httpWanAccessTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.3.9
Ubee Interactive
Parent: httpMgmt
Prev sibling: httpLoginTimeout
Status: current
Size list: 1: 0..86400
Units: seconds
Description: This object controls the length of time after which HTTP access
via the WAN interface will be terminated if no HTTP activity via
the WAN interface is detected within this period. If set to a value
of 0, there will be no such timeout in effect. The timer begins
running when the HTTP server starts. After the number of seconds
specified by this object has elapsed, if no http traffic has been
detected via the WAN interface, a filter will be created which
drops all HTTP traffic destined to any of the device's IP addresses
which arrives via the WAN interface. If any HTTP activity via the
WAN interface is detected during the period of time alloted by this
object, the timer will be reset. Setting this object to any value
will cause the timer to be reset.
12.1.12 UBEE-PING-MGMT-MIB
pingTargetAddressType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.1
Module: UBEE-PING-MGMT-MIB
Parent: pingMgmt
Next sibling: pingTargetAddress
Status: current
Default values: 1: ipv4 (name)
Description: The type of Internet address used for pingTargetAddress. This
object may be changed while a ping is in progress.
pingTargetAddress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.2
Parent: pingMgmt
Prev sibling: pingTargetAddressType
Next sibling: pingNumPkts
Status: current
Default values: 1: 00000000 (hex-str)
Description: Sets the Internet address of the entity to be pinged. Note that if
an all-zeros value is specified for this object, then the ping will
be sent to the default gateway, if one exists. This object may be
changed while a ping is in progress.
pingNumPkts
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.3
Parent: pingMgmt
Prev sibling: pingTargetAddress
Next sibling: pingPktStartSize
Ubee Interactive

Status: current
Description: Allows the client to set the number of pings to be sent. This can
be set to any number between 1 and (2^32 - 1), or can be set to
'infinite' by setting the value to 0. Note that if set to infinite,
then the ping must be stopped explicitly in order to get it to
stop. This object may be changed while a ping is in progress.
pingPktStartSize
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.4
Parent: pingMgmt
Prev sibling: pingNumPkts
Next sibling: pingPktEndSize
Status: current
Size list: 1: 64..1518
Units: bytes
Description: Allows the client to set the initial size of the ping packets that
will be sent. This size includes the LLC header, IP header, ICMP
header, and the CRC32 at the end. You must specify values between
64 and 1518, which are the min and max size Ethernet frames. This
pingPktEndSize
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.5
Parent: pingMgmt
Prev sibling: pingPktStartSize
Next sibling: pingPktStepSize
Status: current
Size list: 1: 64..1518
Units: bytes
Description: Allows the client to set the final size of the ping packets that
will be sent. This size includes the LLC header, IP header, ICMP
header, and the CRC32 at the end. You must specify values between
64 and 1518, which are the min and max size Ethernet frames. This
pingPktStepSize
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.6
Parent: pingMgmt
Prev sibling: pingPktEndSize
Next sibling: pingInterval
Status: current
Size list: 1: -1454..1454
Units: bytes
Ubee Interactive
Description: Specifies the number of bytes by which each subsequent ping packet
is incremented. The step amount can be any number from 0 (which
leaves the ping size constant) up to (2^32 - 1). Note that after
adding the step amount to the current ping size, if this is greater
than the end size, then the current size will be wrapped around to
the start size. If you want to send ping packets of the same size
every time, set the start and end size to be equal, and the step
amount to be 0. To do a sweeping ping of every packet size, set
start to 64, end to 1518, and step amount to 1. You can set step
amount to -1 to sweep in the other direction. This object may be
pingInterval
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.7
Parent: pingMgmt
Prev sibling: pingPktStepSize
Next sibling: pingTimeout
Status: current
Units: milliseconds
Description: Allows the client to set the amount of time (in milliseconds) that
the device will sleep before sending a ping. Generally, this is
the time between when a ping reply is received and when the next
ping will be sent. Note that the amount of time between sending
one ping and sending the next ping varies depending on whether or
not you enable waiting for replies, and how long it takes to
receive the reply. If waiting for replies is disabled, then this
is the time between sending one ping and sending the next ping.
This object may be changed while a ping is in progress.
pingTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.8
Parent: pingMgmt
Prev sibling: pingInterval
Next sibling: pingVerifyReply
Status: current
Size list: 1: -1..65535
Units: milliseconds
Description: Allows the client to set the amount of time (in milliseconds) that
the device should wait for a reply after sending a ping. If set to
any non-negative value, then the device will send a ping and wait
for a response for the specified amount of time. Event if set to
0, the thread will check for and process a reply packet. If set to
-1, then the device will not wait at all, and won't even check for
any replies. This object may be changed while a ping is in
progress.
pingVerifyReply
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.9
Parent: pingMgmt
Prev sibling: pingTimeout
Next sibling: pingIpStackNumber
Ubee Interactive

Status: current
Description: Enables/disables verification of ping replies. If enabled, and if
waiting for replies is enabled, then if a reply is received, it
will verify that it matches the ping that was sent, and that all
of the data is intact. This object may be changed while a ping is
in progress.
pingIpStackNumber
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.10
Parent: pingMgmt
Prev sibling: pingVerifyReply
Next sibling: pingNow
Status: current
Size list: 1: 0..8
Description: Allows the client to select the IP stack from which the pings will
be sent. Specifying 0 means that the pings will be sent from the
same IP stack on which this MIB is hosted. This object may not be
pingNow
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.11
Parent: pingMgmt
Prev sibling: pingIpStackNumber
Next sibling: pingPktsSent
Status: current
Description: Starts or stops the pings, as well as indicating whether a ping is
in progress when read. If a ping is already in progress and this
object is set to true(1), then the ping will continue but the ping
statistics will be reset. This object may be changed while a ping
is in progress.
pingPktsSent
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.12
Parent: pingMgmt
Prev sibling: pingNow
Next sibling: pingRepliesReceived
Status: current
Description: Indicates the number of packets sent since the ping was started.
pingRepliesReceived
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.13
Parent: pingMgmt
Ubee Interactive
Prev sibling: pingPktsSent

Next sibling: pingRepliesVerified
Status: current
Description: Indicates the number of replies received since the ping was
started.
pingRepliesVerified
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.14
Parent: pingMgmt
Prev sibling: pingRepliesReceived
Next sibling: pingOctetsSent
Status: current
Description: Indicates the number of replies which were verified since the ping
was started.
pingOctetsSent
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.15
Parent: pingMgmt
Prev sibling: pingRepliesVerified
Next sibling: pingOctetsReceived
Status: current
Description: Indicates the total number of octets that have been sent in pings
since the ping was started.
pingOctetsReceived
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.16
Parent: pingMgmt
Prev sibling: pingOctetsSent
Next sibling: pingIcmpErrors
Status: current
Description: Indicates the total number of octets that have been sent in pings
since the ping was started.
pingIcmpErrors
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.17
Parent: pingMgmt
Prev sibling: pingOctetsReceived
Next sibling: pingLastIcmpError
Status: current
Ubee Interactive
Description: Indicates the total ICMP errors which have been received since the
ping was started.
pingLastIcmpError
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.5.18
Parent: pingMgmt
Prev sibling: pingIcmpErrors
Status: current
Description: Indicates value of the last ICMP error which was received, if any.
If there have been no errors, this object will have a value of 0.
12.1.13 UBEE-POWER-MGMT-MIB
powerMgmtIfDelay
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.20.1.1.1.1.1
Module: UBEE-POWER-MGMT-MIB
Parent: powerMgmtInterfaceEntry
Status: current
Size list: 1: -1..2147483647
Units: seconds
Description: Specifies the number of seconds following a battery or thermal
event before the interface will enter reduced power mode. If set
to -1, the interface will never enter reduced power mode and will
remain at full power until the trigger event is cleared.
Trigger events may include, but are not limited to, transition to
battery power or temperature which exceeds thermal threshold
limits. Reaction to reduced power mode is interface and device
dependent. Some interfaces may be disabled completely in reduced
power mode, others may have capabilities restricted in order to
conserve power.
powerMgmtCmChannelBondingStrategy
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.20.1.2.1
Parent: powerMgmtCableModem
Status: current
Value list: 1: noChange(0)
2: docsis3(1)
3: macReset1x1(2)
4: docsis3WithMacResetFallback(3)
Default values: 1: docsis3WithMacResetFallback (name)
Description: Determines the channel bonding transition strategy used when the
CM enters reduced power mode due to transition to battery power or
thermal event. For the purposes of this MIB description, 'reduced
power mode' means a mode of operation in which modem features are
intentionally disabled as a response to a trigger event. It is not
related to measures which may be employed during normal operation
with the goal of improving overall energy efficiency.
Ubee Interactive
When set to a value of noChange(0), the modem will not change the
channel bonding configuration in response to a transition to
reduced power mode. The device will continue to operate in the
bonding configuration that was in effect at the time the modem
entered reduced power mode.
When set to docsis3(1), the CM will conform to DOCSIS 3.0
requirements by dispatching a CM-STATUS message to the CMTS with
a type code of 9, 'CM operating on battery backup', indicating a
transition to battery mode. The CMTS is then expected to initiate
a DBC transaction which will reduce the number of channels used by
the CM.
Note that the 'battery backup' event code is used for either type
of trigger, because the CM-STATUS event set does not include
message codes for other reduced power events.
The value of macReset1x1(2) is used when the CM is operating in an
environment in which the CMTS does not respond to CM-STATUS
messaging for type code 9. In this mode, upon transition to reduced
power mode, the CM will re-initialize the MAC and re-register,
reporting a value of 0 for the Multiple Transmit Channel Support
modem capability and a value of 0 for the Multiple Receive Channel
Support modem capability. This disables
both downstream channel bonding and Multiple Transmit Channel
Mode. The CM will then register in DOCSIS 2.0 1x1 mode, resulting
in reduced power consumption.
Note that if a critical data service (such as a telephone call in
the case of a device which includes an eMTA) is in progress, the
MAC re-init will be deferred until the critical operation
completes. Upon transition back to full power mode, the CM will
again re-init the MAC, this time advertising Multiple Transmit
Channel support and Multiple Receive Channel Support to the extent
that the device is capable. Again, the re-init may be deferred if
necessary to avoid interruption of a critical data service.
The default value of cmStatusWith1x1Fallback(3) combines the
docsis3 mode with a fallback to macReset1x1 mode. Upon transition
to reduced power mode, the CM will dispatch a CM-STATUS message to
the CMTS in an attempt to change to 1x1 mode according to standard
DOCSIS mechanisms. If, after 30 seconds, the CM has not
transitioned to 1x1 mode then the CM will re-initialize the MAC
and re-register in 1x1 mode as described
above.
powerMgmtEthDefaultAutoPowerDownEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.20.1.3.1
Parent: powerMgmtEthernet
Next sibling: powerMgmtEthDefaultAutoPowerDownSleepTimer
Status: current
Description: Enables or disables the Ethernet automatic powerdown feature. If
enabled, the analog portion of the Ethernet PHY circuitry will be
shut off when the cable is not connected or the link partner power
is off. If the device has multiple Ethernet ports, the value of
this setting will be applied to all ports. The value of this object
is only applied at system initialization. If the value is modified,
the new value will be stored to non-volatile storage but will not
take effect until the next reboot.
powerMgmtEthDefaultAutoPowerDownSleepTimer
Type: OBJECT-TYPE
Ubee Interactive
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.20.1.3.2
Prev sibling: powerMgmtEthDefaultAutoPowerDownEnable
Next sibling: powerMgmtEthDefaultAutoPowerDownWakeTimer
Status: current
Size list: 1: 0..15000
Units: milliseconds
Description: When powerMgmtEthAutoPowerDownEnable is set to true(1), the value
of this object controls the length of time after the Ethernet link
drops before the PHY circuitry is disabled. If the device has
multiple Ethernet ports, the value of this setting will be applied
to all ports. The acceptable values for this object are device-
specific. If the object is set to a value which is within the
allowable range but does not match a discrete acceptable value for
the specific device, the value will automatically be set to the
nearest acceptable value. The value of this object is only applied
at system initialization. If the value is modified, the new value
will be stored to non-volatile storage but will not take effect
until the next reboot.
powerMgmtEthDefaultAutoPowerDownWakeTimer
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.20.1.3.3
Prev sibling: powerMgmtEthDefaultAutoPowerDownSleepTimer
Status: current
Size list: 1: 0..15000
Units: milliseconds
Description: When powerMgmtEthAutoPowerDownEnable is set to true(1), and the
Ethernet PHY has been disabled due to the link being down, the PHY
will be re-enabled upon restoration of link. The value of this
object controls the frequency at which a check for link restoration
is made. If the device has multiple Ethernet ports, the value of
this setting will be applied to all ports. The acceptable values
for this object are device-specific. If the object is set to a
value which is within the allowable range but does not match a
discrete acceptable value for the specific device, the value will
automatically be set to the nearest acceptable value. The value of
this object is only applied at system initialization. If the value
is modified, the new value will be stored to non-volatile storage
but will not take effect until the next reboot.
12.1.14 UBEE-RG-IP-MIB
rgIpNetworkSettingsCommit
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.1
Module: UBEE-RG-IP-MIB
Parent: rgIpMib
Next sibling: rgIpRipSettings
Ubee Interactive

Status: current
Description: Commit all the parameters that have been entered within the Rg Ip
MIB.
rgIpRipEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.2.1
Parent: rgIpRipSettings
Next sibling: rgIpRipMd5AuthEnable
Status: current
Description: Setting this object to true(1) causes the device to enable RIP
rgIpRipMd5AuthEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.2.2
Prev sibling: rgIpRipEnable
Next sibling: rgIpRipMd5KeyId
Status: current
Description: Setting this object to true(1) causes the device to enable md5 auth
rgIpRipMd5KeyId
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.2.3
Prev sibling: rgIpRipMd5AuthEnable
Next sibling: rgIpRipMd5KeyValue
Status: current
Description: Key ID value for Md5 auth
rgIpRipMd5KeyValue
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.2.4
Prev sibling: rgIpRipMd5KeyId
Next sibling: rgIpRipInterval
Status: current
Size list: 1: 0
2: 20
Description: MD5 Key Value
rgIpRipInterval
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.2.5
Ubee Interactive
Prev sibling: rgIpRipMd5KeyValue
Next sibling: rgIpRipDestIpAddressType
Status: current
Size list: 1: 10..600
Description: Interval in Seconds for the Rip Reporting interval.
rgIpRipDestIpAddressType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.2.6
Prev sibling: rgIpRipInterval
Next sibling: rgIpRipDestIpAddress
Status: current
Description: The type of IP address assigned to the rgIpRipDestIpAddress.
rgIpRipDestIpAddress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.2.7
Prev sibling: rgIpRipDestIpAddressType
Status: current
Description: Defines the Rip unicast destination IP Address for Rip Reports. If
this value returns 0.0.0.0 then this is the default multicast IP
address in the RFC (224.0.0.9)
rgIpLanAddrIpType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.3.1.1.1
Parent: rgIpLanAddrBaseEntry
Next sibling: rgIpLanAddrIp
Status: current
Description: The type of IP address assigned to the LAN IP Device in the LAN-
Trans Realm.
rgIpLanAddrIp
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.3.1.1.2
Prev sibling: rgIpLanAddrIpType
Next sibling: rgIpLanAddrClientID
Status: current
Description: The address assigned to the LAN IP Device.
Ubee Interactive
rgIpLanAddrClientID
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.3.1.1.3
Prev sibling: rgIpLanAddrIp
Next sibling: rgIpLanAddrLeaseCreateTime
Status: current
Size list: 1: 1..80
Description: The client's (i.e., LAN IP Device's) hardware address as indicated
in the chaddr field of its DHCP REQUEST message. There is a one-
to-one relationship between the hardware address and the LAN IP
Device.
rgIpLanAddrLeaseCreateTime
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.3.1.1.4
Prev sibling: rgIpLanAddrClientID
Next sibling: rgIpLanAddrLeaseExpireTime
Status: current
Description: This is the date and time when the LAN IP lease was created.
rgIpLanAddrLeaseExpireTime
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.3.1.1.5
Prev sibling: rgIpLanAddrLeaseCreateTime
Next sibling: rgIpLanAddrHostName
Status: current
Description: This is the date and time when the LAN IP address lease will
expire.
rgIpLanAddrHostName
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.3.1.1.6
Prev sibling: rgIpLanAddrLeaseExpireTime
Status: current
Size list: 1: 0..80
Description: This is the Host Name of the LAN IP address, based on DCHP option
12.
rgIpDnsServerOrder
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.4.1.1.1
Ubee Interactive
Parent: rgIpDnsServerEntry
Next sibling: rgIpDnsServerIpType
Status: current
Size list: 1: 1..65535
Description: Integer index into the rg IP DNS table
rgIpDnsServerIpType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.4.1.1.2
Prev sibling: rgIpDnsServerOrder
Next sibling: rgIpDnsServerIp
Status: current
Description: The type of InetAddress for rgIpDnsServerIp.
rgIpDnsServerIp
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.4.1.1.3
Prev sibling: rgIpDnsServerIpType
Next sibling: rgIpDnsServerRowStatus
Status: current
Description: The DNS IP address.
rgIpDnsServerRowStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.4.1.1.4
Prev sibling: rgIpDnsServerIp
Status: current
Description: The RowStatus interlock for the creation and deletion of a
rgIpDnsServerTable entry. Any writable object in each row of the
rgIpDnsServerTable can be modified at any time while the row is
active(1).
rgIpDhcpServerLanPoolStartType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.5.1.1.1
Parent: rgIpDhcpServerEntry
Next sibling: rgIpDhcpServerLanPoolStart
Status: current
Description: Ip Address Type of the Start of the Network Pool.
Ubee Interactive
rgIpDhcpServerLanPoolStart
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.5.1.1.2
Prev sibling: rgIpDhcpServerLanPoolStartType
Next sibling: rgIpDhcpServerLanPoolEndType
Status: current
Description: Ip Address of the Start of the Network Pool.
rgIpDhcpServerLanPoolEndType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.5.1.1.3
Prev sibling: rgIpDhcpServerLanPoolStart
Next sibling: rgIpDhcpServerLanPoolEnd
Status: current
Description: Ip Address Type of the End of the Network Pool.
rgIpDhcpServerLanPoolEnd
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.5.1.1.4
Prev sibling: rgIpDhcpServerLanPoolEndType
Next sibling: rgIpDhcpServerLeaseTime
Status: current
Description: Ip Address of the End of the Network Pool.
rgIpDhcpServerLanPoolEnd
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.5.1.1.4
Prev sibling: rgIpDhcpServerLanPoolEndType
Next sibling: rgIpDhcpServerLeaseTime
Status: current
Description: Ip Address of the End of the Network Pool.
rgIpDhcpServerLeaseTime
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.5.1.1.5
Prev sibling: rgIpDhcpServerLanPoolEnd
Next sibling: rgIpDhcpServerRowStatus
Ubee Interactive

Status: current
Size list: 1: 1..4294967295
Units: seconds
Description: Lease Time for the Network Pool
rgIpDhcpServerRowStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.5.1.1.6
Prev sibling: rgIpDhcpServerLeaseTime
Status: current
Description: The RowStatus interlock for the creation and deletion can be
modified at any time while the row is active(1).
rgIpRouteMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.6.1.1.1
Parent: rgIpRouteEntry
Next sibling: rgIpRouteNetworkNumberType
Status: current
Value list: 1: napt(1)
2: bridged(2)
3: routeddhcp(3)
4: routedstatic(4)
Default values: 1: napt (name)
Description: The specifies the Type of network that is being defined.
rgIpRouteNetworkNumberType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.6.1.1.2
Prev sibling: rgIpRouteMode
Next sibling: rgIpRouteNetworkNumber
Status: current
Description: Ip Address Type of the Network Number for a specific Network.
rgIpRouteNetworkNumber
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.6.1.1.3
Prev sibling: rgIpRouteNetworkNumberType
Next sibling: rgIpRouteSubnetMaskType
Status: current
Description: Ip Address of the Network Number for a specific Network.
Ubee Interactive
rgIpRouteSubnetMaskType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.6.1.1.4
Prev sibling: rgIpRouteNetworkNumber
Next sibling: rgIpRouteSubnetMask
Status: current
Description: Ip Address Type of the SubnetMask for a specific Network.
rgIpRouteSubnetMask
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.6.1.1.5
Prev sibling: rgIpRouteSubnetMaskType
Next sibling: rgIpRouteGatewayIpType
Status: current
Description: Ip Address of the SubnetMask for a specific Network.
rgIpRouteGatewayIpType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.6.1.1.6
Prev sibling: rgIpRouteSubnetMask
Next sibling: rgIpRouteGatewayIp
Status: current
Description: Ip Address Type of the Gateway for a specific Network.
rgIpRouteGatewayIp
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.6.1.1.7
Prev sibling: rgIpRouteGatewayIpType
Next sibling: rgIpRouteTypeOfService
Status: current
Description: Ip Address of the Gateway for a specific Network.
rgIpRouteTypeOfService
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.6.1.1.8
Prev sibling: rgIpRouteGatewayIp
Next sibling: rgIpRouteFirewallEnable
Ubee Interactive

Status: current
Description: Byte value to be used for the override TOS field for all IP packets
on this BSS. A value of 0 means don’t override, where any other
value will be used to override.
rgIpRouteFirewallEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.6.1.1.9
Prev sibling: rgIpRouteTypeOfService
Next sibling: rgIpRouteRowStatus
Status: current
Description: Enabled/Disable Firewall for specific Network
rgIpRouteRowStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.6.1.1.10
Prev sibling: rgIpRouteFirewallEnable
Next sibling: rgIpRouteUpnpIgdEnable
Status: current
Description: The RowStatus interlock for the creation and deletion can be
modified at any time while the row is active(1).
rgIpRouteUpnpIgdEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.6.1.1.11
Prev sibling: rgIpRouteRowStatus
Status: current
Description: Enabled/Disable UPnP (IGD) for specific Network
rgIpNatAlgsEnabled
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.7.1
Parent: rgIpNat
Base syntax: BITS
Status: current
Value list: 1: rsvp(0)
2: ftp(1)
3: tftp(2)
4: kerb88(3)
Ubee Interactive
5: netBiosDgm(4)
6: ike(5)
7: rtsp(6)
8: kerb1293(7)
9: h225(8)
10: pptp(9)
11: msn(10)
12: sip(11)
13: icq(12)
14: irc666x(13)
15: icqTalk(14)
16: net2Phone(15)
17: irc7000(16)
18: irc8000(17)
Description: Specifies which NAT application layer gateway supplements are
enabled on this device. The default value for this object is for
all ALG's to be enabled.
rgIpPrimaryLANIfBridgeMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.2.8
Parent: rgIpMib
Prev sibling: rgIpNat
Status: current
Description: Sets the Primary LAN Interfaces into bridged mode (true), or out
of bridged mode (false). This includes BOTH Wifi cards if
applicable. This object does not need the
rgIpNetworkSettingsCommit and will cause the device to reset if
changing from FALSE to TRUE, or TRUE to FALSE.
12.1.15 UBEE-RG-MGMT-MIB
rgOperMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.1
Module: UBEE-RG-MGMT-MIB
Parent: rgMgmtBase
Next sibling: rgRipEnabled
Status: deprecated
2: residentialGateway(2)
3: cableHome10(3)
4: cableHome11(4)
Description: Sets the operational mode of the device with regard to residential
gateway behaviour.
rgRipEnabled
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.2
Parent: rgMgmtBase
Prev sibling: rgOperMode
Next sibling: rgVpnEnabled
Ubee Interactive

Status: current
Description: Enables or disable router information protocol support in the
device.
rgVpnEnabled
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.3
Parent: rgMgmtBase
Prev sibling: rgRipEnabled
Next sibling: rgeRouterIpProvMode
Status: current
Description: Enables or disable virtual private network support in the device.
rgeRouterIpProvMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.4
Parent: rgMgmtBase
Prev sibling: rgVpnEnabled
Next sibling: rgVlanStrip
Status: current
2: ipv4(2)
3: ipv6(3)
4: dual(4)
5: ipv4RG(5)
Description: Toggles ip provisioning modes for eRouter.
rgVlanStrip
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.5
Parent: rgMgmtBase
Prev sibling: rgeRouterIpProvMode
Next sibling: rgVlanTable
Status: current
Description: This strips VLAN tags from packets.
rgVlanID
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.1
Parent: rgVlanEntry
Next sibling: rgVlanDesc
Status: current
Size list: 1: 2..4096
Description: The ID of the VLAN Entry.
Ubee Interactive
rgVlanDesc
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.2
Parent: rgVlanEntry
Prev sibling: rgVlanID
Next sibling: rgVlanEthernet
Status: current
Size list: 1: 0..20
Description: Description of this VLAN.
rgVlanEthernet
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.3
Parent: rgVlanEntry
Prev sibling: rgVlanDesc
Next sibling: rgVlanWiFi
Status: current
Size list: 1: 0..15
Description: Assigns the Ethernet Port corresponding to the bit set to the VLAN.
Bit 0 - Ethernet Port 0.
rgVlanWiFi
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.4
Parent: rgVlanEntry
Prev sibling: rgVlanEthernet
Next sibling: rgVlanMoca
Status: current
Size list: 1: 0..15
Description: Assigns the WiFi BSSID corresponding to the bit set to the VLAN.
Bit 0 - WiFi BSSID Port 0.
Bit 15 - WiFi BSSID 15.
rgVlanMoca
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.5
Parent: rgVlanEntry
Prev sibling: rgVlanWiFi
Next sibling: rgVlanUSB
Status: current
Ubee Interactive
Size list: 1: 0..1

Description: Include Moca on the VLAN.
rgVlanUSB
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.6
Parent: rgVlanEntry
Prev sibling: rgVlanMoca
Next sibling: rgVlanStartAddrType
Status: current
Size list: 1: 0..1
Description: Include USB on the VLAN.
rgVlanStartAddrType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.7
Parent: rgVlanEntry
Prev sibling: rgVlanUSB
Next sibling: rgVlanStartAddr
Status: current
Description: The start IP address range type.
rgVlanEndAddrType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.9
Parent: rgVlanEntry
Prev sibling: rgVlanStartAddr
Next sibling: rgVlanEndAddr
Status: current
Description: The end IP address range type.
rgVlanEndAddr
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.10
Parent: rgVlanEntry
Prev sibling: rgVlanEndAddrType
Next sibling: rgVlanSubnetMaskType
Status: current
Description: The end IP Address range.
rgVlanSubnetMaskType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.11
Ubee Interactive
Parent: rgVlanEntry
Prev sibling: rgVlanEndAddr
Next sibling: rgVlanSubnetMask
Status: current
Description: The subnet mask type.
rgVlanSubnetMask
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.12
Parent: rgVlanEntry
Prev sibling: rgVlanSubnetMaskType
Next sibling: rgVlanRouterIpType
Status: current
Description: The subnet mask.
rgVlanRouterIpType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.13
Parent: rgVlanEntry
Prev sibling: rgVlanSubnetMask
Next sibling: rgVlanRouterIp
Status: current
Description: The router IP type.
rgVlanRouterIp
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.14
Parent: rgVlanEntry
Prev sibling: rgVlanRouterIpType
Next sibling: rgVlanLeaseTime
Status: current
Description: The router IP.
rgVlanLeaseTime
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.15
Parent: rgVlanEntry
Prev sibling: rgVlanRouterIp
Next sibling: rgVlanRouteMode
Status: current
Ubee Interactive
Description: The lease time for clients of this VLAN.
rgVlanRouteMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.16
Parent: rgVlanEntry
Prev sibling: rgVlanLeaseTime
Next sibling: rgVlanTOS
Status: current
Value list: 1: napt(1)
2: bridged(2)
3: routeddhcp(3)
Default values: 1: napt (name)
Description: The route mode for this VLAN.
rgVlanTOS
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.17
Parent: rgVlanEntry
Prev sibling: rgVlanRouteMode
Next sibling: rgVlanFirewall
Status: current
Description: The TOS for this VLAN.
rgVlanFirewall
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.18
Parent: rgVlanEntry
Prev sibling: rgVlanTOS
Next sibling: rgVlanUpnp
Status: current
Description: Include the firewall on this VLAN.
rgVlanUpnp
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.19
Parent: rgVlanEntry
Prev sibling: rgVlanFirewall
Next sibling: rgVlanRowStatus
Status: current
Description: Include the IGD UPnP on this VLAN.
Ubee Interactive
rgVlanRowStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.6.1.20
Parent: rgVlanEntry
Prev sibling: rgVlanUpnp
Status: current
Description: The RowStatus interlock for the creation and deletion of a VLAN
entry.
rgVlanApplySettings
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.7
Parent: rgMgmtBase
Prev sibling: rgVlanTable
Next sibling: rgDsliteBase
Status: current
Reference: CableHome 1.1 Specification,Packet Handling & Address Translation
section.
Description: If set to true(1), the current configuration set in this MIB will
be flushed to non-volatile storage, and the VLAN Manager will re-
initialize the networks using this configuration. Unless this
object is explicitly set to true(1), any settings made via other
objects in this MIB will be lost if a reboot occurs. Always returns
false(2) when read.
rgDsliteEnabled
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.8.1
Parent: rgDsliteBase
Next sibling: rgDsliteAftrAddress
Status: current
Description: Enables or disable DS-lite support in the device.
rgDsliteAftrAddress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.8.2
Prev sibling: rgDsliteEnabled
Next sibling: rgDslitePcpMode
Composed syntax: InetAddressIPv6
Status: current
Description: IPv6 address of the AFTR endpoint of the DS-lite tunnel.
rgDslitePcpMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.8.3
Ubee Interactive
Prev sibling: rgDsliteAftrAddress

Next sibling: rgDsliteTcpMssClamping
Status: current
Value list: 1: plain(1)
2: encapsulation(2)
Default values: 1: plain (name)
Description: PCP (Port Control Protocol) operational mode
rgDsliteTcpMssClamping
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.8.4
Prev sibling: rgDslitePcpMode
Next sibling: rgDsliteIPv4FragEnabled
Status: current
Size list: 1: 0..1420
Description: Specifies whether TCP MSS clamping is enabled on the interface. 0
disables clamping, 1 clamps the MSS depending on the interface MTU.
A value > 1 will be used as clamping size.
rgDsliteIPv4FragEnabled
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.8.5
Prev sibling: rgDsliteTcpMssClamping
Status: current
Description: Enables or disable IPv4 fragmentation in DS-Lite
rgLowLatencyEnabled
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.9.1
Parent: rgLowLatencyBase
Next sibling: rgLowLatencyMaxDevices
Status: current
Description: Enables or disable Low Latency service flow in the device.
rgLowLatencyMaxDevices
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.9.2
Prev sibling: rgLowLatencyEnabled
Next sibling: rgLowLatencyDscp
Status: current
Ubee Interactive
Size list: 1: 1..3

Description: The maximum number of devices that can be configured as low latency
devices.
rgLowLatencyDscp
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.9.3
Prev sibling: rgLowLatencyMaxDevices
Next sibling: rgLowLatencyAllDevicesEnabled
Status: current
Size list: 1: 0..63
Description: The IP header Diffserv Code-Point used for the Low Latency service
flow.
rgLowLatencyAllDevicesEnabled
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.9.4
Prev sibling: rgLowLatencyDscp
Next sibling: rgLowLatencyDeviceTable
Status: current
Description: Enable Low Latency for all connected consumer devices. If
disabled, Low Latency must be enabled or disabled per connected
consumer device.
rgLldMacAddress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.9.5.1.1
Parent: rgLowLatencyDeviceEntry
Next sibling: rgLldHostName
Composed syntax: MacAddress
Status: current
Description: Low Latency Device MAC address.
rgLldHostName
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.9.5.1.2
Prev sibling: rgLldMacAddress
Next sibling: rgLldIpAddressType
Status: current
Size list: 1: 0..80
Description: Low Latency Device host name.
rgLldIpAddressType
Type: OBJECT-TYPE
Ubee Interactive
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.9.5.1.3
Prev sibling: rgLldHostName
Next sibling: rgLldIpAddress
Status: current
Description: Low Latency Device IP address type.
rgLldIpAddress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.9.5.1.4
Prev sibling: rgLldIpAddressType
Next sibling: rgLldLowLatencyEnabled
Status: current
Description: Low Latency Device IP address.
rgLldLowLatencyEnabled
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.9.5.1.5
Prev sibling: rgLldIpAddress
Next sibling: rgLldTrafficFlow
Status: current
Description: Low Latency enabled for this device.
rgLldTrafficFlow
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.9.5.1.6
Prev sibling: rgLldLowLatencyEnabled
Status: current
Description: Low Latency traffic flow indicator for the device.
rgResetToFactory
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.10
Parent: rgMgmtBase
Prev sibling: rgLowLatencyBase
Next sibling: rgFirewall
Status: current
Ubee Interactive
Description: If set to true(1), the board will default the DYNAMIC rgNonvol and
eRouterNonvol settings back to their default settings. Reading
this value will always return true. The sections that are set back
to default are rgNonVol, PsNonVOl, eRouterNonVol,
FirewallFilterNonVol, Ipv6FirewallNonVol, CdpNonVol, CspNonVol,
DhcpV6NonVol.
rgIPv4Firewall
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.11.1
Parent: rgFirewall
Next sibling: rgBlockFragIpPackets
Status: current
2: low(1)
3: medium(2)
4: high(3)
Description: Toggles IPv4 Firewall Protection to either disabled, low, medium,
or high.
rgBlockFragIpPackets
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.11.2
Parent: rgFirewall
Prev sibling: rgIPv4Firewall
Next sibling: rgPortScanDetection
Status: current
Description: Enables or disables blocking of Fragmented IP Packets.
rgPortScanDetection
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.11.3
Parent: rgFirewall
Prev sibling: rgBlockFragIpPackets
Next sibling: rgIPFloodDetection
Status: current
Description: Enables or disables Port Scan Detection.
rgIPFloodDetection
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.11.4
Parent: rgFirewall
Prev sibling: rgPortScanDetection
Status: current
Description: Enables or disables IP Flood Detection.
Ubee Interactive
rgWanBlocking
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.12.1
Parent: rgAdvanced
Next sibling: rgIpsecPassthrough
Status: current
Description: Enables or disables WAN Blocking.
rgIpsecPassthrough
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.12.2
Parent: rgAdvanced
Prev sibling: rgWanBlocking
Next sibling: rgPPTPPassthrough
Status: current
Description: Enables or disables Ipsec Passthrough.
rgPPTPPassthrough
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.12.3
Parent: rgAdvanced
Prev sibling: rgIpsecPassthrough
Next sibling: rgRemoteConfigManagement
Status: current
Description: Enables or disables PPTP Passthrough.
rgRemoteConfigManagement
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.12.4
Parent: rgAdvanced
Prev sibling: rgPPTPPassthrough
Next sibling: rgMulticastEnable
Status: current
Description: Enables or disables Remote Configuration Management.
rgMulticastEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.12.5
Parent: rgAdvanced
Prev sibling: rgRemoteConfigManagement
Next sibling: rgUPnPEnable
Status: current
Ubee Interactive
Description: Enables or disables Multicast.
rgUPnPEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.12.6
Parent: rgAdvanced
Prev sibling: rgMulticastEnable
Next sibling: rgPrimaryNetworkBridged
Status: current
Description: Enables or disables UPnP.
rgPrimaryNetworkBridged
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.12.7
Parent: rgAdvanced
Prev sibling: rgUPnPEnable
Next sibling: rgNATALG
Status: current
Description: Enables or disables Primary Network Bridging.
rgNATALG
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.7.1.12.8
Parent: rgAdvanced
Prev sibling: rgPrimaryNetworkBridged
Status: current
Description: Enables/Disables NAT ALGs by setting the following bits:
0x00000001 - RSVP
0x00000002 - FTP
0x00000004 - TFTP
0x00000008 - Kerb88
0x00000010 - NetBios
0x00000020 - IKE
0x00000040 - RTSP
0x00000080 - Kerb1293
0x00000100 - H225
0x00000200 - PPTP
0x00000400 - MSN
0x00000800 - SIP
0x00001000 - ICQ
0x00002000 - IRC666x
0x00004000 - ICQTalk
0x00008000 - Net2Phone
0x00010000 - IRC7000
0x00020000 - IRC8000
12.1.16 UBEE-SNMP-MGMT-MIB
snmpUdpPort
Type: OBJECT-TYPE
Ubee Interactive
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.2.1
Module: UBEE-SNMP-MGMT-MIB
Parent: snmpMgmt
Next sibling: snmpNotifyUdpPort
Status: current
Size list: 1: 1..65535
Description: Controls and reflects the UDP port which will be listened for as
the destination port on received SNMP packets and used as the
source port on subsequent SNMP replies. Setting this object will
result in an immediate change of the SNMP port number, although
the SNMP reply to the set request which modifies this value will
still be sent using the port on which it was received. This
prevents the sending SNMP manager from receiving a timeout on the
set request. This value is NOT stored to non-volatile storage and
will revert to the default value on system reboot.
snmpNotifyUdpPort
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.2.2
Parent: snmpMgmt
Prev sibling: snmpUdpPort
Next sibling: snmpDscpTag
Status: current
Size list: 1: 1..65535
Description: Controls and reflects the UDP port which will be used as the
destination port in SNMP notify packets, including traps and
informs. This value is NOT stored to non-volatile storage and will
revert to the default value on system reboot.
snmpDscpTag
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.2.3
Parent: snmpMgmt
Prev sibling: snmpNotifyUdpPort
Status: current
Size list: 1: 0..63
Description: This object controls the value for the DSCP field (previously known
as ToS) in the IP header which will be used for all SNMP packets
originating from this device. This value is NOT stored to non-
volatile storage and will revert to the default value on system
reboot.
12.1.17 UBEE-SSH-MGMT-MIB
sshIpStackInterfaces
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.1
Module: UBEE-SSH-MGMT-MIB
Parent: sshMgmt
Ubee Interactive
Next sibling: sshUserName

Base syntax: BITS
Status: current
2: interface2(1)
3: interface3(2)
4: interface4(3)
5: interface5(4)
6: interface6(5)
7: interface7(6)
8: interface8(7)
Description: Controls and reflects the IP stack interfaces on which a ssh server
is active.
sshUserName
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.2
Parent: sshMgmt
Prev sibling: sshIpStackInterfaces
Next sibling: sshPassword
Status: current
Size list: 1: 0..15
Description: Controls and reflects the user name which will be allowed ssh
access.
sshPassword
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.3
Parent: sshMgmt
Prev sibling: sshUserName
Next sibling: sshServerControl
Status: current
Size list: 1: 0..15
Description: Controls and reflects the password which will be allowed ssh
access.
sshServerControl
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.4
Parent: sshMgmt
Prev sibling: sshPassword
Next sibling: sshSessionIp
Status: current
Value list: 1: stop(0)
2: start(1)
Description: Used to start or stop the ssh server. When read, indicates the
current state of the server.
Ubee Interactive
sshSessionIp
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.5
Parent: sshMgmt
Prev sibling: sshServerControl
Next sibling: sshSessionInProgress
Numerical syntax: IP Address
Base syntax: IpAddress
Composed syntax: IpAddress
Status: deprecated
Description: This object gives the IP address of the most recently connected
device. If no session has taken place since the last reboot, this
object will read 0.0.0.0.
sshSessionInProgress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.6
Parent: sshMgmt
Prev sibling: sshSessionIp
Next sibling: sshForceUserLogout
Status: current
Description: Indicates whether or not a ssh session is currently in progress.
sshForceUserLogout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.7
Parent: sshMgmt
Prev sibling: sshSessionInProgress
Next sibling: sshSessionAddressType
Status: current
Description: If a ssh session is currently in progress, setting this object to
true(1) will terminate the session. Setting to false(2) has no
effect. Always returns false(2) when read.
sshSessionAddressType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.8
Parent: sshMgmt
Prev sibling: sshForceUserLogout
Next sibling: sshSessionAddress
Status: current
Description: The type of Internet address used for sshSessionAddress.
sshSessionAddress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.9
Parent: sshMgmt
Prev sibling: sshSessionAddressType
Next sibling: sshHackerTable
Ubee Interactive

Status: current
Description: This object gives the address of the most recently connected
object will report an empty string.
sshHackerAddressType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.10.1.1
Parent: sshHackerEntry
Next sibling: sshHackerAddress
Status: current
Max access: accessible-for-notify
Description: The type of Internet address used for sshHackerAddress.
sshHackerAddress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.10.1.2
Prev sibling: sshHackerAddressType
Next sibling: sshHackerNumAttempts
Status: current
Description: The address of an device which has unsuccessfully attempted to log
in to this station enough times to be blacklisted as a hacker.
sshHackerNumAttempts
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.10.1.3
Prev sibling: sshHackerAddress
Next sibling: sshHackerLastTime
Status: current
Description: The number of times that the device represented by this entry has
attempted to log in to this station.
sshHackerLastTime
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.10.1.4
Prev sibling: sshHackerNumAttempts
Numerical syntax: Timeticks
Base syntax: TimeTicks
Composed syntax: TimeTicks
Status: current
Description: The value of sysUpTime when this row was created, or when the value
of sshHackerNumAttempts was last incremented.
Ubee Interactive
sshSessionInactivityTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.11
Parent: sshMgmt
Prev sibling: sshHackerTable
Next sibling: sshHackerInactivityTimeout
Status: current
Size list: 1: 0..86400
Units: seconds
Description: This object controls the length of time after which an ssh session
will be terminated if there is no activity. Note that if this
object is set to zero, the session will never be terminated due to
inactivity.
sshHackerInactivityTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.12
Parent: sshMgmt
Prev sibling: sshSessionInactivityTimeout
Next sibling: sshWanAccessTimeout
Status: current
Size list: 1: -1..86400
Units: seconds
Description: This object controls the length of time after which an entry in
the sshHackerTable will be removed if there are no further attempts
to access the system from the corresponding sshHackerAddress. Note
that if this object is set to zero, the sshHackerTable will be
effectively disabled and no IP addresses will be blacklisted for
unauthorized access. If set to -1, entries in the sshHackerTable
will never be aged out and once blacklisted, only a system reboot
will allow another attempted login from the blacklisted address.
sshWanAccessTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.4.13
Parent: sshMgmt
Prev sibling: sshHackerInactivityTimeout
Next sibling: sshTraps
Status: current
Size list: 1: 0..86400
Units: seconds
Description: This object controls the length of time after which SSH access via
the WAN interface will be terminated if no SSH session is initiated
via the WAN interface within this period. If set to a value of 0,
there will be no such timeout in effect. The timer begins running
when the SSH server starts. After the number of seconds specified
by this object has elapsed, if no SSH session has been initiated
via the WAN interface, a filter will be created which drops all
SSH traffic destined to any of the device's IP addresses which
arrives via the WAN interface. If a SSH session is initiated via
Ubee Interactive
the WAN interface during the period of time alloted by this object,
the timer will be reset. Setting this object to any value will
cause the timer to be reset.
12.1.18 UBEE-SW-DLOAD-MIB
swModuleIndex
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.15.1.1.1
Module: UBEE-SW-DLOAD-MIB
Parent: swModuleDownloadEntry
Next sibling: swModuleDescr
Status: current
Size list: 1: 0..32
Description: This object uniquely identifies the software module that pertains
to this row in the swDownloadTable. The value of this object is
context sensitive, that is, this value has meaning, but that
meaning is known by the managed system and is outside the scope of
this document.
swModuleDescr
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.15.1.1.2
Prev sibling: swModuleIndex
Next sibling: swModuleFilename
Status: current
Size list: 1: 0..64
Description: A short description of this software module, e.g. linux or dhtml.
swModuleFilename
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.15.1.1.3
Prev sibling: swModuleDescr
Next sibling: swModuleAdminStatus
Status: current
Description: The filename of the software image to be downloaded via TFTP.
Unless set via SNMP, this is the filename specified by the
provisioning server during the boot process that corresponds to
the software version that is desired for this module. If unknown,
the value of this object is the zero-length string.
swModuleAdminStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.15.1.1.4
Prev sibling: swModuleFilename
Next sibling: swModuleOperStatus
Ubee Interactive

Status: current
Value list: 1: upgradeFromMgt(1)
2: allowProvisioningUpgrade(2)
3: ignoreProvisioningUpgrade(3)
Default values: 1: allowProvisioningUpgrade (name)
Description: If set to upgradeFromMgt(1), the device will initiate a TFTP
software image download. After successfully receiving an image,
the device will set its state to ignoreProvisioningUpgrade(3). If
the download process is interrupted (e.g., by a reset or power
failure), the device will load the previous image and, after re-
initialization, continue to attempt loading the image specified in
swModuleFilename.
If set to allowProvisioningUpgrade(2), the device will use the
software version information supplied by the provisioning server
when next rebooting (this does not cause a reboot).
When set to ignoreProvisioningUpgrade(3), the device will
disregard software image upgrade information from the provisioning
server.
Note that reading this object can return upgradeFromMgt(1). This
indicates that a software download is currently in progress, and
that the device will reboot after successfully receiving an image.
swModuleOperStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.15.1.1.5
Prev sibling: swModuleAdminStatus
Next sibling: swModuleCurrentVers
Status: current
Value list: 1: inProgress(1)
2: completeFromProvisioning(2)
3: completeFromMgt(3)
4: failed(4)
5: other(5)
Description: InProgress(1) indicates that a TFTP download is underway, either
as a result of a version mismatch at provisioning or as a result
of a upgradeFromMgt request. No other objects in the current row
can be modified while this object is in this state.
CompleteFromProvisioning(2) indicates that the last software
upgrade was a result of version mismatch at provisioning.
CompleteFromMgt(3) indicates that the last software upgrade was a
result of setting swModuleAdminStatus to upgradeFromMgt.
Failed(4) indicates that the last attempted download failed,
ordinarily due to TFTP timeout.
swModuleCurrentVers
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.15.1.1.6
Prev sibling: swModuleOperStatus
Next sibling: swModuleServerAddressType
Status: current
Ubee Interactive

Description: The current version of this software module. This string's syntax
is that used by the individual vendor to identify software
versions. If this is not applicable, the value MUST be a zero-
length string.
swModuleServerAddressType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.15.1.1.7
Prev sibling: swModuleCurrentVers
Next sibling: swModuleServerAddress
Status: current
Description: The type of address of the TFTP server used for software upgrades.
swModuleServerAddress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.15.1.1.8
Prev sibling: swModuleServerAddressType
Next sibling: swModuleDownloadRetries
Status: current
Description: The address of the TFTP or HTTP server used for software upgrades.
If the TFTP server is unknown, return the zero-length address
string (see the TextualConvention).
swModuleDownloadRetries
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.15.1.1.9
Prev sibling: swModuleServerAddress
Status: current
Description: The number of times to attempt a download of this module. If the
value of this object is 0, then the managed system will attempt a
download forever.
12.1.19 UBEE-TELNET-MGMT-MIB
telnetIpStackInterfaces
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.1
Module: UBEE-TELNET-MGMT-MIB
Parent: telnetMgmt
Next sibling: telnetUserName
Base syntax: BITS
Status: current
Ubee Interactive

2: interface2(1)
3: interface3(2)
4: interface4(3)
5: interface5(4)
6: interface6(5)
7: interface7(6)
8: interface8(7)
Description: Controls and reflects the IP stack interfaces on which a telnet
server is active.
telnetUserName
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.2
Parent: telnetMgmt
Prev sibling: telnetIpStackInterfaces
Next sibling: telnetPassword
Status: current
Size list: 1: 0..15
Description: Controls and reflects the user name which will be allowed telnet
access.
telnetPassword
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.3
Parent: telnetMgmt
Prev sibling: telnetUserName
Next sibling: telnetServerControl
Status: current
Size list: 1: 0..15
Description: Controls and reflects the password which will be allowed telnet
access.
telnetServerControl
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.4
Parent: telnetMgmt
Prev sibling: telnetPassword
Next sibling: telnetSessionIp
Status: current
Value list: 1: stop(0)
2: start(1)
Description: Used to start or stop the telnet server. When read, indicates the
current state of the server.
telnetSessionIp
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.5
Parent: telnetMgmt
Ubee Interactive
Prev sibling: telnetServerControl

Next sibling: telnetSessionInProgress
Numerical syntax: IP Address
Base syntax: IpAddress
Composed syntax: IpAddress
Status: deprecated
Description: This object gives the IP address of the most recently connected
object will read 0.0.0.0.
telnetSessionInProgress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.6
Parent: telnetMgmt
Prev sibling: telnetSessionIp
Next sibling: telnetForceUserLogout
Status: current
Description: Indicates whether or not a telnet session is currently in progress.
telnetForceUserLogout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.7
Parent: telnetMgmt
Prev sibling: telnetSessionInProgress
Next sibling: telnetSessionAddressType
Status: current
Description: If a telnet session is currently in progress, setting this object
to true(1) will terminate the session. Setting to false(2) has no
effect. Always returns false(2) when read.
telnetSessionAddressType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.8
Parent: telnetMgmt
Prev sibling: telnetForceUserLogout
Next sibling: telnetSessionAddress
Status: current
Description: The type of Internet address used for telnetSessionAddress.
telnetSessionAddress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.9
Parent: telnetMgmt
Prev sibling: telnetSessionAddressType
Next sibling: telnetHackerTable
Status: current
Ubee Interactive
Description: This object gives the address of the most recently connected
object will report an empty string.
telnetHackerAddressType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.10.1.1
Parent: telnetHackerEntry
Next sibling: telnetHackerAddress
Status: current
Description: The type of Internet address used for telnetHackerAddress.
telnetHackerAddress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.10.1.2
telnetHackerAddress(2)
Prev sibling: telnetHackerAddressType
Next sibling: telnetHackerNumAttempts
Status: current
Description: The address of an device which has unsuccessfully attempted to log
in to this station enough times to be blacklisted as a hacker.
telnetHackerNumAttempts
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.10.1.3
Prev sibling: telnetHackerAddress
Next sibling: telnetHackerLastTime
Status: current
Description: The number of times that the device represented by this entry has
attempted to log in to this station.
telnetHackerLastTime
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.10.1.4
Prev sibling: telnetHackerNumAttempts
Numerical syntax: Timeticks
Base syntax: TimeTicks
Composed syntax: TimeTicks
Status: current
Description: The value of sysUpTime when this row was created, or when the value
of telnetHackerNumAttempts was last incremented.
telnetSessionInactivityTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.11
Parent: telnetMgmt
Ubee Interactive
Prev sibling: telnetHackerTable

Next sibling: telnetHackerInactivityTimeout
Status: current
Size list: 1: 0..86400
Units: seconds
Description: This object controls the length of time after which a telnet
session will be terminated if there is no activity. Note that if
this object is set to zero, the session will never be terminated
due to inactivity.
telnetHackerInactivityTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.12
Parent: telnetMgmt
Prev sibling: telnetSessionInactivityTimeout
Next sibling: telnetWanAccessTimeout
Status: current
Size list: 1: -1..86400
Units: seconds
Description: This object controls the length of time after which an entry in
the telnetHackerTable will be removed if there are no further
attempts to access the system from the corresponding
telnetHackerAddress. Note that if this object is set to zero, the
telnetHackerTable will be effectively disabled and no IP addresses
will be blacklisted for unauthorized access. If set to -1, entries
in the telnetHackerTable will never be aged out and once
blacklisted, only a system reboot will allow another attempted
login from the blacklisted address.
telnetWanAccessTimeout
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.1.1.13
Parent: telnetMgmt
Prev sibling: telnetHackerInactivityTimeout
Next sibling: telnetTraps
Status: current
Size list: 1: 0..86400
Units: seconds
Description: This object controls the length of time after which telnet access
via the WAN interface will be terminated if no telnet session is
initiated via the WAN interface within this period. If set to a
value of 0, there will be no such timeout in effect. The timer
begins running when the telnet server starts. After the number of
seconds specified by this object has elapsed, if no telnet session
has been initiated via the WAN interface, a filter will be created
which drops all telnet traffic destined to any of the device's IP
addresses which arrives via the WAN interface. If a telnet session
is initiated via the WAN interface during the period of time
alloted by this object, the timer will be reset. Setting this
object to any value will cause the timer to be reset.
Ubee Interactive
12.1.20 UBEE-WIFI-MGMT-MIB
wifiApplySettings
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.1
Module: UBEE-WIFI-MGMT-MIB
Parent: wifiBase
Next sibling: wifiPrimaryInterfaceTable
Status: current
Description: If set to true(1), the current configuration set in this MIB will
be written to non-volatile storage, and the wi-fi driver will be
restarted using this configuration. This object may be used to
invoke an immediate reconfiguration of the wi-fi system without
requiring a full reboot. Unless this object is explicitly set to
true(1), any settings made via other objects in this MIB may be
lost if a reboot occurs. Always returns false(2) when read.
wifiOperMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.2.1.1
Parent: wifiPrimaryInterfaceEntry
Next sibling: wifiCurrentChannel
Status: current
Value list: 1: notAvailable(0)
2: off(1)
3: remote(2)
4: local(3)
Description: Used to control the 802.11 operational mode for this interface. If
set to notAvailable(0), then the wireless interface will be
disabled, with the radio off, and no wireless settings web pages
will be available to the user.
If set to off(1) then the wireless interface will be disabled, but
there may be a web page present which indicates that wireless
service is available and that the MSO should be contacted to enable
it.
If set to remote(2), then the wireless interface will be enabled,
but the configuration web pages are read-only so that the user may
not change the settings.
If set to local(3), then the wireless interface will be enabled,
and the web pages will be read-write so that the user has full
control over the settings.
wifiCurrentChannel
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.2.1.2
Prev sibling: wifiOperMode
Next sibling: wifiBeaconInterval
Status: current
Ubee Interactive
Description: Controls and reflects the current channel number (802.11g) or

control channel (802.11n) for this interface.
If set to (0), the AP will be put in auto-channel mode where it
automatically scans for the least-crowded channel.
For 802.11g cards, available channels are 1-14.
For 802.11n cards, available channels are 34-216.
Channel selection is also subject to restrictions based on the
selected country code.
wifiBeaconInterval
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.2.1.3
Prev sibling: wifiCurrentChannel
Next sibling: wifiDTIMInterval
Status: current
Size list: 1: 0..65535
Units: milliseconds
Description: Controls and reflects the beacon interval for this interface.
wifiDTIMInterval
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.2.1.4
Prev sibling: wifiBeaconInterval
Next sibling: wifiFragThresh
Status: current
Units: milliseconds
Description: Controls and reflects the DTIM interval for this interface.
wifiFragThresh
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.2.1.5
Prev sibling: wifiDTIMInterval
Next sibling: wifiRTSThresh
Status: current
Size list: 1: 256..2346
Units: bytes
Description: Controls and reflects the fragmentation threshold for this
interface.
wifiRTSThresh
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.2.1.6
Prev sibling: wifiFragThresh
Next sibling: wifiShortRetryLimit
Ubee Interactive

Status: current
Size list: 1: 0..2347
Description: Controls and reflects the RTS threshold for this interface.
wifiShortRetryLimit
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.2.1.7
Prev sibling: wifiRTSThresh
Next sibling: wifiLongRetryLimit
Status: current
Description: Controls and reflects the short retry limit for this interface.
wifiLongRetryLimit
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.2.1.8
Prev sibling: wifiShortRetryLimit
Next sibling: wifiRate
Status: current
Description: Controls and reflects the long retry limit for this interface.
wifiRate
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.2.1.9
Prev sibling: wifiLongRetryLimit
Next sibling: wifiOutputPower
Status: current
Value list: 1: auto(0)
2: mbits1(1)
3: mbits2(2)
4: mbits5-5(5)
5: mbits6(6)
6: mbits9(9)
7: mbits11(11)
8: mbits12(12)
9: mbits18(18)
10: mbits24(24)
11: mbits36(36)
12: mbits48(48)
13: mbits54(54)
Default values: 1: auto (name)
Description: Forces the transmission rate for the AP to a particular speed.
wifiOutputPower
Type: OBJECT-TYPE
Ubee Interactive
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.2.1.10
Prev sibling: wifiRate
Next sibling: wifiMbssUserControl
Status: current
Value list: 1: percent25(25)
2: percent50(50)
3: percent75(75)
4: percent100(100)
Default values: 1: percent100 (name)
Description: Sets the output power relative to the hardware's maximum
capability.
wifiMbssUserControl
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.2.1.11
Prev sibling: wifiOutputPower
Next sibling: wifiRadioEnable
Status: current
Description: Sets the number of user controlled Wifi networks for this
interface.
0 <--- The user has no control over wireless. No 802.11 web pages
will be displayed. For now, we don't need to support this.
An attempt to set it to zero can just return an error.
1 <--- The user has control over the primary wireless network only.
No guest network page is displayed.
2 <--- The user has control over the primary wireless network and
one guest network. No drop down menu (or only 1 item in the menu)
for additional guest network configuration.
3 <--- Same as above with 2 guest networks
8 <--- Same as above with 7 guest networks (Depending on Wifi Card
either 3 or 7 guest networks are supported).
wifiRadioEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.2.1.12
Prev sibling: wifiMbssUserControl
Next sibling: wifiApsScan
Status: current
Description: Controls and reflects the state of Wifi Radio on the select Card.
If set to true(1), the AP will turn on the wifi Radio for that
card. Set to false(2) to disable the WIFI radio for card.
wifiApsScan
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.2.1.13
Ubee Interactive
Prev sibling: wifiRadioEnable

Next sibling: wifiObssCoexMode
Status: current
Description: If set to true(1), WiFi Radio will be configured to scan for the
APs. Scan results with list of neighboring APs will be updated in
wifiApsScanResultsTable. Always returns false(2) when read.
wifiObssCoexMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.2.1.14
Prev sibling: wifiApsScan
Status: current
Description: Controls and reflects the state of Wifi Radio's OBSS Coexistence
on the selected Card. If set to true(1), the AP will turn on the
OBSS Coexistence for that card. Set to false(2) to disable the OBSS
Coexistence for card.
wifi54gNetMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.3.1.1
Parent: wifi80211gInterfaceEntry
Next sibling: wifi54gProtectionEnable
Status: current
Value list: 1: mode54g11bOnly(0)
2: mode54gAuto(1)
3: mode54gOnly(2)
4: mode54gPerformance(4)
5: mode54gLRS(5)
Default values: 1: mode54gAuto (name)
Description: Controls and reflects the behavior of the interface with regards
to which flavor of 802.11g is used.
If set to mode54gLRS(5), the interface will interoperate with the
widest variety of 54g and 802.11b clients.
If set to mode54gPerformance(4), the highest throughout will be
provided and only 54g clients will be accepted, however nearby
802.11b networks may suffer degraded performance.
If set to mode54g11bOnly(0), only 802.11b clients will be
accepted.
If set to mode54gAuto(1) the interface will attempt to operate at
54g rates unless an 802.11b client is detected.
If set to mode54gOnly(2), only 802.11g clients will be accepted.
wifi54gProtectionEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.3.1.2
Prev sibling: wifi54gNetMode
Next sibling: wifi54gBasicRateSet
Ubee Interactive

Status: current
Description: Controls and reflects the state of 54g protection. If set to
true(1), the AP will use RTS/CTS to improve 802.11g performance in
mixed 802.11g/802.11b networks. Set to false(2) to maximize
802.11g throughput under most conditions.
wifi54gBasicRateSet
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.3.1.3
Prev sibling: wifi54gProtectionEnable
Status: current
Value list: 1: default(1)
2: all(2)
Default values: 1: default (name)
Description: Determines which rates are advertised as BASIC rates in the beacon.
If set to default, the driver defaults for the selected 54gMode
will be used. If set to all, all available rates will be advertised
as BASIC rates regardless of the 54gMode setting.
wifiNMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.4.1.1
Parent: wifi80211nInterfaceEntry
Next sibling: wifiNPhyRate
Status: current
2: off(2)
3: nOnly(3)
Description: Determines which Mode the N card will run in. Auto Mode will detect
which stations are out there and run in the proper mode, Off Mode
will make it such the card will not run in N mode but will operate
in the mode specified by wifi54gNetMode. The nOnly setting will
configure the card to operate only in N mode - 'b' and 'g' modes
will be inhibited. Note: This is for N cards only, and this may
also affect other MIB settings.
wifiNPhyRate
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.4.1.2
Prev sibling: wifiNMode
Next sibling: wifiNBand
Status: current
2: legacy(1)
3: mbits6or13(2)
4: mbits13or27(3)
5: mbits19-5or40-5(4)
Ubee Interactive
6: mbits26or54(5)
7: mbits39or81(6)
8: mbits52or108(7)
9: mbits58or121(8)
10: mbits65or135(9)
11: mbits13or27(10)
12: mbits26or54(11)
13: mbits39or81(12)
14: mbits52or108(13)
15: mbits78or162(14)
16: mbits104or216(15)
17: mbits117or243(16)
18: mbits130or270(17)
Default values: 1: auto (name)
Description: Forces the N Phy transmission rate for the AP to a particular
speed. Each pair of rates corresponds to a 20 MHz or 40 MHz channel
configuration.
wifiNBand
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.4.1.3
Prev sibling: wifiNPhyRate
Next sibling: wifiNBandWidth
Status: current
Value list: 1: band2400MHz(1)
2: band5000MHz(2)
Description: Determines which Band that we will be operating in. Either the 2.4G
or the 5G Hz. Note: This is for N cards only.
wifiNBandWidth
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.4.1.4
Prev sibling: wifiNBand
Next sibling: wifiNSideBand
Status: current
Value list: 1: none(0)
2: width20MHz(1)
3: width40MHz(2)
Description: Determines which Band Width that we will be operating in. Either
the 20MHz or the 40MHz. Note: This is for N cards only, and this
also affect other MIB selections such as wifiNSideBand.
wifiNSideBand
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.4.1.5
Prev sibling: wifiNBandWidth
Next sibling: wifiNProtection
Status: current
Value list: 1: none(0)
2: upper(1)
3: lower(2)
Ubee Interactive
Description: Determines which side Band the channel will operate in. This mib
is dependent of what wifiNBandWidth is selected and only applies
when 40MHz is selected. Returns none(0) when wifiNBandWidth=
40MHz.
wifiNProtection
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.4.1.6
Prev sibling: wifiNSideBand
Status: current
2: off(2)
Description: Determines if protection will be turned on or off for N mode. Note:
This is for N cards only.
wifiValid
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.5.1.1
Parent: wifiApsScanResultsEntry
Next sibling: wifiNetworkName
Status: current
Value list: 1: invalid(0)
2: valid(1)
Description: Determines if the current entry is valid or not.
wifiNetworkName
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.5.1.2
Prev sibling: wifiValid
Next sibling: wifiSecurityMode
Status: current
Description: Neighboring AP name or SSID.
wifiSecurityMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.5.1.3
Prev sibling: wifiNetworkName
Next sibling: wifiPhyMode
Status: current
Description: Neighboring AP security mode.
wifiPhyMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.5.1.4
Ubee Interactive
Prev sibling: wifiSecurityMode
Next sibling: wifiRssi
Status: current
Description: Neighboring AP PHY mode.
wifiRssi
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.5.1.5
Prev sibling: wifiPhyMode
Next sibling: wifiChannel
Status: current
Description: Neighboring AP receive signal strenth.
wifiChannel
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.5.1.6
Prev sibling: wifiRssi
Next sibling: wifiMacAddress
Status: current
Description: Neighboring AP operating channel.
wifiMacAddress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.5.1.7
Prev sibling: wifiChannel
Composed syntax: PhysAddress
Status: current
Description: Neighboring AP MAC address.
wifiACBandWidth
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.6.1.1
Parent: wifi80211acInterfaceEntry
Next sibling: wifiACChannelSpec
Status: current
Value list: 1: width20MHz(1)
2: width40MHz(2)
3: width80MHz(3)
Description: Determines which Band Width that we will be operating in. Either
the 20MHz, 40MHz or the 80MHz. Note: This is for N or AC cards only.
Ubee Interactive
wifiACChannelSpec
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.1.6.1.2
Parent: wifi80211acInterfaceEntry
Prev sibling: wifiACBandWidth
Status: current
Size list: 1: 1..20
Description: Controls and reflects the current channel specification for this
interface.
If set to (0), the AP will be put in auto-channel mode where it
automatically scans for the least-crowded channel.
For 20MHz bandwidth, channel specifications are control channel.
For example 1, 36 etc.
For 40MHz bandwidth, channel specifications are combination of
control channel and sideband ('u' is for upper sideband and 'l' is
for lower sideband). For example 5u, 1l, 40u, 36l etc.
For 80MHz bandwidth, channel specifications are 36/80, 52/80,
100/80 etc.
Channel specification selection is also subject to restrictions
based on the selected country code.
wifiBssId
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.1.1.1
Parent: wifiBssEntry
Next sibling: wifiBssEnable
Status: current
Description: The physical address associated with this service set.
wifiBssEnable
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.1.1.2
Prev sibling: wifiBssId
Next sibling: wifiBssSsid
Status: current
Description: Enables or disables this service set.
wifiBssSsid
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.1.1.3
Prev sibling: wifiBssEnable
Next sibling: wifiBssSecurityMode
Status: current
Ubee Interactive

Size list: 1: 0..32
Description: Controls and reflects the service set identifier for this BSS.
wifiBssSecurityMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.1.1.4
Prev sibling: wifiBssSsid
Next sibling: wifiBssClosedNetwork
Status: current
2: wep(1)
3: wpaPsk(2)
4: wpa2Psk(3)
5: wpaEnterprise(4)
6: wpa2Enterprise(5)
7: radiusWep(6)
8: wpaWpa2Psk(7)
9: wpaWpa2Enterprise(8)
Description: Security mode may be chosen from Disable, WEP, WPA-PSK, WPA2 PSK,
WPA-Enterprise, WPA2-Enterprise or RADIUS-WEP. All devices on the
network must use the same security mode in order to communicate.
If set to disabled(0): Open system. No authentication or
encryption.
If set to wep(1) then the following parameters must be set:
Default Transmit Key (wifiBssWepDefaultKey): Choose which Key to
use.
WEP Key Bit (wifiBssWepEncryptionMode): May select from 64-Bit or
128-Bit encryption.
Passphrase (wifiBssWepPassPhrase): Enter a passphrase consisting
of any keyboard character to be used to generate a hex WEP key.
Key 1-4 (wifiBssWep64BitKeyTable or wifiBssWep128BitKeyTable):
Enter a WEP key manually. Must use only hex character (0-9 and A-
F). 64-bit WEP requires 10 hex characters, 128-Bit WEP requires
the use of 26 hex characters.
If set to wpaPsk(2) then the following parameters must be set:
WPA Algorithm (wifiBssWpaAlgorithm): TKIP or AES.
WPA Pre-Shared Key (wifiBssWpaPreSharedKey): Choose a unique key
to authenticate with other devices on the network. The Pre-Shared
Key must be between 8 and 63 characters in length.
Group Key Renewal (wifiBssWpaGroupRekeyInterval): This settings
determines how often the group key changes.
If set to wpa2Psk(3) then the following parameters must be set:
WPA2 Algorithm (wifiBssWpaAlgorithm): AES or TKIP+AES.
WPA2 Pre-Shared Key (wifiBssWpaPreSharedKey): Choose a unique key
Group Key Renewal (wifiBssWpaGroupRekeyInterval): This settings
If set to wpaEnterprise(4) then the following parameters must
be set:
Ubee Interactive
WPA Algorithm (wifiBssWpaAlgorithm): TKIP or AES.

RADIUS Server Address (wifiBssRadiusAddress): The IP address of
the RADIUS server.
RADIUS Server Port (wifiBssRadiusPort): The port the RADIUS server
uses.
RADIUS Shared Secret (wifiBssRadiusKey): The shared secret set on
the RADIUS server.
Key Renewal Timeout (wifiBssRadiusReAuthInterval): Determines how
often the keys should be renewed.
If set to wpa2Enterprise(5) then the following parameters must be
set:
WPA2 Algorithm (wifiBssWpaAlgorithm): AES or TKIP+AES.
RADIUS Server Address (wifiBssRadiusAddress): The IP address of
the RADIUS server.
uses.
the RADIUS server.
Key Renewal Timeout (wifiBssRadiusReAuthInterval): Determines how
often the keys should be renewed.
If set to radiusWep(6) then the following parameters must be set:
RADIUS Server Address (wifiBssRadiusAddressType /
wifiBssRadiusAddress): The IP address of the RADIUS server.
uses.
the RADIUS server.
Default Transmit Key (wifiBssWepDefaultKey): Choose which Key to
use.
WEP Key Bit (wifiBssWepEncryptionMode): May select from 64-Bit or
128-Bit encryption.
Passphrase (wifiBssWepPassPhrase): Enter a passphrase consisting
of any keyboard character to be used to generate a hex WEP key.
Key 1-4 (wifiBssWep64BitKeyTable or wifiBssWep128BitKeyTable):
Enter a WEP key manually. Must use only hex character (0-9 and A-
F). 64-bit WEP requires 10 hex characters, 128-Bit WEP requires
the use of 26 hex characters.
If set to wpaWpa2Psk(7) then the following parameters must be set:
WPA Algorithm (dot11BssWpaAlgorithm): TKIP or AES.
WPA Pre-Shared Key (dot11BssWpaPreSharedKey): Choose a unique key
Group Key Renewal (dot11BssWpaGroupRekeyInterval): This settings
If set to wpaWpa2Enterprise(8) then the following parameters must
be set:
WPA Algorithm (dot11BssWpaAlgorithm): TKIP or AES.
Ubee Interactive
RADIUS Server Address (dot11BssRadiusAddress): The IP address of

the RADIUS server.
RADIUS Server Port (dot11BssRadiusPort): The port the RADIUS
server uses.
RADIUS Shared Secret (dot11BssRadiusKey): The shared secret set on
the RADIUS server.
Key Renewal Timeout (dot11BssRadiusReAuthInterval):
Determines how often the keys should be renewed.
wifiBssClosedNetwork
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.1.1.5
Prev sibling: wifiBssSecurityMode
Next sibling: wifiBssAccessMode
Status: current
Description: Controls whether the device will operate in closed network mode.
If set to true(1), then the network mode is closed and the SSID
will not be broadcast in beacon packets. If set to false(2), then
the network mode is open and the SSID will be broadcast in beacon
packets.
wifiBssAccessMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.1.1.6
Prev sibling: wifiBssClosedNetwork
Next sibling: wifiBssMaxAssociationsLimit
Status: current
Value list: 1: allowAny(1)
2: allowList(2)
3: denyList(3)
Description: Controls what stations will be given access to the device. If set
to allowAny(1), then any station will be allowed to connect. If
set to restrictToList(2), then only stations whose MAC address
appears in the wifiBssAccessTable will be allowed to connect. If
set to denyList(3), any station will be allowed to connect except
those in the wifiBssAccessTable.
wifiBssMaxAssociationsLimit
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.1.1.7
Prev sibling: wifiBssAccessMode
Status: current
Description: Configure the limit of maximum number of stations can associate
with the device.
Ubee Interactive
wifiBssWepDefaultKey
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.1.1.1
Parent: wifiBssWepEntry
Next sibling: wifiBssWepEncryptionMode
Status: current
Description: Controls and reflects the default key which will be used when 64
or 128 bit encryption is enabled. Indicates the entry from the
wifiBssWep64BitKeyTable if wifiEncryptionMode is set to wep64(1),
or the entry from the wifiBssWep128BitKeyTable if
wifiBssSecurityMode is set to wep128(2). This object may only be
set to indicate an active row in the wifiBssWep64BitKeyTable or
wifiBssWep128BitKeyTable. If the value corresponds to a row which
does not exist or a row which is not active, the set will be
rejected with an inconsistentValue error.
wifiBssWepEncryptionMode
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.1.1.2
Prev sibling: wifiBssWepDefaultKey
Next sibling: wifiBssWepPassPhrase
Status: current
Value list: 1: wep64(1)
2: wep128(2)
Description: Selects the WEP encryption method used by this service set. If set
to wep64(1), then 64 bit WEP encryption will be used with the keys
from the wifiBssWep64BitKeyTable. If set to wep128(2), then 128
bit WEP encryption will be used with keys from the
wifiBssWep128BitKeyTable.
wifiBssWepPassPhrase
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.1.1.3
Prev sibling: wifiBssWepEncryptionMode
Status: current
Size list: 1: 0..32
Description: The passphrase used for WEP security.
wifiBssWep64BitKeyIndex
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.2.1.1
Parent: wifiBssWep64BitKeyEntry
Next sibling: wifiBssWep64BitKeyValue
Status: current
Size list: 1: 1..4
Ubee Interactive
Description: Identifies an instance of a key among those used by the service

set identified by the value of ifIndex in the row index.
wifiBssWep64BitKeyValue
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.2.1.2
Prev sibling: wifiBssWep64BitKeyIndex
Next sibling: wifiBssWep64BitKeyStatus
Status: current
Size list: 1: 5
Description: A 40 bit key to be used when the corresponding instance of
wifiBssSecurityMode is set to wep(1) and the corresponding
instance of wifiBssWepEncryptionMode is set to wep64(1).
wifiBssWep64BitKeyStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.2.1.3
Prev sibling: wifiBssWep64BitKeyValue
Status: current
Description: The status of this conceptual row. To create a row in this table,
a manager must set this object to either createAndGo(4) or
createAndWait(5). Until instances of all corresponding columns are
appropriately configured, the value of the corresponding instance
of the wifiBssAccessStatus column is 'notReady'. In particular, a
newly created row cannot be made active until the corresponding
instance of wifiBssWep64BitKeyValue has been set. Only rows with
a status of active(1) will be applied. This object may not be set
to a value of notInService(2) or destroy(6) if the corresponding
instance of wifiBssWepDefaultKey identifies this row as they
current key in use. Such an attempt will be rejected with an
inconsistentValue error.
wifiBssWep128BitKeyIndex
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.3.1.1
Next sibling: wifiBssWep128BitKeyValue
Status: current
Size list: 1: 1..4
Description: Identifies an instance of a key among those used by the service
set identified by the value of ifIndex in the row index.
wifiBssWep128BitKeyValue
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.3.1.2
Prev sibling: wifiBssWep128BitKeyIndex
Next sibling: wifiBssWep128BitKeyStatus
Ubee Interactive

Status: current
Size list: 1: 13
Description: A 104 bit key to be used when the corresponding instance of
wifiBssSecurityMode is set to wep(1) and the corresponding
instance of wifiBssWepEncryptionMode is set to wep128(128).
wifiBssWep128BitKeyStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.3.1.3
Prev sibling: wifiBssWep128BitKeyValue
Status: current
instance of wifiBssWep128BitKeyValue has been set. Only rows with
a status of active(1) will be applied. This object may not be set
to a value of notInService(2) or destroy(6) if the corresponding
instance of wifiBssWepDefaultKey identifies this row as they
current key in use. Such an attempt will be rejected with an
inconsistentValue error.
wifiBssWpaAlgorithm
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.4.1.1
Parent: wifiBssWpaEntry
Next sibling: wifiBssWpaPreSharedKey
Status: current
Value list: 1: aes(2)
2: tkipPlusAes(3)
Description: Controls and reflects the WPA encryption mode used by the service
set. The WPA algorithm for WPA-PSK and WPA-Enterprise security
mode is aes(2). The WPA algorithm for WPA2-PSK and WPA2-Enterprise
security mode is either aes(2) or tkipPlusAes(3).
wifiBssWpaPreSharedKey
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.4.1.2
Prev sibling: wifiBssWpaAlgorithm
Next sibling: wifiBssWpaGroupRekeyInterval
Status: current
Size list: 1: 8..64
Description: Sets the WPA Pre-Shared Key (PSK) used by this service set. This
value MUST be either a 64 byte hexadecimal number, OR an 8 to 63
character ASCII string.
Ubee Interactive
wifiBssWpaGroupRekeyInterval
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.4.1.3
Prev sibling: wifiBssWpaPreSharedKey
Status: current
Units: seconds
Description: Sets the WPA Group Rekey Interval for this service set. If set to
zero, periodic rekeying is disabled for this service set.
wifiBssRadiusAddressType
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.5.1.1
Parent: wifiBssRadiusEntry
Next sibling: wifiBssRadiusAddress
Status: current
Description: The type of Internet address used for wifiBssRadiusAddress.
wifiBssRadiusAddress
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.5.1.2
Prev sibling: wifiBssRadiusAddressType
Next sibling: wifiBssRadiusPort
Status: current
Description: The Internet address of the RADIUS server for this service set.
wifiBssRadiusPort
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.5.1.3
Prev sibling: wifiBssRadiusAddress
Next sibling: wifiBssRadiusKey
Status: current
Description: The UDP port used to communicate with the RADIUS server for this
service set.
wifiBssRadiusKey
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.5.1.4
Prev sibling: wifiBssRadiusPort
Next sibling: wifiBssRadiusReAuthInterval
Ubee Interactive

Status: current
Description: The RADIUS key.
wifiBssRadiusReAuthInterval
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.3.5.1.5
Prev sibling: wifiBssRadiusKey
Status: current
Units: seconds
Description: The network re-authentication interval. If set to zero, no re-
authentication will be performed.
wifiBssAccessIndex
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.4.1.1.1
Parent: wifiBssAccessEntry
Next sibling: wifiBssAccessStation
Status: current
Size list: 1: 1..16
Description: Indicates the instance of this table row.
wifiBssAccessStation
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.4.1.1.2
Prev sibling: wifiBssAccessIndex
Next sibling: wifiBssAccessStatus
Status: current
Description: A MAC address of a station which will be allowed to connect to the
service set if wifiBssAccessMode is set to restrictToList(2), or
forbidden if wifiBssAccessMode is set to denyList(3).
wifiBssAccessStatus
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.2.4.1.1.3
Prev sibling: wifiBssAccessStation
Status: current
instance of wifiBssAccessStation has been set. Only rows with a
status of active(1) will be applied.
Ubee Interactive
wifiWmmAccessCategory
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.3.1.1.1
Parent: wifiWmmQosEntry
Next sibling: wifiWmmShortRetryLimit
Status: current
Value list: 1: background(0)
2: bestEffort(1)
3: video(2)
4: voice(3)
Description: Controls and reflects the WMM Access Category.
wifiWmmShortRetryLimit
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.3.1.1.2
Prev sibling: wifiWmmAccessCategory
Next sibling: wifiWmmLongRetryLimit
Status: current
Size list: 1: 1..15
Description: Controls and reflects the short retry limit for this WMM Access
Category.
wifiWmmLongRetryLimit
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.4684.38.2.2.2.1.18.1.3.1.1.3
Prev sibling: wifiWmmShortRetryLimit
Status: current
Size list: 1: 1..15
Description: Controls and reflects the long retry limit for this WMM Access
Category.
Ubee Interactive Accessing Telnet Remotely
13 Understanding the Telnet Command Line Interface

The Telnet network protocol provides bi-directional text-oriented communications. These
instructions show you how to access and use the Telnet interface to configure the
DDW365.
Topics
 Accessing Telnet Remotely on page 246
 Getting Help in Telnet on page 247
 Understanding Telnet Commands on page 247
13.1 Accessing Telnet Remotely
 The MSO-specified operational configuration must allow remote Telnet access, or it

must be changed as needed. Refer to Ubee MIBs on page 103 for more information.
 The MSO must obtain the Cable-RF IP address (for the specific cable modem) from
the provisioning system to use for remote Telnet access.
Steps
To remotely access the Telnet interface:
1. Open a command or other terminal window.

2. Enter the following command:
telnet <Cable-RF-IP-address>
3. At the telnet login prompt, use the MSO Web UI login:

MSO User Web Interface Login (Cox):
Username = admin
Password = POD (password of the day)
Ubee Interactive Getting Help in Telnet
13.2 Getting Help in Telnet

After you have logged in to Telnet remotely, you can use the following commands to
configure the DDW365.
Steps
To view help in telnet:
1. Enter a question mark (?) at the system prompt to display a list of commands and
directories.
Console>?
2. To see the options of a command or a command’s sub commands/arguments, use the

question mark (?). For example:
Console> find_command?
Console> find_command show?
3. Some of the Telnet commands are detailed in the following section.
13.3 Understanding Telnet Commands

This section explains some available Telnet command options.
Console> show
USAGE: show [all|tech_support|ip|reset|uptime|version]
Shows state of the system.
EXAMPLES:
show all -- All of the following, plus optionally recurse subtables
show tech_support -- All of the following; recurse all subtables, no user prompts
show ip -- All IP addresses in the system
show reset -- Reset reason history log
show uptime -- Time that system has been up
show version -- SW filename, version, and build info
Console> set
USAGE: set [username|password]
Sets the username/password for telnet/ssh logins
EXAMPLES:
set username -- Sets the username
set password -- Sets the password
Ubee Interactive Understanding Telnet Commands
Console> exit
USAGE: exit
End the current telnet or ssh interactive session
Console> reset
USAGE: reset
Causes the application to exit, shutting everything down and cleaning up resources. On embedded
platforms, this usually also triggers the internal CPU reset logic, causing the h/w to reboot.
Console/cm> diag
USAGE: diag [downstream|upstream] [Parm2]
Executes diag commands of the CM.
EXAMPLES:
diag downstream 525000000 -- Changes downstream frequency
diag upstream 125000000 -- Changes upstream frequency
Console/cm> log
USAGE: log [dsx|ranging|zone|off] [Log Setting{0..65535}]
Enables or disables real-time logging of specified message types or events
EXAMPLES:
log dsx 1 -- Enables DSx message logging
log dsx 0 -- Disables DSx message logging
log ranging 1 -- Enables ranging message logging
log ranging 0 -- Disables ranging message logging
log zone 0xFFFF -- Enables all zone message logging
log zone 0x0000 -- Disables all zone message logging
log off -- Disables all CM logging
Console/cm> ping
USAGE: ping IpAddress
Pings the specified target IP address from the CM IP stack
EXAMPLES:
ping 11.24.4.3 -- Ping IP address 11.24.4.3.
Console/cm> set
USAGE: set [firewall|d30version]
set firewall -- Sets the state of the CM.
set d30version -- Sets D30 version capability advertisement if no mdd is present.
EXAMPLES:
set firewall -- enables or disables the firewall.
set d30version -- enables or disables the D30 version capability advertisement in reg-req.
Console/cm> show
USAGE: show
[all|arp|bpi|certs|cls|cfg|cpe|ds|dscwer|dsx|event|flows|lease|mdd|route|state|status|tod|ucd|us|counters|debug|soc
kets|errors|us30|fam]
Shows the state of the cable modem.
EXAMPLES:
show all -- ALL options of this command
show arp -- ARP table
show bpi -- BPI status
show certs -- CM certificates
show cls -- Docsis classifiers
show cfg -- CM config file name and contents
show cpe -- CPE info/table
show ds -- Downstream status and signal quality
show dscwer -- Downstream Codeword Error Rate
show dsx -- DSx message history
show event -- CM event log
show flows -- Docsis service flows
show lease -- CM IP and DHCP options
show mdd -- MAC domain settings
show route -- The routing table
show state -- Full docsis state information
show status -- Docsis registration Status
show tod -- Time of day
show ucd -- Upstream descriptors
show us -- Upstream status
show counters -- HW Counters
show debug -- Hal debug
show sockets -- BcmSocket debug
show errors -- Error counters
show us30 -- DOCSIS 3.0 upstream counters
show fam -- Forward assist manager
Console/eRouter> show
USAGE: show [all|firewall|fwr|igmp|nat|nd|rg|reg_dump|dqm_status|promotion_threshold|upnp]
shows the state of the eRouter
EXAMPLES:
show firewall -- Displays the firewall nonvol settings
show fwr -- Displays current firewall ruleset
show igmp -- Displays the IGMP Group Statistics
show nat -- Displays the current NAT info
show nd -- Displays the current Neighbor Discovery Thread information
show rg -- Displays the RG nonvol settings
show upnp -- Displays UPnP settings and state information
show reg_dump -- Displays NATP 4KE registers.
show dqm_status -- Displays NATP DQM status
show promotion -- Displays NATP promotion threshold (pps).
Console/ethernet> diag
USAGE: diag [readmii|writemii] [Parm2] [Parm3] [Parm4]
Executes diag commands of the Ethernet interface.
EXAMPLES:
diag readmii 0 0x18 -- Reads from ethernet registers
diag writemii 0 0x18 0x400 -- Writes to ethernet registers
Console/ethernet> show
USAGE: show [all|debug]
Shows debug state of the Ethernet interface.
EXAMPLES:
show all -- Show all of the below
show debug -- Shows debug state of ethernet RX/TX DMA rings.
Console/FtpLite> ftp
USAGE: ftp
Begins FTP to the specified IP address, using the current settings.
EXAMPLES:
ftp -- Initiates FTP until a key is pressed.
Console/Ping> all_sizes
USAGE: all_sizes
Configures the settings for sweeping all packet sizes from 64-1518, with waiting and verification enabled.
The time between pings is set to 0 ms, the verbosity is set to full, and the reply wait time is set to 1/2
second. The IP address is not changed.
EXAMPLES:
all_sizes --
The following commands are listed under Console/Ping> directory:
end_size hs_nowait hs_wait ip_address ip_stack ip_sweep number_of_pings ping

restore_defaults show_settings start_size stats step_amount stop
time_between_pings verbosity verify_enable wait_enable wait_time
Console/power> client
USAGE: client [ID{0..100}] [enable|find|order|state|timer] [value{31}]
Sets the specified client parameter. If client ID is 0, the change will be made to all clients.
EXAMPLES:
client -- Prints the client list ordered by client ID number
client 1 enable 0 -- Disable client 1
client find HalIf -- Displays all clients with 'HalIf' in the name
client order reduced -- Prints the client list ordered by reduced power priority.
client order full -- Prints the client list ordered by full power priority.
client 1 timer 10 -- Sets the timer for client 1 to 10 seconds
client 1 state reduced -- Sets the state for client 1 to reduced power
The following commands are listed under Console/power> directory:
client debug level new_client show state
Console/system> diag
USAGE: diag [-p] [-c] [-s ParmSValue] [-n ParmNValue]
[readmem|writemem|clear_debug_counters|show_debug_counters|set_debug_flow|snmp_reset] [Parm2] [Parm3]
Executes diag commands of the system
EXAMPLES:
readmem -s 4 -n 64 0x80001234 -- Reads 64 bytes as 32-bit values.
writemem 0x80001234 0x56 -- Write a byte to the address.
clear_debug_counters -- Clear UTP debug counters.
show_debug_counters -- Show debug counters for a selected flow.
set_debug_flow 0 -- Enable debug counters for the selected flow.
snmp_reset -- Reset sockets for all SNMP agents.
The following commands are listed under Console/system> directory:
diag pktlog set show
Console/wifi> show
USAGE: show
[all|revision|led|chanspec|channel|country|ssid|wlc|bsscfg|htcap|ampdu|nvram|amsdu|sgitx|sgirx|rifs|wme_counter
s|assoclist]
Shows the state of the wifi interface.
EXAMPLES:
show ssid -- Displays the device's SSID
show revision -- Displays the wireless driver revision information
show led -- Displays the current state of the wireless LED's
show chanspec -- Displays the channel spec setting
show channel -- Displays the channel state and configuration
show country -- Displays the country setting
show wlc -- Displays the WLC setting
show bsscfg -- Displays the bsscfg setting
show htcap -- Displays the htcap configuration
show ampdu -- Displays the ampdu setting
show nvram -- Displays the driver nvram contents
show amsdu -- Displays the amsdu setting
show sgitx -- Displays the sgitx setting
show sgirx -- Displays the sgirx setting
show rifs -- Displays the rifs setting
show wme_counters -- Displays the WME counters
show assoclist -- Displays the association list
Console/wifi> wl
USAGE: wl [CmdLine{127}]
Sends commands to the 802.11 diagnostic and manufacturing utility.
EXAMPLES:
wl [command line parms] --

Ubee DDW365 MSO Operations Guide Cox 091515

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ubee DDW365 MSO Operations Guide Cox 091515

Uploaded by

Copyright:

Available Formats

Ubee DDW365

Wireless Cable Modem

MSO Operations Guide

This device is Wifi Alliance Certified:

2 Installing the DDW365 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Using the Web User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4 Understanding the Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5 Understanding the Basic Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

6 Understanding the Advanced Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

7 Understanding the Firewall Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

8 Understanding the Parental Control Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

9 Understanding the VPN Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

10 Understanding the Wireless Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

11 Understanding the USB Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

12 MIB Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

13 Understanding the Telnet Command Line Interface . . . . . . . . . . . . . . . . . . . . 246

 Understanding Safety and Regulatory Information on page 1

1.1 Understanding Safety and Regulatory Information

1.1.1 Understanding Safety

1.1.2 Understanding Eco-Environmental Statements

Packaging Collection and Recovery Requirements:

1.1.3 Understanding Regulatory Statements

Industry North America Statement:

Radiation Exposure Statement:

1.2 Understanding Connections and Applications

1.3 Requesting Support

1.4 Checking Device Package Components

1 - RJ45 Cable (Ethernet)

Sample image, actual appearance subject to change.

Sample image, actual appearance subject to change.

1.5 Understanding the Device Panels, Connections and LEDs

1.5.1 Understanding the Device Front and Rear Panels

Front Panel Rear Panel

1.5.2 Understanding the Device Connections

ETH1 Connects to Ethernet devices such as computers, gaming consoles,

1.5.3 Understanding LED Behavior

POWER White On – Internal power-on completed successfully.

ONLINE White Flashes – Obtaining an IP address and configuration file.

WiFi White On – WiFi is enabled.

LED Color Description

1.6 Understanding Specifications, Standards, and Firmware

1.7 Understanding Default Values and Logins

Web Interface: http://192.168.100.1

2.1 Setting Up and Connecting the DDW365

2.2 Connecting Devices to the Network

2.2.1 Connecting an Ethernet Device

2.2.2 Connecting a Wireless Device

Example pre-shared key: B7Y3R11000049

2.3 Troubleshooting the Installation

3.1 Accessing the Web User Interface Locally

3. Enter the username and password in the authentication dialog box.

 MSO Web Interface Login:

The Status screen displays software information about the DDW365.

3.2 Accessing the Web User Interface Remotely

3. Enter the username and password in the authentication dialog box.

3.3 Accessing Telnet Remotely

3. At the Telnet login prompt, enter:

3.4 Password of the Day Tool (PoTD)

Seed Enter the passphrase in the Seed field. For Cox

Default Date The default date is set to 1/1/2003.

Generate PoTD Generates the desired PoTD(s).

Encrypt Seed Displays the encrypted seed.

4.1 Using the Software Option

Software Version Defines the general software version of the device.