[UPDATED Oct-2026] Best Value Available Preparation Guide for 71301T Exam [Q43-Q60]

October 5, 2026 admin 0

Categories : 71301T , Avaya

Rate this post

[UPDATED Oct-2026] Best Value Available Preparation Guide for 71301T Exam

1 Full 71301T Practice Test and 140 Unique Questions, Get it Now!

Avaya 71301T Exam Syllabus Topics:

Section	Weight	Objectives
Avaya Aura Communication Manager Implementation	20%	– Configuring Communication Manager features – Station and trunk configuration – Feature administration and call routing
Avaya Aura Session Manager Implementation	20%	– Adapters and endpoint management – SIP entity configuration – Session Manager routing policies
Avaya Aura Communication Applications Integration	20%	– Integrating third-party applications and endpoints – SIP trunking and interoperability – Integrating Communication Manager with Session Manager
Troubleshooting and Maintenance	10%	– Monitoring and diagnostics – Common troubleshooting techniques – Logging and event analysis
Avaya Aura Communication Applications Architecture	15%	– Avaya Aura Communication Manager overview – Avaya Aura System Manager overview – Avaya Aura Session Manager overview – Avaya Aura Communication Applications integration and topology
Avaya Aura System Manager Implementation	15%	– System Manager user and role management – Network and element management – Templates and bulk administration

Q43. Which three functionalities does WebRTC provide? (Choose three.)

NAT / Firewall Traversal

adds click-to-call capabilities from a web application to an Avaya endpoint

Internet-friendly codecs and Privacy

real-time audio and video conferencing

* One of the primary differentiating features for the WebRTC Snap-in is that the web application handles authentication and authorization of calls.
This includes the capability to assert a calling user’s phone number and restrict the numbers that can be called.
* The Avaya SBCE enables secure firewall traversal for HTTP and SRTP packets, facilitates sending DTLS to provide secured key exchange for the SRTP flow, and takes care of all security requirements mentioned in the TURN protocol for the solution.
* WebRTC can be a game changer for enterprise communications and customer engagement.
Enterprises can now add real-time communications to any website.
https://downloads.avaya.com/css/P8/documents/101013939

Q44. An Avaya Aura Messaging (AAM) server intended to store Voice Messages in Avaya Message Store Mode, and you are configuring that server for integration with an Avaya Aura Core. In Messaging Administration > Server Settings > Server Role/AxC Address, which Server Role must be chosen at the “Roles for this server” field?

Application Only

Storage Only

Storage & Application

AMSM

Q45. On Avaya Session Border Controller for Enterprise (SBCE), where do you access the tool that displays SIP messages, in real time, as they pass through the SBCE?

from Avaya Aura System Manager, navigate to “Session Border Controller for Enterprise>; SBCE Administration” menu

from the SBCE EMS Web Console

from the SBCE Server command line via SSH session, using PuTTY

from the traceSIP client installed on a local PC

Stat the tue Tracing Tools, TraceSM, SSH to Session Manager
1. Launch PuTTY (or similar client application) for a SSH session to Session Manager (port 22).
Use the Session Manager IP Address (172.16.255.107).
2. Log in.
3. At the Session Manager command line type traceSM -x and press Enter.
Note: The traceSM tool shows the SIP call flow in Session Manager.
It gives insight into Session Manager’s decisions.
Benefit: can filter certain types of SIP messages

Q46. Refer to the exhibit. When configuring a Reverse Proxy for the Avaya Aura Web Gateway (AAWG) in the Avaya Session Border Controller for Enterprise (ASBCE), what is the significance of using port 8444 in the Server Address field?

It’s the default port used for ICE/STUN/TURN messages on the AAWG.

It is the default listen port on the AAWG used for all WebRTC call signalling.

This port should match the Front-end port for external access on the AAWG so that AAWG sends the media path for external calls through the ASBCE STUN/TURN server.

It’s used for remote access to the AAWG web interface.

In an architecture involving the Avaya Aura Web Gateway (AAWG) and the ASBCE, the Reverse Proxy configuration is not just about routing web traffic; it is critical for Media Path Steering.
Port 8444 Significance: By default, AAWG uses port 8444 as its external “front-end” port. When the ASBCE Reverse Proxy is configured to point to this specific port on the AAWG (the “Real Server” address), it signals to the AAWG that the incoming request is originating from an external/remote network.
STUN/TURN Trigger: When the AAWG recognizes a request coming through this port, it knows to provide the external clients with the STUN/TURN server information (hosted on the ASBCE).
This ensures that WebRTC media (audio/video) is correctly anchored and relayed through the ASBCE rather than attempting a direct internal connection that would be blocked by the firewall.
Consistency: For the solution to function, the “Listen Port” on the ASBCE (External) and the
“Server Port” on the AAWG (Internal) must be aligned with how the AAWG is configured to handle “Front-end” traffic.

Q47. Which statement about enabling IM and Presence for a user is true?

In SMGR, edit the Communication Profile of the user to assign an Avaya E.164 handle and check the Presence profile checkbox.

In SMGR, edit the Communication Profile of the user to assign an Avaya SIP handle and check the Presence profile checkbox.

In SMGR, edit the Communication Profile of the user to assign a XMPP handle and check the Presence profile checkbox.

In SMGR, edit the Communication Profile of the user to assign an Avaya Presence/IM handle and check the Presence profile checkbox.

Communication Profile tab: Presence Profile
Fields include:
* The SIP Entity field used to route SIP based messages through the Presence Services.
* IM Gateway The IP address of the IM gateway
Note: Avaya SMGR stands for Avaya System Manager.

Q48. A company is deploying Avaya Session Border Controller for Enterprise (SBCE) to support SIP trunking. What is the minimum number of IP-addresses they need to assign to the private and public Network Interface Cards (NICs)?

Two addresses are assigned to the private NIC and two addresses are assigned to the public NIC.

One address is assigned to the private NIC and one address is assigned to the public NIC.

Two addresses are assigned to the private NIC and one address is assigned to the public NIC.

One address is assigned to the private NIC and two addresses are assigned to the public NIC.

Q49. Which two options describe the purpose of TraceSM in the Avaya Aura Presence Services?
(Choose two.)

It captures Packet-Size statistics from every telephone call in Avaya Aura 7.

It captures real-time XMPP traffic.

It captures Voice and Video Calls media packets in real-time.

It captures live traces for both SIP and H323/XMPP clients.

It captures Contact details from every user connected to Avaya Aura Presence Services.

It’s important to know that traceSM is a real-time capture tool.
traceSM is an interactive perl script that allows an administrator to capture, view, and save call processing activity on a Session Manager. While not as powerful or versatile as wireshark, traceSM is absolutely essential when it comes to working with Avaya SIP. First off, it allows you to view SIP messages even if they have been encrypted with TLS.
https://andrewjprokop.wordpress.com/2014/06/02/a-necessary-guide-to-the-avaya-tracesm-utility/

Q50. Which statement about the SIP Entities to support single node Avaya Aura Presence Services is true?

Only one SIP Entity is built of Type = “Presence Services”, which uses the SM100 IP address of the Avaya BreezeTM node.

Only one SIP Entity is built of Type = “Avaya Breeze”, which uses the SM100 IP address of the Avaya BreezeTM node.

Two SIP Entities are built to the same SM100 IP address of each node. One is of type = “Avaya Breeze”, and the other is of Type = “Presence Services”.

Two SIP Entities are built to the same SM100 IP address of each node. One is of type = “Avaya Breeze”, and the other is of Type = “Other”.

Q51. Which statement describes how an H.248 signaling link connects the Internet Friendly (EdgE) Gateway to the Avaya Communication Manager (CM)?

It is transported using HTTPs/REST via the Avaya Session Border Controller for Enterprise (ASBCE).

It is transported using HTTPs using port 443.

It is tunnelled using TCP port 2944 and secured using TLS.

It is transported using TCP port 80 and secured using a VPN connection to the Avaya Session Border Controller for Enterprise (ASBCE).

When an Internet Friendly (Edge) Gateway (IFG) is deployed, it must communicate with the Avaya Aura Communication Manager (CM) across potentially untrusted networks. To maintain the security and integrity of the H.248 signaling traffic, the connection follows a specific tunneling process:
Transport: The signaling traffic is encapsulated and tunneled through the Session Border Controller for Enterprise (ASBCE).
Port: The standard communication occurs over TCP port 2944.
Security: Because the traffic traverses the public internet or an untrusted WAN, it is encrypted and authenticated using Transport Layer Security (TLS).

Q52. Refer to the exhibit. Which type of a Configuration Profile in the Avaya Session Border Controller for Enterprise (ASBCE) allows to set Timers, URI Manipulation and Header Manipulation, and can be linked to a SIP Server Profile?

Signaling Manipulation

Routing

Topology Hiding

Server Interworking

In the Avaya Session Border Controller for Enterprise (ASBCE), the Server Interworking Profile is the primary configuration object used to manage the “behavioral” aspects of SIP signaling between the SBC and a specific SIP entity (such as a Session Manager or a third-party SIP trunk provider).
Timers: This profile allows you to define custom values for various SIP timers (e.g., re-invite timeouts, T1/T2 timers) to ensure compatibility with different vendor requirements.
URI Manipulation: It provides the capability to modify the request URIs, which is often required to normalize dialing patterns or comply with specific carrier formatting.
Header Manipulation: It allows for adding, modifying, or removing SIP headers (e.g., P-Asserted- Identity, Diversion headers) to ensure that the internal Avaya network and the external network can communicate correctly.
Linking: You link this profile to a SIP Server Profile within the SBC configuration. Once linked, the SBC applies these specific interworking rules whenever it communicates with that specific server, ensuring that the signaling is tailored to the needs of that connection.

Q53. When looking at Avaya Aura System Manager – Hom>t; Service>t; Replication, what is the name of the replica group representing the EDP / Avaya BreezeTM instances?

CollaborationEnvironment_7.0

Avaya BreezeTM_7.0

CollaborationEnvironment_3.1

Engagement Development Platform EDP_7.0

Confirming that Avaya Breeze successfully replicates with System Manager Procedure
1. On the System Manager web console, navigate to Services > Replication.
2. In Replica Group column, click CollaborationEnvironment_3.1.
3. In Replica Node Host Name column, locate your newly-deployed Avaya Breeze.
4. After 2 – 15 minutes, verify that the status of the Synchronization Status field is green/ Synchronized. If not, see Repairing replication between Avaya BreezeTM and System Manager

Q54. When planning the Avaya Session Border Controller for Enterprise (SBCE) for SIP Trunking, what is a good practice to adopt?

Name Interfaces consistently, for example, A1 for Internal network to Call Server and B1 for external to Trunk Server.

Name all internal and external interfaces exactly the same.

Use the same IP address on both, internal and external sides of the network.

Use one Avaya Session Border Controller for Enterprise on the internal and external sides of the network.

Use the same interface mapping throughout! Examples in this section use:
A1 as the internal interface (to the call server)
B1 as the external interface (to the trunk server)

Q55. In Avaya Aura System Manager, how is Avaya Aura Messaging (AAM) added to the list of Managed Elements?

It is added when you configure the AAM SIP Entity in SMGR.

It is automatically added during the enrollment process.

It can only be manually added.

It is automatically added using initTM -fcommand on the Command Line Interface of AAM.

Q56. WebRTC is used for which type of calls?

video calls only

calls originated from internal web browsers only

calls originated from external web browsers only

calls originated from internal and external web browsers

The Avaya WebRTC Snap-in enables users inside or outside the Enterprise to make a secure call from their web browser to any endpoint to which Avaya Aura can deliver calls.
https://downloads.avaya.com/css/P8/documents/101013939

Q57. In Avaya Session Border Controller for Enterprise (SBCE), what is the default state of an Interface?

Deployed

Enabled

Disabled

Active

Example:
Commission the SBC–SBC Configuration
1. The A1 and B1 interfaces display on the Network Configuration tab.
2. Click on the Interface Configuration tab:

3. Click the Toggle link for both the A1 and the B1 interfaces.
The Administrative Status for both A1 and B1 changes to Enabled:

Q58. How does AES support complex contact center functionalities such as call recording and workforce optimization?

Through its scalable APIs that connect to various auxiliary systems

By providing standalone contact center solutions

By integrating with existing CRM systems

By directly storing data in a central database

Q59. When deploying a Survivable Communication Manager (CM), which statement about the Server ID value is true?

The Server ID of a Survivable CM needs to match the server ID of the Main CM. The Server IDs must be an even/odd pair (N, N+1).

The Server ID is a value found in the license file.

Every CM server in the network needs to be assigned a unique Server ID including servers in a duplex pair.

Every CM server in the network needs to be assigned a unique server ID, but both servers in a duplex pair must have the same Server ID.

The Server ID is a fundamental identifier within the Avaya Aura Communication Manager architecture, used to manage licensing and system identity across the network.
Duplex Pair Logic: A duplex pair consists of an active and a standby processor (often referred to as the “A” and “B” servers) working together to provide high availability. Because they act as a single logical unit to the network and the license file, they must share the exact same Server ID.
Global Uniqueness: Outside of a specific duplex pair, every other CM instance (whether it is a standalone main server or a Survivable CM/LSP) must be assigned a unique Server ID. This ensures that the license manager (WebLM) can accurately track entitlement usage across distributed systems.

Q60. Which two pieces of information in an output from the show mgc command (issued on a G430/G450 Gateway CLI), indicate that the G430/G450 is operating as an Internet Friendly (EdgE) Gateway as opposed tan Enterprise Gateway? (Choose two.)

The Controller displays sbc@.

The H.248 Link Status displays UP/Encrypted.

The Gateway Mode displays Edge.

The H.248 Link Mode displays IFG.

The Management Link Mode displays Tunnelled.

When a G430 or G450 gateway is configured to function in an Internet-friendly capacity (often used for remote branch deployments where traffic traverses public networks), the command-line interface provides explicit status indicators for this mode:
Gateway Mode (Edge): This field confirms the global operational state of the gateway. When set to Edge, the gateway is configured to interact with the Session Border Controller (SBC) or the appropriate edge-aware media server components, rather than acting as a standard Enterprise gateway.
H.248 Link Mode (IFG): The IFG indicator stands for Internet Friendly Gateway. This specifically confirms that the H.248 signaling control link is operating in a mode optimized for traversing NATs or firewalls, ensuring connectivity back to the main site controller.

Loading …