In the Session Manager Communication Profile section, you can associate a primary Session Manager instance as a home server for the currently displayed communication profile. As a home server, the selected primary Session Manager instance is used as the default access point for connecting devices associated with the communication profile to the Avaya Aura® network.

All communication addresses of type SIP for the communication profile are associated with the Avaya Aura® network. If you select a secondary Session Manager instance, Session Manager provides continued service to SIP devices associated with this communication profile when the primary Session Manager is unavailable. You can also administer a third and fourth Session Manager to a communication profile for redundancy service if the policy-based assignment of Session Manager feature is enabled.

You can configure the system to invoke application sequences when routing calls from (origination) or to (termination) the currently displayed user.

You can specify a conference factory set for users for improved voice, video, and text conferencing.

For local survivability, you can specify a survivability server. The server provides survivability communication services for devices associated with a communication profile, when local connectivity to Session Manager instances in the Avaya Aura® core is lost. If you select a Branch Session Manager, and the termination and origination application sequences contain a Communication Manager application, sequencing to this application continues locally to the Communication Manager remote survivable server resident with the Branch Session Manager.

When this user calls numbers that are not associated with an administered user, the system applies dial-plan rules to complete the call based on this home location if the IP address of the SIP device used to make the call is unassigned to a location.