We are planning to upgrade our contact center solution from IPCC 6.0 to 7.2 and CVP from 3.1 to 4.x via technology refresh. We are in early stages and still researching and evaluating our options. Lab testing will start in the next couple of weeks. One of the main reasons to upgrade is security requirements. CVP 4.x has built in SSH and HTTPS capabilities, so we have been asked to move to 4.x. Our Cisco rep has also told us that multiple CVP Combo boxes can be consolidated in less CVp callservers (cost advantage)?
I would like to know if anyone upgraded CVP from 3.1 to 4.x? Any issues converting the scripts from 3.1 to 4.x? What major advantages you experiences after the upgrade? Did you loose any functionality?
We had to create a lot of custom elements because of limitations in CVP 3.x . Anyone with this scenario? how did you handle the conversion of custom elements in cvp 4.x?
You should be able to import the 3.1 CVP Studio app into CVP 4.0 and not have problems. The issues I've heard of are:
1.The subdialog start and return elements are no longer voice elements, so they no longer have a General, Audio, or Data tab. So anything you might've had in those tabs of the element's config will be gone.
2.You may have to delete the .settings file before importing into Studio. Since the .settings file is pretty different now, there may be issues here. I've not experienced issues, but have heard that others have.
3. The Subdialog Return element can't be used as an "Error" element anymore, so if you had that in your 3.1 app, you'll have to use an Audio element as your Error element now.
4.In the latest version of CVP 4.0 if you have any custom elements that create session data that isn't an integer or a string, then you break the ability to log detail information to the "CVP Reporting Database".
5. If using Tomcat, the port number has changed from 8080 to 7000 and it starts up by default at boot time as the 'Cisco VXML Server Service' (or something like that)
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...