Pass the Avaya ACIS-7130 71301X Questions and answers with CertsForce

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.

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

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.

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

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

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

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.

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

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

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.