Specifications

6-17
Cisco AS5x00 Case Study for Basic IP Modem Services
11/24/1999
Section 6 Modem Management Operations
Gathering and Viewing Call Statistics
3.2 Using Modem Call-Record Terse
Starting with Cisco IOS Releases 11.3AA and 12.0T, modem call records can be sent to syslog and
examined to perform statistical analysis.
For example, you can monitor:

Modulation trends such as V.90 verses V.34

Call time durations (consistent short connection times on a modem, regular Lost Carrier counts)

Unavailable user IDs

PPP negotiation or authentication failures
The following example enables modem call-records and sends the logs to wherever your syslog output
goes, for example:

To the console—if you do not have the
no logging console
command enabled.

To the terminal line—if you have the
terminal monitor
command enabled.

To a syslog host—if you have one configured.
5300-NAS#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
5300-NAS(config)#modem call-record terse
*Jan 1 04:19:50.262: %CALLRECORD-3-MICA_TERSE_CALL_REC: DS0 slot/contr/chan=0/0
/0, slot/port=2/0, call_id=18, userid=(n/a), ip=0.0.0.0, calling=4082329440, cal
led=5710945, std=V.34+, prot=LAP-M, comp=V.42bis both, init-rx/tx b-rate=26400/2
6400, finl-rx/tx b-rate=26400/26400, rbs=0, d-pad=None, retr=2, sq=3, snr=25, rx
/tx chars=79/94701, bad=0, rx/tx ec=60/204, bad=521, time=698, finl-state=Steady
, disc(radius)=(n/a)/(n/a), disc(modem)=A220 Rx (line to host) data flushing - n
ot OK/EC condition - locally detected/received DISC frame -- normal LAPM termina
tion