Actions

Difference between revisions of "AlphaCom call statistics log"

From Zenitel Wiki

(What is logged, and where?)
(What is logged, and where?)
Line 53: Line 53:
 
Only the master module needs to have the Call Statistics Log activated in order to log all conversations within the Multi-Module.
 
Only the master module needs to have the Call Statistics Log activated in order to log all conversations within the Multi-Module.
  
Also see: [[RTP statistics in Alphanet]]
+
== Related articles ==
 +
* [[System log]]
 +
* [[Syslog (AlphaCom)]]
 +
* [[RTP statistics in Alphanet]]

Revision as of 13:38, 23 January 2009

This is the call log for the Alphacom. It is part of the Syslog (AlphaCom). Only received calls are logged from a AlphaCom. In order to get the complete picture in a AlphaNet, the call statistics log for all nodes has to be collected.

For calls over IP, statistics of packet loss and delay for the call is also logged.

Description of log string

                       Common part                                                                     Log event
|--------------------------------------------------------| |-----------------------------------------------------------------------------------------|
 Oct 24 10:19:31 src@Oppdal AlphaLog: Stat Event: Received Node3\S561(Ellefsen, Ak)->Node50\S2599(Egil@IP CR) for 322S (g722,late/K0,lost/K0,delay 0)
|---------------|----------|------------------------------|------------------------||------------------------|--------|------------------------------|
        |            |                    |                            |                        |                 |                   |            
        |            |                    |                            |                        |                 |                   |
        1            2                    3                            4                        5                 6                   7

 


Examples of log entries:

Oct 24 10:19:31 src@Oppdal AlphaLog: Stat Event: Received Node3\S561(Ellefsen, Ak)->Node50\S2599(Egil@IP CR) for 322 S (g722, late/K 0, lost/K 0, delay 0)
Oct 24 15:09:59 src@Oppdal AlphaLog: Stat Event: Received  Node50\S102(zEgil@Oppdal)->Node50\S6419(Egil@Analog) for 1 S


First entry is a IP related call (AlphaNet connection). The second one is a internal call between two ASLT based stations.


Detailed description of first entry:

  • 1 - Date and time of log event
  • 2 - Host name of AlphaCom which sent the message
  • 3 - Alphacom statistics log entry
  • 4 - Originator of call: Node Number/Directory Number/User Name
  • 5 - Destination of call: Node Number/Directory Number/User Name
  • 6 - Call duration in seconds
  • 7 - VoIP info
    • G.722 codec
    • 0 packets per 1000 packets arrived too late for playout
    • 0 packets per 1000 packets was lost (never arrived)
    • Delay is a estimate of the total audio roundtrip delay (in ms) of the conversation including local buffering at both ends. It is only calculated for vox duplex connections between analogue duplex stations in AlphaNet, because it is used to adjust the vox duplex algorithm.

What is logged, and where?

SysLog configured in Node 1:

  • logs conversations between locally connected stations (analogue and IP stations).
  • logs incoming calls from analogue and IP stations in other AlphaNet nodes.
  • logs incoming SIP calls from IP DECT phones (SIP registrar)
  • logs incoming calls from AudioCodes (SIP trunk)
  • logs outgoing Pocket Paging

Multi-Module: Only the master module needs to have the Call Statistics Log activated in order to log all conversations within the Multi-Module.

Related articles