SIP user 1011111 and SIP user 1011112 are both based on the same Session Manager with access to a CM Evolution server. Given the following actions: Session Manager searches for the called party in the SIP registry, finds it, registers it and routes the call to it. SIP user 1011111 calls SIP user 1011112, and an Invite request is sent to Session Manager. Session Manager verifies SIP user 1011111 in the SIP registry and authenticates it. Session Manager checks the SIP user's profile for sequenced applications and (in this example) routes the request to Communication Manager. Endpoints negotiate codecs and media, and RTP is sent between endpoints. Communication Manager receives the request from Session Manager, carries out full-call model processing for both endpoints, and routes the call back to Session Manager. If 1011111 makes a call to 1011112, in which order will the actions take place?
An IP (AST) user 1011111 and H.323 user 1011711 share a common Communication Manager (Evolution) server. Given the following actions: CM will negotiate the codec for the H.323 endpoint based on CM configuration. Session Manager verifies SIP user 1011111 in the registry and authenticates it. After authenticating the SIP user, Session Manager checks the SIP user’s profile for sequence applications and routes the request to Communication Manager. Communication Manager performs feature processing and terminates the call to the H.323 endpoint. If SIP user 1011111 calls H.323 user 1011711, in which order will these actions take place?
What is the primary benefit of a Virtual (Intervening) Network Region in Avaya Aura® Communication
Manager?
What happens if Session Manager cannot find a matching SIP Communication Profile for a user in its SIP
registry when that user tries to make a SIP call?
© Copyrights DumpsEngine 2024. All Rights Reserved
We use cookies to ensure your best experience. So we hope you are happy to receive all cookies on the DumpsEngine.