%sev: Difference between revisions
From Zenitel Wiki
No edit summary |
No edit summary |
||
| 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 = 255 is a "wild card", and the main event will be triggered | 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_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 09:55, 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:
- When used with feature 105, 'Event trigger on dialling digits', %SEV will return the dialled digit (Main event is Event Trigger with parameter (Event Type)).
- When used with External_Data_Input, %SEV is the 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
- ...