MDA with one Device Adapter UNIStim endpoint and one or more Avaya Aura® SIP endpoints registered concurrently

Last Updated : Feb 27, 2020 |
Prolog information
Metadata
Keywords:
Device Adapter allows concurrent registrations of a minimum of 2 up to a maximum of 10 SIP endpoints for MDA. However, Avaya recommends that out of the 10 SIP endpoints only one endpoint should be a Device Adapter UNIStim endpoint. One or more Avaya Aura® SIP stations can register at the same time along with the UNIStim endpoint.
Note:
For MDA, ensure that all Avaya Aura® SIP endpoints that are registered concurrently with UNIStim endpoint connect to Session Manager by using secure connection (TLS).
If the endpoints are in a public area and other users can access the endpoints, then retaining a 96x1 or other SIP station in a registered state when the user is not at the desk is possibly a security risk. However, if you do not allow multiple devices to register concurrently, the user cannot transfer the call between devices.
If the user wants to use some other devices or application; for example, Expert Client or 96x1, in addition to the Device Adapter UNIStim endpoint, then out of the permissible number of registered devices, which is 10:
  • Avaya recommends that only one endpoint should be a Device Adapter UNIStim endpoint. This is because registering two or more UNIStim endpoints with the same TN is non-deterministic in MDA.
  • There can be more than one other traditional Avaya Aura® SIP endpoints, such as 96x1, J-series, and Avaya soft clients.
  • The maximum number of endpoints that can register is 10.
For example, the user may have two Avaya Aura® SIP devices, such as a 96X1 and a J-series, in addition to a Device Adapter UNIStim 1140 endpoint. The Max. Simultaneous Devices is set to 2. If the 96X1 and J-series endpoints are registered and the 1140 endpoint tries to register, Session Manager terminates the registration of the device that is registered for the longest period of time to register the Device Adapter UNIStim endpoint. That is, either the J-Series or the 96x1 SIP phone. However, the operation of the J-series and 96x1 is different from that of the 1140 and the user experience is not the same.
This is especially true for soft keys on Device Adapter. For example, a Transfer soft key on a Device Adapter UNIStim endpoint has a call appearance or bridged appearance attached to it. Device Adapter maps the user’s pressing of the Transfer soft key to the equivalent of a 96X1 user seizing a call appearance for a call transfer, including the call being on hold. Device Adapter then sends any transfer key specific SIP messages that are sent by a 96x1.
Therefore, the additional call appearance appears on the 96x1 and can be used in the Avaya Aura® user experience model.
You must also consider the number of keys for the 96x1 that uses the Device Adapter station profile. If the Avaya Aura® SIP endpoint has more programmable buttons, then the endpoint remains functional, but the key expansion modules do not map appropriately. An 18 button Key Expansion Module does not map to a 12 or 24 button Key Expansion Module.