Article ID:	211
Last updated:	November 02, 2006

Would you like to...

Print this page

Post a comment

User Opinions

No users have voted.

---

How would you rate this answer?

Helpful

Not helpful

Thank you for rating this answer.

SUMMARY

This article explains the relationship between Audium Call Services and the application server, and how this setup allows Audium Call Services to be accessible via HTTP, HTTPS and/or SSL.

SYMPTOMS

Administrator or developer is configuring Audium Call Services, and would like to know if it can be setup to be accessed via HTTP, HTTPS and/or SSL.

RESOLUTION

Since Audium Call Services runs on top of an application server (e.g. Tomcat, or WebSphere), it benefits from the features that are provided by the application server.  The application server handles all incoming and outgoing communications in regards to Audium Call Services, and so it also manages which protocols may be used. 

The most common protocol used by voice browsers to access Audium Call Services is HTTP, and in most situations this is adequately secure; voice browsers and application servers used for IVR applications are generally not externally visible (i.e. on the internet), and so a secure protocol is not required.

However, the application server could be configured to only allow HTTPS and/or SSL access to Audium Call Services if the application server supports these protocols.  Protocol changes are transparent to Audium Call Services.  Please note that your voice browser may have restrictions on which protocols are available, please consult your voice browser's documentation for details.