71301X Exam Dumps - Avaya Certification Questions and Answers

To enable IM and Presence for an Avaya Aura® user, you need to edit the Communication Profile of the user in System Manager, under Users > User Management > Manage Users. In the Communication Profile tab, you need to assign an Avaya Presence/IM handle to the user, which is a unique identifier that follows the format username@domain.com. You also need to enable and configure the Presence profile for the user, which specifies the Presence Services snap-in that will provide presence and instant messaging features for the user.

The Avaya Spaces Calling extension is a softphone that provides calling features to users of Avaya Spaces by leveraging their existing Avaya infrastructure. This extension can be used alongside the Avaya Spaces web application or desktop client to make and receive audio calls through the Avaya Aura® Web Gateway (AAWG). To add the Avaya Spaces Calling extension, you need to have internet access and use the Google Chrome browser to open the Chrome Web Store. Then, you need to search for the Avaya Spaces Calling extension and click on the Add to Chrome button. The extension will be installed and added to your Chrome browser. You can then use the extension icon in the browser toolbar to access the Avaya Spaces Calling settings and features12

A user can retrieve a parked call by dialing the Park extension used to park the call. A Park extension is a virtual extension that is assigned to a parked call by the Call Park and Page snap-in on the Avaya Breeze® platform. A Park extension can be either system-wide or location-specific, depending on how the Call Park feature is configured. A system-wide Park extension can be accessed from any endpoint in any location, while a location-specific Park extension can only be accessed from endpoints in the same location as the parked call. When a user dials the Park extension of a parked call, the Call Park and Page snap-in transfers the call to the user’s endpoint12

When deploying Avaya Aura® Presence Services as a snap-in on a single Avaya Breeze® server, you need to create two SIP Entities for the same Avaya Breeze® server Security Module IP address or FQDN in System Manager. One SIP Entity is used for the Avaya Breeze® platform itself, and the other SIP Entity is used for the Presence Services snap-in. The type of the SIP Entity determines how Session Manager routes SIP messages to the Avaya Breeze® server. The type Avaya Breeze® indicates that the SIP Entity is a generic Avaya Breeze® server that canhost any snap-in. The type Presence Services indicates that the SIP Entity is a specific Avaya Breeze® server that hosts the Presence Services snap-in12

To connect to the Application Enablement Services (AES) web interface, you need to use the correct URL and the default login ID. The AES web interface is a web-based application that allows you to configure and manage the AES server and its features. You can access the AES web interface using any web browser that supports HTTPS. The URL for connecting to the AES web interface is https:// :8443, where is the IP address of the AES server that you want to connect to. The port number 8443 is the default port for HTTPS communication with the AES server. After entering the URL in the web browser, you will see a login screen where you need to enter the login ID and password for accessing the AES web interface. The default login ID for the AES web interface is craft, which is a system administrator account that has full access to all features and functions of the AES server. The default password for the craft account is craft. You can change the password or create other user accounts with different access levels using the Security Database feature of the AES web interface.

In the Avaya Session Border Controller for Enterprise (ASBCE), the state of a Network Interface, after the deployment, is Disabled. A Network Interface is a logical interface that represents a physical port on the ASBCE server. A Network Interface can be configured with an IP address, subnet mask, gateway, and VLAN ID. After the deployment of the ASBCE server, the Network Interfaces are in a Disabled state by default. To enable a Network Interface, you need to use the ASBCE web interface or CLI and configure the interface parameters. You also need to assign the interface to a Zone, which is a logical grouping of interfaces that defines the security and routing policies for the ASBCE server

To allow communications between the Avaya Aura® Device Services (AADS) and the Avaya Aura® Web Gateway (AAWG), you need to perform the following configuration steps:

• Configure the AAWG FQDN as a Trusted Host on the AADS: A Trusted Host is an entity that is allowed to communicate with the AADS server using HTTPS or REST APIs. You need to configure the Fully Qualified Domain Name (FQDN) of the AAWG server as a Trusted Host on the AADS server, using the System Manager web interface. This allows the AAWG server to access the AADS server for device management and configuration purposes3
• Configure the AADS FQDN as a Trusted Host on the AAWG: Similarly, you need to configure the FQDN of the AADS server as a Trusted Host on the AAWG server, using the app configure command line utility. This allows the AADS server to send dynamic configuration parameters and certificates to the AAWG server for WebRTC call signaling and media processing4
• Configure the AADS FQDN, Client interface port and Server-to-server interface port on the AAWG: You also need to configure the FQDN, Client interface port and Server-to-server interface port of the AADS server on the AAWG server, using the app configure command line utility. These parameters are used by the AAWG server to establish secure connections with the AADS server for device management and configuration purposes. The default Client interface port is 9443, while the default Server-to-server interface port is 84434

When setting up the Avaya Session Border Controller for Enterprise (ASBCE) SIP Trunking, you need one Subscriber Flow and one Server Flow. A Subscriber Flow is a configuration object that defines how the ASBCE handles SIP requests and responses from or to an endpoint, such as an IP phone or a softphone. A Server Flow is a configuration object that defines how the ASBCE handles SIP requests and responses from or to a server, such as a Communication Manager or a Session Manager. For SIP Trunking, you need one Subscriber Flow that connects the ASBCE to the internal SIP server, and one Server Flow that connects the ASBCE to the external SIP service provider. These flows specify parameters such as source and destination IP addresses, ports, protocols, codecs, encryption, authentication, and routing rules3

In the context of Avaya Aura® Presence Services, a Watcher is a user who is interested in the presence information of another user, called a Presentity. A Watcher sends a Subscribe message to the Presence Services snap-in on the Avaya Breeze® server, requesting to receive notifications about the current and future presence status of the Presentity. The Presence Services snap-in then sends a Notify message to the Watcher, containing the presence information of the Presentity. The Watcher can use this information to decide how and when to communicate with the Presentity12

In some deployments, you can enable a feature called “Stream Users Over Transport Link” in the Signaling Interface used for the Avaya Aura® Session Manager (SM) on the Avaya Session Border Controller for Enterprise (ASBCB). This feature allows reusing the same TCP connection to SM for all SIP messages related to Remote Workers registered with SM through ASBCB. A Signaling Interface is a configuration object that defines how ASBCB handles SIP signaling with other entities, such as endpoints or servers. A Signaling Interface can include parameters such as source and destination IP addresses, ports, protocols, encryption modes, authentication modes, and timers. The “Stream Users Over Transport Link” parameter is an option that can be enabled or disabled in the Advanced tab of the Signaling Interface configuration screen. When this option is enabled, ASBCB will use the same TCP connection to SM for all SIP messages related to the same Remote Worker. This can reduce the number of TCP connections and improve the performance and scalability of ASBCB and SM.