My newly created voice application does not load

Make sure that Call Services starts up properly and that there are no errors during startup.

The following article helps to debug issues related to Call Services startup:

• How to debug issues with Call Services not starting

There are several potential issues that can prevent voice applications from loading. The most common problem is when a voice application is deployed from Studio but its "deployApp" administrative script is not run on Call Services.  In that case, the application's data files are present on Call Services, but it is not yet actively accepting callers.

Another common problem is incorrect general settings for the application. "Deploy version" and "Gateway adapter" should have appropriate values for the particular environment.  

Prior to calling into the application, status of the application should be checked using the administrative script status.bat or status.sh, depending on the OS used. This local status script will output status for this particular application, while the global static script (in AUDIUM_HOME/admin) will list all the applications currently deployed on the Call Services instance.

Please refer to the following articles for full descriptions of the above problems and proposed solutions:

• How to deploy an Audium application from Audium Studio to Audium Call Services
• Error regarding a gateway adapter while attempting to deploy an Audium application
• Error regarding an incorrect Call Services version while attempting to deploy an Audium application
• Administrative Functions

The following articles might be also helpful:

• How to update applications that are in production with active callers
• What command-line options are available for the administrative scripts?
• How to test deployed Audium applications in a web browser