Avaya
LogZilla App Store application: Avaya
App Function
The Avaya app parses 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
- Communication Manager overview
- Administering Avaya Aura Communication Manager
- Avaya Aura Communication Manager Support
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 |
Incoming Log Format
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 | 11.22.33.44 |
net_reg | 241 | ||
| ☑ | ext | voip_ext | 7632 |
| ☑ | the 1st ip | voip_ip | 55.66.77.88 |
the 2nd ip | 0.0.0.0 | ||
| ☑ | reason | avaya_reason | recovery |
Log Examples
VoIP Phone Registration
textIPEVT IPT_REG board=PROCR ip=11.22.33.44 net_reg= 241 ext= 7768 ip= 55.66.77.88; 1024 net_reg= 241 reason=recovery
VoIP Phone Network Status Change
textIPEVT IPT_TCP_UP board=PROCR ip=11.22.33.44 net_reg= 241 ext= 7632 the 1st ip=55.66.77.88;35770 the 2nd ip=0.0.0.0; 0 net_reg= 241 reason=endpoint_request
Configuration
In order to interface with LogZilla, the Avaya Communications Manager must be configured appropriately.