The weirdest thing...
I did a call studio project a few month ago and I wrote some needed custom elements, everything worked fine at the time.
Now, I'm doing another call studio project and I'm trying to write a couple of custom elements and I can't seem to get them to work.
No matter what I do I always get the same java exception according to element type:
- Element is not a valid decision element class.
- Element is not a valid action element class.
- Element is not a valid voice element class.
I tried using my old custom elements from the last project and none of them seems to work anymore.
I even tried starting from scratch, I've used the custom elements templates from the Cisco forums and got the same result.
The outcome is the same in both debug and runtime.
The only difference from the project I did a few month ago and a project I'm doing now is that my endpoint has since been replaced and I've reinstalled Call Studio and transferred my license.
I've tried writing my java files with Call Studio and with Eclipse.
I'm saving my files as jar files and placing them in the plugins lib directories 'debug.core' and 'elements.core'/library.common' (tried both separately and combined).
I really have no idea what i'm doing wrong and I'm loosing sleep over it for about a week now...
Please help me...
Often when you see the error message that '... is not a valid
...class' it means that the system can't find the code for the java
class being called.
The java class must either be
a) in the Studio app within the appname/java/deploy/application/classes
(or lib) folder
b)on VXMLServer under C:\cisco\cvp\VXMLServer\common\classes (or lib)
and then you have to restart VXMLServer.
Thank you for your reply.
If I'm not mistaken those are the destinations for uploading my lib for runtine use,
For debug use on my endpoint's Call Studio, I was sure I need to place my lib at the 'debug.core' directory in eclipse's plugins, is that correct?
For use with the Debugger, the lib (jar file) must go into
For VXMLServer, the lib (jar) goes into
C:\Cisco\CVP\VxmlServer\common\lib (and a restart of vxml server is
Thank you very much!
It works. :-)
Please sign in to leave a comment.