Table Of Contents
Call Tracker plus ISDN and AAA Enhancements for the Cisco AS5300 and Cisco AS5800
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Configuring Polling of Link Statistics
Configuring RADIUS Acct-Session-Id
Configuring RADIUS Login-IP-Host
Configuring AAA DNIS Authentication
Configuring ISDN B Channel Busyout
Configuring ISDN Cause Code Override
Configuring IP Multicast Heartbeat
ISDN Cause Code Override and Guard Timer
calltracker history retain-mins
radius-server attribute 44 include-in-access-req
radius-server challenge-noecho
Call Tracker plus ISDN and AAA Enhancements for the Cisco AS5300 and Cisco AS5800
This document introduces the Call Tracker feature and a set of ISDN and authentication, authorization, and accounting (AAA) enhancements to expand the call handling and real-time monitoring capabilities of the Cisco AS5300 and Cisco AS5800 universal access servers. The Call Tracker feature captures detailed statistics on the status and progress of active calls and retains historical data for disconnected call sessions. Call Tracker collects session information such as call states and resources, traffic statistics, total bytes transmitted and received, user IP address, and disconnect reason. This data is maintained within the Call Tracker database tables, accessible through SNMP, CLI , or SYSLOG.
The ISDN enhancements provide additional call-handling functionality for incoming ISDN calls, including a timer for authentication responses, an override for ISDN cause codes, and a flag indicating support for B-channel busyouts. The AAA enhancements include authentication by dialed number identification service (DNIS), selective termination of call sessions, and expanded support for several RADIUS attributes.
This document includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
This feature set provides additional call handling and monitoring functionality in these areas:
•
•
•
–
–
–
•
–
–
–
•
•
•
•
•
•
•
•
•
Even though Multicast Routing Monitor (MRM) can be used for this purpose, it has two problems:
–
–
To meet user requirements, the following configuration elements have been added/modified:
–
–
–
Benefits
•
•
•
•
•
•
Related Features and Technologies
•
•
•
•
Related Documents
•
•
•
•
•
•
Supported Platforms
•
•
Supported Standards, MIBs, and RFCs
MIBs
CISCO-CALL-TRACKER-MIB
CISCO-CALL-TRACKER-MODEM-MIB
CISCO-CALL-TRACKER-TCP-MIB
CISCO-MODEM-MGMT-MIB
CISCO-POP-MGMT-MIB
CISCO-IPMROUTE-MIB
For descriptions of supported MIBs and how to use MIBs, see Cisco's MIB web site on CCO at: http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
RADIUS Extensions (draft-ietf-radius-ext04.txt)
Prerequisites
Before configuring Call Tracker and its associated features, you must complete the following tasks on your network access server:
•
•
Note
•
•
Configuration Tasks
Perform the following tasks to configure Call Tracker and its related features:
•
•
•
•
•
•
•
Configuring Call Tracker
To configure Call Tracker, perform the following tasks in global configuration mode:
Configuring Polling of Link Statistics
To poll modem-link statistics, perform the following tasks in global configuration mode:
Note
Configuring RADIUS Acct-Session-Id
To configure AAA to include the Acct-Session-ID in Access-Request packets, perform the following tasks in global configuration mode:
Note
Configuring RADIUS Login-IP-Host
To enable the network access server to attempt more than one login host when trying to connect a dial-in user, you can enter up to three Login-IP-Host entries in the user's profile on the RADIUS server. The following example shows that three Login-IP-Host instances have been configured for the user joeuser, and that TCP-Clear will be used for the connection:
joeuser Password = xyzService-Type = Login,Login-Service = TCP-Clear,Login-IP-Host = 10.0.0.0,Login-IP-Host = 10.2.2.2,Login-IP-Host = 10.255.255.255,Login-TCP-Port = 23The order in which the hosts are entered is the order in which they are attempted. Use the ip tcp synwait-time command to set the seconds that the network access server waits before trying to connect to the next host on the list; otherwise, it waits 30 seconds.
Note
Configuring RADIUS Prompt
To control whether a user's responses to Access-Challenge packets are echoed to the screen, the Prompt attribute can be configured in the user's profile on the RADIUS server. This attribute is included only in Access-Challenge packets. The following example shows the Prompt attribute set to No-Echo, which prevents the user's responses from echoing:
joeuser Password = xyzService-Type = Login,Login-Service = Telnet,Prompt = No-Echo,Login-IP-Host = 172.31.255.255To allow a user's responses to echo, set the attribute to Echo. If the Prompt attribute is not included in the user profile, responses are echoed by default.
This attribute overrides the behavior of the radius-server challenge-noecho command configured on the access server. For example, if the access server is configured to suppress echoing, but the individual user's profile allows echoing, then the user's responses are echoed.
Note
Configuring AAA DNIS Authentication
To configure DNIS authentication, perform the following tasks in global configuration mode:
Configuring AAA POD
To configure POD, perform the following tasks in global configuration mode:
Configuring ISDN B Channel Busyout
To allow the busyout of individual ISDN PRI B channels, perform the following tasks in interface configuration mode:
Configuring ISDN Cause Code Override
To configure ISDN cause code overrides, perform the following tasks in interface configuration mode:
Configuring ISDN Guard Timer
To configure the ISDN guard timer, perform the following tasks in interface configuration mode:
Configuring IP Multicast Heartbeat
To configure IP multicast heartbeat, perform the following tasks in global configuration mode:
Verifying
To verify that the Call Tracker feature is configured properly, perform these tasks:
•
5300-UUT# show call calltracker summaryCall Tracker Status:Active Table:- 7 call(s)- 4473 bytes used (639 average, 639 maximum)History Table:- 50 of a maximum of 240 call(s) (20% full)- 45157 bytes used (903 average, 921 maximum)- 260000 minute(s) call retain timeAPI Front-end:- event elements:512 total, 512 free, 0 in-use- free event elements' low watermark:467- events dropped due to unavailability of free elts:0
Note
•
To verify that other features are configured correctly, enter the show running-config command.
Configuration Examples
The following examples display the screen output using the show running-config command:
•
•
Call Tracker
!calltracker enablecalltracker call-record tersecalltracker history max-size 50calltracker history retain-mins 5000!snmp-server engineID local 0012345snmp-server community public RWsnmp-server community private RWsnmp-server community wxyz123 view v1default ROsnmp-server trap-source FastEthernet0snmp-server packetsize 17940snmp-server queue-length 200snmp-server location SanJosesnmp-server contact Bobsnmp-server enable traps snmpsnmp-server enable traps calltrackersnmp-server enable traps isdn call-informationsnmp-server enable traps hsrpsnmp-server enable traps configsnmp-server enable traps entitysnmp-server enable traps envmonsnmp-server enable traps bgpsnmp-server enable traps ipmulticast-heartbeatsnmp-server enable traps rsvpsnmp-server enable traps frame-relaysnmp-server enable traps rtrsnmp-server enable traps syslogsnmp-server enable traps dlswsnmp-server enable traps dialsnmp-server enable traps dsp card-statussnmp-server enable traps voice poor-qovsnmp-server host 10.255.255.255 wxyz123snmp-server host 10.0.0.0 xxxyyy calltracker!radius-server host 172.16.0.0 auth-port 1645 acct-port 1646 non-standardradius-server key xyz!IP Multicast Heartbeat
!ip multicast-routing!snmp-server host 224.1.0.1 traps publicsnmp-server enable traps ipmulticastip multicast heartbeat ethernet0 224.1.1.1 1 1 10Modem Polling Link Statistics
!clock timezone PDT -8clock summer-time PDT recurringcalltracker enablecalltracker history retain-mins 10modem link-info poll time 300ip subnet-zerono ip domain-lookupip host jjjxxx 192.168.255.255ip host xxxyyy 172.31.255.255ip domain-name cisco.com!isdn switch-type primary-5esschat-script dial ABORT ERROR ABORT BUSY ABORT "NO CARRIER" TIMEOUT 30 "" at OK "mta receive maximum-recipients 0partition flash 2 8 8!RADIUS Acct-Session-Id
!aaa new-modelaaa authentication login CONSOLE noneaaa authentication login RADIUS-LIST group radius localaaa authentication ppp default localaaa authentication ppp RADIUS-LIST group radiusaaa authorization exec RADIUS-LIST group radius if-authenticatedaaa authorization exec CONSOLE noneaaa authorization network RADIUS-LIST group radius if-authenticatedaaa accounting suppress null-usernameaaa accounting delay-startaaa accounting network default start-stop group radiusaaa configuration config-username pools-ISP-r2 password ascendaaa nas port extendedenable secret 5 $ABCxyz!radius-server configure-nasradius-server host 172.16.0.0 auth-port 1645 acct-port 1646 non-standardradius-server timeout 15radius-server attribute 6 on-for-login-authradius-server attribute 44 include-in-access-reqno radius-server attribute nas-portradius-server key ciscoradius-server vsa send accountingradius-server vsa send authentication!DNIS Pre-authentication
!aaa new-modelaaa authentication login CONSOLE noneaaa authentication login RADIUS_LIST group radiusaaa authentication login TAC_PLUS group tacacs+ enableaaa authentication login V.120 noneaaa authentication enable default enable group tacacs+aaa authentication ppp RADIUS_LIST if-needed group radiusaaa authorization exec RADIUS_LIST group radius if-authenticatedaaa authorization exec V.120 noneaaa authorization network default group radius if-authenticatedaaa authorization network RADIUS_LIST if-authenticated group radiusaaa authorization network V.120 group radius if-authenticatedaaa accounting suppress null-usernameaaa accounting exec default start-stop group radiusaaa accounting commands 0 default start-stop group radiusaaa accounting network default start-stop group radiusaaa accounting connection default start-stop group radiusaaa accounting system default start-stop group radiusaaa preauthdnis password Cisco-DNISaaa nas port extended!radius-server configure-nasradius-server host 10.0.0.0 auth-port 1645 acct-port 1646 non-standardradius-server host 10.255.255.255 auth-port 1645 acct-port 1646 non-standardradius-server retransmit 2radius-server deadtime 1radius-server attribute nas-port format cradius-server unique-ident 18radius-server key MyKey!POD Server Key
!aaa new-modelaaa authentication ppp default radiusaaa accounting network default start-stop radiusaaa accounting delay-startaaa pod server server-key xyz123radius-server host 172.16.0.0 non-standardradius-server key rad123!ISDN B-Channel Busyout
!interface Serial0:23ip address 172.16.0.0 192.168.0.0no ip directed-broadcastencapsulation pppno keepalivedialer idle-timeout 400dialer load-threshold 1 eitherdialer-group 1isdn switch-type primary-5essisdn incoming-voice modemisdn snmp busyout b-channelno fair-queueno cdp enable!ISDN Cause Code Override and Guard Timer
!interface Serial0:23no ip addressno ip directed-broadcastencapsulation pppdialer rotary-group 0isdn switch-type primary-5essisdn incoming-voice modemisdn disconnect-cause 17isdn guard-timer 3000 on-expiry acceptisdn calling-number 8005551234no fair-queueno cdp enable!Command Reference
This section documents new and modified commands. All other commands used with these features are documented in the Cisco IOS Release 12.1 command references.
New Commands
•
•
•
•
•
•
Modified Commands
aaa pod server
To enable inbound user sessions to be disconnected when specific session attributes are presented, use the aaa pod server command. Enter the no form of this command to disable this feature.
aaa pod server [port port number] [auth-type {any | all | session-key}] server-key string
no aaa pod server
Syntax Description
Defaults
The POD server function is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
To disconnect a session, the values in one or more of the key fields in the POD request must match the values for a session on one of the network access server's ports. Which values must match depends on the auth-type attribute defined in the command. If no auth-type is specified, then all four values must match. If no match is found, all connections remain intact and an error response is returned. The key fields are as follows:
•
•
•
•
Examples
The following example enables POD and sets the secret key to ab9123.
aaa pod server server-key ab9123Related Commands
aaa preauth
To enable AAA pre-authentication, use the aaa preauth command. Use the no form of this command to disable AAA pre-authentication.
aaa preauth
no aaa preauth
Syntax Description
This command has no keywords or arguments.
Defaults
Pre-authentication using DNIS is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the aaa preauth command to enter AAA pre-authentication mode and enable pre-authentication using DNIS. In this mode, you can specify pre-authentication using the dnis subcommand and select the security server that provides authentication using the group subcommand.
Examples
The following example enables DNIS pre-authentication using a RADIUS server and the password Ascend-DNIS:
aaa preauthdnis password Ascend-DNISRelated Commands
Enables AAA pre-authentication using DNIS.
Selects the security server to use for AAA pre-authentication.
Enables a timer for AAA server requests.
calltracker call-record
To enable Call Record SYSLOG generation for the purpose of debugging, monitoring, or externally saving detailed call record information, use the calltracker call-record command. Use the no form of this command to disable Call Record SYSLOG generation.
calltracker call-record <terse | verbose> [quiet]
no calltracker call-record <terse | verbose> [quiet]
Syntax Description
Defaults
Call Tracker Call Record logging is disabled.
Command Modes
Global configuration
Related Commands
Usage Guidelines
SYSLOG Call Records will be generated in the order of 10 seconds of call termination. A small delay is needed to ensure that all subsystems finish reporting all appropriate information upon call termination. Furthermore, the process of logging is considered a very low priority with respect to normal call processing and data routing. As such, logging all call records can be guaranteed if Call Tracker is properly configured. However, the delay from the time a call actually terminated may vary if the CPU is busy handling higher-priority processes.
Call Tracker records must be found within the History table for at least 1 minute after call termination for this capability to work. As such, one must ensure that Call Tracker history collection is not disabled with the calltracker history configuration options.
Since the call rates possible on a high-capacity Access Server can be rather large and the information provided by the Call Records is substantial, simply enabling normal SYSLOG Call Records can make the use of the console difficult from the volume of records. As such, by using the quiet option and having a SYSLOG server configured to capture the Call Records, the console can be freed from displaying any Call Records, yet still have the Call Records captured by a SYSLOG server.
Currently, five different informational logs are available:
•
•
•
•
•
Examples
The following example reports the Verbose Call Records for a normal modem call termination:
*Nov 16 18:30:26.097: %CALLTRKR-3-CALL_RECORD: ct_hndl=5, service=PPP, origin=Answer, category=Modem, DS0 slot/cntr/chan=0/0/22, called=71071, calling=6669999, resource slot/port=1/0, userid=maverick5200, ip=192.9.1.2, mask=255.255.255.0, account id=5, setup=10/16/1999 18:29:20, conn=0.10, phys=17.12, srvc=23.16, auth=23.16, init-rx/tx b-rate=31200/33600, rx/tx chars=246/161, time=53.50, disc subsys=ModemDrvr, disc code=0xA220, disc text= Rx (line to host) data flushing - not OK/EC condition - locally detected/received DISC frame -- normal LAPM termination*Nov 16 18:30:26.097: %CALLTRKR-3-MODEM_CALL_REC: ct_hndl=5, prot: last=LAP-M, attempt=LAP-M, comp: last=V.42bis-Both, supp= V.42bis-RX V.42bis-TX, std: last=V.34+, attempt=V.34+, init=V.34+, snr=38, sq=3, rx/tx: chars=246/161, ec: rx/tx=22/12, rx bad=46, rx/tx b-rate: last=33600/33600, low=31200/33600, high=33600/33600, desired-client=33600/33600, desired-host=33600/33600, retr: local=0, remote=0, fail=0, speedshift: local up/down=1/0, remote up/down=0/0, fail=0, v90: stat=No Attempt, client=(n/a), fail=None, time(sec)=52, disc reason=0xA220*Nov 16 18:30:26.101: %CALLTRKR-3-MODEM_LINE_CALL_REC: ct_hndl=5, rx/tx levl=-17/-16, phase-jit: freq=0, levl=0, far-end echo-levl=-71, freq offst=0, phase-roll=-98, round-trip=1, d-pad=None, d-pad comp=0, rbs=0, const=16, rx/tx: sym-rate=3429/3429, carr-freq=1959/1959, trel-code=0/0, preemph-index=6/0, rx/tx: const-shape=Off/On, nonlin-encode=Off/On, precode=Off/On, xmit levl-reduct=2/3, shape=0x1920212120202120202020202020202020202020201F1D191100*Nov 16 18:30:26.101: %CALLTRKR-3-MODEM_INFO_CALL_REC: ct_hndl=5, general info=0x0, rx/tx link-layer=264/182, NAKs=0/0, rx/tx ppp-slip=5/7, bad ppp-slip=0, proj max rx b-rate: client=19200, host=24000, rx/tx: max neg I frame=128/128, neg window=15/15, T401 timeouts=1, tx window closures=0, rx overruns=0, retrans frames=0, v110: rx good=0, rx bad=0, tx=0, sync-lost=0, ss7/cot=0x00, v42bis size: dict=1024, test err=0, reset=0, v0 synch-loss=0, mail lost: host=0, sp=0, diag=0x00000000000000000000000000000000*Nov 16 18:30:26.101: %CALLTRKR-3-MODEM_NEG_CALL_REC: ct_hndl=5, v8bis cap=0x00000000000000000000000000000000000000000000, v8bis mod-sl=0x00000000000000000000000000000000000000000000, v8 jnt-menu=0x01E0C14513942A000000000000000000000000000000, v8 call-menu=0x01C14513942A00000000000000000000000000000000, v90 train=0x00000000, v90 sgn-ptrn=0x00000000, state trnsn=0x000102030410204042430451FF00000000000000000000000000000000000000, phase2=0x010000F4EF221FF37E0001E4EFA21FF2E30001A4EF980101B7CF98003C0000000034EF4000050216 0AE0301FFFFE1C07A707A70D650D6500Related Commands
calltracker enable
To enable Call Tracker on the access server, use the calltracker enable command. Use the no form of this command to restore the default condition.
calltracker enable
no calltracker enable
Syntax Description
This command has no keywords or arguments.
Defaults
Call Tracker is not enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
To enable real-time call statistics from the MICA modem to Call Tracker, you must configure the modem link-info poll time command.
Examples
None
Related Commands
calltracker history max-size
To set the maximum number of call entries stored in the Call Tracker history table, use the calltracker history max-size command. Use the no form of this command to restore the default value.
calltracker history max-size number
no calltracker history max-size number
Syntax Description
Defaults
The default maximum is dynamically calculated to be 1 time the max DS0 supported on given platform.
Command Modes
Global configuration
Command History
Usage Guidelines
Be careful when extending the history max-size, as this activity will cause Call Tracker to use more memory resources to store the additional call data. NAS memory consumption must be considered when increasing this parameter. The active call table is not affected by this command.
Examples
The following example sets the history table size to 50 calls:
calltracker history max-size 50Related Commands
calltracker history retain-mins
To set the number of minutes that call entries are stored in the Call Tracker history table, use the calltracker history retain-mins command. Use the no form of this command to restore the default value.
calltracker history retain-mins minutes
no calltracker history retain-mins minutes
Syntax Description
minutes
The length of time to store calls in the Call Tracker history table. The valid range is from 0 through 26,000 minutes. A value of 0 prevents any history from being saved.
Defaults
The default minutes is 5000.
Command Modes
Global configuration
Command History
Usage Guidelines
Active calls are not affected by this command. Entries in the active table are retained as long as the calls are connected.
Examples
The following example sets the retain time for the history table to 5000 minutes:
calltracker history retain-mins 5000Related Commands
dnis
To enable AAA pre-authentication based on the DNIS number, use the dnis AAA pre-authentication command.
dnis [password string]
Syntax Description
Pre-authentication using DNIS is disabled.
Command Modes
AAA pre-authentication configuration
Command History
Examples
The following example enables DNIS pre-authentication using a RADIUS server and the password Ascend-DNIS:
aaa preauthdnis password Ascend-DNISRelated Commands
Enters AAA pre-authentication mode.
Selects the security server to use for AAA pre-authentication.
Enables a timer for AAA server requests.
group
To select the security server to use for AAA pre-authentication requests, use the group AAA pre-authentication command.
group {radius | tacacs+ | server-group}
Syntax Description
Defaults
If this command is not configured, pre-authentication is performed by a RADIUS server.
Command Modes
AAA pre-authentication configuration
Command History
Examples
The following example enables DNIS pre-authentication using the abc123 server group and the password aaa-DNIS:
aaa preauthgroup abc123dnis password aaa-DNISRelated Commands
ip multicast heartbeat
To monitor the health of multicast delivery and be alerted when the delivery fails to meet certain parameters, use the ip multicast heartbeat command in global configuration mode. Use the no form of the command to disable the heartbeat.
ip multicast heartbeat group minimum window-size interval
no ip multicast heartbeat group minimum window interval
Syntax Description
Defaults
The command is disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
The subject group is joined at the subject interface so multicast data for the subject group will be attracted toward the subject router.
The router monitors multicast packets destined to group at interval seconds. This is a binary decision. That is, the number of packets seen in this period is not as important as whether any packet for the group is seen or not.
If multicast packets were observed in less than minimum out of the last window-size intervals, an SNMP trap would be sent from this router to a network management station to indicate a "loss of hearbeat" exception. This trap will be defined in CISCO-IPMROUTE-MIB.my.
The value of interval must be a multiple of 10. In multicast distributed switching (MDS), statistics from VIP (in RSP) or LC (in GSR) are passed to the routing processor once every 10 seconds. Monitoring packets not in intervals of multiple of 10 seconds may lead to incorrect decisions.
This command does not create any multicast routing entries that is necessary for the monitoring of the heartbeat packets. These entries can be created by either the downstream members of the group, or with the ip pim join-group or ip pim static-group commands. If a multicast routing entry corresponding to a group address is expired due to lack of interest from the downstream members, then the monitoring for the subject group would cease to work; that is, no more SNMP Trap would be emitted.
Examples
The following is an example configuration of the ip multicast heartbeat command.
snmp-server enable traps ipmulticast-heartbeatip multicast heartbeat 224.0.1.53 1 1 10In this example, multicast packets forwarded through this router to group address 224.0.1.53 will be monitored. If no packet for this group is received in a 10-second interval, an SNMP trap would be sent to a designated SNMP management station.
Note
Related Commands
Enables the router to send SNMP traps.
Monitors the action of the heartbeat trap.
isdn disconnect-cause
To send a specific ISDN cause code to the switch, use the isdn disconnect-cause command. Use the no form of the command to return to the default condition.
isdn disconnect-cause {cause-code-number | busy | not-available}
no isdn disconnect-cause
Syntax Description
Defaults
The default condition is no cause code override. If the isdn disconnect-cause command is not configured, the default cause codes for the application are sent.
Command Modes
Interface configuration
Command History
12.0(5)T
This command was introduced, and is a replacement for the isdn modem-busy-cause command.
Usage Guidelines
The isdn disconnect-cause command overrides specific cause codes (such as modem availability and resource pooling) that are sent to the switch by ISDN applications. When the isdn disconnect-cause command is implemented, the configured cause codes are sent to the switch; otherwise, the default cause codes for the application are sent. ISDN protocol errors are still reflected in the cause codes and are not overridden.
Examples
The following example sends the CHANNEL-NOT-AVAILABLE code to the ISDN switch:
interface serial0:20 isdn disconnect-cause not-availableRelated Commands
isdn guard-timer
To enable a managed timer for authentication requests, use the isdn guard-timer command. Use the no form of this command to reset the timer to its default value.
isdn guard-timer msecs [on-expiry {accept | reject}]
no isdn guard-timer
Syntax Description
Defaults
The default timer value is eight (8) seconds and calls are rejected when the timer expires.
Command Modes
Interface configuration
Command History
Usage Guidelines
The guard-timer starts when the DNIS number is sent to AAA for authentication. When the timer expires, authentication ends and the call is accepted or rejected based on the configured expiry action.
Examples
The following example sets the guard-timer to six (6) seconds and specifies that the call should be rejected if AAA does not respond within that interval:
interface serial 1/0/0:23isdn guard-timer 6000 on-expiry rejectRelated Commands
isdn snmp busyout b-channel
To enable PRI B channels to be busied out via SNMP, use the isdn snmp busyout b-channel command. Use the no form of this command to prevent B channels from being busied out via SNMP.
isdn snmp busyout b-channel
no isdn snmp busyout b-channel
Syntax Description
This command has no keywords or arguments.
Defaults
The default value is TRUE; that is, setting busyout via SNMP is allowed.
Command Modes
Interface configuration
Command History
Usage Guidelines
To busy out B channels on a PRI, the ISDN switch must support service messages. The isdn snmp busyout b-channel command sets the MIB object, cpmDS0BusyoutAllow, indicating whether or not the switch supports service messages, thereby allowing the busyout of B channels. When the network access server receives an SNMP request for a busyout, it checks the value of this object. If the no isdn snmp busyout b-channel command is configured, the busyout request fails.
Examples
The following example allows the busyout of B channels for serial interface 0:23:
router# conf trouter(config)# interface serial 0:23router(config-if)# isdn snmp busyout b-channelRelated Commands
None
modem link-info poll time
To set the polling interval at which link statistics are retrieved from the MICA modem, use the modem link-info poll time command. Use the no form of this command to return to the default condition.
modem link-info poll time seconds
no modem link-info poll seconds
Syntax Description
seconds
Number of seconds between polling intervals. The valid range is from 10 through 6,5535 seconds.
Link statistics are not polled.
Command Modes
Global configuration
Command History
Usage Guidelines
The modem link-info poll time command periodically polls active modem sessions to collect information such as attempted transmit and receive rates, maximum and minimum transmit and receive rates, and locally and remotely issued retrains and speedshift counters. This data is polled from MICA portware and passed to Cisco IOS software unsolicited.
Enabling the modem link-info poll time command disables the modem poll time command. Any modem poll time configuration is ignored because all modem events are sent to the access server unsolicited and no longer require polling by Cisco IOS software.
Note
Examples
The following example polls link statistics at 90 second intervals:
modem link-info poll time 300Related Commands
radius-server attribute 44 include-in-access-req
To send the RADIUS Acct-Session-Id (attribute 44) in authentication Access-Request packets, use the radius-server attribute 44 include-in-access-req command. Use the no form of this command to return to the default condition.
radius-server attribute 44 include-in-access-req
no radius-server attribute 44 include-in-access-req
Syntax Description
This command has no arguments or keywords.
Defaults
The Acct-Session-Id is not included in Access-Request packets.
Command Modes
Global configuration
Command History
Usage Guidelines
Using the radius-server attribute 44 include-in-access-req command generates the Acct-Session_Id prior to authentication, allowing a call's authentication records to be linked to its accounting records.
Examples
The following example sends the Acct-Session-Id in authentication Access-Requests:
radius-server attribute 44 include-in-access-reqRelated Commands
None
radius-server challenge-noecho
To prevent user responses to Access-Challenge packets from displaying on the screen, use the radius-server challenge-noecho command. Use the no form of this command to return to the default condition.
radius-server challenge-noecho
no radius-server challenge-noecho
Syntax Description
This command has no arguments or keywords.
Defaults
All user responses to Access-Challenge packets are echoed to the screen.
Command Modes
Global configuration
Command History
Usage Guidelines
This command applies to all users. When the radius-server challenge-noecho command is configured, user responses to Access-Challenge packets are not displayed; unless the Prompt attribute in the user's profile is set to echo on the RADIUS server. The Prompt attribute in a user's profile overrides the radius-server challenge-noecho command, for the individual user. For more information, see the "Configuring RADIUS Prompt" section.
Examples
The following example stops all user responses from displaying on the screen:
radius-server challenge-noechoRelated Commands
None
show call calltracker active
To display all of the information stored within the Call Tracker Active Database for all active calls, use the show call calltracker active command. This command allows you to display only calls for a single supported call category type, if desired.
show call calltracker active [category <isdn | modem | other | v110 | v120>]
Syntax Description
Defaults
The activity and configuration information is not displayed. The command show call calltracker active will show all calls, regardless of type, unless specified by the category option field.
Command Modes
Privileged EXEC
Command History
5300# show call calltracker active category modem-------------------------- call handle=0000000058 --------------------------status=Active, service=PPP, origin=Answer, category=ModemDS0 slot/cntr/chan=0/0/22, called=71071, calling=6669999userid=maverick5200, ip=192.9.4.2, mask=255.255.255.0setup=10/16/1999 18:29:20, conn=0.10, phys=17.00, service=24.71, authen=24.71init rx/tx b-rate=28800/33600, rx/tx chars=0/0resource slot/port=1/1, mp bundle=0, charged units=0, account id=75idb handle=0x6185B968, tty handle=0x612F8598, tcb handle=0x0----------------------------------------------------------------------------protocol: last=LAP-M, attempted=LAP-Mcompression: last=V.42bis-Both, supported= V.42bis-RX V.42bis-TXstandard: last=V.34+, attempted=V.34+, initial=V.34+snr=35 dB, sq=3, rx/tx level=-16/-15 dBmphase jitter: freq=0 Hz, level=0 degreesfar end echo level=-83 dBm, freq offset=0 Hzphase roll=-99 degrees, round-trip delay=1 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=0/0, preemphasis index=6/0rx/tx: constellation shape=Off/On, nonlinear encode=Off/Onrx/tx: precode=Off/On, xmit level reduct=2/2 dBmrx/tx: chars=0/0, general info=0x0rx/tx: link layer chars=0/0, NAKs=0/0error corrected: rx/tx=0/0, rx bad=0ec retransmissions=0, retransmitted frames=0rx/tx ppp slip=0/0, bad ppp slip=0rx/tx b-rate: last=28800/33600, lowest=28800/33600, highest=28800/33600phase 2 projected max rx b-rate: client=19200, host=24000phase 4 desired rx/tx b-rate: client=28800/33600, host=28800/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=1024, string=64T401 timeouts=0, tx window closures=0, rx overruns=0test err=0, reset=0, v0 synch loss=0mail lost: host=0, sp=0duration(sec)=16, disc reason=0x0disc text=(n/a)--------5---------10--------15--------20--------25--------30line shape : 0x1920212120202120202021202020202020202020201F1D191100v8bis capab : 0x00000000000000000000000000000000000000000000v8bis mod sl: 0x00000000000000000000000000000000000000000000v8 jnt menu : 0x01E0C14513942A000000000000000000000000000000v8 call menu: 0x01C14513942A00000000000000000000000000000000v90 training: 0x00000000v90 sgn ptrn: 0x00000000state trnsn : 0x00010203041020404243FF000000000000000000000000000000000000000000portwre diag: 0x00000000000000000000000000000000phase 2 info: 0x010000F4EF221FF37E0001E4EFA21FF2E30001A4EF980101B7CF98003C0000000024EF40000502160AE0304DFFFECE07A707A70D650D6500phase 4 info: 0x01834070808340708000Related Commands
show call calltracker handle
To display all the information stored within the Call Tracker Active or History Database Table for a specified unique call handle identifier, the show call calltracker handle command.
show call calltracker handle handle
Syntax Description
handle
Unique Call Identifier assigned by Call Tracker from moment a DS0 B Channel is requested. This identifier is a sequential number starting with handle 1.
Defaults
The activity and configuration information is not displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Each call managed by Call Tracker is assigned a unique call handle. This handle is provided to users via SNMP, CLI, or SYSLOG for all forms of data transfers. Thus, it becomes easier to display the information desired for a given call knowing its call handle than manually searching through all Call Tracker Database Tables for latest updates.
Examples
5300# show call calltracker handle 30-------------------------- call handle=0000000030 --------------------------status=History, service=None, origin=Answer, category=OtherDS0 slot/cntr/chan=0/0/22, called=71071, calling=6669999userid=(n/a), ip=0.0.0.0, mask=0.0.0.0setup=10/16/1999 18:29:20, conn=0.00, phys=0.00, service=0.00, authen=0.00init rx/tx b-rate=0/0, rx/tx chars=0/0resource slot/port=(n/a)/(n/a), mp bundle=0, charged units=0, account id=0duration(sec)=0.00, disc subsys=CSM, disc code=0x1Adisc text=Failed to find DSP resource----------------------------------------------------------------------------Related Commands
show call calltracker history
To display all the information stored within the Call Tracker History Database Table for most recent disconnected calls, use the show call calltracker history command.
show call calltracker history [category <isdn | modem | other | v110 | v120>]
Syntax Description
Defaults
The activity and configuration information is not displayed. The command show call calltracker history will show all calls, regardless of type, unless specified by the category option field.
Command Modes
Privileged EXEC
Command History
Examples
5300# show call calltracker history-------------------------- call handle=0000000030 --------------------------status=History, service=None, origin=Answer, category=OtherDS0 slot/cntr/chan=0/0/22, called=71071, calling=6669999userid=(n/a), ip=0.0.0.0, mask=0.0.0.0setup=10/16/1999 18:29:15, conn=0.00, phys=0.00, service=0.00, authen=0.00init rx/tx b-rate=0/0, rx/tx chars=0/0resource slot/port=(n/a)/(n/a), mp bundle=0, charged units=0, account id=0duration(sec)=0.00, disc subsys=CSM, disc code=0x1Adisc text=Failed to find DSP resource------------------------------------------------------------------------------------------------------ call handle=0000000031 --------------------------status=History, service=PPP, origin=Answer, category=ModemDS0 slot/cntr/chan=0/1/2, called=71071, calling=(n/a)userid=testme, ip=0.0.0.0, mask=0.0.0.0setup=10/16/1999 18:29:20, conn=3.12, phys=20.63, service=22.74, authen=0.00init rx/tx b-rate=31200/31200, rx/tx chars=221/120resource slot/port=1/1, mp bundle=0, charged units=0, account id=0duration(sec)=27.95, disc subsys=PPP, disc code=0x12disc text=Invalid Username----------------------------------------------------------------------------protocol: last=LAP-M, attempted=LAP-Mcompression: last=V.42bis-Both, supported= V.42bis-RX V.42bis-TXstandard: last=V.34+, attempted=V.34+, initial=V.34+snr=36 dB, sq=3, rx/tx level=-17/-14 dBmphase jitter: freq=0 Hz, level=0 degreesfar end echo level=-77 dBm, freq offset=0 Hzphase roll=-98 degrees, round-trip delay=2 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=0/0, preemphasis index=6/3rx/tx: constellation shape=Off/On, nonlinear encode=Off/Onrx/tx: precode=Off/On, xmit level reduct=2/1 dBmrx/tx: chars=221/120, general info=0x0rx/tx: link layer chars=242/167, NAKs=0/0error corrected: rx/tx=19/9, rx bad=32ec retransmissions=0, retransmitted frames=0rx/tx ppp slip=4/5, bad ppp slip=0rx/tx b-rate: last=31200/31200, lowest=31200/31200, highest=31200/31200phase 2 projected max rx b-rate: client=19200, host=24000phase 4 desired rx/tx b-rate: client=31200/31200, host=31200/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=1024, string=64T401 timeouts=0, tx window closures=0, rx overruns=0test err=0, reset=0, v0 synch loss=0mail lost: host=0, sp=0duration(sec)=24, disc reason=0xDF03disc text= Tx (host to line) data flushing - OK/Requested by host/DTR dropped--------5---------10--------15--------20--------25--------30line shape : 0x1920212120202120202020202020202020202020201F1D191100v8bis capab : 0x00000000000000000000000000000000000000000000v8bis mod sl: 0x00000000000000000000000000000000000000000000v8 jnt menu : 0x01E0C14513942A000000000000000000000000000000v8 call menu: 0x01C14513942A00000000000000000000000000000000v90 training: 0x00000000v90 sgn ptrn: 0x00000000state trnsn : 0x00010203041020FF000000000000000000000000000000000000000000000000portwre diag: 0x00000000000000000000000000000000phase 2 info: 0x010000F4EF321FE3FF0001E4EFA21FF2E30001A4EF980101B7CF98003C0000000014EF48002512D66AE1B0E1FFFE2207A707A70D650D6500phase 4 info: 0x01834079E079E079E000----------------------------------------------------------------------------Related Commands
show call calltracker summary
To display Call Tracker activity and configuration information such as the number of active calls and the history table attributes, use the show call calltracker summary privileged EXEC command.
show call calltracker summary
Syntax Description
This command has no keywords or arguments.
Defaults
The activity and configuration information is not displayed.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show call calltracker summary command:
5300# show call calltracker summaryCall Tracker Status:Active Table:- 7 call(s)- 4473 bytes used (639 average, 639 maximum)History Table:- 50 of a maximum of 240 call(s) (20% full)- 45157 bytes used (903 average, 921 maximum)- 260000 minute(s) call retain timeAPI Front-end:- event elements:512 total, 512 free, 0 in-use- free event elements' low watermark:467- events dropped due to unavailability of free elts:0Table 1 describes the fields shown in the show call calltracker summary display.
Related Commands
show modem calltracker
To display all of the information stored within the Call Tracker Active or History Database for latest call assigned to specified modem, use the show modem calltracker command. This command allows you to display all the Call Tracker data for a given modem when one does not have the call handle readily available and does not want to search the Call Tracker database.
show modem calltracker [slot/port]
Syntax Description
slot/port
(Optional) Specifies the location of a slot and modem port. Remember to include the forward slash(/) when entering this variable.
Defaults
The activity and configuration information is not displayed.
Command Modes
Privileged EXEC
Command History
Examples
5300# show modem calltracker 1/1-------------------------- call handle=0000000058 --------------------------status=Active, service=PPP, origin=Answer, category=ModemDS0 slot/cntr/chan=0/0/22, called=71071, calling=6669999userid=maverick5200, ip=192.9.4.2, mask=255.255.255.0setup=10/16/1999 18:29:20, conn=0.10, phys=17.00, service=24.71, authen=24.71init rx/tx b-rate=28800/33600, rx/tx chars=0/0resource slot/port=1/1, mp bundle=0, charged units=0, account id=75idb handle=0x6185B968, tty handle=0x612F8598, tcb handle=0x0----------------------------------------------------------------------------protocol: last=LAP-M, attempted=LAP-Mcompression: last=V.42bis-Both, supported= V.42bis-RX V.42bis-TXstandard: last=V.34+, attempted=V.34+, initial=V.34+snr=35 dB, sq=3, rx/tx level=-16/-15 dBmphase jitter: freq=0 Hz, level=0 degreesfar end echo level=-83 dBm, freq offset=0 Hzphase roll=-99 degrees, round-trip delay=1 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=0/0, preemphasis index=6/0rx/tx: constellation shape=Off/On, nonlinear encode=Off/Onrx/tx: precode=Off/On, xmit level reduct=2/2 dBmrx/tx: chars=0/0, general info=0x0rx/tx: link layer chars=0/0, NAKs=0/0error corrected: rx/tx=0/0, rx bad=0ec retransmissions=0, retransmitted frames=0rx/tx ppp slip=0/0, bad ppp slip=0rx/tx b-rate: last=28800/33600, lowest=28800/33600, highest=28800/33600phase 2 projected max rx b-rate: client=19200, host=24000phase 4 desired rx/tx b-rate: client=28800/33600, host=28800/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=1024, string=64T401 timeouts=0, tx window closures=0, rx overruns=0test err=0, reset=0, v0 synch loss=0mail lost: host=0, sp=0duration(sec)=16, disc reason=0x0disc text=(n/a)--------5---------10--------15--------20--------25--------30line shape : 0x1920212120202120202021202020202020202020201F1D191100v8bis capab : 0x00000000000000000000000000000000000000000000v8bis mod sl: 0x00000000000000000000000000000000000000000000v8 jnt menu : 0x01E0C14513942A000000000000000000000000000000v8 call menu: 0x01C14513942A00000000000000000000000000000000v90 training: 0x00000000v90 sgn ptrn: 0x00000000state trnsn : 0x00010203041020404243FF000000000000000000000000000000000000000000portwre diag: 0x00000000000000000000000000000000phase 2 info: 0x010000F4EF221FF37E0001E4EFA21FF2E30001A4EF980101B7CF98003C0000000024EF40000502160AE0304DFFFECE07A707A70D650D6500phase 4 info: 0x01834070808340708000----------------------------------------------------------------------------Related Commands
snmp-server enable traps
To enable the router to send SNMP traps, use the snmp-server enable traps command. Use the no form of this command to disable SNMP traps. The calltracker trap type was added for Cisco IOS Release 12.1(2)XH.
snmp-server enable traps [trap-type] [trap-option]
no snmp-server enable traps [trap-type] [trap-option]
Syntax Description
Defaults
This command is disabled by default. No traps are enabled.
If you enter this command with no keywords, the default is to enable all trap types.
Some trap types cannot be controlled with this command. These traps are either always enabled or enabled by some other means. For example, the linkUpDown messages are disabled by the no snmp trap link-status command.
Command Modes
Global configuration
Command History
11.1
This command was introduced.
11.3(1) MA
The voice trap type was added.
12.1(2)XH
The calltracker trap type was added.
Usage Guidelines
This command is useful for disabling traps that are generating a large amount of uninteresting or useless noise.
If you do not enter an snmp-server enable traps command, no traps controlled by this command are sent. In order to configure the router to send these SNMP traps, you must enter at least one snmp-server enable traps command. If you enter the command with no keywords, all trap types are enabled. If you enter the command with a keyword, only the trap type related to that keyword is enabled. To enable multiple types of traps, you must issue a separate snmp-server enable traps command for each trap type and option.
The snmp-server enable traps command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP traps. To send traps, you must configure at least one snmp-server host command.
For a host to receive a trap controlled by this command, both the snmp-server enable traps command and the snmp-server host command for that host must be enabled. If the trap type is not controlled by this command, only the appropriate snmp-server host command must be enabled.
The trap types used in this command all have an associated MIB object that allows them to be globally enabled or disabled. Not all of the trap types available in the snmp-server host command have notificationEnable MIB objects, so some of these cannot be controlled using the snmp-server enable traps command.
Examples
The following example enables the router to send Call Tracker traps:
configure terminalsnmp-server enable traps calltrackerThe following example enables the router to send poor quality of voice traps:
configure terminalsnmp-server enable traps voice poor-qovThe following example enables the router to send all traps to the myhost.cisco.com host using the public community string:
snmp-server enable trapssnmp-server host myhost.cisco.com publicThe following example enables the router to send Frame Relay and environmental monitor traps to the myhost.cisco.com host using the public community string:
snmp-server enable traps frame-relaysnmp-server enable traps envmon temperaturesnmp-server host myhost.cisco.com publicThe following example will not send traps to any host. The BGP traps are enabled for all hosts, but the only traps enabled to be sent to a host are ISDN traps.
snmp-server enable traps bgpsnmp-server host bob public isdnRelated Commands
snmp-server host
To specify the recipient of an SNMP notification operation, use the snmp-server host command. Use the no form of this command to remove the specified host. The calltracker notification type was added for Cisco IOS Release c5300-is-mz.redwood.beta.mmddyy.
snmp-server host host [traps | informs] [version {1 | 2c}] community-string [udp-port port]
[notification-type]no snmp-server host host [traps | informs]
Syntax Description
Defaults
This command is disabled by default. No notifications are sent.
If you enter this command with no keywords, the default is to send all trap types to the host. No informs will be sent to this host.
If no version keyword is present, the default is version 1. If no traps or informs keyword is present, traps are enabled.
The no snmp-server host command with no keywords will disable traps, but not informs, to the host. In order to disable informs, use the no snmp-server host informs command.
Command Modes
Global configuration
Command History
10.0
This command was introduced.
11.3(1) MA
The voice trap type was added.
12.1(2)XH
The calltracker notification type was added.
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. Traps are unreliable because the receiver does not send acknowledgments when it receives traps. The sender cannot determine if the traps were received. However, an SNMP entity that receives an inform request acknowledges the message with an SNMP response PDU. If the sender never receives the response, the inform request can be sent again. Thus, informs are more likely to reach their intended destination.
However, informs consume more resources in the agent and in the network. Unlike a trap, which is discarded as soon as it is sent, an inform request must be held in memory until a response is received or the request times out. Also, traps are sent only once, while an inform may be retried several times. The retries increase traffic and contribute to a higher overhead on the network.
If you do not enter an snmp-server host command, no notifications are sent. In order to configure the router to send SNMP notifications, you must enter at least one snmp-server host command. If you enter the command with no keywords, all trap types are enabled for the host. In order to enable multiple hosts, you must issue a separate snmp-server host command for each host. You can specify multiple notification types in the command for each host.
When multiple snmp-server host commands are given for the same host and kind of notification (trap or inform), each succeeding command overwrites the previous command. Only the last snmp-server host command will be in effect. For example, if you enter an snmp-server host inform command for a host and then enter another snmp-server host inform command for the same host, the second command will replace the first.
The snmp-server host command is used in conjunction with the snmp-server enable command. Use the snmp-server enable command to specify which SNMP notifications are sent globally. For a host to receive most notifications, at least one snmp-server enable command and the snmp-server host command for that host must be enabled.
However, some notification types cannot be controlled with the snmp-server enable command. For example, some notification types are always enabled. Other notification types are enabled by a different command. For example, the linkUpDown notifications are controlled by the snmp trap link-status command. These notification types do not require an snmp-server enable command.
A notification-type option's availability depends on the router and Cisco IOS software features supported on the router. For example, the envmon notification-type is available only if the environmental monitor is part of the system.
Examples
The following example sends Call Tracker traps to the host address 172.30.2.160 using the community string public:
snmp-server enable traps calltrackersnmp-server host 172.30.2.160 public calltrackerThe following example sends the SNMP and Cisco environmental monitor enterprise-specific traps to address 172.30.2.160:
snmp-server enable trapssnmp-server host 172.30.2.160 public snmp envmonThe following example sends all traps to the host myhost.cisco.com using the community string public:
snmp-server enable trapssnmp-server host myhost.cisco.com publicThe following example does not send traps to any host. The BGP traps are enabled for all hosts, but only the ISDN traps are enabled to be sent to a host.
snmp-server enable traps bgpsnmp-server host bob public isdnThe following example enables the router to send all inform requests to the host myhost.cisco.com using the public community string:
snmp-server enable trapssnmp-server host myhost.cisco.com informs version 2c publicRelated Commands
Debug Commands
This section describes new debug commands. All other commands used with these features are documented in the Cisco IOS Release 12.1 command references.
debug aaa pod
To display debug messages related to POD packets, use the debug aaa pod command. Use the no form of this command to disable debugging output.
debug aaa pod
no debug aaa pod
Syntax Description
This command has no keywords or arguments.
Defaults
Debugging for POD packets is not enabled.
Command History
Examples
The following example shows output from a successful POD request, when using the show debug command.
5300# debug aaa podAAA POD packet processing debugging is on5300# show debugGeneral OS:AAA POD packet processing debugging is on5300#*Jul 9 16:04:32.271:POD:10.100.1.34 request queued*Jul 9 16:04:32.271:POD:10.100.1.34 user 0.0.0.0 sessid 0x0 key 0xA5AFA004*Jul 9 16:04:32.271:POD: Line User IDB Session Id Key*Jul 9 16:04:32.271:POD:Skip Se0:21 meklund 0.0.0.0 0x0 0x0*Jul 9 16:04:32.271:POD:KILL Se0:22 meklund 0.0.0.0 0x60000020 0xA5AFA004*Jul 9 16:04:32.271:POD:Sending ACK to 10.100.1.34/1812---Interface Se0:22 was killed because the pod request contained a key of0xA5AFA004 and pod was configured with the commandaaa pod server port 1812 auth-type any server-key mykeyRelated Commands
debug calltracker
To display debug messages tracing the Call Tracker processing flow, use the debug calltracker command. Use the no form of this command to disable debugging output.
debug calltracker
no debug calltracker
Syntax Description
This command has no keywords or arguments.
Defaults
Call Tracker debugging is not enabled.
Command History
Examples
The following example shows output for a call coming up, when using the show debug command:
5300# debug calltracker5300# sh debugCall Tracker:Call Tracker's Registry API debugging is onCall Tracker's MIB API debugging is onCall Tracker's data base debugging is on5300#*Jan 1 17:33:00.195:CT:find_actv_by_ct_hndl:node (hndl=416) not in active table*Jan 1 17:33:00.195:Posting 19 event ../call-mgmt/calltrkr_api_frontend.c:801CT:reading new event(s) from API front-end*Jan 1 17:33:00.195:CT:find_actv_by_ct_hndl:node (hndl=416) not in active tableCT:node (hndl=416) found in history tableCT:actv-->hist ok:node (hndl=416) is now (or already was) in history table*Jan 1 17:33:00.319:ISDN Se0:23:calltrkr_disconnect hndl=416*Jan 1 17:33:00.319:SWAT-5300-UUT#CT:find_actv_by_ct_hndl:node (hndl=416) not in active table*Jan 1 17:33:00.319:Posting 19 event ../call-mgmt/calltrkr_api_frontend.c:801CT:reading new event(s) from API front-end*Jan 1 17:33:00.319:CT:find_actv_by_ct_hndl:node (hndl=416) not in active tableCT:node (hndl=416) found in history tableCT:actv-->hist ok:node (hndl=416) is now (or already was) in history table*Jan 1 17:33:00.331:%LINK-3-UPDOWN:Interface Serial0:20, changed state to down*Jan 1 17:33:00.331:Se0:20 PPP/CT/disconnect:zero handle detected, idb=0x61C25A84, code=3*Jan 1 17:33:02.183:%LINK-5-CHANGED:Interface Async8, changed state to reset5300#*Jan 1 17:33:02.183:As8 PPP/CT/disconnect:ct_hndl=416, idb=0x62235310*Jan 1 17:33:02.183:CT:find_actv_by_ct_hndl:node (hndl=416) not in active table*Jan 1 17:33:02.183:Posting 19 event ../call-mgmt/calltrkr_api_frontend.c:801CT:reading new event(s) from API front-end*Jan 1 17:33:02.187:CT:find_actv_by_ct_hndl:node (hndl=416) not in active tableCT:node (hndl=416) found in history tableCT:actv-->hist ok:node (hndl=416) is now (or already was) in history table*Jan 1 17:33:03.191:%LINEPROTO-5-UPDOWN:Line protocol on Interface Async8, changed state to down5300#*Jan 1 17:33:05.131:Posting 18 event ../call-mgmt/calltrkr_api_frontend.c:764CT:reading new event(s) from API front-endCT:calltrkr_dspbytecount():ct_hndl=416, tx/rx=426/647349CT:node (hndl=416) found in history table5300#*Jan 1 17:33:07.183:%LINK-3-UPDOWN:Interface Async8, changed state to down
Note
Related Commands
debug ip mhbeat
To monitor the action of the heartbeat trap, use the debug ip mhbeat command. Use the no form of this command to disable debugging output.
debug ip mhbeat
no debug ip mhbeat
Syntax Description
This command has no keywords or arguments.
Defaults
Debugging is not enabled.
Command History
Examples
5300#debug ip mhbeatIP multicast heartbeat debugging is on5300#debug snmp packetsSNMP packet debugging is onrouter(config)#ip multicast heartbeat intervals-of 10Dec 23 13:34:21.132: MHBEAT: ip multicast-heartbeat group 224.0.1.53 port 0source 0.0.0.0 0.0.0.0 at-least 3 in 5 intervals-of 10 secondsd5300#Dec 23 13:34:23: %SYS-5-CONFIG_I: Configured from console by consoleDec 23 13:34:31.136: MHBEAT: timer ticked, t=1,i=1,c=0Dec 23 13:34:41.136: MHBEAT: timer ticked, t=2,i=2,c=0Dec 23 13:34:51.136: MHBEAT: timer ticked, t=3,i=3,c=0Dec 23 13:35:01.136: MHBEAT: timer ticked, t=4,i=4,c=0Dec 23 13:35:11.136: MHBEAT: timer ticked, t=5,i=0,c=0Dec 23 13:35:21.135: Send SNMP Trap for missing heartbeatDec 23 13:35:21.135: SNMP: Queuing packet to 171.69.55.12Dec 23 13:35:21.135: SNMP: V1 Trap, ent ciscoExperiment.2.3.1, addr 4.4.4.4, gentrap 6, spectrap 1ciscoIpMRouteHeartBeat.1.0 = 224.0.1.53ciscoIpMRouteHeartBeat.2.0 = 0.0.0.0ciscoIpMRouteHeartBeat.3.0 = 10ciscoIpMRouteHeartBeat.4.0 = 5ciscoIpMRouteHeartBeat.5.0 = 0ciscoIpMRouteHeartBeat.6.0 = 3Related Commands
Monitors the health of multicast delivery and be alerted when the delivery fails to meet certain parameters.
Glossary
AAA—The services of authentication, authorization, and accounting
Access-Accept—A response packet from the RADIUS server notifying the access server that the user is authenticated. This packet contains the user profile, which defines the specific AAA functions assigned to the user.
Access-Challenge—A response packet from the RADIUS server requesting that the user supply additional information before being authenticated.
Access-Request—A request packet sent to the RADIUS server by the access server requesting authentication of the user.
accounting—The process of recording what a user is doing.
authentication—The process of determining who a user is.
authorization—The process of determining what a user can do.
B channel—bearer channel. In ISDN, a full-duplex, 64-kbps channel used to send user data.
CAS—channel associated signaling. Call signaling that enables the access server to send or receive analog calls.
cause codes—(defined by ITU Series Q Recommendation 850) Code that indicates the reason for ISDN call failure or completion.
DNIS—Dialed Number Identification Service, also known as the called party number. The telephone number of the called party after translation occurs in the Public Switched Telephone Network. A given destination may have a different DNIS number based on how the call is placed (for example, 800 or direct dial).
DS0—Digital signal level 0. Framing specification used in transmitting digital signals over a single channel at 64-kbps on a T1 facility.
ISDN—Integrated Services Digital Network. Communication protocol offered by telephone companies that permits telephone networks to carry data, voice, and other source traffic.
MIB—Management Information Base. Database of network management information that is used and maintained by a network management protocol such as SNMP. The value of a MIB object can be changed or retrieved using SNMP commands, usually through a GUI network management system.
NOC—network operations center. Organization responsible for maintaining a network.
POD—Packet of disconnect. A process that allows a PPP session to be verified and then terminated by the network access server.
PPP—Point-to-Point Protocol. Successor to SLIP that provides router-to-router and host-to-network connections over synchronous and asynchronous circuits.
PRI—Primary Rate Interface. ISDN interface to primary rate access. Primary rate access consists of a single 64-kbps D channel plus 23 (T1) or 30 (E1) B channels for voice or data.
RADIUS—Remote Authentication Dial-In User Service. RADIUS is a distributed client/server system that secures networks against unauthorized access. RADIUS clients run on Cisco routers and send authentication requests to a central RADIUS server containing all user authentication and network-service access information.
SNMP—Simple Network Management Protocol. Network management protocol used almost exclusively in TCP/IP networks. SNMP provides a means to monitor and control network devices, and to manage configurations, statistics collection, performance, and security.
switch—Network device that filters, forwards, and floods frames based on the destination address of each frame. The switch operates at the data link layer of the OSI model.
TACACS+—Terminal Access Controller Access Control System Plus. Authentication protocol, developed by the DDN community, that provides remote access authentication and related services, such as event logging. User passwords are administered in a central database rather than in individual routers, providing an easily scalable network security solution.
TCP-Clear—A raw TCP dialup connection, not using the Telnet protocol. It allows a direct connection from the user's termination point on the network access server to the destination specified by the Login-IP-Host and Login-TCP-Port.
Note
Guest
