CISCO-CALL-TRACKER-TCP-MIB

All MIBs › CISCO-CALL-TRACKER-TCP-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2005-12-06

Category: Cisco Devices, Telephony and VoIP

Description: Tracks TCP-based call connections and statistics on Cisco access server platforms.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is CISCO-CALL-TRACKER-TCP-MIB?

CISCO-CALL-TRACKER-TCP-MIB extends the base CISCO-CALL-TRACKER-MIB with TCP-layer connection detail for calls handled by Cisco access server or gateway platforms, such as dial or VoIP-related sessions that use TCP transport. It exposes both an active-connection table and a history table recording local/remote IP addresses and TCP ports, plus failure counters for destination connection attempts. Its monitoring focus is on call/session performance and fault detection rather than hardware health: it lets an administrator see which TCP endpoints a device is actively servicing and detect connection failures that would indicate an unreachable or misbehaving remote peer. As its description states, it explicitly extends tables in CISCO-CALL-TRACKER-MIB, so meaningful use requires that base module's call context. It is used on Cisco access servers or voice gateways to troubleshoot call setup or signaling problems tied to TCP-based services. Engineers can download the CISCO-CALL-TRACKER-TCP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-CALL-TRACKER-TCP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Cisco access server or gateway (TCP-based call/signaling platform)

Monitoring Examples

An administrator would poll ccttActiveTable, examining ccttActiveLocalIpAddress, ccttActiveLocalTcpPort, ccttActiveRemoteIpAddress, and ccttActiveRemoteTcpPort to see current TCP-based call connections, then check ccttActiveDestinationFailures for a given entry. A rising ccttActiveDestinationFailures count for connections to one ccttActiveRemoteIpAddress would indicate that remote signaling server is unreachable or refusing connections, which the admin could confirm by reviewing matching entries in ccttHistoryTable.

What Can Be Monitored

active TCP call connections
local/remote IP address and port per call
destination connection failures
historical TCP call records

Imported Objects

From CISCO-CALL-TRACKER-MIB

cctActiveCallId	OBJECT-TYPE
cctHistoryIndex	OBJECT-TYPE

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From CISCO-TC

CiscoPort

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE

How to Use in IPNetwork Monitor

Example using ccttActiveDestinationFailures OID:

Select a Cisco access server or gateway (TCP-based call tracking) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type ccttActiveDestinationFailures into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of requests from the call processing software to the Telnet/TCP to setup a connection for which Telnet/TCP was unable to establish the requested connection. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoCallTrackerTCPMIB	1.3.6.1.4.1.9.9.164			This MIB module provides TCP service connection related data for tracking the progress and status of a call. This module extends tables defined in the MIB module ciscoCallTrackerMIB in CISCO-CALL-TRACKER-MIB.
ccttMIBObjects	1.3.6.1.4.1.9.9.164.1
ccttActive	1.3.6.1.4.1.9.9.164.1.1
ccttActiveTable	1.3.6.1.4.1.9.9.164.1.1.1		not-accessible	This table contains entries for active calls in the system which utilize TCP connections, as reported by cctActiveServiceType. This table extends the cctActiveTable, using the same index, cctActiveCallId.
ccttActiveEntry	1.3.6.1.4.1.9.9.164.1.1.1.1		not-accessible	The information related to TCP connection for a single call. Entries are created if the call requests TCP connection based service. Entries are deleted when the call terminates.
IP ccttActiveLocalIpAddress	1.3.6.1.4.1.9.9.164.1.1.1.1.1	IpAddress	read-only	The IP address for local endpoint of the call's TCP connection. This object has the same value as tcpConnLocalAddress from TCP-MIB.
CIS ccttActiveLocalTcpPort	1.3.6.1.4.1.9.9.164.1.1.1.1.2	CiscoPort	read-only	TCP port number for local endpoint of the call's TCP connection. This object has the same value as tcpConnLocalPort from TCP-MIB.
IP ccttActiveRemoteIpAddress	1.3.6.1.4.1.9.9.164.1.1.1.1.3	IpAddress	read-only	The IP address for remote endpoint of the call's TCP connection. This object has the same value as tcpConnRemAddress from TCP-MIB.
CIS ccttActiveRemoteTcpPort	1.3.6.1.4.1.9.9.164.1.1.1.1.4	CiscoPort	read-only	TCP port number for remote endpoint of the call's TCP connection. This object has the same value as tcpConnRemPort from TCP-MIB.
C32 ccttActiveDestinationFailuresEx	1.3.6.1.4.1.9.9.164.1.1.1.1.5	Counter32	read-only	The number of requests from the call processing software to the Telnet/TCP to setup a connection for which Telnet/TCP was unable to establish the requested connection.
ccttHistory	1.3.6.1.4.1.9.9.164.1.2
ccttHistoryTable	1.3.6.1.4.1.9.9.164.1.2.1		not-accessible	This table provides information on terminated calls with associated TCP connections, as reported by cctHistoryServiceType. This table extends the cctHistoryTable, using the same index, cctHistoryIndex.
ccttHistoryEntry	1.3.6.1.4.1.9.9.164.1.2.1.1		not-accessible	The information regarding a single terminated call with TCP connections. Entries are created and deleted in sync with the entries in cctHistoryTable, when there is a TCP connection service requested for the call.
IP ccttHistoryLocalIpAddress	1.3.6.1.4.1.9.9.164.1.2.1.1.1	IpAddress	read-only	The IP address for local endpoint of the call's TCP connection.
CIS ccttHistoryLocalTcpPort	1.3.6.1.4.1.9.9.164.1.2.1.1.2	CiscoPort	read-only	TCP port number for local endpoint of the call's TCP connection.
IP ccttHistoryRemoteIpAddress	1.3.6.1.4.1.9.9.164.1.2.1.1.3	IpAddress	read-only	The IP address for remote endpoint of the call's TCP connection. If no TCP connection was established, this object reports the first destination attempted.
CIS ccttHistoryRemoteTcpPort	1.3.6.1.4.1.9.9.164.1.2.1.1.4	CiscoPort	read-only	TCP port number for remote endpoint of the call's TCP connection. If no TCP connection was established, this object reports the TCP port of the first destination attempted.
C32 ccttHistoryDestinationFailures	1.3.6.1.4.1.9.9.164.1.2.1.1.5	Counter32	read-only	The number of requests from the call processing software to the Telnet/TCP to setup a connection for which Telnet/TCP was unable to establish the requested connection.
ccttMIBNotificationPrefix	1.3.6.1.4.1.9.9.164.2
ccttMIBNotifications	1.3.6.1.4.1.9.9.164.2.0
ccttMIBConformance	1.3.6.1.4.1.9.9.164.3
ccttMIBCompliances	1.3.6.1.4.1.9.9.164.3.1
ccttMIBCompliance	1.3.6.1.4.1.9.9.164.3.1.1			The compliance statement for entities which implement the CISCO CALL TRACKER TCP MIB
ccttMIBGroups	1.3.6.1.4.1.9.9.164.3.2
ccttActiveGroup	1.3.6.1.4.1.9.9.164.3.2.2			A collection of objects providing the active call information.
ccttHistoryGroup	1.3.6.1.4.1.9.9.164.3.2.3			A collection of objects providing the historical call information.

RFC description

Tracks TCP connection progress and status for VoIP and dial calls with connection statistics and state information.

Start monitoring Cisco access server or gateway (TCP-based call tracking) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-CALL-TRACKER-TCP-MIB