Difference between revisions of "ATLB stations R-key use"
From Zenitel Wiki
(→Functionality) |
|||
| (12 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | == Description == | |
| − | The ATLB | + | The ATLB/ATLB-12 card can detect voice as DTMF signal during conversation, and thus trigger "features during" conversation.<br> |
| − | "features during" conversation. | + | To inhibit triggering of unintended features, digits during conversation for internal interpretation (inquiry, door opening)is allowed only after using the R-key (Hook Flash).<br> |
| − | To inhibit triggering of unintended features, digits during conversation | + | However, the Alphacom system can be complicated needing different behavour when involving Billing, SIP trunk, AlphaNet etc.<br> |
| + | Different situations and different types of 3rd party equipment can require use of some configuration options for the R-key behaviour. | ||
| − | ===Communication situations where feature during conversation can only be be used after using R-key | + | == Functionality == |
| + | The general functionality is based on the enabling of the microphone input at the ATLB line point. After MIC_OPEN is active the R-key must be used to allow internal interpretation of preceding digits. The enabling of the microphone is done after a local call or AlphaNet call is established (After setup tone is finish). When activating a local feature like WakeUp or AreaCode the microphone is not activated thus enabling proceeding digits without the use of R-key. For SIP trunk calls the microphone is enabled when audio is established to the gateway thus no SIP_INFO is generated when the PSTN digits are dialled. However the DTMF interpreter is still active locally for reporting digits to the billing system. | ||
| + | |||
| + | == Configuration == | ||
| + | The R-Key behaviour can be adjusted with an Nvram variable: | ||
| + | |||
| + | 24 &000144 .ex_profile.flags.ATLB_R_key = 0 | ||
| + | |||
| + | |||
| + | '''Value 0 (Default)''' | ||
| + | |||
| + | R-Key must be used for internal interpretation in all situations where the conversations is established, implies when the microphone input is opened. | ||
| + | When pressing the R key during conversation the telephone will get a new "Handset off" tone and can activate "Local" features during conversation. Also on AlphaNet the handset tone will now be activated due to the new $DP R_KEY command. | ||
| + | When calling a SIP trunk this system implies that no SIP_INFO digit messages is sent after calling the trunk with the use of an area code. For most SIP trunks this will work due to the DTMF signalling from the Telephone in the audio band. This DTMF signalling will be interpreted at most SIP gateways. | ||
| + | |||
| + | '''Value 1''' | ||
| + | |||
| + | DTMF signalling is always interpreted inside the AlphaCom thus no R-KEY is needed for activating features during conversation. | ||
| + | When calling a SIP trunk the R-Key will be used to change to "local features" like the DAK 8 does from ASLT stations. | ||
| + | SIP_INFO will always be sent to the SIP gateway except when in local feature mode (after pressing R-Key). | ||
| + | |||
| + | |||
| + | '''Value 2''' | ||
| + | |||
| + | DTMF signalling is interpreted for the period of "dial tone timeout" after each digit after call established. This mode is intended for system having "pure" SIP trunks not able to detect DTMF signaling. | ||
| + | When calling the SIP trunk with an area code the user is able to continue dialling the PSTN number. (No local dial tone is generated). | ||
| + | When dialling is stopped the dial tone timeout (5 sec) will turn off the DTMF interpretor. It is currently not possible to get back to the AlphaCom DTMF interpretor mode (SIP INFO) after the dial time out. (Dual R-key use? I believe users will be confused if first R-key press give you local function and the next gives you SIP INFO). | ||
| + | If the user press R-key local AlphaCom functions will be available. | ||
| + | |||
| + | =='''A little more about default behaviour:'''== | ||
| + | |||
| + | ==Communication situations where feature during conversation can only be be used after using R-key== | ||
*Local Call A to B, A is ATLB | *Local Call A to B, A is ATLB | ||
*Local Call A to B, B is ATLB | *Local Call A to B, B is ATLB | ||
| Line 12: | Line 44: | ||
*Call from SIP, A is ATLB | *Call from SIP, A is ATLB | ||
| − | + | ==Communication situations where dialing must be available after activating a feature== | |
*Dialing a AlphaNet area code, the proceeding digits must be sent to the remote exchange | *Dialing a AlphaNet area code, the proceeding digits must be sent to the remote exchange | ||
*Dialing a feature code requiring additional digits, wake-up etc. | *Dialing a feature code requiring additional digits, wake-up etc. | ||
| + | |||
| + | ==SIP situations where dialling is not sent to remote node== | ||
| + | *Calling a SIP trunk, the call is established after dialling the area code (for example "0"). No SIP INFO is sent for proceeding digits. | ||
Latest revision as of 09:12, 12 February 2020
Contents
- 1 Description
- 2 Functionality
- 3 Configuration
- 4 A little more about default behaviour:
- 5 Communication situations where feature during conversation can only be be used after using R-key
- 6 Communication situations where dialing must be available after activating a feature
- 7 SIP situations where dialling is not sent to remote node
Description
The ATLB/ATLB-12 card can detect voice as DTMF signal during conversation, and thus trigger "features during" conversation.
To inhibit triggering of unintended features, digits during conversation for internal interpretation (inquiry, door opening)is allowed only after using the R-key (Hook Flash).
However, the Alphacom system can be complicated needing different behavour when involving Billing, SIP trunk, AlphaNet etc.
Different situations and different types of 3rd party equipment can require use of some configuration options for the R-key behaviour.
Functionality
The general functionality is based on the enabling of the microphone input at the ATLB line point. After MIC_OPEN is active the R-key must be used to allow internal interpretation of preceding digits. The enabling of the microphone is done after a local call or AlphaNet call is established (After setup tone is finish). When activating a local feature like WakeUp or AreaCode the microphone is not activated thus enabling proceeding digits without the use of R-key. For SIP trunk calls the microphone is enabled when audio is established to the gateway thus no SIP_INFO is generated when the PSTN digits are dialled. However the DTMF interpreter is still active locally for reporting digits to the billing system.
Configuration
The R-Key behaviour can be adjusted with an Nvram variable:
24 &000144 .ex_profile.flags.ATLB_R_key = 0
Value 0 (Default)
R-Key must be used for internal interpretation in all situations where the conversations is established, implies when the microphone input is opened. When pressing the R key during conversation the telephone will get a new "Handset off" tone and can activate "Local" features during conversation. Also on AlphaNet the handset tone will now be activated due to the new $DP R_KEY command. When calling a SIP trunk this system implies that no SIP_INFO digit messages is sent after calling the trunk with the use of an area code. For most SIP trunks this will work due to the DTMF signalling from the Telephone in the audio band. This DTMF signalling will be interpreted at most SIP gateways.
Value 1
DTMF signalling is always interpreted inside the AlphaCom thus no R-KEY is needed for activating features during conversation. When calling a SIP trunk the R-Key will be used to change to "local features" like the DAK 8 does from ASLT stations. SIP_INFO will always be sent to the SIP gateway except when in local feature mode (after pressing R-Key).
Value 2
DTMF signalling is interpreted for the period of "dial tone timeout" after each digit after call established. This mode is intended for system having "pure" SIP trunks not able to detect DTMF signaling. When calling the SIP trunk with an area code the user is able to continue dialling the PSTN number. (No local dial tone is generated). When dialling is stopped the dial tone timeout (5 sec) will turn off the DTMF interpretor. It is currently not possible to get back to the AlphaCom DTMF interpretor mode (SIP INFO) after the dial time out. (Dual R-key use? I believe users will be confused if first R-key press give you local function and the next gives you SIP INFO). If the user press R-key local AlphaCom functions will be available.
A little more about default behaviour:
Communication situations where feature during conversation can only be be used after using R-key
- Local Call A to B, A is ATLB
- Local Call A to B, B is ATLB
- AlphaNet Call A to B, A is ATLB
- AlphaNet Call A to B, B is ATLB
- Call to SIP, A is ATLB (Dual R-key must be used)
- Call from SIP, A is ATLB
Communication situations where dialing must be available after activating a feature
- Dialing a AlphaNet area code, the proceeding digits must be sent to the remote exchange
- Dialing a feature code requiring additional digits, wake-up etc.
SIP situations where dialling is not sent to remote node
- Calling a SIP trunk, the call is established after dialling the area code (for example "0"). No SIP INFO is sent for proceeding digits.