Free Practice Questions for Avaya 71301X Exam

When configuring a Reverse Proxy for the Avaya Aura® Web Gateway (AAWG) in the Avaya Session Border Controller for Enterprise (ASBCE), the Server Address field is used to specify the IP address or FQDN and port of the AAWG server. The port used in this field shouldmatch the listen port on the AAWG server that is used for all WebRTC call signalling. The default listen port on the AAWG server is 8444, which is also used by default in the Server Address field of the ASBCE Reverse Proxy configuration. The Reverse Proxy allows external clients to access the AAWG server securely and transparently through the ASBCE

To associate the Avaya Call Park and Page snap-in to an Avaya Workplace Client, you need to perform the following key configuration steps:

Add a Service Profile: A Service Profile is a set of parameters that defines the features and capabilities of a user or device in System Manager. You need to create a Service Profile for the Call Park and Page snap-in, under Users > User Management > Service Profiles. In the Service Profile, you need to specify the name, type, domain, and SIP Entity of the Call Park and Page snap-in. You also need to enable the Call Park feature and configure the Call Park activation and deactivation feature codes1

Configure a Call Park activation and deactivation feature code: A feature code is a numeric sequence that activates or deactivates a specific feature on Communication Manager. You need to configure a Call Park activation and deactivation feature code on Communication Manager, using the change feature-access-codes command. The Call Park activation feature code allows a user to park a call on a specified extension, while the Call Park deactivation feature code allows a user to retrieve a parked call from any extension2

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

After deploying Avaya Aura® Web Gateway (AAWG) in a Virtualized Environment (VE), the next step is to enroll AAWG with System Manager (SMGR) by running the initTM command on the AAWG CLI. The initTM command is used to initialize the trust management between the AAWG server and the SMGR server. This command requires an enrollment password that is configured in the SMGR web interface, under Security > Enrollment Password. The enrollment password has a validity period that can be set by the administrator. If the enrollment password has expired, the initTM command will fail. Therefore, before running the initTM command, you should verify that the enrollment password is configured and valid

A Server Interworking Profile is a type of a Configuration Profile in the Avaya Session Border Controller for Enterprise (ASBCE) that allows setting Timers, URI Manipulation and Header Manipulation, and can be linked to a SIP Server Profile. A Configuration Profile is a configuration object that defines how the ASBCE server handles different aspects of SIP signaling and media processing. A Server Interworking Profile is a Configuration Profile that defines how the ASBCE server interworks with different types of SIP servers, such as Communication Manager, Session Manager, or third-party servers. A Server Interworking Profile can include parameters such as Timers, which specify the timeout values for various SIP transactions; URI Manipulation, which specifies how to modify the user part or domain part of SIP URIs; and Header Manipulation, which specifies how to add, delete, or modify SIP headers. A Server Interworking Profile can be linked to a SIP Server Profile, which is another Configuration Profile that defines the identity and characteristics of a SIP server that communicates with the ASBCE server.

The initTM -f command is used to initialize the trust management between the Avaya Breeze® server and the Avaya Aura® System Manager. This command requires an enrollment password that is configured in the System Manager web interface, under Security > Enrollment Password. The enrollment password has a validity period that can be set by the administrator. If the enrollment password has expired, the initTM -f command will fail. Therefore, before running the initTM -f command, you should verify that the enrollment password is configured and valid12

Avaya Session Border Controller for Enterprise (ASBCE) can be deployed on the Kernel-based Virtual Machine (KVM) infrastructure. KVM is a virtualization technology that allows multiple operating systems to run on a single physical machine. To deploy ASBCE on KVM, you need to use a template file that contains the ASBCE software image and configuration parameters. The template file type to be used for KVM deployment is QCOW2, which stands for QEMU Copy-On-Write version 2. QCOW2 is a file format for disk images that can be used by QEMU, which is an open source emulator and virtualizer that can run KVM virtual machines. QCOW2 files support features such as compression, encryption, snapshots, and backing files

Avaya Aura® Presence Services uses different ports for different purposes. Port 5222 is used by endpoints like Avaya one-X® Communicators, Avaya Equinox®, or Avaya IX™ Workplace to establish client-to-server XMPP connections with the Presence Services snap-in on the Avaya Breeze® server. Port 5269 is used for server-to-server XMPP connections with the third-party XMPP servers, such as Google Talk or Jabber. These ports enable the presence and instant messaging features for the users34

The Avaya Aura® Media Server (AAMS) associated with the Avaya Aura® Web Gateway (AAWG) is used for media processing for calls to or from Avaya Spaces Calling. Avaya Spaces Calling is a softphone that provides calling features to users of Avaya Spaces by leveraging their existing Avaya infrastructure. When a user makes or receives a call using Avaya Spaces Calling, the AAWG handles the WebRTC call signaling and the AAMS handles the media. The AAMS converts the WebRTC media to SIP media and vice versa, and provides services such as announcements, music on hold, conferencing, transcoding, and recording. The AAMS processes the media for the duration of the call, regardless of whether the call is shuffled or not by Communication Manager