Difference between revisions of "Event Timeout (Event Type)"
From Zenitel Wiki
(→Event description) |
(→Additional information) |
||
| Line 18: | Line 18: | ||
==Additional information== | ==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== | ==Application== | ||
Revision as of 00:10, 15 November 2007
Event description
| Event Owner: | A station or UDP group |
| Event type: | 21 - Event Timeout |
| Subevent: | N/A |
| 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