QUESTION 14You are creating a SIP Entity for Avaya Aura® Engagement Development Platform – EDP / Avaya Breeze™.What do you have to enter in the field labelled FQDN or IP Address?

A. the Management IP-Address or FQDN of the Avaya Breeze™ platform.B. the SM100 IP-address or FQDN of the Avaya Breeze™ platformC. the IP-Address or FQDN of Core Platform ClusterD. the IP-Address or FQDN of general Purpose Cluster

A. It captures Packet-Size statistics from every telephone call in Avaya Aura® 7.B. It captures real-time XMPP traffic.C. It captures Voice and Video Calls media packets in real-time.D. It captures live traces for both SIP and H323/XMPP clients.E. It captures Contact details from every user connected to Avaya Aura® Presence Services.

Answer: BDExplanation:It’s important to know that traceSM is a real-time capture tool.traceSM is an interactive perl script that allows an administrator to capture, view, and save call processing activity on a Session Manager. While not as powerful or versatile as wireshark, traceSM is absolutely essential when it comes to working with Avaya SIP. First off, it allows you to view SIP messages even if they have been encrypted with TLS.https://andrewjprokop.wordpress.com/2014/06/02/a-necessary-guide-to-the-avaya-tracesm-utility/

A. It allows multi-media services over a standard Web-Browser.B. It allows independent management capabilities to filter out undesired message to every Avaya Aura® Presence Services user.C. It collects statistics about Port-Usage from each Presence-compatible endpoint across the network.D. Port 5222 is used for one-X?Endpoints, while Port 5269 is open for connecting with other XMPP 3rd- Party Servers.

Answer: DExplanation:Port 5222: XMPP connection configurationThe Connection Manager runs by default when you install the XCP server. It is configured with a JSM Command Processor and two XMPP directors. The XMPP directors handle communication with IM clients.One of the directors is configured to use port 5222 and the other is configured to use port 5223 for secure communications.Port 5269:Example Obtaining the Server-to-Server Port from an Openfire server Procedure1. Log in to the Openfire Web console.2. Click Server > Server Settings > Server to Server.3. In the Service Enabled section, the Enabled check box should be checked, and the port value is contained in the box to the right of Remote servers can exchange packets with this server on port.By default the value is 5269, and it is recommended that this default value be maintained.https://downloads.avaya.com/css/P8/documents/100180467

Answer: BExplanation:Verifying that Presence Services snap-in is ready to support Presence and IM Procedure1. On the System Manager web console, navigate to Elements > Avaya Breeze> Cluster Administration.2. Locate the row for the cluster, and verify that:* The Cluster Profile field shows Core Platform.etc.https://downloads.avaya.com/css/P8/documents/101013646

QUESTION 19Avaya Aura® Presence Services 7.x is implemented on Avaya Breeze™ (formerly known as Engagement Development Platform (EDP)).When looking at Elements > Engagement Development Platform > Service Management, which status would you expect for a Presence Services snap-in that is ready to support Avaya Aura® Presence Services?

QUESTION 20Which statement about the SIP Entities to support Avaya Aura® Presence Services is true?

A. Only one SIP Entity is built of Type = “Presence Services”, which uses the SM100 IP address of the Avaya Breeze™ node.B. Only one SIP Entity is built of Type = “Engagement Development Platform”, which uses the SM100 IP Address of the Avaya Breeze™ node.C. Two SIP Entities are built to the same SM100 IP address of each node. One is of Type = “Engagement Development Platform”, and the other is of Type = “Other”.D. Two SIP Entities are built to the same SM100 IP address of each node. One is of Type = “Engagement Development Platform”, and the other is of Type = “Presence Services”.

Answer: BCDExplanation:BD: Administering Entity Link between Presence Services Cluster SIP Entity and Session Manager Procedure1. On the System Manager web console, navigate to Elements > Routing > Entity Links.2. In the Name field, enter a name for Entity Link.3. In the SIP Entity 1 field, select the Session Manager instance.4. In the Protocol field, select TLS.5. In the Port field, type 5062.Note: Note that this port number cannot be the same as the port number administered in “Administering Entity Link between Avaya Breeze and Session Manager”.CD: Administering Entity Link between Avaya Breeze and Session Manager.About this taskCreate an En2tity Link to connect Session Manager to Avaya Breeze. You must administer separate Entity Links for Avaya Breeze servers in order to open SIP listeners on the designated ports.Session Manager requires a Listen Port with the Listen Port as 5061, Protocol as TLS, and Default Domain as the login domain of endpoint devices. Without this, PPM will fail for SIP endpoints.https://downloads.avaya.com/css/P8/documents/101013646

QUESTION 22In the context of Avaya Aura® Presence Services 7.x, what is a Fetcher?

A. It is a kind of watcher that requests a one-time view of the user’s current presentity information, but does not get future presentity information for a user.B. It is a user whose devices are sending status or presentity information on his behalf using a Publish message regarding his communication status.C. It is a watcher that is subscribing to current and future presentity information from another user.D. It is the presence information about a user that the system reports.

Answer: AExplanation:Fetchers pull the value of presence information for a specific presentity from the presence service. If a fetcher is fetching information on a regular basis, it is called a poller. Subscribers, on the other hand, subscribe to presentity information on the presence service.