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
(1) |
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Michael K. <mic...@ip...> - 2022-02-09 04:50:11
|
Hi Group I have a site that for years intermittently has periods where it loses PPPoE connectivity on a regular basis. After further investigation by one of my techs, it appears that when this is happening there is significant upstream congestion on the service due to a Veeam backup in progress. Note that I have set traffic shaping and the voice is not affected however it is when the PPPoE drops the connection e.g. Feb 9 12:40:33 3060-ETS_Ref-CM1 daemon.info pppd[362]: No response to 3 echo-requests We have always blamed the access provider but have not been able to pinpoint the issue. I'm now thinking that possibly during this high congestion, LCP Echo Request/Reply are being delayed and/or dropped meaning that Astlinux thinks connectivity is lost and it resets the connection. So my questions are: 1. Is this possible? 2. If so, how can I fix it? Something in QoS? Can I change the PPPoE parameters for LCP echos maybe? 3. Would changing the service to IPoE fix the problem e.g. only DHCP then? Thanks all. Regards Michael Knill Managing Director D: +61 2 6189 1360 P: +61 2 6140 4656 E: mic...@ip...<mailto:mic...@ip...> W: ipcsolutions.com.au<https://ipcsolutions.com.au/> [Icon Description automatically generated] Smarter Business Communications |
|
From: Ionel C. <ion...@me...> - 2022-02-05 19:25:55
|
Well I did a POC and the answer to that is NO :) Looks like this PCI-E card AEX410 does not support passthrough. Bummer but it was fun trying > On Feb 5, 2022, at 12:29 PM, Ionel Chila via Astlinux-users <ast...@li...> wrote: > > You’re correct PCI vs PCI-E :) my mistake > > I actually do have a spare Digium AEX410 PIC-E which should do the trick for that mobo. Will that work? > > Cheers > > > > > > >> On Feb 5, 2022, at 12:26 PM, Ionel Chila via Astlinux-users <ast...@li... <mailto:ast...@li...>> wrote: >> >> That sealed the deal Lonnie. Why break a perfectly working thing LOL. I will leave it alone for now. The SIP/ATA gateways won’t work with the automation stuff I am doing. >> >> Thank you all for continuing to support these analog TDM410 cards in all astlinux releases. That’s a big ask and you guys are just awesome >> >> And as for the full PCI, actually my mobo SuperMicro X11SPM-F does have 3 PCI slots on it. I run a 2nd generation Xeon 28 cores on it with 256G memory so I think is beefy enough :) >> >> https://www.supermicro.com/en/products/motherboard/X11SPM-F <https://www.supermicro.com/en/products/motherboard/X11SPM-F> >> >> >> Cheer and thanks again >> >> Ionel Chila >> >> >> >> >> >>> On Feb 5, 2022, at 11:57 AM, Lonnie Abelbeck <li...@lo... <mailto:li...@lo...>> wrote: >>> >>> >>> >>>> On Feb 5, 2022, at 11:50 AM, Lonnie Abelbeck <li...@lo... <mailto:li...@lo...>> wrote: >>>> >>>>> >>>>> On Feb 5, 2022, at 11:09 AM, Ionel Chila via Astlinux-users <ast...@li... <mailto:ast...@li...>> wrote: >>>>> >>>>> I had this dedicated box with a Digium Wildcard TDM410 running forever, thanks for all the hard work that is put into this great project. I run few SIP trunks on this home PBX with VOIP providers from Europe, Asia and US as I have family all over the world. I also use this for some automation tasks, so the need for the FXO and FXS modules besides my home line. >>>>> >>>>> I am in process of consolidating some of my small servers into a beefy VmWare Esxi 7.0 server and I was wondering if migrating from this current physical PBX to VmWare will work. The only part I am not sure in VmWare is about TDM410. Will this TDM410 card still work properly even in the virtual environment, of course after putting the card in passthrough mode. Does anyone have a similar working setup? >>>>> >>>>> https://doc.astlinux-project.org/userdoc:guest_vm_vmware_vsphere <https://doc.astlinux-project.org/userdoc:guest_vm_vmware_vsphere> >>>>> >>>>> Thanks >>>>> Ionel Chila >>>> >>>> The TDM410 is PCI not PCIe, so you have a "beefy VmWare Esxi 7.0 server" with PCI? >>>> >>>> While possible, (I have never done it) I would consider reserving one of your old boxes with PCI as a home-built SIP/ATA using AstLinux. >>>> >>>> Lonnie >>> >>> Update Ionel, >>> >>> No, using a DAHDI card will not work in a VM, as least with the standard builds as the Digium hardware firmware is not installed for genx86_64-vm builds. >>> >>> Building you own SIP/ATA gateway is the best option ... or leave a working solution alone :-) >>> >>> Lonnie >>> >>> >>> >>> >>> _______________________________________________ >>> Astlinux-users mailing list >>> Ast...@li... <mailto:Ast...@li...> >>> https://lists.sourceforge.net/lists/listinfo/astlinux-users <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... <mailto: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...> - 2022-02-05 18:29:56
|
You’re correct PCI vs PCI-E :) my mistake I actually do have a spare Digium AEX410 PIC-E which should do the trick for that mobo. Will that work? Cheers > On Feb 5, 2022, at 12:26 PM, Ionel Chila via Astlinux-users <ast...@li...> wrote: > > That sealed the deal Lonnie. Why break a perfectly working thing LOL. I will leave it alone for now. The SIP/ATA gateways won’t work with the automation stuff I am doing. > > Thank you all for continuing to support these analog TDM410 cards in all astlinux releases. That’s a big ask and you guys are just awesome > > And as for the full PCI, actually my mobo SuperMicro X11SPM-F does have 3 PCI slots on it. I run a 2nd generation Xeon 28 cores on it with 256G memory so I think is beefy enough :) > > https://www.supermicro.com/en/products/motherboard/X11SPM-F <https://www.supermicro.com/en/products/motherboard/X11SPM-F> > > > Cheer and thanks again > > Ionel Chila > > > > > >> On Feb 5, 2022, at 11:57 AM, Lonnie Abelbeck <li...@lo... <mailto:li...@lo...>> wrote: >> >> >> >>> On Feb 5, 2022, at 11:50 AM, Lonnie Abelbeck <li...@lo... <mailto:li...@lo...>> wrote: >>> >>>> >>>> On Feb 5, 2022, at 11:09 AM, Ionel Chila via Astlinux-users <ast...@li... <mailto:ast...@li...>> wrote: >>>> >>>> I had this dedicated box with a Digium Wildcard TDM410 running forever, thanks for all the hard work that is put into this great project. I run few SIP trunks on this home PBX with VOIP providers from Europe, Asia and US as I have family all over the world. I also use this for some automation tasks, so the need for the FXO and FXS modules besides my home line. >>>> >>>> I am in process of consolidating some of my small servers into a beefy VmWare Esxi 7.0 server and I was wondering if migrating from this current physical PBX to VmWare will work. The only part I am not sure in VmWare is about TDM410. Will this TDM410 card still work properly even in the virtual environment, of course after putting the card in passthrough mode. Does anyone have a similar working setup? >>>> >>>> https://doc.astlinux-project.org/userdoc:guest_vm_vmware_vsphere <https://doc.astlinux-project.org/userdoc:guest_vm_vmware_vsphere> >>>> >>>> Thanks >>>> Ionel Chila >>> >>> The TDM410 is PCI not PCIe, so you have a "beefy VmWare Esxi 7.0 server" with PCI? >>> >>> While possible, (I have never done it) I would consider reserving one of your old boxes with PCI as a home-built SIP/ATA using AstLinux. >>> >>> Lonnie >> >> Update Ionel, >> >> No, using a DAHDI card will not work in a VM, as least with the standard builds as the Digium hardware firmware is not installed for genx86_64-vm builds. >> >> Building you own SIP/ATA gateway is the best option ... or leave a working solution alone :-) >> >> Lonnie >> >> >> >> >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li... <mailto: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...> - 2022-02-05 18:26:22
|
That sealed the deal Lonnie. Why break a perfectly working thing LOL. I will leave it alone for now. The SIP/ATA gateways won’t work with the automation stuff I am doing. Thank you all for continuing to support these analog TDM410 cards in all astlinux releases. That’s a big ask and you guys are just awesome And as for the full PCI, actually my mobo SuperMicro X11SPM-F does have 3 PCI slots on it. I run a 2nd generation Xeon 28 cores on it with 256G memory so I think is beefy enough :) https://www.supermicro.com/en/products/motherboard/X11SPM-F <https://www.supermicro.com/en/products/motherboard/X11SPM-F> Cheer and thanks again Ionel Chila > On Feb 5, 2022, at 11:57 AM, Lonnie Abelbeck <li...@lo...> wrote: > > > >> On Feb 5, 2022, at 11:50 AM, Lonnie Abelbeck <li...@lo...> wrote: >> >>> >>> On Feb 5, 2022, at 11:09 AM, Ionel Chila via Astlinux-users <ast...@li...> wrote: >>> >>> I had this dedicated box with a Digium Wildcard TDM410 running forever, thanks for all the hard work that is put into this great project. I run few SIP trunks on this home PBX with VOIP providers from Europe, Asia and US as I have family all over the world. I also use this for some automation tasks, so the need for the FXO and FXS modules besides my home line. >>> >>> I am in process of consolidating some of my small servers into a beefy VmWare Esxi 7.0 server and I was wondering if migrating from this current physical PBX to VmWare will work. The only part I am not sure in VmWare is about TDM410. Will this TDM410 card still work properly even in the virtual environment, of course after putting the card in passthrough mode. Does anyone have a similar working setup? >>> >>> https://doc.astlinux-project.org/userdoc:guest_vm_vmware_vsphere >>> >>> Thanks >>> Ionel Chila >> >> The TDM410 is PCI not PCIe, so you have a "beefy VmWare Esxi 7.0 server" with PCI? >> >> While possible, (I have never done it) I would consider reserving one of your old boxes with PCI as a home-built SIP/ATA using AstLinux. >> >> Lonnie > > Update Ionel, > > No, using a DAHDI card will not work in a VM, as least with the standard builds as the Digium hardware firmware is not installed for genx86_64-vm builds. > > Building you own SIP/ATA gateway is the best option ... or leave a working solution alone :-) > > Lonnie > > > > > _______________________________________________ > 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...> - 2022-02-05 17:57:49
|
> On Feb 5, 2022, at 11:50 AM, Lonnie Abelbeck <li...@lo...> wrote: > >> >> On Feb 5, 2022, at 11:09 AM, Ionel Chila via Astlinux-users <ast...@li...> wrote: >> >> I had this dedicated box with a Digium Wildcard TDM410 running forever, thanks for all the hard work that is put into this great project. I run few SIP trunks on this home PBX with VOIP providers from Europe, Asia and US as I have family all over the world. I also use this for some automation tasks, so the need for the FXO and FXS modules besides my home line. >> >> I am in process of consolidating some of my small servers into a beefy VmWare Esxi 7.0 server and I was wondering if migrating from this current physical PBX to VmWare will work. The only part I am not sure in VmWare is about TDM410. Will this TDM410 card still work properly even in the virtual environment, of course after putting the card in passthrough mode. Does anyone have a similar working setup? >> >> https://doc.astlinux-project.org/userdoc:guest_vm_vmware_vsphere >> >> Thanks >> Ionel Chila > > The TDM410 is PCI not PCIe, so you have a "beefy VmWare Esxi 7.0 server" with PCI? > > While possible, (I have never done it) I would consider reserving one of your old boxes with PCI as a home-built SIP/ATA using AstLinux. > > Lonnie Update Ionel, No, using a DAHDI card will not work in a VM, as least with the standard builds as the Digium hardware firmware is not installed for genx86_64-vm builds. Building you own SIP/ATA gateway is the best option ... or leave a working solution alone :-) Lonnie |
|
From: Michael K. <li...@mk...> - 2022-02-05 17:56:49
|
> Am 05.02.2022 um 18:50 schrieb Lonnie Abelbeck <li...@lo...>: > >> >> On Feb 5, 2022, at 11:09 AM, Ionel Chila via Astlinux-users <ast...@li...> wrote: >> >> I had this dedicated box with a Digium Wildcard TDM410 running forever, thanks for all the hard work that is put into this great project. I run few SIP trunks on this home PBX with VOIP providers from Europe, Asia and US as I have family all over the world. I also use this for some automation tasks, so the need for the FXO and FXS modules besides my home line. >> >> I am in process of consolidating some of my small servers into a beefy VmWare Esxi 7.0 server and I was wondering if migrating from this current physical PBX to VmWare will work. The only part I am not sure in VmWare is about TDM410. Will this TDM410 card still work properly even in the virtual environment, of course after putting the card in passthrough mode. Does anyone have a similar working setup? >> >> https://doc.astlinux-project.org/userdoc:guest_vm_vmware_vsphere >> >> Thanks >> Ionel Chila > > The TDM410 is PCI not PCIe, so you have a "beefy VmWare Esxi 7.0 server" with PCI? > > While possible, (I have never done it) I would consider reserving one of your old boxes with PCI as a home-built SIP/ATA using AstLinux. > > Lonnie Or use physical ATAs from Cisco, Yeastar, Grandstream via SIP instead. That works without VM issues (only configuring th ATAs, which can be tricky as well). Michael http://www.mksolutions.info |
|
From: Lonnie A. <li...@lo...> - 2022-02-05 17:51:05
|
> On Feb 5, 2022, at 11:09 AM, Ionel Chila via Astlinux-users <ast...@li...> wrote: > > I had this dedicated box with a Digium Wildcard TDM410 running forever, thanks for all the hard work that is put into this great project. I run few SIP trunks on this home PBX with VOIP providers from Europe, Asia and US as I have family all over the world. I also use this for some automation tasks, so the need for the FXO and FXS modules besides my home line. > > I am in process of consolidating some of my small servers into a beefy VmWare Esxi 7.0 server and I was wondering if migrating from this current physical PBX to VmWare will work. The only part I am not sure in VmWare is about TDM410. Will this TDM410 card still work properly even in the virtual environment, of course after putting the card in passthrough mode. Does anyone have a similar working setup? > > https://doc.astlinux-project.org/userdoc:guest_vm_vmware_vsphere > > Thanks > Ionel Chila The TDM410 is PCI not PCIe, so you have a "beefy VmWare Esxi 7.0 server" with PCI? While possible, (I have never done it) I would consider reserving one of your old boxes with PCI as a home-built SIP/ATA using AstLinux. Lonnie |
|
From: Ionel C. <ion...@me...> - 2022-02-05 17:09:41
|
I had this dedicated box with a Digium Wildcard TDM410 running forever, thanks for all the hard work that is put into this great project. I run few SIP trunks on this home PBX with VOIP providers from Europe, Asia and US as I have family all over the world. I also use this for some automation tasks, so the need for the FXO and FXS modules besides my home line. I am in process of consolidating some of my small servers into a beefy VmWare Esxi 7.0 server and I was wondering if migrating from this current physical PBX to VmWare will work. The only part I am not sure in VmWare is about TDM410. Will this TDM410 card still work properly even in the virtual environment, of course after putting the card in passthrough mode. Does anyone have a similar working setup? https://doc.astlinux-project.org/userdoc:guest_vm_vmware_vsphere <https://doc.astlinux-project.org/userdoc:guest_vm_vmware_vsphere> Thanks Ionel Chila |
|
From: Michael K. <mic...@ip...> - 2022-02-03 19:20:35
|
Thanks David Regards Michael Knill From: David Kerr <da...@ke...> Reply to: AstLinux List <ast...@li...> Date: Thursday, 3 February 2022 at 7:51 pm To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] WAN Bridge interface If you are looking for redundancy on the WAN uplink then the way to do it is with bonded interfaces not bridged interfaces, assuming the other end supports bonds (also known as Link Aggregation) then the network layer will take care of it all. Astlinux out-of-the-box does not support bonded interfaces, I have added support in my version of Astlinux (on my Github, in the develop branch). I have bonded interfaces on both my WAN and LAN. The WAN has two ethernet cables connecting to my cable modem. The LAN has two ethernet cables connected to my switch that is configured with a LAG (link aggregation group), you need a managed switch that supports LAG. I did it because my Comcast/Xfinity service will deliver 1.4Gbps download speeds, and one ethernet cable maxes out at just under 1Gbps, so to get the most out of my internet service I need to be able to pump more through the Astlinux gateway than a single cable will allow. But you also get redundancy, disconnect one of the two bonded cables and the system doesn't miss a beat (but max throughput drops to 1Gbps). David On Wed, Feb 2, 2022 at 6:28 PM Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote: Hi Lonnie It's the firewalls that are configured for failover using FireCluster. They use VRRP as I just found out: https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/ha/cluster_ap_cluster_id_wsm.html?Highlight=firecluster%20mac%20address Regards Michael Knill On 3/2/22, 9:23 am, "Lonnie Abelbeck" <li...@lo...<mailto:li...@lo...>> wrote: Interesting, but I don't quite understand how the upstream multihomed link works. If the AstLinux WAN bridge interface has a static IP and gateway, how is this a failover situation ... unless like you mentioned a VRRP (keepalived) setup. Is the AstLinux static gateway IP ARP'ing to different MACs depending on some magic upstream? All in the same subnet? If "yes" above, then this would indeed be a special case where you would want the WAN to be a bridge interface. Lonnie > On Feb 2, 2022, at 4:04 PM, Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote: > > It's a static address with the gateway address shared on the firewalls as active and standby. Not sure if they have a virtual address like VRRP but doesn't make any difference from Astlinux's perspective. > I did some testing and all seemed to work. Its on a Qotom box so I assume performance should not be an issue. > > Regards > Michael Knill > > On 3/2/22, 9:00 am, "Lonnie Abelbeck" <li...@lo...<mailto:li...@lo...>> wrote: > > Hi Michael, > > It would be a special case where you would want the WAN to be a bridge interface. > > How is the WAN interface's IP address defined? > > I'm not sure how your two WAN trunks are routed to your bridge interface. > > But, if a 2-port ethernet switch would work, so should a 2-interface linux bridge. > > Lonnie > > > > >> On Feb 2, 2022, at 3:33 PM, Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote: >> >> Hi Group >> >> I have set up two ports on my Astlinux box into a bridge and allocated to the WAN interface. These ports are connected behind a primary and failover Watchguard firewall as a DMZ interface. The LAN interface connects to the Voice VLAN making this system a VPN router only for about 70 phones. >> >> Just wanting to know if anyone can see any issues with this architecture as I haven’t used bridge interfaces before. >> It just seems better than sticking a switch in between creating another single point of failure. >> >> Regards >> >> Michael Knill >> Managing Director >> >> D: +61 2 6189 1360 >> P: +61 2 6140 4656 >> E: mic...@ip...<mailto:mic...@ip...> >> W: ipcsolutions.com.au<http://ipcsolutions.com.au> >> >> <image001.png> >> Smarter Business Communications >> >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li...<mailto:Ast...@li...> >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>. > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li...<mailto:Ast...@li...> > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>. > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li...<mailto:Ast...@li...> > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>. _______________________________________________ Astlinux-users mailing list Ast...@li...<mailto:Ast...@li...> https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>. _______________________________________________ Astlinux-users mailing list Ast...@li...<mailto:Ast...@li...> https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>. |
|
From: David K. <da...@ke...> - 2022-02-03 08:50:56
|
If you are looking for redundancy on the WAN uplink then the way to do it is with bonded interfaces not bridged interfaces, assuming the other end supports bonds (also known as Link Aggregation) then the network layer will take care of it all. Astlinux out-of-the-box does not support bonded interfaces, I have added support in my version of Astlinux (on my Github, in the develop branch). I have bonded interfaces on both my WAN and LAN. The WAN has two ethernet cables connecting to my cable modem. The LAN has two ethernet cables connected to my switch that is configured with a LAG (link aggregation group), you need a managed switch that supports LAG. I did it because my Comcast/Xfinity service will deliver 1.4Gbps download speeds, and one ethernet cable maxes out at just under 1Gbps, so to get the most out of my internet service I need to be able to pump more through the Astlinux gateway than a single cable will allow. But you also get redundancy, disconnect one of the two bonded cables and the system doesn't miss a beat (but max throughput drops to 1Gbps). David On Wed, Feb 2, 2022 at 6:28 PM Michael Knill < mic...@ip...> wrote: > Hi Lonnie > > It's the firewalls that are configured for failover using FireCluster. > They use VRRP as I just found out: > > https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/ha/cluster_ap_cluster_id_wsm.html?Highlight=firecluster%20mac%20address > > Regards > Michael Knill > > On 3/2/22, 9:23 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Interesting, but I don't quite understand how the upstream multihomed > link works. > > If the AstLinux WAN bridge interface has a static IP and gateway, how > is this a failover situation ... unless like you mentioned a VRRP > (keepalived) setup. > > Is the AstLinux static gateway IP ARP'ing to different MACs depending > on some magic upstream? All in the same subnet? > > If "yes" above, then this would indeed be a special case where you > would want the WAN to be a bridge interface. > > Lonnie > > > > On Feb 2, 2022, at 4:04 PM, Michael Knill < > mic...@ip...> wrote: > > > > It's a static address with the gateway address shared on the > firewalls as active and standby. Not sure if they have a virtual address > like VRRP but doesn't make any difference from Astlinux's perspective. > > I did some testing and all seemed to work. Its on a Qotom box so I > assume performance should not be an issue. > > > > Regards > > Michael Knill > > > > On 3/2/22, 9:00 am, "Lonnie Abelbeck" <li...@lo...> > wrote: > > > > Hi Michael, > > > > It would be a special case where you would want the WAN to be a > bridge interface. > > > > How is the WAN interface's IP address defined? > > > > I'm not sure how your two WAN trunks are routed to your bridge > interface. > > > > But, if a 2-port ethernet switch would work, so should a > 2-interface linux bridge. > > > > Lonnie > > > > > > > > > >> On Feb 2, 2022, at 3:33 PM, Michael Knill < > mic...@ip...> wrote: > >> > >> Hi Group > >> > >> I have set up two ports on my Astlinux box into a bridge and > allocated to the WAN interface. These ports are connected behind a primary > and failover Watchguard firewall as a DMZ interface. The LAN interface > connects to the Voice VLAN making this system a VPN router only for about > 70 phones. > >> > >> Just wanting to know if anyone can see any issues with this > architecture as I haven’t used bridge interfaces before. > >> It just seems better than sticking a switch in between creating > another single point of failure. > >> > >> 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.... > > > > > > _______________________________________________ > > 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...> - 2022-02-02 23:28:19
|
Hi Lonnie It's the firewalls that are configured for failover using FireCluster. They use VRRP as I just found out: https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/ha/cluster_ap_cluster_id_wsm.html?Highlight=firecluster%20mac%20address Regards Michael Knill On 3/2/22, 9:23 am, "Lonnie Abelbeck" <li...@lo...> wrote: Interesting, but I don't quite understand how the upstream multihomed link works. If the AstLinux WAN bridge interface has a static IP and gateway, how is this a failover situation ... unless like you mentioned a VRRP (keepalived) setup. Is the AstLinux static gateway IP ARP'ing to different MACs depending on some magic upstream? All in the same subnet? If "yes" above, then this would indeed be a special case where you would want the WAN to be a bridge interface. Lonnie > On Feb 2, 2022, at 4:04 PM, Michael Knill <mic...@ip...> wrote: > > It's a static address with the gateway address shared on the firewalls as active and standby. Not sure if they have a virtual address like VRRP but doesn't make any difference from Astlinux's perspective. > I did some testing and all seemed to work. Its on a Qotom box so I assume performance should not be an issue. > > Regards > Michael Knill > > On 3/2/22, 9:00 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Hi Michael, > > It would be a special case where you would want the WAN to be a bridge interface. > > How is the WAN interface's IP address defined? > > I'm not sure how your two WAN trunks are routed to your bridge interface. > > But, if a 2-port ethernet switch would work, so should a 2-interface linux bridge. > > Lonnie > > > > >> On Feb 2, 2022, at 3:33 PM, Michael Knill <mic...@ip...> wrote: >> >> Hi Group >> >> I have set up two ports on my Astlinux box into a bridge and allocated to the WAN interface. These ports are connected behind a primary and failover Watchguard firewall as a DMZ interface. The LAN interface connects to the Voice VLAN making this system a VPN router only for about 70 phones. >> >> Just wanting to know if anyone can see any issues with this architecture as I haven’t used bridge interfaces before. >> It just seems better than sticking a switch in between creating another single point of failure. >> >> 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.... > > > _______________________________________________ > 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...> - 2022-02-02 22:23:28
|
Interesting, but I don't quite understand how the upstream multihomed link works. If the AstLinux WAN bridge interface has a static IP and gateway, how is this a failover situation ... unless like you mentioned a VRRP (keepalived) setup. Is the AstLinux static gateway IP ARP'ing to different MACs depending on some magic upstream? All in the same subnet? If "yes" above, then this would indeed be a special case where you would want the WAN to be a bridge interface. Lonnie > On Feb 2, 2022, at 4:04 PM, Michael Knill <mic...@ip...> wrote: > > It's a static address with the gateway address shared on the firewalls as active and standby. Not sure if they have a virtual address like VRRP but doesn't make any difference from Astlinux's perspective. > I did some testing and all seemed to work. Its on a Qotom box so I assume performance should not be an issue. > > Regards > Michael Knill > > On 3/2/22, 9:00 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Hi Michael, > > It would be a special case where you would want the WAN to be a bridge interface. > > How is the WAN interface's IP address defined? > > I'm not sure how your two WAN trunks are routed to your bridge interface. > > But, if a 2-port ethernet switch would work, so should a 2-interface linux bridge. > > Lonnie > > > > >> On Feb 2, 2022, at 3:33 PM, Michael Knill <mic...@ip...> wrote: >> >> Hi Group >> >> I have set up two ports on my Astlinux box into a bridge and allocated to the WAN interface. These ports are connected behind a primary and failover Watchguard firewall as a DMZ interface. The LAN interface connects to the Voice VLAN making this system a VPN router only for about 70 phones. >> >> Just wanting to know if anyone can see any issues with this architecture as I haven’t used bridge interfaces before. >> It just seems better than sticking a switch in between creating another single point of failure. >> >> 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.... > > > _______________________________________________ > 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...> - 2022-02-02 22:05:12
|
It's a static address with the gateway address shared on the firewalls as active and standby. Not sure if they have a virtual address like VRRP but doesn't make any difference from Astlinux's perspective.
I did some testing and all seemed to work. Its on a Qotom box so I assume performance should not be an issue.
Regards
Michael Knill
On 3/2/22, 9:00 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Hi Michael,
It would be a special case where you would want the WAN to be a bridge interface.
How is the WAN interface's IP address defined?
I'm not sure how your two WAN trunks are routed to your bridge interface.
But, if a 2-port ethernet switch would work, so should a 2-interface linux bridge.
Lonnie
> On Feb 2, 2022, at 3:33 PM, Michael Knill <mic...@ip...> wrote:
>
> Hi Group
>
> I have set up two ports on my Astlinux box into a bridge and allocated to the WAN interface. These ports are connected behind a primary and failover Watchguard firewall as a DMZ interface. The LAN interface connects to the Voice VLAN making this system a VPN router only for about 70 phones.
>
> Just wanting to know if anyone can see any issues with this architecture as I haven’t used bridge interfaces before.
> It just seems better than sticking a switch in between creating another single point of failure.
>
> 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: Lonnie A. <li...@lo...> - 2022-02-02 21:59:33
|
Hi Michael, It would be a special case where you would want the WAN to be a bridge interface. How is the WAN interface's IP address defined? I'm not sure how your two WAN trunks are routed to your bridge interface. But, if a 2-port ethernet switch would work, so should a 2-interface linux bridge. Lonnie > On Feb 2, 2022, at 3:33 PM, Michael Knill <mic...@ip...> wrote: > > Hi Group > > I have set up two ports on my Astlinux box into a bridge and allocated to the WAN interface. These ports are connected behind a primary and failover Watchguard firewall as a DMZ interface. The LAN interface connects to the Voice VLAN making this system a VPN router only for about 70 phones. > > Just wanting to know if anyone can see any issues with this architecture as I haven’t used bridge interfaces before. > It just seems better than sticking a switch in between creating another single point of failure. > > 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...> - 2022-02-02 21:34:13
|
Hi Group I have set up two ports on my Astlinux box into a bridge and allocated to the WAN interface. These ports are connected behind a primary and failover Watchguard firewall as a DMZ interface. The LAN interface connects to the Voice VLAN making this system a VPN router only for about 70 phones. Just wanting to know if anyone can see any issues with this architecture as I haven’t used bridge interfaces before. It just seems better than sticking a switch in between creating another single point of failure. Regards Michael Knill Managing Director D: +61 2 6189 1360 P: +61 2 6140 4656 E: mic...@ip...<mailto:mic...@ip...> W: ipcsolutions.com.au<https://ipcsolutions.com.au/> [Icon Description automatically generated] Smarter Business Communications |
|
From: Lonnie A. <li...@lo...> - 2022-01-30 17:12:57
|
Greetings, A simple note to let our users know about a new back-end cloud infrastructure for the AstLinux Project. This change should be seamless, and unnoticed for the majority of you. The AstLinux Project cloud infrastructure, including the documentation wiki, release images, release ISOs, domain DNS, as well as development files are all now hosted via Linode [1]. As such, some of you may download official release images to your own private repository. Previously a person could use HTTPS with "s3.amazonaws.com/mirror.astlinux-project/..." to access release images and ISOs, for the future use HTTPS with "astlinux-project.org/mirror/...". Note, if you use 'curl' include the '-L' option to follow the redirect. Lastly, as special thanks goes out to Darrick Hartman for hosting the documentation wiki in his Colo and paying for AWS S3 costs for many years. Darrick has long been involved with AstLinux (since 2006) and assisted with this transition ... Thanks! AstLinux Team [1] https://www.linode.com/ |
|
From: Michael K. <mic...@ip...> - 2022-01-21 02:27:14
|
These are the best resources: https://wiki.asterisk.org/wiki/display/AST/Upgrading+to+Asterisk+14 https://wiki.asterisk.org/wiki/display/AST/Upgrading+to+Asterisk+15 https://wiki.asterisk.org/wiki/display/AST/Upgrading+to+Asterisk+16 Significant changes that I see: * The 'Macro' dialplan application has been deprecated and is no longer built by default * The Command action now sends the output from the CLI command as a series of Output headers for each line instead of as a block of text with the --END COMMAND-- delimiter to match the output from other actions. Regards Michael Knill From: AstLinux List <ast...@li...> Reply to: AstLinux List <ast...@li...> Date: Friday, 21 January 2022 at 10:58 am To: AstLinux List <ast...@li...> Cc: Ionel Chila <ion...@me...> Subject: [Astlinux-users] Moving to Asterisk 16 from 13 guidance Any guidance / faq, formal or informal for moving from Asterisk 13 to 16? I run a very small home setup with 3 SIP providers and about 20 clients. My sip.conf and extensions.conf is not that complex :) Do I need to put in another image? Would it preserve my current configuration? I appreciate any guidance. As always great community and great work with Astlinux team. Cheers ||||| | A | Release: astlinux-1.4.4 - Asterisk 13.38.3 | s | Host Name: HOME-PBX.entouch.net<http://HOME-PBX.entouch.net> | t | Last Boot: 2022-01-20 12:21 | L | Linux: 4.19.208-astlinux x86_64 | i | CPU: Intel Atom D2550 (4x) @ 1866 MHz | n | RAM: 3933 MB | u | Board Type: genx86_64 | x | Hardware: Generic x86_64 ||||| HOME-PBX ~ # |
|
From: Ionel C. <ion...@me...> - 2022-01-21 01:55:49
|
Thanks Michael. How about 13 to 18? Might as well go that path since I plan to make a switch :) Cheers > On Jan 20, 2022, at 6:09 PM, Michael Keuter <li...@mk...> wrote: > > > >> Am 21.01.2022 um 00:57 schrieb Ionel Chila via Astlinux-users <ast...@li...>: >> >> Any guidance / faq, formal or informal for moving from Asterisk 13 to 16? I run a very small home setup with 3 SIP providers and about 20 clients. My sip.conf and extensions.conf is not that complex :) >> Do I need to put in another image? > > No, just make a backup before. Then change the Repository URL. > >> Would it preserve my current configuration? I appreciate any guidance. > > Your current config is preserved. Asterisk 16 includes a few new modules. You can exclude them in "modules.conf" with "noload => xyz.so" if you don't need them. > No so much has changed in the dialplan. > > Look into the CHANGES and UPGRADE.txt: > https://github.com/asterisk/asterisk/tree/16 > >> As always great community and great work with Astlinux team. >> >> Cheers >> >> >> ||||| >> | A | Release: astlinux-1.4.4 - Asterisk 13.38.3 >> | s | Host Name: HOME-PBX.entouch.net >> | t | Last Boot: 2022-01-20 12:21 >> | L | Linux: 4.19.208-astlinux x86_64 >> | i | CPU: Intel Atom D2550 (4x) @ 1866 MHz >> | n | RAM: 3933 MB >> | u | Board Type: genx86_64 >> | x | Hardware: Generic x86_64 >> ||||| >> HOME-PBX ~ # > > > 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.... |
|
From: Michael K. <li...@mk...> - 2022-01-21 00:10:06
|
> Am 21.01.2022 um 00:57 schrieb Ionel Chila via Astlinux-users <ast...@li...>: > > Any guidance / faq, formal or informal for moving from Asterisk 13 to 16? I run a very small home setup with 3 SIP providers and about 20 clients. My sip.conf and extensions.conf is not that complex :) > Do I need to put in another image? No, just make a backup before. Then change the Repository URL. > Would it preserve my current configuration? I appreciate any guidance. Your current config is preserved. Asterisk 16 includes a few new modules. You can exclude them in "modules.conf" with "noload => xyz.so" if you don't need them. No so much has changed in the dialplan. Look into the CHANGES and UPGRADE.txt: https://github.com/asterisk/asterisk/tree/16 > As always great community and great work with Astlinux team. > > Cheers > > > ||||| > | A | Release: astlinux-1.4.4 - Asterisk 13.38.3 > | s | Host Name: HOME-PBX.entouch.net > | t | Last Boot: 2022-01-20 12:21 > | L | Linux: 4.19.208-astlinux x86_64 > | i | CPU: Intel Atom D2550 (4x) @ 1866 MHz > | n | RAM: 3933 MB > | u | Board Type: genx86_64 > | x | Hardware: Generic x86_64 > ||||| > HOME-PBX ~ # Michael http://www.mksolutions.info |
|
From: Ionel C. <ion...@me...> - 2022-01-20 23:57:54
|
Any guidance / faq, formal or informal for moving from Asterisk 13 to 16? I run a very small home setup with 3 SIP providers and about 20 clients. My sip.conf and extensions.conf is not that complex :) Do I need to put in another image? Would it preserve my current configuration? I appreciate any guidance. As always great community and great work with Astlinux team. Cheers ||||| | A | Release: astlinux-1.4.4 - Asterisk 13.38.3 | s | Host Name: HOME-PBX.entouch.net <http://home-pbx.entouch.net/> | t | Last Boot: 2022-01-20 12:21 | L | Linux: 4.19.208-astlinux x86_64 | i | CPU: Intel Atom D2550 (4x) @ 1866 MHz | n | RAM: 3933 MB | u | Board Type: genx86_64 | x | Hardware: Generic x86_64 ||||| HOME-PBX ~ # |
|
From: Dan R. <da...@ry...> - 2022-01-20 16:53:32
|
Hi Lonnie and Team AstLinux,
No worries. This wasn't an urgent request.
I agree that pjsip show channels is sub-ideal for this purpose. After all, 95% of the data shown simply echos the configuration. I've settled on pjsip show contacts, which looks good since it's all on one line, and provides useful data regarding contact availability and qualify RTTs.
I too have been clinging on to chan_sip which continues to work fine. However, since it's been deprecated and has no official maintainer, the writing is clearly on the wall.
Dan
On Thu, Jan 20, 2022 at 11:08 AM, Lonnie Abelbeck wrote:
Hi Dan,
Sorry for the lack of replies, but many of us are still using chan_sip.
There may be a command more useful than "pjsip show channels"
--
pbx*CLI> pjsip show
aor aors auth auths channel
channels channelstats contact contacts endpoint
endpoints history identifiers identifies identify
qualify registration registrations scheduled_tasks settings
subscription subscriptions transport transports unidentified_requests
--
Lonnie
On Jan 18, 2022, at 8:19 AM, Dan Ryson wrote:
AstLinux Team,
I'm delighted to see the ongoing progress of AstLinux. Thank you!
Although Asterisk 13SE is still working fine for me, the Pre-Release recommendation (highlighted below) prompted me to start experimenting with Asterisk 16 and pjsip/pjproject on a new droplet PBX, which is now 48 hours old. It's working well for the most part and I'm making slow and steady progress.
To force myself to learn pjsip, I defeated the chan_sip module. Accordingly, the AstLinux Status page now shows "No such command 'sip show registry'" and "No such command 'sip show peers'. As a possible work around, I updated the Active Channels Command to "pjsip show channels" and repurposed the Show DAHDI Command to "pjsip show endpoints" - since DAHDI isn't being used. This provides useful data and works fine. However, the raw CLI output isn't particularly pretty.
Since I'm surely not the first person to head down this path, I have a feeling that I'm missing something obvious and should ask the pros. I'm hoping to hear your thoughts and advice for showing pjsip status. Is there a better recommended practice?
Thanks,
Dan
On Thu, Jan 13, 2022 at 02:20 PM, Lonnie Abelbeck wrote:
Announcing AstLinux Pre-Release: astlinux-1.4-5333-94c1eb
Key new features:
-- Asterisk 18.x is now supported, along with Asterisk 16.x and Asterisk 13.x built --without-pjproject
-- Previous ast13-firmware-1.x is no longer being updated, ast13-firmware-1.x users should either switch to ast16-firmware-1.x (recommended)
or use ast13se-firmware-1.x if chan_pjsip is not used in your dialplan.
** The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own.
-- Linux Kernel 4.19.224 (version bump), security and bug fixes
-- OpenSSL, version bump to 1.1.1m, security fixes: none
-- WireGuard VPN, module 1.0.20211208 (version bump), tools 1.0.20210914 (no change)
-- libcurl (curl) version bump to 7.81.0
-- LibreTLS, version bump to 3.4.2
-- msmtp, version bump to 1.8.19, 'msmtpd' security fix
-- nano, version 2.7.5, fix issue where not saving a file could still copy the file to /mnt/asturw/
-- Network tab, Non-ACME Self-Signed HTTPS Certificate, use 2048 key length.
-- Asterisk 13.38.3 ('13se' no change)
Last Asterisk 13.x "Legacy" version, built --without-pjproject
-- Asterisk 16.23.0 (version bump) and 18.9.0 (new version)
-- Complete Pre-Release ChangeLog:
https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt (https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt)
The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ...
AstLinux Project -> Development
https://www.astlinux-project.org/dev.html (https://www.astlinux-project.org/dev.html)
AstLinux Team
_______________________________________________
Astlinux-users mailing list
Ast...@li... (mailto:Ast...@li...)
https://lists.sourceforge.net/lists/listinfo/astlinux-users (https://lists.sourceforge.net/lists/listinfo/astlinux-users)
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr... (mailto:pa...@kr...).
_______________________________________________
Astlinux-users mailing list
Ast...@li... (mailto:Ast...@li...)
https://lists.sourceforge.net/lists/listinfo/astlinux-users (https://lists.sourceforge.net/lists/listinfo/astlinux-users)
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr... (mailto:pa...@kr...).
|
|
From: Adrian H. <adr...@go...> - 2022-01-20 16:09:55
|
Well I am corrected Lonnie. For some reason possibly corrupt SD card it failed, re did the SD card and tried again and it has worked, now at astlinux-1.4.4 Asterisk 13.38.3 Thanks for the push. Adrian On 20/01/2022 14:27, Lonnie Abelbeck wrote: > Hi Adrian, > > In 2020-07-25, AstLinux 1.3.10 (and onward) no longer supports 32-bit CPU's. > > I did a little DDG'ing and the HP t5730 [1] uses an "AMD Sempron 2100+" CPU [2] "AMD64 / AMD 64-bit technology". > > As such I would try installing AstLinux 1.4.4 from https://www.astlinux-project.org/ > > It is possible "x86-64bit" will not work due to the HP board design, but that would give you ongoing AstLinux support. > > Lonnie > > [1] https://support.hp.com/id-en/document/c01342752 > > [2] https://www.cpu-world.com/CPUs/K8/AMD-Mobile%20Sempron%202100%2B%20-%20SMF2100HAX3DQ%20-%20SMF2100HAX3DQE.html > > >> On Jan 20, 2022, at 3:41 AM, Adrian Hodgson via Astlinux-users <ast...@li...> wrote: >> >> OK I have had success with getting the sounds packages installed, doing computer stuff in the early hours does not always go well when tired. So with some sleep.. >> >> The installer was 32 bit, what I had not taken into account was my own network. I have a typical UK home internet connection, ISP provided router that then provides a internal 192.168.1.X network, this is used by the family and typical devices in the house. I then have a UbuntuMate thin client, that does nothing but act as a simple gateway for my network 10.42.0.X, the astlinux box being 10.42.0.5 and the gateway address 10.42.0.1. >> >> So basically the box could not see the outside world until I entered 'Network settings' and allowed for Static IP, set the gateway IP as about and the DNS server as the address of my ISP provided router of 192.168.1.254. >> >> I do struggle with networking in general and only get by with my inefficient trial and error. >> >> Adrian >> >> On 20/01/2022 02:43, John Novack wrote: >>> I believe you want the 13SE version >>> AFAIK the 5730 is a 32 bit processor, though the install should complain if you try to install a 64 bit in a 32 bit machine >>> >>> JN >>> >>> >> _______________________________________________ >> 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...> - 2022-01-20 16:07:49
|
Hi Dan,
Sorry for the lack of replies, but many of us are still using chan_sip.
There may be a command more useful than "pjsip show channels"
--
pbx*CLI> pjsip show
aor aors auth auths channel
channels channelstats contact contacts endpoint
endpoints history identifiers identifies identify
qualify registration registrations scheduled_tasks settings
subscription subscriptions transport transports unidentified_requests
--
Lonnie
> On Jan 18, 2022, at 8:19 AM, Dan Ryson <da...@ry...> wrote:
>
> AstLinux Team,
>
> I'm delighted to see the ongoing progress of AstLinux. Thank you!
>
> Although Asterisk 13SE is still working fine for me, the Pre-Release recommendation (highlighted below) prompted me to start experimenting with Asterisk 16 and pjsip/pjproject on a new droplet PBX, which is now 48 hours old. It's working well for the most part and I'm making slow and steady progress.
>
> To force myself to learn pjsip, I defeated the chan_sip module. Accordingly, the AstLinux Status page now shows "No such command 'sip show registry'" and "No such command 'sip show peers'. As a possible work around, I updated the Active Channels Command to "pjsip show channels" and repurposed the Show DAHDI Command to "pjsip show endpoints" - since DAHDI isn't being used. This provides useful data and works fine. However, the raw CLI output isn't particularly pretty.
>
> Since I'm surely not the first person to head down this path, I have a feeling that I'm missing something obvious and should ask the pros. I'm hoping to hear your thoughts and advice for showing pjsip status. Is there a better recommended practice?
>
> Thanks,
>
> Dan
>
> On Thu, Jan 13, 2022 at 02:20 PM, Lonnie Abelbeck <li...@lo...> wrote:
> Announcing AstLinux Pre-Release: astlinux-1.4-5333-94c1eb
>
> Key new features:
>
> -- Asterisk 18.x is now supported, along with Asterisk 16.x and Asterisk 13.x built --without-pjproject
>
> -- Previous ast13-firmware-1.x is no longer being updated, ast13-firmware-1.x users should either switch to ast16-firmware-1.x (recommended)
> or use ast13se-firmware-1.x if chan_pjsip is not used in your dialplan.
>
> ** The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own.
>
> -- Linux Kernel 4.19.224 (version bump), security and bug fixes
>
> -- OpenSSL, version bump to 1.1.1m, security fixes: none
>
> -- WireGuard VPN, module 1.0.20211208 (version bump), tools 1.0.20210914 (no change)
>
> -- libcurl (curl) version bump to 7.81.0
>
> -- LibreTLS, version bump to 3.4.2
>
> -- msmtp, version bump to 1.8.19, 'msmtpd' security fix
>
> -- nano, version 2.7.5, fix issue where not saving a file could still copy the file to /mnt/asturw/
>
> -- Network tab, Non-ACME Self-Signed HTTPS Certificate, use 2048 key length.
>
> -- Asterisk 13.38.3 ('13se' no change)
> Last Asterisk 13.x "Legacy" version, built --without-pjproject
>
> -- Asterisk 16.23.0 (version bump) and 18.9.0 (new version)
>
> -- Complete Pre-Release ChangeLog:
> https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt
>
> The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ...
>
> AstLinux Project -> Development
> https://www.astlinux-project.org/dev.html
>
> AstLinux Team
>
> _______________________________________________
> 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: Adrian H. <adr...@go...> - 2022-01-20 14:51:57
|
Hello Lonnie; Think I have tried x64 stuff before without success, the specs are a bit scarce on the board but HP says 'Win32-based application support' so I suspect more a limitation of the motherboard data lines, but I could try it again. At least this Thin Client supports PAE which is something the T5700 I used to use a few years ago did not support. Cheers Adrian On 20/01/2022 14:27, Lonnie Abelbeck wrote: > Hi Adrian, > > In 2020-07-25, AstLinux 1.3.10 (and onward) no longer supports 32-bit CPU's. > > I did a little DDG'ing and the HP t5730 [1] uses an "AMD Sempron 2100+" CPU [2] "AMD64 / AMD 64-bit technology". > > As such I would try installing AstLinux 1.4.4 from https://www.astlinux-project.org/ > > It is possible "x86-64bit" will not work due to the HP board design, but that would give you ongoing AstLinux support. > > Lonnie > > [1] https://support.hp.com/id-en/document/c01342752 > > [2] https://www.cpu-world.com/CPUs/K8/AMD-Mobile%20Sempron%202100%2B%20-%20SMF2100HAX3DQ%20-%20SMF2100HAX3DQE.html > > >> On Jan 20, 2022, at 3:41 AM, Adrian Hodgson via Astlinux-users <ast...@li...> wrote: >> >> OK I have had success with getting the sounds packages installed, doing computer stuff in the early hours does not always go well when tired. So with some sleep.. >> >> The installer was 32 bit, what I had not taken into account was my own network. I have a typical UK home internet connection, ISP provided router that then provides a internal 192.168.1.X network, this is used by the family and typical devices in the house. I then have a UbuntuMate thin client, that does nothing but act as a simple gateway for my network 10.42.0.X, the astlinux box being 10.42.0.5 and the gateway address 10.42.0.1. >> >> So basically the box could not see the outside world until I entered 'Network settings' and allowed for Static IP, set the gateway IP as about and the DNS server as the address of my ISP provided router of 192.168.1.254. >> >> I do struggle with networking in general and only get by with my inefficient trial and error. >> >> Adrian >> >> On 20/01/2022 02:43, John Novack wrote: >>> I believe you want the 13SE version >>> AFAIK the 5730 is a 32 bit processor, though the install should complain if you try to install a 64 bit in a 32 bit machine >>> >>> JN >>> >>> >> _______________________________________________ >> 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...> - 2022-01-20 14:27:35
|
Hi Adrian, In 2020-07-25, AstLinux 1.3.10 (and onward) no longer supports 32-bit CPU's. I did a little DDG'ing and the HP t5730 [1] uses an "AMD Sempron 2100+" CPU [2] "AMD64 / AMD 64-bit technology". As such I would try installing AstLinux 1.4.4 from https://www.astlinux-project.org/ It is possible "x86-64bit" will not work due to the HP board design, but that would give you ongoing AstLinux support. Lonnie [1] https://support.hp.com/id-en/document/c01342752 [2] https://www.cpu-world.com/CPUs/K8/AMD-Mobile%20Sempron%202100%2B%20-%20SMF2100HAX3DQ%20-%20SMF2100HAX3DQE.html > On Jan 20, 2022, at 3:41 AM, Adrian Hodgson via Astlinux-users <ast...@li...> wrote: > > OK I have had success with getting the sounds packages installed, doing computer stuff in the early hours does not always go well when tired. So with some sleep.. > > The installer was 32 bit, what I had not taken into account was my own network. I have a typical UK home internet connection, ISP provided router that then provides a internal 192.168.1.X network, this is used by the family and typical devices in the house. I then have a UbuntuMate thin client, that does nothing but act as a simple gateway for my network 10.42.0.X, the astlinux box being 10.42.0.5 and the gateway address 10.42.0.1. > > So basically the box could not see the outside world until I entered 'Network settings' and allowed for Static IP, set the gateway IP as about and the DNS server as the address of my ISP provided router of 192.168.1.254. > > I do struggle with networking in general and only get by with my inefficient trial and error. > > Adrian > > On 20/01/2022 02:43, John Novack wrote: >> I believe you want the 13SE version >> AFAIK the 5730 is a 32 bit processor, though the install should complain if you try to install a 64 bit in a 32 bit machine >> >> JN >> >> > > _______________________________________________ > 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.
