71300X Avaya Aura Communication Applications Integration Exam Questions and Answers

A trust relationship based on certificates must be built to make WebRTC work.

No trust relationship exists between enterprise edge security and web browsers; therefore, the security strategy is based on an Authorization Token instead.

There must be a VPN connection between the Web Browser and the Enterprise-edge to build a WebRTC link.

WebRTC only works within the Enterprise network. External Web Browsers must connect through an Avaya Session Border Controller for Enterprise (SBCE) via a SIP trunk.

Automatic mode

Real-time mode

Ladder mode

Summary-time mode

Non real-time mode

ICE

SRTCP

TURN

HTTPS

STUN

traceSBC

traceCE

traceSM

tracePRS

tracePS

The Avaya SBC secures and authenticates Integrated Services Digital network (ISDN) calls placed to/from

the Public Switched Telephone Network (PSTN).

The Avaya SBC is the enabling and secure pivot point for SIP Communications in and out of the

Enterprise.

The Avaya SBC is a service within System Manager (SMGR) to support deployments.

The Avaya SBC is the enabling and secure pivot point for H.323 Communications in and out of the

Enterprise.

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.

It is a user whose devices are sending status or presentity information on his behalf using a Publish message regarding his communication status.

It is a watcher that is subscribing to current and future presentity information from another user.

It is the presence information about a user that the system reports.

Two addresses are assigned to the private NIC and two addresses are assigned to the public NIC.

One address is assigned to the private NIC and one address is assigned to the public NIC.

Two addresses are assigned to the private NIC and one address is assigned to the public NIC.

One address is assigned to the private NIC and two addresses are assigned to the public NIC.

In ‘ip-services’ form on Avaya Aura® Communication Manager (CM) and in ‘TSAPI link’ on Avaya Aura® Application Enablement Services (AES)

In ‘ip-services’ form on Avaya Aura® Communication Manager (CM) and in ‘Switch Connection’ on Avaya Aura® Application Enablement Services (AES)

In ‘cti-link’ form on Avaya Aura® Communication Manager (CM) and in ‘Switch Connection’ on Avaya Aura® Application Enablement Services (AES)

In ‘cti-link’ form on Avaya Aura® Communication Manager (CM) and in ‘TSAPI link’ on Avaya Aura® Application Enablement Services (AES)

Use SSH to Avaya Breeze ™ and edit the /etc/config.properties file.

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.

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.

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.

Load the Snap-in.

Download and Install WebRTC License file.

Busy and Release the WebRTC snap-in.

Manually configure the WebLM IP address in the WebRTC configuration attributes.

Install the Snap-in.

A CTI link must be configured on Avaya Aura® Communication Manager (CM) first.

A Switch Connection must be configured on Avaya Aura® Application Enablement Services (AES) first.

A signaling-group must be configured on Avaya Aura® Communication Manager (CM) first.

A CTI-user must be configured on Avaya Aura® Application Enablement Services (AES) first.