Menu
▾
▴
astlinux-users — AstLinux Users Mailing List
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(91) |
Feb
(111) |
Mar
(226) |
Apr
(65) |
May
(197) |
Jun
(202) |
Jul
(92) |
Aug
(87) |
Sep
(120) |
Oct
(133) |
Nov
(89) |
Dec
(155) |
| 2008 |
Jan
(251) |
Feb
(136) |
Mar
(174) |
Apr
(149) |
May
(56) |
Jun
(32) |
Jul
(36) |
Aug
(171) |
Sep
(245) |
Oct
(244) |
Nov
(218) |
Dec
(272) |
| 2009 |
Jan
(113) |
Feb
(119) |
Mar
(192) |
Apr
(117) |
May
(93) |
Jun
(46) |
Jul
(80) |
Aug
(54) |
Sep
(109) |
Oct
(70) |
Nov
(145) |
Dec
(110) |
| 2010 |
Jan
(137) |
Feb
(87) |
Mar
(45) |
Apr
(157) |
May
(58) |
Jun
(99) |
Jul
(188) |
Aug
(136) |
Sep
(101) |
Oct
(100) |
Nov
(61) |
Dec
(60) |
| 2011 |
Jan
(84) |
Feb
(43) |
Mar
(70) |
Apr
(17) |
May
(69) |
Jun
(28) |
Jul
(43) |
Aug
(21) |
Sep
(151) |
Oct
(120) |
Nov
(84) |
Dec
(101) |
| 2012 |
Jan
(119) |
Feb
(82) |
Mar
(70) |
Apr
(115) |
May
(66) |
Jun
(131) |
Jul
(70) |
Aug
(65) |
Sep
(66) |
Oct
(86) |
Nov
(197) |
Dec
(81) |
| 2013 |
Jan
(65) |
Feb
(48) |
Mar
(32) |
Apr
(68) |
May
(98) |
Jun
(59) |
Jul
(41) |
Aug
(52) |
Sep
(42) |
Oct
(37) |
Nov
(10) |
Dec
(27) |
| 2014 |
Jan
(61) |
Feb
(34) |
Mar
(30) |
Apr
(52) |
May
(45) |
Jun
(40) |
Jul
(28) |
Aug
(9) |
Sep
(39) |
Oct
(69) |
Nov
(55) |
Dec
(19) |
| 2015 |
Jan
(13) |
Feb
(21) |
Mar
(5) |
Apr
(14) |
May
(30) |
Jun
(51) |
Jul
(31) |
Aug
(12) |
Sep
(29) |
Oct
(15) |
Nov
(24) |
Dec
(16) |
| 2016 |
Jan
(62) |
Feb
(76) |
Mar
(30) |
Apr
(43) |
May
(46) |
Jun
(62) |
Jul
(21) |
Aug
(49) |
Sep
(67) |
Oct
(27) |
Nov
(26) |
Dec
(38) |
| 2017 |
Jan
(7) |
Feb
(12) |
Mar
(69) |
Apr
(59) |
May
(54) |
Jun
(40) |
Jul
(76) |
Aug
(82) |
Sep
(92) |
Oct
(51) |
Nov
(32) |
Dec
(30) |
| 2018 |
Jan
(22) |
Feb
(25) |
Mar
(34) |
Apr
(35) |
May
(37) |
Jun
(21) |
Jul
(69) |
Aug
(55) |
Sep
(17) |
Oct
(67) |
Nov
(9) |
Dec
(5) |
| 2019 |
Jan
(19) |
Feb
(12) |
Mar
(15) |
Apr
(19) |
May
|
Jun
(27) |
Jul
(27) |
Aug
(25) |
Sep
(25) |
Oct
(27) |
Nov
(10) |
Dec
(14) |
| 2020 |
Jan
(22) |
Feb
(20) |
Mar
(36) |
Apr
(40) |
May
(52) |
Jun
(35) |
Jul
(21) |
Aug
(32) |
Sep
(71) |
Oct
(27) |
Nov
(11) |
Dec
(16) |
| 2021 |
Jan
(16) |
Feb
(21) |
Mar
(21) |
Apr
(27) |
May
(17) |
Jun
|
Jul
(2) |
Aug
(22) |
Sep
(23) |
Oct
(7) |
Nov
(11) |
Dec
(28) |
| 2022 |
Jan
(23) |
Feb
(18) |
Mar
(9) |
Apr
(15) |
May
(15) |
Jun
(7) |
Jul
(8) |
Aug
(15) |
Sep
(1) |
Oct
|
Nov
(11) |
Dec
(10) |
| 2023 |
Jan
(14) |
Feb
(10) |
Mar
(11) |
Apr
(13) |
May
(2) |
Jun
(30) |
Jul
(1) |
Aug
(15) |
Sep
(13) |
Oct
(3) |
Nov
(25) |
Dec
(5) |
| 2024 |
Jan
(3) |
Feb
(10) |
Mar
(9) |
Apr
|
May
(1) |
Jun
(15) |
Jul
(7) |
Aug
(10) |
Sep
(3) |
Oct
(8) |
Nov
(6) |
Dec
(15) |
| 2025 |
Jan
(3) |
Feb
(1) |
Mar
(7) |
Apr
(5) |
May
(13) |
Jun
(16) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Home <da...@ry...> - 2024-06-12 22:54:20
|
For what it may be worth, I've found...pjsip show endpointsandpjsip show contacts... to be useful.Dan -------- Original message --------From: Lonnie Abelbeck <li...@lo...> Date: 6/12/24 6:05 PM (GMT-05:00) To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] PJSIP Hi David,In the Prefs -> Status Tab Options:, there are 4 pairs of these:--Custom Asterisk Name:Custom Asterisk Command:--Which you can label and call what commands you want.And uncheck:--Show SIP Trunk RegistrationsShow SIP Peer Status--Though I don't think there is an exact equivalent from chan_sip to chan_pjsip for status. I still use chan_sip.Lonnie> On Jun 12, 2024, at 4:17 PM, David Kerr <da...@ke...> wrote:> > It looks like> > pjsip list (or show) registrations> pjsip list (or show) contacts> > Gets closest to the old versions? Should the prefs panel be updated to allow a command to be provided?> > David> > On Wed, Jun 12, 2024 at 5:10 PM David Kerr <da...@ke...> wrote:> I'm embarking on a long overdue conversion from SIP to PJSIP in my Asterisk configuration. I think I have it mostly working now but I notice that in the status page the commands to show SIP trunk and SIP peer status no longer exist (I have noload for chan_sip.so). > > SIP Trunk Registrations:No such command 'sip show registry' (type 'core show help sip show' for other possible commands)> > SIP Peer Status:No such command 'sip show peers' (type 'core show help sip show' for other possible commands)> > > Are there alternative commands we could use?> > Thanks> David> > > _______________________________________________> Astlinux-users mailing list> Ast...@li...> https://lists.sourceforge.net/lists/listinfo/astlinux-users> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...._______________________________________________Astlinux-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/astlinux-usersDonations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: David K. <da...@ke...> - 2024-06-12 22:20:11
|
I'm embarking on a long overdue conversion from SIP to PJSIP in my Asterisk configuration. I think I have it mostly working now but I notice that in the status page the commands to show SIP trunk and SIP peer status no longer exist (I have noload for chan_sip.so). SIP Trunk Registrations: No such command 'sip show registry' (type 'core show help sip show' for other possible commands) SIP Peer Status: No such command 'sip show peers' (type 'core show help sip show' for other possible commands) Are there alternative commands we could use? Thanks David |
|
From: Lonnie A. <li...@lo...> - 2024-06-12 22:04:49
|
Hi David, In the Prefs -> Status Tab Options:, there are 4 pairs of these: -- Custom Asterisk Name: Custom Asterisk Command: -- Which you can label and call what commands you want. And uncheck: -- Show SIP Trunk Registrations Show SIP Peer Status -- Though I don't think there is an exact equivalent from chan_sip to chan_pjsip for status. I still use chan_sip. Lonnie > On Jun 12, 2024, at 4:17 PM, David Kerr <da...@ke...> wrote: > > It looks like > > pjsip list (or show) registrations > pjsip list (or show) contacts > > Gets closest to the old versions? Should the prefs panel be updated to allow a command to be provided? > > David > > On Wed, Jun 12, 2024 at 5:10 PM David Kerr <da...@ke...> wrote: > I'm embarking on a long overdue conversion from SIP to PJSIP in my Asterisk configuration. I think I have it mostly working now but I notice that in the status page the commands to show SIP trunk and SIP peer status no longer exist (I have noload for chan_sip.so). > > SIP Trunk Registrations:No such command 'sip show registry' (type 'core show help sip show' for other possible commands) > > SIP Peer Status:No such command 'sip show peers' (type 'core show help sip show' for other possible commands) > > > Are there alternative commands we could use? > > Thanks > David > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: David K. <da...@ke...> - 2024-06-12 21:23:26
|
It looks like pjsip list (or show) registrations pjsip list (or show) contacts Gets closest to the old versions? Should the prefs panel be updated to allow a command to be provided? David On Wed, Jun 12, 2024 at 5:10 PM David Kerr <da...@ke...> wrote: > I'm embarking on a long overdue conversion from SIP to PJSIP in my > Asterisk configuration. I think I have it mostly working now but I notice > that in the status page the commands to show SIP trunk and SIP peer status > no longer exist (I have noload for chan_sip.so). > > SIP Trunk Registrations: > > No such command 'sip show registry' (type 'core show help sip show' for other possible commands) > > SIP Peer Status: > > No such command 'sip show peers' (type 'core show help sip show' for other possible commands) > > > Are there alternative commands we could use? > > Thanks > David > > > |
|
From: Lonnie A. <li...@lo...> - 2024-06-11 01:00:31
|
Great! Thanks for the note. Lonnie > On Jun 10, 2024, at 7:56 PM, Ionel Chila via Astlinux-users <ast...@li...> wrote: > > That was easy. Looks like it worked perfect under UnRaid VM. I will ne to document and take some screenshots for future installations. I need to now configure and do some testing. Will keep you updated. > > > > <Screenshot 2024-06-10 at 7.54.46 PM.png> > > >> On Jun 10, 2024, at 6:52 PM, Lonnie Abelbeck <li...@lo...> wrote: >> >> /mnt/kd/rc.conf.d/user.conf > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Ionel C. <ion...@me...> - 2024-06-11 00:57:08
|
That was easy. Looks like it worked perfect under UnRaid VM. I will ne to document and take some screenshots for future installations. I need to now configure and do some testing. Will keep you updated.  > On Jun 10, 2024, at 6:52 PM, Lonnie Abelbeck <li...@lo...> wrote: > > /mnt/kd/rc.conf.d/user.conf |
|
From: Ionel C. <ion...@me...> - 2024-06-11 00:23:31
|
Hi Lonnie, And I hope things are good with you Sir. Thanks again for all the hard work. I was thinking about keeping the DAHDI PCI but I guess not anymore :) If the UnRaid VM works I may just buy me one of these PAP2 boxes and put the analog line for the house on that box. Will let you know about my progress Best regards > On Jun 10, 2024, at 6:52 PM, Lonnie Abelbeck <li...@lo...> wrote: > > Hi Ionel, > > Do you use still use DAHDI PCI hardware? If so, that is a problem as the AstLinux VM ISO does not include the DAHDI PCI firmware files. If you are still using DAHDI PCI hardware I would keep your dedicated hardware. > > On the other hand, if your setup is VoIP-only, I have not used UnRaid, but it seems to use KVM/QEMU, so in theory it should work. > > Just like Proxmox, you may want to enable the QEMU Guest Agent: > -- /mnt/kd/rc.conf.d/user.conf > QEMU_GUEST_AGENT="yes" > -- > > It should be easy to give it a try using UnRaid with the AstLinux VM ISO. > > Lonnie > > > >> On Jun 10, 2024, at 6:20 PM, Ionel Chila via Astlinux-users <ast...@li...> wrote: >> >> I am running two UnRaid NAS and they have a very rich ecosystems as far as dockers and VM goes. I was wondering if anyone managed to install and run an AstLinux VM under UnRaid? I would love to retire my home-pbx dedicated hardware and run this VM in my existing UnRaid setup. >> >> Thanks for your advise. >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2024-06-10 23:52:16
|
Hi Ionel, Do you use still use DAHDI PCI hardware? If so, that is a problem as the AstLinux VM ISO does not include the DAHDI PCI firmware files. If you are still using DAHDI PCI hardware I would keep your dedicated hardware. On the other hand, if your setup is VoIP-only, I have not used UnRaid, but it seems to use KVM/QEMU, so in theory it should work. Just like Proxmox, you may want to enable the QEMU Guest Agent: -- /mnt/kd/rc.conf.d/user.conf QEMU_GUEST_AGENT="yes" -- It should be easy to give it a try using UnRaid with the AstLinux VM ISO. Lonnie > On Jun 10, 2024, at 6:20 PM, Ionel Chila via Astlinux-users <ast...@li...> wrote: > > I am running two UnRaid NAS and they have a very rich ecosystems as far as dockers and VM goes. I was wondering if anyone managed to install and run an AstLinux VM under UnRaid? I would love to retire my home-pbx dedicated hardware and run this VM in my existing UnRaid setup. > > Thanks for your advise. > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Ionel C. <ion...@me...> - 2024-06-10 23:20:58
|
I am running two UnRaid NAS and they have a very rich ecosystems as far as dockers and VM goes. I was wondering if anyone managed to install and run an AstLinux VM under UnRaid? I would love to retire my home-pbx dedicated hardware and run this VM in my existing UnRaid setup. Thanks for your advise. |
|
From: Lonnie A. <li...@lo...> - 2024-05-30 19:10:57
|
Announcing AstLinux Release: 1.5.4 More Info: AstLinux Project https://www.astlinux-project.org/ AstLinux 1.5.4 Highlights: * Asterisk Versions: 16.30.0, 18.22.0, 20.7.0 * Linux Kernel 5.10.216, security and bug fixes * RUNNIX, version bump to runnix-0.6.18 * atlantic, enable the Marvell (Aquantia) 10-Gigabit Ethernet Network Driver (Aquantia AQC107/AQC113/etc. support) * r8125, version 9.013.02, Realtek RTL8125 2.5-Gigabit Ethernet Network Driver * libcurl (curl) version bump to 8.7.1, security fixes: CVE-2024-0853, CVE-2024-2004, CVE-2024-2379, CVE-2024-2398, CVE-2024-2466 * expat, version bump to 2.6.2, security fixes: CVE-2023-52425, CVE-2023-52426, CVE-2024-28757 * libxml2, version bump to 2.11.8, security fixes: CVE-2024-25062, CVE-2024-34459 * php, version 7.2.34, add security fixes: CVE-2024-2756, CVE-2024-3096 * sngrep, version bump to 1.8.1, security fix: CVE-2024-3120 * tinyproxy, version bump to 1.11.2, security fix: CVE-2023-49606 * unbound, version bump to 1.19.3, security fixes: CVE-2023-50387, CVE-2023-50868, CVE-2024-1931 * fping, version bump to 5.2 * htop, version bump to 3.3.0 * msmtp, version bump to 1.8.26 * sqlite, version bump to 3.45.3 * stunnel, version bump to 5.72 * vnStat, version bump to 2.12 * ca-certificates, update trusted root certificates 2024-03-11 * mac2vendor, oui.txt database snapshot 2024-05-22 * Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x "Legacy" version, built --without-pjproject and --without-dahdi * Package upgrades providing important security and bug fixes Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.4/docs/ChangeLog.txt All users are encouraged to upgrade, read the ChangeLog for the details. AstLinux Team |
|
From: Michael K. <li...@mk...> - 2024-03-22 14:16:25
|
Hi Peter, some things have changed between 16 and 18, there are now a few new modules, that have no config files. The 4 voicemail config changes could be adapted, but will still work as they are. > Am 22.03.2024 um 14:59 schrieb Dr. Peter Voigt <pv...@uo...>: > > Hi Lonnie, > > thanks, that trick helped - I'm now on > "astlinux-1.5.3 x86_64 - Asterisk 18.20.2". > > Good news: My simple configuration survived the upgrade: I can still make and receive phone calls, voicemals are still > accepted an sent by email. > > I am no Asterisk expert at all so need some advice on the remaining errors and warnings, full boot log: > > Mar 22 14:27:11] Asterisk 18.20.2 built by build @ build on a x86_64 running Linux on 2024-01-30 17:27:01 UTC > [Mar 22 14:27:11] NOTICE[534] loader.c: 349 modules will be loaded. > [Mar 22 14:27:13] NOTICE[534] res_odbc.c: Registered ODBC class 'asterisk' dsn->[asterisk] > [Mar 22 14:27:13] NOTICE[534] res_odbc.c: Registered ODBC class 'asterisk-cdr' dsn->[asterisk-cdr] > [Mar 22 14:27:13] NOTICE[534] cdr.c: CDR simple logging enabled. > [Mar 22 14:27:13] NOTICE[534] dnsmgr.c: Managed DNS entries will be refreshed every 30 seconds. > [Mar 22 14:27:13] NOTICE[534] indications.c: Default country for indication tones: us > [Mar 22 14:27:13] NOTICE[534] indications.c: Setting default indication country to 'us' > [Mar 22 14:27:14] WARNING[534] res_musiconhold.c: No music on hold classes configured, disabling music on hold. > [Mar 22 14:27:14] NOTICE[534] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener. > [Mar 22 14:27:14] WARNING[534] res_phoneprov.c: Unable to find a valid server address or name. > [Mar 22 14:27:14] ERROR[534] res_sorcery_config.c: Unable to load config file 'aeap.conf' > [Mar 22 14:27:14] NOTICE[534] chan_skinny.c: Configuring skinny from skinny.conf > [Mar 22 14:27:14] NOTICE[692] chan_sip.c: Peer '6003' is now Reachable. (28ms / 2000ms) > [Mar 22 14:27:14] NOTICE[534] chan_dahdi.c: Ignoring any changes to 'userbase' (on reload) at line 23. > [Mar 22 14:27:14] NOTICE[534] chan_dahdi.c: Ignoring any changes to 'vmsecret' (on reload) at line 31. > [Mar 22 14:27:14] NOTICE[534] chan_dahdi.c: Ignoring any changes to 'hassip' (on reload) at line 35. > [Mar 22 14:27:14] NOTICE[534] chan_dahdi.c: Ignoring any changes to 'hasiax' (on reload) at line 39. > [Mar 22 14:27:14] NOTICE[534] chan_dahdi.c: Ignoring any changes to 'hasmanager' (on reload) at line 47. > [Mar 22 14:27:14] NOTICE[692] chan_sip.c: Peer '6002' is now Reachable. (25ms / 2000ms) > [Mar 22 14:27:14] ERROR[534] ari/config.c: No configured users for ARI > [Mar 22 14:27:15] NOTICE[534] confbridge/conf_config_parser.c: Adding default_menu menu to app_confbridge > [Mar 22 14:27:15] NOTICE[692] chan_sip.c: Peer 'sipgate_de' is now Reachable. (31ms / 2000ms) > [Mar 22 14:27:15] NOTICE[692] chan_sip.c: Peer 'telekom' is now Reachable. (51ms / 2000ms) > [Mar 22 14:27:15] NOTICE[534] cel_custom.c: No mappings found in cel_custom.conf. Not logging CEL to custom CSVs. > [Mar 22 14:27:15] ERROR[534] config_options.c: Unable to load config file 'res_http_media_cache.conf' > [Mar 22 14:27:15] NOTICE[534] res_http_media_cache.c: Could not load res_http_media_cache config; using defaults > [Mar 22 14:27:16] ERROR[534] codec_dahdi.c: Failed to open /dev/dahdi/transcode: No such file or directory > [Mar 22 14:27:16] WARNING[534] app_voicemail.c: Setting 'maxmessage' has been deprecated in favor of 'maxsecs'. > [Mar 22 14:27:16] WARNING[534] app_voicemail.c: Setting 'minmessage' has been deprecated in favor of 'minsecs'. > [Mar 22 14:27:16] WARNING[534] app_voicemail.c: maxsilence should be less than minmessage or you may get empty messages > [Mar 22 14:27:16] WARNING[534] app_voicemail.c: Invalid max message greeting length > [Mar 22 14:27:16] WARNING[534] res_hep_rtcp.c: res_hep is disabled; declining module load > [Mar 22 14:27:16] ERROR[534] config_options.c: Unable to load config file 'prometheus.conf' > [Mar 22 14:27:16] WARNING[534] res_hep_pjsip.c: res_hep is disabled; declining module load > [Mar 22 14:27:16] WARNING[534] loader.c: Some non-required modules failed to load. > [Mar 22 14:27:17] ERROR[534] loader.c: res_pjsip_transport_websocket declined to load. > [Mar 22 14:27:17] ERROR[534] loader.c: cel_sqlite3_custom declined to load. > [Mar 22 14:27:17] ERROR[534] loader.c: cdr_sqlite3_custom declined to load. > [Mar 22 14:27:17] ERROR[534] loader.c: res_hep_rtcp declined to load. > [Mar 22 14:27:17] ERROR[534] loader.c: res_prometheus declined to load. > [Mar 22 14:27:17] ERROR[534] loader.c: res_hep_pjsip declined to load. > > I could fix: > loader.c: res_pjsip_transport_websocket declined to load. > by adding: > websocket_enabled = false > to /etc/asterisk/sip.conf [General] section. > > Peter > > > On Fri, 2024-03-22 at 07:52 -0500, Lonnie Abelbeck wrote: >> Hi Peter, >> >> What you need to do is first perform a "System tab -> "Revert to Previous" >> >> >> >> Then (no need to reboot) perform an "Upgrade with New". >> >> This will use your changed repository URL, and since the previous version is different from the latest it will allow >> the upgrade. >> >> Lonnie >> >> >> >>> On Mar 22, 2024, at 7:10 AM, Dr. Peter Voigt <pv...@uo...> wrote: >>> >>> Well, I have some time left and would like to upgrade to ast18. >>> >>> I am currently on 1.5.3 of ast16se. I've just changed the repository URL >>> from https://mirror.astlinux-project.org/ast16se-firmware-1.x >>> to https://mirror.astlinux-project.org/ast18-firmware-1.x >>> and checked for new firmware (System -> System Firmware Upgrade:). >>> However: "You are running the newest available version: astlinux-1.5.3". >>> >>> Can I upgrade the Asterisk version only, if there is also a new AstLinux release >>> available or what else might be wrong? >>> >>> Peter >>> >>> >>> On Fri, 2023-11-17 at 15:03 -0600, Lonnie Abelbeck wrote: >>>> +1 what Michael said ... my thoughts. >>>> >>>> Given, currently using ast16: >>>> >>>> 1) If currently using chan_pjsip, migrate to ast18. >>>> >>>> 2) If currently using dahdi (ex. pcie telephony card), migrate to ast18. >>>> >>>> 3) Else next step, change the "ast16" to "ast16se", ex. >>>> -- >>>> Prefs -> System & Staff Tab Options: Repository URL: >>>> https://mirror.astlinux-project.org/ast16se-firmware-1.x >>>> -- >>>> This should be quick and painless and will give you the latest security fixes >>>> in the packages with 1.5.2. >>>> >>>> 3a) Consider migrating to "ast18" when you have time to research the >>>> differences and testing. >>>> >>>> >>>> Additionally, it is recommended any "ast13se" systems be migrated to at least >>>> "ast16se". Relatively painless, but still requires some research and testing >>>> as with any version change of Asterisk. >>>> >>>> >>>> Lonnie >>>> >>>> >>>> >>>>> On Nov 17, 2023, at 12:21 PM, Dr. Peter Voigt <pv...@uo...> wrote: >>>>> >>>>> Hi Michael, >>>>> >>>>> thanks for feedback. I will try the upgrade to ast18 as soon as I've some >>>>> time >>>>> left necessary to deal with obviously arising error messages and required >>>>> configuration changes. May be I'll have to contact the list again, if >>>>> something >>>>> goes wrong. >>>>> >>>>> >>>>> On Fri, 2023-11-17 at 19:06 +0100, Michael Keuter wrote: >>>>>> Hi Peter, >>>>>> >>>>>> it is just a matter of changing the repository URL (you must run a lower >>>>>> version). >>>>>> >>>>>> I would suggest you choose ast18 cause Asterisk is EOL now. >>>>>> 20 is not well tested yet, it runs fine for me though. >>>>>> There was much changed between 16 and 18 (a few missing new config files >>>>>> => >>>>>> error messages.) >>>>>> The originals are in "/stat/etc/asterisk/". >>>>>> >>>>>>> Am 17.11.2023 um 18:21 schrieb Dr. Peter Voigt <pv...@uo...>: >>>>>>> >>>>>>> I am currently on the ast16 branch and ask myself, if I should switch to >>>>>>> ast16se >>>>>>> or to one of the higher version branches ast18/ast20. >>>>>>> >>>>>>> And another question: Is upgrading just a matter of changing the >>>>>>> repository >>>>>>> URL >>>>>>> according to >>>>>>> https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version >>>>>>> or will I have to adapt or re-create my Asterisk configuration? >>>>>>> >>>>>>> Regards, >>>>>>> Peter >>>>>>> >>>>>>> >>>>>>> On Thu, 2023-11-16 at 07:33 -0600, Lonnie Abelbeck wrote: >>>>>>>> Announcing AstLinux Release: 1.5.2 >>>>>>>> >>>>>>>> More Info: AstLinux Project >>>>>>>> https://www.astlinux-project.org/ >>>>>>>> >>>>>>>> Changes to supported firmware builds: >>>>>>>> * Previous 'ast13se' and 'ast16' firmware branches are no longer >>>>>>>> updated. >>>>>>>> * New 'ast16se' firmware branch, Asterisk 16.x built --without- >>>>>>>> pjproject >>>>>>>> and - >>>>>>>> -without-dahdi >>>>>>>> * Previous 'ast18' firmware branch, Asterisk 18.x built --with- >>>>>>>> pjproject >>>>>>>> and - >>>>>>>> -with-dahdi >>>>>>>> * New 'ast20' firmware branch, Asterisk 20.x built --with-pjproject >>>>>>>> and -- >>>>>>>> with-dahdi >>>>>>>> >>>>>>>> AstLinux 1.5.2 Highlights: >>>>>>>> * Asterisk Versions: 16.30.0, 18.20.0, 20.5.0 >>>>>>>> >>>>>>>> * Linux Kernel 5.10.197, security and bug fixes >>>>>>>> * RUNNIX, version bump to runnix-0.6.16 >>>>>>>> * OpenSSL, version bump to 1.1.1w, security fixes: CVE-2023-3446, CVE- >>>>>>>> 2023- >>>>>>>> 3817 >>>>>>>> * libcurl (curl) version bump to 8.4.0, security fixes: CVE-2023- >>>>>>>> 38039, >>>>>>>> CVE- >>>>>>>> 2023-38545, CVE-2023-38546 >>>>>>>> * LibreTLS, version bump to 3.8.1 >>>>>>>> * libpng, version bump to 1.6.40 >>>>>>>> * libsodium, version bump to 1.0.19 >>>>>>>> * libxml2, version bump to 2.11.5 >>>>>>>> * chrony, version bump to 4.4 >>>>>>>> * ne, version bump to 3.3.3 >>>>>>>> * msmtp, version bump to 1.8.25 >>>>>>>> * netsnmp, version bump to 5.9.4 >>>>>>>> * pjsip version bump to 2.13.1 >>>>>>>> * screen, version 4.9.1, security fix: CVE-2023-24626 >>>>>>>> * sqlite, version bump to 3.43.2 >>>>>>>> * sqliteodbc, version bump to 0.99991 >>>>>>>> * tiff, version bump to 4.6.0 >>>>>>>> * unbound, version bump to 1.18.0 >>>>>>>> * unixodbc, version bump to 2.3.12 >>>>>>>> * vnStat, version bump to 2.11 >>>>>>>> * zabbix, version bump to 4.0.50 >>>>>>>> * Asterisk '16se' (stable edition) version 16.30.0 is the last >>>>>>>> Asterisk >>>>>>>> 16.x >>>>>>>> "Legacy" version, built --without-pjproject and --without-dahdi >>>>>>>> * Package upgrades providing important security and bug fixes >>>>>>>> >>>>>>>> Full ChangeLog: >>>>>>>> https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.2/docs/ChangeLog.txt >>>>>>>> >>>>>>>> All users are encouraged to upgrade, read the ChangeLog for the >>>>>>>> details. >>>>>>>> >>>>>>>> AstLinux Team >>>>>> >>>>>> Michael >>>>>> >>>>>> http://www.mksolutions.info Michael http://www.mksolutions.info |
|
From: Dr. P. V. <pv...@uo...> - 2024-03-22 13:59:48
|
Hi Lonnie, thanks, that trick helped - I'm now on "astlinux-1.5.3 x86_64 - Asterisk 18.20.2". Good news: My simple configuration survived the upgrade: I can still make and receive phone calls, voicemals are still accepted an sent by email. I am no Asterisk expert at all so need some advice on the remaining errors and warnings, full boot log: Mar 22 14:27:11] Asterisk 18.20.2 built by build @ build on a x86_64 running Linux on 2024-01-30 17:27:01 UTC [Mar 22 14:27:11] NOTICE[534] loader.c: 349 modules will be loaded. [Mar 22 14:27:13] NOTICE[534] res_odbc.c: Registered ODBC class 'asterisk' dsn->[asterisk] [Mar 22 14:27:13] NOTICE[534] res_odbc.c: Registered ODBC class 'asterisk-cdr' dsn->[asterisk-cdr] [Mar 22 14:27:13] NOTICE[534] cdr.c: CDR simple logging enabled. [Mar 22 14:27:13] NOTICE[534] dnsmgr.c: Managed DNS entries will be refreshed every 30 seconds. [Mar 22 14:27:13] NOTICE[534] indications.c: Default country for indication tones: us [Mar 22 14:27:13] NOTICE[534] indications.c: Setting default indication country to 'us' [Mar 22 14:27:14] WARNING[534] res_musiconhold.c: No music on hold classes configured, disabling music on hold. [Mar 22 14:27:14] NOTICE[534] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener. [Mar 22 14:27:14] WARNING[534] res_phoneprov.c: Unable to find a valid server address or name. [Mar 22 14:27:14] ERROR[534] res_sorcery_config.c: Unable to load config file 'aeap.conf' [Mar 22 14:27:14] NOTICE[534] chan_skinny.c: Configuring skinny from skinny.conf [Mar 22 14:27:14] NOTICE[692] chan_sip.c: Peer '6003' is now Reachable. (28ms / 2000ms) [Mar 22 14:27:14] NOTICE[534] chan_dahdi.c: Ignoring any changes to 'userbase' (on reload) at line 23. [Mar 22 14:27:14] NOTICE[534] chan_dahdi.c: Ignoring any changes to 'vmsecret' (on reload) at line 31. [Mar 22 14:27:14] NOTICE[534] chan_dahdi.c: Ignoring any changes to 'hassip' (on reload) at line 35. [Mar 22 14:27:14] NOTICE[534] chan_dahdi.c: Ignoring any changes to 'hasiax' (on reload) at line 39. [Mar 22 14:27:14] NOTICE[534] chan_dahdi.c: Ignoring any changes to 'hasmanager' (on reload) at line 47. [Mar 22 14:27:14] NOTICE[692] chan_sip.c: Peer '6002' is now Reachable. (25ms / 2000ms) [Mar 22 14:27:14] ERROR[534] ari/config.c: No configured users for ARI [Mar 22 14:27:15] NOTICE[534] confbridge/conf_config_parser.c: Adding default_menu menu to app_confbridge [Mar 22 14:27:15] NOTICE[692] chan_sip.c: Peer 'sipgate_de' is now Reachable. (31ms / 2000ms) [Mar 22 14:27:15] NOTICE[692] chan_sip.c: Peer 'telekom' is now Reachable. (51ms / 2000ms) [Mar 22 14:27:15] NOTICE[534] cel_custom.c: No mappings found in cel_custom.conf. Not logging CEL to custom CSVs. [Mar 22 14:27:15] ERROR[534] config_options.c: Unable to load config file 'res_http_media_cache.conf' [Mar 22 14:27:15] NOTICE[534] res_http_media_cache.c: Could not load res_http_media_cache config; using defaults [Mar 22 14:27:16] ERROR[534] codec_dahdi.c: Failed to open /dev/dahdi/transcode: No such file or directory [Mar 22 14:27:16] WARNING[534] app_voicemail.c: Setting 'maxmessage' has been deprecated in favor of 'maxsecs'. [Mar 22 14:27:16] WARNING[534] app_voicemail.c: Setting 'minmessage' has been deprecated in favor of 'minsecs'. [Mar 22 14:27:16] WARNING[534] app_voicemail.c: maxsilence should be less than minmessage or you may get empty messages [Mar 22 14:27:16] WARNING[534] app_voicemail.c: Invalid max message greeting length [Mar 22 14:27:16] WARNING[534] res_hep_rtcp.c: res_hep is disabled; declining module load [Mar 22 14:27:16] ERROR[534] config_options.c: Unable to load config file 'prometheus.conf' [Mar 22 14:27:16] WARNING[534] res_hep_pjsip.c: res_hep is disabled; declining module load [Mar 22 14:27:16] WARNING[534] loader.c: Some non-required modules failed to load. [Mar 22 14:27:17] ERROR[534] loader.c: res_pjsip_transport_websocket declined to load. [Mar 22 14:27:17] ERROR[534] loader.c: cel_sqlite3_custom declined to load. [Mar 22 14:27:17] ERROR[534] loader.c: cdr_sqlite3_custom declined to load. [Mar 22 14:27:17] ERROR[534] loader.c: res_hep_rtcp declined to load. [Mar 22 14:27:17] ERROR[534] loader.c: res_prometheus declined to load. [Mar 22 14:27:17] ERROR[534] loader.c: res_hep_pjsip declined to load. I could fix: loader.c: res_pjsip_transport_websocket declined to load. by adding: websocket_enabled = false to /etc/asterisk/sip.conf [General] section. Peter On Fri, 2024-03-22 at 07:52 -0500, Lonnie Abelbeck wrote: > Hi Peter, > > What you need to do is first perform a "System tab -> "Revert to Previous" > > > > Then (no need to reboot) perform an "Upgrade with New". > > This will use your changed repository URL, and since the previous version is different from the latest it will allow > the upgrade. > > Lonnie > > > > > On Mar 22, 2024, at 7:10 AM, Dr. Peter Voigt <pv...@uo...> wrote: > > > > Well, I have some time left and would like to upgrade to ast18. > > > > I am currently on 1.5.3 of ast16se. I've just changed the repository URL > > from https://mirror.astlinux-project.org/ast16se-firmware-1.x > > to https://mirror.astlinux-project.org/ast18-firmware-1.x > > and checked for new firmware (System -> System Firmware Upgrade:). > > However: "You are running the newest available version: astlinux-1.5.3". > > > > Can I upgrade the Asterisk version only, if there is also a new AstLinux release > > available or what else might be wrong? > > > > Peter > > > > > > On Fri, 2023-11-17 at 15:03 -0600, Lonnie Abelbeck wrote: > > > +1 what Michael said ... my thoughts. > > > > > > Given, currently using ast16: > > > > > > 1) If currently using chan_pjsip, migrate to ast18. > > > > > > 2) If currently using dahdi (ex. pcie telephony card), migrate to ast18. > > > > > > 3) Else next step, change the "ast16" to "ast16se", ex. > > > -- > > > Prefs -> System & Staff Tab Options: Repository URL: > > > https://mirror.astlinux-project.org/ast16se-firmware-1.x > > > -- > > > This should be quick and painless and will give you the latest security fixes > > > in the packages with 1.5.2. > > > > > > 3a) Consider migrating to "ast18" when you have time to research the > > > differences and testing. > > > > > > > > > Additionally, it is recommended any "ast13se" systems be migrated to at least > > > "ast16se". Relatively painless, but still requires some research and testing > > > as with any version change of Asterisk. > > > > > > > > > Lonnie > > > > > > > > > > > > > On Nov 17, 2023, at 12:21 PM, Dr. Peter Voigt <pv...@uo...> wrote: > > > > > > > > Hi Michael, > > > > > > > > thanks for feedback. I will try the upgrade to ast18 as soon as I've some > > > > time > > > > left necessary to deal with obviously arising error messages and required > > > > configuration changes. May be I'll have to contact the list again, if > > > > something > > > > goes wrong. > > > > > > > > > > > > On Fri, 2023-11-17 at 19:06 +0100, Michael Keuter wrote: > > > > > Hi Peter, > > > > > > > > > > it is just a matter of changing the repository URL (you must run a lower > > > > > version). > > > > > > > > > > I would suggest you choose ast18 cause Asterisk is EOL now. > > > > > 20 is not well tested yet, it runs fine for me though. > > > > > There was much changed between 16 and 18 (a few missing new config files > > > > > => > > > > > error messages.) > > > > > The originals are in "/stat/etc/asterisk/". > > > > > > > > > > > Am 17.11.2023 um 18:21 schrieb Dr. Peter Voigt <pv...@uo...>: > > > > > > > > > > > > I am currently on the ast16 branch and ask myself, if I should switch to > > > > > > ast16se > > > > > > or to one of the higher version branches ast18/ast20. > > > > > > > > > > > > And another question: Is upgrading just a matter of changing the > > > > > > repository > > > > > > URL > > > > > > according to > > > > > > https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version > > > > > > or will I have to adapt or re-create my Asterisk configuration? > > > > > > > > > > > > Regards, > > > > > > Peter > > > > > > > > > > > > > > > > > > On Thu, 2023-11-16 at 07:33 -0600, Lonnie Abelbeck wrote: > > > > > > > Announcing AstLinux Release: 1.5.2 > > > > > > > > > > > > > > More Info: AstLinux Project > > > > > > > https://www.astlinux-project.org/ > > > > > > > > > > > > > > Changes to supported firmware builds: > > > > > > > * Previous 'ast13se' and 'ast16' firmware branches are no longer > > > > > > > updated. > > > > > > > * New 'ast16se' firmware branch, Asterisk 16.x built --without- > > > > > > > pjproject > > > > > > > and - > > > > > > > -without-dahdi > > > > > > > * Previous 'ast18' firmware branch, Asterisk 18.x built --with- > > > > > > > pjproject > > > > > > > and - > > > > > > > -with-dahdi > > > > > > > * New 'ast20' firmware branch, Asterisk 20.x built --with-pjproject > > > > > > > and -- > > > > > > > with-dahdi > > > > > > > > > > > > > > AstLinux 1.5.2 Highlights: > > > > > > > * Asterisk Versions: 16.30.0, 18.20.0, 20.5.0 > > > > > > > > > > > > > > * Linux Kernel 5.10.197, security and bug fixes > > > > > > > * RUNNIX, version bump to runnix-0.6.16 > > > > > > > * OpenSSL, version bump to 1.1.1w, security fixes: CVE-2023-3446, CVE- > > > > > > > 2023- > > > > > > > 3817 > > > > > > > * libcurl (curl) version bump to 8.4.0, security fixes: CVE-2023- > > > > > > > 38039, > > > > > > > CVE- > > > > > > > 2023-38545, CVE-2023-38546 > > > > > > > * LibreTLS, version bump to 3.8.1 > > > > > > > * libpng, version bump to 1.6.40 > > > > > > > * libsodium, version bump to 1.0.19 > > > > > > > * libxml2, version bump to 2.11.5 > > > > > > > * chrony, version bump to 4.4 > > > > > > > * ne, version bump to 3.3.3 > > > > > > > * msmtp, version bump to 1.8.25 > > > > > > > * netsnmp, version bump to 5.9.4 > > > > > > > * pjsip version bump to 2.13.1 > > > > > > > * screen, version 4.9.1, security fix: CVE-2023-24626 > > > > > > > * sqlite, version bump to 3.43.2 > > > > > > > * sqliteodbc, version bump to 0.99991 > > > > > > > * tiff, version bump to 4.6.0 > > > > > > > * unbound, version bump to 1.18.0 > > > > > > > * unixodbc, version bump to 2.3.12 > > > > > > > * vnStat, version bump to 2.11 > > > > > > > * zabbix, version bump to 4.0.50 > > > > > > > * Asterisk '16se' (stable edition) version 16.30.0 is the last > > > > > > > Asterisk > > > > > > > 16.x > > > > > > > "Legacy" version, built --without-pjproject and --without-dahdi > > > > > > > * Package upgrades providing important security and bug fixes > > > > > > > > > > > > > > Full ChangeLog: > > > > > > > https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.2/docs/ChangeLog.txt > > > > > > > > > > > > > > All users are encouraged to upgrade, read the ChangeLog for the > > > > > > > details. > > > > > > > > > > > > > > AstLinux Team > > > > > > > > > > Michael > > > > > > > > > > http://www.mksolutions.info > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Astlinux-users mailing list > > > > > Ast...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > > > > > > > Donations to support AstLinux are graciously accepted via PayPal to > > > > > pa...@kr.... > > > > > > > > > > > > _______________________________________________ > > > > Astlinux-users mailing list > > > > Ast...@li... > > > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > > > > > Donations to support AstLinux are graciously accepted via PayPal to > > > > pa...@kr.... > > > > > > > > > > > > _______________________________________________ > > > Astlinux-users mailing list > > > Ast...@li... > > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > > > Donations to support AstLinux are graciously accepted via PayPal to > > > pa...@kr.... > > > > > > _______________________________________________ > > Astlinux-users mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2024-03-22 12:52:18
|
Hi Peter, What you need to do is first perform a "System tab -> "Revert to Previous" |
|
From: Dr. P. V. <pv...@uo...> - 2024-03-22 12:38:14
|
Well, I have some time left and would like to upgrade to ast18. I am currently on 1.5.3 of ast16se. I've just changed the repository URL from https://mirror.astlinux-project.org/ast16se-firmware-1.x to https://mirror.astlinux-project.org/ast18-firmware-1.x and checked for new firmware (System -> System Firmware Upgrade:). However: "You are running the newest available version: astlinux-1.5.3". Can I upgrade the Asterisk version only, if there is also a new AstLinux release available or what else might be wrong? Peter On Fri, 2023-11-17 at 15:03 -0600, Lonnie Abelbeck wrote: > +1 what Michael said ... my thoughts. > > Given, currently using ast16: > > 1) If currently using chan_pjsip, migrate to ast18. > > 2) If currently using dahdi (ex. pcie telephony card), migrate to ast18. > > 3) Else next step, change the "ast16" to "ast16se", ex. > -- > Prefs -> System & Staff Tab Options: Repository URL: > https://mirror.astlinux-project.org/ast16se-firmware-1.x > -- > This should be quick and painless and will give you the latest security fixes > in the packages with 1.5.2. > > 3a) Consider migrating to "ast18" when you have time to research the > differences and testing. > > > Additionally, it is recommended any "ast13se" systems be migrated to at least > "ast16se". Relatively painless, but still requires some research and testing > as with any version change of Asterisk. > > > Lonnie > > > > > On Nov 17, 2023, at 12:21 PM, Dr. Peter Voigt <pv...@uo...> wrote: > > > > Hi Michael, > > > > thanks for feedback. I will try the upgrade to ast18 as soon as I've some > > time > > left necessary to deal with obviously arising error messages and required > > configuration changes. May be I'll have to contact the list again, if > > something > > goes wrong. > > > > > > On Fri, 2023-11-17 at 19:06 +0100, Michael Keuter wrote: > > > Hi Peter, > > > > > > it is just a matter of changing the repository URL (you must run a lower > > > version). > > > > > > I would suggest you choose ast18 cause Asterisk is EOL now. > > > 20 is not well tested yet, it runs fine for me though. > > > There was much changed between 16 and 18 (a few missing new config files > > > => > > > error messages.) > > > The originals are in "/stat/etc/asterisk/". > > > > > > > Am 17.11.2023 um 18:21 schrieb Dr. Peter Voigt <pv...@uo...>: > > > > > > > > I am currently on the ast16 branch and ask myself, if I should switch to > > > > ast16se > > > > or to one of the higher version branches ast18/ast20. > > > > > > > > And another question: Is upgrading just a matter of changing the > > > > repository > > > > URL > > > > according to > > > > https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version > > > > or will I have to adapt or re-create my Asterisk configuration? > > > > > > > > Regards, > > > > Peter > > > > > > > > > > > > On Thu, 2023-11-16 at 07:33 -0600, Lonnie Abelbeck wrote: > > > > > Announcing AstLinux Release: 1.5.2 > > > > > > > > > > More Info: AstLinux Project > > > > > https://www.astlinux-project.org/ > > > > > > > > > > Changes to supported firmware builds: > > > > > * Previous 'ast13se' and 'ast16' firmware branches are no longer > > > > > updated. > > > > > * New 'ast16se' firmware branch, Asterisk 16.x built --without- > > > > > pjproject > > > > > and - > > > > > -without-dahdi > > > > > * Previous 'ast18' firmware branch, Asterisk 18.x built --with- > > > > > pjproject > > > > > and - > > > > > -with-dahdi > > > > > * New 'ast20' firmware branch, Asterisk 20.x built --with-pjproject > > > > > and -- > > > > > with-dahdi > > > > > > > > > > AstLinux 1.5.2 Highlights: > > > > > * Asterisk Versions: 16.30.0, 18.20.0, 20.5.0 > > > > > > > > > > * Linux Kernel 5.10.197, security and bug fixes > > > > > * RUNNIX, version bump to runnix-0.6.16 > > > > > * OpenSSL, version bump to 1.1.1w, security fixes: CVE-2023-3446, CVE- > > > > > 2023- > > > > > 3817 > > > > > * libcurl (curl) version bump to 8.4.0, security fixes: CVE-2023- > > > > > 38039, > > > > > CVE- > > > > > 2023-38545, CVE-2023-38546 > > > > > * LibreTLS, version bump to 3.8.1 > > > > > * libpng, version bump to 1.6.40 > > > > > * libsodium, version bump to 1.0.19 > > > > > * libxml2, version bump to 2.11.5 > > > > > * chrony, version bump to 4.4 > > > > > * ne, version bump to 3.3.3 > > > > > * msmtp, version bump to 1.8.25 > > > > > * netsnmp, version bump to 5.9.4 > > > > > * pjsip version bump to 2.13.1 > > > > > * screen, version 4.9.1, security fix: CVE-2023-24626 > > > > > * sqlite, version bump to 3.43.2 > > > > > * sqliteodbc, version bump to 0.99991 > > > > > * tiff, version bump to 4.6.0 > > > > > * unbound, version bump to 1.18.0 > > > > > * unixodbc, version bump to 2.3.12 > > > > > * vnStat, version bump to 2.11 > > > > > * zabbix, version bump to 4.0.50 > > > > > * Asterisk '16se' (stable edition) version 16.30.0 is the last > > > > > Asterisk > > > > > 16.x > > > > > "Legacy" version, built --without-pjproject and --without-dahdi > > > > > * Package upgrades providing important security and bug fixes > > > > > > > > > > Full ChangeLog: > > > > > https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.2/docs/ChangeLog.txt > > > > > > > > > > All users are encouraged to upgrade, read the ChangeLog for the > > > > > details. > > > > > > > > > > AstLinux Team > > > > > > Michael > > > > > > http://www.mksolutions.info > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Astlinux-users mailing list > > > Ast...@li... > > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > > > Donations to support AstLinux are graciously accepted via PayPal to > > > pa...@kr.... > > > > > > _______________________________________________ > > Astlinux-users mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > Donations to support AstLinux are graciously accepted via PayPal to > > pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2024-03-18 02:00:37
|
Thanks all for responding. Sorry I changed my email setup so I missed these responses. Yes I have decided to not continue trying to get things working with Unifi Gateways and Astlinux until they have Wireguard Site to Site VPN. Yes the GL.Inet boxes seem to work quite well however I'm thinking I will try the Teltonika RUT300 as we already have these as part of our product portfolio: https://teltonika-networks.com/products/routers/rut300 Im also using Netgate 1100 (pfSense) which also work great. Awesome to have a number of options. Regards Michael Knill ________________________________ From: Ionel Chila via Astlinux-users <ast...@li...> Sent: Friday, 8 March 2024 12:56 AM To: AstLinux Users Mailing List <ast...@li...> Cc: Ionel Chila <ion...@me...> Subject: Re: [Astlinux-users] Ubiquiti Unifi I use Unifi UDM-SE for VPN with Gl.inet routers and WireGuard. Works very consistent and reliable. > On Mar 7, 2024, at 6:20 AM, Michael Keuter <li...@mk...> wrote: > > Hi Michael, > > I only used StrongSwan with the AVM Fritzbox router/DSL modem models, which are widely used in Germany. You'll have to create a textfile, which has to be imported into the Fritzbox via the WebGUI. > > Luckily the newer Fritzbox models now support WireGuard. Never used Unifi for VPN. I thought you wanted to use Gl.inet routers … > > Michael > > http://www.mksolutions.info > >> Am 07.03.2024 um 12:52 schrieb Lonnie Abelbeck <li...@lo...>: >> >> Hi Michael, >> >> Unifi access points and switches have played well with others over the years. >> >> Unifi routing products, while based on linux, never had a good track record of interoperability, particularly with VPNs. >> >> It would seem straightforward for Unifi to support sourcing manual Wireguard configs in addition to the pretty GUI Wireguard configs ... maybe someday. >> >> Personally, I would not even try to get AstLinux Strongswan to work with Unifi's IPsec. >> >> Lonnie >> >> >> >>> On Mar 7, 2024, at 12:17 AM, Michael Knill <mic...@ip...> wrote: >>> >>> Noone 🙁 >>> >>> Regards >>> Michael Knill >>> From: Michael Knill <mic...@ip...> >>> Sent: Friday, 23 February 2024 2:50 PM >>> To: AstLinux List (ast...@li...) <ast...@li...> >>> Subject: [Astlinux-users] Ubiquiti Unifi >>> >>> Im kicking and screaming all the way, but I will probably be moving to the Ubiquiti Unifi ecosystem (we already use their WAP’s). >>> As part of this, I will be implementing some of their gateways (routers) which I really need to connect via VPN to Astlinux in the cloud. >>> They now support Wireguard but only as a client or server and not as a site to site VPN which they support Open VPN and IPsec only. In the Wireguard client configuration they emulate a mobile client so all traffic is from the gateway address (NAT). >>> >>> So just wondering if Im going to be able to get this working with OpenVPN as per below: >>> >>> <image002.png> >>> >>> Looks like it only support Pre-Shared Key and not certificates? >>> >>> Could probably use Strongswan with IPsec but would rather not unless someone has got this working or something similar. >>> >>> Regards >>> >>> Michael Knill >>> Managing Director >>> >>> D: +61 2 6189 1360 >>> P: +61 2 6140 4656 >>> E: mic...@ip... >>> W: ipcsolutions.com.au >>> >>> <image001.png> >>> Smarter Business Communications > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Ionel C. <ion...@me...> - 2024-03-07 14:13:07
|
I use Unifi UDM-SE for VPN with Gl.inet routers and WireGuard. Works very consistent and reliable. > On Mar 7, 2024, at 6:20 AM, Michael Keuter <li...@mk...> wrote: > > Hi Michael, > > I only used StrongSwan with the AVM Fritzbox router/DSL modem models, which are widely used in Germany. You'll have to create a textfile, which has to be imported into the Fritzbox via the WebGUI. > > Luckily the newer Fritzbox models now support WireGuard. Never used Unifi for VPN. I thought you wanted to use Gl.inet routers … > > Michael > > http://www.mksolutions.info > >> Am 07.03.2024 um 12:52 schrieb Lonnie Abelbeck <li...@lo...>: >> >> Hi Michael, >> >> Unifi access points and switches have played well with others over the years. >> >> Unifi routing products, while based on linux, never had a good track record of interoperability, particularly with VPNs. >> >> It would seem straightforward for Unifi to support sourcing manual Wireguard configs in addition to the pretty GUI Wireguard configs ... maybe someday. >> >> Personally, I would not even try to get AstLinux Strongswan to work with Unifi's IPsec. >> >> Lonnie >> >> >> >>> On Mar 7, 2024, at 12:17 AM, Michael Knill <mic...@ip...> wrote: >>> >>> Noone 🙁 >>> >>> Regards >>> Michael Knill >>> From: Michael Knill <mic...@ip...> >>> Sent: Friday, 23 February 2024 2:50 PM >>> To: AstLinux List (ast...@li...) <ast...@li...> >>> Subject: [Astlinux-users] Ubiquiti Unifi >>> >>> Im kicking and screaming all the way, but I will probably be moving to the Ubiquiti Unifi ecosystem (we already use their WAP’s). >>> As part of this, I will be implementing some of their gateways (routers) which I really need to connect via VPN to Astlinux in the cloud. >>> They now support Wireguard but only as a client or server and not as a site to site VPN which they support Open VPN and IPsec only. In the Wireguard client configuration they emulate a mobile client so all traffic is from the gateway address (NAT). >>> >>> So just wondering if Im going to be able to get this working with OpenVPN as per below: >>> >>> <image002.png> >>> >>> Looks like it only support Pre-Shared Key and not certificates? >>> >>> Could probably use Strongswan with IPsec but would rather not unless someone has got this working or something similar. >>> >>> Regards >>> >>> Michael Knill >>> Managing Director >>> >>> D: +61 2 6189 1360 >>> P: +61 2 6140 4656 >>> E: mic...@ip... >>> W: ipcsolutions.com.au >>> >>> <image001.png> >>> Smarter Business Communications > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <li...@mk...> - 2024-03-07 12:21:13
|
Hi Michael, I only used StrongSwan with the AVM Fritzbox router/DSL modem models, which are widely used in Germany. You'll have to create a textfile, which has to be imported into the Fritzbox via the WebGUI. Luckily the newer Fritzbox models now support WireGuard. Never used Unifi for VPN. I thought you wanted to use Gl.inet routers … Michael http://www.mksolutions.info > Am 07.03.2024 um 12:52 schrieb Lonnie Abelbeck <li...@lo...>: > > Hi Michael, > > Unifi access points and switches have played well with others over the years. > > Unifi routing products, while based on linux, never had a good track record of interoperability, particularly with VPNs. > > It would seem straightforward for Unifi to support sourcing manual Wireguard configs in addition to the pretty GUI Wireguard configs ... maybe someday. > > Personally, I would not even try to get AstLinux Strongswan to work with Unifi's IPsec. > > Lonnie > > > >> On Mar 7, 2024, at 12:17 AM, Michael Knill <mic...@ip...> wrote: >> >> Noone 🙁 >> >> Regards >> Michael Knill >> From: Michael Knill <mic...@ip...> >> Sent: Friday, 23 February 2024 2:50 PM >> To: AstLinux List (ast...@li...) <ast...@li...> >> Subject: [Astlinux-users] Ubiquiti Unifi >> >> Im kicking and screaming all the way, but I will probably be moving to the Ubiquiti Unifi ecosystem (we already use their WAP’s). >> As part of this, I will be implementing some of their gateways (routers) which I really need to connect via VPN to Astlinux in the cloud. >> They now support Wireguard but only as a client or server and not as a site to site VPN which they support Open VPN and IPsec only. In the Wireguard client configuration they emulate a mobile client so all traffic is from the gateway address (NAT). >> >> So just wondering if Im going to be able to get this working with OpenVPN as per below: >> >> <image002.png> >> >> Looks like it only support Pre-Shared Key and not certificates? >> >> Could probably use Strongswan with IPsec but would rather not unless someone has got this working or something similar. >> >> Regards >> >> Michael Knill >> Managing Director >> >> D: +61 2 6189 1360 >> P: +61 2 6140 4656 >> E: mic...@ip... >> W: ipcsolutions.com.au >> >> <image001.png> >> Smarter Business Communications |
|
From: Lonnie A. <li...@lo...> - 2024-03-07 11:52:34
|
Hi Michael, Unifi access points and switches have played well with others over the years. Unifi routing products, while based on linux, never had a good track record of interoperability, particularly with VPNs. It would seem straightforward for Unifi to support sourcing manual Wireguard configs in addition to the pretty GUI Wireguard configs ... maybe someday. Personally, I would not even try to get AstLinux Strongswan to work with Unifi's IPsec. Lonnie > On Mar 7, 2024, at 12:17 AM, Michael Knill <mic...@ip...> wrote: > > Noone 🙁 > > Regards > Michael Knill > From: Michael Knill <mic...@ip...> > Sent: Friday, 23 February 2024 2:50 PM > To: AstLinux List (ast...@li...) <ast...@li...> > Subject: [Astlinux-users] Ubiquiti Unifi > > Im kicking and screaming all the way, but I will probably be moving to the Ubiquiti Unifi ecosystem (we already use their WAP’s). > As part of this, I will be implementing some of their gateways (routers) which I really need to connect via VPN to Astlinux in the cloud. > They now support Wireguard but only as a client or server and not as a site to site VPN which they support Open VPN and IPsec only. In the Wireguard client configuration they emulate a mobile client so all traffic is from the gateway address (NAT). > > So just wondering if Im going to be able to get this working with OpenVPN as per below: > > <image002.png> > > Looks like it only support Pre-Shared Key and not certificates? > > Could probably use Strongswan with IPsec but would rather not unless someone has got this working or something similar. > > Regards > > Michael Knill > Managing Director > > D: +61 2 6189 1360 > P: +61 2 6140 4656 > E: mic...@ip... > W: ipcsolutions.com.au > > <image001.png> > Smarter Business Communications > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2024-03-07 06:50:00
|
Noone 🙁 Regards Michael Knill ________________________________ From: Michael Knill <mic...@ip...> Sent: Friday, 23 February 2024 2:50 PM To: AstLinux List (ast...@li...) <ast...@li...> Subject: [Astlinux-users] Ubiquiti Unifi Im kicking and screaming all the way, but I will probably be moving to the Ubiquiti Unifi ecosystem (we already use their WAP’s). As part of this, I will be implementing some of their gateways (routers) which I really need to connect via VPN to Astlinux in the cloud. They now support Wireguard but only as a client or server and not as a site to site VPN which they support Open VPN and IPsec only. In the Wireguard client configuration they emulate a mobile client so all traffic is from the gateway address (NAT). So just wondering if Im going to be able to get this working with OpenVPN as per below: [cid:image002.png@01DA6666.E9951590] Looks like it only support Pre-Shared Key and not certificates? Could probably use Strongswan with IPsec but would rather not unless someone has got this working or something similar. Regards Michael Knill Managing Director D: +61 2 6189 1360<tel:+61261891360> P: +61 2 6140 4656<tel:+61261404656> E: mic...@ip...<mailto:mic...@ip...> W: ipcsolutions.com.au<https://ipcsolutions.com.au/> [Icon Description automatically generated] Smarter Business Communications |
|
From: Michael K. <mic...@ip...> - 2024-02-23 03:50:37
|
Im kicking and screaming all the way, but I will probably be moving to the Ubiquiti Unifi ecosystem (we already use their WAP’s). As part of this, I will be implementing some of their gateways (routers) which I really need to connect via VPN to Astlinux in the cloud. They now support Wireguard but only as a client or server and not as a site to site VPN which they support Open VPN and IPsec only. In the Wireguard client configuration they emulate a mobile client so all traffic is from the gateway address (NAT). So just wondering if Im going to be able to get this working with OpenVPN as per below: [cid:image002.png@01DA6666.E9951590] Looks like it only support Pre-Shared Key and not certificates? Could probably use Strongswan with IPsec but would rather not unless someone has got this working or something similar. Regards Michael Knill Managing Director D: +61 2 6189 1360<tel:+61261891360> P: +61 2 6140 4656<tel:+61261404656> E: mic...@ip...<mailto:mic...@ip...> W: ipcsolutions.com.au<https://ipcsolutions.com.au/> [Icon Description automatically generated] Smarter Business Communications |
|
From: Michael K. <mic...@ip...> - 2024-02-23 03:13:37
|
Whoops I was wrong. It doesn’t seem that we’re generating two certs rather we are just adding multiple domains to the same cert. The commands we use are (after adding the DNS entries): acme-client --issue --dns dns_acmedns -d <access ID>.myportal.tel -d <access ID>.ipcaccess.net acme-client --deploy --deploy-hook astlinux -d <access ID>.myportal.tel -d <access ID>.ipcaccess.net I think we will just leave it to see if it happens again. Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Date: Friday, 23 February 2024 at 8:50 am To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] Asterisk appeared to crash after ACME deploy > I recall having a case where acme.sh generated two certs and the deploy script was called for the second cert, but asterisk was not done starting up and something similar happened. To be more clear, "asterisk was not done starting up" from deploying the first certificate and then tried to deploy again for the second certificate. Lonnie > On Feb 22, 2024, at 3:37 PM, Lonnie Abelbeck <li...@lo...> wrote: > > Hi Michael, > > I had my Jetway NF9HG-2930 die a year or so ago, I know Michael Keuter had a couple NF9HG-2930s die. Though in my case it would not power up anymore. > > This case does seem to be different. > > Hmmm, is your ACME only a single domain (cert)? > > I recall having a case where acme.sh generated two certs and the deploy script was called for the second cert, but asterisk was not done starting up and something similar happened. > > Lonnie > > > > > >> On Feb 22, 2024, at 2:39 PM, Michael Knill <mic...@ip...> wrote: >> >> Running version 1.5.0 on Jetway NF9HG-2930. >> >> ------------------- >> Feb 22 23:00:42 30390_Ortho-ACT_CM1 daemon.err lighttpd[30995]: (server.c.2029) server stopped by UID = 0 PID = 7065 >> Feb 22 23:00:43 30390_Ortho-ACT_CM1 daemon.err lighttpd[7087]: (server.c.1436) server started (lighttpd/1.4.51) >> Feb 22 23:00:43 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for HTTPS and 'lighttpd' restarted >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for SIP-TLS and 'asterisk' restart when convenient requested >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: astobj2_container.c:492 in ao2_iterator_init: FRACK!, Failed assertion user_data is NULL (0) >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: :0 in : Got 11 backtrace records # 0: /usr/sbin/asterisk(__ao2_ref+0x5de) [0x46213e] # 1: /usr/sbin/asterisk(ao2_iterator_init+0x2f) [0x464a1f] # 2: /usr/lib/asterisk/modules/app_queue.so(+0xef4d) [0x14f159681f4d] # 3: /usr/sbin/asterisk() [0x51849e] # 4: /usr/sbin/asterisk() [0x5206a4] # 5: /usr/sbin/asterisk() [0x573c60] # 6: /usr/sbin/asterisk(ast_taskprocessor_execute+0x16f) [0x591f0f] # 7: /usr/sbin/asterisk() [0x591fb0] # 8: /usr/sbin/asterisk() [0x >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: app_queue.c:2823 in extension_state_cb: FRACK!, Failed assertion user_data is NULL (0) >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: :0 in : Got 11 backtrace records # 0: /usr/sbin/asterisk() [0x461502] # 1: /usr/sbin/asterisk(__ao2_iterator_next+0x1d8) [0x464e28] # 2: /usr/lib/asterisk/modules/app_queue.so(+0xef9c) [0x14f159681f9c] # 3: /usr/sbin/asterisk() [0x51849e] # 4: /usr/sbin/asterisk() [0x5206a4] # 5: /usr/sbin/asterisk() [0x573c60] # 6: /usr/sbin/asterisk(ast_taskprocessor_execute+0x16f) [0x591f0f] # 7: /usr/sbin/asterisk() [0x591fb0] # 8: /usr/sbin/asterisk() [0x5a0c5a] # 9: >> >> ……. more of the same ……... >> >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.info kernel: asterisk[31178]: segfault at 58 ip 00000000004f4da0 sp 000014f15a55ba58 error 4 in asterisk[43d000+1d6000] >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.info kernel: Code: c0 74 1f 85 f6 74 1b 89 f2 48 39 d0 72 14 48 8b 47 68 48 63 f6 48 8b 44 f0 f8 c3 0f 1f 80 00 00 00 00 31 c0 c3 0f 1f 44 00 00 <48> 8b 47 58 c3 66 66 2e 0f 1f 84 00 00 00 00 00 49 89 f9 41 b8 af >> Feb 22 23:00:45 30390_Ortho-ACT_CM1 user.info safe_asterisk: Asterisk exited on signal 11. >> Feb 22 23:00:45 30390_Ortho-ACT_CM1 user.info safe_asterisk: Automatically restarting Asterisk. >> Feb 22 23:00:46 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for XMPP and 'prosody' restarted >> ------------------- >> >> Im thinking of putting this one in the cloud as this box has been there for a while, but wondering if this is a bug or something else? I cant recall seeing it before. >> >> Thanks >> Michael Knill >> >> >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2024-02-22 21:50:31
|
> I recall having a case where acme.sh generated two certs and the deploy script was called for the second cert, but asterisk was not done starting up and something similar happened. To be more clear, "asterisk was not done starting up" from deploying the first certificate and then tried to deploy again for the second certificate. Lonnie > On Feb 22, 2024, at 3:37 PM, Lonnie Abelbeck <li...@lo...> wrote: > > Hi Michael, > > I had my Jetway NF9HG-2930 die a year or so ago, I know Michael Keuter had a couple NF9HG-2930s die. Though in my case it would not power up anymore. > > This case does seem to be different. > > Hmmm, is your ACME only a single domain (cert)? > > I recall having a case where acme.sh generated two certs and the deploy script was called for the second cert, but asterisk was not done starting up and something similar happened. > > Lonnie > > > > > >> On Feb 22, 2024, at 2:39 PM, Michael Knill <mic...@ip...> wrote: >> >> Running version 1.5.0 on Jetway NF9HG-2930. >> >> ------------------- >> Feb 22 23:00:42 30390_Ortho-ACT_CM1 daemon.err lighttpd[30995]: (server.c.2029) server stopped by UID = 0 PID = 7065 >> Feb 22 23:00:43 30390_Ortho-ACT_CM1 daemon.err lighttpd[7087]: (server.c.1436) server started (lighttpd/1.4.51) >> Feb 22 23:00:43 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for HTTPS and 'lighttpd' restarted >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for SIP-TLS and 'asterisk' restart when convenient requested >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: astobj2_container.c:492 in ao2_iterator_init: FRACK!, Failed assertion user_data is NULL (0) >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: :0 in : Got 11 backtrace records # 0: /usr/sbin/asterisk(__ao2_ref+0x5de) [0x46213e] # 1: /usr/sbin/asterisk(ao2_iterator_init+0x2f) [0x464a1f] # 2: /usr/lib/asterisk/modules/app_queue.so(+0xef4d) [0x14f159681f4d] # 3: /usr/sbin/asterisk() [0x51849e] # 4: /usr/sbin/asterisk() [0x5206a4] # 5: /usr/sbin/asterisk() [0x573c60] # 6: /usr/sbin/asterisk(ast_taskprocessor_execute+0x16f) [0x591f0f] # 7: /usr/sbin/asterisk() [0x591fb0] # 8: /usr/sbin/asterisk() [0x >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: app_queue.c:2823 in extension_state_cb: FRACK!, Failed assertion user_data is NULL (0) >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: :0 in : Got 11 backtrace records # 0: /usr/sbin/asterisk() [0x461502] # 1: /usr/sbin/asterisk(__ao2_iterator_next+0x1d8) [0x464e28] # 2: /usr/lib/asterisk/modules/app_queue.so(+0xef9c) [0x14f159681f9c] # 3: /usr/sbin/asterisk() [0x51849e] # 4: /usr/sbin/asterisk() [0x5206a4] # 5: /usr/sbin/asterisk() [0x573c60] # 6: /usr/sbin/asterisk(ast_taskprocessor_execute+0x16f) [0x591f0f] # 7: /usr/sbin/asterisk() [0x591fb0] # 8: /usr/sbin/asterisk() [0x5a0c5a] # 9: >> >> ……. more of the same ……... >> >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.info kernel: asterisk[31178]: segfault at 58 ip 00000000004f4da0 sp 000014f15a55ba58 error 4 in asterisk[43d000+1d6000] >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.info kernel: Code: c0 74 1f 85 f6 74 1b 89 f2 48 39 d0 72 14 48 8b 47 68 48 63 f6 48 8b 44 f0 f8 c3 0f 1f 80 00 00 00 00 31 c0 c3 0f 1f 44 00 00 <48> 8b 47 58 c3 66 66 2e 0f 1f 84 00 00 00 00 00 49 89 f9 41 b8 af >> Feb 22 23:00:45 30390_Ortho-ACT_CM1 user.info safe_asterisk: Asterisk exited on signal 11. >> Feb 22 23:00:45 30390_Ortho-ACT_CM1 user.info safe_asterisk: Automatically restarting Asterisk. >> Feb 22 23:00:46 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for XMPP and 'prosody' restarted >> ------------------- >> >> Im thinking of putting this one in the cloud as this box has been there for a while, but wondering if this is a bug or something else? I cant recall seeing it before. >> >> Thanks >> Michael Knill >> >> >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2024-02-22 21:48:19
|
Yes good question but we certainly need multiple certs. We basically have a domain for the customer portal and a domain for management access which may not be the same address e.g. management via VPN. Thanks I will add this to the next release. Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Date: Friday, 23 February 2024 at 8:45 am To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] Asterisk appeared to crash after ACME deploy A 60 second delay should do it, but I would question why you need two certs. In my case I was testing something and switched to using only one cert. Lonnie > On Feb 22, 2024, at 3:41 PM, Michael Knill <mic...@ip...> wrote: > > Ah interesting I do have two certs. Should I add a delay before the second deploy script? > > Regards > Michael Knill > > > From: Lonnie Abelbeck <li...@lo...> > Date: Friday, 23 February 2024 at 8:38 am > To: AstLinux Users Mailing List <ast...@li...> > Subject: Re: [Astlinux-users] Asterisk appeared to crash after ACME deploy > > Hi Michael, > > I had my Jetway NF9HG-2930 die a year or so ago, I know Michael Keuter had a couple NF9HG-2930s die. Though in my case it would not power up anymore. > > This case does seem to be different. > > Hmmm, is your ACME only a single domain (cert)? > > I recall having a case where acme.sh generated two certs and the deploy script was called for the second cert, but asterisk was not done starting up and something similar happened. > > Lonnie > > > > > > > On Feb 22, 2024, at 2:39 PM, Michael Knill <mic...@ip...> wrote: > > > > Running version 1.5.0 on Jetway NF9HG-2930. > > > > ------------------- > > Feb 22 23:00:42 30390_Ortho-ACT_CM1 daemon.err lighttpd[30995]: (server.c.2029) server stopped by UID = 0 PID = 7065 > > Feb 22 23:00:43 30390_Ortho-ACT_CM1 daemon.err lighttpd[7087]: (server.c.1436) server started (lighttpd/1.4.51) > > Feb 22 23:00:43 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for HTTPS and 'lighttpd' restarted > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for SIP-TLS and 'asterisk' restart when convenient requested > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: astobj2_container.c:492 in ao2_iterator_init: FRACK!, Failed assertion user_data is NULL (0) > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: :0 in : Got 11 backtrace records # 0: /usr/sbin/asterisk(__ao2_ref+0x5de) [0x46213e] # 1: /usr/sbin/asterisk(ao2_iterator_init+0x2f) [0x464a1f] # 2: /usr/lib/asterisk/modules/app_queue.so(+0xef4d) [0x14f159681f4d] # 3: /usr/sbin/asterisk() [0x51849e] # 4: /usr/sbin/asterisk() [0x5206a4] # 5: /usr/sbin/asterisk() [0x573c60] # 6: /usr/sbin/asterisk(ast_taskprocessor_execute+0x16f) [0x591f0f] # 7: /usr/sbin/asterisk() [0x591fb0] # 8: /usr/sbin/asterisk() [0x > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: app_queue.c:2823 in extension_state_cb: FRACK!, Failed assertion user_data is NULL (0) > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: :0 in : Got 11 backtrace records # 0: /usr/sbin/asterisk() [0x461502] # 1: /usr/sbin/asterisk(__ao2_iterator_next+0x1d8) [0x464e28] # 2: /usr/lib/asterisk/modules/app_queue.so(+0xef9c) [0x14f159681f9c] # 3: /usr/sbin/asterisk() [0x51849e] # 4: /usr/sbin/asterisk() [0x5206a4] # 5: /usr/sbin/asterisk() [0x573c60] # 6: /usr/sbin/asterisk(ast_taskprocessor_execute+0x16f) [0x591f0f] # 7: /usr/sbin/asterisk() [0x591fb0] # 8: /usr/sbin/asterisk() [0x5a0c5a] # 9: > > > > ……. more of the same ……... > > > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.info kernel: asterisk[31178]: segfault at 58 ip 00000000004f4da0 sp 000014f15a55ba58 error 4 in asterisk[43d000+1d6000] > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.info kernel: Code: c0 74 1f 85 f6 74 1b 89 f2 48 39 d0 72 14 48 8b 47 68 48 63 f6 48 8b 44 f0 f8 c3 0f 1f 80 00 00 00 00 31 c0 c3 0f 1f 44 00 00 <48> 8b 47 58 c3 66 66 2e 0f 1f 84 00 00 00 00 00 49 89 f9 41 b8 af > > Feb 22 23:00:45 30390_Ortho-ACT_CM1 user.info safe_asterisk: Asterisk exited on signal 11. > > Feb 22 23:00:45 30390_Ortho-ACT_CM1 user.info safe_asterisk: Automatically restarting Asterisk. > > Feb 22 23:00:46 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for XMPP and 'prosody' restarted > > ------------------- > > > > Im thinking of putting this one in the cloud as this box has been there for a while, but wondering if this is a bug or something else? I cant recall seeing it before. > > > > Thanks > > Michael Knill > > > > > > _______________________________________________ > > Astlinux-users mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2024-02-22 21:45:26
|
A 60 second delay should do it, but I would question why you need two certs. In my case I was testing something and switched to using only one cert. Lonnie > On Feb 22, 2024, at 3:41 PM, Michael Knill <mic...@ip...> wrote: > > Ah interesting I do have two certs. Should I add a delay before the second deploy script? > > Regards > Michael Knill > > > From: Lonnie Abelbeck <li...@lo...> > Date: Friday, 23 February 2024 at 8:38 am > To: AstLinux Users Mailing List <ast...@li...> > Subject: Re: [Astlinux-users] Asterisk appeared to crash after ACME deploy > > Hi Michael, > > I had my Jetway NF9HG-2930 die a year or so ago, I know Michael Keuter had a couple NF9HG-2930s die. Though in my case it would not power up anymore. > > This case does seem to be different. > > Hmmm, is your ACME only a single domain (cert)? > > I recall having a case where acme.sh generated two certs and the deploy script was called for the second cert, but asterisk was not done starting up and something similar happened. > > Lonnie > > > > > > > On Feb 22, 2024, at 2:39 PM, Michael Knill <mic...@ip...> wrote: > > > > Running version 1.5.0 on Jetway NF9HG-2930. > > > > ------------------- > > Feb 22 23:00:42 30390_Ortho-ACT_CM1 daemon.err lighttpd[30995]: (server.c.2029) server stopped by UID = 0 PID = 7065 > > Feb 22 23:00:43 30390_Ortho-ACT_CM1 daemon.err lighttpd[7087]: (server.c.1436) server started (lighttpd/1.4.51) > > Feb 22 23:00:43 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for HTTPS and 'lighttpd' restarted > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for SIP-TLS and 'asterisk' restart when convenient requested > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: astobj2_container.c:492 in ao2_iterator_init: FRACK!, Failed assertion user_data is NULL (0) > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: :0 in : Got 11 backtrace records # 0: /usr/sbin/asterisk(__ao2_ref+0x5de) [0x46213e] # 1: /usr/sbin/asterisk(ao2_iterator_init+0x2f) [0x464a1f] # 2: /usr/lib/asterisk/modules/app_queue.so(+0xef4d) [0x14f159681f4d] # 3: /usr/sbin/asterisk() [0x51849e] # 4: /usr/sbin/asterisk() [0x5206a4] # 5: /usr/sbin/asterisk() [0x573c60] # 6: /usr/sbin/asterisk(ast_taskprocessor_execute+0x16f) [0x591f0f] # 7: /usr/sbin/asterisk() [0x591fb0] # 8: /usr/sbin/asterisk() [0x > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: app_queue.c:2823 in extension_state_cb: FRACK!, Failed assertion user_data is NULL (0) > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: :0 in : Got 11 backtrace records # 0: /usr/sbin/asterisk() [0x461502] # 1: /usr/sbin/asterisk(__ao2_iterator_next+0x1d8) [0x464e28] # 2: /usr/lib/asterisk/modules/app_queue.so(+0xef9c) [0x14f159681f9c] # 3: /usr/sbin/asterisk() [0x51849e] # 4: /usr/sbin/asterisk() [0x5206a4] # 5: /usr/sbin/asterisk() [0x573c60] # 6: /usr/sbin/asterisk(ast_taskprocessor_execute+0x16f) [0x591f0f] # 7: /usr/sbin/asterisk() [0x591fb0] # 8: /usr/sbin/asterisk() [0x5a0c5a] # 9: > > > > ……. more of the same ……... > > > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.info kernel: asterisk[31178]: segfault at 58 ip 00000000004f4da0 sp 000014f15a55ba58 error 4 in asterisk[43d000+1d6000] > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.info kernel: Code: c0 74 1f 85 f6 74 1b 89 f2 48 39 d0 72 14 48 8b 47 68 48 63 f6 48 8b 44 f0 f8 c3 0f 1f 80 00 00 00 00 31 c0 c3 0f 1f 44 00 00 <48> 8b 47 58 c3 66 66 2e 0f 1f 84 00 00 00 00 00 49 89 f9 41 b8 af > > Feb 22 23:00:45 30390_Ortho-ACT_CM1 user.info safe_asterisk: Asterisk exited on signal 11. > > Feb 22 23:00:45 30390_Ortho-ACT_CM1 user.info safe_asterisk: Automatically restarting Asterisk. > > Feb 22 23:00:46 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for XMPP and 'prosody' restarted > > ------------------- > > > > Im thinking of putting this one in the cloud as this box has been there for a while, but wondering if this is a bug or something else? I cant recall seeing it before. > > > > Thanks > > Michael Knill > > > > > > _______________________________________________ > > Astlinux-users mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2024-02-22 21:41:30
|
Ah interesting I do have two certs. Should I add a delay before the second deploy script? Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Date: Friday, 23 February 2024 at 8:38 am To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] Asterisk appeared to crash after ACME deploy Hi Michael, I had my Jetway NF9HG-2930 die a year or so ago, I know Michael Keuter had a couple NF9HG-2930s die. Though in my case it would not power up anymore. This case does seem to be different. Hmmm, is your ACME only a single domain (cert)? I recall having a case where acme.sh generated two certs and the deploy script was called for the second cert, but asterisk was not done starting up and something similar happened. Lonnie > On Feb 22, 2024, at 2:39 PM, Michael Knill <mic...@ip...> wrote: > > Running version 1.5.0 on Jetway NF9HG-2930. > > ------------------- > Feb 22 23:00:42 30390_Ortho-ACT_CM1 daemon.err lighttpd[30995]: (server.c.2029) server stopped by UID = 0 PID = 7065 > Feb 22 23:00:43 30390_Ortho-ACT_CM1 daemon.err lighttpd[7087]: (server.c.1436) server started (lighttpd/1.4.51) > Feb 22 23:00:43 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for HTTPS and 'lighttpd' restarted > Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for SIP-TLS and 'asterisk' restart when convenient requested > Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: astobj2_container.c:492 in ao2_iterator_init: FRACK!, Failed assertion user_data is NULL (0) > Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: :0 in : Got 11 backtrace records # 0: /usr/sbin/asterisk(__ao2_ref+0x5de) [0x46213e] # 1: /usr/sbin/asterisk(ao2_iterator_init+0x2f) [0x464a1f] # 2: /usr/lib/asterisk/modules/app_queue.so(+0xef4d) [0x14f159681f4d] # 3: /usr/sbin/asterisk() [0x51849e] # 4: /usr/sbin/asterisk() [0x5206a4] # 5: /usr/sbin/asterisk() [0x573c60] # 6: /usr/sbin/asterisk(ast_taskprocessor_execute+0x16f) [0x591f0f] # 7: /usr/sbin/asterisk() [0x591fb0] # 8: /usr/sbin/asterisk() [0x > Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: app_queue.c:2823 in extension_state_cb: FRACK!, Failed assertion user_data is NULL (0) > Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: ERROR[31178]: :0 in : Got 11 backtrace records # 0: /usr/sbin/asterisk() [0x461502] # 1: /usr/sbin/asterisk(__ao2_iterator_next+0x1d8) [0x464e28] # 2: /usr/lib/asterisk/modules/app_queue.so(+0xef9c) [0x14f159681f9c] # 3: /usr/sbin/asterisk() [0x51849e] # 4: /usr/sbin/asterisk() [0x5206a4] # 5: /usr/sbin/asterisk() [0x573c60] # 6: /usr/sbin/asterisk(ast_taskprocessor_execute+0x16f) [0x591f0f] # 7: /usr/sbin/asterisk() [0x591fb0] # 8: /usr/sbin/asterisk() [0x5a0c5a] # 9: > > ……. more of the same ……... > > Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.info kernel: asterisk[31178]: segfault at 58 ip 00000000004f4da0 sp 000014f15a55ba58 error 4 in asterisk[43d000+1d6000] > Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.info kernel: Code: c0 74 1f 85 f6 74 1b 89 f2 48 39 d0 72 14 48 8b 47 68 48 63 f6 48 8b 44 f0 f8 c3 0f 1f 80 00 00 00 00 31 c0 c3 0f 1f 44 00 00 <48> 8b 47 58 c3 66 66 2e 0f 1f 84 00 00 00 00 00 49 89 f9 41 b8 af > Feb 22 23:00:45 30390_Ortho-ACT_CM1 user.info safe_asterisk: Asterisk exited on signal 11. > Feb 22 23:00:45 30390_Ortho-ACT_CM1 user.info safe_asterisk: Automatically restarting Asterisk. > Feb 22 23:00:46 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME certificates deployed for XMPP and 'prosody' restarted > ------------------- > > Im thinking of putting this one in the cloud as this box has been there for a while, but wondering if this is a bug or something else? I cant recall seeing it before. > > Thanks > Michael Knill > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
63 messages has been excluded from this view by a project administrator.
