CVP 8.5(1) - Post Call Survey in SIP http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&threadId=6228196 2013-05-24T05:02:40Z 2013-05-24T05:02:40Z KENT ROBERTS http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=6295688 2012-08-16T19:24:04Z 2012-08-16T19:24:04Z

Haven't worked on the SIP side of this yet, but the issues I have run into are durning the cvp restart the only tag or piece of data that remains constant is the media.id that comes from the gateway. What I have done since our users requried tracking the agent as well, was to write to a database table the media.id, RouterCallKey and RouterCallKeyDay and the DNIS or in your case the langauge preference. If this SQL write failed I didn't tell the user the survey was available, if it completed then I played that wonderful survey message is available after a call.... When the call restarts, I read the database using the media.id and that returned the DNIS or in your case here the langauge information I needed to know which survey to play. I wrote this to support a different survey per DNIS. I have tried using the peripheral vars, and other information but it seems that ICM/UCCE was not always able to have the data written to a table, or available 100% of the time as fast as I needed it to make a routing decision, so I started using the database so I would always have that information when I needed it.

KENT ROBERTS 2012-08-16T19:24:04Z Koen Van Impe http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=6228195 2012-08-03T13:48:41Z 2012-08-03T13:48:41Z

Hi!   We are setting up a comprehensive deployment with ICM 8.5 and CVP 8.5(1). Our client wants to use the CVP post call survey (PCS) feature.   According to SRND, PCS should retrieve the call context from the original call. That feature is very useful in our case to retrieve the language selection made at the very beginning of the call. That info is saved in an ECC var user.Language. Alas, it doesn't seem to work as expected.   Digging some more on the subject, I learned that there's a know bug in the version we are running (CVP 8.5(1)): [url=http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtk13452]CSCtk13452[/url] The very simple workaround involves setting ICM.icmPCSUseCachedCallContext to true in the appropriate properties file. After this step, still not working as expected. I noticed Peripheral Vars are copied to the PCS call, but not the custom created ECC Vars.   I could off course copy the required information into Peripheral Vars, but that has an impact on already developed apps (using Periph Vars in different places). The bug report mentions it being solved in version 8.5(2), but that is not available in the Cisco download site.   I'm out of ideas right now. Has any one else used the PCS feature with call context data? Maybe some tweak I missed?   Any help / suggestion is welcome!   K  

Koen Van Impe 2012-08-03T13:48:41Z