Asterisk 18.0.0 Now Available

Home » Asterisk Users » Asterisk 18.0.0 Now Available
Asterisk Users 4 Comments

The Asterisk Development Team would like to announce the release of Asterisk 18.0.0. This release is available for immediate download at https://downloads.asterisk.org/pub/telephony/asterisk

The release of Asterisk 18.0.0 resolves several issues reported by the community and would have not been possible without your participation.

Thank you!

The following issues are resolved in this release:

Security bugs fixed in this release:
———————————

4 thoughts on - Asterisk 18.0.0 Now Available

  • Hello!

    I just tested the new codec negotiation feature and unfortunately wasn’t able to get it working as expected. I tried several configurations – but none has been working – the result has always been the same.

    Use case:
    Alice calls Bob – sends INVITE G722 / alaw / ulaw

    Configured in Asterisk for this device: G722 / alaw / ulaw / gsm A:
    codec_prefs_incoming_offer = prefer: configured, operation: intersect, keep: all, transcode: prevent

    Bob:
    Configured in Asterisk for this device: alaw / ulaw B:
    codec_prefs_outgoing_offer = prefer: configured or pending, operation: intersect, keep: first or all, transcode: prevent Asterisk sends INVITE to Bob alaw / ulaw

    Asterisk receives OK from Bob alaw B:
    codec_prefs_incoming_answer = prefer: configured or pending, operation: intersect, keep: first or all, transcode: prevent

    Asterisk sends OK to Alice G722 / alaw / ulaw A:
    codec_prefs_outgoing_answer = prefer: pending, operation: intersect, keep: first or all, transcode: prevent

    => I would have expected alaw to be sent to A – but G722 / alaw / ulaw is sent and transcoding is active!

    What did I do wrong?
    Could you please add the correct configuration you expect to get the expected result alaw?

    Thanks Kind regards Michael

  • This is expected right now. Foundational aspects were put in, but there is still work to be done for PJSIP which will land in a future release. The complexity of it and the investigation of how things work, interactions, etc took considerably longer than expected. If there’s specific scenarios that you’d like to ensure are met you can reach out on the asterisk-dev mailing list and George Joseph will add them to the list if not already present. Even just from AstriDevCon there were some things that individuals brought up.

  • Oh – thanks for the information – I missed this :-(. How do I know if this feature is finally enabled? Will it be in asterisk 18 – or will it come in some later major version?

    Well, I think the scenario I have should be a very easy and basic scenario. I already discussed it in the past. Therefore I think it’s not necessary to add it again.

    Thanks Michael

  • It is planned to land in a future Asterisk 18 release, it will be stated in the changelog/release notes and we will likely do a blog post about it as well.