Avaya 71301X - 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

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

To access the TSAPI Test from the Application Enablement Services (AES) menu, you need to select Utilities. The TSAPI Test is a basic application for making a call using TSAPI, which is a high-level API for CTI applications based on CSTA I standard. TSAPI allows access to the third party call control capabilities of CM through AES. The TSAPI Test application can be used to verify that the TSAPI client is correctly installed and working on AES. If the TSAPI Test application fails to make the call, an error message is provided to aid in troubleshooting the cause of the failure. To access the TSAPI Test from the AES menu, you need to follow these steps:

Log in to the web interface of AES using your username and password.

Click on Utilities on the left side menu.

Click on TSAPI Test under Utilities.

Enter the parameters for making a call, such as device name, destination number, user ID, and password.

Click on Make Call.

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.

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

With Dynamic Licensing configured in the Avaya Session Border Controller for Enterprise (ASBCE), the ASBCE will issue a request to the WebLM server to allocate additional licenses based on the Fetch Count value when the percentage of free (available) standard sessions licenses drops below 30% (Low Watermark). Dynamic Licensing is a feature that allows the ASBCE to dynamically allocate and release licenses from a pool of licenses managed by the WebLM server. The Fetch Count value is a parameter that specifies how many licenses are requested from the WebLM server at a time. The Low Watermark value is a parameter that specifies the threshold percentage of free licenses that triggers a request for more licenses from the WebLM server. The High Watermark value is a parameter that specifies the threshold percentage of free licenses that triggers a release of unused licenses to the WebLM server