Genesys Cloud - Main

Hi all

This (or very similar) has likely been asked before but darned if I can find it.

Some of our architect flows have a transfer to external number option and we also manually transfer calls to external numbers.

We have found that recording has continued on these calls, even after the call is transferred and has only external parties involved. This bit of the issue has been resolved.

But what to do with the thousands of recordings that have already happened?

Is there a way that I can create a recording bulk job to delete these recordings, based on the numbers these calls were transferred to?

Or is a GDPR job the best route to take? Apart from the recordings and transcripts, what else do these GDPR jobs delete?

Thanks in advance,

Tim

Hey Tim, 

I've had this kind of scenario a few times, what you will need to do is POST a recording job (/api/v2/recording/jobs) with a payload like below - please check it/test etc but from your explanation would be something like that. The action date needs to be in the future (can be a few mins) and the dnis value needs to be the target number etc, or whatever way you want to narrow your search. 

You will then get a response with a job ID which you need to put into a PUT (/api/v2/recording/jobs/JOBIDHERE) and the payload needs to be {"state": "PROCESSING"} This will then start the job (after it's ready) and away you go

{  "action": "DELETE",  "actionDate": "2023-09-27T14:00:00.000Z",  "includeRecordingsWithSensitiveData": true,  "includeScreenRecordings": true,  "clearExport": false,  "conversationQuery": {    "segmentFilters": [      {        "type": "and",        "predicates": [          {            "type": "dimension",            "dimension": "dnis",            "operator": "matches",            "value": "+61299999999"          }        ]      }    ],    "interval": "2023-09-26T14:00:00.000Z/2023-09-27T14:00:00.000Z"  }}

Hi all

This (or very similar) has likely been asked before but darned if I can find it.

Some of our architect flows have a transfer to external number option and we also manually transfer calls to external numbers.

We have found that recording has continued on these calls, even after the call is transferred and has only external parties involved. This bit of the issue has been resolved.

But what to do with the thousands of recordings that have already happened?

Is there a way that I can create a recording bulk job to delete these recordings, based on the numbers these calls were transferred to?

Or is a GDPR job the best route to take? Apart from the recordings and transcripts, what else do these GDPR jobs delete?

Thanks in advance,

Tim

Thanks for the rapid response Lawrence, it's much appreciated.

I was looking at that method but the docs didn't list "dnis" as a valid dimension:

(string) Left hand side for dimension predicates.Valid values: conversationEnd, conversationId, conversationInitiator, conversationStart, customerParticipation, divisionId, externalTag, mediaStatsMinConversationMos, originatingDirection.

I will give it a shot and let you know how it goes.

Hey Tim, 

I've had this kind of scenario a few times, what you will need to do is POST a recording job (/api/v2/recording/jobs) with a payload like below - please check it/test etc but from your explanation would be something like that. The action date needs to be in the future (can be a few mins) and the dnis value needs to be the target number etc, or whatever way you want to narrow your search. 

You will then get a response with a job ID which you need to put into a PUT (/api/v2/recording/jobs/JOBIDHERE) and the payload needs to be {"state": "PROCESSING"} This will then start the job (after it's ready) and away you go

{  "action": "DELETE",  "actionDate": "2023-09-27T14:00:00.000Z",  "includeRecordingsWithSensitiveData": true,  "includeScreenRecordings": true,  "clearExport": false,  "conversationQuery": {    "segmentFilters": [      {        "type": "and",        "predicates": [          {            "type": "dimension",            "dimension": "dnis",            "operator": "matches",            "value": "+61299999999"          }        ]      }    ],    "interval": "2023-09-26T14:00:00.000Z/2023-09-27T14:00:00.000Z"  }}

Hi all

This (or very similar) has likely been asked before but darned if I can find it.

Some of our architect flows have a transfer to external number option and we also manually transfer calls to external numbers.

We have found that recording has continued on these calls, even after the call is transferred and has only external parties involved. This bit of the issue has been resolved.

But what to do with the thousands of recordings that have already happened?

Is there a way that I can create a recording bulk job to delete these recordings, based on the numbers these calls were transferred to?

Or is a GDPR job the best route to take? Apart from the recordings and transcripts, what else do these GDPR jobs delete?

Thanks in advance,

Tim

Anytime Tim :)

Just checking you are using the segments filter and not the conversation filter - those attributes sound like the conversationFilters

Thanks for the rapid response Lawrence, it's much appreciated.

I was looking at that method but the docs didn't list "dnis" as a valid dimension:

(string) Left hand side for dimension predicates.Valid values: conversationEnd, conversationId, conversationInitiator, conversationStart, customerParticipation, divisionId, externalTag, mediaStatsMinConversationMos, originatingDirection.

I will give it a shot and let you know how it goes.

Hey Tim, 

I've had this kind of scenario a few times, what you will need to do is POST a recording job (/api/v2/recording/jobs) with a payload like below - please check it/test etc but from your explanation would be something like that. The action date needs to be in the future (can be a few mins) and the dnis value needs to be the target number etc, or whatever way you want to narrow your search. 

You will then get a response with a job ID which you need to put into a PUT (/api/v2/recording/jobs/JOBIDHERE) and the payload needs to be {"state": "PROCESSING"} This will then start the job (after it's ready) and away you go

{  "action": "DELETE",  "actionDate": "2023-09-27T14:00:00.000Z",  "includeRecordingsWithSensitiveData": true,  "includeScreenRecordings": true,  "clearExport": false,  "conversationQuery": {    "segmentFilters": [      {        "type": "and",        "predicates": [          {            "type": "dimension",            "dimension": "dnis",            "operator": "matches",            "value": "+61299999999"          }        ]      }    ],    "interval": "2023-09-26T14:00:00.000Z/2023-09-27T14:00:00.000Z"  }}

Hi all

This (or very similar) has likely been asked before but darned if I can find it.

Some of our architect flows have a transfer to external number option and we also manually transfer calls to external numbers.

We have found that recording has continued on these calls, even after the call is transferred and has only external parties involved. This bit of the issue has been resolved.

But what to do with the thousands of recordings that have already happened?

Is there a way that I can create a recording bulk job to delete these recordings, based on the numbers these calls were transferred to?

Or is a GDPR job the best route to take? Apart from the recordings and transcripts, what else do these GDPR jobs delete?

Thanks in advance,

Tim