| Running Call Services |
| Categories: User Guide Ch3: Administration |
| Article ID: | 169 |
| Last updated: | January 12, 2007 |
| User Opinions |
|
No users have voted.
|
|
Thank you for rating this answer.
|
SUMMARY
This article details what happens when Audium Call Services is started, as well as explains conditions that cause it to start and stop.
SYMPTOMS
N/A
RESOLUTION
Call Services starts up automatically when the Java application server it is installed on is started. Assuming the AUDIUM_HOME environment variable is set and the license files are valid, Call Services will first display all of the Gateway Adapters installed, followed by loading all the voice applications deployed on it. As each application is loaded, Call Services will report it in the application server console window (which will not be seen if the window was started in the background or a service, or when using some application servers that pipe this content to a log file). If any application encounters problems with its XML files or missing Java classes, a brief message will be displayed in the console window and the full description is placed in the error log. The loading of just that particular voice application will be aborted, correctly configured applications will load normally. Once all applications are loaded Call Services is ready to start handling calls.
Shutting down the application server will stop all calls on the system at the time. If the voice browser requests a document while the application server is down, it will be unable to reach Call Services prompting the voice browser to play an error message to the caller. It is important, especially for production systems, to prevent accidental or intentional shutdowns of the application server.
|
| Visitor Comments |
|
No visitor comments posted. Post a comment
|
| Related Questions |
|
No related questions were found.
|
| Attachments |
|
No attachments were found.
|
Search the Knowledgebase
Jump to ID
Browse by Category
Print this page
Post a comment