
Avaya MPS Architectural Overview
# P0602477 Ver: 3.1.11 Page 49
VMM
VMM resides in the VOS subcomponent of the MPS component and provides media
management services for the VOS. When VMM starts it connects to TCAD, TRIP and
the VMEM port of the TMS. Once VMM detects that TCAD has configured the TMS,
VMM loads the Voice Data Memory (VDM).
The startup time for VMM is minimal and does not delay speak/record requests unless
the system is under heavy load. In the case of a record request under heavy load, the
TMS buffers that data destined for VMM. Since input/output (I/O) blocking is
performed, VMM is capable of servicing all other requests that arrive while prior I/O
requests are awaiting completion, eliminating direct impact on other lines.
The VMM process is primarily responsible for:
• loading and managing VDM
• loading and managing media MMF files both system wide and application
specific (playback and record)
• creating and managing hash tables of element names
• performing hash lookups on behalf of CCM
• performing on-line updates and deletes
• receiving data for ethernet based Caller Message Recording (CMR)
• maintaining maximum workload constraints and related queuing of pending
I/O operations
• maintaining media access related statistics (reference counts and cache hits,
for example)
The VSH interface provides the ability to send commands to VMM. For a list of these
commands, see the VMM Commands section in the Avaya Media Processing Server
Series Command Reference Manual.
VMM associations:
• Connections: CCM, TRIP, TCAD, and the VMEM port of the TMS
• Location: $MPSHOME/bin or %MPSHOME%\bin
• Configuration File: $MPSHOME/mpsN/etc/vmm.cfg
• $MPSHOME/mpsN/etc/vmm-mmf.cfg
• SRP Startup File: $MPSHOME/mpsN/etc/vos.cfg
Comentarios a estos manuales