
Avaya MPS Architectural Overview
# P0602477 Ver: 3.1.11 Page 39
ASE/VOS Integration Layer
This layer is used to convert and translate messages from the applications to the VOS
processes. For PeriProducer applications, this layer communicates with the ASE
processes, which in turn communicate with the applications themselves. The Vengine
Application Management Process (VAMP) is an interface between the Application
Services Environment (ASE) and the Voice Operating Software (VOS).
The VAMP services application requests:
• Consolidate information (lines, resources, etc.) for applications
• Consolidate information for commands issued by applications
• Control line bridging based on Call Progress Detection information
• Process resource control commands which may be directed to different
resource providers and have different formats
VOS Processes
The Voice Operating Software (VOS) process group is comprised of the main system
software required to run the MPS system. VOS processes can be common (only one
instance required per node) or MPS-specific (one instance required per MPS
component). This software group consist of the following independently running
processes:
Process Description
ALARMD (Alarm Daemon) Collects alarm messages, writes them to
the alarm log, and forwards them to any
running alarm viewers.
CCM (Call Control Manager) The primary interface between VAMP
and the VOS services. Provides request
synchronization and resource
management.
COMMGR (Communications Manager) Manages external host communications.
CONFIGD (Configuration Daemon) System wide configuration process.
CONOUT (Console Output Process) Relays output from VOS processes to
the system console.
CONSOLED (Console Daemon) Takes messages that would normally
appear on the system console and
displays them in the alarm viewers.
(Solaris only.)
NCD (Network Interface Controller
Daemon)
Controls interconnections between
multiple TMS platforms attached to the
NIC card.
nriod Daemon responsible for remote
input/output.
Comentarios a estos manuales