When adding a new Avaya Aura Session Manager (SM), where are its Listen Ports defined?

In Avaya Aura® System Manager, a Session Manager instance is represented as a SIP Entity. The configuration for this SIP Entity is where the core communication parameters are defined. This includes the FQDN or IP address of the Session Manager and, crucially, the specific transport protocols (TCP, UDP, TLS) and the corresponding port numbers on which the Session Manager will listen for incoming SIP traffic. This configuration is fundamental for routing and connectivity within the Aura environment.

A. Communication Profile: A Communication Profile is assigned to a user, not a system component. It defines the user's primary Session Manager for registration and feature access, but not the server's listening ports.

B. SM Firewall: The firewall permits or denies traffic on specific ports. It does not define which ports the Session Manager application actively listens on; it must be configured to allow traffic on the ports defined elsewhere.

D. SM Administration: This term is too general. While the configuration is performed within the Session Manager administration interface (System Manager), the specific location for defining listen ports is the SIP Entity page.

1. Avaya Aura® Session Manager Documentation, "Administering Avaya Aura® Session Manager" (Release 8.1.3, November 2021), Page 51, Chapter: "Administering Session Manager instances".

The section "Adding a Session Manager instance" states: "On the SIP Entity Details page, in the Port and Protocol Information section, click Add to add the ports on which Session Manager listens for SIP traffic." This explicitly confirms that Listen Ports are defined within the SIP Entity configuration.

2. Avaya Aura® System Manager Documentation, "Administering and Maintaining Avaya Aura® System Manager" (Release 8.1.3, November 2021), Page 487, Chapter: "Elements".

The section "SIP Entity Details fields" describes the configuration page for a SIP Entity. It details the "Port" field where administrators must "Enter the port number that the SIP entity uses to listen for SIP messages." This directly supports the answer.