71301X Exam Dumps - Avaya Aura Communication Applications Implement Certified Exam

A Service Profile is a configuration mechanism that allows an administered group of snap-ins to be invoked in a specified order. A Service Profile defines the name, type, domain, and SIP Entity of a snap-in, as well as the features and parameters that are enabled for the snap-in. A Service Profile can also include other snap-ins as sub-services, which are invoked in a sequential or parallel manner. A Service Profile can be assigned to a user or a device in System Manager, under Users > User Management > Service Profiles2

Before obtaining a server identity certificate from a Certificate Authority (CA) for the installation on the Avaya Session Border Controller for Enterprise (ASBCE), you need to generate a Certificate Signing Request (CSR). A CSR is a file that contains information about the identity and public key of the ASBCE server, as well as a digital signature that proves the ownership of the public key. A CSR is used to request a server identity certificate from a CA, which is an entity that issues and verifies certificates. The CA will check the information in the CSR and issue a server identity certificate that contains the same information and public key, as well as the CA’s signature and validity period. The server identity certificate is used to authenticate the ASBCE server to other entities that communicate with it using HTTPS or SIP over TLS. To generate a CSR for the ASBCE server, you can use tools such as OpenSSL or Keytool, or use the ASBCE web interface or CLI.

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

If the Avaya Session Border Controller for Enterprise (ASBCE) does not trust the Certificate Authority (CA) that signed the WebLM server identity certificate, you can use the sbceconfigurator.py fix-weblm-cert command issued from the EMS CLI to fix the trust issue. The WebLM server is a web-based licensing application that manages licenses for various Avaya products, such as Communication Manager, Session Manager, Presence Services, or Breeze Platform. The WebLM server uses an identity certificate to authenticate itself to other entities that communicate with it using HTTPS or REST APIs. The identity certificate is signed by a CA, which is an entity that issues and verifies certificates. The ASBCE server needs to trust the CA that signed the WebLM server identity certificate in order to communicate with it securely and obtain licenses from it. If the ASBCE server does not trust the CA, you can use the sbceconfigurator.py fix-weblm-cert command to install the CA certificate on the ASBCE server and establish trust with it. The sbceconfigurator.py tool is a Python script that runs on the EMS component of the ASBCE server and performs various configuration tasks. The EMS component is responsible for managing and monitoring the ASBCE server. You can access the EMS CLI using SSH or Telnet and run the sbceconfigurator.py tool from there.

The Avaya Session Border Controller for Enterprise (ASBCE) certificate management is a feature that allows you to install, manage, and renew certificates for the ASBCE server. Certificates are used to authenticate and encrypt the communication between the ASBCE server and other entities, such as endpoints, servers, or service providers. The following statements about the ASBCE certificate management are true:

• It allows using a default server certificate for up to one year after the installation: The ASBCE server comes with a default self-signed server certificate that can be used for testing or demonstration purposes. The default server certificate is valid for one year from the date of installation. After one year, the default server certificate expires and needs to be replaced with a valid certificate from a trusted Certificate Authority (CA).
• It supports both the Root and Intermediate Certificate Authority (CA) certificates: The ASBCE server supports installing both the Root and Intermediate CA certificates, which are used to verify the identity and trustworthiness of other certificates. A Root CA certificate is a certificate that is issued by a trusted authority and is self-signed. An Intermediate CA certificate is a certificate that is issued by a Root CA or another Intermediate CA and is used to sign other certificates. The ASBCE server can store up to 10 Root CA certificates and up to 10 Intermediate CA certificates.

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.

Application Enablement Services (AES) communicates with Avaya Aura® Communication Manager (CM) using SIP, which is a protocol for initiating and managing multimedia sessions, such as voice, video, or instant messaging. AES is a server that provides APIs and interfaces for developing and integrating CTI applications with CM and other Avaya Aura® Platform components. AES supports various APIs and interfaces, such as TSAPI, JTAPI, DMCC, Web Services, and ASAI. AES uses SIP to communicate with CM for various purposes, such as registering endpoints, sending and receiving SIP messages, controlling calls, and capturing media. AES also uses SIP to communicate with other Avaya Aura® Platform components, such as Session Manager (SM), System Manager (SMGR), Presence Services (PS), or Breeze Platform.

To provide the customized music, prompts, and/or error announcements when using the Avaya Call Park and Page snap-in, you need to use the Avaya Aura® Media Server (MS). The Media Server is an application that provides media processing services for voice and video calls, such as playing announcements, music on hold, conferencing, transcoding, and recording. The Media Server can be integrated with the Call Park and Page snap-in on the Avaya Breeze® platform, using SIP trunks and media resources. You can upload your own audio files to the Media Server and configure them as custom announcements for the Call Park and Page snap-in34

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 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.

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

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

Avaya Breeze® is a development platform that enables rapid development for applications targeted to meet a customer’s communications needs. It is used by Avaya, Partner, and third-party developers to create and deploy snap-ins, which are modular software components that provide specific functionality or features. Avaya Breeze® allows application developers to quickly add new capabilities to their Avaya solutions, such as voice, video, messaging, presence, collaboration, and analytics.

The Avaya Session Border Controller for Enterprise (ASBCE) provides an integrated (local) WebLM server that can be used to install and manage licenses for the ASBCE server. The local WebLM server is only supported in a single-server hardware-based deployment, which is a deployment where the ASBCE server runs on a dedicated hardware appliance, such as an Avaya SBCe 1U or 2U server. In this deployment, the local WebLM server runs on the same hardware appliance as the ASBCE server and can be accessed using the ASBCE web interface or CLI. The local WebLM server can store up to 10 license files and can handle up to 5000 concurrent sessions.

The tracePS CLI tool is a command-line interface tool that allows you to capture and analyze XMPP traffic between Avaya Aura® Presence Services and other XMPP servers or clients. You can use this tool to troubleshoot issues related to presence, instant messaging, federation, or integration with third-party applications. You can also use this tool to generate reports on XMPP traffic statistics, such as message count, message size, message type, and message direction1

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