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

Question

Options

• ACommunication Profile
• BSM Firewall
• CSession Manager SIP Entity
• DSM Administration

• A
  6% (2)
• B
  3% (1)
• C
  91% (30)

Explanation

Option C is correct because in Avaya Aura, a Session Manager is represented as a SIP Entity in System Manager, and the Listen Ports (e.g., UDP/TCP 5060, TLS 5061) are configured directly on that SIP Entity - this tells the system which protocols and ports the SM will accept inbound SIP traffic on.

Why the distractors are wrong:

• A. Communication Profile - This is part of a user object, defining which Communication Manager or endpoints a user is associated with; it has nothing to do with SM port configuration.
• B. SM Firewall - While firewall rules govern what traffic reaches the SM, there is no "SM Firewall" configuration screen where Listen Ports are defined.
• D. SM Administration - This section handles system-level admin tasks (alarms, logs, maintenance), not SIP transport configuration.

Memory tip: Think "Entity = Endpoints." The SIP Entity is the Session Manager from the network's perspective - so all the "who I am and how to reach me" settings (including Listen Ports) live there, just as you'd configure ports on any network entity you're registering.

No community discussion yet for this question.