Accounting and System Messages


This description was taken from the Software Reference Guide, see at www.bintec.de

Syslog messages fall into two categories; Accounting messages and System

messages. Accounting messages are generated by the acct subsystem. (See

the Subject field of the biboAdmSyslogTable above.) System messages are

generated by any of the other BRICK subsystems which, depending on the

current license(s) installed on the system, may include:

isdn inet x25 ipx capi ppp

bridge config snmp x21 token ether

radius tapi ospf fr modem

Accounting Messages

Accounting messages are used to report accounting information relating to

either an ISDN connection or an IP session that was closed/routed over the

BRICK. Accounting messages are identified (in the biboAdmSyslogTable or

in a remote file on a LogHost where syslog messages are being sent) by an

initial ACCT: tag in the text of the message. For ISDN messages, the ISDN:

tag immediately follows; for IP accounting messages INET: follows.

ISDN Accounting Messages

An ISDN accounting message contains information regarding an ISDN

call that was either placed or received by the BRICK. Details for both suc-cessful

and unsuccessful ISDN outgoing calls are reported here. The con-tent

and format of ISDN accounting messages vary according to the spe-cial

formatting tags contained in the isdnAccountingTemplate. A list of

possible format tags that can be used in the accounting template and their

meanings are shown below.

The default accounting template setting contains the following tags:

%S,%s,%r,%d,%y,%Y,%g,%G,%C,%n,%Z,%T,%i,%u,%L

This template produces accounting messages similar to the following.

ISDN:18.08.1997,13:53:19,13:53:34,12,1096,1875,33,33,1Units,O,2,003039988452,7/0,9F,0

Format

Tag

Meaning

%S Date the connection opened; in DD.MM.YY format.

%s Time the connection was established: in HH:MM:SS format

%r Time the connection was closed: in HH:MM:SS format.

%d The duration of the connection in seconds.

%y Total number of bytes received over the connection.

%Y Total number of bytes sent over the connection.

%g Total packets received over the connection

%G Total packets sent over the connection.

%C Total number of charging units incurred for the connection.

%n The call’s direction; either incoming or outgoing.

%Z The local address (Calling or Called party’s number, see %n).

%T The remote address (Calling or Called party’s number %n).

%i Service indicator and additional information for the call.

%u DSS1 error cause, if applicable.

%L Local (BRICK internal) error cause.

%I Information about the BRICK subsystem the call was given to.

 

Wichtige Links

FAQ-Indexseite
 
If you have comments or suggestions, send email  at support@BinTec.DE