Installed the Scribe module and paid for the 1000 minutes and setup a couple of users for transcription. The intention is to transcribe call recordings.
Now the service is going back in time and seems it is going back in time a transcribing recordings from the past. I dont know how far back it will go, and I’m afraid to enable more users.
In a couple of hours it has eaten up over 600 minutes of transcription.
Anyone know of a way to stop this, and only transcribe recordings moving forward?
Also, as a user issue or I guess maybe a feature request, there does not seem to be a way to download the transcription from the User Control Panel, have to log in to the system GUI, which really isn’t practical for all the different users on the system.
Commercial modules include bug fix support and this sounds like that may be the case. Are you able to open a ticket via help.sangoma.com ? Also what version of Scribe are you using ?
Please DM the ticket number. Curious if you had previously activated the trial Scribe license on your system ?
For more background, the Scribe module continues to see improvements. The histo-scribe functionality is fairly new and designed for users with previous call recordings to selectively process these into Scribe text format – by year, month or day. There was also recently the addition of arbitrary file upload in multiple different source audio formats, along with Text-To-Speech integration of the Scribe engine in to the System Recordings and subsequent saving of the text for quicker adjustments later on e.g. adding one new IVR menu option.
It would be really useful if the user could download their own transcriptions inside the UCP so thye wouldnt need to have access to or log in to the PBX Web GUI
Dealing with Scribe consuming excessive minutes and slowing down UCP downloads seems to highlight how sensitive call-recording setups are to storage, timing, and processing delays. I try to keep logs, transcription tasks, and recording retention tightly controlled, since any backlog can cascade into performance problems. A streamlined workflow with clear limits usually helps stabilize modules that rely on continuous background processing.
I ended up opening a ticket with Sangoma and someone logged into the system - I have no idea what they did, but now it does not go back and transcribe from the past, only new recordings (which is what I wanted).
I did not see anywhere that you could define whether you wanted to transcribe past recordings, or any other settings related to retention or logs.
Scribe Rewind is the public-facing name of the feature (histo-scribe was an earlier potential candidate.) From the Scribe Rewind documentation:
This new feature involves enhancing the user experience for accessing and managing historical transcription data, particularly for old recordings and voicemails. Through this option, user can transcript old recordings or voicemails with the Scribe license.
The feature is available to PBX systems with an active Scribe module license and works seamlessly with existing Scribe functionality.
You can view the Scribe Rewind transcriptions in UCP – same as before – but not initiate them. Maybe a request feature ? So admins can manage how many minutes are used (instead of leaving it up to the users to burn through all your usage credits ?
