Difference between revisions of "Event Trigger Feature 15"
From Zenitel Wiki
| Line 1: | Line 1: | ||
Event Trigger Feature : type 15 | Event Trigger Feature : type 15 | ||
| − | The 'Owner' station dials a directory number with feature 52 (event trigger without tone) or feature 85 (event trigger with cancel tone) which triggers the defined events. The event must be related to | + | The 'Owner' station dials a directory number with feature 52 (event trigger without tone) or feature 85 (event trigger with cancel tone) which triggers the defined events. The event must be related to the directory number which triggers the event. When the event is triggered by physically dialling the ‘Related to’ directory number, the event can only report an ON status. If the event is triggered from the [[EVENT REPORT|data protocol message $ER]], it is also possible to report an OFF status. <br> |
The field ‘Subevent’ can be used to group event triggers. This field is associated with the 'Parameter 1' field of the feature. This means that a number of event trigger directory numbers can be defined with the same parameter. If the ‘Related to’ field is set to ‘ALL’ and the ‘Subevent’ field is set to that same parameter value, all these directory numbers will trigger the same event.<br> | The field ‘Subevent’ can be used to group event triggers. This field is associated with the 'Parameter 1' field of the feature. This means that a number of event trigger directory numbers can be defined with the same parameter. If the ‘Related to’ field is set to ‘ALL’ and the ‘Subevent’ field is set to that same parameter value, all these directory numbers will trigger the same event.<br> | ||
When used in conjunction with the data protocol message $ER, the owner does not need to be a physical station, but can be a dummy (non-existent) station. This can be useful when an [[RCI]] needs to trigger a lengthy action string, which exceeds the allowed length for the RCI action string itself. The action string for the RCI can then be an event report on a dummy station, where the real actions are performed on the event trigger on this dummy station.<br> | When used in conjunction with the data protocol message $ER, the owner does not need to be a physical station, but can be a dummy (non-existent) station. This can be useful when an [[RCI]] needs to trigger a lengthy action string, which exceeds the allowed length for the RCI action string itself. The action string for the RCI can then be an event report on a dummy station, where the real actions are performed on the event trigger on this dummy station.<br> | ||
| − | The event is also triggered on dialling a directory number with feature 95 (Event trigger with user parameter) or feature 105 (Event trigger with digits). In this case the event reports ON when the event directory number has been dialled and OFF when the event is ‘disconnected’. In the case of feature 95 and 105, this is useful functionality. Feature 95 and 105 directory numbers do not disconnect immediately after connection (like feature 52 or 85 directory numbers), but either timeout after 20 seconds, or can be disconnected via a data protocol message $DISCON_ST. | + | The event is also triggered on dialling a directory number with feature 95 (Event trigger with user parameter) or feature 105 (Event trigger with digits). In this case the event reports ON when the event directory number has been dialled and OFF when the event is ‘disconnected’. In the case of feature 95 and 105, this is useful functionality. Feature 95 and 105 directory numbers do not disconnect immediately after connection (like feature 52 or 85 directory numbers), but either timeout after 20 seconds, or can be disconnected via a data protocol message [[DISCON ST|$DISCON_ST]]. |
See also the [[Event Handler]] | See also the [[Event Handler]] | ||
Revision as of 23:31, 14 February 2008
Event Trigger Feature : type 15
The 'Owner' station dials a directory number with feature 52 (event trigger without tone) or feature 85 (event trigger with cancel tone) which triggers the defined events. The event must be related to the directory number which triggers the event. When the event is triggered by physically dialling the ‘Related to’ directory number, the event can only report an ON status. If the event is triggered from the data protocol message $ER, it is also possible to report an OFF status.
The field ‘Subevent’ can be used to group event triggers. This field is associated with the 'Parameter 1' field of the feature. This means that a number of event trigger directory numbers can be defined with the same parameter. If the ‘Related to’ field is set to ‘ALL’ and the ‘Subevent’ field is set to that same parameter value, all these directory numbers will trigger the same event.
When used in conjunction with the data protocol message $ER, the owner does not need to be a physical station, but can be a dummy (non-existent) station. This can be useful when an RCI needs to trigger a lengthy action string, which exceeds the allowed length for the RCI action string itself. The action string for the RCI can then be an event report on a dummy station, where the real actions are performed on the event trigger on this dummy station.
The event is also triggered on dialling a directory number with feature 95 (Event trigger with user parameter) or feature 105 (Event trigger with digits). In this case the event reports ON when the event directory number has been dialled and OFF when the event is ‘disconnected’. In the case of feature 95 and 105, this is useful functionality. Feature 95 and 105 directory numbers do not disconnect immediately after connection (like feature 52 or 85 directory numbers), but either timeout after 20 seconds, or can be disconnected via a data protocol message $DISCON_ST.
See also the Event Handler