%sev: Difference between revisions
From Zenitel Wiki
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
Some EventHandler reports uses ''sub event'' in addition to the main [[Event_Handler#Events_Types|event type]]: | Some EventHandler reports uses ''sub event'' in addition to the main [[Event_Handler#Events_Types|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 - 4 the EDI text arrived on. | * When used with [[External_Data_Input]], %SEV is the EDIO port 1 - 4 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 [[Private Ringing Outgoing(Event Type)|event 33 - Private Ringing Outgoing]], %SEV returns a number indicating the reason why ringing ended | |||
* ... | * ... | ||
Revision as of 20:37, 7 November 2007
Returns the sub-event number (in decimal format) of the event being processed.
If the sub-type of en event is defined as 255, the main event will be triggered independent on the reported sub-type.
Some EventHandler reports uses 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 - 4 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
- ...
