- Joined
- Jun 29, 2016
- Messages
- 53
- Reaction score
- 26
In 3CX V20 Update 9, a failed call transcription can leave historical recordings without any supported way to retry or reprocess them from the PBX.
We encountered this after a transcription issue involving Unicode characters in extension/contact names. After correcting the source identities, new calls could be transcribed again, but previously failed recordings remained without transcription.
3CX Support confirmed that recovering them would require manual changes to recording files and database records, which is unsupported.
Requested improvement:
1. Identify recordings whose transcription failed.
2. Requeue or retry transcription for selected recordings.
3. Safely reset inconsistent failed/processed states.
4. Bulk-reprocess historical recordings after the original issue is corrected.
5. Show the reprocessing result or permanent failure reason.
This would prevent permanent gaps in historical transcripts and avoid unsupported database manipulation.
We encountered this after a transcription issue involving Unicode characters in extension/contact names. After correcting the source identities, new calls could be transcribed again, but previously failed recordings remained without transcription.
3CX Support confirmed that recovering them would require manual changes to recording files and database records, which is unsupported.
Requested improvement:
1. Identify recordings whose transcription failed.
2. Requeue or retry transcription for selected recordings.
3. Safely reset inconsistent failed/processed states.
4. Bulk-reprocess historical recordings after the original issue is corrected.
5. Show the reprocessing result or permanent failure reason.
This would prevent permanent gaps in historical transcripts and avoid unsupported database manipulation.
Upvote
0
