Adutante
  • Infoshare
    • Infoshare
    • AduCRM
    • Recordings
    • Users
    • AduCRM
  • Signed in: Administrator
    • Change Password
    • Signoff
    • Online Documentation
    • Adutante ver. 5.0.0.0
    • Product Registration
  • Language
    • English
    • Spanish

PAGE TITLE

Date Last Modified
infoshare.htm
Infostore
    • Content
    • Test Groups
    • Comments
    • Revisions
  • Content
  • Comments
  • Test Groups
  • SSU
  • Attachments
  • Tools
  • Tags
  • Edit
  • English - About VSLogger Call Recording
    • Quick Guides
      • Quick Guide - Recorder system
      • Quick Guide - Backup and Archiving
      • Quick Guide - Call Recording kit installation
      • Quick Guide - Restore or Migration
      • Quick Guide - Upgrading
      • Quick Guide - User Interface
    • Adutante Server
      • General Administration
        • Guest Tab
        • Modules Tab
        • Tools Tab
        • Users Tab
      • Adutante - QC Modules
        • Evaluate Tab
        • Evaluation History Tab
        • QC Admin Module - Permissions Tab
        • QC Forms Tab
        • QC Reports Tab
        • Review Tab
      • Adutante - Recorders Modules
        • Call Center Seating Tab
        • Recorders Admin - Call Center Tab
        • Recorders Admin - Module Permissions Tab
        • Recorders Admin - Recorder Permissions Tab
        • Recorders Admin - Recorders Tab
        • Recorders Tab
        • Recordings Tab - Obsolete
      • How to Add VSLogger to Adutante
    • Tips, Best Practices, Troubleshooting
      • Authentication and Active directory Integration
      • About Screen Capture
      • Adutante vs. VSLogger
      • Frequently Asked Questions (FAQ)
      • Known Issues
      • Languages and Translations
      • SSL Certificates
      • Support plan has expired and License not activated messages
      • User Functionality Configuration Samples
      • Wireshark: How to Capture VoIP Traffic
    • VSLogger Server
      • Configure Hardware and Channels
        • Analog Channels
        • Common Parameters and VOX
        • D-Channel events
        • Digital PBX Channels
        • Passive VOIP
        • Passive VOIP Channels
        • T1, E1, ISDN PRI Channels
        • Terminating IPCAST Channels
        • Terminating IPCAST(Unicast/Multcast) HW
        • Terminating VOIP Channels
        • Terminating VOIP HW
        • VOIP Trunk Channels
        • Verification Channels
        • Virtual HW and Channels / Recordings Replication
      • VSLogger Monitor UI
        • VSLogger Monitor - Setup Tab
          • Desktop Assistant (DTA) Administration
          • Storage and Archives section
          • System/License Activation section
        • Dashboard Tab
        • Links Tab
        • Live Monitoring Tab
        • Recorder Reports Tab
        • Search and Playback Tab 4.7.1
        • Search and Playback Tab 4.7.2+
      • General Configuration
        • Adutante Registration
        • Alarms Configuration, rev. 4.9.1 and earlier
        • Alarms Configuration, rev. 4.9.2 and after
        • Connection Service / Netserver
        • Licensing Configuration
        • Logs Configuration
        • Recording Filters
        • SMDR Configuration
        • SMTP Settings
        • Storage and Archives
        • T1 E1 Signaling Schemes
        • Vaults and Encryption
      • VSLogger API
        • VSLogger Call Recording Engine
        • VSLogger HTML API
      • VSLogger CLI Tool Overview
        • DB Maintenance Utilities
        • File converter
      • Avaya TSAPI DMCC recording
      • Cisco BIB /JTAPI Configuration
      • Cisco BIB SIP/TLS SIP trunk configuration
      • Desktop Assistant
      • Hardware Drivers
      • Microsoft Teams Recording
      • Mitel SRC (Secure Recording Connector)/ Mitel OIG CTI Configuration
      • Voice Analytics features and providers
    • Supported Providers and PBX/Phone Models
  • Français (French) - A propos de VSLogger
    • Adutante Server
      • Adutante - Modules généraux
        • Administration Générale – L’Onglet Hôtes
        • Administration Générale – L’Onglet Modules
        • Administration Générale – L’Onglet Outils
        • Administration Générale – L’Onglet Utilisateurs
      • Adutante - Modules QC
        • Administration QC – L’Onglet Module des Autorisations
        • Les Formulaires QC
        • L’Anglet Examen
        • L’Onglet d’Evaluation QC
        • L’anglet Rapports
        • L’historique de l’évaluation
      • Adutante - Enregistreurs Modules
        • Admin. Enregistreurs | L’Onglet Enregistreurs
        • Admin. Enregistreurs | L’Onglet du Centre d’Appels
        • Admin. Enregistreurs | Onglet Autorisations Enregistreur
        • Admin. Enregistreurs | Onglet des Autorisations Module
        • L’Onglet des Enregistrements - Obsolète
        • L’Onglet des Enregistreurs
        • L’onglet Siège
      • Comment ajouter ou supprimer un Enregistreur
    • VSLogger Server
      • À propos de l'outil CLI de VSLogger
        • DB Maintenance Utilities
        • À propos du convertisseur de fichiers
      • config hw | Matériel
        • Virtual HW et canaux. Réplication d'enregistrements.
        • config channel | Paramètres communs
        • config channel | Canaux de ligne tronc SIP
        • config channel | Configuration de canal T1/E1/ISDN PRI
        • config channel | Configuration de canal analogique
        • config channel | La Configuration du canal PBX numérique
        • config channel | La Configuration du canal de VOIP Passif
        • config channel | Les Evènements D-Channel
        • config channel | Terminant(active) les canaux VOIP
        • config channel | canaux de Vérification
        • config hw siprec | VoIP (terminant) active
        • config hw voip | VOIP Passive
      • config general | Configuration générale
        • config adutante | Inscription avec Adutante
        • config alarms | Configuration des alarmes
        • config filters | Filtres d'enregistrement
        • config license | Configuration des licences
        • config logging | Configuration des journaux
        • config netserver | Service de connexion
        • config smdr | Configuration SMDR
        • config smtp | Paramètres SMTP
        • config storage | Stockage et archives
        • config t1e1 | Systèmes de signalisation T1 E1
      • À propos de l'API VSLogger (interface du programme d'application)
        • Moteur d'enregistrement d'appel VSLogger
        • VSLogger HTML API
      • A propos de VSLogger Monitor
        • Le Moniteur VSLogger – L’onglet de configuration
          • Administration Assistant de bureau (DTA)
          • Section Activation système et licence
          • Section Stockage et Archives
        • Le Moniteur VSLogger – L’Onglet Tableau de Bord
        • Le Moniteur VSLogger – L’Onglet de supervision en direct
        • Le Moniteur VSLogger – l’Onglet Rapports
        • Le Moniteur VSLogger- Les onglet Recherche et Lecture
        • Onglet Recherche et lecture (4.7.2+)
      • Enregistrement des téléphones Cisco BIB ( built-in-bridge)
      • Pilotes de matériel
      • Configuration du lien JTAPI
      • L’Assistant de Bureau
    • FAQ, meilleures pratiques, astuces, dépannage
      • A propos de la capture d'écran
      • Les Langues et Les Traductions
      • Les certificats SSL
      • Récapitulation de la différence entre Adultante et VSLogger
      • Utilisateur exemples de configuration de la fonctionnalité
    • Démarrage rapide - Kit de enregistrement
    • Démarrage rapide - Mise à niveau
    • Démarrage rapide - Système enregistreur
    • PBX et modèles de téléphone pris en charge par les enregistreurs d'appels Versadial
  • Español (Spanish) - Sobre VSLogger
    • Adutante Server
      • Adutante - Módulos generales
        • Administración General | Pestaña de Módulos
        • Pestaña de Herramientas
        • Pestaña de Invitado
        • Pestaña de Usuarios
      • Adutante - Módulos CC (control de calidad)
        • Formularios de Control de Calidad
        • Historial de Evaluación
        • Pestaña de Evaluación de Control de Calidad
        • Pestaña de Informes
        • Pestaña de Revisión
        • QC Admin | Pestaña de Permisos de Módulo
      • Adutante - Módulos de Grabadores
        • Admin. de Grabadores | Pestaña de Centro de Atención Telefónica
        • Admin. de Grabadores | Pestaña de Grabadores
        • Admin. de Grabadores | Pestaña de Permisos de Grabador
        • Admin. de Grabadores | Pestaña de Permisos del Módulo
        • Centro de llamadas
        • Pestaña de Grabaciones
        • Pestaña de Grabadores
      • Cómo agregar un Grabador al Sistema de Grabación Distribuida
    • VSLogger Server
      • Acerca de la herramienta CLI de VSLogger
        • Acerca de las Utilidades de Mantenimiento de Base de Datos
        • Acerca del convertidor de archivos
      • config hw | configurar el Hardware de VSLogger
        • Virtual HW y Canales. La replicación.
        • config channel | Canales T1, E1, ISDN PRI
        • config channel | Canales de grabación de llamadas de verificación
        • config channel | Canales de troncales SIP
        • config channel | Configuración activa del canal VOIP
        • config channel | Configuración del canal analógico
        • config channel | Configuración pasiva de canal VOIP
        • config channel | Eventos D-Canal
        • config channel | Parámetros de canal comunes a todos los tipos de canal
        • config channel |Configuración del canal digital
        • config hw siprec | Configuración activa de VOIP
        • config hw voip | Configurar la grabación VOIP pasiva
      • config general | Configuración general
        • config adutante | Adutante Registro
        • config alarms | Configuración de Alarmas
        • config filters | Configuración de los filtros de grabación
        • config license | Configuración de Licencias
        • config logging | Configuración de Registros
        • config netserver | Configuración del Servicio de Conexión
        • config smdr | Configuración SMDR
        • config smtp | Configuración de SMTP
        • config storage |Configuración de Archivos y Almacenamiento
        • config t1e1 | Configurar esquema de señalización CAS T1 o E1
      • Acerca de API VSLogger
        • Motor de grabación de llamadas VSLogger
        • VSLogger HTML API
      • Acerca del Monitor de VSLogger
        • Pestaña de Configuración
          • Administración de Asistente de escritorio (DTA)
          • Sección Almacenamiento y Archivos
          • Sección de activación de sistema y licencia
        • Pestaña de Búsqueda y Reproducción
        • Pestaña de Búsqueda y Reproducción 4.7.2+
        • Pestaña de Informes
        • Pestaña de Monitoreo en Vivo
        • Tablero
      • Acerca del hardware Controladores
      • Asistente de Escritorio de VSLogger
      • Configuración de JTAPI Enlace a la grabadora de llamadas
      • Grabación de los teléfonos Cisco BIB (built-in-bridge)
    • Preguntas, mejores prácticas, consejos, Solución de problemas
      • Acerca de la captura de pantalla
      • Adutante contra VSLogger
      • Certificados SSL
      • Idiomas y Traducciones
      • Usuario muestras de configuración Funcionalidad
    • Inicio rápido - Actualización
    • Inicio rápido - Kit de grabación
    • Inicio rápido - Sistema completo
    • PBX y modelos de teléfono compatibles con grabadoras de llamadas Versadial
  • Português (Portuguese) - Sobre a gravação de chamadas do VSLogger
    • PBX e modelos de telefone suportados por gravadores de chamadas Versadial
  • العربية (Arabic) - حول VSLogger تسجيل المكالمات
    • Versadial مقسم الهاتف ونماذج بدعم من مسجلات نداء

D-Channel Events

D- Channel Events are special events available on digital PBX recording boards such as SmartWorks NGXXXX and Synway DSTXXXX series.

Digital telephone sets often have multiple controls: buttons, LEDs and menu displays.  D-Channel Events correspond to activities or state changes of those controls:  light on, button press, feature selected, light flashing etc.

Considering the multitude of different events generated on these boards, the recorder is expected to handle different combinations of these events to execute specific actions e.g. Start Stop recording.  To achieve this,  D-Channel events configuration of VSLogger is organized as D-Channel Event Sets, with expected events, conditions, and corresponding actions.

CLI (Command Line Interface)

  GUI (Graphical User Interface)

To access D-Channel Event sets configuration 

cli>(config)
->channel 1 evtsets
add evtset [1-5] - add d-channel event
remove evtset [1-5] - remove d-channel event
evtset [1-5] - d-channel events set configuration mode
show - show current configuration
stopby [first|last|all|any] - stop recording by set
exit - exit configuration mode
cli>(config-ch_1-evtsets)

 

Each channel includes up to 5 event sets.

Each event set includes 1-N d-ch events  (see  CLI (config channel evtsets eventset_1 ) list command  for available event ids)

To process stop recording, it is often important to know what event set triggered start recording. For this, there are four options available for triggering "stop recording" event action, see  stopby [first|last|all|any] parameter.

  • first - first activated events set. Trigger "Stop Recording" action only, if it was received from the first event set responsible for triggering "Start Recording".
  • last - last activated events set. Trigger "Stop Recording" action only if it was received from the last event set responsible for triggering "Start Recording".
  • all - all activated events set. Trigger "Stop Recording" action only if it was received from all event sets responsible for triggering "Start Recording".
  • any - any activated event sets. Trigger "Stop Recording" action, if it was received from any event set responsible for triggering "Start Recording".

 

  1) Navigate to Setup -> Channels -> Edit selected channel, then scroll to the "D-Channel Event Sets"
2) Click on the blue "Add" button to create an event set
3) The newly created event set will appear
4) Click on the + button on the event set to begin configuration
Gallery: dchan-1

Configure D-Channel set 

cli>(config-ch_1-evtsets)
->evtset 1
add evt [1-n] [id] - add d-channel event
remove evt [1-n] - remove d-channel event
evt [1-n] - d-channel events configuration mode
list - d-channel events list
show - show current configuration
exit - exit configuration mode
cli>(config-ch_1-evtsets-evtset_1)

->show
[1] evtset
{
[1] evt [offhook]
actions:
[1] start

[2] evt [onhook]
actions:
[1] stop

[3] evt [release_btn_pressed]
actions:
[1] stop

}

 

  1) Select event
2) Select action to perform
3) Click Add
4) The newly created event and action will appear
5) Submit event
Gallery: dchan-2

6) Repeat similar steps to configure "STOP" when "ONHOOK" event
7) The event actions should be displayed below the event set
Gallery: dchan-3

Use list command  for available event ids

cli>(config-ch_1-evtsets-evtset_1)
->list
0 func_btn_pressed
1 func_btn_released
2 light_off
3 light_on
4 light_flashing
5 light_fastflashing
6 audio_change
7 offhook
8 onhook
9 release_btn_pressed
10 release_btn_released
11 speaker_btn_pressed
12 speaker_btn_released
13 hold_btn_pressed
14 hold_btn_released
15 transf_btn_pressed
16 conf_btn_pressed
17 conf_btn_released
18 feature_btn_pressed
19 exit_btn_pressed
20 exit_btn_released
21 line_btn_pressed
22 mic_btn_pressed
23 mic_btn_released
24 intercom_btn_pressed
25 intercom _btn_released
26 light_quick_flash
27 light_very_fastflashing
28 line_light_off
29 line_light_on
30 line_light_flashing
31 line_light_fastflashing
32 line_light_very_fastflashing
33 line_light_quickflash
34 feature_light_off
35 feature_light_on
36 feature_light_flashing
37 feature_light_fastflashing
38 feature_light_very_fastflashing
39 feature_light_quickflash
40 speaker_light_off
41 speaker_light_on
42 speaker_light_flashing
43 speaker_light_fastflashing
44 speaker_light_very_fastflashing
45 speaker_light_quickflash
46 mic_light_off
47 mic_light_on
48 mic_light_flashing
49 mic_light_fastflashing
50 mic_light_very_fastflashing
51 mic_light_quickflash
52 hold_light_off
53 hold _light_on
54 hold _light_flashing
55 hold _light_fastflashing
56 hold _light_very_fastflashing
57 hold _light_quickflash
58 release_light_off
59 release_light_on
60 release_light_flashing
61 release_light_fastflashing
62 release_light_very_fastflashing
63 release_light_quickflash
64 transf_light_off
65 transf_light_on
66 transf_light_flashing
67 transf_light_fastflashing
68 transf_light_very_fastflashing
69 transf_light_quickflash
70 conf_light_off
71 conf_light_on
72 conf_light_flashing
73 conf_light_fastflashing
74 conf_light_very_fastflashing
75 conf_light_quickflash
76 intercom_light_off
77 intercom_light_on
78 intercom_light_flashing
79 intercom_light_fastflashing
80 intercom_light_very_fastflashing
81 intercom_light_quickflash
82 isdn_bri_call_alerting
83 isdn_bri_call_connected
84 isdn_bri_call_released
85 isdn_bri_call_suspended
86 isdn_bri_call_resumed
87 isdn_bri_call_held
88 isdn_bri_call_retrieved
89 isdn_bri_call_abandoned
90 isdn_bri_call_rejected
91 message_change

cli>(config-ch_1-evtsets-evtset_1)

 

   

Finding your individual D-Channel events per call pattern

VSLogger CLI provides a method (debug command) which allows to review events detected during the test call on a specific phone.

If  phone models, styles of calling (call patterns: handset, headset, speakerphone), are identical for all recorded phones – then you have only one test to do. Otherwise, (the more likely scenario) you’ll need to test each phone model and call pattern individually.

To make process simple we recommend to test a single channel (recorded phone) and record  events for a brief (5 to 10 second) test call.

In the example below, there will be 3 call patterns for single handset model connected to recorder channel 16. We'll explain other possibilities, and the logic involved in selecting an event, or set of events. 

Events from other phones ( channels ) have been removed.
Comments marked  as ***** COMMENT*****

To view events,  open the CLI and enabled debug mode.

cli>
->debug enable y
<enter>
cli>(debug)
->level shcti 8 (for Synway)
->level smart 8 (for Audio Codes)

Now, if you'll make a call on the telephone connected to the selected hardware, you’ll see corresponding events…

To end the test type exit.

 

   

Test 1, using handset only (significant events listed):

cli>
->debug level shcti 8
cli>(debug)
*****Call Start*****
2015-05-01 15:18:43.784 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_OFFHOOK (0x8)
2015-05-01 15:18:43.913 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_AUDIO_CHG (0x104a) Subreason 0x7 XtraInfo 0x7 audio: 7
*****Call End*****
2015-05-01 15:18:54.037 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_ONHOOK (0xe)
2015-05-01 15:18:54.161 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_AUDIO_CHG (0x104a) Subreason 0x4 XtraInfo 0x4 audio: 4
->exit 

   

Test 2, using headset only (significant events listed):

cli>
->debug level shcti 8
 
cli>(debug)
*****Call Start*****
2015-05-01 15:15:53.747 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_OFFHOOK (0x8)
2015-05-01 15:15:53.872 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_AUDIO_CHG (0x104a) Subreason 0x7 XtraInfo 0x7 audio: 7
*****Call End*****
2015-05-01 15:16:12.888 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_ONHOOK (0xe)
2015-05-01 15:16:13.007 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_AUDIO_CHG (0x104a) Subreason 0x4 XtraInfo 0x4 audio: 4
->exit

   

Test 3, using speaker only (significant events listed):

cli>
->debug level shcti 8
cli>(debug)
*****Call Start*****
2015-05-01 15:13:43.320 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_SPEAKER_BTN_PRS (0x1016)
2015-05-01 15:13:43.445 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_AUDIO_CHG (0x104a) Subreason 0x7 XtraInfo 0x7
audio: 7
2015-05-01 15:13:43.445 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_AUDIO_CHG (0x104a) Subreason 0xf XtraInfo 0xf
audio: f
2015-05-01 15:13:43.535 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_SPEAKER_LT_ON (0x1071) Subreason 0x0 XtraInfo 0x200
led: 0 color: red
*****Call End*****
2015-05-01 15:14:01.301 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_AUDIO_CHG (0x104a) Subreason 0xc XtraInfo 0xc
audio: c
2015-05-01 15:14:01.301 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_AUDIO_CHG (0x104a) Subreason 0x4 XtraInfo 0x4
audio: 4
2015-05-01 15:14:01.394 0 [Debug] debugger.shcti:CSHPDSTChannel::ProcessEvent(16/15) DST_SPEAKER_LT_OFF (0x1070) Subreason 0x0 XtraInfo 0x300
led: 0 color: red
->exit 

For each call pattern  we look for common triggers to use as start and stop recording events. .

Handset and Headset calls look the same:

Start – Off Hook, Audio 7

Stop – On Hook, Audio 4

 

Speaker call:

Start – Speaker button, Speaker light on, Audio 7, Audio F

Stop – Speaker light off, Audio C, Audio 4

 

In such case the suggestion would be…

1 event set:

Start – on Audio 7

Stop – on Audio 4

 

   

As other example, if test call events were different :

Handset call : On / Off Hook only

Headset call : Audio C On / Audio 0 Off

Speaker call: Light On / Off 

The  suggested configuration would be 3 sets, 1 for each type of event, and stop by last(most recent) event set.

Set 1:
On / Off Hook
Set 2:
Audio C on / Audio 0 Off
Set 3:
Speaker light or button press On / Speaker light off
Stop by: Last 

The logic of  above configuration:

If a handset answered the call (normal start).

Then, they switched to the speaker for the conference (speaker light came on).

Next, the phone was placed on hook (as they switched to the speaker).

Lastly, ending the call… (Speaker light off.)

We would get the entire recording, as the speaker light was the last set used.

 

   

Add and configure individual D-Channel events

cli>(config-ch_1-evtsets-evtset_1)
->add evt func_btn_pressed ?
add cond|act [1-n] [condition|action] - add event condition/action
set cond|act [1-n] [condition|action] - update event condition/action
remove cond|act [1-n] - remove event condition/action
show - show current configuration
exit - exit configuration mode

cli>(config-ch_1-evtsets-evtset_1-event_func_btn_pressed(0))

 

   

About Event Conditions, Actions and Event processing sequence 

Each event can contain none, one or more conditions

Each event can contain one or more actions

Events processing sequence. First matching condition, terminates processing.

For each evtsets do

if (Event  found) 

        1.  check conditions 

        2.  if matching condition found, process all event actions and exit this event processing

end if

 

   

Configure event conditions and actions

Options for conditions and actions can be displayed as below

cli>(config-ch_1-evtsets-evtset_1-event_audio_change(0))
->add cond ?
led - led condition
btn - btn condition
lookup - lookup condition
audio - audio change condition (Applied only for audio_change event)

cli>(config-ch_1-evtsets-evtset_1-event_audio_change(0))

->add act ?

start - start recording
stop - stop recording
set - set recording field
rewrite - rewrite recording field

Refer to table and samples below for more details 

 

   

 

D-ch events can be divided by following categories:

BTN events :  btn_press,  funct_btn_press .....

LED events  :   light_on, light_off, funct_light_on ....

AUDIO event :   audio_change

MESSAGE event : message_change

OTHER events (events without conditions)  : offhook, onhook, release_btn_press, trans_btn_press,  call_alerting, call_connected, call_released .....

 

D-channel event Category

Configuration commands

event edit mode level cli>(config-ch_1-evtsets-evtset_1-event_func_btn_pressed(0)

Conditions for  BTN events : 

btn_press,  funct_btn_press .....

add cond [1-n]  btn key [0-256,0-256,...]  - create new condition and insert at position  [1-n]

set cond   [1-n]  btn  key [0-256,0-256,...]  - change setting of condition at position [1-n]

remove cond [1-n]  - remove condition at position  [1-n]

Note: you can set multiple button indices(comma delimited) in single condition key parameter.

Conditions for LED events  : 

light_on, light_off, funct_light_on ....

add cond [1-n]  led key [0-256,0-256,...]  - create new condition and insert at position  [1-n]

set cond   [1-n]  led  key [0-256,0-256,...]  - change setting of condition at position [1-n]

remove cond [1-n]  - remove condition at position  [1-n]

Note: you can set multiple button indices(comma delimited) in single condition key parameter.

Actions for  BTN events : 

btn_press,  funct_btn_press .....

and 

Actions for  LED events : 

light_on, light_off, funct_light_on ....

add act [1-n]  start key [0-256] field [callerid|dialed|note|sessionid|extension|direction] val []  ref [] - create new action and insert at position  [1-n]

set act [1-n] start key [0-256] field [callerid|dialed|note|sessionid|extension|direction] val []  ref [] - change settings of action at position [1-n]

add act [1-n]  set key [0-256] field [callerid|dialed|note|sessionid|extension|direction] val [] - create new action and insert at position  [1-n]

set act   [1-n] set key [0-256] field  [callerid|dialed|note|sessionid|extension|direction] val [] - change settings of action at position [1-n]

add act [1-n]  stop key [0-256] field [callerid|dialed|note|sessionid|extension|direction] val [] ref []- create new action and insert at position  [1-n]

set act   [1-n] stop key [0-256] field  [callerid|dialed|note|sessionid|extension|direction] val [] ref []- change setting of action at position [1-n]

remove act [1-n]  - remove condition at position  [1-n]

Note: you can select none or single button index in in action key parameter.  So you might have single condition true for several buttons, and several separate actions for those buttons

 

Conditions for MESSAGE event : message_change

 

add cond [1-n]  lookup key [value | regExp] opr [eq|noteq|contain|notcontain|match|notmatch]  - create new condition and insert at position  [1-n]

set cond   [1-n]  lookup key [value | regExp] opr [eq|noteq|contain|notcontain|match|notmatch] - change setting of condition at position [1-n]

remove cond [1-n]  - remove condition at position  [1-n]

see message_change Event  parameter notes 

Actions for MESSAGE event : message_change

add act [1-n] rewrite key [regExp]  field [callerid|dialed|note|sessionid|extension|direction] val [$1] - create new action and insert at position  [1-n]

set act   [1-n] rewrite key [regExp] field [callerid|dialed|note|sessionid|extension|direction]  val [$1] - change setting of action at position [1-n]

add act [1-n]  set  field [callerid|dialed|note|sessionid|extension|direction] val [] - create new action and insert at position  [1-n]

set act   [1-n] set  field  [callerid|dialed|note|sessionid|extension|direction] val [] - change settings of action at position [1-n]

remove act [1-n]  - remove condition at position  [1-n]

see message_change Event  parameter notes 

Conditions for  AUDIO event :   

audio_change 

 

add cond [1-n]  audio trans from [0x0-0xf] to [0x0-0xf]  - create new condition and insert at position  [1-n]

set cond   [1-n]  audio trans from [0x0-0xf] to [0x0-0xf] - change setting of condition at position [1-n]

remove cond [1-n]  - remove condition at position  [1-n]

Note:  audio change values can be detected and tested with driver provided tools e.g. SmartTap Even viewer. Values used for from and to parameters are corresponding values of AUDIO_CHANGE event

trans - (optional), transition from to
from - audio change value [0x0-0xf]
to - (optional) transition to audio change value [0x0-0xf], needed only if trans parameter present

see  audio_change Event  parameter notes below

Actions for  AUDIO event :   

audio_change 

 

add act [1-n]  start  field [callerid|dialed|note|sessionid|extension|direction] val []  ref []- create new action and insert at position  [1-n]

set act   [1-n] start  field [callerid|dialed|note|sessionid|extension|direction] val []  ref [] - change setting of action at position [1-n]

add act [1-n]  set  field [callerid|dialed|note|sessionid|extension|direction] val [] - create new action and insert at position  [1-n]

set act   [1-n] set  field  [callerid|dialed|note|sessionid|extension|direction] val [] - change

setting of action at position [1-n]

add act [1-n]  stop  field [callerid|dialed|note|sessionid|extension|direction] val [] ref []- create new action and insert at position  [1-n]

set act   [1-n] stop  field  [callerid|dialed|note|sessionid|extension|direction] val [] ref []- change setting of action at position [1-n]

remove act [1-n]  - remove condition at position  [1-n]

 

Actions for OTHER events: offhook, onhook, release_btn_press, trans_btn_press,  call_alerting, call_connected, call_released .....

 

add act [1-n]  start  field [callerid|dialed|note|sessionid|extension|direction] val []  ref []- create new action and insert at position  [1-n]

set act   [1-n] start  field [callerid|dialed|note|sessionid|extension|direction] val []  ref [] - change setting of action at position [1-n]

add act [1-n]  set  field [callerid|dialed|note|sessionid|extension|direction] val [] - create new action and insert at position  [1-n]

set act   [1-n] set  field  [callerid|dialed|note|sessionid|extension|direction] val [] - change

setting of action at position [1-n]

add act [1-n]  stop  field [callerid|dialed|note|sessionid|extension|direction] val [] ref []- create new action and insert at position  [1-n]

set act   [1-n] stop  field  [callerid|dialed|note|sessionid|extension|direction] val [] ref []- change setting of action at position [1-n]

remove act [1-n]  - remove condition at position  [1-n]

Note: These events do not have conditions

 

CLI (Command Line Interface)

GUI (Graphical User Interface)

Using ref parameter

Parameter ref can be used to associate start and stop events within the same event set.  For example, if you have several start events and several stop events and you want to use specific stop only if recording started with specific start. 

Starts: event1 start ref 1 ,  event3 start ref 2 ,  event3 start ref 3

Stops: event4 stop ref 1 ,  event5 stop ref 2 ,  event6 stop ref 3

Gallery: dchan-4

Sample configurations

Scenario 1 :   

  • Start recording on  "offhook" event
  • Stop recording on  "onhook"  event

add event and start activity 

cli>(config-ch_9-evtsets-evtset_1)
->add evt offhook
cli>(config-ch_9-evtsets-evtset_1-event_offhook(7))
->add act start 

 

return to event set configuration mode

cli>(config-ch_9-evtsets-evtset_1-event_offhook(7))
->exit
cli>(config-ch_9-evtsets-evtset_1)
->add evt onhook
cli>(config-ch_9-evtsets-evtset_1-event_onhook(8))
->add act stop

return to event set configuration mode and display setting

cli>(config-ch_9-evtsets-evtset_1-event_onhook(8))
->exit
cli>(config-ch_9-evtsets-evtset_1)
->show
[1] evtset
{
[1] evt [offhook]
actions:
[1] start
[2] evt [onhook]
actions:
[1] stop
}

1) Configuration of "Start recording on  'offhook' event"
Gallery: dchansc1

2) Configuration of "Stop recording on  'onhook'  event"
Gallery: dchansc2

3) The event actions will be displayed below the event set
Gallery: dchansc3

Scenario 2:   

  • Start recording on channel 2 on "audio_change" event , if audio = 8 
  • Stop recording on channel 2 on "audio_change"  event, if audio = 0

Note : audio change parameters from and to accept values in hex format (both 10 or 0x10 will be accepted as hex 10 ( 16 decimal) ). see  audio_change Event  parameter notes below

cli>(config)ch 2

cli>(config-ch_2) evtsets

cli>(config-ch_2-eventsets)add evtset 1

cli>(config-ch_2-eventsets-evtset_1)add evt audio_change

cli>(config-ch_2-eventsets-evtset_1-evt_audio_change)add cond audio from 8

cli>(config-ch_2-eventsets-evtset_1-evt_audio_change)add act start

cli>(config-ch_2-eventsets-evtset_1-evt_audio_change)exit

cli>(config-ch_2-eventsets-evtset_1)add evt audio_change

cli>(config-ch_2-eventsets-evtset_1-evt_audio_change)add cond audio from 0

cli>(config-ch_2-eventsets-evtset_1-evt_audio_change)add act stop

cli>(config-ch_2-eventsets-evtset_1)show

->show
[1] evtset
{
[1] evt [audio_change]
conditions:
[1] audio from 8
actions:
[1] start

[2] evt [audio_change]
conditions:
[1] audio from 0
actions:
[1] stop

}

1) Configuration of "Start recording on "audio_change" event , if audio = 8"
Gallery: dchan-5

2) Configuration of "Stop recording on "audio_change"  event, if audio = 0"
Gallery: dchan-6

3) The event actions will be displayed below the event set
Gallery: dchan-7



Scenario 3:   

  • Start recording on channel 2 on "audio_change"  event, if audio transition from=3 to=8
  • Stop recording on channel 2 on "audio_change" event, if  audio = 0

Note : audio change parameters from and to accept values in hex format (both 10 or 0x10 will be accepted as hex 10 ( 16 decimal) ) see  audio_change Event  parameter notes below

 

cli>(config-ch_2-eventsets-evtset_1)add evt audio_change

cli>(config-ch_2-eventsets-evtset_1-evt_audio_change)add cond audio trans from 3 to 8  

cli>(config-ch_2-eventsets-evtset_1-evt_audio_change)add act start

cli>(config-ch_2-eventsets-evtset_1-evt_audio_change)exit

cli>(config-ch_2-eventsets-evtset_1)add evt audio_change

cli>(config-ch_2-eventsets-evtset_1-evt_audio_change)add cond audio from 0

cli>(config-ch_2-eventsets-evtset_1-evt_audio_change)add act stop

cli>(config-ch_2-eventsets-evtset_1-evt_func_btn_pressed)exit

cli>(config-ch_2-eventsets-evtset_1)show

 

->show
[1] evtset
{
[1] evt [audio_change]
conditions:
[1] audio trans from 3 to 8
actions:
[1] start

[2] evt [audio_change]
conditions:
[1] audio from 0
actions:
[1] stop

}

1) Configuration of "Start recording on "audio_change"  event, if audio transition from=3 to=8"
Gallery: dchan-8

2) Configuration of "Stop recording on "audio_change" event, if  audio = 0"
Gallery: dchan-6

3) The event actions will be displayed below the event set
Gallery: dchan-9

Scenario 4:   

  • Start recording  on "func_btn_pressed" event, if  buttons numbers = 1 or 3 or 5 or 7  
  • Update "note" field with value "btn1" , if  button number = 1
  • Update "note" field with value "btn2",  if  button number = 2
  • Stop recording  on "func_btn_pressed"  event,  if  button number = 2 or 4 or 6


cli>(config-ch_2-eventsets-evtset_1)add evt func_btn_pressed

cli>(config-ch_2-eventsets-evtset_1-evt_func_btn_pressed)add cond btn key 1,3,5,7

cli>(config-ch_2-eventsets-evtset_1-evt_func_btn_pressed)add act start

cli>(config-ch_2-eventsets-evtset_1-evt_func_btn_pressed)add act set field note val btn1 key 1 

cli>(config-ch_2-eventsets-evtset_1-evt_func_btn_pressed)exit

cli>(config-ch_2-eventsets-evtset_1)add evt func_btn_pressed

cli>(config-ch_2-eventsets-evtset_1-evt_func_btn_pressed)add cond btn key 2,4,6

cli>(config-ch_2-eventsets-evtset_1-evt_func_btn_pressed)add act set field note val btn2 key 2 

cli>(config-ch_2-eventsets-evtset_1-evt_func_btn_pressed)add act stop

cli>(config-ch_2-eventsets-evtset_1-evt_func_btn_pressed)exit

cli>(config-ch_2-eventsets-evtset_1)show

[1] evtset
{

[1] evt [func_btn_pressed]

conditions:
[1] btn key 1,3,5,7
actions:
[1] start
[2] set field note val btn1 key 1 

[4] evt [func_btn_pressed]
conditions:
[1] btn key 2,4,6
actions:
[1] set field note val btn2 key 2 
[2] stop

}

1) Configuration of "Start recording  on "func_btn_pressed" event, if  buttons numbers = 1 or 3 or 5 or 7"
Gallery: dchan-10

2) Configuration of "Update "note" field with value "btn1" , if  button number = 1"
Gallery: dchan-11

3) Configuration of "Update "note" field with value "btn2",  if  button number = 2"
Gallery: dchan-12

4) Configuration of "Stop recording  on "func_btn_pressed"  event,  if  button number = 2 or 4 or 6"
Gallery: dchan-13

5) The event actions will be displayed below the event set
Gallery: dchan-14

Scenario 5:   

  • Start recording on channel 2 on "light_on" event,  if led number = 1 or 3 or 5 and  led color is red  
  • Stop recording on channel 2 on "light_off" event,  if led number = 1 or 3 or 5 

cli>(config-ch_2-eventsets-evtset_1)add evt light_on

cli>(config-ch_2-eventsets-evtset_1-evt_light_on)add cond led key 1,3,5 color red

cli>(config-ch_2-eventsets-evtset_1-evt_light_on)add act start

cli>(config-ch_2-eventsets-evtset_1-evt_light_on)exit

cli>(config-ch_2-eventsets-evtset_1)add evt light_off

cli>(config-ch_2-eventsets-evtset_1-evt_light_off)add cond led key 1,3,5

cli>(config-ch_2-eventsets-evtset_1-evt_light_off)add act stop

cli>(config-ch_2-eventsets-evtset_1-evt_func_btn_pressed)exit

cli>(config-ch_2-eventsets-evtset_1)show

->show
[1] evtset
{
[1] evt [light_on]
conditions:
[1] led key 1,3,5 color red
actions:
[1] start

[2] evt [light_off]
conditions:
[1] led key 1,3,5
actions:
[1] stop

}

 

1) Configuration of "Start recording on "light_on" event,  if led number = 1 or 3 or 5 and  led color is red"
Gallery: dchan-15

2) Configuration of "Stop recording on "light_off" event,  if led number = 1 or 3 or 5"
Gallery: dchan-16

3) The event actions will be displayed below the event set
Gallery: dchan-17

Scenario 6:   

  • Update "note" field with value "Agent1" on channel 2 on "message_change" event, if message contains  text "AGENT"  

cli>(config-ch_2-eventsets-evtset_1)add evt message_change

cli>(config-ch_2-eventsets-evtset_1-evt_message_change)add cond lookup  key AGENT opr contain

cli>(config-ch_2-eventsets-evtset_1-evt_message_change)add act set field note val Agent1

cli>(config-ch_2-eventsets-evtset_1-evt_message_change)exit

li>(config-ch_2-eventsets-evtset_1)show

->show
[1] evtset
{
[1] evt [message_change]
conditions:
[1] lookup key AGENT opr contain
actions:
[1] set field note val Agent1

}

1) Configuration of "Update "note" field with value "Agent1" on channel 2 on "message_change" event, if message contains  text "AGENT""
Gallery: dchan-18

2) The event action will be displayed below the event set
Gallery: dchan-19

Scenario 7:   

  • Update "callerid" field with regExp2 property $1 , on "message_change" event, which match regExp1 message contains  text "AGENT"  

This example intended for advanced users familiar with regular expressions. Some VSLogger CLI parameters support Regular expressions based on PCRE, the Perl Compatible Regular Expressions library by Philip Hazel (see http://www.pcre.org)

For more information, see message_change Event  parameter notes 

 

cli>(config-ch_2-eventsets-evtset_1)add evt message_change

cli>(config-ch_2-eventsets-evtset_1-evt_message_change)add cond lookup  key RegExp1 opr match

cli>(config-ch_2-eventsets-evtset_1-evt_message_change)add act rewrite key regExp2 field callerid val $1

cli>(config-ch_2-eventsets-evtset_1-evt_message_change)exit

li>(config-ch_2-eventsets-evtset_1)show

->show
[1] evtset
{
[1] evt [message_change]
conditions:
[1] lookup key RegExp1 opr match
actions:
[1] set field callerid val $1 key regExp2

}

 

1) Configuration of "Update "callerid" field with regExp2 property $1 , on "message_change" event, which match regExp1 message contains  text "AGENT""
Gallery: dchan-20

2) The event action will be displayed below the event set
Gallery: dchan-21

message_change Event  parameter notes 

cli>(config-ch_9-evtsets-evtset_1-event_message_change(91))
->add cond lookup ?
lookup key [] opr []
key - lookup value/regexpr pattern
opr - lookup operator (eq/noteq,contain/notcontain,match/notmatch)

cli>(config-ch_9-evtsets-evtset_1-event_message_change(91))

->add act ?
start - start recording
stop - stop recording
set - (d-channel only), set recording field
rewrite - (d-channel only), rewrite recording field

cli>(config-ch_9-evtsets-evtset_1-event_message_change(91))

->add action rewrite ?
key [] - (d-channel only), regexp pattern
field [] - (d-channel only), set recording field: callerid,dialed,note,sessionid,extension,direction
val [] - (d-channel only), replacement pattern ($1...$9)
cli>(config-ch_9-evtsets-evtset_1-event_message_change(91)) 

Note: Some VSLogger CLI parameters support Regular expressions based on PCRE, the Perl Compatible Regular Expressions library by Philip Hazel (see http://www.pcre.org)

Message-change event corresponds to Telephone display text changes and can happen multiple times during the call.  

The event contains new text applied to telephone display at a specific moment and this text can be creatively used with VSLogger conditions and actions.

 

Basically programming of message_change events includes two steps;

  1. Create an Event condition based on RegularExpression1  to detect phone display containing specific information 
  2. Create the corresponding action, which will use RegularExpression2 to retrieve required information from the display text and apply it to the recording field

Create conditions without regular expressions:

  • add cond lookup  key KEY_TEXT opr eq  -  Display message equals to KEY_TEXT
  • add cond lookup  key KEY_TEXT opr noteq  -  Display message not equals to KEY_TEXT
  • add cond lookup  key KEY_TEXT opr contain  -  Display message contains  KEY_TEXT
  • add cond lookup  key KEY_TEXT opr notcontain  -  Display message does not contain KEY_TEXT

Create SET actions without regular expressions:

  • add act set field [callerid,dialed,note,sessionid,extension,direction] val NEW_VALUE  -  Set selected field  with provided NEW_VALUE

Create conditions with  regular expressions:

  • add cond lookup  key RegExp1 opr match - Display message match to Regular Expression RegExpr1 
  • add cond lookup  key RegExp1 opr notmatch - Display message does not match to Regular Expression RegExpr1 

Create REWRITE actions with regular expressions:

  • add act rewrite  key RegExp1 field [callerid,dialed,note,sessionid,extension,direction] val [$1-$9]  -  Set selected field  with results of  Regular Expression RegExp2 to display text 

 

Note:  When you create a regular expression you have the option of capturing portions of the match and saving them as placeholders. They are numbered starting at $1.

Refer to Regular Expressions tutorials for details  

 

audio_change Event  parameter notes 

cli>(config-ch_1-evtsets-evtset_1-event_audio_change(0))

->add cond audio ?
audio trans from [] to []
trans - (optional), transition from to
from - audio change value [0x0-0xf]
to - (optional) transition to audio change value [0x0-0xf]

cli>(config-ch_1-evtsets-evtset_1-event_audio_change(0))

  

 

from and to parameters

audio_change event parameters from and to accept values in hex format (both f or 0xf will be accepted as hex f  ). Longer values 0xFF  or similar will be accepted, but only low 4 bits will be used by the program.

Bit 0 = Handset transmit (Mic)
Bit 1 = Handset receive (Spkr)
Bit 2 = Speakerphone (handsfree) transmit (Mic)
Bit 3 = Speakerphone (handsfree) receive (Spkr)
Bits 4-31 = Reserved

Per AudioCodes NGX boards documentation:  Transmit and receive are always with respect to the phone’s position. Transmit - phone to PBX, and
Receive - PBX to the phone. The following table lists all possible options. Not all states are observed with each PBX

 

Device State SPKR
RECV
SPKR
TRANS
HDSET
RECV
HDSET
TRANS
(LSB)
HEX VALUE
All devices are off 0 0 0 0 0x0000
  0 0 0 1 0x0001
  0 0 1 0 0x0002
Handset active 0 0 1 1 0x0003
  0 1 0 0 0x0004
  0 1 0 1 0x0005
  0 1 1 0 0x0006
  0 1 1 1 0x0007
  1 0 0 0 0x0008
  1 0 0 1 0x0009
Handset & SPR receive
only
1 0 1 0 0x000A
  1 0 1 1 0x000B
  1 1 0 0 0x000C
  1 1 0 1 0x000D
  1 1 1 0 0x000E
All devices are active 1 1 1 1 0x000F

 

 

 

  • MM/DD/YYYY
  • HH:MM:SSAM
  • HH:MM:SS
  • https://www.adutante.com/portal
  • 1680052270467
  • 94d345c085abcb9893920264df10fafe51b2deacb5b542953dc54a3ff69e6f03
  • f68de7f68859990131f5f9b40b56926a68b7965329b943ebde1a894b012f5387
  • ADUTANTE
  • UNKNOWN
  • Y
  • Versadial Solutions
  • N
  • Y
  • 1
Hosted by: Versadial Solutions
try_count=458
p_count=9
u_count=365
s_count=9761