Difference between revisions of "AlphaCom call statistics log"
From Zenitel Wiki
(→Description of log string) |
|||
| (24 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{obsolete}} | ||
| + | This article is valid for AMC software 10.56 and earlier. As from AMC 10.60 the [[Call Statistics Log]] has been improved. | ||
| + | |||
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. | 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. | ||
| Line 6: | Line 9: | ||
<pre> | <pre> | ||
| − | + | 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) | 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 | + | 1 2 3 4 5 6 7 |
| − | |||
| − | |||
| − | |||
</pre> | </pre> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Detailed description of first entry: | Detailed description of first entry: | ||
| Line 36: | Line 26: | ||
* 5 - Destination of call: Node Number/Directory Number/User Name | * 5 - Destination of call: Node Number/Directory Number/User Name | ||
* 6 - Call duration in seconds | * 6 - Call duration in seconds | ||
| − | * | + | * 7 - VoIP info |
** G.722 codec | ** G.722 codec | ||
** 0 packets per 1000 packets arrived too late for playout | ** 0 packets per 1000 packets arrived too late for playout | ||
** 0 packets per 1000 packets was lost (never arrived) | ** 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. |
| + | |||
| + | ==Log string examples== | ||
| + | |||
| + | 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 | ||
| + | |||
| + | The first entry is an IP related call (AlphaNet connection). <br/> | ||
| + | The second one is an internal call between two ASLT based stations. | ||
| + | |||
| + | ==What is logged, and where?== | ||
| + | |||
| + | Call Statistics Log configured in Node 1 will log: | ||
| + | * conversations between locally connected stations (analogue and IP stations) | ||
| + | * incoming calls from analogue and IP stations in other AlphaNet nodes | ||
| + | * AllCall, Local Group Calls and Global Group Calls | ||
| + | * incoming calls from External Systems such as [[CB901 and AlphaCom E interfacing|RingMaster]] | ||
| + | * incoming SIP calls from IP DECT phones (SIP registrar) | ||
| + | * incoming calls from [[Configuration guide for AudioCodes MP114/118|AudioCodes]] (SIP trunk) | ||
| + | * outgoing Pocket Paging calls | ||
| + | |||
| + | '''AlphaNet:''' | ||
| + | In order to log all conversations between stations (analogue and IP), the Call Statistics Log in all ACE nodes must be activated. If they are all sent to the same SysLog (e.g. Kiwi Syslog Daemon), it will present a complete picture. If SIP calls are involved, call statistics from the different SIP equipment must be relayed to the same SysLog in order to log conversations in both directions. | ||
| + | |||
| + | '''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 == | ||
| + | * [[System log]] | ||
| + | * [[Syslog (AlphaCom)]] | ||
| + | * [[RTP statistics in Alphanet]] | ||
| − | + | [[Category:Logging]] | |
Latest revision as of 11:46, 11 September 2019
|
This product is discontinued! |
This article is valid for AMC software 10.56 and earlier. As from AMC 10.60 the Call Statistics Log has been improved.
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.
Contents
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
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.
Log string examples
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
The first entry is an IP related call (AlphaNet connection).
The second one is an internal call between two ASLT based stations.
What is logged, and where?
Call Statistics Log configured in Node 1 will log:
- conversations between locally connected stations (analogue and IP stations)
- incoming calls from analogue and IP stations in other AlphaNet nodes
- AllCall, Local Group Calls and Global Group Calls
- incoming calls from External Systems such as RingMaster
- incoming SIP calls from IP DECT phones (SIP registrar)
- incoming calls from AudioCodes (SIP trunk)
- outgoing Pocket Paging calls
AlphaNet: In order to log all conversations between stations (analogue and IP), the Call Statistics Log in all ACE nodes must be activated. If they are all sent to the same SysLog (e.g. Kiwi Syslog Daemon), it will present a complete picture. If SIP calls are involved, call statistics from the different SIP equipment must be relayed to the same SysLog in order to log conversations in both directions.
Multi-Module: Only the master module needs to have the Call Statistics Log activated in order to log all conversations within the Multi-Module.