The Access Protocol Emulator (APE) implements Meridian Access Protocol and Access Link Protocol. The Access Link Protocol is used on messages exchanged over a TCP connection between CallPilot and SCCS.
APE routes Access messages between Access applications and call applications. APE is also communicating with BCR for resource allocation, e.g., acquire/release voice channels.
Call applications communicate with APE using the Access Protocol Library which is a DLL.
Severity Critical
Description Error occurred in process initialization.
Impact The application will terminate.
Recovery Action Reboot or restart the application. If problem persists, call Customer Service.
Technical Support Action Check the return code. If problem persists, call Product Support.
Severity Critical
Description Error occurred in process initialization.
Impact The application will terminate.
Recovery Action Reboot or restart the application. If problem persists, call Customer Service.
Technical Support Action Check the return code. If problem persists, call Product Support.
Severity Critical
Description Unable to allocate memory buffers for Access messages.
Impact The application will terminate.
Recovery Action Reboot and perhaps allocate more virtual memory space on the hard drive.
Technical Support Action If problem persists, call Product Support. The system could be checked for possible memory leaks.
Severity Critical
Description Incompatible Windows Sockets library was used by the application.
Impact The application will terminate.
Recovery Action Call Customer Service.
Technical Support Action Check the return code. It may be caused by possible installation problems. If problem persists, call Product Support.
Severity Critical
Description Error occurred in process initialization
Impact The application will terminate.
Recovery Action Reboot or restart the application. If problem persists, call Customer Service.
Technical Support Action Check the return code. If problem persists, call Product Support.
Severity Critical
Description Error occurred in process initialization.
Impact The application will terminate.
Recovery Action Check registry settings for the application. Ensure the TCP port number matches what is defined on the Symposium server. Reboot. If problem persists, call Customer Service.
Technical Support Action Check the return code. If problem persists, call Product Support.
Severity Major
Description Broken TCP connection between Access Protocol Emulator and the Symposium server.
Impact Access applications will not be able to communicate with call applications.
Recovery Action Check the system status of CallPilot to ensure it is call processing ready or better. Check network connectivity by pinging the Symposium server ELAN IP address, e.g., "ping 12.34.56.78". If "ping" responds successfully, restart the CallPilot Access Protocol Emulator service. If problem persists after the restart, call Customer Service.
Technical Support Action Check the return code. If problem persists, call Product Support.
Severity Major
Description Broken named pipe connection between Access Protocol Emulator and call applications.
Impact Access applications will not be able to communicate with call applications.
Recovery Action If problem persists, reboot or restart the application. If problem persists after the restart, call Customer Service.
Technical Support Action Check the return code. If problem persists, call Product Support.
Severity Major
Description This is part of the message throttling mechanism to avoid storing large amount of Access messages while the upstream communication problem occurred between Access Protocol Emulator and call applications.
Impact Access applications cannot send message to call applications.
Recovery Action If alarm persists, reboot or restart the application. If problem persists after the restart, call Customer Service.
Technical Support Action If problem persists, call Product Support.
Severity Major
Description This is part of the message throttling mechanism to avoid storing large amount of Access messages while the downstream communication problem occurred between Access Protocol Emulator and Access applications.
Impact Call applications cannot send message to Access applications.
Recovery Action If alarm persists, reboot or restart the application. If problem persists, call Customer Service.
Technical Support Action Check for possible network problems. If problem persists, call Product Support.
Severity Critical
Description Error occurred in network communication initialization.
Impact The application will terminate.
Recovery Action Reboot or restart the application. If problem persists, call Customer Service.
Technical Support Action Check the return code. If problem persists, call Product Support.
Severity Critical
Description Unable to acquire voice channels from BCR.
Impact The application will terminate.
Recovery Action Reboot or restart the application. If problem persists, call Customer Service.
Technical Support Action Check the return code. If problem persists, call Product Support.
Severity Minor
Description Unable to acquire voice channel.
Impact The application will retry.
Recovery Action If problem persists, call Customer Service.
Technical Support Action Check the returned code. If problem persists, call Product Support.
Severity Major
Description Access link between CallPilot and SCCS is down due to loss of polling.
Impact Access applications will not be able to communicate with call applications.
Recovery Action Check link cable connection. Check network connectivity by pinging the SCCS ELAN IP address, e.g., "ping 12.34.56.78". If "ping" responds successfully, restart the CallPilot Access Protocol Emulator service. If problem persists after the restart, call Customer Service.
Technical Support Action If problem persists, call Product Support.
Severity Info
Description Access link between CallPilot and SCCS has synced up.
Impact Access applications are able to communicate with call applications.
Recovery Action None
Technical Support Action None
Severity Major
Description Error occurred in Access Protocol Library initialization function.
Impact Access applications will not be able to communicate with call applications.
Recovery Action Reboot or restart application. If problem persists, call Customer Service.
Technical Support Action Check return code. If problem persists, call Product Support.