Sangoma Desktop Client closes call just after pickup after changing SSL certificate

Commercial Modules Sangoma Talk / Software Phone
1

Dear all,
We are experiencing a problem that seems to be related to the new SSL certificate I just loaded in our PBXAct installation.

I loaded a new SSL certificate before expiration of the previous one with the Certificate Management module, and set as the default one.
Then I deleted the expiring one and went to System Admin module - HTTPS setup to set the new Certificate as the configured one.

But now if I use Sangoma Phone Desktop Client application to make a call, the call is terminated just at the moment the called extension picks up.

I think the two things are related… Is it possibile I forgot some point to setup the new certificate?

I checked that https://<my PBXACT>:6443/ answers 404 with the correct new certificate.

Thanks in advance.
Lorenzo

2

I add version information, if useful:
PBX Version:

16.0.40.13

PBX Distro:

12.7.8-2306-1.sng7

Asterisk Version:

18.20.2

3

What do the asterisk logs show when the call hangs up?

This is probably totally off, since you’re pretty sure it’s a certificate issue, but I encountered an issue with effectively the same symptoms on Sangoma Desktop that was related to having a loopback trunk connected to 127.0.0.1.

4

I tried to filter out only the relevant rows from asterisk log but I’m not sure what’s happening here.

I substituted <CALLED_NUMBER> to the called external number (but it happens also calling an extension) and <CLID> to the complete Caller ID of the calling extension. 226 is the calling extension, so you can find some “98226” referring to Sangoma Desktop Phone, I suppose.

[REMOVED LOG]

5

Desktop client (A) ---- pbx — B

if the called extension got the call which means from desktop client to freepbx call (A leg) got connected between desktop client and pbx so may not be cert issue, Otherwise this leg itself will not be able to make the connection.

You may enable the desktop client log and check the desktop client log to see what is happening from the client side.

‘Options in app → Advanced Settings → Enable Logging’ and toggle it on/off."

also didnt noticed hangup in your shared asterisk cli logs so may be please share your complete call log via pastebin.

Thanks
Kapil

6

Thank you Kapil for your help.
Sorry for the wrong asterisk log paste, I’ll try to do better.
In the meantime I obtained a detailed log from Sangoma Phone Desktop Client (I am using 4.1.0-alpha.52 because it solves a problem in listening to voicemail messages, but others are using latest 4.0.6 released version)

I can see this line
info [2025-06-13T06:28:50.469Z]: Ending the Outgoing call - Cause : Bad Media Description, Originator : remote

To add some detail, I am relating certificate change to this problem because all was in good shape last week and now, this week, Sangoma Desktop Phone Client is not working for anyone using it in our organizaiton, and I changed the certificate on monday.

7

And this is the pastebin for asterisk log, I hope to have cut it correctly.

I can see in the second line that asterisk doesn’t find the key file for the old certificate I deleted.
[2025-06-13 08:28:44] ERROR[19490] res_rtp_asterisk.c: Failed to read private key from file '/etc/asterisk/keys/CertificatoComune2024.key': No such file or directory

The old key is “CertificatoComune2024.key”
The new key is “CertificatoComune2025.key”

Why is asterisk looking for the deleted certificate?

8

I think I solved it.
I went to
Advanced Settings - Asterisk Builtin mini-HTTP server
and disabled TLS 1.1 ( I should have done it before).
Then I saved and applied the new config.
After this action, now the call remains up after answering.

I also reactivated TLS 1.1 and it still works.
I believe that, after changing SSL cert, Asterisk configuration wasn’t regenerated, and my action of disabling TLS 1.1 caused the regeneration of asterisk settings.

HTH someone!
Thanks all for helping me and pointing out to logs.

2 Likes