Logging (VS-Operator)
From Zenitel Wiki
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).
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 | Triggered when a call is removed from the call queue |
OnConnect | Conversation with %DIRA %ACAPTION | Info | Triggered when a conversation is established |
OnDisconnect | Conversation with %DIRA %ACAPTION ended | Info | Triggered when a conversation is terminated |
OnError | Device error at %DIRA %ACAPTION | Alarm | Triggered when a station or device is reported faulty |
On Custom params | <depends on the event> | <depends on the event> | Triggers on.... |
On Custom word string | <depends on the event> | <depends on the event> | Triggers on.... |
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");
|
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.