Difference between revisions of "Event Timeout (Event Type)"
From Zenitel Wiki
| Line 6: | Line 6: | ||
|- | |- | ||
! align="left"|[[Event Handler#Events Types - Grouped by Function|Event type]]: | ! align="left"|[[Event Handler#Events Types - Grouped by Function|Event type]]: | ||
| − | | Event Timeout | + | | 21 - Event Timeout |
|- | |- | ||
! align="left"|[[Sub-Event (Event Handler)|Sub-Event]]: | ! align="left"|[[Sub-Event (Event Handler)|Sub-Event]]: | ||
Revision as of 17:03, 31 August 2007
Event description
| Event Owner: | A station |
|---|---|
| Event type: | 21 - Event Timeout |
| Sub-Event: | Parameter-attribute of the Event Trigger number |
| When Change to ON: | When a timer owned by this station expires |
| When Change to OFF: | N/A |
| When Related to: | Yes (optional) |
- Additional information:
- -From any event or RCI a timer can be started (or stopped) by the data message $ST (Set_Timer)
- -100 ms resolution
- -When the timer expires the event “21 Event Timeout” is triggered
- -Syntax:
- $ST Lxxxx Wyy Lzzzz
- xxxx = station which is owner of the timer
- yy = timeout value in 100ms steps
- zzzz = “related to” number (optional)
- Example 1: $ST L102 W50 - set a 5 second timer on station 102
- Example 2: $ST L102 – stop all timers on station 102
- Example 3: $ST L102 W50 L101 - set a 5 second timer on station 102, 101 is “related-to”
- Application:
- - Pulse RCO’s
- - Timeout of conversations