Sequential Registration

Last Updated : Oct 01, 2019 |
Prolog information
Metadata
Keywords:
As opposed to Multi-Device Access (MDA), which allows 2 or more concurrent endpoint registrations, Sequential Registration allows one endpoint to be registered at one time. You can use the Multi-Device Access (MDA) configuration fields to limit the number of concurrent registered devices to 1 for Sequential Registration.
You must use Sequential Registration, instead of MDA, when a user wants to use multiple UNIStim endpoints so that the number of concurrent registrations is limited to 1. This is because registering two or more UNIStim endpoints with the same TN is non-deterministic in MDA.
Whether a new endpoint can register for MDA or Sequential Registration depends on whether you select or clear the Block New Registration When Maximum Registrations Active check box.
  • If the Block New Registration When Maximum Registrations Active is selected, then the user must manually un-register an existing registered endpoint before registering a new endpoint. Typically, the user logs out from the endpoint to un-register the endpoint.
  • If the Block New Registration When Maximum Registrations Active is cleared, Session Manager un-registers an existing endpoint that is registered the longest period of time to register the new endpoint.
For example, a user has a 96x1 at the desk, a 96x1 in the lab, and an Avaya Workplace Client on the laptop. All these devices are registered with the same extension number 123456.
  • If the user registers with the 96x1, then Session Manager clears any prior registration.
  • If the user registers with the J-Series, then Session Manager clears the 96x1 registration.
  • Similarly, every new registration clears the old registration.
  • CS 1000 endpoint user experience
    The registration handling process upon network failures for UNIStim endpoints and for endpoints on MGC servers in Sequential Registration is similar to that of the CS 1000 TPS.
    The following is the initial registration recovery attempt in CS 1000 for UNIStim endpoints and MGC:
    • UNIStim endpoint: When a CS 1000 UNIStim endpoint restarts or fails over, it attempts to register with the TPS load balancer of the primary server (S1). The UNIStim endpoint may or may not register on the same TPS.
    • MGC: When CS 1000 MGC restarts or fails over, it attempts to register with the primary call server.
    The following the registration recovery attempt in CS 1000 when initial registration attempt fails:
    • UNIStim endpoint: If the primary server TPS is unavailable, then the TPS on the geo-redundant alternate data center is attempted. The endpoint attempts the alternate server (S2). In this case, it does not register on the same CS 1000 that it was originally using. Therefore, it uses a different TPS load balancer.
    • MGC: If the primary call server is unavailable, then a geo-redundant alternative is attempted. MGC attempts to register with the alternate server.
      MGC allows triple redundancy. Which means, there can be a primary MGC and two alternate MGCs that control the devices, unlike the S1/S2 (primary and one alternative) of the UNIStim endpoints.
      If two alternate servers are defined, then MGC attempts the first alternate server. Because triple redundancy is designed to provide a geo-redundant recovery, MGC does not register to the same call server it was originally using. In addition, because there are two alternate servers, if the registration or registration attempt to the first alternate server fails, MGC attempts to register to the second alternate server.
      For more information, see the Communication Server 1000E Planning and Engineering guide and the CS 1000 documentation.
    In both cases, CS 1000 identifies the hardware ID of the registering endpoint or the TN entered by the user when registering a UNIStim endpoint. CS 1000 uses the hardware ID or TN to allow or block fail over and endpoint registration when a UNIStim endpoint or MGC restarts or loses connectivity to the current target. If there is a mismatch in the hardware ID between the original registration and the new one, the registration fails.
    Unlike Sequential Registration, CS 1000 rejects a new device attempting to register to an existing registration, but accepts a re-registration on another TPS or call server.
    This CS 1000 behavior can be deemed as conditional Sequential Registration. If the same device re-registers at another TPS, the registration is allowed. If a device with a different hardware ID tries to register, the registration is denied.
  • Communication Manager endpoint user experience
    When a device is already SIP registered, and the user registers from elsewhere as the user identity, Session Manager does the following:
    • Session Manager:
      • Verifies the user identity that is attempting the registration.
      • Detects whether a current registration exists.
      • Detects whether the Max. Simultaneous Devices is set to 1. Therefore, the maximum number of devices registered is reached.
    • Session Manager verifies if the user profile is configured to allow or block new registrations:
      • If the Block New Registration When Maximum Registrations Active check box is selected, the registration request is rejected. The user must manually un-register an existing device to register the new device.
      • If the Block New Registration When Maximum Registrations Active is clear, Session Manager does the following to allow new registrations:
        • Session Manager terminates the registration of an existing device to register the new device.
        • The new registration is completed. If necessary, the device data is mapped to a format suitable for the new endpoint. For example, allowing a J-series to register as a 96x1 identity.
  • Device Adapter endpoint user experience
    Device Adapter supports Sequential Registration. To configure Sequential Registration, set the MDA configuration fields to the following:
    • Set the Max. Simultaneous Devices value to 1.
    • Clear the Block New Registration When Maximum Registrations Active check box to allow new registrations. Session Manager terminates the registration of an existing device to register the new device.
    This provides a similar CS 1000 user experience in case of a fail over or endpoint restart. However, if a user tries to register a second station to CS 1000, CS 1000 blocks the registration attempt. This is because the fail-over handling in CS 1000 does not find a match in the hardware IDs of both requests.
    Whereas, Device Adapter allows the new registration request because the device ID is not available and cannot be sent to Session Manager. If the Session Manager user profile is set to allow new registrations when the maximum number of registered devices is reached, Session Manager allows another endpoint to register by using Sequential Registration.
    Sequential Registration allows sequential registration for any endpoint that can use the CS1K-IP station definition to define the endpoint. Although, the Avaya Aura® SIP endpoints will have a different user experience.
The following is an example of Sequential Registration:
  1. Device X is SIP registered as the user identity A.
  2. Device Y attempts to SIP register as the user identity A.
  3. Session Manager verifies whether this is a permissible registration and does one of the following:
    • If the configuration is to block new registrations, the registration request is rejected.
    • If the configuration is to allow new registrations, Session Manager terminates the SIP registration of device X and registers device Y.
For more information, see Sequential Registration in Appendix H: Call processing features and services.