Menu
▾
▴
astlinux-devel — The AstLinux development environment, compilation, etc
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
(41) |
Apr
(35) |
May
(18) |
Jun
(5) |
Jul
(4) |
Aug
(37) |
Sep
(9) |
Oct
(20) |
Nov
(50) |
Dec
(217) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(212) |
Feb
(76) |
Mar
(113) |
Apr
(88) |
May
(130) |
Jun
(54) |
Jul
(208) |
Aug
(223) |
Sep
(112) |
Oct
(63) |
Nov
(131) |
Dec
(103) |
| 2010 |
Jan
(247) |
Feb
(130) |
Mar
(43) |
Apr
(92) |
May
(40) |
Jun
(43) |
Jul
(43) |
Aug
(80) |
Sep
(44) |
Oct
(74) |
Nov
(21) |
Dec
(46) |
| 2011 |
Jan
(36) |
Feb
(11) |
Mar
(21) |
Apr
(33) |
May
(4) |
Jun
(12) |
Jul
(5) |
Aug
(20) |
Sep
|
Oct
(64) |
Nov
(26) |
Dec
(71) |
| 2012 |
Jan
(13) |
Feb
(24) |
Mar
(11) |
Apr
(2) |
May
(10) |
Jun
(5) |
Jul
(13) |
Aug
(7) |
Sep
(26) |
Oct
(22) |
Nov
(17) |
Dec
(16) |
| 2013 |
Jan
(6) |
Feb
(6) |
Mar
(6) |
Apr
(8) |
May
(20) |
Jun
|
Jul
(1) |
Aug
(4) |
Sep
(18) |
Oct
(3) |
Nov
(14) |
Dec
(33) |
| 2014 |
Jan
(26) |
Feb
(6) |
Mar
(69) |
Apr
(10) |
May
|
Jun
(8) |
Jul
(18) |
Aug
(22) |
Sep
(19) |
Oct
(17) |
Nov
|
Dec
(4) |
| 2015 |
Jan
(14) |
Feb
(18) |
Mar
|
Apr
|
May
(26) |
Jun
(8) |
Jul
(9) |
Aug
(10) |
Sep
(15) |
Oct
(2) |
Nov
(30) |
Dec
(33) |
| 2016 |
Jan
(1) |
Feb
(24) |
Mar
(19) |
Apr
(1) |
May
|
Jun
(3) |
Jul
(1) |
Aug
(1) |
Sep
(20) |
Oct
(5) |
Nov
(14) |
Dec
(4) |
| 2017 |
Jan
(15) |
Feb
(35) |
Mar
(10) |
Apr
(9) |
May
(14) |
Jun
(33) |
Jul
(1) |
Aug
(27) |
Sep
(7) |
Oct
|
Nov
(10) |
Dec
(15) |
| 2018 |
Jan
(29) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(11) |
Jun
|
Jul
(1) |
Aug
(8) |
Sep
(11) |
Oct
(22) |
Nov
(9) |
Dec
(13) |
| 2019 |
Jan
(1) |
Feb
(7) |
Mar
(3) |
Apr
(21) |
May
(34) |
Jun
(36) |
Jul
(18) |
Aug
(17) |
Sep
(19) |
Oct
(8) |
Nov
(3) |
Dec
|
| 2020 |
Jan
|
Feb
(4) |
Mar
(8) |
Apr
(29) |
May
(50) |
Jun
(8) |
Jul
(2) |
Aug
(10) |
Sep
(1) |
Oct
(7) |
Nov
(9) |
Dec
(19) |
| 2021 |
Jan
(2) |
Feb
(9) |
Mar
(6) |
Apr
(21) |
May
(13) |
Jun
(11) |
Jul
(2) |
Aug
(1) |
Sep
(3) |
Oct
(26) |
Nov
(2) |
Dec
(16) |
| 2022 |
Jan
(8) |
Feb
(7) |
Mar
(1) |
Apr
(13) |
May
(1) |
Jun
(4) |
Jul
(4) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2023 |
Jan
(2) |
Feb
(3) |
Mar
(16) |
Apr
|
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(13) |
Sep
(8) |
Oct
(6) |
Nov
(4) |
Dec
|
| 2024 |
Jan
(3) |
Feb
(3) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(5) |
Aug
|
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2025 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
(11) |
May
(1) |
Jun
(9) |
Jul
(18) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
1
|
2
|
3
|
|
4
|
5
|
6
(1) |
7
|
8
|
9
|
10
|
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
|
18
|
19
|
20
|
21
|
22
|
23
|
24
(6) |
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
|
From: Michael K. <mic...@ip...> - 2020-10-24 23:27:56
|
Thanks that works. I will do that!
Regards
Michael Knill
On 25/10/20, 10:13 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Good point ... how about
if ls -l /usr/lib/asterisk/modules/*pjsip.so >/dev/null 2>&1; then
echo "pjsip installed"
else
echo "pjsip not installed"
fi
Lonnie
> On Oct 24, 2020, at 5:57 PM, Michael Knill <mic...@ip...> wrote:
>
> Thanks Lonnie.
>
> Unfortunately I turn off PJSIP in modules.conf already so this method does not help me find whether its an SE version or not.
> For example:
> |||||
> | A | Release: astlinux-1.3.7.1 - Asterisk 13.29.2
> | s | Host Name: 3037-QGPSC-CM1.private.ipcaccess.net
> | t | Last Boot: 2020-10-24 15:35
> | L | Linux: 3.16.74-astlinux x86_64
> | i | CPU: Intel Xeon E5-2670 v2 (2x) @ 2500 MHz
> | n | RAM: 2011 MB
> | u | Board Type: genx86_64
> | x | Hardware: VMware Guest VM
> |||||
> 3037-QGPSC-CM1 kd # asterisk -rnx "pjsip show version"
> No such command 'pjsip show version' (type 'core show help pjsip show version' for other possible commands)
> 3037-QGPSC-CM1 kd #
>
> Regards
> Michael Knill
>
> On 25/10/20, 9:43 am, "Lonnie Abelbeck" <li...@lo...> wrote:
>
>
>
>> On Oct 24, 2020, at 4:56 PM, Michael Knill <mic...@ip...> wrote:
>>
>> Hi Devs
>>
>> Just wondering with the astlinux-release file whether it can show if its an SE version or not e.g. ‘astlinux-1.4.0SE’.
>> What uses this file? Would it break anything?
>>
>> Regards
>> Michael Knill
>
> The SE version is only related to the Asterisk version and how it was built.
>
> The /etc/astlinux-release file relates the base system.
>
> If you need to programmatically know if pjsip is supported, one method is:
>
> (SE version, w/o pjsip)
> # asterisk -rnx "pjsip show version"
> No such command 'pjsip show version' (type 'core show help pjsip show' for other possible commands)
>
> (non-SE version, with pjsip)
> # asterisk -rnx "pjsip show version"
> PJPROJECT version currently running against: 2.10
>
>
> I would not mess with the /etc/astlinux-release file.
>
> Lonnie
>
>
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: Lonnie A. <li...@lo...> - 2020-10-24 23:13:41
|
Good point ... how about if ls -l /usr/lib/asterisk/modules/*pjsip.so >/dev/null 2>&1; then echo "pjsip installed" else echo "pjsip not installed" fi Lonnie > On Oct 24, 2020, at 5:57 PM, Michael Knill <mic...@ip...> wrote: > > Thanks Lonnie. > > Unfortunately I turn off PJSIP in modules.conf already so this method does not help me find whether its an SE version or not. > For example: > ||||| > | A | Release: astlinux-1.3.7.1 - Asterisk 13.29.2 > | s | Host Name: 3037-QGPSC-CM1.private.ipcaccess.net > | t | Last Boot: 2020-10-24 15:35 > | L | Linux: 3.16.74-astlinux x86_64 > | i | CPU: Intel Xeon E5-2670 v2 (2x) @ 2500 MHz > | n | RAM: 2011 MB > | u | Board Type: genx86_64 > | x | Hardware: VMware Guest VM > ||||| > 3037-QGPSC-CM1 kd # asterisk -rnx "pjsip show version" > No such command 'pjsip show version' (type 'core show help pjsip show version' for other possible commands) > 3037-QGPSC-CM1 kd # > > Regards > Michael Knill > > On 25/10/20, 9:43 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > > >> On Oct 24, 2020, at 4:56 PM, Michael Knill <mic...@ip...> wrote: >> >> Hi Devs >> >> Just wondering with the astlinux-release file whether it can show if its an SE version or not e.g. ‘astlinux-1.4.0SE’. >> What uses this file? Would it break anything? >> >> Regards >> Michael Knill > > The SE version is only related to the Asterisk version and how it was built. > > The /etc/astlinux-release file relates the base system. > > If you need to programmatically know if pjsip is supported, one method is: > > (SE version, w/o pjsip) > # asterisk -rnx "pjsip show version" > No such command 'pjsip show version' (type 'core show help pjsip show' for other possible commands) > > (non-SE version, with pjsip) > # asterisk -rnx "pjsip show version" > PJPROJECT version currently running against: 2.10 > > > I would not mess with the /etc/astlinux-release file. > > Lonnie > > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <mic...@ip...> - 2020-10-24 23:02:08
|
Option 2 may be to just look at the system_firmware_repository_url in webgui-prefs.txt. Not completely accurate as it can be changed but better than nothing.
Regards
Michael Knill
On 25/10/20, 9:57 am, "Michael Knill" <mic...@ip...> wrote:
Thanks Lonnie.
Unfortunately I turn off PJSIP in modules.conf already so this method does not help me find whether its an SE version or not.
For example:
|||||
| A | Release: astlinux-1.3.7.1 - Asterisk 13.29.2
| s | Host Name: 3037-QGPSC-CM1.private.ipcaccess.net
| t | Last Boot: 2020-10-24 15:35
| L | Linux: 3.16.74-astlinux x86_64
| i | CPU: Intel Xeon E5-2670 v2 (2x) @ 2500 MHz
| n | RAM: 2011 MB
| u | Board Type: genx86_64
| x | Hardware: VMware Guest VM
|||||
3037-QGPSC-CM1 kd # asterisk -rnx "pjsip show version"
No such command 'pjsip show version' (type 'core show help pjsip show version' for other possible commands)
3037-QGPSC-CM1 kd #
Regards
Michael Knill
On 25/10/20, 9:43 am, "Lonnie Abelbeck" <li...@lo...> wrote:
> On Oct 24, 2020, at 4:56 PM, Michael Knill <mic...@ip...> wrote:
>
> Hi Devs
>
> Just wondering with the astlinux-release file whether it can show if its an SE version or not e.g. ‘astlinux-1.4.0SE’.
> What uses this file? Would it break anything?
>
> Regards
> Michael Knill
The SE version is only related to the Asterisk version and how it was built.
The /etc/astlinux-release file relates the base system.
If you need to programmatically know if pjsip is supported, one method is:
(SE version, w/o pjsip)
# asterisk -rnx "pjsip show version"
No such command 'pjsip show version' (type 'core show help pjsip show' for other possible commands)
(non-SE version, with pjsip)
# asterisk -rnx "pjsip show version"
PJPROJECT version currently running against: 2.10
I would not mess with the /etc/astlinux-release file.
Lonnie
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: Michael K. <mic...@ip...> - 2020-10-24 22:57:50
|
Thanks Lonnie. Unfortunately I turn off PJSIP in modules.conf already so this method does not help me find whether its an SE version or not. For example: ||||| | A | Release: astlinux-1.3.7.1 - Asterisk 13.29.2 | s | Host Name: 3037-QGPSC-CM1.private.ipcaccess.net | t | Last Boot: 2020-10-24 15:35 | L | Linux: 3.16.74-astlinux x86_64 | i | CPU: Intel Xeon E5-2670 v2 (2x) @ 2500 MHz | n | RAM: 2011 MB | u | Board Type: genx86_64 | x | Hardware: VMware Guest VM ||||| 3037-QGPSC-CM1 kd # asterisk -rnx "pjsip show version" No such command 'pjsip show version' (type 'core show help pjsip show version' for other possible commands) 3037-QGPSC-CM1 kd # Regards Michael Knill On 25/10/20, 9:43 am, "Lonnie Abelbeck" <li...@lo...> wrote: > On Oct 24, 2020, at 4:56 PM, Michael Knill <mic...@ip...> wrote: > > Hi Devs > > Just wondering with the astlinux-release file whether it can show if its an SE version or not e.g. ‘astlinux-1.4.0SE’. > What uses this file? Would it break anything? > > Regards > Michael Knill The SE version is only related to the Asterisk version and how it was built. The /etc/astlinux-release file relates the base system. If you need to programmatically know if pjsip is supported, one method is: (SE version, w/o pjsip) # asterisk -rnx "pjsip show version" No such command 'pjsip show version' (type 'core show help pjsip show' for other possible commands) (non-SE version, with pjsip) # asterisk -rnx "pjsip show version" PJPROJECT version currently running against: 2.10 I would not mess with the /etc/astlinux-release file. Lonnie _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Lonnie A. <li...@lo...> - 2020-10-24 22:43:35
|
> On Oct 24, 2020, at 4:56 PM, Michael Knill <mic...@ip...> wrote: > > Hi Devs > > Just wondering with the astlinux-release file whether it can show if its an SE version or not e.g. ‘astlinux-1.4.0SE’. > What uses this file? Would it break anything? > > Regards > Michael Knill The SE version is only related to the Asterisk version and how it was built. The /etc/astlinux-release file relates the base system. If you need to programmatically know if pjsip is supported, one method is: (SE version, w/o pjsip) # asterisk -rnx "pjsip show version" No such command 'pjsip show version' (type 'core show help pjsip show' for other possible commands) (non-SE version, with pjsip) # asterisk -rnx "pjsip show version" PJPROJECT version currently running against: 2.10 I would not mess with the /etc/astlinux-release file. Lonnie |
|
From: Michael K. <mic...@ip...> - 2020-10-24 21:57:05
|
Hi Devs Just wondering with the astlinux-release file whether it can show if its an SE version or not e.g. ‘astlinux-1.4.0SE’. What uses this file? Would it break anything? Regards Michael Knill |
|
From: Lonnie A. <li...@lo...> - 2020-10-06 14:56:55
|
Announcing AstLinux Release: 1.4.0 More Info: AstLinux Project https://www.astlinux-project.org/ AstLinux 1.4.0 Highlights: * Asterisk Versions: 13.29.2, 13.36.0, 16.13.0 * Linux Kernel 4.19.146, major bump from 3.16.x series * RUNNIX, version bump to runnix-0.6.2, with Linux Kernel 4.19.146, e2fsprogs 1.45.6, util-linux 2.33.2 * WireGuard VPN, version bump, module 1.0.20200908, tools 1.0.20200827 * iproute2 (ip, tc, bridge, etc.) version bump to 4.20.0 * iptables, version bump to 1.8.4 * Fossil, version bump to 2.10.2, security fixes * acme-client, version 2.8.7, add email notify support * dnsmasq, version bump to 2.82, performance improvements and bug fixes * util-linux, version bump to 2.33.2, add 'nsenter' command * zabbix, version bump to 4.0.24 * Asterisk '13se' (stable edition) version 13.29.2 is older than latest Asterisk 13.x version but more tested, built --without-pjproject * pjsip, version bump to 2.10 * DAHDI, version bump to dahdi-linux 3.1.0 and dahdi-tools 3.1.0, required to support the new kernel Previous DAHDI_HFCS and RHINO drivers are no longer supported Add patch to return DAHDI support for (wctdm24xxp) TDM800P/AEX800 and TDM410P/AEX410 PCI cards Add patch to return DAHDI support for (wctdm) TDM400P PCI cards Add patch to return DAHDI support for (wcfxo) X100P PCI cards * Package upgrades providing important security and bug fixes Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.4.0/docs/ChangeLog.txt All users are encouraged to upgrade. Previous Asterisk 11.x users are encouraged to switch to the new Asterisk '13se' (stable edition). Some configuration changes will be needed, though minimal. AstLinux Team |
