Using the Cluster Session Manager, you can administer a list of unique node names having Session Manager IPs that are configured on Communication Manager. This eliminates the need for provisioning trunks for redundancy. This feature frees up trunks so that the available trunks can be used by SIP agents, SIP stations, or PSTN bound SIP trunk calls. You can also can generate reports for displaying the status of active and idle trunks.

With Cluster Session Manager, you can manage up to 10 clusters, and each cluster can manage up to 28 Session Managers. From the Manage Users page, you can define the Primary Session Manager and the Secondary Session Manager. If the call to the SIP station is routed to a SIP trunk that has a clustered signaling group, then the Invite is sent to the station on primary Session Manager. If the primary Session Manager is not reachable, then the Invite is sent to the station on secondary Session Manager.

Using the Signaling Groups page, you can access the Communication Manager CLI and administer the Clustered and Cluster ID fields. These fields appear for SIP signaling groups only. For more information, see Cluster Session Manager chapter in Avaya Aura® Communication Manager Screen Reference and SIP trunk optimization chapter in Avaya Aura® Communication Manager Feature Description and Implementation.