Avaya 71301X Dumps

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

The steps for deploying the Avaya Presence Services snap-in are as follows:

• Download the Presence Services snap-in software bundle from the Avaya Support website.
• Log in to System Manager and navigate to Elements > Inventory > Manage Elements.
• Select the Breeze® cluster where you want to deploy the Presence Services snap-in and click Edit.
• In the Snap-ins tab, click Add Snap-in and browse to the location where you saved the Presence Services snap-in software bundle.
• Select the Presence Services snap-in file and click Open.
• Click Commit to load the Presence Services snap-in to System Manager.
• Navigate to Elements > Inventory > Cluster Administration.
• Select the Breeze® cluster where you loaded the Presence Services snap-in and click Manage Snap-ins.
• In the Snap-ins tab, select the Presence Services snap-in and click Activate/Upgrade/Downgrade.
• Click OK to load the Presence Services snap-in into the Breeze® cluster

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 context of Avaya Aura® Presence Services, a Watcher is a user who is interested in the presence information of another user, called a Presentity. A Watcher sends a Subscribe message to the Presence Services snap-in on the Avaya Breeze® server, requesting to receive notifications about the current and future presence status of the Presentity. The Presence Services snap-in then sends a Notify message to the Watcher, containing the presence information of the Presentity. The Watcher can use this information to decide how and when to communicate with the Presentity12

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.

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

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.

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

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.

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

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.

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

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.

In the Avaya Session Border Controller for Enterprise (ASBCB) Multi-Server/ HA deployments, you can access the tracesbc tool that displays SIP messages in real-time as they pass through the ASBCE from the SBC component/ device command line via SSH session using PuTTY. A Multi-Server/ HA deployment is a deployment where two or more ASBCE servers are deployed in a pair or cluster, providing redundancy and scalability for the ASBCE server. Each ASBCE server consists of two components: the EMS component and the SBC component. The EMS component is responsible for managing and monitoring the ASBCE server, while the SBC component is responsible for processing and routing the SIP traffic. The tracesbc tool is a CLI tool that runs on the SBC component and captures and displays SIP messages and mediastatistics for calls that traverse the ASBCE server. You can use PuTTY, which is a terminal emulator application, to establish an SSH session with the SBC component and run the tracesbc tool from the command line.

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.

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) requires licenses to support different types of services, such as SIP Trunking or Remote Worker. The ASBCE licenses are based on the number of concurrent sessions that are handled by the ASBCE server. There are two types of licenses: standard services licenses and advanced services licenses. A standard services license is required for each SIP Trunking session, which is a session between the ASBCE server and a SIP service provider. An advanced services license is required for each Remote Worker session, which is a session between the ASBCE server and a remote endpoint, such as an IP phone or a softphone. Therefore, if the customer plans to have 50 SIP Trunks and100 Remote Workers supported by the ASBCE, they will need 50 standard services licenses and 100 advanced services licenses.

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.

To enable downloading the Personal Profile Manager (PPM) data to an Advanced SIP Telephone (AST), you need to configure two configuration screens in the Avaya Session Border Controller for Enterprise (ASBCE): Reverse Proxy and File Transfer. PPM is a feature that allows ASTs to download configuration data from an Avaya Aura® Device Services (AADS) server or an HTTP server in the enterprise network. The configuration data includes settings such as firmware versions, network parameters, feature options, and user preferences. The ASBCE server acts as a proxy for the ASTs and enables secure access to the internal servers that host the configuration data. To configure this feature in the ASBCE server, you need to use these two configuration screens:

• Reverse Proxy: This is a configuration object that enables secure access to internal web servers from external clients. The Reverse Proxy intercepts HTTP or HTTPS requests from external clients and forwards them to the appropriate internal web servers, such as an AADS server or an HTTP server. The Reverse Proxy also returns the responses from the internal web servers to the external clients. You need to configure a Reverse Proxy that maps the external URL of the PPM data to the internal URL of the PPM data on the AADS server or HTTP server.
• File Transfer: This is a configuration object that enables secure file transfer between external clients and internal servers using protocols such as FTP or SCP. The File Transfer intercepts file transfer requests from external clients and forwards them to the appropriate internal servers, such as an AADS server or an HTTP server. The File Transfer also returns the files from the internal servers to the external clients. You need to configure a File Transfer that specifies parameters such as source and destination IP addresses, ports, protocols, usernames, passwords, encryption modes, and file paths for transferring PPM data files between ASTs and AADS servers or HTTP servers.