Hi, I am running the latest FreePBX (17.0.19.24) with the latest Scribe module (17.0.2.34) on Debian ( 12.10.0) and transcriptions didn’t work for a long call (38min). The recording’s wav file is 70M large. I don’t find any error messages anywhere and there aren’t any recordings pending in the report page.
When the same extension/user does a shorter call (about a minute long) everything works as expected.
Where did you check for error messages ? Reports → System Logfiles ? Covered a bit of that during Sangoma’s first Scribe webinar a few months ago, starting around the 28:20 mark:
Oh never mind, the scribe_out.log file has this error message matching the call time:
31 2025-04-01 13:39 -07:00: PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away in file /var/www/html/admin/modules/userman/functions.inc/auth/Auth.php on line 327
32 2025-04-01 13:39 -07:00: Stack trace:
33 2025-04-01 13:39 -07:00: 1. PDOException->() /var/www/html/admin/modules/userman/functions.inc/auth/Auth.php:327
34 2025-04-01 13:39 -07:00: 2. PDOStatement->execute() /var/www/html/admin/modules/userman/functions.inc/auth/Auth.php:327
35 2025-04-01 13:39 -07:00: 3. FreePBX\modules\Userman\Auth\Auth->getUserByDefaultExtension() /var/www/html/admin/modules/userman/Userman.class.php:1510
36 2025-04-01 13:39 -07:00: 4. FreePBX\modules\Userman->getUserByDefaultExtension() /var/www/html/admin/modules/scribe/Scribe.class.php:2444
37 2025-04-01 13:39 -07:00: 5. FreePBX\modules\Scribe->validateUserCall() /var/www/html/admin/modules/scribe/Scribe.class.php:1603
38 2025-04-01 13:39 -07:00: 6. FreePBX\modules\Scribe->callrecordingTranscript() /var/www/html/admin/modules/scribe/functions.inc/scribe_monitor_event_lister.php:49
39 2025-04-01 13:39 -07:00: 7. MixMonitorStop() /var/www/html/admin/modules/scribe/functions.inc/scribe_monitor_event_lister.php:7
40 2025-04-01 13:39 -07:00: 8. {closure}() /var/www/html/admin/libraries/php-asmanager.php:1615
41 2025-04-01 13:39 -07:00: 9. AGI_AsteriskManager->process_event() /var/www/html/admin/libraries/php-asmanager.php:349
42 2025-04-01 13:39 -07:00: 10. AGI_AsteriskManager->wait_response() /var/www/html/admin/modules/scribe/functions.inc/scribe_monitor_event_lister.php:16
43 2025-04-01 13:39 -07:00: 11. unknown() /var/www/html/admin/modules/scribe/scribe_monitor_event_lister.php:14
44 2025-04-01 13:39 -07:00: Monitor Event listener
Something odd is that later that same day, the user had a 36 minutes call that had a transcription done as expected. Only 2 minutes shorter and a couple megabytes lighter.
The server has 8GB of ram and according to my monitoring, the ram usage didn’t increase during and after that call, the server never swapped, the cpu usage doesn’t show much increase.
Is there a place where I can see mariadb logs? Are there specific settings for mariadb? I have not tweaked or touched any mariadb config.
Was this failed Scribe call the first call of the day and/or the first call into the system after an extended period of inactivity ?
Are there CDRs for these calls ?
The first called that failed wasn’t the first call of the day and 2 more calls failed scribe after the one that did work. Same error message.
There are CDR, how should I share them? I would prefer keeping the numbers private.
Agreed!
You might try manually changing the numbers (but keeping the same length and any interesting formatting like E.164) or pasting a solid color over screenshots of them with the GIMP (suboptimal). Probably text copy/pasta is best – you can use our pastebin as well.
Also, as this is a commercial module, and this is starting to sound like a bug, you can open a support ticket for further assistance - please DM me the ticket number to help follow it along.
Here’s an attempt in copy pasting a failed scribe transcription:
Time Event CNAM CNUM ANI DID AMA exten context App channel UserDefType EventExtra CEL Table
Wed, 2 Apr 2025 15:31 CHAN_START John Do 120 DEFAULT 2999999999 from-internal PJSIP/120-00000d38
Wed, 2 Apr 2025 15:31 APP_START John Do 120 120 2999999999 DEFAULT recordcheck sub-record-check MixMonitor PJSIP/120-00000d38
Wed, 2 Apr 2025 15:31 APP_END John Do 120 120 2999999999 DEFAULT recordcheck sub-record-check MixMonitor PJSIP/120-00000d38
Wed, 2 Apr 2025 15:31 CHAN_START DEFAULT s from-trunk PJSIP/SIPTRUNKPROVIDER_pjsip-00000d39
Wed, 2 Apr 2025 15:31 ANSWER CID:6888888888 2999999999 DEFAULT 2999999999 from-trunk AppDial PJSIP/SIPTRUNKPROVIDER_pjsip-00000d39
Wed, 2 Apr 2025 15:31 ANSWER CompanyName 6888888888 120 2999999999 DEFAULT 2999999999 trunk-dial-with-exten Dial PJSIP/120-00000d38
Wed, 2 Apr 2025 15:31 BRIDGE_ENTER CID:6888888888 2999999999 DEFAULT from-trunk AppDial PJSIP/SIPTRUNKPROVIDER_pjsip-00000d39
Wed, 2 Apr 2025 15:31 BRIDGE_ENTER CompanyName 6888888888 120 2999999999 DEFAULT 2999999999 trunk-dial-with-exten Dial PJSIP/120-00000d38
Wed, 2 Apr 2025 15:49 BRIDGE_EXIT CompanyName 6888888888 120 2999999999 DEFAULT 2999999999 trunk-dial-with-exten Dial PJSIP/120-00000d38
Wed, 2 Apr 2025 15:49 BRIDGE_EXIT CID:6888888888 2999999999 DEFAULT from-trunk AppDial PJSIP/SIPTRUNKPROVIDER_pjsip-00000d39
Wed, 2 Apr 2025 15:49 HANGUP CompanyName 6888888888 120 2999999999 DEFAULT 2999999999 trunk-dial-with-exten PJSIP/120-00000d38
Wed, 2 Apr 2025 15:49 CHAN_END CompanyName 6888888888 120 2999999999 DEFAULT 2999999999 trunk-dial-with-exten PJSIP/120-00000d38
Wed, 2 Apr 2025 15:49 HANGUP CID:6888888888 2999999999 DEFAULT from-trunk AppDial PJSIP/SIPTRUNKPROVIDER_pjsip-00000d39
Wed, 2 Apr 2025 15:49 CHAN_END CID:6888888888 2999999999 DEFAULT from-trunk AppDial PJSIP/SIPTRUNKPROVIDER_pjsip-00000d39
Wed, 2 Apr 2025 15:49 LINKEDID_END CID:6888888888 2999999999 DEFAULT from-trunk AppDial PJSIP/SIPTRUNKPROVIDER_pjsip-00000d39
here’s a successful one:
Time Event CNAM CNUM ANI DID AMA exten context App channel UserDefType EventExtra CEL Table
Tue, 1 Apr 2025 15:30 CHAN_START John Do 120 DEFAULT 2999999999 from-internal PJSIP/120-00000c8f
Tue, 1 Apr 2025 15:30 APP_START John Do 120 120 2999999999 DEFAULT recordcheck sub-record-check MixMonitor PJSIP/120-00000c8f
Tue, 1 Apr 2025 15:30 APP_END John Do 120 120 2999999999 DEFAULT recordcheck sub-record-check MixMonitor PJSIP/120-00000c8f
Tue, 1 Apr 2025 15:30 CHAN_START DEFAULT s from-trunk PJSIP/SIPTRUNKPROVIDER_pjsip-00000c90
Tue, 1 Apr 2025 15:30 ANSWER CID:6888888888 2999999999 DEFAULT 2999999999 from-trunk AppDial PJSIP/SIPTRUNKPROVIDER_pjsip-00000c90
Tue, 1 Apr 2025 15:30 ANSWER CompanyName 6888888888 120 2999999999 DEFAULT 2999999999 trunk-dial-with-exten Dial PJSIP/120-00000c8f
Tue, 1 Apr 2025 15:30 BRIDGE_ENTER CID:6888888888 2999999999 DEFAULT from-trunk AppDial PJSIP/SIPTRUNKPROVIDER_pjsip-00000c90
Tue, 1 Apr 2025 15:30 BRIDGE_ENTER CompanyName 6888888888 120 2999999999 DEFAULT 2999999999 trunk-dial-with-exten Dial PJSIP/120-00000c8f
Tue, 1 Apr 2025 16:07 BRIDGE_EXIT CID:6888888888 2999999999 DEFAULT from-trunk AppDial PJSIP/SIPTRUNKPROVIDER_pjsip-00000c90
Tue, 1 Apr 2025 16:07 BRIDGE_EXIT CompanyName 6888888888 120 2999999999 DEFAULT 2999999999 trunk-dial-with-exten Dial PJSIP/120-00000c8f
Tue, 1 Apr 2025 16:07 HANGUP CID:6888888888 2999999999 DEFAULT from-trunk AppDial PJSIP/SIPTRUNKPROVIDER_pjsip-00000c90
Tue, 1 Apr 2025 16:07 CHAN_END CID:6888888888 2999999999 DEFAULT from-trunk AppDial PJSIP/SIPTRUNKPROVIDER_pjsip-00000c90
Tue, 1 Apr 2025 16:07 HANGUP CompanyName 6888888888 120 2999999999 DEFAULT 2999999999 trunk-dial-with-exten PJSIP/120-00000c8f
Tue, 1 Apr 2025 16:07 CHAN_END CompanyName 6888888888 120 2999999999 DEFAULT 2999999999 trunk-dial-with-exten PJSIP/120-00000c8f
Tue, 1 Apr 2025 16:07 LINKEDID_END CompanyName 6888888888 120 2999999999 DEFAULT 2999999999 trunk-dial-with-exten PJSIP/120-00000c8f
I will create a ticket tomorrow!