Asterisk crashes on trunk registration on latest version 18.15

[sim0Nfrem0Nt]

Hi,
I've stumbled upon an issue about asterisk crashing when I tried to register a trunk on the latest update (docker hub of 30/11/2023).
The registration message got to the trunk, and it sent an Unauthorized answer. When Asterisk receives the message, it crashes right away.
I've rolled back to the alpine-3.17-18.15.1 version and it works properly.
Might be good to check the 20.5 versions of asterisk.

I've noticed that the GitHub repository has not been updated lately when the image on docker hub has been updated. Is it intentional?

Best Regards,
Simon

[TheMrTaik]

Hi @andrius , I have the same problem.

I noticed that by not registering the trunk, but only the internal phones, when I go to perform a test phone call (echotest), the container crashes, always giving me segfault error 4 in libpjsip.so.2 in the syslog of the host system.

No problem going back to the version indicated by @sim0Nfrem0Nt

Even in 20.5.0 same problem.

Thanks for collaboration,
Best regards
MrTaik

[kantum]

⚠️ @andrius Do you still have access to your docker hub account? This looks like some vulnerability injection, all images are updated without any difference from the source repository!

Please clarify your actions on docker hub and why they are not related to this repository.

[andrius]

Hello, yes, I have access to the docker hub. The issue is with the asterisk/alpine/pjsip and it is there for a long time already. As you might find from the Dockerfile's, in case of alpine it just install asterisk with the apk command.
I suggest to use debian-based image or to use SIP stack (so you will need a older asterisk).

[kantum]

I understand, but why all the images are being rebuilt each time? It breaks the reproducibility of docker.

For instance, we use the alpine-3.17-18.15.1. It has been rebuilt yesterday with a (possibly) new digest! So our application might not work if we pull the new image.

We will make our own copy of Dockerfile, but it's kind of a shame.

[piotrooo]

I would also like to inquire about the general maintenance of this project. The significant refactor is mentioned in the readme.

Caution

What is the status of this refactor? Can we rely on these Asterisk images?