Difference between revisions of "%1.dak"
From Zenitel Wiki
| Line 4: | Line 4: | ||
%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 characters I, D and P. Example: I432. It is possible to match long DAK strings using wildcards: |
:: '?' - match any lead-in | :: '?' - match any lead-in | ||
:: '+' - match any digit up to the next 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* | :: '*' - 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). |
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. | ||
Revision as of 22:53, 28 January 2009
The %1.dak parameter is used in combination with the 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.
Syntax:
%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:
- '?' - 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.
- station number given by event context
- %2.dak can also be used if related-to is in local exchange
- Used for controlling the LEDs of CRMIV
Examples:
%1.dak(I215) returns the number of the DAK key containing "I215". If not existing it will return ther value 0. %1.dak(I215,2) returns the number of the DAK key containing "I215" if it exists on DAK key 31-40