Whore are the listening ports defined that allow Avaya Aura® Session Manager to listen for SIP traffic?

Question

Options

• ACommunication Profile
• BSM Firewall
• CSM Administration
• DSession Manager SIP Entity

• A
  6% (2)
• B
  3% (1)
• C
  3% (1)
• D
  87% (27)

Explanation

Session Manager SIP Entity (D) is where listening ports are configured because the SIP Entity record for Session Manager is the administrative object that defines how SM accepts inbound SIP traffic - including which ports (e.g., 5060 for UDP/TCP, 5061 for TLS) it listens on.

• A (Communication Profile) is a user-level construct that defines how an endpoint communicates, not how the Session Manager server listens for traffic.
• B (SM Firewall) is a distractor; while firewall rules may permit traffic on those ports, the port definitions themselves are not configured there.
• C (SM Administration) refers to the broader SM admin interface, but listening ports are configured within a specific object inside that interface - the SIP Entity - not at the top-level administration page.

Memory tip: Think of the SIP Entity as SM's "front door" - you define the door's address and which port numbers it answers on, right there in that entity's settings.

No community discussion yet for this question.