...
Following are the limitations of the solution
Summary | Description | |
| Direct Transfer scenario | In cases of Direct Transfer call, if the call is not picked up by the transferred agent within the configured time then, in this case, two separate recordings are made instead of one single combined, with two legsConference and consult transfer calls | Conference and consult transfer calls are not properly recorded. |
| Currently, the solution is handling the single codec | The Voice recording solution is not supporting multiple codexescodecs. It is only handling the G711 codec. | |
| KeyCloak | For now, the Keycloak does not sync agents or supervisors from finesse. So, the admin needs to create all users manually on the KeyCloak. The Username and Password of the users should be the same as in the CUCM. | |
| KeyCloak | A user cannot log in on VRS Gadget if he has no role assigned in KeyCloak | |
| KeyCloak | If an admin role is assigned to a User he will see all recordings | |
| KeyCloak | If an agent role is assigned to the user he will see only his own recordings | |
| Finesse Gadget | In the finesse gadget, only those users will be logged in who are created in the KeyCloak. | |
| Finesse Gadget | If you manually log out a user then it will not auto-login. | |
| Finesse Gadget | In case of hold resume call user will see the multi-legged calls | |
| Finesse Gadget | User will not see the multi-legged recordings in the case of Direct Transfer, Consult Transfer, and the conference call. He will only see his leg, related to his agent id. It will be shown as a single recording. |
Other Limitations
| Jira Legacy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|