ZyXEL 2WG User Guide

Page of 780
 Chapter 43 System Information & Diagnosis
ZyWALL 2WG User’s Guide
637
CDR
Packet triggered
Filter log 
CDR Message Format
   SdcmdSyslogSend( SYSLOG_CDR, SYSLOG_INFO, String );
   String = board xx line xx channel xx, call xx, str
   board = the hardware board ID
   line = the WAN ID in a board
   Channel = channel ID within the WAN
   call = the call reference number which starts from 1 and increments by 1 for each new call
   str = C01 Outgoing Call dev xx ch xx (dev:device No. ch:channel No.)
         L02 Tunnel Connected(L2TP)
         C02 OutCall Connected xxxx (means connected speed) xxxxx (means Remote Call Number)
         L02 Call Terminated
         C02 Call Terminated
Jul 19 11:19:27 192.168.102.2 ZyXEL: board 0 line 0 channel 0, call 1, C01 Outgoing Call dev=2 
ch=0 40002
Jul 19 11:19:32 192.168.102.2 ZyXEL: board 0 line 0 channel 0, call 1, C02 OutCall Connected 
64000 40002
Jul 19 11:20:06 192.168.102.2 ZyXEL: board 0 line 0 channel 0, call 1, C02 Call Terminated
Packet triggered Message Format
SdcmdSyslogSend( SYSLOG_PKTTRI, SYSLOG_NOTICE, String );
       String = Packet trigger: Protocol=xx Data=xxxxxxxxxx…..x
       Protocol: (1:IP 2:IPX 3:IPXHC 4:BPDU 5:ATALK 6:IPNG)
       Data: We will send forty-eight Hex characters to the server
Jul 19 11:28:39 192.168.102.2 ZyXEL: Packet Trigger: Protocol=1,
Data=4500003c100100001f010004c0a86614ca849a7b08004a5c02000100616263646566676869
6a6b6c6d6e6f7071727374
Jul 19 11:28:56 192.168.102.2 ZyXEL: Packet Trigger: Protocol=1, 
Data=4500002c1b0140001f06b50ec0a86614ca849a7b0427001700195b3e00000000600220008c
d40000020405b4
Jul 19 11:29:06 192.168.102.2 ZyXEL: Packet Trigger: Protocol=1, 
Data=45000028240140001f06ac12c0a86614ca849a7b0427001700195b451d1430135004000077
600000