06-27-2011 02:30 PM - edited 03-14-2019 08:08 AM
Howdy Netpros, I can't find anything in the documentation for UCCX 7 on encrypting call recordings. I assume this is not possible and we are looking into a seperate call recording solution that supports encryption, but does anyone have any ideas about what I can do now to encrypt the call recording files besides exporting them to .wav and making them inaccessible to the Supervisor application?
Thanks!
Brett
Solved! Go to Solution.
07-02-2011 01:49 PM
Brett,
UCCX doesn't natively support encrypted calls using SRTP. In fact, it's a requirement to turn it off. However if all you are worried about is encrypting the recordings, I would do the following:
1.) Create a secure server that has adequate storage.
2.) Create a script that copies over the .raw files every X (minutes,hours,days). Basically you just need to copy over as often as you feel the need exists.
3.) Use the built in Windows signing functionality to sign and encrypt the files.
You now have encrypted recordings, the downside of which is you don't have a player for them. To rectify this, you will need to allow a copy of the raw2wav to run on that server and use usernames that have the security token to unencrypt the data. You could then also give that token to your call center supervisors and allow them to listen to the recordings using the token and then delete.
It's not a perfect solution, but it may work. Let me know if you have any questions about this. You Windows team should be able to provide you details on the signing tokens as they have been a part of Active Directory and Windows for a couple of generations now. Hopefully this will give you somewhere to start.
Regards,
Robert W. Rogier
07-02-2011 01:49 PM
Brett,
UCCX doesn't natively support encrypted calls using SRTP. In fact, it's a requirement to turn it off. However if all you are worried about is encrypting the recordings, I would do the following:
1.) Create a secure server that has adequate storage.
2.) Create a script that copies over the .raw files every X (minutes,hours,days). Basically you just need to copy over as often as you feel the need exists.
3.) Use the built in Windows signing functionality to sign and encrypt the files.
You now have encrypted recordings, the downside of which is you don't have a player for them. To rectify this, you will need to allow a copy of the raw2wav to run on that server and use usernames that have the security token to unencrypt the data. You could then also give that token to your call center supervisors and allow them to listen to the recordings using the token and then delete.
It's not a perfect solution, but it may work. Let me know if you have any questions about this. You Windows team should be able to provide you details on the signing tokens as they have been a part of Active Directory and Windows for a couple of generations now. Hopefully this will give you somewhere to start.
Regards,
Robert W. Rogier
07-05-2011 07:20 AM
Thanks for your reply Robert. I figured that was the case.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide