Hi there

I currently run Asterisk 16 on a Debian 12 / Bookworm box, which is like installing Asterisk on Debian 11 / Bullseye and then upgrading to 12.
As far as I can tell, this won't work on 13 / Trixie.
From the libgnutls30t64 control;

Breaks: libgnutls30 (<< 3.8.9-3+deb13u1)
Replaces: libgnutls30
Provides: libgnutls30 (= 3.8.9-3+deb13u1)

This leaves me with two options:
- Download Asterisk from the Asterisk site and then compile.
- Backport Asterisk 22 from Debian Unstable / Sid to Debian 13

As a little test I build a backport to 12. This does produce packages,
but I did not test these.

So what does one recommend?


Regards,
Rob

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2/7/26 14:57, Rob van der Putten wrote:

Hi there

I currently run Asterisk 16 on a Debian 12 / Bookworm box, which is
like installing Asterisk on Debian 11 / Bullseye and then upgrading to
12.
As far as I can tell, this won't work on 13 / Trixie.
From the libgnutls30t64 control;

?Breaks: libgnutls30 (<< 3.8.9-3+deb13u1)
?Replaces: libgnutls30
?Provides: libgnutls30 (= 3.8.9-3+deb13u1)

This leaves me with two options:
- Download Asterisk from the Asterisk site and then compile.
- Backport Asterisk 22 from Debian Unstable / Sid to Debian 13

As a little test I build a backport to 12. This does produce packages,
but I did not test these.

So what does one recommend?

It looks like Asterisk didn't make it to Debian Stable release:
? ? $ rmadison asterisk
? ? asterisk? ?| 1:16.28.0~dfsg-0+deb11u3? ? ? ? ?| oldoldstable ? ? ?| source
? ? asterisk? ?| 1:16.28.0~dfsg-0+deb11u3? ? ? ? ?| oldoldstable-debug
| source
? ? asterisk? ?| 1:16.28.0~dfsg-0+deb11u4? ? ? ? ?| oldoldstable ? ? ?| source, amd64, arm64, armhf, i386
? ? asterisk? ?| 1:16.28.0~dfsg-0+deb11u4? ? ? ? ?| oldoldstable-debug
| source
? ? asterisk? ?| 1:22.8.0+dfsg+~cs6.15.60671435-1 | unstable ? ? ?|
source, amd64, arm64, armhf, i386, loong64, ppc64el, riscv64, s390x
? ? asterisk? ?| 1:22.8.0+dfsg+~cs6.15.60671435-1 | unstable-debug? ?
?| source
So I think your best bet is to build a backport from source package in unstable.
I don't know why there is no package in testing yet.
But I'd still go that route myself and tried to build simple backport
inside chroot-ed environment of Debian Stable.
Could be quite an adventure, especially if it also require to build a
chain of different dependencies for it first.
--
With kindest regards, Alexander.
Debian - The universal operating system
https://www.debian.org


--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Hi there


On 07/02/2026 12:42, Alexander V. Makartsev wrote:

On 2/7/26 14:57, Rob van der Putten wrote:

Hi there

I currently run Asterisk 16 on a Debian 12 / Bookworm box, which is
like installing Asterisk on Debian 11 / Bullseye and then upgrading to
12.
As far as I can tell, this won't work on 13 / Trixie.
From the libgnutls30t64 control;

ÿBreaks: libgnutls30 (<< 3.8.9-3+deb13u1)
ÿReplaces: libgnutls30
ÿProvides: libgnutls30 (= 3.8.9-3+deb13u1)

This leaves me with two options:
- Download Asterisk from the Asterisk site and then compile.
- Backport Asterisk 22 from Debian Unstable / Sid to Debian 13

As a little test I build a backport to 12. This does produce packages,
but I did not test these.

So what does one recommend?

It looks like Asterisk didn't make it to Debian Stable release:
$ rmadison asterisk
ÿ asteriskÿ| 1:16.28.0~dfsg-0+deb11u3ÿ ÿ ÿ ÿ ÿ| oldoldstable ÿ ÿ ÿ| source
ÿ asteriskÿ| 1:16.28.0~dfsg-0+deb11u3ÿ ÿ ÿ ÿ ÿ| oldoldstable-debug | source
ÿ asteriskÿ| 1:16.28.0~dfsg-0+deb11u4ÿ ÿ ÿ ÿ ÿ| oldoldstable ÿ ÿ ÿ| source, amd64, arm64, armhf, i386> ÿ asteriskÿ| 1:16.28.0~dfsg-0+deb11u4ÿ ÿ ÿ ÿ ÿ| oldoldstable-debug

| source

ÿ asteriskÿ| 1:22.8.0+dfsg+~cs6.15.60671435-1 | unstable ÿ ÿ ÿ| source, amd64, arm64, armhf, i386, loong64, ppc64el, riscv64, s390x
ÿ asteriskÿ| 1:22.8.0+dfsg+~cs6.15.60671435-1 | unstable-debugÿ ÿ ÿ| source

So I think your best bet is to build a backport from source package in unstable.
I don't know why there is no package in testing yet.

This is due to lack of maintainers. Debian has been asking for new
volunteers for years.

But I'd still go that route myself and tried to build simple backport
inside chroot-ed environment of Debian Stable.
Could be quite an adventure, especially if it also require to build a
chain of different dependencies for it first.

AFIAK, if the Build-Depends do not require a package that is newer than
what is available in Stable this is not an issue. It even builds in
oldstable.


Regards,
Rob

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Sat, 7 Feb 2026, Rob van der Putten wrote:

Hi there

I currently run Asterisk 16 on a Debian 12 / Bookworm box, which is like installing Asterisk on Debian 11 / Bullseye and then upgrading to 12.
As far as I can tell, this won't work on 13 / Trixie.
From the libgnutls30t64 control;

Breaks: libgnutls30 (<< 3.8.9-3+deb13u1)
Replaces: libgnutls30
Provides: libgnutls30 (= 3.8.9-3+deb13u1)

This leaves me with two options:
- Download Asterisk from the Asterisk site and then compile.
- Backport Asterisk 22 from Debian Unstable / Sid to Debian 13

As a little test I build a backport to 12. This does produce packages, but I did not test these.

So what does one recommend?

I'm running sid built on bookworm with no issues.

Tim.

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Sat, Feb 7, 2026 at 4:58?AM Rob van der Putten <rob@sput.nl> wrote:

Hi there

I currently run Asterisk 16 on a Debian 12 / Bookworm box, which is like installing Asterisk on Debian 11 / Bullseye and then upgrading to 12.
As far as I can tell, this won't work on 13 / Trixie.
From the libgnutls30t64 control;

Breaks: libgnutls30 (<< 3.8.9-3+deb13u1)
Replaces: libgnutls30
Provides: libgnutls30 (= 3.8.9-3+deb13u1)

This leaves me with two options:
- Download Asterisk from the Asterisk site and then compile.
- Backport Asterisk 22 from Debian Unstable / Sid to Debian 13

As a little test I build a backport to 12. This does produce packages,
but I did not test these.

So what does one recommend?

You should probably build a modern version of Astersik on your own.
I was just reading about the latest releases of Astersik due to security
bugs. The latest Astersik versions are 23.2.2 and 22.8.2 (and 21.12.1
and 20.18.2). Also see <https://seclists.org/fulldisclosure/2026/Feb/> and <https://github.com/asterisk/asterisk>.
Jeff


--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Hi there


On 08/02/2026 22:04, Jeffrey Walton wrote:

On Sat, Feb 7, 2026 at 4:58?AM Rob van der Putten <rob@sput.nl <mailto:rob@sput.nl>> wrote:

Hi there

I currently run Asterisk 16 on a Debian 12 / Bookworm box, which is
like
installing Asterisk on Debian 11 / Bullseye and then upgrading to 12.
As far as I can tell, this won't work on 13 / Trixie.
ÿFrom the libgnutls30t64 control;

ÿ Breaks: libgnutls30 (<< 3.8.9-3+deb13u1)
ÿ Replaces: libgnutls30
ÿ Provides: libgnutls30 (= 3.8.9-3+deb13u1)

This leaves me with two options:
- Download Asterisk from the Asterisk site and then compile.
- Backport Asterisk 22 from Debian Unstable / Sid to Debian 13

As a little test I build a backport to 12. This does produce packages,
but I did not test these.

So what does one recommend?

You should probably build a modern version of Astersik on your own.

I was just reading about the latest releases of Astersikÿdue to security bugs.ÿ The latestÿAstersik versions areÿ23.2.2 and 22.8.2 (andÿ21.12.1
andÿ20.18.2).ÿ Also see <https://seclists.org/fulldisclosure/2026/Feb/ <https://seclists.org/fulldisclosure/2026/Feb/>> and <https:// github.com/asterisk/asterisk <https://github.com/asterisk/asterisk>>.

The speed at which security patches are implemented is an issue. I'm not
sure what a releasable time would be.


Regards,
Rob

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Mon, 9 Feb 2026, Rob van der Putten wrote:

Hi there

On 08/02/2026 22:04, Jeffrey Walton wrote:

On Sat, Feb 7, 2026 at 4:58?AM Rob van der Putten <rob@sput.nl
<mailto:rob@sput.nl>> wrote:

Hi there

I currently run Asterisk 16 on a Debian 12 / Bookworm box, which is
like
installing Asterisk on Debian 11 / Bullseye and then upgrading to 12.
As far as I can tell, this won't work on 13 / Trixie.
From the libgnutls30t64 control;

Breaks: libgnutls30 (<< 3.8.9-3+deb13u1)
Replaces: libgnutls30
Provides: libgnutls30 (= 3.8.9-3+deb13u1)

This leaves me with two options:
- Download Asterisk from the Asterisk site and then compile.
- Backport Asterisk 22 from Debian Unstable / Sid to Debian 13

As a little test I build a backport to 12. This does produce packages, >> but I did not test these.

So what does one recommend?


You should probably build a modern version of Astersik on your own.

I was just reading about the latest releases of Astersik due to security
bugs. The latest Astersik versions are 23.2.2 and 22.8.2 (and 21.12.1
and 20.18.2). Also see <https://seclists.org/fulldisclosure/2026/Feb/
<https://seclists.org/fulldisclosure/2026/Feb/>> and <https://
github.com/asterisk/asterisk <https://github.com/asterisk/asterisk>>.

The speed at which security patches are implemented is an issue. I'm not sure
what a releasable time would be.

Regards,
Rob

One of the difficulties with asterisk security is that few people run a
truely open system, and most setups use a tiny frsction of the possible configuration options.

This means that even easily exploitable bugs might, in practice, be
vanisingly unlikely to be exposed to attackers.

In my own setup, only whitelisted clients can connect and I only use
pjsip. Firewalling is independent of asterisk. Therefore it's unlikely
that a bug in asterisk is actually exploitable on my setup. (I still
keep up-to-date with latest sid but I don't subscribe to bug/security
lists)

Tim.

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Hi there


On 09/02/2026 09:44, Tim Woodall wrote:

On Mon, 9 Feb 2026, Rob van der Putten wrote:

On 08/02/2026 22:04, Jeffrey Walton wrote:

On Sat, Feb 7, 2026 at 4:58?AM Rob van der Putten <rob@sput.nl
<mailto:rob@sput.nl>> wrote:

ÿÿÿ Hi there

ÿÿÿ I currently run Asterisk 16 on a Debian 12 / Bookworm box, which is
ÿÿÿ like
ÿÿÿ installing Asterisk on Debian 11 / Bullseye and then upgrading to
12.
ÿÿÿ As far as I can tell, this won't work on 13 / Trixie.
ÿÿÿÿÿ From the libgnutls30t64 control;

ÿÿÿÿÿÿ Breaks: libgnutls30 (<< 3.8.9-3+deb13u1)
ÿÿÿÿÿÿ Replaces: libgnutls30
ÿÿÿÿÿÿ Provides: libgnutls30 (= 3.8.9-3+deb13u1)

ÿÿÿ This leaves me with two options:
ÿÿÿ - Download Asterisk from the Asterisk site and then compile.
ÿÿÿ - Backport Asterisk 22 from Debian Unstable / Sid to Debian 13

ÿÿÿ As a little test I build a backport to 12. This does produce
packages,
ÿÿÿ but I did not test these.

ÿÿÿ So what does one recommend?


You should probably build a modern version of Astersik on your own.

I was just reading about the latest releases of Astersik due to
security bugs.ÿ The latest Astersik versions are 23.2.2 and 22.8.2
(and 21.12.1 and 20.18.2).ÿ Also see <https://seclists.org/
fulldisclosure/2026/Feb/ <https://seclists.org/fulldisclosure/2026/
Feb/>> and <https:// github.com/asterisk/asterisk <https://
github.com/asterisk/asterisk>>.

The speed at which security patches are implemented is an issue. I'm
not sure what a releasable time would be.

One of the difficulties with asterisk security is that few people run a truely open system, and most setups use a tiny frsction of the possible configuration options.

This means that even easily exploitable bugs might, in practice, be vanisingly unlikely to be exposed to attackers.

In my own setup, only whitelisted clients can connect and I only use
pjsip. Firewalling is independent of asterisk. Therefore it's unlikely
that a bug in asterisk is actually exploitable on my setup. (I still
keep up-to-date with latest sid but I don't subscribe to bug/security
lists)

With a default Debian install, the files in /etc/asterisk/ are owned asterisk:asterisk. I always change that to root:asterisk. This way the
daemon can't write to it's own config files.
And there is a firewall and access control lists.
So I'm not overly worried.

Whenever I build a backport I install a cron job to keep track of
changes. Currently that's a cronjob for RDAP.

Asterisk in Sid just changed from 20.8.0 to 20.8.2. So that's four days
after the original security release.


Regards,
Rob

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Hi there


On 09/02/2026 10:25, Rob van der Putten wrote:

On 09/02/2026 09:44, Tim Woodall wrote:

On Mon, 9 Feb 2026, Rob van der Putten wrote:

On 08/02/2026 22:04, Jeffrey Walton wrote:

On Sat, Feb 7, 2026 at 4:58?AM Rob van der Putten <rob@sput.nl
<mailto:rob@sput.nl>> wrote:

ÿÿÿ Hi there

ÿÿÿ I currently run Asterisk 16 on a Debian 12 / Bookworm box, which is >>>> ÿÿÿ like
ÿÿÿ installing Asterisk on Debian 11 / Bullseye and then upgrading
to ÿÿÿ 12.
ÿÿÿ As far as I can tell, this won't work on 13 / Trixie.
ÿÿÿÿÿ From the libgnutls30t64 control;

ÿÿÿÿÿÿ Breaks: libgnutls30 (<< 3.8.9-3+deb13u1)
ÿÿÿÿÿÿ Replaces: libgnutls30
ÿÿÿÿÿÿ Provides: libgnutls30 (= 3.8.9-3+deb13u1)

ÿÿÿ This leaves me with two options:
ÿÿÿ - Download Asterisk from the Asterisk site and then compile.
ÿÿÿ - Backport Asterisk 22 from Debian Unstable / Sid to Debian 13

ÿÿÿ As a little test I build a backport to 12. This does produce
packages,
ÿÿÿ but I did not test these.

ÿÿÿ So what does one recommend?


You should probably build a modern version of Astersik on your own.

I was just reading about the latest releases of Astersik due to
security bugs.ÿ The latest Astersik versions are 23.2.2 and 22.8.2
(and 21.12.1 and 20.18.2).ÿ Also see <https://seclists.org/
fulldisclosure/2026/Feb/ <https://seclists.org/fulldisclosure/2026/
Feb/>> and <https:// github.com/asterisk/asterisk <https://
github.com/asterisk/asterisk>>.

The speed at which security patches are implemented is an issue. I'm
not sure what a releasable time would be.

One of the difficulties with asterisk security is that few people run
a truely open system, and most setups use a tiny frsction of the
possible configuration options.

This means that even easily exploitable bugs might, in practice, be
vanisingly unlikely to be exposed to attackers.

In my own setup, only whitelisted clients can connect and I only use
pjsip. Firewalling is independent of asterisk. Therefore it's unlikely
that a bug in asterisk is actually exploitable on my setup. (I still
keep up-to-date with latest sid but I don't subscribe to bug/security
lists)

With a default Debian install, the files in /etc/asterisk/ are owned asterisk:asterisk. I always change that to root:asterisk. This way the daemon can't write to it's own config files.
And there is a firewall and access control lists.
So I'm not overly worried.

Whenever I build a backport I install a cron job to keep track of
changes. Currently that's a cronjob for RDAP.

Asterisk in Sid just changed from 20.8.0 to 20.8.2. So that's four days after the original security release.

Building the backport complains about missing symbols.
As it turns out, some of those are in the asterisk binary. Th rest is in glibc.
Now I know where to look for missing symbols.


Regards,
Rob
--
Safe internet for everyone: <https://www.freedom.nl/en>

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Mon, 9 Feb 2026, Rob van der Putten wrote:

Hi there

On 09/02/2026 10:25, Rob van der Putten wrote:

Building the backport complains about missing symbols.
As it turns out, some of those are in the asterisk binary. Th rest is in glibc.
Now I know where to look for missing symbols.

apt-mirror@aptmirror19:/mnt/mirror/local/main/a/asterisk-bookworm (master)$ cat fixdepends.patch
diff -urN asterisk-22.7.0~dfsg+~cs6.15.60671435.orig/debian/control asterisk-22.7.0~dfsg+~cs6.15.6
0671435/debian/control
--- asterisk-22.7.0~dfsg+~cs6.15.60671435.orig/debian/control 2025-10-28 19:08:32.000000000 +000

0
+++ asterisk-22.7.0~dfsg+~cs6.15.60671435/debian/control 2025-10-28 19:08:32.000000000 +000

0
@@ -73,7 +73,6 @@
libxslt1-dev,
perl <!nodoc>,
portaudio19-dev,
- systemd-dev,
unixodbc-dev,
uuid-dev,
zlib1g-dev, apt-mirror@aptmirror19:/mnt/mirror/local/main/a/asterisk-bookworm (master)$

I think that's all I need to build on bookworm. But I build without systemd instslled.

apt-mirror@aptmirror19:/mnt/mirror/local/main/a/asterisk (master)$ apt-cache policy asterisk
asterisk:
Installed: (none)
Candidate: 1:22.8.2+dfsg+~cs6.15.60671435-1+~tjw12r1
Version table:
1:22.8.2+dfsg+~cs6.15.60671435-1+~tjw12r1 995
995 http://aptmirror.home.woodall.me.uk/local bookworm/main amd64 Packages
apt-mirror@aptmirror19:/mnt/mirror/local/main/a/asterisk (master)$

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

El s b, 07-02-2026 a las 10:57 +0100, Rob van der Putten escribi¢
:

This leaves me with two options:
- Download Asterisk from the Asterisk site and then compile.

Compile is what I did when Asterisk was no longer in Debian (old
fashion way)

Download Asterisk

$ ./configure

After that, if you want a lot of tunning you can use "$ make
menuconfig"

$ make
# make install


Works like a charm.

For more information:

https://docs.asterisk.org/Getting-Started/Installing-Asterisk/Installing-As terisk-From-Source/

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Tue, 10 Feb 2026, Tim Woodall wrote:

On Mon, 9 Feb 2026, Rob van der Putten wrote:

Hi there


On 09/02/2026 10:25, Rob van der Putten wrote:

Building the backport complains about missing symbols.
As it turns out, some of those are in the asterisk binary. Th rest is in
glibc.
Now I know where to look for missing symbols.

I think that's all I need to build on bookworm. But I build without systemd instslled.

Note, I build in a chroot without any init system installed, not just
not systemd. I don't recall why I had to remove that build-depends.

Tim.

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Mon, Feb 9, 2026 at 4:26?AM Rob van der Putten <rob@sput.nl> wrote:

[...]

So what does one recommend?


You should probably build a modern version of Astersik on your own.

I was just reading about the latest releases of Astersik due to
security bugs. The latest Astersik versions are 23.2.2 and 22.8.2
(and 21.12.1 and 20.18.2). Also see <https://seclists.org/
fulldisclosure/2026/Feb/ <https://seclists.org/fulldisclosure/2026/
Feb/>> and <https:// github.com/asterisk/asterisk <https://
github.com/asterisk/asterisk>>.

[...]

Asterisk in Sid just changed from 20.8.0 to 20.8.2. So that's four days
after the original security release.

The latest version of the 20.x line is 20.18.2, not 20.8.2. It looks like
the 20.8.1 tag happened about 2 years ago. I cannot find 20.8.2 in GitHub
for the project. Confer, <https://github.com/asterisk/asterisk/tree/20.18.2> and <https://github.com/asterisk/asterisk/tree/20.8.1>.
Jeff


--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Hi there


On 11/02/2026 00:41, Jeffrey Walton wrote:

On Mon, Feb 9, 2026 at 4:26?AM Rob van der Putten <rob@sput.nl <mailto:rob@sput.nl>> wrote:

>>> [...]
>>>
>>> ÿÿÿ So what does one recommend?
>>>
>>>
>>> You should probably build a modern version of Astersik on your own.
>>>
>>> I was just reading about the latest releases of Astersik due to
>>> security bugs.ÿ The latest Astersik versions are 23.2.2 and 22.8.2
>>> (and 21.12.1 and 20.18.2).ÿ Also see <https://seclists.org/
<https://seclists.org/>
>>> fulldisclosure/2026/Feb/ <https://seclists.org/
fulldisclosure/2026/ <https://seclists.org/fulldisclosure/2026/>
>>> Feb/>> and <https:// github.com/asterisk/asterisk <http://
github.com/asterisk/asterisk> <https://
>>> github.com/asterisk/asterisk <http://github.com/asterisk/
asterisk>>>.
ÿ[...]

Asterisk in Sid just changed from 20.8.0 to 20.8.2. So that's four days
after the original security release.

The latest version of the 20.x line is 20.18.2, not 20.8.2.ÿ It looks
like the 20.8.1 tag happened about 2 years ago.ÿ I cannot find 20.8.2 in GitHub for the project.ÿ Confer, <https://github.com/asterisk/asterisk/ tree/20.18.2 <https://github.com/asterisk/asterisk/tree/20.18.2>> and <https://github.com/asterisk/asterisk/tree/20.8.1 <https://github.com/ asterisk/asterisk/tree/20.8.1>>.

Its's a typo. I meant 22.8.0 to 22.8.2.


Regards,
Rob

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Hi there


On 10/02/2026 13:04, Listas wrote:

El s b, 07-02-2026 a las 10:57 +0100, Rob van der Putten escribi¢:

This leaves me with two options:
- Download Asterisk from the Asterisk site and then compile.

Compile is what I did when Asterisk was no longer in Debian (old
fashion way)

Download Asterisk

$ ./configure

If you have got an older version of libjwt, you might want to use
'configure --with-libjwt-bundled'. This enables more options in 'make menuconfig'.
Debian 12 comes with 1.10.2-1+deb12u1. Debian 13 with 1.17.2-1. The
version used with '--with-libjwt-bundled' is 1.15.3.

After that, if you want a lot of tunning you can use "$ make
menuconfig"

$ make
# make install

Works like a charm.

For more information:

https://docs.asterisk.org/Getting-Started/Installing-Asterisk/Installing-Asterisk-From-Source/

Regards,
Rob

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Hi there


On 10/02/2026 19:31, Tim Woodall wrote:

On Tue, 10 Feb 2026, Tim Woodall wrote:

On Mon, 9 Feb 2026, Rob van der Putten wrote:

Hi there


On 09/02/2026 10:25, Rob van der Putten wrote:


Building the backport complains about missing symbols.
As it turns out, some of those are in the asterisk binary. Th rest is
in glibc.
Now I know where to look for missing symbols.

I think that's all I need to build on bookworm. But I build without
systemd instslled.

Note, I build in a chroot without any init system installed, not just
not systemd. I don't recall why I had to remove that build-depends.

It complains about systemd-dev not being installed, even though it is.
You can override that with '-d'.
I don't use systemd on the box that runs Asterisk.


Regards,
Rob

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Hi there


On 11/02/2026 09:45, Rob van der Putten wrote:

On 10/02/2026 19:31, Tim Woodall wrote:

On Tue, 10 Feb 2026, Tim Woodall wrote:

On Mon, 9 Feb 2026, Rob van der Putten wrote:

Hi there


On 09/02/2026 10:25, Rob van der Putten wrote:


Building the backport complains about missing symbols.
As it turns out, some of those are in the asterisk binary. Th rest
is in glibc.
Now I know where to look for missing symbols.

I think that's all I need to build on bookworm. But I build without
systemd instslled.

Note, I build in a chroot without any init system installed, not just
not systemd. I don't recall why I had to remove that build-depends.

It complains about systemd-dev not being installed, even though it is.
You can override that with '-d'.
I don't use systemd on the box that runs Asterisk.

I'm currently experimenting with a backport.
Somehow IAX doesn't work with IPv6.


Regards,
Rob

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Hi there


On 12/02/2026 17:57, Rob van der Putten wrote:

On 11/02/2026 09:45, Rob van der Putten wrote:

On 10/02/2026 19:31, Tim Woodall wrote:

On Tue, 10 Feb 2026, Tim Woodall wrote:

On Mon, 9 Feb 2026, Rob van der Putten wrote:

Hi there


On 09/02/2026 10:25, Rob van der Putten wrote:


Building the backport complains about missing symbols.
As it turns out, some of those are in the asterisk binary. Th rest
is in glibc.
Now I know where to look for missing symbols.

I think that's all I need to build on bookworm. But I build without
systemd instslled.

Note, I build in a chroot without any init system installed, not just
not systemd. I don't recall why I had to remove that build-depends.

It complains about systemd-dev not being installed, even though it is.
You can override that with '-d'.
I don't use systemd on the box that runs Asterisk.

I'm currently experimenting with a backport.
Somehow IAX doesn't work with IPv6.

This now works too.


Regards,
Rob

--- PyGate Linux v1.5.11
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)