Actions

Difference between revisions of "Delayed Reporting of Line Errors"

From Zenitel Wiki

(→‎Reporting to station)
(→‎Configure Station Error reporting in Event Handler)
 
(29 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
{{A}}
+
{{AI}}
−
By default station errors are reported more or less instantly when the AlphaCom server looses connection to an IP Station, or if there is an error on the analog [[ASLT]] station line.
+
By default station errors are reported more or less instantly when the ICX-AlphaCom server looses communication with an IP Station, or if there is an error on the analog [[ASLT]] station line (AlphaCom only).
  
−
Sometimes it could be convenient to delay the reporting, for example if there is maintenance work in the IP network, repatching of cables etc.
+
Sometimes it could be convenient to delay the reporting, for example if there is maintenance work in the IP network, re-patching of cables etc.
  
 
This article describes how to disable the default reporting, and how to use customized error reporting using the [[Event Handler]] instead.
 
This article describes how to disable the default reporting, and how to use customized error reporting using the [[Event Handler]] instead.
Line 8: Line 8:
 
== Disable default Line Error reporting ==
 
== Disable default Line Error reporting ==
  
−
=== Reporting to station ===
+
=== Disable reporting to station ===
 
Station errors are by default sent to station on [[physical number]] 1. From AlphaPro one can disable this reporting.
 
Station errors are by default sent to station on [[physical number]] 1. From AlphaPro one can disable this reporting.
  
−
Go to the [[Exchange_%26_System_(AlphaPro)#Faults|Exchange & System > RCI > Faults window]], select '''Fault Line''' > Change, and delete MST command the '''ON Action'''.
+
Go to the [[Exchange_%26_System_(AlphaPro)#Faults|Exchange & System > RCI > Faults window]], select '''Fault Line''' > Change, and delete the [[MST_-_Mail_to_Station|MST command]] in the '''ON Action''' field.
 
[[Image:AP RCI Faults.png|thumb|500px|none|The Exchange & System > RCI > Faults window]]
 
[[Image:AP RCI Faults.png|thumb|500px|none|The Exchange & System > RCI > Faults window]]
  
 +
=== Disable reporting to System Log ===
 +
Station errors are by default sent to the [[System log]]. From AlphaPro one can disable this reporting.
  
−
'''Fault cases:'''
+
Go to the [[Exchange_%26_System_(AlphaPro)#Logs_and_Errors|Exchange & System > System > Logs and Errors window]]. Under "System Log", uncheck '''Line Error'''.
−
* '''Faulty Line''': Triggered when there is a station error. All types of stations (IP Stations, SIP phones, analog [[ASLT]] stations and [[ATLB-12]] phones) are monitored and reported
 
−
* '''Faulty Board''': Triggered if there is an error on one of the AlphaCom feature boards [[ASLT]], [[ATLB-12]], [[AGA]] or [[ASVP]].
 
−
* '''Faulty Device''': Triggered if there is communication error between AlphaCom and a [[RIO|RIO unit]], or between AlphaCom Master Module and a Slave Module in a [[MultiModule|MultiModule system]]
 
−
* '''Faulty AGA Line''': Triggered if there is an error on an analog AGA line between AlphaCom servers in [[AlphaNet]] or [[MultiModule]]
 
  
−
* '''Description''': Any describing text. Note that this text is not transferred to the AlphaCom server. It is stored locally on the PC only.
+
[[Image:AP LogsAndErrors.png|thumb|500px|The Exchange & System > System > Logs and Errors window|none]]
  
−
* '''ON Action''': Enter the action command to take place when the specified fault occurs. It is possible to have several commands separated by semicolons <;>. Maximum 40 characters. If this is not sufficient the data command [[EVENT_REPORT|$ER]] can be used to trigger an event in the event handler, and the actual commands can be executed there.
 
−
** The default "ON Action" will send the fault reports to station 1.
 
−
** '''MST 1 0 28''' means:
 
−
*** [[MST - Mail to Station|MST]] = Mail to STation
 
−
*** 1 = Physical number of station to receive the error report
 
−
*** 0 = Filler (always use "0")
 
−
*** 28 = Station Line error. Other codes are: 27 = Board error. 29 = Decvice error. 30 = AGA Line error.
 
−
** If the error reports should be sent to another station, simply change the first parameter. '''MST 23 0 28''' will send Station Error reports to station 23.
 
−
** If the error reporting should be removed, simply delete the text in the "ON Action" field.
 
  
−
* '''OFF Action''': Not in use.
+
== Configure Station Error reporting in Event Handler ==
 +
Station errors are reported in the [[Event Handler]] as [[Faulty Station Line (Event Type)|Event 13 - Faulty Station Line]].
 +
 
 +
When a station error is detected by ICX-AlphaCom, the event 13 goes ON. A timer can then be started. When the station error goes away, the event 13 goes OFF, and the timer is stopped. If the error is not OK within the preset time, the timer will time out, and event [[Event Timeout (Event Type)|21 - Event Timeout]] will be triggered. This event is used to generate the error reports.
 +
 
 +
[[Image:DelayedLineError1.PNG|thumb|500px|left|Start (and stop) a 60.0 second timer when Station error is detected]]
 +
<br style="clear:both;" />
 +
 
 +
{{Code2|
 +
$ST L%1.dir W%chg(600,0) L9966
 +
}}
 +
 
 +
600 means 60.0 seconds delay. Change this value according to the requirements.
 +
 
 +
 
 +
Send error message to station and to System Log:
 +
 
 +
[[Image:DelayedLineError2.PNG|thumb|500px|left|Send message to station 101, and to System Log if error is not OK within the preset time]]
 +
<br style="clear:both;" />
 +
 
 +
{{Code2|
 +
$STM L%1.dir L101 U103 'Error: %1.dir'
 +
LOG "Station Error: %1.dir %1.nam"
 +
}}
 +
 
 +
*L101 = Station to receive the error report
 +
*U103 = Priority level of the message
 +
 
 +
[[Category:AlphaCom Applications]]
 +
[[Category:ICX-AlphaCom Applications]]

Latest revision as of 13:02, 31 May 2022

AI.png

By default station errors are reported more or less instantly when the ICX-AlphaCom server looses communication with an IP Station, or if there is an error on the analog ASLT station line (AlphaCom only).

Sometimes it could be convenient to delay the reporting, for example if there is maintenance work in the IP network, re-patching of cables etc.

This article describes how to disable the default reporting, and how to use customized error reporting using the Event Handler instead.

Disable default Line Error reporting

Disable reporting to station

Station errors are by default sent to station on physical number 1. From AlphaPro one can disable this reporting.

Go to the Exchange & System > RCI > Faults window, select Fault Line > Change, and delete the MST command in the ON Action field.

The Exchange & System > RCI > Faults window

Disable reporting to System Log

Station errors are by default sent to the System log. From AlphaPro one can disable this reporting.

Go to the Exchange & System > System > Logs and Errors window. Under "System Log", uncheck Line Error.

The Exchange & System > System > Logs and Errors window


Configure Station Error reporting in Event Handler

Station errors are reported in the Event Handler as Event 13 - Faulty Station Line.

When a station error is detected by ICX-AlphaCom, the event 13 goes ON. A timer can then be started. When the station error goes away, the event 13 goes OFF, and the timer is stopped. If the error is not OK within the preset time, the timer will time out, and event 21 - Event Timeout will be triggered. This event is used to generate the error reports.

Start (and stop) a 60.0 second timer when Station error is detected


Action commands: 

$ST L%1.dir W%chg(600,0) L9966


600 means 60.0 seconds delay. Change this value according to the requirements.


Send error message to station and to System Log:

Send message to station 101, and to System Log if error is not OK within the preset time


Action commands: 

$STM L%1.dir L101 U103 'Error: %1.dir'
LOG "Station Error: %1.dir %1.nam"


  • L101 = Station to receive the error report
  • U103 = Priority level of the message
Retrieved from "https://wiki.zenitel.com/w/index.php?title=Delayed_Reporting_of_Line_Errors&oldid=228847"