Asynchronous Connections

Step 1.

enable

Example:

Router> enable

Enters privileged EXEC mode or any other security level set by a system administrator. Enter your password if prompted.

Step 2.

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3.

calltracker enable

Example:

Router(config)# calltracker enable

Enables Call Tracker on the NAS.

Step 4.

calltracker call-record {terse | verbose} [quiet]

Example:

Router(config)# calltracker call-record verbose quiet

The information provided can be gathered by SNMP and SYSLOG from the call history table of Call Tracker.

The terse option generates a brief set of call records, which contains a subset of data stored within Call Tracker that is used primarily to manage calls.

The verbose option generates a complete set of call records that contain all data stored within Call Tracker that is used primarily to debug calls.

With the quiet option, the call record is sent only to the configured SYSLOG server and not to the console.

Step 5.

calltracker history max-size number

Example:

Router(config)# calltracker history max-size 50

To configure the history buffer (the maximum number of call entries stored in the Call Tracker history table), use the calltracker history max-size number command.

number is the maximum number of call entries to store in the Call Tracker history table. The valid range is from zero through ten times the maximum DS0 supported on given platform. A value of 0 prevents any history from being saved.

Because the reporting task is not a high priority process and because it must wait for available CPU, Call Tracker can take up to one minute to report after a call has disconnected. Therefore, you must configure the history buffer so that it is large enough to store the data that will be reported.

When you configure the buffer size, take into account the call length and type of call (ISDN is shorter than modem), and then determine the maximum number of calls that can be received over a one minute period. In addition, a higher call rate can occur when a configuration error or hardware failure occurs. Therefore, it is recommended that you use four times the number of ports on the platform.

For more information, refer to Call Tracker plus ISDN and AAA Enhancements for the Cisco AS5300 and Cisco AS5800.

Step 6.

calltracker history retain-mins minutes

Example:

Router(config)# calltracker history retain-mins 5000

Sets the number of minutes to store calls in the Call Tracker history table.

minutes is the length of time to store the calls. The valid range is from 0 through 26,000 minutes. A value of 0 prevents calls from being stored.

Step 7.

snmp-server packetsize byte-count

Example:

Router(config)# snmp-server packetsize 1024

Establishes control over the largest Simple Network Management Protocol (SNMP) packet size permitted when the SNMP server receives a request or generates a reply.

byte-count is an integer from 484 to 8192. The default is 1500.

Step 8.

snmp-server queue-length length

Example:

Router(config)# snmp-server queue-length 50

Defines the length of the message queue for each trap host. When a trap message is successfully transmitted, Cisco IOS software continues to empty the queue; however, it does not empty the queue faster than a rate of four trap messages per second.

During device bootup, some traps can be dropped because of trap queue overflow on the device. If you think that traps are being dropped, you can increase the size of the trap queue (for example, to 100) to determine if traps can then be sent during bootup

length is an integer that specifies the number of trap events that can be held before the queue must be emptied. The default is 10.

Step 9.

snmp-server enable traps calltracker

Example:

Router(config)# snmp-server enable traps

SNMP notifications can be sent as traps or inform requests; this command enables both traps and inform requests.

This command controls (enables or disables) Call Tracker CallSetup and CallTerminate notifications. CallSetup notifications are generated at the start of each call and when an entry is created in the active table (cctActiveTable). CallTerminate notifications are generated at the end of each call and when an entry is created in the history table (cctHistoryTable).

Step 10.

snmp-server host host community-string calltracker

Example:

Router(config)# snmp-server host host community string calltracker

Specifies the recipient of an Simple Network Management Protocol notification operation.

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 a SNMP response protocol data unit (PDU). If the sender never receives the response, the inform request can be sent again. Therefore, informs are more likely to reach their intended destination.

Compared to traps, informs consume more resources in the agent and in the network. Unlike traps, which are discarded as soon as they are 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; 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. 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.

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, as well as the type of notification (trap or inform), each succeeding command overwrites the previous command. Only the last snmp-server host command is 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 replaces the first.

Step 11.

calltracker timestamp msec (Optional)

Example:

Router(config)# calltracker timestamp msec

Displays the millisecond value of the call setup time in the Call Record (CDR) on the access server. If you do not execute this command, the call setup time is displayed in seconds.

Note: You can use this command with Cisco IOS Releases 12.3(4) and 12.3(4)T only.

Step 12.

modem link-info poll time seconds (Optional)

or

spe link-info poll modem seconds (Optional)

Example:

Router(config)# modem link-info poll time 320

Enables Call Tracker modem detail records.

Optionally, you can use either the modem link-info poll time seconds command or the spe link-info poll modem seconds command. These commands set the polling interval at which link statistics for active calls are retrieved from the modem. The recommended poll time value is 320 seconds.

To enable real-time call statistics from the MICA technologies modem to Call Tracker, you must use the modem link-info poll time command.

Note: The modem link-info poll time command consumes a significant amount of memory, approximately 500 bytes for each MICA modem call. Use this command only if you require the specific data that it collects.

Step 13.

exit

Example:

Router(config)# exit

Exits the current mode.

ct_hndl

Call Tracker Handle

A unique number used by Call Tracker to handle active calls. The calls are assigned an identification (ID) number from 1 to 4,294,967,296. These IDs start with 1 and increment by 1. After 4,294,967,295 calls, the ID wraps, and the 4,294,967,296^th call receives the next smallest available number that starts from 1. It is possible for the call history, syslog, and SNMP records to have the same ID number for different calls. This is because the number is only unique for active calls. Zero is not a valid value.

rx/tx levl

Receive/Transmit Level

Receive/Transmit Level Power of the receive/transmit signal, ranges from 0 to -128 in dBm steps. Typically the range in the United States is about -22 dBm and in Europe is -12 dBm. A good range is from -12dBm to -24dBm. For more information, refer to:

Understanding Transmit and Receive Levels on Modems

phase-jit: freq

Phase-jitter: Frequency

Peak to peak differential (in hertz) between two signal points. Phase jitter that is not cancelled looks like "rocking" of the baseband quadrature amplitude modulation (QAM) constellation. The points look like arcs with longer arcs on the outer points.

phase-jit: levl

Phase-jitter: Level

Level amount of phase jitter measured and indicates how large the "rocking" is in degrees. On an oscilloscope, the constellation points would look like crescent moons. Values can range up to 15 degrees. The typical value is zero (that is, phase jitter is not normally present).

far-end echo-levl

Far-end Echo-level

Over long connections, an echo is produced by impedance mismatches at 2-wire-to-4-wire and 4-wire-to-2-wire hybrid circuitry. The far-end echo level (that portion of the sent analog signal that has bounced off of the remote modem analog front end) may range from 0 to -90 in dBm.

freq offst

Frequency Offset

The difference (in hertz) between the expected RX carrier frequency and the actual RX carrier frequency.

phase-roll

Phase-roll

Phase roll affects the echo signal coming back. A certain constellation pattern is sent from a modem and arrives at to the central office. Some echoed form of this signal/constellation pattern is sent back. However, the constellation shape may be rotated from 0 to 359 degrees. This rotation is called the phase roll.

round-trip

Round Trip Delay

Total round trip propagation delay of the link (in milliseconds). This is important for proper echo cancellation. The amount that the delay varies on the network.

d-pad

Digital-pad

Digital padding value.

d-pad comp

Digital-pad Compression

This is an integer that represents the compression.

• 0 = None

• 1 = V.42bis TX

• 2 = V.42bis RX

• 3 = V.42bis both

• 4 = MNP5

• 5 = MH (FAX)

• 6 = MR (FAX)

• 7 = MMR (FAX)

• 8 = V.44 TX

• 9 = V.44 RX

• 10 = V.44 both

• 0xFF (-1) = Data Compression not yet negotiated

rbs

Robed Bit Signaling

Actual RBS pattern observed by the modem. The 6 least significant bits (LSB) of the returned value indicate the periodic RBS pattern where a 1 denotes a PCM sample with a robbed-bit.

const

Constellation

This is the number of points in the constellation.

• 0xFF = Invalid

• 1 = 4 point

• 2 = 16 point

rx/tx: sym-rate

Receive/Transmit: Symbol-rate

TX is symbol rate used to send samples to the line. RX is the symbol rate used to receive samples off of the line. The rates are synchronous with each other.

rx/tx: carr-freq

Receive/Transmit: Carrier-frequency

For TX, carrier frequency used by the local DCE. For RX, carrier frequency used by the remote DCE.

ct_hndl

Call Tracker Handle

A unique number used by Call Tracker to handle active calls. The calls are assigned an identification (ID) number from 1 to 4,294,967,296. These IDs start with 1 and increment by 1. After 4,294,967,295 calls, the ID wraps, and the 4,294,967,296^th call receives the next smallest available number that starts from 1. It is possible for the call history, syslog, and SNMP records to have the same ID number for different calls. This is because the number is only unique for active calls. Zero is not a valid value.

general info

General Information

General portware information.

rx/tx link-layer

Receive/Transmit Link-layer

The link-layer that were received or transmitted.

NAKs

NAKs

Total number of received and transmitted LCP messages that were not acknowledged.

rx/tx ppp-slip

Receive/Transmit PPP-SLIP

The number of PPP and Slip frames received or transmitted.

bad ppp-slip

Bad PPP-SLIP

The number of bad PPP and Slip frames received or transmitted.

proj max rx b-rate: client

Projected Max Receive Bit-rate: client

Projected maximum receive bit rate for the client.

rproj max rx b-rate: host

Projected Max Receive Bit-rate: Host

Projected maximum receive bit rate for the host.

rx/tx: max neg I frame

Receive/Transmit: Maximum Negotiated I Frame.

Transmit and receive maximum negotiated values for the frame.

rx/tx: neg window

Receive/Transmit: Negotiated Window

Transmit and receive negotiation window.

T401 timeouts

T401 Timeouts

Establish a connection to a client with V.42 EC enabled and pass data from the CSM. Query the statistic before the data is passed and again after the transfer was successful. The statistic should not increment.

tx window closures

Transmit Window Closures

Establish a connection to a client and pass data from the CSM. The statistic only increments if the window closes and does not receive an ACK/NAK from the client modem. The expected result should indicate 0.

rx overruns

Received Overruns

Total number of received overruns.

retrans frames

Retrain Frames

Total retrain frames initiated.

v110: rx good

V.110: Received Good

Number of v110 good frames received.

v110: rx bad

V.110: Received Bad

Number of v110 bad frames received.

v110: tx

V.110: Transmitted

Number of v110 frames transmitted.

v110: sync lost

v110: synchronization lost.

Number of times v110 synchronization is lost.

ss7/cot

Signaling System 7 (SS7) and Continuity Test (COT) statistics.

v42bis size: dict

V.42bis Size: Dictionary

Provides v42bis dictionary size.

test err

Test Error

Self test error encountered.

reset

Reset

DSP reset value.

v0 synch-loss

V.0 Synchronization Loss

Establish a connection with a client and verify the query indicates 0. The counter should only increment V0 sync is lost in the received signal which will trigger a retrain.

Mail lost: host

Mail Lost: Host

Number of host mail lost.

sp

SP

Number of sp mail lost.

diag

Diagnostic

Value for the portware diagnostic.

ct_hndl

Call Tracker Handle

A unique number used by Call Tracker to handle active calls. The calls are assigned an identification (ID) number from 1 to 4,294,967,296. These IDs start with 1 and increment by 1. After 4,294,967,295 calls, the ID wraps, and the 4,294,967,296^th call receives the next smallest available number that starts from 1. It is possible for the call history, syslog, and SNMP records to have the same ID number for different calls. This is because the number is only unique for active calls. Zero is not a valid value.

v8bis cap

V.8bis Capabilities.

Capabilities list received during V.8bis represented in hex. Refer to ITU-T V.8bis for more information about these bits.

v8bis mod_sl

V.8 Bis Mode Select

Mode selected during V.8bis represented in hex. Refer to ITU-T V.8bis for more information about these bits.

v8 jnt-menu

V.8 Joint-menu

Joint menu exchanged during V.8 represented in hex. Refer to ITU-T V.8 for more information about these bits.

v8 call-menu

V.8 Call-Menu

Call menu exchangeV.8 Call-Menu during V.8 represented in hex. Refer to ITU-T V.8 for more information about these bits.

v90 train

V.90 Train

Representation of V.90 Train in Hex.

v90 sgn-ptrn

V.90 Sign Pattern

The V.90 Sign Pattern.

state tsrnsn

State Transition

Value for state transition.

phase2

Phase 2

During Phase 2, all signals except L1 shall be transmitted at the nominal transmit power level. If a recovery mechanism returns the modem to Phase 2 from a later phase, the transmit level shall revert to the nominal transmit power from the previously negotiated transmit power level.