Difference between revisions of "%sev"
From Zenitel Wiki
| Line 5: | Line 5: | ||
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]]: | ||
| − | * | + | * 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. |
* When used with [[AlphaNet Link (Event Type)|event 29 - AlphaNet Link]], %SEV is the remote node number | * When used with [[AlphaNet Link (Event Type)|event 29 - AlphaNet Link]], %SEV is the remote node number | ||
* When used with [[Private Ringing Outgoing(Event Type)|event 33 - Private Ringing Outgoing]], %SEV returns a number indicating the reason why ringing ended | * When used with [[Private Ringing Outgoing(Event Type)|event 33 - Private Ringing Outgoing]], %SEV returns a number indicating the reason why ringing ended | ||
Revision as of 10:01, 22 August 2018
- Returns the sub-event number (in decimal format) of the event being processed.
Sub-event = 255 is 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.
- When used with event 29 - AlphaNet Link, %SEV is the remote node number
- When used with event 33 - Private Ringing Outgoing, %SEV returns a number indicating the reason why ringing ended
- ...