Skip to content

Avaya Call Manager

Rule Function

This rule parses the log messages provided by the Avaya Call Manager to extract information pertaining to certain VoIP phone operations and creates user tags with that information. There are two similar types of log messages that are handled.

Vendor Documentation

Log Source Details

Item Value
Vendor Avaya
Device Type VoIP telephone system
Collection Method Syslog
Configurable Log Output? no
Log Source Type Communications Manager software
Exceptions N/A

Currently Supported Log Types

These log messages are sent as syslog messages from the Communications Manager. The log format is approximately key-value pairs delimited by = and separated by spaces. However spaces may appear in the key names and otherwise seem to be inconsistent so strictly variable key-value parsing cannot be accomplished and message recognition must be used to parse the appropriate fields.

Parsed Metadata Fields

Tagged Field Name User Tag Name Example
(event) ipevt IPT_TCP_UP
board board PROCR
ip bpard_ip
net_reg 241
ext voip_ext 7632
the 1st ip voip_ip
the 2nd ip
reason avaya_reason recovery

High-Cardinality (HC) Tags

The set of values for each of the tagged fields should be of reasonable size, therefore it is not necessary to indicate any of the user tags are high cardinality (HC).

Log Examples

(line breaks between fields in the following examples are not included and have been added for readability:)

VoIP Phone Registration

IPEVT IPT_REG board=PROCR ip= net_reg= 241 ext= 7768 ip=; 1024 net_reg= 241 reason=recovery

VoIP Phone Network Status Change

IPEVT IPT_TCP_UP board=PROCR ip= net_reg= 241 ext= 7632 the 1st ip=;35770 the 2nd ip=; 0 net_reg= 241 reason=endpoint_request


In order to interface with LogZilla, the Avaya Communications Manager must be configured appropriately. There is documentation for how to do this here.