Chapter 1 Overview 35Network Managers Guide for Symposium TAPI Service Provider for Succession, release 3.0• It is a console application, therefore, it is CPU efficient (less than 5%).• Data is written asynchronosly. The Symposium TAPI SP does not wait forTAPIDBM to finish writing before returning to execution.• In the event of a Symposium TAPI SP crash, the TAPIDBM will continue tooutput log data until the buffer is emptied. This makes it possible to acquiremore information up to the point of the crash than was possible with theLogger application.Logger applicationIn the event of problems, you can use the logger tool to trace application activities.During a troubleshooting session, the logger application writes status and errormessages (as defined on the configuration dialog boxes) to the scrollable loggerwindow. When the logger window is full, the logger application writes status anderror messages to a logger overflow file. You can save the information in thelogger overflow file to use for diagnostic and troubleshooting purposes. You canalso print a complete file, or highlighted sections.Microsoft TAPI browser applicationThe Microsoft TAPI browser appplication enables you to verify that SymposiumTAPI SP is installed and configured properly and is operating correctly.Symposium TAPI SP feature interactionsUsers of TAPI-compliant applications must be aware of feature interactions withSymposium TAPI SP.Feature interactions in a call center environmentWhen running TAPI-compliant applications with Symposium TAPI SP usingMeridian Link Services on the SCCS, the following features are not available:• not-ready with optional disconnect. An application invokes the not-readystatus for a set without disconnecting the call• enhanced time stamp IE. This feature is used in status change• set feature notification messages for:
