Migrating from IDVoice to IDVoice CC

Since IDVoice 3.4.0 release all telephone-channel capabilities (voice verification, age and gender estimation, diarization and identification) are distributed within a different product called IDVoice Call Center (CC). Because of this change all customers currently using IDVoice product for telephone channel audio processing are recommended to migrate to IDVoice CC distribution. This paragraph covers the aspects of such migration including SDK and Docker distributions and describes the differences between the IDVoice and IDVoice CC products.

IDVoice CC SDK¶

IDVoice CC SDK is a core of IDVoice CC product. Below is the list of topics to consider while migrating from IDVoice SDK to IDVoice CC SDK:

1. The main IDVoice CC SDK binary is libCallCenterSdk.so for Linux and CallCenterSdk.dll for Windows, so binary name is different.
2. Both SDKs contain verify, media and core components providing the same API. C, C++ and Java APIs for these components are exactly the same (header files are the same), so no code changes are required for them.
3. C++ API for attributes and diarization components is almost the same for IDVoice SDK and IDVoice CC: IDVoice CC SDK API has slightly different namings (all method names are starting with capital letter, struct fields are written in underscore) and each component API is now stored in its own sub-namespace (e.g. voicesdk::attr:: instead of voicesdk:: which was used previously).
4. Python API is exactly the same for both SDKs except the main module name: voicesdk for IDVoice SDK and voicesdk_cc for VIDVoice CC SDK.
5. Java API is exactly the same for both SDKs.

IDVoice CC Server¶

IDVoice CC Server which is shipped as Docker image has exactly the same API and configuration process as IDVoice Server.