Table Of Contents
Call Tracker show Commands Extensions
Supported Standards, MIBs, and RFCs
Call Tracker show Commands Extensions
Feature History
This document describes the Call Tracker show Commands Extensions feature in Cisco IOS Release 12.2(11)T and includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
Before Cisco IOS Release 12.2(11)T, the show calltracker active and show calltracker history commands provided a simple way to examine the Call Tracker active table and Call Tracker history table in chronological order. The extensions to these commands available in Cisco IOS Release 12.2(11)T allow the command output to be reverse collated (output from most recent to least recent) or to be filtered by call category or service type. Historical data for disconnected call sessions can be filtered by subsystem type.
Benefits
The command enhancements allow the user more control over the quantity and type of information that is displayed from the show calltracker active and show calltracker history commands. Streamlined command output simplifies troubleshooting, especially for newer platforms where the number of ports is in the several hundreds, or even thousands.
Supported Platforms
•
Cisco AS5300
•
Cisco AS5350
•
Cisco AS5400
•
Cisco AS5800
•
Cisco AS5850
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions at http://www.cisco.com/register
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
Availability of Cisco IOS Software Images
Platform support for particular Cisco IOS software releases is dependent on the availability of the software images for those platforms. Software images for some platforms may be deferred, delayed, or changed without prior notice. For updated information about platform support and availability of software images for each Cisco IOS software release, refer to the online release notes or, if supported, Cisco Feature Navigator.
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature.
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites
Ensure that Call Tracker has been configured with adequate memory to hold history records for completed calls sufficiently long enough to be useful, as determined by the peak call completion rate and polling interval. For more information on setting up the Call Tracker feature, refer to the "Configuring and Managing Integrated Modems" section in the "Modem and Dial Shelf Configuration and Management" chapter of the Release 12.2 Cisco IOS Dial Technologies Configuration Guide.
Configuration Tasks
None
Configuration Examples
None
Command Reference
This section documents modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
•
show call calltracker history
show call calltracker active
To display all information stored within the Call Tracker active database for all active calls, use the show call calltracker active command in EXEC mode.
show call calltracker active [{category call-type} | {service session-type}] [reverse]
Syntax Description
Defaults
The default if neither the category nor service keyword is specified is to display all calls regardless of category or service session types.
Command Modes
EXEC
Command History
Release Modification12.1(3)T
This command was introduced.
12.2
This command was integrated into Cisco IOS Release 12.2.
12.2(11)T
The reverse and service keywords were added.
Usage Guidelines
The show call calltracker active command allows you to display active calls for a single supported call category or service session type, if desired, by using the category or service keyword, respectively. Call activity can be listed in reverse chronological order, from most recent to least recent, by using the reverse keyword.
Examples
The following example shows all Call Tracker activity in reverse order, from most recent to least recent. The entries are sorted by call handle, from highest to lowest.
Router# show call calltracker active reverse-------------------------- call handle=0000000003 --------------------------status=Active, service=PPP, origin=Answer, category=ModemDS0 slot/port/ds1/chan=7/0/19/0, called=77777, calling=(n/a)userid=modem1_2, ip=172.16.11.3, mask=172.16.11.3setup=08/01/2001 13:36:44, conn=0.02, phys=17.98, service=24.90, authen=24.90,init rx/tx b-rate=33600/33600, rx/tx chars=0/0resource slot/port=1/2, mp bundle=0, charged units=0, account id=7idb handle=0x660EB040, tty handle=0x62828B04, tcb handle=0x0...Table 1 describes the significant fields shown in the display.
Related Commands
show call calltracker history
To display all information stored within the Call Tracker history database table for the most recent historical calls, use the show call calltracker history command in EXEC mode.
show call calltracker history [{category call-type} | {service session-type} | {subsystem subsystem-type}] [reverse]
Syntax Description
Defaults
Specific activity and configuration information is not displayed.
Command Modes
EXEC
Command History
Release Modification12.1(3)T
This command was introduced.
12.2
This command was integrated into Cisco IOS Release 12.2.
12.2(11)T
The reverse, service, and subsystem keywords were added.
Usage Guidelines
The show call calltracker history command allows you to display the call history for a single supported call category type or service type, if desired, by using the category or service keywords respectively. Completed calls can be filtered based upon the disconnecting subsystem by using the subsystem keyword. For all tabular forms of the show call calltracker history command, the sorting order may be inverted by using the reverse keyword to give most-recent to least-recent collation.
Examples
The following example shows Call Tracker historical data for an outgoing modem-to-Layer 2 Transport (L2TP) Virtual Private Network (VPN) tunneled call that was disconnected by the ISDN subsystem:
Router# show call calltracker history subsystem isdn-------------------------- call handle=0000000002 ---------------------status=History, service=L2TP, origin=Answer, category=ModemDS0 slot/port/ds1/chan=7/0/2/0, called=70911, calling=(n/a)userid=modem1_1@bmw.com, ip=172.16.0.0, mask=172.16.0.0setup=08/01/2001 13:36:44, conn=0.02, phys=17.96, service=23.30, authen=22.26,init rx/tx b-rate=33600/33600, rx/tx chars=201/247resource slot/port=1/1, mp bundle=0, charged units=0, account id=6duration(sec)=132.50, disc subsys=ISDN, disc code=0x10disc text=Normal call clearing-----------------------------------------------------------------------protocol: last=LAP-M, attempted=LAP-Mcompression: last=V.42bis-Both, attempted= V.42bis-RX V.42bis-TXstandard: last=V.34+, attempted=V.90, initial=V.34+snr=40 dB, sq=5, rx/tx level=-15/-13 dBmphase jitter: freq=12 Hz, level=2 degreesfar end echo level=-90 dBm, freq offset=0 Hzphase roll=0 degrees, round-trip delay=0 msecsdigital pad=None dB, digital pad comp=0rbs pattern=0, constellation=16 pointrx/tx: symbol rate=3429/3429, carrier freq=1959/1959rx/tx: trellis code=16/16 preemphasis index=0/0rx/tx: constellation shape=Off/Off, nonlinear encode=Off/Offrx/tx: precode=Off/Off, xmit level reduct=0/0 dBmrx/tx: chars=201/247, general info=0x0rx/tx: link layer chars=172/214, NAKs=0/0error corrected: rx/tx=9/5, rx bad=0ec retransmissions=0, retransmitted frames=0rx/tx ppp slip=4/4, bad ppp slip=0rx/tx b-rate: last=33600/33600, lowest=33600/300, highest=33600/33600phase 2 projected max rx b-rate: client=33600, host=33600phase 4 desired rx/tx b-rate: client=33600/33600, host=33600/33600retrains: local=0, remote=0, failed=0speedshift: local up/down=0/0, remote up/down=0/0, failed=0v110: rx good=0, rx bad=0, tx=0, sync lost=0SS7/COT status=0x00v90: status=No Attempt, client=(n/a), failure=Nonerx/tx: max neg I frame=128/128, neg window=15/15v42bis size: dictionary=4096, string=32T401 timeouts=0, tx window closures=0, rx overruns=0test err=0, reset=0, v0 synch loss=0mail lost: host=0, sp=0duration(sec)=116, disc reason=0x220disc text= <unknown>/EC condition - locally detected/received DISC frame -- normal LAPM termination--------5---------10--------15--------20--------25--------30line shape : 0x0000000000000000000000000000000000000000000000000000v8bis capab : 0x12C9808081C609B502009481834347CB00000000000000000000000000000000v8bis mod sl: 0x0000000000000000000000000000000000000000000000000000000000000000v8 call menu: 0xC16513942A8D000000000000v90 training: 0x00000000v90 sgn ptrn: 0x00000000state trnsn : 0x0102030410151920FF0000000000000000000000000000000000000000000000portwre diag: 0x00000000000000000000000000000000phase 2 info: 0x02EFF41F120000003CEFF41F0200E0EF01040040860D1B083470600000EF1E041400E22D00003C07A707A70D650D65834083400000000000phase 4 info: 0x02834083408340834000total speedshifts: 0qc exchange: No QC Requestedmoh status: Modem is Not on Holdmoh count: 0, moh request count: 0total moh time: 0, cur moh time: 0call waiting retrains: 0rx/tx codewords: 0/0, rx/tx string: 0/0rx/tx history size: 0/0encoder/decoder state: 0/0rx/tx compression ratio: 0/0, rx/tx dictionary reset count: 0/0diagnostic code: 0x0000000000000000----------------------------------------------------------------------------Table 2 describes the significant fields shown in the display.
Related Commands
Glossary
CHAP—Challenge Handshake Authentication Protocol. Security feature supported on lines using PPP encapsulation that prevents unauthorized access. CHAP does not itself prevent unauthorized access, but merely identifies the remote end. The router or access server then determines whether that user is allowed access.
DSP—digital signal processor. A DSP segments the voice signal into frames and stores them in voice packets.
NAS—network access server. Cisco platform (or collection of platforms, such as an AccessPath system) that interfaces between the packet world (for example, the Internet) and the circuit world (for example, the Public Switched Telephone Network).
VPN—Virtual Private Network. Enables IP traffic to travel securely over a public TCP/IP network by encrypting all traffic from one network to another. A VPN uses tunneling to encrypt all information at the IP level.
