Transparent Mode DAK-Key Configuration: Difference between revisions
From Zenitel Wiki
No edit summary |
No edit summary |
||
| (19 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{AI}} | |||
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. | 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 [[Inquiry Call feature|call transfer]] (2 + intercom number + 3) or [[Blind Transfer During Connection|blind transfer]] after the telephone call has been established. | However, there might be a need to let the AlphaCom handle the digits, for example if one wants to make a [[Inquiry Call feature|call transfer]] (2 + intercom number + 3) or [[Blind Transfer During Connection|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 | The full operation to transfer a call after having established an external conversation, is: DAK 8 + 2 + intercom number + 3. | ||
== Configuration from AlphaPro Event Handler == | |||
DAK | 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}} | |||
<DAK key> = 2 to 9. | |||
== Configuration | Example: | ||
[[File:Trans mode off.PNG|left|thumb|400px|Use DAK key 2 to turn off "transparent mode"]] | |||
<br style="clear:both;" /> | |||
== Configuration using TST console == | |||
Which DAK key to use for switching off transparent mode can be configured from the nvram editor in the [[TST console]]: | |||
{{code|.ex_profile.glob_const.trans_mode_dak <nowiki>=</nowiki> 8 (0x08)}} | |||
Possible values are 2 - 9 <br /> | |||
DAK | 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. | |||
Back to [[Feature description]] | Back to [[Feature description]] | ||
[[Category: ICX-AlphaCom features]] | |||
[[Category: ICX-AlphaCom - SIP Integration]] | |||
[[Category: AlphaCom features]] | [[Category: AlphaCom features]] | ||
[[Category: AlphaCom - SIP Integration]] | |||
Latest revision as of 11:16, 23 February 2023
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.
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:
Configuration using TST console
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.
Back to Feature description