A customer called is stating they cannot place WebRTC calls. You discover that Avaya Breeze T™ has not been configured to allow Cross-origin Resource Sharing (CORS).
How would you allow cross-origin resource sharing for all?

• A.Use Avaya Aura® System Manager (SMGR) web GUI to access Breeze > Configuration > HTTP Security > HTTP CORS tab, the check the box Allow Cross-origin Resource Sharing for all.
• B.Use SSH to Avaya Breeze ™ and edit the /etc/config.properties file.
• C.Use Avaya Aura® System Manager (SMGR) web GUI to access the Inventory > Manage Elements.
  Edit
  the Avaya Breeze ™ element, and check the box Allow Cross-origin Resource Sharing.
• D.Use Avaya Aura® System Manager (SMGR) web GUI to access the Breeze > Configuration > Attributes, then select the webRTC attributes and check the box Allow Cross-origin Resource Sharing.

Comment: *

Name: *

Email: *

Verification: *

In which way can you check if the Avaya Session Border Controller (SBC) is using the correct server certificate?

• A.Using System Manager (SMGR), navigate to Services > Security > Certificates
• B.Using Avaya SBC, navigate to Dashboard > Security > Certificates
• C.Using System Manager (SMGR), navigate to Dashboard > TLS Management > Certificates
• D.Using Avaya SBC, navigate to Dashboard > TLS Management > Server Profiles

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.
In the Cluster Administration screen of a PresenceServices cluster, when you try to change the cluster state to Accept New Service, you receive the error:
Servers that are not in License Restricted mode assigned to the cluster are below the Minimum number of required servers.
You check that a server has been administered under Engagement Development Platform > Server Administration which shows green check under License Mode, and a System State of Denying.
Which action needs to be taken to solve this problem?

• A.Obtain and install an Avaya Breeze™ license on webLM with more instances of Avaya Breeze™ nodes.
• B.Edit the Cluster, access the Servers tab, and assign the server to the cluster; then set the cluster to Accept New Service.
• C.Under Engagement Development Platform > Server Administration, select the server and change the System State to Accept New Service, then return to the Cluster Administration screen and set the cluster to Accept New Service.
• D.Edit the cluster to change the cluster profile from Core Platform to General Purpose.

Comment: *

Name: *

Email: *

Verification: *

In which two Avaya Aura® Communication Manager (CM) System Administration Terminal (SAT) forms does the SIP domain need to be configured? (Choose two.)

• A.trunk-group
• B.ip-network-region
• C.ip-network-map
• D.signaling-group

Comment: *

Name: *

Email: *

Verification: *

Incoming SIP Trunking calls from Service Provider to Session Manager are failing because Avaya Session Border Controller for Enterprise (SBCE) is not sending a domain name in the TO, FROM and REQUEST headers.
What needs to be changed in SBCE to make this happen?

• A.In SBCE GUI, navigate to Global Profiles > Routing. Edit the Session Manager Routing Profile to link to a URI Group, which has the To, From and Request Headers and Replace Action set to Overwrite with domain name.
• B.In Avaya Session Border Controller for Enterprise (SBCE) GUI, navigate to Global Profiles > Server Configuration > Edit the Session Manager server entry to set "Overwrite Domain Name."
• C.In SBCE GUI, navigate to Device Specific Settings > Endpoint Flows > Server Flows. Edit the Session Manager flow to change the End Point Policy Group to default-low.
• D.In SBCE GUI, navigate to Global Profiles > Topology Hiding. Edit the SessionManager_TH to change the To, From and Request Headers Replace Action, to Overwrite with domain name.

Comment: *

Name: *

Email: *

Verification: *