The ECTF component is divided into several areas. They are:
The Resource Core component is responsible for providing a framework for communication with the CTMedia Server, into which other media components integrate. The resource core provides a hierarchical framework for the orderly startup and shutdown of media.
The Low Level Suite (LLS) Core is a low-level component responsible for communication with the DSP firmware. If provides a framework into which other media components integrate. The LLS core receives events from the DSP firmware and passes them to the media resources. The LLS core also monitors the health of DSPs by periodically pinging them. The other media resources include: signal detection, signal generation, speech recognition, voice play and record, FAX transmit and receive.
The Voice Resource provides voice playback and recording functionality to applications. The player reads voice data from the Multimedia File System (MMFS) and passes it to the DSP for decompression. The player also responds to positioning commands (such as play skip). The recorder receives compressed voice data from the DSP and stores it into the MMFS.
The Fax Resource provides fax transmit and receive functionality to applications. The transmitter reads fax data from the Multimedia File System (MMFS) and passes it to the DSP for transmission. The transmitter also generates header and footer trim tabs.
The Signal Resource component provides signal detection and generation services to MAS applications. It contains two component, one for signal detection and the other for signal generation. Signal resource components uses Multimedia Processing Components for detecting and generating signals. The capabilities provided by signal resource are DTMF detection, DTMF generation, Call Progress Tone Detection, Energy Detection, DISA tone detection, and customized tone generation.
The ASR Resource provides Speech Recognition capabilities to MAS applications. The ASR resource uses the speech recognition technology developed by Lernout & Hauspie and runs on MAS Multimedia Processing Components.
The functionality’s provided by ASR in MAS R2.0 are:
Single word speech detection in speaker independent mode.
User word detection in speaker dependent mode.
Tokenizer capabilities for collecting voice sample for analysis. ASR resource APIs are accessed by application using S.100 compatible APIs via CTMS server. In order to make use of ASR, it is necessary that the Middleware is properly configured on the server.
The Call Channel Resource (CCR) is a CTM resource that represents a port on the Switch. CCr notifies application when the port is idle or active. It supports port maintenance operations, time slots setup/teardown between the port and SCbus. It interfaces with TAPI for port related telephony information.
The Blue Call Router (BCR) provides functionality to route incoming calls that are queued at a Controlled DN (CDN) on the switch onto the appropriate Applications for further treatment of the call. It is built upon lower-level call control services, such as TAPI and AML, that have specialized knowledge of the call control environment in which the CTMedia server operates. Using the Group Management APIs of CTMS, and call control APIs provided by TAPI, BCR provides Applications with a simple method of receiving incoming calls, making outgoing calls and passing calls to other applications.
EMCI is a MAS Middleware server which runs as a Windows NT service. Its purpose is to bring up, monitor, maintain, and bring down Middleware services as needed. EMCI is an essential service for call processing. EMCI is service and its startup, recovery, and shutdown are controlled by MAS System Manager.
The events that occur when EMCI starts up are as follows:
EMCI scan the system for hardware components such as Multimedia Processing Boards, Multimedia Processing Cards, Signal Computing Bus, DS30X etc. as well their configuration in the MAS database.
EMCI starts up diagnostics on the hardware detected and ACD Proxy server for Switch/TSP initialization.
Once the diagnostics and ACD Proxy initialization successfully completed, EMCI starts up Middleware (Blue Call Router, Media Resource, Call Channel Resource, and Maintenance Service Provider.
Once the Middleware is up and running, EMCI continue to monitor them for failures and restarts any failed components.
Once the EMCI completed Middleware startup, it
Handles Maintenance requests from the MAS client via DMI server.
Monitor DSP removal and insertion into the system and modify the state of the DSP concerned 3) Notify any administrative state changes of MAS components that are monitored by EMCI to the MAS Maintenance Server.
Monitors and exports error logs produced by the CTMS to MAS fault management.
When the EMCI shuts down, the following events occur:
EMCI brings up the Middleware.
Terminate ACD Proxy server.
Cleanup any files or handles opened.
Severity INFO
Description Resource Monitor (audit) thread started.
Impact Not applicable
Recovery Action Not applicable
Technical Support Action Not applicable
Severity INFO
Description Resource Monitor shutdown as commanded by System Manager.
Impact Not applicable
Recovery Action Not applicable
Technical Support Action Not applicable
Severity INFO
Description Resource Monitor shutdown immediately without cleanup as commanded by System Manager.
Impact Not applicable
Recovery Action Not applicable
Technical Support Action Not applicable
Severity INFO
Description Failed to log Operation Measurement statement to report size of all logical drives
Impact Cannot record logical drives data. No system or customer impact.
Recovery Action Not applicable
Technical Support Action Refer to return code and related events. Look for Operation Measurement Server events for more iformation.
Severity MAJOR
Description Failed to retrieve CPU performance data
Impact Cannot evaluate the CPU performance.
Recovery Action Check CPU performance from Windows Task Manager on CallPilot server PC. Contact your technical support organization if experience performance problem.
Technical Support Action Check CPU usage from Windows Task Manager on CallPilot server PC and make note of which process(es) takes up most of the CPU usage. Save a copy of the event log. If performance problem remains after peak operating hour, reboot system if necessary.
Severity MAJOR
Description Could not find system threshold registry entry.
Impact CallPilot may not be installed completely. Resource Monitor may log events about insufficient resource.
Recovery Action Contact your technical support organization to verify the CallPilot server is installed completely.
Technical Support Action Check for incomplete installation. Reinstall CallPilot server if necessary.
Severity MINOR
Description Detected invalid drive log thresholds set. Use default threshold values instead.
Impact If the system threshold was modified before, it will not take effect.
Recovery Action Reconfigure system threshold from CallPilot Manager.
Technical Support Action Reconfigure system threshold from CallPilot Manager.
Severity MINOR
Description Detected invalid drive broadcast thresholds set. Use default threshold values instead.
Impact If the system threshold was modified before, it will not take effect.
Recovery Action Reconfigure system threshold from CallPilot Manager.
Technical Support Action Reconfigure system threshold from CallPilot Manager.
Severity MINOR
Description Detected invalid MMFS text/voice thresholds set. Use default threshold values instead.
Impact If the system threshold was modified before, it will not take effect.
Recovery Action Reconfigure system threshold from CallPilot Manager.
Technical Support Action Reconfigure system threshold from CallPilot Manager.
Severity CRITICAL
Description Could not detect any MISA volumes to monitor.
Impact If MISA volume cannot be detected, all messaging services will not function. CallPilot cannot play voice prompts, messages, etc. CallPilot may not be installed completely.
Recovery Action Contact your technical support organization to verify the CallPilot server is installed completely.
Technical Support Action Check for incomplete installation. Reinstall CallPilot server if necessary.
Severity CRITICAL
Description Could not detected database.
Impact If database cannot be detected, all messaging services will not function. CallPilot cannot be administrated/configured, mailbox login will fail, etc. CallPilot may not be installed completely.
Recovery Action Contact your technical support organization to verify the CallPilot server is installed completely.
Technical Support Action Check for incomplete installation. Reinstall CallPilot server if necessary.
Severity MAJOR
Description Database space is getting low.
Impact If CallPilot runs out of database space, administration/configuration may be affected. Operational Measurement will also be affected. Messaging services should not be affected.
Recovery Action Contact your technical support organization to verify sufficient database size was allocated as specified in customer order.
Technical Support Action Check for insufficient database size.
Severity MAJOR
Description Disk space is getting low.
Impact CallPilot system may slow down due to insufficient disk space available on the system.
Recovery Action Check for insufficient disk space on CallPilot server. Contact your technical support organization for solution.
Technical Support Action Check for insufficient disk space size.
Severity MAJOR
Description "Database internal free space is getting critically low. It has reached 98% capacity.
Impact CallPilot system may slow down due to insufficient disk space available on the system.
Recovery Action OM is storing too many records in the database. Reduce your OM storage size further(System/OM Configuration/storage size)
Technical Support Action No action, the Admin action should correct, if not the 100% Major alarm will stop LDAP updates/inserts and GNTS will be required.
Severity INFO
Description OM is not pegging information to the database since the database is at 98% or 100% full capacity.
Impact Valuable information may be lost.
Recovery Action OM is storing too many records in the database. Reduce your OM storage size further(System/OM Configuration/storage size)
Technical Support Action No action, the Admin action should correct, if not the 100% Major alarm will stop LDAP updates/inserts and GNTS will be required.
Severity INFO
Description OM is pegging information to the database..
Impact None. Information only.
Recovery Action No action required. Information only.
Technical Support Action No action, the Admin action should correct, if not the 100% Major alarm will stop LDAP updates/inserts and GNTS will be required.
Severity INFO
Description Database internal free space is getting low. It has reached 95% capacity.
Impact CallPilot system may slow down due to insufficient limited internal disk space available on the system.
Recovery Action OM is storing too many records in the database. Reduce your OM storage size (System/OM Configuration/storage size)
Technical Support Action No action, the Admin action should correct, if not the 98% Major alarm will stop OM pegging.
Severity Critical
Description The timeswitch software could not initialize because an invalid platform type has been specified. Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Platform type information should be configured at installation time. Consult the product documentation for details on how to perform this task. Once the platform type has been set, shutdown and reboot the server.
Technical Support Action The nbhwtest.exe support tool can be used to set, query, and alter the platform type. The only supported platform types are TRP and IPE (i.e., 200i). Platform type information is stored in the registry.
Severity Critical
Description The timeswitch software could not initialize because it could not determine the current platform. Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Platform type information should be configured at installation time. Consult the product documentation for details on how to perform this task. Once the platform type has been set, shutdown and reboot the server.
Technical Support Action The nbhwtest.exe support tool can be used to set, query, and alter the platform type. The only supported platform types are TRP and IPE (i.e., 200i). Platform type information is stored in the registry.
Severity Critical
Description The timeswitch software could not initialize because it could not determine the current version number of the installed timeswitch hardware. Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Ensure that the ntbus and c52 drivers are running. Shutdown and restart the server.
Technical Support Action Try replacing the MPB.
Severity Critical
Description The timeswitch software could not initialize because it received an invalid version number for the hardware. Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Ensure that the ntbus and c52 drivers are running. Shutdown and restart the server.
Technical Support Action Try replacing the MPB.
Severity Minor
Description The timeswitch software could not initialize because it determined that no voice processing hardware was present on the platform. Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Ensure that the MPB is properly seated into its backplane/PCI slot. Ensure that the ntbus and c52 drivers are running. Shutdown and restart the server. If this error reoccurs, then all of the MPBs or the 200I are not functioning properly. Try replacing these items.
Technical Support Action Try replacing the MPB
Severity Minor
Description The timeswitch software could not initialize because it encountered an internal software bug. Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action Please report the occurrence of this software problem to Nortel Networks.
Severity Critical
Description The timeswitch software could not initialize because it encountered an internal software error (could not set security descriptor) Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action Please report the occurrence of this software problem to Nortel Networks
Severity Critical
Description The timeswitch software could not initialize because it encountered an internal software error (could not set security descriptor) Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action Please report the occurrence of this software problem to Nortel Networks
Severity Critical
Description The timeswitch software could not initialize because it encountered an internal software error (could not create Mutex software) Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action Please report the occurrence of this software problem to Nortel Networks
Severity Critical
Description The timeswitch software could not initialize because it could not open a required UNICODE text file (version file) Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action Ensure that the specified file exists and is located in the local directory. The problem should not normally occur; the file may have been deleted or moved. A reinstall is required.
Severity Critical
Description The timeswitch software could not initialize because a required UNICODE text file that it depends upon for configuration information has been corrupted (version file) Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action The problem should not normally occur; the file may have been deleted or moved. A reinstall is required.
Severity Critical
Description The timeswitch software could not initialize because a required UNICODE text file that it depends upon for configuration information has been corrupted (version file) Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action The problem should not normally occur; the file may have been deleted or moved. A reinstall is required.
Severity Critical
Description The timeswitch software could not initialize because it encountered an internal software error (buffer too small) Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action Please report the occurrence of this software problem to Nortel Networks.
Severity Critical
Description The timeswitch software could not initialize because it encountered an internal software error (could not close version file) Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action Please report the occurrence of this software problem to Nortel Networks
Severity Critical
Description The timeswitch software could not initialize because it could not open a required UNICODE text file (mapping file) Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action Ensure that the specified file exists and is located in the local directory. The problem should not normally occur; the file may have been deleted or moved. A reinstall is required.
Severity Critical
Description The timeswitch software could not initialize because it encountered an internal software error (could not close mapping file) Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action Please report the occurrence of this software problem to Nortel Networks.
Severity Critical
Description The timeswitch software could not initialize because a required UNICODE text file that it depends upon for configuration information has been corrupted (mapping file). Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action The problem should not normally occur; the file may have been deleted or moved. A reinstall is required.
Severity Critical
Description The timeswitch software could not initialize because a required UNICODE text file that it depends upon for configuration information has been corrupted (mapping file). Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action The problem should not normally occur; the file may have been deleted or moved. A reinstall is required.
Severity Critical
Description The timeswitch software could not initialize because a required UNICODE text file that it depends upon for configuration information has been corrupted (mapping file - memory section). Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action The problem should not normally occur; the file may have been deleted or moved. A reinstall is required.
Severity Critical
Description The timeswitch software could not initialize because a required UNICODE text file that it depends upon for configuration information has been corrupted (mapping file - idle channel section_. Consult the Windows NT Event Log for details.
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Contact your technical support organization.
Technical Support Action The problem should not normally occur; the file may have been deleted or moved. A reinstall is required.
Severity Critical
Description The timeswitch software could not initialize because it encountered an internal software error (could not create file mapping object). Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Ensure that the local disk drive is not full. Contact your technical support organization.
Technical Support Action Please report the occurrence of this software problem to Nortel Networks.
Severity Critical
Description The timeswitch software could not initialize because it encountered an internal software error (could not zero file mapping section). Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Ensure that the local disk drive is not full. Contact your technical support organization.
Technical Support Action Please report the occurrence of this software problem to Nortel Networks.
Severity Critical
Description The timeswitch software could not initialize because it encountered an internal software error (could not map view of file mapping section). Consult the Windows NT Event Log for details.
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted.
Recovery Action Ensure that the local disk drive is not full. Contact your technical support organization.
Technical Support Action Please report the occurrence of this software problem to Nortel Networks.
Severity Critical
Description The timeswitch software could not initialize because it could not determine the platform type dynamically (querying Ntbus1 for the platform type failed). Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Ensure that the local disk drive is not full. Contact your technical support organization.
Technical Support Action Please report the occurrence of this software problem to Nortel Networks.
Severity Critical
Description The timeswitch software could not initialize because it encountered an internal software error (could not acquire DLLAtach Mutex object). Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Ensure that the local disk drive is not full. Contact your technical support organization.
Technical Support Action Please report the occurrence of this software problem to Nortel Networks.
Severity Critical
Description The timeswitch software could not initialize because it encountered an internal software error (could not release previously acquired DLLAtach Mutex object). Consult the Windows NT Event Log for details..
Impact The timeswitch software cannot be used; as a result no call processing can take place. The system has been severely impacted..
Recovery Action Ensure that the local disk drive is not full. Contact your technical support organization.
Technical Support Action Please report the occurrence of this software problem to Nortel Networks.