Which statement is true regarding Avaya Aura Communication Manager as a feature server for SIP Endpoints?

The statement that Avaya Aura Communication Manager (CM) must be added as an Application for Session Manager is accurate because, in the context of Avaya's architecture, Session Manager plays a critical role in interconnecting SIP endpoints and managing their registration.

For SIP endpoints to effectively communicate and be managed within an Avaya environment, they typically register with Session Manager rather than directly with the Communication Manager. However, Communication Manager can still act as a feature server for these endpoints. By designating Communication Manager as an application within the Session Manager, it allows Session Manager to route calls between the endpoints and manage features seamlessly, integrating various elements of the Avaya environment.

This integration leverages the capabilities of both systems, ensuring that the SIP endpoints can utilize Communication Manager's extensive feature set while being managed by Session Manager's control mechanism, which enhances scalability and flexibility.

Thus, adding CM as an Application for Session Manager is essential to ensure proper call routing and feature access for SIP endpoints, making it a vital part of the overall system architecture in Avaya's setup.