Difference between revisions of "Transparent Mode DAK-Key Configuration"
From Zenitel Wiki
(→Configuration from AlphaPro Event Handler) |
|||
Line 24: | Line 24: | ||
The [[System_Status_%28Event_Type%29 | System Status Event]] related to device (subevent) 65 can be used to write the wanted value to the nvram at system startup: | The [[System_Status_%28Event_Type%29 | System Status Event]] related to device (subevent) 65 can be used to write the wanted value to the nvram at system startup: | ||
− | + | {{code2| | |
− | $SNV Q(DAK key) W1 W2 W21 | + | $SNV Q(DAK key) W1 W2 W21}} |
DAK key = 2 to 9. | DAK key = 2 to 9. |
Revision as of 13:09, 3 June 2022
When making an external call from AlphaCom out on a SIP trunk (or to a station type PNCI), the dialed digits are sent transparent through the AlphaCom, out on the SIP Trunk.
However, there might be a need to let the AlphaCom handle the digits, for example if one wants to make a call transfer (2 + intercom number + 3) or blind transfer after the telephone call has been established.
Default operation:
- DAK key 8 (counted from 0) is used for switching off "transparent mode" when calling from analog (ASLT) stations.
- DAK key 3 (counted from 0) is used when calling from IP stations.
The full operation to transfer a call after having established an external conversation, is: DAK 8 + 2 + intercom number + 3.
Which DAK key to use for switching off transparent mode can be configured from the nvram editor in the TST console:
.ex_profile.glob_const.trans_mode_dak = 8 (0x08)
Possible values are 2 - 9
Note that DAK keys 0 and 1 are reserved for * and # and cannot be used.
If trans_mode_dak is changed from default 8, both IP stations and ASLT stations will use the configured DAK key.
Configuration from AlphaPro Event Handler
The System Status Event related to device (subevent) 65 can be used to write the wanted value to the nvram at system startup:
Action commands:
$SNV Q(DAK key) W1 W2 W21
DAK key = 2 to 9.
Example:
Back to Feature description