The following is a list of the key features of the Avaya Device Adapter Snap-in solution:
Existing CS 1000 server components such as the Terminal Proxy Server (TPS) and the Personal Directory are migrated to the Avaya Device Adapter Snap-in as an integral part of the Avaya Device Adapter Snap-in.
Existing CS 1000 endpoints interact directly with the snap-in.
Terminal adaptation from CS 1000 Stimulus to Avaya SIP Telephony (AST) is implemented on the Avaya Device Adapter Snap-in.
Provisioning of the Avaya Device Adapter Snap-in configuration is done through the Avaya Breeze® platform Service Attributes.
The Avaya Aura® System Manager administers all CS 1000 endpoints.
CS 1000 style Park and Page functionality is available when Avaya Device Adapter Snap-in is paired with Avaya Call Park and Page Snap-in.
Note:
Avaya Call Park and Page Snap-in must be deployed in a dedicated Avaya Breeze® platform cluster to enable this functionality.
Avaya Device Adapter Snap-in uses the ProVision/NMT utility to migrate most CS 1000 endpoint data to Communication Manager stations.
Communication Manager supports administering the CS 1000 endpoints as Avaya SIP Telephony (AST) endpoints connected to Session Manager.
The Avaya Device Adapter Snap-in-based solution supports High Availability and Geo-redundant operation to preserve call connection and state of CS 1000 endpoints.
Corporate directory support using Avaya Aura® Device Services.
