Actions

Recording of conversations using Duplex Conference and AGA board

From Zenitel Wiki

AlphaCom icon 300px.png
Recording of conversations - configuration example

See also: STENTOFON Recording
This article describes how the Duplex Conference can be used in combination with the AGA board to provide audio output for recording of conversations. The general concept is to convert a conversation to a 3-party duplex conference. The 3rd party is an AGA port. The audio from the AGA port goes to an external analog audio recorder. The stations involved can be analog (ASLT) stations or IP stations.

Software and hardware requirement

  • As from AMC 10.50 the Duplex Conference is included as a standard feature of the AMC-IP board, no additional hardware (AGA board) is required for the conference mixing. This article assumes that AMC 10.50 or later is used.
  • An AGA board provides the audio output to the external recorder. One AGA board has 6 "station" outputs. The audio output is 0 dBm level, available on the ab-wires of the port.
  • When the conversation beteween master station and substation is converted to duplex conference, two ASLT "speech channels" are required (Only when analog ASLT stations are used. IP stations don't use speech channels)

Important limitations

  • During the conversation there is no support for "digits during conversation". This means that the following features are NOT supported:
    • Put on Hold (Inquiry call) (2)
    • Call Transfer (3)
    • Busy Notify (57)
    • Private or Busy Override (58/59)
    • Door Opening (6)
    • Leave Call Back message (8)

Configuration example

In the following example the conversation from 3 master stations (101 to 103) needs to be recorded. The system can be configured to provide audio on the AGA ports only when calling to a predefined group of stations (UDP group 2), or one can choose to record all conversations.

Master stations

Master 102 included in UDP group 1 and EXP field set to 8302


  • Include the master stations in UDP group 1.
  • Each master station must "own" a Duplex Conference channel. The conference channel is defined in the "EXP field" of each master. Here station 101 is using conference 8301, station 102 is using 8302 and station 103 is using 8303.
  • In the Open Duplex window each master station must be set as "Master" of his conference. When the "Master" exit the conference all stations in this conference channel will be cancelled.

Substations

  • Include the substations to be recorded in UDP group 2. If all conversations should be recorded, use UDP group 8 (all stations included by default).

AGA ports

There must be one AGA port dedicated to each master station which is to be recorded.

Event Handler programming

Master stations are A-subscribers

If the substations are making Call Request to the master stations, the master station will be the the calling station (A-subscriber) in the conversation. The event type "08 - Conversation Outgoing" will be triggered when the conversation starts.

In AlphaPro, go to Exchange and System -> Events, press Insert and create the following event:


Event Owner: Stations w/ UDP Id: 1 (the master stations)
Event type: 08 – Conversation outgoing
Subevent: 0
When change to: ON
When related to: Stations w/ UDP Id:2 (the substations) or All
Action: $DISCON_ST L%1.dir U0
  $SDT L%1.exp '%2.nam'
  $ODC L%1.dir L%1.exp U1 U3
  $ODC L%2.dir L%1.exp U1 U3
  $ODC L9%1.dir L%1.exp U1 U3

Explanation:

When a master (UDP 1) calls a substation (UDP 2):
   $DISCON_ST L%1.dir           - Disconnect the master without cancel tone
   $SDT L%1.exp '%2.nam'        - Set the substation name as the name of the conference channel
   $ODC L%1.dir L%1.exp U1 U3   - Include the master in the conference channel defined in the EXP field of the master
   $ODC L%2.dir L%1.exp U1 U3   - Include the substation in the conference channel
   $ODC L9%1.dir L%1.exp U1 U3  - Include the AGA port 9xxx in the conference channel

Master stations are B-subscribers

If the substations are making direct calls in private mode, the master stations will be the called station (B-subscriber). Then the event type "07 – Conversation Incoming" must be used.

In AlphaPro, go to Exchange and System -> Events, press Insert and create the following event:


Event Owner: Stations w/ UDP Id: 1 (the master stations)
Event type: 07 – Conversation Incoming
Subevent: 0
When change to: ON
When related to: Stations w/ UDP Id: 2 (the substations) or All
Action: $DISCON_ST L%1.dir U0
  $SDT L%1.exp '%2.nam'
  $ODC L%1.dir L%1.exp U1 U3
  $ODC L%2.dir L%1.exp U1 U3
  $ODC L9%1.dir L%1.exp U1 U3

Start and stop recording by relay contact

Start and stop of recording can be controlled by a relay contact. There must be one relay contact for each master station.

In AlphaPro, go to Exchange and System -> Events, press Insert and create the following event:


Event Owner: Stations w/ UDP Id: 1 (the master stations)
Event type: 19 - Open Duplex Conf. Connect
Subevent: 0
When change to: ON or OFF
When related to: All
Action: RCO %1.phy %chg(ON,OFF)

Explanation: A RCO will go ON when a master station enters a Duplex Conference, and OFF when the master station leaves the conference. The RCO number is equal to the physical number of the master station, i.e. if the master station is connected to physical number 3, RCO 3 will be triggered.

Related articles