Amfat,   Have you reviewed the Finesse Devnet yet? This is all point of the Finesse Rest APIs.   The options are 1) Use Standard Finesse Browser Client and create your own custom open social gadgets where you can do whatever you want and the gadget is "contained" within standard Finesse - use Finesse JavaScript Library   2) Create your own Agent Desktop using Finesse REST APIs - which is what you seem to want - i.e. use Finesse REST API and the real-time updates are received via XMPP.   https://developer.cisco.com/site/finesse/   Gerry ... View more

thanks for letting us know Bill. Nicely explained and good to know.   Gerry ... View more

Tobias,   >  is it possible to change IP address in Finesse 12.0.1? If yes where can I find a description for that? "You cannot change the IP address of a Finesse server after it is installed."   https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/finesse/finesse_1201/Admin/guide/cfin_b_1201-administration-guide-release-1201/cfin_b_1201-administration-guide-release-1201_chapter_01.html   Regards, Gerry ... View more

Hi Bill,   Could you try using Wireshark on the CVP Server instead and use "sip" filter and attached the results for a working and not working call?   Then save export the capture with just the SIP trace and attach to the post? It might make it easier to spot whats is different and what the issue might be.   Regards, Gerry ... View more

The default audio path should contain a full URL (i.e. include the servername).   The above example meant that the audio would be located on the VXML Tomcat server, which is not recommended / supported for production apps. Audio files should be located on the IIS server. Make sure the set caching expiry on the IIS server to 5-15 mins - so when you update a audio , the VXML browser will check for a new file relatively quickly. Note - even when cache has expired it only checks for a new file, if file has notr changed it still uses the one in cache - so its very efficient.   So the URL for the default prompts should be something like:   http://cvp-server.mydomain.com/en-us/app/sample/   The audio files can then be co hosted on the IIS web server located on the CVP Call Server. You can change the default audio path in a call studio app itself - using the application modifier element - so that you could select the specific Call Server the call was on (for better resilience).   Make sure that the VXML Browser (Virtual Voice Browser) or the VXML Gateway can resolve the hostname configured. As it is this device which is rendering the VXML and downloading & caching the audio file.   You can use debugging on the VXML Gateway / VVB Server to help you determine why it cannot download the audio. You can also review and look at the IIS logs files for 404 errors etc.   Regards, Gerry   ... View more

Boyd, That auth popup was a bug and should not occur if the server has been updated. i.e. it send the post to the backend server without the end user having to do anything. That is an old post and not accurate. However if your backend server requires authentication - this might be an issue and that would likely require a custom gadget. Gerry ... View more