If you have some other device or application; for example, Expert Client or 96x1, in addition to two or more Device Adapter UNIStim stations, the same general feature interaction applies as when you configure Sequential Registration for multiple UNIStim endpoints without the Avaya Aura® endpoints.

Furthermore, if a Device Adapter station definition is used as the primary station definition and an Avaya Aura® SIP endpoint uses this station definition, the user experience on the Avaya Aura® SIP endpoint differs.

For example, a user has a 1140, a 2050 soft client, and a 96x1 SIP phone. The user may register with the Avaya Aura® SIP device, terminating the registration of the Device Adapter endpoint, which can be either the 1140 hard client or the 2050 soft client. However, the operation of the 1140 and the 96x1 are different, most feature buttons on the Device Adapter station map to the feature list on the 96x1, and the user experience of the feature buttons that are on both the CS 1000 endpoint and the Avaya Aura® endpoint is not the same.

This is especially true for the definition and handling of some context-sensitive 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 action of the user pressing the key to the equivalent of:

Conversely, a 96x1 or any other Avaya Aura® SIP phone that uses this station definition has one or more additional call appearance buttons. The additional call appearance behind the transfer soft key on the UNIStim phone appears as a new call appearance, with the button labeled transfer. This provides the line appearance that is crucial for allowing the transfer to be carried out.

This button is configured to reserve a call appearance for outgoing calls used for Transfer and Conference. Therefore, the additional call appearance appears on the 96x1 and can be used in the Avaya Aura® user experience model. No visible button exists on the Device Adapter UNIStim phone.

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, if the UNIStim endpoint has key expansion modules, 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.

Some feature buttons on the Device Adapter endpoint are included in the feature list on the 96x1 and other Avaya Aura® SIP endpoints. You can access this feature list by using the scrollable menu on the 96x1 and the Avaya Aura® SIP endpoints. Therefore, a feature that uses a feature button on the 1140 potentially uses a corresponding entry in the feature list of the 96x1 and other Avaya Aura® SIP endpoints to obtain a similar service operation whenever the CS1K-IP definition maps to a 96X1, J-series, or Expert Client.