Components

Last Updated : Jun 04, 2018 |
Prolog information
The following table briefly describes the components in the IP Office Branch solution and how these components fit into the Branch architecture. Some of these components are only implemented in certain branch deployment environments. For more information about supported Avaya and third-party components, see https://secureservices.avaya.com/compatibility-matrix/menus/product.xhtml?name=IP+Office+Platform.
Branch components
Component
Reference Configuration Characteristics
IP Office
Includes hardware and software components. In this solution, there is an IP Office in each branch. IP Office systems can be deployed as stand-alone branches or connected to an Avaya Aura® network.
Main Avaya Aura® network
Avaya Aura® provides access to centralized services.
  • Avaya Aura® System Manager provides administrative functions that administrators can use to easily manage all users and IP Office systems in the enterprise. In a Distributed, Mixed, or Centralized environment, IP Office branches are connected to the Avaya Aura® System Manager server.
    Note:
    Avaya Aura® System Manager does not manage the following applications: Voicemail Pro, Avaya one-X® Portal for IP Office, CCR, and Unified Communications Module.
  • Avaya Aura® Session Manager connects branches to each other and to other applications and services in the enterprise center. For IP Office users in Distributed and Mixed deployment environments, Avaya Aura® Session Manager acts as a SIP proxy to route SIP sessions to and from the SIP connections to the IP Office. For centralized users, Avaya Aura® Session Manager is also the main interface that handles user registration and call routing.
  • Avaya Aura® Communication Manager provides telephony services to centralized users through Avaya Aura® Session Manager.
  • Avaya WebLM is included within the Avaya Aura® System Manager and provides centralized licensing management.
  • Secure Access Link (SAL) provides remote access and alarm reception capabilities. The SAL Gateway is installed on a Red Hat Enterprise Linux host in the customer network and acts as an agent on behalf of several managed elements. All communication is outbound from the environment of the customer and uses encapsulated Hypertext Transfer Protocol Secure (HTTPS).
Other centralized services such as conferencing and messaging are available to centralized users. Some of these services are also available to IP Office users deployed in Distributed and Mixed branch environments. For more information about applications that interoperate with the IP Office branch, see the IP Office branch interoperability section.
CS 1000
In a Distributed branch environment, you can connect CS 1000 to the IP Office in the branch through Avaya Aura® Session Manager. Users still obtain telephony services from the local IP Office, but can use Avaya CallPilot® as their voice mail system.
CS 1000 provides telephony interoperability between IP Office users in the branch and CS 1000 users at other sites. Avaya Aura® System Manager is used to centrally manage CS 1000.
In branch deployments with CS 1000, all IP Office endpoints are supported. Some CS 1000 endpoints can also be migrated to IP Office endpoints. For more information about supported endpoints, see the following documents:
Important:
IP Office does not support Meridian Customer Defined Networking (MCDN), but all major Branch features, including dial plans and centralized voice mail, are supported in Distributed branch environments with CS 1000.
Supported endpoints
All IP Office endpoints are supported as IP Office users. For a list of IP Office endpoints, see phones in Deploying an IP500 V2 IP Office Essential Edition System.
The following SIP endpoints are supported as Centralized users. For information about centralized phones and adding Centralized users to an enterprise branch, see Administering Centralized Users for an IP Office™ Platform Enterprise Branch.
  • 9620 SIP
  • 9630 SIP
  • 9640 SIP
  • 9650 SIP
  • 9601 SIP
  • 9608 SIP
  • 9611G SIP
  • 9621G SIP
  • 9641G SIP
  • 1120E
  • 1140E
  • 1220
  • 1230
  • Avaya B179
  • Avaya J159 IP Phone
  • Avaya J169 IP Phone
  • Avaya J179 IP Phone
  • Avaya J129 IP Phone
  • Avaya J139 IP Phone
  • Avaya J189 IP Phone
  • Avaya Workplace Client for Windows
Note:
The 9600 series SIP phones and Avaya one-X® Communicator SIP are supported only as Centralized phones for use by Centralized users. They are not supported as IP Office phones for use by IP Office users.
The following endpoints are supported as IP Office or Centralized users:
  • Avaya H175 Video Collaboration Station
  • The 1100 and 1200 series phones
  • B179 series phones
  • J100 series for J129, J139, J159, J169/179, J189 phones (Supported only as Standard SIP phone)
IP Office Branch also supports video endpoints connected to IP Office or to the Avaya Aura® infrastructure.