Difference between revisions of "External Data Input"
From Zenitel Wiki
(→Example) |
|||
Line 1: | Line 1: | ||
==Event description== | ==Event description== | ||
+ | {| | ||
+ | |- | ||
+ | |width="100pt"|'''Event Owner''': | ||
+ | |width="300pt"|EDI Text Config | ||
+ | |- | ||
+ | |'''Event type''': || 28 - External Data Input | ||
+ | |- | ||
+ | |'''Subevent''': || 1 – 4: specifies which EDI port. 0: matches all ports | ||
+ | |- | ||
+ | |'''When change to ON''': || When valid data is received on EDI port | ||
+ | |- | ||
+ | |'''When change to OFF''': || N/A | ||
+ | |- | ||
+ | |'''When related to''': || N/A | ||
+ | |- | ||
+ | |} | ||
{| border="1" cellpadding="4" | {| border="1" cellpadding="4" |
Revision as of 20:30, 26 November 2007
Event description
Event Owner: | EDI Text Config |
Event type: | 28 - External Data Input |
Subevent: | 1 – 4: specifies which EDI port. 0: matches all ports |
When change to ON: | When valid data is received on EDI port |
When change to OFF: | N/A |
When related to: | N/A |
Event Owner: | EDI Text Config |
---|---|
Event type: | 28 - External Data Input |
Sub-Event: | 1 – 4: specifies which EDI port. 0: matches all ports |
When Change to ON: | When valid data is received on EDI port |
When Change to OFF: | N/A |
When Related to: | N/A |
- Input message
- - The EDI port is defined in the ‘Serial Ports’ Setup
- - The input message must have a termination character. Max 128 char.
- - Parsing the content is done in the action string in the Event Handler
- Context parameters
- Useful macros and statements
Example
The rule below will allow you to issue commands to EDI port like this:
- Input command: connect,101,103
- -Generates internal command $CALL L101 L103
- Input command: disconnect,101,103
- -Generates internal commands $C L101and $C L103
tmp 0 "%scutf(%edi,\,,0)" tmp 1 "%scutf(%edi,\,,1)" tmp 2 "%scutf(%edi,\,,2)" if %scmp(%tmp(0),connect) $CALL L%tmp(1) L%tmp(2) stop endif if %scmp(%tmp(0),disconnect) $C L%tmp(1) $C L%tmp(2) stop endif