ZyXEL Communications P-660R-T1 - Page 91

P-660 series Support Notes
es)
SYSLOG_CDR, SYSLOG_INFO, String );
String = board xx line xx channel xx, call xx, str
the ha
e WAN ID in a board
AN
call
Outg
Incomi
C01 Incoming Call xxxx (means connected speed) xxxxx (means Remote Call ID)
(means connected speed) xxxxx (means Remote Call
ID)
L02 Call Terminated
1. CDR log(call messag
Format:
sdcmdSyslogSend(
board =
line = th
channel = channel ID within the W
rdware board ID
call = the
call
reference number which starts from 1 and increments by 1 for each new
str = C01
C01
oing Call dev xx ch xx (dev:device No. ch:channel No.)
ng Call xxxxBps xxxxx (L2TP,xxxxx means Remote Call ID)
L02 Tunnel Connected(L2TP)
C02 OutCall Connected xxxx
C02 CLID call refused
C02 Call Terminated
Example:
Feb 14 16:57:17 192.168.1.1 ZyXEL Communications Corp.: board 0 line 0 channel 0, call 18,
C01 Incoming Call OK
Feb 14 17:07:18 192.168.1.1 ZyXEL Communications Corp.: board 0 line 0 channel 0, call 18,
C02 Call Terminated
, SYSLOG_NOTICE, String );
x
Protocol: (1:IP 2:IPX 3:IPXHC 4:BPDU 5:ATALK 6:IPNG)
ata: We will send forty-eight Hex characters to the server
xample:
2. Packet triggered log
Format:
sdcmdSyslogSend( SYSLOG_PKTTRI
String = Packet trigger: Protocol=xx Data=xxxxxxxxx
D
E
Jul 19 11:28:39 192.168.102.2 ZyXEL Communications Corp.: Packet Trigger: Protocol=1,
Data=4500003c100100001f010004c0a86614ca849a7b08004a5c020001006162636465666768696
a6b6c6d6e6f7071727374
Jul 19 11:28:56 192.168.102.2 ZyXEL Communications Corp.: Packet Trigger: Protocol=1,
90
All contents copyright © 2005 ZyXEL Communications Corporation.