Actions

Difference between revisions of "ATLB stations R-key use"

From Zenitel Wiki

Line 4: Line 4:
 
However, the Alphacom system can be complicated needing different behavour when involving Billing, SIP trunk, AlphaNet etc.<br>
 
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.
 
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 interpretation of preceding digits. The enabling of the microphone is done after a local call or AlphaNet call is established (After setup tone is finnish). 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 call the microphone is enable when the 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.
 +
  
 
==Communication situations where feature during conversation can only be be used after using R-key==
 
==Communication situations where feature during conversation can only be be used after using R-key==

Revision as of 09:30, 15 August 2018

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 interpretation of preceding digits. The enabling of the microphone is done after a local call or AlphaNet call is established (After setup tone is finnish). 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 call the microphone is enable when the 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.


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.