Difference between revisions of "%sev"
From Zenitel Wiki
| Line 9: | Line 9: | ||
* [[AlphaNet Link (Event Type)|Event 29 - AlphaNet Link]]. %SEV is the remote node number | * [[AlphaNet Link (Event Type)|Event 29 - AlphaNet Link]]. %SEV is the remote node number | ||
* [[Station DAK key as RCI (Event Type)| Event 30 - Station DAK key as RCI]]: %SEV will return the DAK key number pressed | * [[Station DAK key as RCI (Event Type)| Event 30 - Station DAK key as RCI]]: %SEV will return the DAK key number pressed | ||
| − | * [[Private Ringing Outgoing(Event Type)|Event 33 - Private Ringing Outgoing]]. %SEV | + | * [[Private Ringing Outgoing(Event Type)|Event 33 - Private Ringing Outgoing]]. %SEV will return a number indicating the reason why ringing ended |
* | * | ||
Revision as of 11:05, 22 August 2018
- Returns the sub-event number (in decimal format) of the event being processed.
Sub-event value 255 acts 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 is triggered when reciving text on an External_Data_Input. %SEV tells which EDIO port 1 - 10 the EDI text arrived on.
- Event 29 - AlphaNet Link. %SEV is the remote node number
- Event 30 - Station DAK key as RCI: %SEV will return the DAK key number pressed
- Event 33 - Private Ringing Outgoing. %SEV will return a number indicating the reason why ringing ended