Difference between revisions of "%sev"
From Zenitel Wiki
| Line 2: | Line 2: | ||
* Returns the [[Sub-Event (Event Handler)|sub-event]] number (in decimal format) of the event being processed. | * Returns the [[Sub-Event (Event Handler)|sub-event]] number (in decimal format) of the event being processed. | ||
| − | Sub-event value 255 | + | Sub-event value 255 can be used as a "wild card", and the main event will be triggered regardless of the sub-event number. |
Some EventHandler reports use ''sub event'' in addition to the main [[Event_Handler#Events_Types|event type]]: | Some EventHandler reports use ''sub event'' in addition to the main [[Event_Handler#Events_Types|event type]]: | ||
Revision as of 11:09, 22 August 2018
- Returns the sub-event number (in decimal format) of the event being processed.
Sub-event value 255 can be used as a "wild card", and the main event will be triggered regardless of the sub-event number.
Some EventHandler reports use sub event in addition to the main event type:
- Event 25 is triggered when dialing digits after having called feature 105. %SEV will return the dialled digit
- Event 28 - External Data Input is triggered when reciving text on an EDIO port. %SEV tells which EDIO port 1 - 10 the text arrived on.
- Event 29 - AlphaNet Link reports AlphaNet links up or down. %SEV is the remote node number
- Event 30 - Station DAK key as RCI reports DAK keys or inputs activated: %SEV will return the DAK key number or Input number
- Event 33 - Private Ringing Outgoing. %SEV will return a number indicating the reason why ringing ended