Layer1 Alarms

From RtpBridge
Jump to: navigation, search

Abstract

RtpBridge could be configured to send Layer1 Alarms to a remote host using the UDP transport. It is possible to send the Layer1 Alarms using the command events.

Command syntax Description

[console] events udp:<ip_addr>:<remote_port>:<local_port>

Fields:

ip_addr - Outgoing UDP Connection IP Address of the Remote Host;
remote_port - Outgoing UDP Connection port of the Remote Host;
local_port - UDP port that the data will be sent from.

When configuring via Telnet or via configuration file /etc/rtpbridge/cfg the word console should precede the word events.

Layer1 Alarm packet format

Format of the Layer1 Alarm packet is shown below.

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   0 |                                                               |
     +                           Timestamp                           +
  32 |                                                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  64 |                          Device Type                          |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  96 |           Source ID           |           Bridge ID           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 128 |                             Device                            |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 160 |                              Code                             |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 192 |                           Request ID                          |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 224 |                           Parameter                           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Note that each tick mark represents one bit position.

Fields

Timestamp: 64 bits
Timestamp of the event. Absolute time in 100 nanosecond increments since midnight Jan 1, 1601, often used for time stamps.
Device Type: 32 bits
Device Type with which the event is associated. The most possible types:
17: T1/E1 Line Interface;
64: Board Alvis-ASM with 1,2 or 4 DaVinci DMPs;
67: Digital Media Processor on Alvis-ASM board or Alvis-PCIe board;
68: Board Alvis-PCIe;
69: Digital Media Processor on Alvis-4-CSI;
70: Digital Media Processor on Alvis-4M-CSI;
71: Digital Media Processor on Alvis-8-CSI;
72: Digital Media Processor on Alvis-8M-CSI;
81: Digital Media Processor on Alvis-2-CSI;
82: Digital Media Processor on Alvis-0-CSI;
83: Digital Media Processor on Alvis-2-PBX;
84: Digital Media Processor on Alvis-0-PBX;
85: Digital Media Processor on Alvis-4-PBX;
86: Digital Media Processor on Alvis-8-PBX.
Source ID: 16 bits
Device ID of the Device that the event is associated with (supplied by the user when the device was opened/created).
Bridge ID: 16 bits
Identifier of the RtpBridge instance. To set Bridge ID use rtpbridge command line argument: -i (or --id). For example, the command:

 /opt/rtpbridge/rtpbridge --id 12

sets the identifier of the RtpBridge instance to 12.
Device: 32 bits
Handle of the Device with which the event is associated.
Code: 32 bits
Device specific cause code indicating what happened. Each device type has its own set of event cause codes.
Request ID: 32 bits
If the message is for a previous user request, this member holds the user assigned request ID.
Parameter: 32 bits
Optional parameter, usually number of bytes to be fetched.


Note: all values are in host byte order.