Free and Premium Avaya 71301X Dumps Questions Answers

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 does not require a separate license file or an instance license. User licenses are an entitlement as part of the Avaya Aura® suite licensing, such as Foundation, Mobility, Team Engagement, or Customer Engagement. The user licenses are consumed based on the number of users who are provisioned for Presence Services in System 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.

An H.248 signaling link connects the Internet Friendly (Edge) Gateway to Avaya Communication Manager (CM) by tunneling H.248 messages using TCP port 2944 and securing them using TLS. H.248 is a protocol that defines how media gateway controllers control media gateways for supporting multimedia streams across different networks, such as IP networks and PSTN networks. An H.248 signaling link is a logical connection between an H.248 controller and an H.248 gateway that allows exchanging H.248 messages for controlling media streams. In an Internet Friendly (Edge) Gateway scenario, CM acts as an H.248 controller and ASBCE DBE acts as an H.248 gateway. To connect an H.248 signaling link between CM and ASBCE DBE, these steps are performed:

• CM initiates a TCP connection to ASBCE DBE using port 2944, which is reserved for H.248 over TLS.
• CM and ASBCE DBE negotiate TLS parameters and exchange certificates for mutual authentication and encryption.
• CM and ASBCE DBE establish a secure TLS session over TCP port 2944.
• CM and ASBCE DBE exchange H.248 messages over TLS session for controlling media streams.

When registering as a Remote Worker via the Avaya Session Border Controller for Enterprise (ASBCE), you should configure the ASBCE External (Public) Interface IP address allocated for Remote Workers in the Server List of the Avaya one-X® Communicator. The ASBCE External (Public) Interface is the interface that connects the ASBCE server to the public Internet and allows communication with external entities, such as Remote Workers or SIP service providers. The ASBCE server acts as a proxy for the Remote Workers and handles the SIP registration and call signaling with the Avaya Aura® Session Manager (SM). Therefore, you need to specify the ASBCE External (Public) Interface IP address as the SIP server address in the Avaya one-X® Communicator settings

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.

An Avaya Workplace client learns about a Survivability Server assigned in its User Profile from the Avaya Aura® Device Services (AADS) via the Dynamic Configuration. TheDynamic Configuration is a set of parameters that are sent by the AADS to the Avaya Workplace client during login or registration. The Dynamic Configuration contains information such as the SIP domain, SIP proxy, SIP registrar, and Survivability Server for the Avaya Workplace client. The Survivability Server is an Avaya Aura® Communication Manager instance that provides call processing and voice mail access for the Avaya Workplace client in case of a network failure or loss of connectivity with the core servers34

 tracePS is a CLI 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 direction

The CLI tool that is used to trace messages in real-time as they pass through the Avaya Session Border Controller for Enterprise (ASBCE) is tracesbc. The tracesbc tool is a CLI tool that runs on the SBC component of the ASBCE server and captures and displays SIP messages and media statistics for calls that traverse the ASBCE server. You can use various filters and options to specify which calls or messages you want to trace. For example, you can filter by source or destination IP address, port, protocol, or call ID. You can also specify how long you want to run the trace and how many messages you want to display. The tracesbc tool can help you troubleshoot and diagnose issues with SIP registration and call setup.

When planning the Avaya Session Border Controller for an Enterprise (ASBCE) deployment, a good practice to adopt is to name interfaces consistently, for example, Al as “Internal” or “Private” for connectivity to the Call Server. The ASBCE server has four network ports that can be configured as logical interfaces with different IP addresses, subnet masks, gateways, and VLAN IDs. The logical interfaces are named Al, A2, Bl, and B2. A good practice is to use a consistent naming convention for the interfaces that reflects their purpose and function. For example, you can name Al as “Internal” or “Private” because it connects the ASBCE server to the internal network and the Call Server. Similarly, you can name Bl as “External” or “Public” because it connects the ASBCE server to the external network and the Internet. This naming convention can help you avoid confusion and errors when configuring the interfaces and assigning them to zones.

When configuring a Topology Hiding Profile associated with a Session Manager in a typical Avaya Session Border Controller for Enterprise (ASBCE) deployment, you should overwrite the following three SIP headers with a SIP domain: From, Refer-To, and To. A Topology Hiding Profile is a configuration object that masks the FQDN or IP address portion of SIP headers to hide the internal topology of the network. For example, SBCE@avaya.com can become SBCE@135.122.18.7, or just the opposite. The From header indicates the identity of the originator of a SIP request or response. The Refer-To header indicates the identity of the recipient of a REFER request, which is used to transfer calls or sessions. The To header indicates the identity of the intended recipient of a SIP request or response. These headers should be overwritten with a SIP domain to prevent exposing internal FQDNs or IP addresses to external entities

After running the Install wizard on the Avaya Session Border Controller for Enterprise (ASBCE), you add a Public (External) IP address to the Bl interface. The Bl interface is a logical interface that represents the external network port on the ASBCE server. The Bl interface is used to communicate with external entities, such as SIP service providers or remote workers. If you try to ping the Bl interface IP address from a PC in the same subnet, but it fails, the first step to resolve the problem is to navigate to Network & Flows > Network Management > Interfaces and enable the Bl interface. By default, the Bl interface is disabled after the Install wizard. You need to enable it and assign it to an External Zone, which is a logical grouping of interfaces that defines the security and routing policies for the external network

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

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

A field engineer runs the Installation Wizard during the deployment of the Avaya Session Border Controller for Enterprise (ASBCE). The Installation Wizard is a tool that guides the engineer through the initial configuration of the ASBCE server, such as setting the hostname, IP addresses, passwords, and time zone. During the Installation Wizard, one of the steps is to configure a Domain Name System (DNS) server address for the ASBCE server. A DNS server is a server that resolves domain names into IP addresses and vice versa. The ASBCE server needs a DNS server address to communicate with other entities that use domain names, such as SIP servers or endpoints. The Installation Wizard allows configuring both a Primary DNS server address and a Secondary DNS server address for redundancy purposes. However, only a Primary DNS server address is mandatory, while a Secondary DNS server address is optional. Therefore, the statement that is true about configuring a DNS server address during the Installation Wizard is that a Primary DNS server address needs to be configured.

To integrate Avaya Aura® Communication Manager (CM) with Application Enablement Services (AES), and enable the TSAPI link, you need to perform two configuration steps on CM: Configure IP Services and Create a CTI link. These steps are necessary to establish a connection between CM and AES using ASAI protocol, which is a proprietary protocol that provides access to various CTI features of CM. A TSAPI link is a logical connection between CM and AES that allows TSAPI applications to use ASAI features through AES. To configure IP Services and Create a CTI link on CM, you need to use these screens:

• The “ip-services” screen: This is a screen that allows you to create and manage IP services on CM, such as ASAI-IP or C-LAN. You can access this screen using the System Access Terminal (SAT) interface of CM. On this screen, you need to specify a service type, node name, local node, local port, remote node, remote port, remote domain name, service state, and service link for each IP service. For integrating with AES, you need to create an ASAI-IP service that points to the node name of an AES server.
• The “cti-link” screen: This is a screen that allows you to create and manage CTI links on CM, which are logical connections between CM and CTI servers, such as AES. You can access this screen using the System Access Terminal (SAT) interface of CM. On this screen, you need to specify a name, number, type, and password for each CTI link. For integrating with AES, you need to create a CTI link of type ADJ-IP that matches the switch CTI link number on AES.

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

Before you can begin configuring SIP Trunking, the status that all the Avaya Session Border Controller for Enterprise (ASBCE) components / devices should show on the Device Management screen is Ready. The Device Management screen is a web interface that allows you to view and manage the ASBCE components / devices, such as EMS (Element Management System), SBC (Session Border Controller), or HCA (High Capacity Appliance). The Device Management screen displays information such as device name, management IP, version, status, reboot, and shutdown for each component / device. The status indicates the operational state of the component / device, which can be one of these values: Provisioned, Commissioned, Registered, or Ready. The Ready status means that the component / device is fully operational and ready to handle traffic. Therefore, before configuring SIP Trunking, you should make sure that all the ASBCE components / devices have a Ready status on the Device Management screen.

After installing a new Avaya Session Border Controller for Enterprise (ASBC6) component / device using the EMS GUI, you click on the Install link on the EMS Device Management page. After briefly displaying the Provisioned status, the final status that the ASBCE component / device should display is Running. The EMS Device Management page is a web interface that allows you to view and manage the ASBCE components / devices, such as EMS (Element Management System), SBC (Session Border Controller), or HCA (High Capacity Appliance). The EMS Device Management page displays information such as device name, management IP, version, status, reboot, and shutdown for each component / device. The status indicates the operational state of the component / device, which can be one of these values: Provisioned, Commissioned, Registered, or Running. The Running status means that the component / device is fully operational and ready to handle traffic. Therefore, after installing a new ASBCE component / device using the EMS GUI, you should wait until it displays a Running status on the EMS Device Management page.

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