Avaya 7120X (Avaya Aura Core Components Integration Exam) exam dumps vce, practice test questions, study guide & video training course to study and pass quickly and easily. Avaya 7120X Avaya Aura Core Components Integration Exam exam dumps & practice test questions and answers. You need avanset vce exam simulator in order to study the Avaya ACIS-7120 7120X certification exam dumps & Avaya ACIS-7120 7120X practice test questions in vce format.

Mastering the Avaya 7120X Exam - Core Concepts and System Manager

The Avaya Aura Core Components Integration exam, known as the Avaya 7120X, is a critical step for professionals seeking the ACIS credential. This certification validates an individual's ability to integrate and implement the essential elements of the Avaya Aura platform. The exam structure requires candidates to answer 68 questions within a 90-minute timeframe. To pass, a minimum score of 69 percent is necessary, which translates to correctly answering at least 47 questions. A thorough understanding of the core components is not just recommended; it is essential for success. This guide will delve into the key knowledge areas covered in the Avaya 7120X exam.

This series aims to provide a comprehensive overview of the topics you will encounter, from system deployment and component configuration to routing policies and endpoint registration. By breaking down complex subjects into manageable sections, you can build a solid foundation of knowledge. We will explore the roles of System Manager, Session Manager, and Communication Manager, and how they interact to create a cohesive communications solution. Diligent study of these areas will equip you with the skills needed to confidently approach the Avaya 7120X exam and achieve a passing score.

The Role of Avaya Aura System Manager (SMGR)

Avaya Aura System Manager, often referred to as SMGR, serves as the centralized management platform for the entire Avaya Aura ecosystem. It provides a web-based graphical user interface for the administration, maintenance, and provisioning of all core components. This centralized approach simplifies what would otherwise be a complex and fragmented management task. For the Avaya 7120X exam, it is crucial to understand that SMGR is the single point of control for managing users, Session Managers, Communication Managers, and various other applications within the solution. All system-wide configurations, such as dial plans and routing policies, originate within SMGR.

From a practical standpoint, an administrator uses SMGR to build the foundational elements of the communication system. This includes creating user profiles, defining SIP entities which represent other systems, and configuring security settings. The platform synchronizes this data to the relevant components, such as Session Manager, ensuring consistency across the network. For example, when you create a new SIP user in SMGR, the authentication and profile data are pushed to the Session Manager instances responsible for handling that user's registration and call processing. Understanding this data flow is a key concept for the Avaya 7120X.

The SMGR dashboard provides a high-level overview of the health and status of the entire Aura system. It is a critical tool for daily monitoring and initial troubleshooting. From the dashboard, you can quickly assess the state of managed elements, view active alarms, and check system capacity. Questions on the Avaya 7120X exam may reference the capabilities of the dashboard, such as its ability to show the health summary of each administered Session Manager. It is a monitoring tool, not a direct configuration interface for individual calls, but it is the starting point for navigating to the administrative sections for each component.

Understanding User and Communication Profiles

A fundamental concept in the Avaya 7120X curriculum is the provisioning of users, which is accomplished through profiles in System Manager. When a new user is created, they are assigned a Communication Profile. This profile is a critical piece of the configuration that links a user's identity to their communication endpoints and services. It contains the user's SIP handle, also known as their SIP address of record, and an associated password for authentication. This profile is what allows a SIP endpoint to register successfully with Session Manager, as it provides the necessary credentials for validation.

The Communication Profile also dictates which Session Manager instance will act as the primary, secondary, and tertiary registrar for the user's endpoint. This assignment is crucial for redundancy and load balancing within the network. Furthermore, the profile ties the user to an Application Sequence. This sequence determines which applications, such as Communication Manager for features or Avaya Aura Messaging for voicemail, are engaged during call processing. Without a correctly configured Communication Profile, a SIP user cannot be created, and their phone will fail to register with the system, highlighting its importance for the Avaya 7120X exam.

In contrast, a Communication Manager Profile is a separate configuration element within a user's profile. This specific profile is only required when the user needs to access features hosted on an Avaya Aura Communication Manager. It contains the user's extension number on CM and links them to CM-specific attributes like Class of Service (COS) and Class of Restriction (COR). For a Simple SIP Phone (SST) that does not require advanced CM features, this profile is not necessary. However, for feature-rich endpoints like Avaya Equinox or J-Series phones, it is essential for full functionality.

Introduction to Solution Deployment Manager (SDM)

Solution Deployment Manager, or SDM, is a vital tool for the initial installation and upgrading of Avaya Aura components. It is not an application for daily administration but is used exclusively for deployment tasks. For the Avaya 7120X, you should know that SDM is a client-based application that an installer runs on their laptop. It can be installed on a Windows or Macintosh computer. This tool provides a streamlined, wizard-driven process for deploying virtualized Aura applications onto a host server, such as an ESXI server or the Avaya Virtualized Platform (AVP).

SDM is included as part of the Avaya Aura System Manager 7.x software package and is the primary method for deploying new instances of Session Manager, Communication Manager, and other applications. The tool automates many of the complex steps involved in virtualization, such as creating the virtual machine, configuring network settings, and installing the application software. This reduces the potential for human error and significantly speeds up the deployment process. The ability of SDM to install Avaya Aura Session Manager on AVP is a specific capability you should be aware of for the Avaya 7120X exam.

It is important to distinguish the function of SDM from that of SMGR. While SMGR is used for the ongoing administration and provisioning of an already running system, SDM is used to get the system running in the first place. Once an application like Session Manager has been deployed using SDM, it is then enrolled with and managed by System Manager. SDM's role is therefore foundational but distinct. You would not use SDM to create a new user or change a routing policy; those are SMGR functions. Recognizing this division of labor is key.

Building a Network Routing Policy

Network Routing Policies are at the heart of call routing within Avaya Aura Session Manager. They are powerful rules that determine how calls are directed between different parts of the network. Before you can create a Network Routing Policy in System Manager, several prerequisite objects must be configured. The Avaya 7120X exam will test your knowledge of these dependencies. A common question format is to ask which elements are necessary before a specific configuration, like a routing policy, can be completed. This requires a procedural understanding of the system's architecture.

The three essential configuration points required to build a Network Routing Policy are Locations, SIP Entities, and Domains. Locations are used to define geographical or logical areas of the network, which are then used for call admission control and E911 routing. SIP Entities represent the various SIP-aware systems that Session Manager will communicate with, such as Communication Manager, a SIP trunking provider, or another Session Manager cluster. Each SIP Entity has an associated IP address or fully qualified domain name that Session Manager uses to send traffic.

Domains are used for addressing and routing within the SIP environment. A domain name is configured in SMGR and is used as part of a user's SIP address, for example, user@companydomain. Once these three elements—Locations, SIP Entities, and Domains—are defined in System Manager, you can then proceed to create a Network Routing Policy. The policy itself will reference these objects to make its routing decisions. For example, a policy might state that calls from a user in the "NewYork" location destined for the "PSTN" SIP Entity should be routed out a specific trunk.

System Health and Monitoring from the SMGR Dashboard

The Avaya Aura System Manager (SMGR) Dashboard is the primary tool for at-a-glance monitoring of the entire Aura platform. A key topic for the Avaya 7120X exam is understanding the capabilities and limitations of this dashboard. Its main purpose is to provide a consolidated view of the operational status and health of all managed components. When you log into SMGR, the dashboard is typically the first screen you see, presenting a summary of system alarms, service states, and overall component health. This allows administrators to quickly identify potential issues without needing to check each server individually.

From the dashboard, you can get information on the status and health summary of each administered Session Manager (SM) instance. This includes details like its connection status to SMGR, any active alarms on that SM, and its current software version. This high-level view is crucial for maintaining system uptime and ensuring that all parts of the communication infrastructure are functioning as expected. It acts as a central nervous system for monitoring, providing a single pane of glass for the entire solution. You cannot use the dashboard to directly administer a new user or import data, but it provides the links to navigate to the correct administration pages.

The dashboard's function is purely for monitoring and providing easy navigation. For instance, if you see an alarm related to a specific Session Manager on the dashboard, you can click on it to drill down into the Session Manager administration section for more detailed troubleshooting. It is not a tool for performing administrative tasks like creating a user profile or a routing policy directly. Those actions are performed in their respective sections within the SMGR web interface. For the Avaya 7120X exam, remember that the dashboard is for status, health, and alarms, not for direct configuration changes.

The Core Function of Session Manager in Avaya Aura

Avaya Aura Session Manager, often abbreviated as SM, is the core SIP routing engine of the Avaya Aura platform. Its primary function is to act as a SIP registrar, proxy, and router. Understanding its central role is absolutely critical for the Avaya 7120X exam. All SIP-based communication, whether from endpoints, trunk lines, or other applications, flows through Session Manager. It is responsible for registering SIP endpoints, authenticating users, and applying routing policies to direct call traffic to the appropriate destination. It effectively decouples endpoints and applications, allowing for immense flexibility and scalability.

When a SIP endpoint, such as a SIP phone or a soft client, starts up, its first task is to register with the network. It sends a SIP REGISTER message to a pre-configured IP address. This address must be the signaling interface of a Session Manager, known as the SM100 interface. Session Manager receives this request, authenticates the user's credentials against the profile data synchronized from System Manager, and upon success, maintains the endpoint's registration status. This process allows SM to know the current IP address and availability of every SIP user, enabling it to route incoming calls to them correctly.

Beyond registration, Session Manager processes every call signal. It uses the dial plan and routing policies configured in System Manager to make intelligent decisions about where to send a call. For instance, a call from a SIP phone to a traditional digital phone will be routed by Session Manager to Communication Manager for processing. A call to an external number might be routed to a SIP trunk provider. This centralized routing logic simplifies the network architecture, as individual endpoints and systems do not need to contain complex routing information themselves. They simply send all calls to Session Manager.

The SIP Endpoint Registration Process

For a Simple SIP Phone (SST) to successfully register with the Avaya Aura Core, it must be configured with the correct network information. A common point of confusion, and therefore a likely topic for the Avaya 7120X exam, is which specific IP address the endpoint should point to. The phone's configuration must contain the IP address of the Session Manager's SM100 interface. The SM100 is a dedicated network interface on the Session Manager server specifically designed for SIP signaling traffic. It is separate from the management interface, which is used for administration and communication with System Manager.

The registration sequence begins with the SIP endpoint sending a SIP REGISTER message to the SM100 IP address. Inside this message are the user's credentials, typically a username and password. Session Manager receives this message on one of its configured listening ports. It then validates the credentials against the user's Communication Profile, which has been synchronized from System Manager. If the credentials are valid and the user profile is correctly configured, Session Manager responds with a "200 OK" message, confirming the successful registration. The phone is now online and ready to make and receive calls.

Several configuration elements in System Manager must be in place for this process to succeed. First and foremost, the user must have a Communication Profile created. This profile defines the user's SIP identity and authentication credentials. Second, the Session Manager instance itself must be configured to listen for registration requests. This is done in the SM Administration section of System Manager, where listening ports for different transport protocols like TCP, UDP, and TLS are defined. Without these two key configurations, a SIP phone will be unable to register, even if it has the correct SM100 address.

Understanding the Half Call Model

The Avaya Aura Session Manager utilizes a processing logic known as the Half Call Model. This concept is fundamental to how Session Manager handles calls and is a key topic for the Avaya 7120X exam. The model essentially splits a single call into two distinct halves: an originating half and a terminating half. Session Manager processes each half independently, applying a specific set of rules and application sequences to each part. This provides a high degree of flexibility in how calls are treated based on who is calling and who is being called.

When a call originates from a user or trunk, Session Manager processes it as the originating half. It consults the originator's profile to find the Origination Application Sequence. This sequence is an ordered list of applications that should be invoked for the caller. For example, it might first send the call to a call recording server and then to Communication Manager for feature processing. Once the origination sequence is complete, Session Manager has all the information it needs about the caller's side of the conversation.

Next, Session Manager processes the terminating half of the call. It determines the destination of the call and looks up the Termination Application Sequence for that destination user or route. This sequence defines the applications that need to be involved for the person being called, such as sending the call to a voicemail server if the user is busy or unavailable. After processing both the origination and termination sequences, Session Manager has a complete picture of the call and then connects the two halves. This model allows for granular control over the call flow.

Essential Session Manager Command-Line Tools

While most Session Manager administration is performed through the System Manager web interface, some tasks, particularly for troubleshooting and initial setup, require access to the command-line interface (CLI). The Avaya 7120X exam expects candidates to be familiar with several key commands. One of the most important is traceSM. This powerful utility is executed directly from the command line of the Session Manager server, not from System Manager or Communication Manager. It provides a real-time log of all SIP messages being processed by the Session Manager.

The traceSM tool is invaluable for diagnosing call failures, registration problems, and routing issues. By running this command, an administrator can see the raw SIP messages, such as INVITE, REGISTER, BYE, and any error responses like "404 Not Found" or "401 Unauthorized." This detailed view allows for a deep analysis of the call flow, helping to pinpoint exactly where a problem is occurring. For example, if a phone is failing to register, traceSM will show the incoming REGISTER request and the specific error response being sent back by Session Manager, which can guide the troubleshooting process.

Another critical command-line tool is SMnetSetup. This command is used for the initial network configuration of a Session Manager server or for correcting network settings after deployment. If you encounter a situation where you cannot ping the SM100 interface of a newly deployed SM, it is often due to an incorrect IP address, subnet mask, or default gateway. The SMnetSetup script provides a menu-driven interface to configure all network parameters for the Session Manager, including the management interface and the critical SM100 signaling interface. It is the correct tool for modifying the core network configuration of the server itself.

Administering SM via System Manager

The primary interface for administering a Session Manager is through the System Manager (SMGR) web GUI. Within SMGR, there is a dedicated section for Session Manager Administration. This is where you configure the core operational parameters of each SM instance. A key configuration screen is the SIP Entity screen, found under the Routing elements. A SIP Entity is an object that represents a SIP-aware device or system that Session Manager will communicate with. This could be a Communication Manager, a third-party application server, or a SIP trunk provider.

When creating a SIP Entity for a Communication Manager, for instance, you define its IP address, the port it listens on, and the transport protocol (TCP, UDP, TLS) to be used. This information allows Session Manager to correctly route calls to that CM. The SIP Entity configuration is also where you would link the entity to a specific Location for Call Admission Control purposes. Correctly defining all SIP Entities is a foundational step in building the routing logic for the entire Avaya Aura solution.

Another crucial administrative area in SMGR is the SM Administration page for each individual Session Manager instance. This is where you define the listening ports that the Session Manager will use to accept incoming SIP traffic. For example, you would typically configure it to listen on port 5060 for UDP and TCP, and port 5061 for TLS. If these ports are not defined and enabled, the Session Manager will not be able to receive any registration requests or incoming calls from SIP endpoints. Understanding where to configure these core settings in SMGR is a must for the Avaya 7120X exam.

Authentication and Security in Session Manager

Security is a critical aspect of any communications platform, and Avaya Aura is no exception. Session Manager handles user authentication for SIP endpoints. This process relies on authentication files that are managed and distributed by System Manager. When you change user passwords or trust certificates in SMGR, these changes need to be propagated to the Session Manager instances. The method for installing these files is a specific procedural detail that could appear on the Avaya 7120X exam.

The correct procedure involves transferring the authentication file, often named pwd.txt or a similar variant, from System Manager to the Session Manager using a secure file transfer protocol, specifically SFTP. Once the file is on the Session Manager's local file system, you must log into the SM command line as a privileged user. From there, you execute the loadpwd command with the appropriate options, such as loadpwd -l <auth file name>. This command parses the file and securely loads the updated user credentials into the Session Manager's database, allowing it to authenticate users with the new information.

Another security mechanism is the use of trust certificates. Session Manager must trust the System Manager that administers it. This is established through a certificate exchange during the initial enrollment process. If this trust is ever broken or a certificate expires, communication between SMGR and SM will fail, preventing any further configuration updates from being synchronized. Maintaining the security and trust relationships between components is a key administrative responsibility and an important concept for the Avaya 7120X exam.

The Role of Communication Manager in a SIP Architecture

Avaya Aura Communication Manager, or CM, remains a cornerstone of the Avaya Aura platform, even in a SIP-centric architecture. While Session Manager handles the core SIP routing and registration, Communication Manager serves as a powerful feature and application server. Its primary role in a modern Aura deployment is to provide advanced telephony features to endpoints, act as a gateway for legacy TDM trunks and digital or analog endpoints, and provide survivability options. Understanding this division of roles between SM and CM is crucial for the Avaya 7120X exam.

When a SIP user registered with Session Manager needs access to features like call park, call pickup, or extension-to-extension dialing with traditional phones, Session Manager routes the call to Communication Manager. CM processes the feature request and manages the call state, providing the rich set of features that Avaya is known for. Essentially, CM acts as a sequenced application in the Session Manager call flow. For endpoints that are not SIP-native, such as H.323, digital, or analog phones, Communication Manager serves as their primary registrar and call controller.

Communication Manager is also responsible for interfacing with the Public Switched Telephone Network (PSTN) via traditional trunking protocols like ISDN or T1/E1. It acts as a media gateway controller, managing the conversion between the IP-based internal network and the circuit-switched external world. For the Avaya 7120X, you must recognize that CM is not just a legacy component but an integral part of the solution, providing essential features and connectivity that a pure SIP environment may not offer.

Accessing and Administering Communication Manager

There are several methods for accessing and administering a Communication Manager server, and the Avaya 7120X exam expects you to know them. The most traditional method is through a terminal emulator application using Secure Shell (SSH) to access the command-line interface. This interface, known as the System Access Terminal (SAT), presents a series of forms or screens for configuration. Commands like change station, add trunk-group, or display node-names are entered here. This text-based interface is powerful and is still the preferred method for many experienced administrators.

Another important access method is via the service port. Each Communication Manager server or gateway has a physical Ethernet port designated as the service port. This port provides direct, local access for initial configuration and maintenance, especially when network connectivity to the main corporate LAN is unavailable. To connect a laptop to this port, you must configure your laptop's IP address to be on the same subnet. The standard IP address for the service port interface on the CM server is 192.11.13.6, which means your laptop must be set to a static IP address on that same network, such as 192.11.13.5, with a subnet mask of 255.255.255.252.

A more modern approach is using the System Management Interface (SMI), which is a web-based GUI for administering CM. The SMI provides a graphical way to perform many of the same tasks as the SAT interface, as well as crucial maintenance functions like scheduling backups and installing software patches. For example, performing a system backup is a common task done through the SMI. It allows administrators to schedule backups to be sent to a remote server using secure protocols like SCP (Secure Copy Protocol) or to save them to the CM's local hard disk.

Core CM Configuration: COR and COS

Two of the most fundamental configuration elements in Communication Manager are the Class of Restriction (COR) and the Class of Service (COS). A solid understanding of their purpose and function is essential for the Avaya 7120X. A Class of Restriction is primarily a security and toll-fraud prevention tool. It defines what a user or trunk is allowed to call. Each station, trunk group, and routing pattern is assigned a COR number. The system then compares the COR of the calling party with the COR of the facility (trunk or route) they are trying to access to determine if the call is permitted.

For example, a lobby phone might have a COR that only allows it to call internal extensions, while an executive's phone would have a COR that permits international dialing. The COR also controls feature access, such as the ability to forward calls off-net or use priority calling. When administering a Communication Manager 7.x system, the valid range for COR numbers is 0 to 255. This provides a large number of restriction classes to meet the needs of complex organizational policies.

Class of Service (COS), on the other hand, determines how a user's phone behaves and which features are enabled at the set level. It is not a security feature like COR. Instead, COS controls things like whether a phone has data privacy, call waiting, or automatic callback enabled. It also manages how many calls can appear at once and whether the phone can be a coverage answer position for other users. Each device is assigned a COS group number, which can range from 0 to 100 in recent versions. The command to modify a COS is change cos.

Configuring Dial Plan and Feature Access

The dial plan in Communication Manager is the set of rules that interprets dialed digits and routes calls accordingly. A key component of the dial plan is the Automatic Alternate Routing (AAR) analysis table. AAR is used to route calls between different locations or systems within the private network. It allows users to dial a uniform extension number regardless of the user's physical location. The change aar analysis command is used to populate this table, mapping dialed number patterns to specific route patterns that direct the call to the correct destination.

To enable users to access AAR, an AAR access code must be defined. This is a prefix that users dial before the destination extension number to signal that they are making an inter-site call. For example, if the AAR access code is 8, a user would dial 8 plus the extension to reach someone at a different office. The command used to define this and other feature codes is the change feature-access-code command. This single SAT screen is the central point for managing all the service codes on the system, from call forwarding and call park to AAR and ARS access codes.

The feature access code screen is a critical part of the CM administration that will likely be covered on the Avaya 7120X exam. Knowing which command to use to change a specific code is important. If the requirement is to enable the digit 8 as the AAR access code, the correct procedure is to navigate to the change feature-access-code form, find the field for AAR Access Code, and enter the digit 8. This simple change instantly updates the dial plan for all users on the system.

Tenant Partitioning and its Impact

The Tenant Partitioning feature in Avaya Aura Communication Manager allows a single CM system to be divided into multiple logical partitions, effectively serving different groups of users or departments as if they were separate systems. This is particularly useful in large enterprises or multi-tenant environments where distinct calling privileges and dial plans are required for different business units. When tenant partitioning is enabled, it changes some of the fundamental administration behaviors of the system, which is an important concept for the Avaya 7120X.

For instance, with tenant partitioning active, certain configuration elements like Class of Service (COS) are managed on a per-tenant basis. Each tenant partition can have its own set of COS groups, numbered from 1 to 100. To administer the Class of Service for a specific tenant, you must use a modified command. Instead of simply using change cos, the command becomes change cos-group <group-number>. The system will then prompt for the tenant partition number to which this COS group belongs.

This distinction is crucial. Using the generic change cos command in a tenant-partitioned system may not show all available options or could lead to incorrect configuration. The exam may present a scenario where tenant partitioning is enabled and ask for the correct command to modify a specific configuration element. Recognizing that commands are often modified or require additional parameters (like a tenant number) when this feature is active demonstrates a deeper understanding of CM administration.

CM Backup and Maintenance Procedures

Regular backups are a critical maintenance task for any Communication Manager system to ensure data can be recovered in the event of a hardware failure or data corruption. The Avaya 7120X exam will likely include questions about the backup process and available methods. A CM backup saves the call processing translations, which is the database containing all the configured stations, trunks, dial plan information, and feature settings. It is important to understand that the backup process saves the last saved version of these translations from the CM's local hard disk, not directly from volatile memory.

The primary interface for managing backups on a modern CM system is the System Management Interface (SMI), the web-based GUI. The SMI offers several methods for performing backups. An administrator can choose to perform a local backup, which saves the backup file directly onto the CM server's own local hard disk. While convenient, this is not a disaster recovery solution, as the backup file would be lost if the server itself failed. It is more suitable for creating a quick restore point before making major configuration changes.

For robust disaster recovery, remote backups are the recommended approach. The SMI provides options to schedule or manually initiate backups to a remote file server. The most common and secure protocol supported for this is the Secure Copy Protocol (SCP). This method allows the CM to push its backup file over the network to a designated external server, providing a safe, off-box copy of the translations. Knowing that both local and remote SCP backups are available through the SMI is a key piece of information for the Avaya 7120X exam. Remote FTP is also an option, but SCP is generally preferred for security.

Configuring H.323 Trunks in Communication Manager

While SIP has become the standard for modern enterprise communication, H.323 remains a relevant protocol, especially for connecting to older systems or for specific integration scenarios within Avaya Aura. Communication Manager is the component responsible for managing H.323 endpoints and trunks. Creating an H.323 trunk between a Communication Manager and another system, like a Session Manager's H.323 trunking interface or a legacy PBX, requires several distinct configuration steps. The Avaya 7120X exam will test your knowledge of this specific procedure.

The first step is to define the far-end system in the CM's network configuration. This is done using the change node-names ip command in the System Access Terminal (SAT). Here, you create an entry that maps a logical name to the IP address of the H.323 device you are connecting to. This name will be referenced in subsequent steps, so it is a critical prerequisite. Without this node name entry, CM will not know where to send the H.323 signaling traffic.

Next, you must create a signaling group using the add signaling-group command. This object defines the communication parameters for the trunk's signaling path. You will specify the "Group Type" as H.323 and reference the node name you created in the previous step as the "Far-end Node Name". The signaling group also defines settings like the port for communication and the link loss delay timer. Finally, you create the trunk group itself with the add trunk-group command. On the first page of this form, the "Group Type" field must be set to isdn. This can be confusing, but for H.323 trunks, CM uses the ISDN group type as a template. On a subsequent page, you will then associate this trunk group with the H.323 signaling group you just created.

H.323 Endpoint Registration

In an Avaya Aura environment, the registration process for H.323 endpoints is fundamentally different from that of SIP endpoints. While SIP endpoints register with Session Manager, H.323 endpoints register directly with Communication Manager. The Communication Manager acts as the H.323 gatekeeper, handling all registration and call control for these devices. This is a critical distinction that you must understand for the Avaya 7120X exam. A question might present a scenario with an H.323 phone and ask which component it should be configured to register with.

For an H.323 endpoint, such as an Avaya 96x1 series phone running H.323 firmware, to register, its configuration files must point it to the IP address of the Communication Manager's Processor Ethernet interface. This is the primary network interface of the CM server that is used for call control signaling. The phone sends its H.323 Registration, Admission, and Status (RAS) messages to this IP address. Communication Manager receives these messages, validates the endpoint's extension against its configured station database, and if successful, allows the phone to register.

This direct registration to CM means that the initial call signaling for an H.323 phone does not traverse Session Manager. However, once a call is established, Session Manager may still be involved. For example, if an H.323 user calls a SIP user, the call signaling will be sent from Communication Manager to Session Manager via the configured H.323 or SIP trunk between them. Session Manager then processes the call and routes it to the destination SIP endpoint. Understanding this call flow is key to grasping the integrated nature of the Aura platform.

Exploring Advanced CM Features: Single Button Press-Park Pickup

Communication Manager is renowned for its extensive feature set, and new capabilities are added with major releases. The Avaya 7120X exam may include questions about specific features to test your knowledge of their operation and configuration. One such feature introduced in Aura 7.x is the "Single Button Press-Park Pickup". This feature streamlines the process of parking a call and allowing another user to retrieve it, combining what was previously two separate actions into a more intuitive workflow for team environments.

Several key characteristics of this feature are important to remember. When a user with this feature enabled presses their configured call-park button during an active call, the call is immediately parked in a system-wide queue. This action simultaneously triggers a call pickup alert to all other members of that user's defined pickup group. This proactive alerting is a major part of the feature, as it informs team members that a call is waiting for them without them needing to manually check a park orbit. A user can therefore delegate a call to their team simply by parking it.

Another core aspect of this feature is the ease of retrieval. The other members of the pickup group can see the alerting parked call on their phones. To retrieve it, they simply press their own call-park button. This single action answers the call, making the process much faster than traditional methods that required dialing a specific park orbit code. Furthermore, with a single button press, users can also pick up calls that were parked by another team member, fostering a collaborative call-handling environment. This seamless integration of park and pickup is the feature's primary benefit.

Contrasting SIP and H.323 Trunking

In Avaya Aura, both SIP and H.323 protocols are used for trunking between major components. While they achieve a similar goal of connecting systems, their configuration and underlying operation are quite different. As discussed previously, an H.323 trunk in Communication Manager requires a node-name entry, an H.323 signaling group, and an ISDN-type trunk group. This multi-step process is specific to the way CM handles H.323 connections. All configuration for this trunk type is done exclusively within the Communication Manager's SAT interface or SMI.

SIP trunks, on the other hand, are primarily configured within System Manager, as they are managed by Session Manager. To create a SIP trunk from Session Manager to Communication Manager, you would first define a SIP Entity in SMGR to represent the CM. Then, you would configure routing policies to direct calls to that entity. On the Communication Manager side, you would also configure a SIP signaling group and a SIP trunk group. The key difference is that the central routing intelligence for SIP trunks resides in Session Manager, whereas H.323 trunk routing is handled entirely by Communication Manager's dial plan.

The choice between SIP and H.323 for the trunk between CM and SM has design implications. The Avaya-recommended and most common approach is to use a SIP trunk, as this keeps the core of the network SIP-native and allows Session Manager to have full visibility and control over the call flow. Using an H.323 trunk is a valid option, often used during migrations or for specific feature integrations, but it means that CM is acting as an H.323 gateway, and calls are converted from SIP to H.323 and back again as they traverse the trunk, which can add complexity.

Understanding Trunk Group Configuration Details

When configuring any type of trunk group in Communication Manager, the SAT form presents numerous fields that control its behavior. For the Avaya 7120X, you should be familiar with the key fields on the trunk group administration screen. One of the most basic but critical fields is the "Group Type". This field determines the technology and protocol the trunk group will use. The options include isdn, sip, co (Central Office), and others. As noted earlier, when building an H.323 trunk, you must select isdn as the group type, even though the signaling is H.323. For a native SIP trunk, you would select sip.

Another important element is the "Group Name," which is a descriptive label for the trunk group. On subsequent pages of the form, you will associate the trunk group with its corresponding signaling group. This linkage is what tells the trunk group which signaling protocol and path to use. The form also includes fields for assigning a Class of Restriction (COR) and a Class of Service (COS) to the trunk group. The COR assigned to a trunk group is particularly important as it helps control toll fraud by restricting the types of outbound calls that can be made over that trunk.

The number of "Members" in the trunk group is also defined on this form. For IP-based trunks like SIP or H.323, this number represents the maximum number of concurrent call channels that can be active over the trunk at any given time. This is a critical capacity management setting. If all members of a trunk group are in use, any new call attempt will be rejected, typically with a busy signal. Properly sizing the trunk group based on expected call volume is a key aspect of system design and administration.

The Importance of Node-Names in IP Connectivity

The node-names table in Communication Manager is a foundational networking configuration that serves as a local DNS resolver for the system. The command display node-names ip allows an administrator to view this table. It contains a list of hostnames and their corresponding IP addresses. Communication Manager uses this table to resolve the IP addresses for all its IP-based communication, including connections to media gateways, Avaya Aura Messaging servers, and other systems it needs to communicate with via an IP trunk.

When you configure an H.323 signaling group, you specify the "Far-end Node Name". CM looks up this name in the node-names table to find the IP address it needs to send the H.323 signaling to. If the entry is missing or incorrect, the trunk will fail to establish a connection. Therefore, populating the node-names table is one of the very first steps an administrator must take when integrating CM with other IP-based systems. This principle applies not only to H.323 trunks but also to media gateways (CLAN and Medpro boards) and other IP-connected resources.

While modern networks rely heavily on DNS, the internal node-names table in CM provides a self-contained and reliable method for name resolution, removing dependency on an external DNS server for critical internal communications. This ensures that even if the corporate DNS server is unavailable, CM can still communicate with its essential components like gateways and application servers. For the Avaya 7120X exam, remember that the node-names table is a prerequisite for establishing almost any IP-based connection from Communication Manager.

Go to testing centre with ease on our mind when you use Avaya ACIS-7120 7120X vce exam dumps, practice test questions and answers. Avaya 7120X Avaya Aura Core Components Integration Exam certification practice test questions and answers, study guide, exam dumps and video training course in vce format to help you study with ease. Prepare with confidence and study using Avaya ACIS-7120 7120X exam dumps & practice test questions and answers vce from ExamCollection.