Configurations related to Avaya Aura® Session Manager for Avaya Device Adapter Snap-in

Last Updated : Dec 11, 2020 |
Avaya Device Adapter Snap-in uses the following features of Avaya Aura® Session Manager to perform tasks:
  • Avaya Device Adapter Snap-in performs challenge and authentication on behalf of an UNIStim or TDM station with Avaya Aura® Session Manager.
  • Avaya Device Adapter Snap-in indicates the signaling location of a call by the IP address located in the header of the INVITE request. Signaling locations must be administered using IP address patterns.
  • Avaya Device Adapter Snap-in indicates the media location of a call by the IP address located in the SDP.
For every Avaya Breeze® platform server running Avaya Device Adapter Snap-in, an additional SIP Entity of the Endpoint Concentrator type must be defined. Many Entity links between the SIP Entity and one or more Avaya Aura® Session Managers must also be defined. The Entity links must have a Connection Policy set to Endpoint Concentrator. An Avaya Aura® Session Manager Communication Profile must also be defined for every user or endpoint.
The location implies to the personnel who perform the migration and maintain the Device Adapter clusters.
This requires the following three levels in the hierarchy of configuration:
  • Location: The location of the site must be defined in the locations data. This allows the calls to receive different routing based on the site in question.
  • Network region: Each location has one or more network regions. For example, a university may have multiple campuses. Each campus may have multiple buildings, large buildings may have multiple floors, and each floor may be an individual region.
  • Network address map: Each IP subnet (or possibly every IP address) maps to a suitable network region. Each entry may also include a number allowing calls back from the PSAP.
For more information, see Appendix N: Location-based operations.