Actions

Difference between revisions of "Recording Event (Event Type)"

From Zenitel Wiki

Line 3: Line 3:
 
{|  
 
{|  
 
|-
 
|-
|width="180pt"|'''Event Owner''':
+
| width="180pt" |'''Event Owner''':
|width="600pt"| Station initiating the recording feature.
+
| width="600pt" |Station initiating the recording feature.
 
|-
 
|-
|'''Event type''': || 40 - Recording Info
+
|'''Event type''':||40 - Recording Info
 
|-
 
|-
|'''Subevent''': || Information type, see list below
+
|'''Subevent''':||Information type, see list below
 
|-
 
|-
|'''When change to ON''': || When state is reported.
+
|'''When change to ON''':||When state is reported.
 
|-
 
|-
|'''When change to OFF''': || Only for sub event 0 when recording ends.
+
|'''When change to OFF''':||Only for sub event 0 when recording ends.
 
|-
 
|-
|'''When related to''': || Participant of the recording session. (B station, group call etc.)
+
|'''When related to''':||Participant of the recording session. (B station, group call etc.)
 
|-
 
|-
 
|}
 
|}
Line 20: Line 20:
  
 
Regarding the Event Owner:  
 
Regarding the Event Owner:  
* The owner of the event is the A-station in a conversation, or the initiator of a group call.
+
 
* For Simplex conference, station "1" is always the owner. "Related To" is the conference directory number, e.g. "8201".
+
*The owner of the event is the A-station in a conversation, or the initiator of a group call.
 +
*For Simplex conference, station "1" is always the owner. "Related To" is the conference directory number, e.g. "8201".
  
 
==Additional information==
 
==Additional information==
* Sub-event 0:  ON = Recording "process" starts. OFF = Recording "process" stop. (This does not mean that the actual recording is taking place. For "recording on demand" the ON event will trigger when conversation starts, sub event 1 or 2 will trigger when or if $REC start the recording.)
+
 
* Sub-event 1:  ON = The Recorder "1" reply "OK" to recording audio session. (This means the "physical" recording starts)
+
*Sub-event 0:  ON = Recording "process" starts. OFF = Recording "process" stop. (This does not mean that the actual recording is taking place. For "recording on demand" the ON event will trigger when conversation starts, sub event 1 or 2 will trigger when or if $REC start the recording.)
* Sub-event 2:  ON = The Recorder "2" reply "OK" to recording audio session. (This means the "physical" recording starts)
+
*Sub-event 1:  ON = The Recorder "1" reply "OK" to recording audio session. (This means the "physical" recording starts)
* Sub-event 10: ON = No response from any of the recorders, this means the recording is failing at start up.
+
*Sub-event 2:  ON = The Recorder "2" reply "OK" to recording audio session. (This means the "physical" recording starts)
* Sub-event 11: ON = Recorder terminated the recording session before the "audio" recording session was ended at AlphaCom side.
+
*Sub-event 10: ON = No response from any of the recorders, this means the recording is failing at start up.
 +
*Sub-event 11: ON = Recorder terminated the recording session before the "audio" recording session was ended at AlphaCom side.
 +
*Sub-event 20:  ON = SIP registration Recorder "1", OFF = SIP registration timeout. (ICX 1.0.3.3)
 +
*Sub-event 21:  ON = SIP registration Recorder "2", OFF = SIP registration timeout (ICX 1.0.3.3)
  
 
Available from alphasys 11.3.3.1.
 
Available from alphasys 11.3.3.1.

Revision as of 15:18, 9 December 2019

AI.png


Event description

Event Owner: Station initiating the recording feature.
Event type: 40 - Recording Info
Subevent: Information type, see list below
When change to ON: When state is reported.
When change to OFF: Only for sub event 0 when recording ends.
When related to: Participant of the recording session. (B station, group call etc.)


Regarding the Event Owner:

  • The owner of the event is the A-station in a conversation, or the initiator of a group call.
  • For Simplex conference, station "1" is always the owner. "Related To" is the conference directory number, e.g. "8201".

Additional information

  • Sub-event 0: ON = Recording "process" starts. OFF = Recording "process" stop. (This does not mean that the actual recording is taking place. For "recording on demand" the ON event will trigger when conversation starts, sub event 1 or 2 will trigger when or if $REC start the recording.)
  • Sub-event 1: ON = The Recorder "1" reply "OK" to recording audio session. (This means the "physical" recording starts)
  • Sub-event 2: ON = The Recorder "2" reply "OK" to recording audio session. (This means the "physical" recording starts)
  • Sub-event 10: ON = No response from any of the recorders, this means the recording is failing at start up.
  • Sub-event 11: ON = Recorder terminated the recording session before the "audio" recording session was ended at AlphaCom side.
  • Sub-event 20: ON = SIP registration Recorder "1", OFF = SIP registration timeout. (ICX 1.0.3.3)
  • Sub-event 21: ON = SIP registration Recorder "2", OFF = SIP registration timeout (ICX 1.0.3.3)

Available from alphasys 11.3.3.1.

Application