• Use the same CS1K_IP or CS1K_IPCC station definition for endpoint types with similar capabilities only. For example, a 12 feature key station definition should only be used with the 12 feature key endpoint devices.
  However, you can use the same station definition with endpoint types that have different capabilities for emergency purposes, provided that you configure the lowest indexed button as a call appearance button.
  When the endpoint has fewer buttons or display lines than the station definition, these buttons and the associated services along with the display lines are lost on the endpoint.
• When you want to use stations with divergent capabilities, then to avoid loss of keys, Avaya recommends that you use an endpoint with the least number of keys as the primary station. Ensure that you configure the most crucial features and at least one call appearance for the buttons available on the primary station.
  The station data that is sent to Device Adapter is according to the template that is generated by the station definition. Device Adapter modifies the information to ensure maximum compatibility with the endpoint that is being registered, although, there might be some loss of keys. The 96x1 and other SIP endpoints use a similar data conversion for compatibility with the SIP stations.
  For more information, see Sequential Registration with two or more Device Adapter UNIStim endpoints and one or more Avaya Aura SIP endpoints.
• Ensure that the endpoint supports the programmable feature buttons that you have defined in the CS1K_IP or CS1K_IPCC station definition.
• Ensure that the expansion module supports the same number of feature buttons that you have defined in the CS1K_IP or CS1K_IPCC station definition.
• Avoid configuring essential buttons on the expansion modules.

Caveats

• Capability mismatch due to changes in the number of available buttons is beyond the scope of Device Adapter. Avaya recommends that you register the migrated CS 1000 endpoints to user stations with equal number of programmable buttons. If necessary, the user can register and have fewer buttons, but that is a limitation of the device used.
• There might be some user experience differences if the user switches between the migrated CS 1000 endpoint and the Avaya Aura® SIP endpoint. For example, some feature buttons on the Device Adapter endpoint are included in the feature list of the 96x1 and other Avaya Aura® SIP endpoints. You can access this feature list by using the scrollable menu on the 96x1 and Avaya Aura® SIP endpoints. Therefore, a feature that uses a feature button on the 1140 uses a corresponding entry in the feature list of the 96x1 and other Avaya Aura® SIP endpoints to obtain a similar service operation.
• Legacy Avaya Aura® SIP devices have fewer significant caveats, although there might be an extra call appearance for the Transfer key. However, buttons on expansion modules may be lost in legacy Avaya Aura® SIP devices.