MDA limitations

Last Updated : Feb 17, 2020 |
Prolog information
The following are the limitations of MDA in Device Adapter:
  • Device Adapter uses the hardware ID of the UNIStim phone, from CS 1000, to register the UNIStim phone. This hardware ID must be unique in CS 1000. Whereas, MDA uses the user identity to register the UNIStim phone.
    During phone registration, Device Adapter uses the TN of the phone to map the hardware ID and user identity.
    The TN is nothing but the physical port ID of a phone on CS 1000. For a UNIStim phone, the TN is a logical port ID of the UNIStim phone because the UNIStim phone does not have a physical shelf. For digital and analog phones, the TN is the physical port ID to which the phone is physically connected by wires.
    The following are the registration differences in different infrastructure scenarios when two or more UNIStim endpoints, with the same TN, try to register:
    • In a single-node cluster, the registration always fails.
    • In geo-redundant clusters, including two single-node clusters, a second registration succeeds.
    • In all other cases, the registration may or may not succeed depending on the current registrations.
    Therefore, registering two or more UNIStim phones with the same TN is non-deterministic in MDA.
    Hence, registration of a UNIStim endpoint is non-deterministic in an MDA configuration where the maximum number of concurrent registrations is set to two or more, and out of these endpoints more than one endpoint is a UNIStim endpoint.
    Avaya recommends that if your MDA configuration contains two or more phones, ensure that only one phone out of these phones is a UNIStim phone.
  • The primary station definition must be that of a UNIStim endpoint because the intent is to migrate the CS 1000 endpoints and its users to Avaya Aura®. Registering an existing UNIStim endpoint to a new 96x1 station definition is contradictory. Device Adapter does not support using a non-UNIStim station definition for a UNIStim endpoint that is registering for MDA.
    You must use the CS1K_IP station template to define the station definition for a UNIStim phone that will be used as a UC phone.
    You must use the CS1K_IPCC station template to define the station definition for a UNIStim phone that will be used as a call center-capable phone.
  • Digital and analog endpoints do not support MDA. These endpoints use the physical device access port (loop, shelf, card, unit) or Terminal Number (TN) to identify the set. This is a physical port of these devices and cannot be modified by the user. Only UNIStim endpoints that use a virtual TN, allow the user to modify the TN. Note that after the user modifies the TN, the user must restart the endpoint. For more information, see MDA limitations for digital and analog endpoints.
    However, you can use the Sequential Registration fail-over configuration to configure fail-over support for digital and analog endpoints. For more information, see Sequential Registration fail-over support for analog and digital endpoints.