Aura Core Components Technical Associate Support Free Sample Questions

In Avaya Session Manager, if an INVITE receives a '404 Not Found' generated locally by the SM (not relayed from a downstream entity), it typically indicates that the Routing Engine could not find a matching Dial Pattern for the specific location or domain of the caller. If the trunk were down, SM would attempt to route and likely return a 408 Request Timeout or 503 Service Unavailable.

For a TLS connection to be established, the Session Manager must trust the certificate presented by the remote entity. This requires the Root CA certificate of the third-party PBX to be imported into the System Manager's Trust Management Service and replicated to the Session Manager. Without this, the handshake will fail with a 'Certificate Unknown' or similar error.

Avaya Aura Session Manager (SM) is the core SIP routing engine. It centralizes the dial plan, handles SIP user registrations, and normalizes signaling between different vendors and systems using Adaptations. Communication Manager handles features and call control, while System Manager is the management interface.

If the call is set up with Direct Media (Shuffling), the media stream (RTP) goes directly between the two endpoints (peer-to-peer). Communication Manager or Media Gateway DSP resources are NOT involved in the media path after the initial setup. If the endpoints cannot route to each other's IPs, silence occurs. Disabling direct media (hairpinning) would force audio through a Media Gateway/Server, potentially fixing the routing issue by using the gateway as a proxy.

This statement is generally False in terms of service impact. While System Manager is down, you cannot make administrative changes, and services relying on real-time queries to SMGR (like WebLM licensing if co-resident) might buffer or enter a grace period, but active call processing on Session Manager and Communication Manager continues uninterrupted. They function autonomously for call routing.

Adaptations in Session Manager are used to manipulate SIP headers and digits (ingress or egress) on a per-entity basis. You would configure a 'DigitConversionAdapter' and apply it to the SIP Entity link for the Service Provider to strip headers or modify numbers before routing.

Denial event 1183 usually indicates an incompatibility in the bearer capability or codec negotiation. This often happens when the IP Network Regions of the two endpoints (or endpoint and trunk) do not have a common codec defined in their respective Codec Sets, or the inter-region connectivity is blocked.

System Manager supports backing up data to a remote server using SFTP (Secure File Transfer Protocol) or SCP. This is the recommended method for disaster recovery.

Backups can also be stored locally on the System Manager server itself, although off-box storage is best practice. The local directory is typically within the /var partition structure.

AADS connects to the enterprise directory (like Active Directory) using LDAP or LDAPS to authenticate users and retrieve their configuration profiles. LDAPS (Port 636) is the standard secure method for this integration.

To strictly enforce local routing for emergency calls, you define the Originating Location (Branch A). The Dial Pattern for 911 is tied to this location. The Routing Policy selected by this Dial Pattern must contain only the local gateway. If you added other gateways as secondary choices in the Routing Policy (or used a Time of Day list with alternatives), the call would overflow, violating the requirement.