Avaya Communication Manager Messaging
Home Getting StartedAdministrationMaintenanceReference

Search This CD

Index

Contact Us

 

 

 

  
Home > Getting Started > Concepts and Features > System Architecture

System Architecture

This section discusses the hardware and software components that make up Communication Manager Messaging. Topics include:

See Messaging Architecture for an illustration of the hardware and software components that comprise the Communication Manager Messaging server.

Communication Manager server and Communication Manager Messaging Sever co-residency

Communication Manager and Communication Manager Messaging are installed on the same server and are integrated using H.323 and / or Q.Sig protocol.

Media Gateways

No media gateway servers and associated circuit hardware is required.

Communication Manager server

To install CM Messaging release 5.2 software, the Communication Manager software must be release 5.2 and can reside any of the following servers: S8300C, S8300D, S8400A, S8400B, S8500C or S8510 Server.

The Communication Manager server comes loaded with the following resources:

  • Red Hat Enterprise Linux Version 4 operating system
  • Web server software
  • TFTP server software
  • H.248 and H.323 protocol IP software
  • Avaya Communication Manager software, which serves as the primary voice/data communications application

The Communication Manager server serves as a full-featured integrated data and phone communication system. The Communication Manager server has its own IP address for administration access.

Disk Partitioning

The disk partitioning scheme has three partitions (two active and one duplicate).

The layout of active partitions used by the Communication Manager server products is defined as follows:

  • /msg/software: for messaging software, database, and add-on applications. Symbolic links, references to mount points, and so on are modified as needed to preserve the existing directory structure. The size of this partition is at least as large as the sum of the replaced three partitions on the latest Communication Manager server product.
  • /msg/media1: for the message bodies. The size of this partition is at least as large as the existing partition on the latest Communication Manager server product.

Note:
This assumes the partition size is already adjusted to account for the move from the denser CELP voice encoding to the G711 voice encoding.

Communication Manager:

    • Is used to create stations, coverage path, trunk groups
    • Has a different IP address for remote administration access and TCP/IP networking functions such as Digital Networking and Message Manager

Resources Shared by Communication Manager Messaging and Communication Manager

CM Messaging release 5.2 application is a voice messaging system that is based on the Intuity AUDIX family of messaging applications. The CM Messaging application uses many of the media gateway and Communication Manager server resources for call processing, access and use of administrative tools.

As a result, the administrator administers some functions directly on the messaging software, while the administrator administers other functions used by the messaging software by administering the Communication Manager server platform.

Communication Manager Messaging Software

Requirements:

  • Communication Manager release 5.2

Security enhancements and scalability

  • Telnet (Command Line) screens are replaced by web administration pages
  • Use of User based profiles created by Communication Manager
  • Increased capabilities for S8300, S8400, and S8500 Servers.
  • Disallows Voice Mail PINS Related to Mailbox Number
  • Aging of Voice Mail PINs
  • Enabling Aging of Voice Mail PINs
  • Configuring Aging of Voice Mail PINs
  • Range for Maximum Age of Voice Mail PINs
  • Default Aging of Voice Mail PINs
  • Locking of Voice Mail After Invalid PIN Attempts
  • Enabling Locking of Voice Mail After Invalid PIN Attempts
  • Configure Number of Invalid PIN Attempts Resulting in Locking of Voice Mail Account
  • Range for Number of Invalid PIN Attempts Resulting in Locking of Voice Mail Account
  • Number of Invalid PIN Attempts that Shall be Allowed in a Single TUI session
  • Aggregation of Invalid PIN Attempts Across Interfaces
  • Reduction of Count of Invalid PIN Attempts
  • Default Number of Invalid PIN Attempts Resulting in Locking of Voice Mail Account
  • Configurable Duration of Voice Mail Account Locking
  • Range for Duration of Voice Mail Account Locking
  • Default Duration of a Voice Mail Account Lock
  • Configure Duration of a Voice Mail Account Lock to Never Expire
  • Unlocking of Voice Mail Account by Administrator
  • Locking of Voice Mail After Invalid PIN Attempts Applies to All Access Methods
  • Locking of Voice Mail Applies to an Access Method on Next Login Attempt
  • Locking of Voice Mail Doesn't Prevent Addition of New Messages
  • Logging of Voice Mail Locking
  • Alarming of Voice Mail Locking
  • History of Voice Mail Account PINs
  • Enabling Voice Mail Account PIN History
  • History of Voice Mail account PINs Enabled by Default
  • Configuring Voice Mail Account PIN History
  • Range of Number of Voice Mail Account PINs Saved in History
  • Default Number of Voice Mail Account PINs Saved in History
  • Voice Mail Account PINs Saved in History Not Usable as New PINs
  • Default Voice Mail Account PIN Length

Communication Manager Messaging:

  • Embedded application on the Communication Manager application
  • Does not need a license file. CMM uses the Communication Manager server's license file for feature activation
  • Uses a separate IP address for administration

Communication Manager Messaging provides the following features:

  • The subscriber telephone user interface (TUI) software
  • The messaging administration command line interface (SSH sessions that service technicians can use)
  • Messaging software, which enables the messaging system to use lower level functions and includes the following capabilities:
    • Switch integration software
      This software allows call control messages (timestamps, calling party information, called party information, and message waiting indicator control) to pass between the messaging software and the Communication Manager server Communication Manager software.
    • Virtual port software
      This software manages the voice message processing and emulates physical analog ports for sending and receiving voice messages.
    • Event and alarm logging software
      This software logs alarms and sends them to the Communication Manager server Global Alarm Manager.
    • Disk space management
      This software manages the portion of the Communication Manager server hard drive that is allocated to the messaging software.
  • Digital networking
  • Communication Manager Messaging Hardware

    Supported Servers

    S8300C, S8300D, S8400A, S8400B, S8500C or S8510 Servers

    H.323 protocol

    This protocol integrates CM Messaging and CM, as a result CMM can use the call processing ability of CM.

    Disk Partioning

    The CM Messaging server does not use RAM Disk. As a result, the server does not create a RAM Disk partition and does not boot from RAM Disk.

    Media Modules

    No media modules required for CM Messaging.

    Ports

    Communication Manager servers have a serial port. This serial port can be used for a direct connection to a laptop or PC. The port is called Service on the S8400 Server.

    The AUDIX Data Acquisition Package (ADAP) is not supported to work with the CM Messaging software.

    Terminals

    You can administer the system through the use of a SSH session and one of the following terminal emulations:

    • Avaya 386
    • Avaya 4410 (for PROCOMM PLUS 4410 or Terranova emulation)
    • Avaya 513 (for Terranova emulation)
    • Avaya 715
    • Avaya 4425
    • vt100

     

    Top of page

      Search This CD     Index     Contact Us
    � 2002-2009 Avaya Inc. All rights reserved.