71301X Avaya Aura Communication Applications Implement Certified Exam Questions and Answers

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

When installing the identity certificate and encryption key files on the Avaya Session Border Controller for Enterprise (ASBCE), you need to follow this rule: The filename of the identity certificate (.pem or .crt file) must be different from the filename of the encryption key (.key file). An identity certificate is a file that contains information about the identity and public key of an entity, such as a server or an endpoint. An encryption key is a file that contains information about the private key of an entity, which is used to encrypt and decrypt data. The identity certificate and encryption key files are obtained from a Certificate Authority (CA) or generated by yourself using tools such as OpenSSL. When installing these files on the ASBCE server, you need to make sure that they have different filenames, otherwise they will overwriteeach other and cause errors. For example, you can name them as sbce-cert.pem and sbce-key.key respectively.

To connect one Internet Friendly (Edge) Gateway to Avaya Communication Manager (CM), you need two Public and two Private IP addresses. An Internet Friendly (Edge) Gateway is a device that provides secure and reliable connectivity between endpoints on different networks, such as the public internet and a private enterprise network. An Internet Friendly (Edge) Gateway can be implemented using an Avaya Session Border Controller for Enterprise (ASBCE) in distributed mode, where the ASBCE consists of two components: a Signaling Border Element (SBE) and a Data Border Element (DBE). The SBE handles SIP signaling and call control, while the DBE handles media packets and signaling pinholes. To connect one Internet Friendly (Edge) Gateway to CM, you need these IP addresses:

• A Public IP address for the SBE: This is the IP address that is visible to external entities, such as endpoints or servers on the public internet. This IP address is used by external entities to communicate with the SBE using SIP over TLS.
• A Private IP address for the SBE: This is the IP address that is visible to internal entities, such as CM or other ASBCE components on the private enterprise network. This IP address is used by internal entities to communicate with the SBE using SIP over TCP or UDP.
• A Public IP address for the DBE: This is the IP address that is visible to external entities, such as endpoints or servers on the public internet. This IP address is used by external entities to communicate with the DBE using RTP or RTCP.
• A Private IP address for the DBE: This is the IP address that is visible to internal entities, such as CM or other ASBCE components on the private enterprise network. This IP address is used by internal entities to communicate with the DBE using H.248.

If the customer requires High Availability (HA) for the Avaya Session Border Controller for Enterprise (ASBCE), the minimum number of servers or virtual machines that are required is 2. High Availability (HA) is a feature that provides redundancy and fault tolerance for the ASBCE server by deploying two ASBCE servers in a pair, either in the same location or geographically dispersed. The two ASBCE servers act as a single logical entity and share a common configuration and license. One ASBCE server is designated as the active server and handles all traffic, while the other ASBCE server is designated as the standby server and monitors the status of the active server. If the active server fails or becomes unreachable, the standby server takes over and becomes the new active server, ensuring continuity ofservice. The two ASBCE servers synchronize their configuration and state information using a dedicated HA link between them

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

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

An Application Rule is a type of Domain Policy Rule in the Avaya Session Border Controller for Enterprise (ASBCE) that allows setting a limit to the maximum audio sessions per endpoint, enabling the ASBCE to reject the call when this limit is reached. A Domain Policy Rule is a configuration object that defines the security and quality of service policies for SIP domains that are managed by the ASBCE server. There are four types of Domain Policy Rules: Security Rule, Border Rule, Application Rule, and Media Rule. An Application Rule is a Domain Policy Rule that defines the application-level policies for SIP domains, such as call admission control,bandwidth management, session timers, and session limits. An Application Rule can include a parameter called Max Audio Sessions Per Endpoint, which specifies the maximum number of concurrent audio sessions that an endpoint can have within a SIP domain. If an endpoint tries to initiate or receive more audio sessions than this limit, the ASBCE server will reject the call with a 403 Forbidden response.

When configuring the Avaya Call Park and Page snap-in, the Call Park Extension Group attribute is used to specify the extensions that can be used to park calls. The format of the Call Park Extension Group attribute is as follows:

():,,…

The location ID is a numeric value that identifies the location where the Call Park and Page snap-in is deployed. The number of digits is the number of digits in each extension. The extensions are the actual extensions that can be used to park calls. For example, 3(1):4000,4001,4002 means that the Call Park and Page snap-in is deployed in location 3, each extension has one digit, and the extensions are 4000, 4001, and 40021

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

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.

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

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

The Avaya Aura® Web Gateway (AAWG) requires a license file to operate and provide WebRTC services for endpoints such as Avaya Workplace clients or Avaya Spaces Calling extension users. The license file can be installed on either of these two options:

• The WebLM server embedded in System Manager (SMGR): This is a web-based licensing application that is integrated with SMGR and can manage licenses formultiple Avaya products, such as Communication Manager, Session Manager, Presence Services, or Breeze Platform. You can install an AAWG license file on this WebLM server using SMGR web interface, under Elements > Licensing > Licenses5
• A standalone WebLM server: This is a web-based licensing application that runs on a separate Linux or Windows server and can manage licenses for multiple Avaya products, such as Communication Manager, Session Manager, Presence Services, or Breeze Platform. You can install an AAWG license file on this WebLM server using its web interface, under Licenses > Add License File6

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

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.

A Survivable Communication Manager (CM) is a Communication Manager instance that provides local call processing and trunking capabilities for remote sites or branches in case of a WAN outage or loss of connectivity with the core servers. A Survivable CM monitors thestatus of the main CM by sending and receiving heartbeat messages at regular intervals. A heartbeat message is a SIP OPTIONS request that tests the availability of the main CM. If the Survivable CM does not receive a response to its heartbeat message within a specified timeout period, it assumes that the main CM is down and triggers a failover process. During the failover process, the Survivable CM accepts IP phone registration requests from the local endpoints and puts the configured IP trunks in a working condition, allowing the remote site or branch to continue making and receiving calls