For some reason Sangoma desktop app users stopped receiving text messages. The same users continue to receive messages in the Sangoma mobile app. This was not preceeded by any changes to the deployment. All modules are the latest from stable. Reboot did not fix. I ran the domain action and CloudConnect Agent action in the Sangoma Talk module but no change.
Hi @chrisduncansb
There is no such known issue with Sangoma Desktop App,
can you provide more details about the issue, such as FreePBX version v16 or v17?
also let me know the Sangoma Desktop App version, sangomartapi and SMS module versions installed in the system, along with the following log file for testing sms:
/var/log/asterisk/sangomartapi/chat.log
Hi @Santhosh
FreePBX versions is v16.
Sangoma desktop app version is the latest: 4.0.6
Sangomartapi version is the latest from standard: 16.0.54.8
SMS version is the latest from standard: 16.0.29
/var/log/asterisk/sangomartapi/chat.log was empty. Last touched on 9/6/24. However /var/log/asterisk/sangomaconnect_out.log seems to have relevant data from a test I just performed. It contains log entries for sending the received SMS message to the mobile sangoma apps, but no entiries for the desktop apps.
Log excerpt (sensitive data obfuscated):
2025-05-08 12:08 -04:00: New sms-inbound SMS from 11NNNNNNNNNN to 11NNNNNNNNNN
2025-05-08 12:08 -04:00: { event: ‘UserEvent’,
2025-05-08 12:08 -04:00: privilege: ‘user,all’,
2025-05-08 12:08 -04:00: userevent: ‘sms-inbound’,
2025-05-08 12:08 -04:00: id: ‘218’,
2025-05-08 12:08 -04:00: to: ‘1NNNNNNNNNN’,
2025-05-08 12:08 -04:00: from: ‘1NNNNNNNNNN’,
2025-05-08 12:08 -04:00: cnam: ‘’,
2025-05-08 12:08 -04:00: message: ‘“test 1208 p.m. EST”’,
2025-05-08 12:08 -04:00: time: ‘1746720516’,
2025-05-08 12:08 -04:00: adaptor: ‘Voipinnovations’,
2025-05-08 12:08 -04:00: emid: ‘’,
2025-05-08 12:08 -04:00: threadid: ‘d78f8f5f58c40636d4ba67e613a2c4825124bfff’,
2025-05-08 12:08 -04:00: didid: ‘2’ }
2025-05-08 12:08 -04:00: GET /mobile/sip/provision query { cloud_username: ‘[email protected]’,
2025-05-08 12:08 -04:00: cloud_password: ‘obfuscated’,
2025-05-08 12:08 -04:00: cloud_id: ‘SANGOMACONNECT’,
2025-05-08 12:08 -04:00: build: ‘2187372’,
2025-05-08 12:08 -04:00: platform: ‘Android’,
2025-05-08 12:08 -04:00: platformversion: ‘15’,
2025-05-08 12:08 -04:00: version: ‘1.0.17’,
2025-05-08 12:08 -04:00: locale: ‘en_US’,
2025-05-08 12:08 -04:00: cpu: ‘arm64-v8a’,
2025-05-08 12:08 -04:00: device: ‘Pixel 9 Pro XL’ }
2025-05-08 12:08 -04:00: GET /mobile/sip/provision params {}
2025-05-08 12:08 -04:00: POST /mobile/sms/fetch query {}
2025-05-08 12:08 -04:00: POST /mobile/sms/fetch params {}
2025-05-08 12:08 -04:00: POST /mobile/sms/fetch body { email: ‘[email protected]’,
2025-05-08 12:08 -04:00: password: ‘obfuscated’,
2025-05-08 12:08 -04:00: last_id: ‘217’,
2025-05-08 12:08 -04:00: last_sent_id: ‘216’ }
2025-05-08 12:08 -04:00: POST /mobile/sms/fetch query {}
2025-05-08 12:08 -04:00: POST /mobile/sms/fetch params {}
2025-05-08 12:08 -04:00: POST /mobile/sms/fetch body { email: ‘[email protected]’,
2025-05-08 12:08 -04:00: password: ‘obfuscated’,
2025-05-08 12:08 -04:00: last_id: ‘217’,
2025-05-08 12:08 -04:00: last_sent_id: ‘216’ }
2025-05-08 12:08 -04:00: GET /mobile/sip/provision query { cloud_username: ‘[email protected]’,
2025-05-08 12:08 -04:00: cloud_password: ‘obfuscated’,
2025-05-08 12:08 -04:00: cloud_id: ‘SANGOMACONNECT’,
2025-05-08 12:08 -04:00: build: ‘2187372’,
2025-05-08 12:08 -04:00: platform: ‘Android’,
2025-05-08 12:08 -04:00: platformversion: ‘15’,
2025-05-08 12:08 -04:00: version: ‘1.0.17’,
2025-05-08 12:08 -04:00: locale: ‘en_US’,
2025-05-08 12:08 -04:00: cpu: ‘arm64-v8a’,
2025-05-08 12:08 -04:00: device: ‘SM-S918U’ }
2025-05-08 12:08 -04:00: GET /mobile/sip/provision params {}
2025-05-08 12:08 -04:00: GET /mobile/sip/contacts { cloud_username: ‘[email protected]’,
2025-05-08 12:08 -04:00: cloud_password: ‘obfuscated’,
2025-05-08 12:08 -04:00: cloud_id: ‘SANGOMACONNECT’ }
2025-05-08 12:08 -04:00: GET /mobile/sip/contacts {}
Hi @chrisduncansb
The above logs shows the sms received in sangomaconnect but we need to check same for sangoma desktop app,
Seems like chat.log is not enabled from GUI, can you enable from Advanced Settings → Sangoma RTAPI and look for Set RTAPI Log Level then set to DEBUG, enable Enable RTAPI Logs and Enable Chat Logs
Make few test and share the /var/log/asterisk/sangomartapi/chat.log for tested sms
Hi @Santhosh
You were correct, the chat log was disabled. However I enabled it and set the RTAPI log level to Debug, tested and still the chat.log file still does not contain incoming SMS information. It does contain information pertaining to the test SMS I sent outbound from the desktop app, which has always worked:
[debug] 2025-5-9 13:32:31 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:31 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:31 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:31 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:31 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:31 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:31 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:31 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:31 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:31 notifyOnlineStatus 25
[debug] 2025-5-9 13:32:32 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:32 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:32 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:32 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:32 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:32 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:32 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:32 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:32 notifyOnlineStatus 18
[debug] 2025-5-9 13:32:32 notifyOnlineStatus 25
[debug] 2025-5-9 13:32:49 sendMessage:: from:[987654], participants:[987654,1XXXXXXXXXX], user_id:18 chat_id:36
[debug] 2025-5-9 13:32:49 sending to sms number 1XXXXXXXXXX
[debug] 2025-5-9 13:32:49 sms.sendFromChatUser { user_id: 18,
chat_id: 36,
number: ‘1XXXXXXXXXX’,
richMessage: [ ‘test oubound from desktop 5/9/25 10:32am PST’ ] }
[debug] 2025-5-9 13:32:49 getAccountUserRecord 334
I did however see a corresponding entry in the rtapi.log file:
[debug] 2025-5-9 13:26:39 send notification: SID-1041 {“jsonrpc”:“2.0”,“method”:“chat.smsPermission”,“params”:{“outgoingDids”:[“1XXXXXXXXXX”]}}
[debug] 2025-5-9 13:26:39 send notification: SID-1056 {“jsonrpc”:“2.0”,“method”:“chat.smsPermission”,“params”:{“outgoingDids”:[“1XXXXXXXXXX”]}}
Hi @chrisduncansb
If chat.log doesn’t contain any incoming SMS-related logs, it may indicate that events are not being received by RTAPI. Please try restarting RTAPI and check again after upgrading to the latest stable version.
fwconsole ma upgrade sangomartapi
fwconsole pm2 --restart sangomartapi
That did the trick. Thank you @Santhosh!