Ring Again

Last Updated : Dec 05, 2019 |
Prolog information
Metadata
Keywords:
  • CS 1000 endpoint user experience
    Ring Again is programmable for UNIStim and 39XX endpoints at a fixed position, and digital 200X endpoints at an unfixed position. For UNIStim and 39XX endpoints, it maps to a soft key. This feature works in the following manner:
    • User makes a call to a busy destination. The phone displays the Ring Again key.
      Note:
      The phone does not display the Ring Again key if the call was made using a PSTN trunk.
    • User presses the Ring Again key.
    • The phone screen returns to an idle state with the Ring Again key indicating it is active.
    • The user can cancel the Ring Again request by pressing the Ring Again key before a callback offer is received. A callback offer is received when Avaya Aura® presents the Ringout call invitation.
    • When the far-end becomes available, a callback offer is presented to the endpoint. The Ring Again key flashes and an audible tone is heard to indicate that a callback offer is received. The user cannot cancel the Ring Again request after the callback offer is received.
    • User places a call by selecting a line and pressing the Ring Again key.
    The Ring Again feature can be activated for calls made from any line DN key. A corresponding variant is available for Ring Again on No Answer (RANA). For RANA, the same button is used, but the behavior is different.
    Upon encountering a station that does not answer, a station with the Ring Again capability can activate RANA by pressing the Ring Again key. Later, when the desired station goes off-hook to make or receive a call, and then goes on hook, the station that activated Ring Again receives a ring through the telephone’s loudspeaker and the lamp flashes if the station is idle. The station user can dial the desired station by lifting the handset and pressing a DN key, and then pressing the Ring Again key.
    This feature works as follows:
    1. User A calls user B. User A receives a ring back tone.
    2. The user waits long enough to decide to activate RANA.
    3. User A presses the Ring Again (RGA) key. The RGA key indicator turns on steadily.
    4. User A either goes on-hook or presses the Release (RLS) key. The indicator associated with RGA key remains on and user A is now free to receive or make other calls.
    5. User B goes off-hook to make a call, and then goes on-hook. User A is given a short ring through the loudspeaker and the indicator associated with the RGA key flashes.
    6. User A either picks up the handset or presses a DN key. User A receives dial tone.
    7. User A presses the RGA key. The user against which the Ring Again was placed is rung and the indicator associated with the RGA key is turned off.
    If the called party does not accept the call in a duration of six ringing cycles, the request is cancelled. If no appearances are available during that time, the request is cancelled.
    If the called party goes off-hook, and if the calling party accepts the Ring Again on No Answer request, the calling party may encounter Ring Again, Busy case.
  • Communication Manager endpoint user experience
    This feature maps to the Automatic Callback functionality. This feature works in the following manner:
    • The phone is assigned the Automatic Callback key.
    • The Automatic Callback button becomes available when a call is made to a busy extension or when a destination does not answer.
    • When the destination extension finishes the call or in case of a no answer scenario where the called party becomes active on a call and finishes the call, a Ringout call is initiated.
    • The originating phone is notified of the destination’s availability.
    • The Callback call is presented to the destination phone when the originating phone goes off-hook.
    The following limitations exist in the Communication Manager implementation when compared with CS 1000:
    • Users cannot activate Automatic Callback from a bridged call appearance.
    • If a user activates Automatic Callback from a primary extension number, the return call notification rings at all bridged call appearances.
      Important:
      There should be a wait time of 32 seconds before attempting second Ring Again to same phone as the previous, over the same network.
  • Device Adapter endpoint user experience
    This feature is implemented in the following ways:
    • For UNIStim endpoints, the Ring Again feature key is mapped to the Auto Callback key at a fixed position key. This fixed position key maps to a context-sensitive soft key and is active only when the capability is needed and applicable. Device Adapter treats it as a legacy RGA button and provides localization for UNIStim and all 39xx endpoints, except the 3901 endpoints.
      For digital M3903, M3904, and M3905 sets, the Ring Again feature key is mapped to the Auto Callback key at a fixed position in the soft keys, in the same way it is done for the UNIStim endpoints. Other digital sets must have the Auto Callback key assigned to one of the available programmable keys. Device Adapter treats the Auto Callback button as a legacy RGA button, and provides localization for the M3902 set that has programmable soft keys, and for the M3903, M3904, and M3905 sets.
      Analog sets can invoke Ring Again by using the Communication Manager Automatic Call Back Feature Access Code. Device Adapter treats it as a Flexible Feature Code equivalent.
    • When the destination is busy and the user presses the Ring Again key, Device Adapter subscribes to a Ringout call. The Ring Again key with an arrow now appears on the idle screen.
    • When the destination does not answer and the user presses the Ring Again key, Device Adapter subscribes to a Ringout call. The Ring Again key with an arrow now appears on the idle screen. However, in this case, the called party must become active and then become idle to send an indication to the party that activated the Ring Again.
    • The user can cancel the Ring Again request by pressing the Ring Again key before a callback offer is received. A callback offer is received when Avaya Aura® presents the Ringout call invitation.
    • When the endpoint receives a callback offer, the Ring Again key flashes and an audible tone is heard to indicate that a callback offer is received. The user cannot cancel the Ring Again request after the callback offer is received.
    • When Ringout call is presented by CM, the user receives an incoming call on a free call appearance, and Ring Again soft key flashes indicating this is a Ringout call.
    • If the user does not accept the Ringout call before the offer times out, Ring Again is cancelled.
    • If the user is on a call, a tone burst is heard and a lamp flashes.
    • The user answers this Ringout call like a normal call by off-hook or by selecting the ringing call appearance.
    • When the Ring Again key flashes to present the callback offer, the user can press the Ring Again key to ignore the offer. The Ring Again key becomes dark and the audible tone stops. Pressing the Ring Again key only ignores the callback offer and does not cancel it. The offer automatically times out after the time-out period is reached.
      This behavior is similar to the Ignore option on the Avaya Aura® SIP endpoints. When a callback offer is presented on an Avaya Aura® SIP endpoint, the Ignore soft key appears on the endpoint. The user can press the Ignore soft key to ignore the callback offer.
    Note:
    There is a difference in configuration between Device Adapter and Communication Manager phones. Device Adapter phones have one call appearance by default and Communication Manager phones have two. Additionally, Communication Manager phones cannot deactivate Ring Again (Automatic Callback) when both call appearance lines are busy. This same behavior is applicable to a Device Adapter phone.
    If both lines become busy, users will not be able to use Ring Again unless they restart their phone. The following is an example of this scenario on Device Adapter phones:
    • Assume that User C has only one available call appearance.
    • User A calls User B. User B answers.
    • User C calls User A but User A does not answer. User C presses Ring Again to invoke Ring Again against call User A.
    • User D calls User C and User C answers.
    • User A and User B end their call.
    • The Ring Again is cancelled because there is only one call appearance at user C, and that appearance is in use.
    • User C and User D end their call. Ring Again does not happen.
    It is recommended that a second call appearance be configured for Device Adapter phones so that this limitation is not encountered.
For more information, see Ring Again in Appendix H: Call processing features and services.