on 01-24-2014 04:13 PM
Some strange reason customer doesn't want to install IIS on any server. They are more interested to go with Tomcat server which is already installed for VXML server.
I am trying to use Tomcast as Media server. I have find the followong link regarding Tomcat cache control.
http://developer.cisco.com/documents/10501/2125796/Cache+Control+Tomcat.pdf
This document is asking to create a java class and when I tried to do that I am geting error messages. As I am not good with Java, anyone here will be able to help me by uploading this Java class or tell me where this java code is wrong?.
I am trying to use Tomcast as Media server. I have find the followong link regarding Tomcat cache control.
http://developer.cisco.com/documents/10501/2125796/Cache+Control+Tomcat.pdf
This document is asking to create a java class and when I tried to do that I am geting error messages. As I am not good with Java, anyone here will be able to help me by uploading this Java class or tell me where this java code is wrong?.
Yes, Tomcat is good and you can use the method described. However per my understanding and the recommendations I got from Cisco, Tomcat is not really recommended for prod environments for hosting prompts. It does not mean that it won’t work. Depending on your architecture, setup etc you could get away with using Tomcat and have no issues .
You can always use audio maxage wherever you want to locally change the settings and need audio to be fetched sooner etc. In my lab, I use Tomcat and in prod IIS.
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, September 11, 2012 1:21 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Bill Webb in Customer Voice Portal (CVP) - CVP - All Versions: RE: CVP VoiceXML Tomcat instance as a media server
Bill Webb has created a new message in the forum "CVP - All Versions":
--------------------------------------------------------------
News flash on this thread - Cisco actually added their own Cache Control Class to CVP starting somewhere in CVP 8.6. There's a commented out example in the web.xml!
I am strongly in favor of using Tomcat for the Media Server for exactly the same reason as this customer - why would you want to install IIS (which is not a required component on the CVP Call/VXML Server) just to serve up .wav files?
I'll concede that the IIS Management GUI is a little easier to use than modifying the web.xml file, but there is little you cannot do in terms of setting content expiration differently for different directories, file names - just about anything.
- Bill
--
To respond to this post, please click the following link:
<http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/6475090>
or simply reply to this email.
Ooh, goodie.
>>>If at some point in the future, CVP finally moves to the Cisco VOS, which I personally think it should, then IIS is out the window anyway
It will and it should. Perhaps they will have Apache on board.
>>>Is the recommendation then going to be for a separate Windows box running IIS?
I’m in the middle of upgrading a big site and am doing exactly that. Taking CVP off the two servers that are running IIS for the CVP farm and turning them into Media Stores only.
>>> separate Windows box running IIS?
One more point – not “box”. They would be Virtual Machines on an ESX hypervisor. It could easily be a Linux VM running Apache. Not wedded to the IIS idea but just anti-Tomcat. ;-)
>> So you don't have to send in a media URL (http://blahblah) to every application
Default Audio Path = http://blahblah/ and each audio item looks like “foo.wav”. Or use the App Modifiers and set a session variable so Audio Item looks like “{SessionVariable}/foo.wav” if you want different paths for the multiple languages your app has to handle. Many options – although I do like to keep those short.
>>>if you're using collocated Call Server/VXML Server
On big farms you may have more call servers than VXML servers. Big farms will probably have 2 dedicated Media Stores. That’s how it was originally with CVP 3.0
Ooh, goodie.
>>>If at some point in the future, CVP finally moves to the Cisco VOS, which I personally think it should, then IIS is out the window anyway
It will and it should. Perhaps they will have Apache on board.
>>>Is the recommendation then going to be for a separate Windows box running IIS?
I’m in the middle of upgrading a big site and am doing exactly that. Taking CVP off the two servers that are running IIS for the CVP farm and turning them into Media Stores only.
>>> separate Windows box running IIS?
One more point – not “box”. They would be Virtual Machines on an ESX hypervisor. It could easily be a Linux VM running Apache. Not wedded to the IIS idea but just anti-Tomcat. ;-)
>> So you don't have to send in a media URL (http://blahblah) to every application
Default Audio Path = http://blahblah/ and each audio item looks like “foo.wav”. Or use the App Modifiers and set a session variable so Audio Item looks like “{SessionVariable}/foo.wav” if you want different paths for the multiple languages your app has to handle. Many options – although I do like to keep those short.
>>>if you're using collocated Call Server/VXML Server
On big farms you may have more call servers than VXML servers. Big farms will probably have 2 dedicated Media Stores. That’s how it was originally with CVP 3.0
Ooh, goodie.
>>>If at some point in the future, CVP finally moves to the Cisco VOS, which I personally think it should, then IIS is out the window anyway
It will and it should. Perhaps they will have Apache on board.
>>>Is the recommendation then going to be for a separate Windows box running IIS?
I’m in the middle of upgrading a big site and am doing exactly that. Taking CVP off the two servers that are running IIS for the CVP farm and turning them into Media Stores only.
>>> separate Windows box running IIS?
One more point – not “box”. They would be Virtual Machines on an ESX hypervisor. It could easily be a Linux VM running Apache. Not wedded to the IIS idea but just anti-Tomcat. ;-)
>> So you don't have to send in a media URL (http://blahblah) to every application
Default Audio Path = http://blahblah/ and each audio item looks like “foo.wav”. Or use the App Modifiers and set a session variable so Audio Item looks like “{SessionVariable}/foo.wav” if you want different paths for the multiple languages your app has to handle. Many options – although I do like to keep those short.
>>>if you're using collocated Call Server/VXML Server
On big farms you may have more call servers than VXML servers. Big farms will probably have 2 dedicated Media Stores. That’s how it was originally with CVP 3.0
>>>>"In Unified CVP 9.0(1), the Call Server, VXML Server, and Media Server are combined as one installation. Installing the CVP Server will install all three components. In the earlier versions, Call Server, VXML Server, and Media Server could be installed on different machines."
That’s misleading. Cisco does not install a Media Server. It just drops some files somewhere.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: