Difference between revisions of "IND - Indicator control for CRMIV LEDs, buzzer etc."
From Zenitel Wiki
(→Parameter description) |
(→Station Connect Operations) |
||
| Line 17: | Line 17: | ||
! style="background:#ffdead;" width="600" |PrisCom | ! style="background:#ffdead;" width="600" |PrisCom | ||
|- | |- | ||
| − | | align=center| | + | | align=center| '''station phys.no''' ||align=center|CALL||align=center|0x0008||Sets up a coversation between two users |
|- | |- | ||
| − | |align=center| | + | |align=center| '''output''' ||align=center|CONN||align=center|0x000A|| Sets up a coversation between two users |
|- | |- | ||
| − | |align=center| | + | |align=center| '''Led no/buzzer''' ||align=center| ||align=center|0x000B|| Positive response from the exchange to CONN_REQUEST |
|- | |- | ||
| − | | align=center| | + | | align=center| '''Ind-type''' ||align=center| ||align=center|0x000E|| The external application acknowledges the CONN_REFERENCE |
|- | |- | ||
| − | | align=center|[ | + | | align=center| '''[state]''' ||align=center| ||align=center|0x000D|| Negative response to CONN_REQUEST |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
|} | |} | ||
Revision as of 23:33, 10 November 2007
The IND (INDication) action is used for sending commands to a station. The commands are sent as display data. The following stations are currently using the IND command:
- CRM IV: Control the LED's in the DAK keys, the internal buzzer or relay, and the backlight of the display
- DualDisplay station: Control the video-state of the DAK-display
- Priscom station: Control the outputs used for lamps, cell light, call LED and spare output
The command syntax:
IND <station phys.no> <key no.> <LED no/buzzer> <Ind-type> [state]
Parameter description
Between the command parameters, there must always be a space.
Station Connect Operations
| Message | CRM IV | DualDisplay | PrisCom |
|---|---|---|---|
| station phys.no | CALL | 0x0008 | Sets up a coversation between two users |
| output | CONN | 0x000A | Sets up a coversation between two users |
| Led no/buzzer | 0x000B | Positive response from the exchange to CONN_REQUEST | |
| Ind-type | 0x000E | The external application acknowledges the CONN_REFERENCE | |
| [state] | 0x000D | Negative response to CONN_REQUEST |
station phys.no:
- 1-552 = The physical number of the station
key no.:
- 1-100 = The key number of the DAK-key
- 1023 = Buzzer
- 1024 = Display
- 1-100 = The key number of the DAK-key
Led no/buzzer:
- If the previous parameter was DAK-key (1 - 100):
- 1 = Red LED
- 2 = Green LED
- If the previous parameter was Buzzer (1023):
- 1 = Internal buzzer
- 2 = External buzzer (relay)
- If the previous parameter was Display (1024):
- 1 = Backlight
Ind-type:
- LEDs and display:
- 1 = continuous (low priority)
- 2 = slow flash (medium priority)
- 3 = fast flash (high priority)
- Buzzers:
- 1 = 1 bleep per 8 seconds (low priority)
- 2 = 1 bleep per 2 seconds (medium priority)
- 3 = 4 bleeps per second (high priority)
- 4 = continuous (alarm priority)
[state]:
- The brackets [ ] indicate that this command is optional. If nothing is entered in this field, the indication is switched on/off along with the event. By entering OFF, for example, you can set an indication to turn off when the event turns on.
- ON or OFF (capital letters)
Example
IND 2 23 2 3 ON – Station 2, key 23, turn green led, fast flashing, ON