Actions

Difference between revisions of "%1.dak"

From Zenitel Wiki

 
(16 intermediate revisions by 4 users not shown)
Line 1: Line 1:
The '''%1.dak''' parameter is used in combination with the [[IND|IND command]]. One of the parameters of the IND command is a DAK key number. The exchange can find a DAK containing a specific configuration, returning the DAK number 1 - 100.
+
{{AI}}
 +
The '''%1.dak''' parameter is used in combination with the [[IND|IND command]]. The IND command is mainly used for controlling the LEDs in the [[DAK|DAK keys]] of the [[Control_Room_Master_IV|CRMIV]] or IP Master station. One of the parameters of the IND command is a DAK key number. The exchange can find a DAK containing a specific configuration, returning the DAK number 1 - 100.
  
Syntax:
+
===Syntax===
 
  %1.dak(DAK search string[,DAK-10 range])
 
  %1.dak(DAK search string[,DAK-10 range])
  
* ''DAK search string'': This is a string matching the DAK configuration exactly, including the lead characters I, D and P. Example: I432. It is possible to match long DAK strings using wildcards:
+
* ''DAK search string'': This is a string matching the DAK configuration exactly, including the lead-in characters.
:: '?' - match any lead-in
+
 
:: '+' - match any digit up to the next lead-in
+
:Lead-in characters are:
:: '*' - match anything up to the end of the string. Example: Match any transfer key: I71*
+
:* I, E, D and P. Example: I432.  
 +
 
 +
It is possible to match long DAK strings using wildcards. Wildcards are:
 +
: '?' - match any lead-in
 +
: '+' - match any digit up to the next lead-in
 +
: '*' - match anything up to the end of the string. Example: Match any transfer key: I71*
  
 
* ''DAK-10 range'' (optional): Limits the search to one 10-DAK range. 0 = 1-10.... 9 = 91 - 100. Speeds up the search and reduces the CPU load (relevant for the old [[AMC]] card with less CPU power).
 
* ''DAK-10 range'' (optional): Limits the search to one 10-DAK range. 0 = 1-10.... 9 = 91 - 100. Speeds up the search and reduces the CPU load (relevant for the old [[AMC]] card with less CPU power).
Line 13: Line 19:
 
If the string does not match any DAK, key number 0 is returned. The IND command handles a reference to key 0 by doing nothing.
 
If the string does not match any DAK, key number 0 is returned. The IND command handles a reference to key 0 by doing nothing.
  
* station number given by event context
+
===Examples===
* %2.dak can also be used if related-to is in local exchange
+
%1.dak(I215)    - returns the DAK key number containing "I215". If not existing it will return the value 0.
* Used for controlling the LEDs of [[Control_Room_Master_IV|CRMIV]]
+
%1.dak(I215,2)  - returns the DAK key number containing "I215" if it exists on DAK key 21-30
 +
%1.dak(I%2.dir)  - returns the DAK key number of the 'Related To' station, i.e. the conversation partner or Call Request sender
  
Examples:
+
===Additional information===
%1.dak(I215)     returns the number of the DAK key containing "I215". If not existing it will return ther value 0.
+
* '''%2.dak''' (using the 'Related To') can also be used if the related-to is in local exchange
%1.dak(I215,2)   returns the number of the DAK key containing "I215" if it exists on DAK key 31-40
+
* '''%1.dak(?+)''' is not working. It's not possible to use two wildcards. Instead try %1.dak(I*), %1.dak(E*) or %1.dak(P*)
  
 +
----
  
  
 
Back to [[Event_Handler#List_of_context_parameters]].
 
Back to [[Event_Handler#List_of_context_parameters]].
  
 +
[[Category:Event Handler macros]]
 
[[Category:Event Handler]]
 
[[Category:Event Handler]]

Latest revision as of 09:45, 4 October 2019

AI.png

The %1.dak parameter is used in combination with the IND command. The IND command is mainly used for controlling the LEDs in the DAK keys of the CRMIV or IP Master station. One of the parameters of the IND command is a DAK key number. The exchange can find a DAK containing a specific configuration, returning the DAK number 1 - 100.

Syntax

%1.dak(DAK search string[,DAK-10 range])
  • DAK search string: This is a string matching the DAK configuration exactly, including the lead-in characters.
Lead-in characters are:
  • I, E, D and P. Example: I432.

It is possible to match long DAK strings using wildcards. Wildcards are:

'?' - match any lead-in
'+' - match any digit up to the next lead-in
'*' - match anything up to the end of the string. Example: Match any transfer key: I71*
  • DAK-10 range (optional): Limits the search to one 10-DAK range. 0 = 1-10.... 9 = 91 - 100. Speeds up the search and reduces the CPU load (relevant for the old AMC card with less CPU power).

If the string does not match any DAK, key number 0 is returned. The IND command handles a reference to key 0 by doing nothing.

Examples

%1.dak(I215)     - returns the DAK key number containing "I215". If not existing it will return the value 0.
%1.dak(I215,2)   - returns the DAK key number containing "I215" if it exists on DAK key 21-30
%1.dak(I%2.dir)  - returns the DAK key number of the 'Related To' station, i.e. the conversation partner or Call Request sender

Additional information

  • %2.dak (using the 'Related To') can also be used if the related-to is in local exchange
  • %1.dak(?+) is not working. It's not possible to use two wildcards. Instead try %1.dak(I*), %1.dak(E*) or %1.dak(P*)


Back to Event_Handler#List_of_context_parameters.