Actions

Logging (VS-Operator)

From Zenitel Wiki

Revision as of 16:19, 7 November 2023 by Asle (talk | contribs)
AI.png

This article shows how to configure the logging feature in the VS-Operator.

In the VSOP Client, select Filter sets, and Add a filter set for Station, and in the Caption field assign a descriptive name to the filter set, e.g. "Journal".

Information can be logged into the onscreen journal (Show) and to disk (Log).

Configuring Filter Set "Journal" for logging. Here "Call Received" is logged when a call request is received



The text to send to the log is defined in the field Message text.

Here are some examples that can be used:

Event Text in "Message text" field Information Level Comment
On CallRequest Add Call received from %DIRA %ACAPTION Info Triggered when a Ringing Group call (or Call Request) is received
On CallRequest Remove Call from %DIRA %ACAPTION removed from queue Info Linux system files, libraries, webserver etc. (Board Support Package patch)
OnConnect Conversation with %DIRA %ACAPTION Info Other AlphaCom Daemons - rmd, m100d
OnDisconnect Conversation with %DIRA %ACAPTION ended Info Billing Software, absd, Billing Web etc
OnError Device error at %DIRA %ACAPTION Alarm Billing Software, absd, Billing Web etc
On Custom params xxx <depends on the event> Billing Software, absd, Billing Web etc
On Custom word string xxx <depends on the event> Billing Software, absd, Billing Web etc



It is possible to add parameters into this text field.

In the case of OnConnect a Message text could be:

  • Call %DIROP %DIRB
    • %DIROP will be replaced with the directory number of the station assosiated to the V-S Operator
App.STE("$SLRC W%RCO U1 W30");


Configuring Filter Set for logging



Now change the mode of operation to Operational, and verify that the RCO is triggered when clicking on the RCO icon, or alternatively when right-clicking the icon and selecting the command.