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: Lonnie A. <li...@lo...> - 2018-04-23 12:53:05
|
Brian, As David said ... Though python is *huge* relatively speaking, around 36 MB uncompressed, while the complete standard AstLinux compressed image is around 50 MB. The least amount of work would be to rewrite your script in bash, php or basic perl. Lonnie On Apr 22, 2018, at 10:32 PM, David Kerr <Da...@Ke...> wrote: > You would need to do a custom build. Astlinux does not have a package manager so you cannot simply add packages to a running system. But python exists in the Astlinux build system, it is just not included by default. So you would need to setup a build system (Linux in a virtual machine) and then make your own custom build that included python. Follow developer documentation at the astlinux-project web page. > > David > > On Sun, Apr 22, 2018 at 10:41 PM, Brian Barr <bri...@gm...> wrote: > Is there any easy and simple way to install Python on Astlinux? > > I want to automate a few things that I already have python scripts debugged and working for. > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > 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.... > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > 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...> - 2018-04-23 03:55:57
|
You would need to do a custom build. Astlinux does not have a package manager so you cannot simply add packages to a running system. But python exists in the Astlinux build system, it is just not included by default. So you would need to setup a build system (Linux in a virtual machine) and then make your own custom build that included python. Follow developer documentation at the astlinux-project web page. David On Sun, Apr 22, 2018 at 10:41 PM, Brian Barr <bri...@gm...> wrote: > Is there any easy and simple way to install Python on Astlinux? > > I want to automate a few things that I already have python scripts > debugged and working for. > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > 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: Brian B. <bri...@gm...> - 2018-04-23 02:41:36
|
Is there any easy and simple way to install Python on Astlinux? I want to automate a few things that I already have python scripts debugged and working for. |
|
From: Michael K. <mic...@ip...> - 2018-04-19 21:41:24
|
Thanks Michael
Regards
Michael Knill
On 19/4/18, 5:57 pm, "Michael Keuter" <li...@mk...> wrote:
> Am 19.04.2018 um 01:23 schrieb Michael Knill <mic...@ip...>:
>
> Hi Group
>
> Just wondering if its possible to manually define an address from the OVPN IP Address Pool for a specific device.
> I want to do this to prevent it from changing e.g. I will be pointing an Asterisk SIP Peer to it.
>
> Regards
> Michael Knill
Hi Michael,
that can be done easily:
- Create a client file in the /mnt/kd/openvpn/ccd/ directory named like the profile name for the device.
- It then shows up on the WebGUI under "OpenVPN Client Configs".
- Add e.g. "ifconfig-push 10.8.122.82 255.255.255.0" to that file, and
- add "client-config-dir /etc/openvpn/ccd" to the "Raw Commands" in the OpenVPN server section.
Michael
http://www.mksolutions.info
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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...> - 2018-04-19 07:57:33
|
> Am 19.04.2018 um 01:23 schrieb Michael Knill <mic...@ip...>: > > Hi Group > > Just wondering if its possible to manually define an address from the OVPN IP Address Pool for a specific device. > I want to do this to prevent it from changing e.g. I will be pointing an Asterisk SIP Peer to it. > > Regards > Michael Knill Hi Michael, that can be done easily: - Create a client file in the /mnt/kd/openvpn/ccd/ directory named like the profile name for the device. - It then shows up on the WebGUI under "OpenVPN Client Configs". - Add e.g. "ifconfig-push 10.8.122.82 255.255.255.0" to that file, and - add "client-config-dir /etc/openvpn/ccd" to the "Raw Commands" in the OpenVPN server section. Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2018-04-18 23:39:22
|
Hi Group Just wondering if its possible to manually define an address from the OVPN IP Address Pool for a specific device. I want to do this to prevent it from changing e.g. I will be pointing an Asterisk SIP Peer to it. Regards Michael Knill |
|
From: Lonnie A. <li...@lo...> - 2018-04-17 19:10:41
|
On Apr 17, 2018, at 12:43 PM, twanny Azzopardi <twa...@gm...> wrote: > Hello astlinux, > > I'm missing the wifi module? > > Regards, > Twanny. No Native Wireless (WiFi) support in AstLinux, since AstLinux 1.0.0, December 2011. Best to use an external access point. Lonnie |
|
From: twanny A. <twa...@gm...> - 2018-04-17 17:43:09
|
Hello astlinux, I'm missing the wifi module? Regards, Twanny. |
|
From: Lonnie A. <li...@lo...> - 2018-04-17 15:15:46
|
Hi Josh, Great to hear you got it working ! Lonnie On Apr 17, 2018, at 10:10 AM, Josh Alberts <jm...@ho...> wrote: > Oops, I managed to bump CTRL+ENTER. Continuing my response.... > > When I run the command you mention: > > pbx kd # show-union | grep '/etc/rc$' > /oldroot/mnt/asturw/etc/rc > > I reverted to the standard /etc/rc using the command you provided, created a /mnt/kd/rc.elocal, put the mkdir and mount commands there, ran chmod +x on it, restarted, and now everything is working! dahdi_cfg has ran and my channel bank is all green. Thank you so much! If only those pesky users would get the point that is clearly laid out in the documentation, and stop editing /etc/rc! And to be clear, in my post a few minutes ago, I misstated what I did - I added lines to /etc/rc to make my hard drive mount, not rc.conf. > > Josh > > From: Josh Alberts <jm...@ho...> > Sent: Tuesday, April 17, 2018 11:00 AM > To: AstLinux Users Mailing List > Subject: Re: [Astlinux-users] Problem Running dahdi_cfg > > Hey Lonnie! > > I certainly have edited rc.conf, and you caught me! I have an external USB hard drive (/dev/sdb2) that I use to store recordings of phone calls. I couldn't figure out how to get it to auto mount, so I ended up adding the following lines to rc.conf that did the trick: > > mkdir /mnt/usbhd > mount /dev/sdb2 /mnt/usbhd > > > From: Lonnie Abelbeck <li...@lo...> > Sent: Tuesday, April 17, 2018 8:47 AM > To: AstLinux Users Mailing List > Subject: Re: [Astlinux-users] Problem Running dahdi_cfg > > > On Apr 16, 2018, at 11:16 PM, Josh Alberts <jm...@ho...> wrote: > > > I'm on astlinux-1.3.2 i686 - Asterisk 13.18.5 and I'm setting up a new channel bank. I'm unable to run dahdi_cfg; I get the following error after it shows the (correct) channel map as defined in /etc/dahdi/system.conf: > > > > Unable to create 'dahdi_cfg' mutex: Read-only file system > > > > Here is the output of mount: > > > > rootfs on / type rootfs (rw) > > /dev/root on /oldroot type ext2 (rw,relatime) > > devtmpfs on /dev type devtmpfs (rw,relatime,size=512k,nr_inodes=221195,mode=755) > > /dev/sda2 on /oldroot/mnt/asturw type ext2 (rw,noatime,errors=continue) > > none on /oldroot/mnt/asturo type tmpfs (ro,relatime,size=114012k) > > none on / type unionfs (rw,relatime,dirs=/oldroot/mnt/asturw=rw:/oldroot/mnt/asturo=ro) > > none on /proc type proc (rw,relatime) > > none on /tmp type tmpfs (rw,relatime,size=10000k) > > none on /var type tmpfs (rw,relatime,size=10000k) > > none on /sys type sysfs (rw,relatime) > > none on /dev/pts type devpts (rw,relatime,mode=600) > > /dev/sdb2 on /mnt/usbhd type ext3 (rw,relatime,errors=continue,barrier=1,data=writeback) > > /dev/sda1 on /oldroot/cdrom type vfat (ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) > > > > I don't really know what's going on. FWIW, the light on my TE122P card is out, but it's showing in up dahdi_hardware: > > > > pci:0000:01:06.0 wcte12xp+ d161:8001 Wildcard TE122 > > > > And I have DAHDIMODS="wcte12xp" defined in /mnt/kd/rc.conf.d/user.conf. I have a feeling I'm doing (or not doing) something silly. Can someone please help me figure out why I can't run dahdi_cfg? Thanks! > > Hi Josh, > > Quick answer, it looks like you have edited the system initialization script /etc/rc in the past (a no-no :-) ) As such /dev/shm is not getting mounted, which is generating the "Unable to create 'dahdi_cfg' mutex:". > > More specifically ... > > Does this command generate any output ? > -- > show-union | grep '/etc/rc$' > -- > My guess is yes. Assuming so ... > > Determine what changes you made relative the of latest official /etc/rc > -- > diff -u /oldroot/mnt/asturo/etc/rc /oldroot/mnt/asturw/etc/rc > -- > > I'm assuming you made changes to mount your /mnt/usbhd as shown above ... a supported method to do so would be to create a bash script "/mnt/kd/rc.elocal" make it executable and put any initialization commands there. > > If you want to revert to the standard /etc/rc remove your edited version off unionfs by: > -- > rm /oldroot/mnt/asturw/etc/rc > -- > (and reboot) > > Worst case solution, you could add the one line to your edited /etc/rc that mounts /dev/shm on tmpfs, (and reboot). Fixes the problem today, causes problems down the road. > > Lonnie > > PS, just curious, can you explain why you need/want to mount /dev/sdb2 on /mnt/usbhd ? > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > 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.... > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > 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...> - 2018-04-17 15:12:20
|
> > Am 17.04.2018 um 17:00 schrieb Josh Alberts <jm...@ho... <mailto:jm...@ho...>>: > > Hey Lonnie! > > I certainly have edited rc.conf, and you caught me! I have an external USB hard drive (/dev/sdb2) that I use to store recordings of phone calls. I couldn't figure out how to get it to auto mount, so I ended up adding the following lines to rc.conf that did the trick: > > mkdir /mnt/usbhd > mount /dev/sdb2 /mnt/usbhd Please put these lines in "/mnt/kd/rc.elocal" Create it, if it does not exist and make it executable. > From: Lonnie Abelbeck <li...@lo...> > Sent: Tuesday, April 17, 2018 8:47 AM > To: AstLinux Users Mailing List > Subject: Re: [Astlinux-users] Problem Running dahdi_cfg > > > On Apr 16, 2018, at 11:16 PM, Josh Alberts <jm...@ho...> wrote: > >> I'm on astlinux-1.3.2 i686 - Asterisk 13.18.5 and I'm setting up a new channel bank. I'm unable to run dahdi_cfg; I get the following error after it shows the (correct) channel map as defined in /etc/dahdi/system.conf: >> >> Unable to create 'dahdi_cfg' mutex: Read-only file system >> >> Here is the output of mount: >> >> rootfs on / type rootfs (rw) >> /dev/root on /oldroot type ext2 (rw,relatime) >> devtmpfs on /dev type devtmpfs (rw,relatime,size=512k,nr_inodes=221195,mode=755) >> /dev/sda2 on /oldroot/mnt/asturw type ext2 (rw,noatime,errors=continue) >> none on /oldroot/mnt/asturo type tmpfs (ro,relatime,size=114012k) >> none on / type unionfs (rw,relatime,dirs=/oldroot/mnt/asturw=rw:/oldroot/mnt/asturo=ro) >> none on /proc type proc (rw,relatime) >> none on /tmp type tmpfs (rw,relatime,size=10000k) >> none on /var type tmpfs (rw,relatime,size=10000k) >> none on /sys type sysfs (rw,relatime) >> none on /dev/pts type devpts (rw,relatime,mode=600) >> /dev/sdb2 on /mnt/usbhd type ext3 (rw,relatime,errors=continue,barrier=1,data=writeback) >> /dev/sda1 on /oldroot/cdrom type vfat (ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) >> >> I don't really know what's going on. FWIW, the light on my TE122P card is out, but it's showing in up dahdi_hardware: >> >> pci:0000:01:06.0 wcte12xp+ d161:8001 Wildcard TE122 >> >> And I have DAHDIMODS="wcte12xp" defined in /mnt/kd/rc.conf.d/user.conf. I have a feeling I'm doing (or not doing) something silly. Can someone please help me figure out why I can't run dahdi_cfg? Thanks! > > Hi Josh, > > Quick answer, it looks like you have edited the system initialization script /etc/rc in the past (a no-no :-) ) As such /dev/shm is not getting mounted, which is generating the "Unable to create 'dahdi_cfg' mutex:". > > More specifically ... > > Does this command generate any output ? > -- > show-union | grep '/etc/rc$' > -- > My guess is yes. Assuming so ... > > Determine what changes you made relative the of latest official /etc/rc > -- > diff -u /oldroot/mnt/asturo/etc/rc /oldroot/mnt/asturw/etc/rc > -- > > I'm assuming you made changes to mount your /mnt/usbhd as shown above ... a supported method to do so would be to create a bash script "/mnt/kd/rc.elocal" make it executable and put any initialization commands there. > > If you want to revert to the standard /etc/rc remove your edited version off unionfs by: > -- > rm /oldroot/mnt/asturw/etc/rc > -- > (and reboot) > > Worst case solution, you could add the one line to your edited /etc/rc that mounts /dev/shm on tmpfs, (and reboot). Fixes the problem today, causes problems down the road. > > Lonnie > > PS, just curious, can you explain why you need/want to mount /dev/sdb2 on /mnt/usbhd ? Michael http://www.mksolutions.info |
|
From: Josh A. <jm...@ho...> - 2018-04-17 15:10:33
|
Oops, I managed to bump CTRL+ENTER. Continuing my response.... When I run the command you mention: pbx kd # show-union | grep '/etc/rc$' /oldroot/mnt/asturw/etc/rc I reverted to the standard /etc/rc using the command you provided, created a /mnt/kd/rc.elocal, put the mkdir and mount commands there, ran chmod +x on it, restarted, and now everything is working! dahdi_cfg has ran and my channel bank is all green. Thank you so much! If only those pesky users would get the point that is clearly laid out in the documentation, and stop editing /etc/rc! And to be clear, in my post a few minutes ago, I misstated what I did - I added lines to /etc/rc to make my hard drive mount, not rc.conf. Josh ________________________________ From: Josh Alberts <jm...@ho...> Sent: Tuesday, April 17, 2018 11:00 AM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] Problem Running dahdi_cfg Hey Lonnie! I certainly have edited rc.conf, and you caught me! I have an external USB hard drive (/dev/sdb2) that I use to store recordings of phone calls. I couldn't figure out how to get it to auto mount, so I ended up adding the following lines to rc.conf that did the trick: mkdir /mnt/usbhd mount /dev/sdb2 /mnt/usbhd ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Tuesday, April 17, 2018 8:47 AM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] Problem Running dahdi_cfg On Apr 16, 2018, at 11:16 PM, Josh Alberts <jm...@ho...> wrote: > I'm on astlinux-1.3.2 i686 - Asterisk 13.18.5 and I'm setting up a new channel bank. I'm unable to run dahdi_cfg; I get the following error after it shows the (correct) channel map as defined in /etc/dahdi/system.conf: > > Unable to create 'dahdi_cfg' mutex: Read-only file system > > Here is the output of mount: > > rootfs on / type rootfs (rw) > /dev/root on /oldroot type ext2 (rw,relatime) > devtmpfs on /dev type devtmpfs (rw,relatime,size=512k,nr_inodes=221195,mode=755) > /dev/sda2 on /oldroot/mnt/asturw type ext2 (rw,noatime,errors=continue) > none on /oldroot/mnt/asturo type tmpfs (ro,relatime,size=114012k) > none on / type unionfs (rw,relatime,dirs=/oldroot/mnt/asturw=rw:/oldroot/mnt/asturo=ro) > none on /proc type proc (rw,relatime) > none on /tmp type tmpfs (rw,relatime,size=10000k) > none on /var type tmpfs (rw,relatime,size=10000k) > none on /sys type sysfs (rw,relatime) > none on /dev/pts type devpts (rw,relatime,mode=600) > /dev/sdb2 on /mnt/usbhd type ext3 (rw,relatime,errors=continue,barrier=1,data=writeback) > /dev/sda1 on /oldroot/cdrom type vfat (ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) > > I don't really know what's going on. FWIW, the light on my TE122P card is out, but it's showing in up dahdi_hardware: > > pci:0000:01:06.0 wcte12xp+ d161:8001 Wildcard TE122 > > And I have DAHDIMODS="wcte12xp" defined in /mnt/kd/rc.conf.d/user.conf. I have a feeling I'm doing (or not doing) something silly. Can someone please help me figure out why I can't run dahdi_cfg? Thanks! Hi Josh, Quick answer, it looks like you have edited the system initialization script /etc/rc in the past (a no-no :-) ) As such /dev/shm is not getting mounted, which is generating the "Unable to create 'dahdi_cfg' mutex:". More specifically ... Does this command generate any output ? -- show-union | grep '/etc/rc$' -- My guess is yes. Assuming so ... Determine what changes you made relative the of latest official /etc/rc -- diff -u /oldroot/mnt/asturo/etc/rc /oldroot/mnt/asturw/etc/rc -- I'm assuming you made changes to mount your /mnt/usbhd as shown above ... a supported method to do so would be to create a bash script "/mnt/kd/rc.elocal" make it executable and put any initialization commands there. If you want to revert to the standard /etc/rc remove your edited version off unionfs by: -- rm /oldroot/mnt/asturw/etc/rc -- (and reboot) Worst case solution, you could add the one line to your edited /etc/rc that mounts /dev/shm on tmpfs, (and reboot). Fixes the problem today, causes problems down the road. Lonnie PS, just curious, can you explain why you need/want to mount /dev/sdb2 on /mnt/usbhd ? ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ 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: Josh A. <jm...@ho...> - 2018-04-17 15:00:52
|
Hey Lonnie! I certainly have edited rc.conf, and you caught me! I have an external USB hard drive (/dev/sdb2) that I use to store recordings of phone calls. I couldn't figure out how to get it to auto mount, so I ended up adding the following lines to rc.conf that did the trick: mkdir /mnt/usbhd mount /dev/sdb2 /mnt/usbhd ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Tuesday, April 17, 2018 8:47 AM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] Problem Running dahdi_cfg On Apr 16, 2018, at 11:16 PM, Josh Alberts <jm...@ho...> wrote: > I'm on astlinux-1.3.2 i686 - Asterisk 13.18.5 and I'm setting up a new channel bank. I'm unable to run dahdi_cfg; I get the following error after it shows the (correct) channel map as defined in /etc/dahdi/system.conf: > > Unable to create 'dahdi_cfg' mutex: Read-only file system > > Here is the output of mount: > > rootfs on / type rootfs (rw) > /dev/root on /oldroot type ext2 (rw,relatime) > devtmpfs on /dev type devtmpfs (rw,relatime,size=512k,nr_inodes=221195,mode=755) > /dev/sda2 on /oldroot/mnt/asturw type ext2 (rw,noatime,errors=continue) > none on /oldroot/mnt/asturo type tmpfs (ro,relatime,size=114012k) > none on / type unionfs (rw,relatime,dirs=/oldroot/mnt/asturw=rw:/oldroot/mnt/asturo=ro) > none on /proc type proc (rw,relatime) > none on /tmp type tmpfs (rw,relatime,size=10000k) > none on /var type tmpfs (rw,relatime,size=10000k) > none on /sys type sysfs (rw,relatime) > none on /dev/pts type devpts (rw,relatime,mode=600) > /dev/sdb2 on /mnt/usbhd type ext3 (rw,relatime,errors=continue,barrier=1,data=writeback) > /dev/sda1 on /oldroot/cdrom type vfat (ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) > > I don't really know what's going on. FWIW, the light on my TE122P card is out, but it's showing in up dahdi_hardware: > > pci:0000:01:06.0 wcte12xp+ d161:8001 Wildcard TE122 > > And I have DAHDIMODS="wcte12xp" defined in /mnt/kd/rc.conf.d/user.conf. I have a feeling I'm doing (or not doing) something silly. Can someone please help me figure out why I can't run dahdi_cfg? Thanks! Hi Josh, Quick answer, it looks like you have edited the system initialization script /etc/rc in the past (a no-no :-) ) As such /dev/shm is not getting mounted, which is generating the "Unable to create 'dahdi_cfg' mutex:". More specifically ... Does this command generate any output ? -- show-union | grep '/etc/rc$' -- My guess is yes. Assuming so ... Determine what changes you made relative the of latest official /etc/rc -- diff -u /oldroot/mnt/asturo/etc/rc /oldroot/mnt/asturw/etc/rc -- I'm assuming you made changes to mount your /mnt/usbhd as shown above ... a supported method to do so would be to create a bash script "/mnt/kd/rc.elocal" make it executable and put any initialization commands there. If you want to revert to the standard /etc/rc remove your edited version off unionfs by: -- rm /oldroot/mnt/asturw/etc/rc -- (and reboot) Worst case solution, you could add the one line to your edited /etc/rc that mounts /dev/shm on tmpfs, (and reboot). Fixes the problem today, causes problems down the road. Lonnie PS, just curious, can you explain why you need/want to mount /dev/sdb2 on /mnt/usbhd ? ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ 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...> - 2018-04-17 13:06:37
|
On Apr 16, 2018, at 11:16 PM, Josh Alberts <jm...@ho...> wrote: > I'm on astlinux-1.3.2 i686 - Asterisk 13.18.5 and I'm setting up a new channel bank. I'm unable to run dahdi_cfg; I get the following error after it shows the (correct) channel map as defined in /etc/dahdi/system.conf: > > Unable to create 'dahdi_cfg' mutex: Read-only file system > > Here is the output of mount: > > rootfs on / type rootfs (rw) > /dev/root on /oldroot type ext2 (rw,relatime) > devtmpfs on /dev type devtmpfs (rw,relatime,size=512k,nr_inodes=221195,mode=755) > /dev/sda2 on /oldroot/mnt/asturw type ext2 (rw,noatime,errors=continue) > none on /oldroot/mnt/asturo type tmpfs (ro,relatime,size=114012k) > none on / type unionfs (rw,relatime,dirs=/oldroot/mnt/asturw=rw:/oldroot/mnt/asturo=ro) > none on /proc type proc (rw,relatime) > none on /tmp type tmpfs (rw,relatime,size=10000k) > none on /var type tmpfs (rw,relatime,size=10000k) > none on /sys type sysfs (rw,relatime) > none on /dev/pts type devpts (rw,relatime,mode=600) > /dev/sdb2 on /mnt/usbhd type ext3 (rw,relatime,errors=continue,barrier=1,data=writeback) > /dev/sda1 on /oldroot/cdrom type vfat (ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) > > I don't really know what's going on. FWIW, the light on my TE122P card is out, but it's showing in up dahdi_hardware: > > pci:0000:01:06.0 wcte12xp+ d161:8001 Wildcard TE122 > > And I have DAHDIMODS="wcte12xp" defined in /mnt/kd/rc.conf.d/user.conf. I have a feeling I'm doing (or not doing) something silly. Can someone please help me figure out why I can't run dahdi_cfg? Thanks! Hi Josh, Quick answer, it looks like you have edited the system initialization script /etc/rc in the past (a no-no :-) ) As such /dev/shm is not getting mounted, which is generating the "Unable to create 'dahdi_cfg' mutex:". More specifically ... Does this command generate any output ? -- show-union | grep '/etc/rc$' -- My guess is yes. Assuming so ... Determine what changes you made relative the of latest official /etc/rc -- diff -u /oldroot/mnt/asturo/etc/rc /oldroot/mnt/asturw/etc/rc -- I'm assuming you made changes to mount your /mnt/usbhd as shown above ... a supported method to do so would be to create a bash script "/mnt/kd/rc.elocal" make it executable and put any initialization commands there. If you want to revert to the standard /etc/rc remove your edited version off unionfs by: -- rm /oldroot/mnt/asturw/etc/rc -- (and reboot) Worst case solution, you could add the one line to your edited /etc/rc that mounts /dev/shm on tmpfs, (and reboot). Fixes the problem today, causes problems down the road. Lonnie PS, just curious, can you explain why you need/want to mount /dev/sdb2 on /mnt/usbhd ? |
|
From: twanny A. <twa...@gm...> - 2018-04-17 13:03:11
|
Hello Michael Knill Installed. Thank you, Twanny. On Tue, Apr 17, 2018 at 1:49 PM, Michael Knill < mic...@ip...> wrote: > Hi Twanny > > > > You need to extract the .img file from ISO and dd to the ALIX compact > flash. > > The ISO is an installer that you place on a USB or CD that writes to > internal storage. I think you are not able to boot from USB on the ALIX. > > PS I would recommend the APU2 as the ALIX is getting pretty old and I have > had lots of issues with running out of resources with the later Astlinux > versions. > > > > https://doc.astlinux-project.org/userdoc:new-install > > > > Regards > > Michael Knill > > *From: *twanny Azzopardi <twa...@gm...> > *Reply-To: *AstLinux List <ast...@li...> > *Date: *Tuesday, 17 April 2018 at 9:31 pm > *To: *AstLinux List <ast...@li...> > *Subject: *[Astlinux-users] Installing astlinux-1.2.10-alix-serial.iso > > > > Hello astlinux, > > > > I'm trying to install astlinux-1.2.10-alix-serial.iso onto my old Alix.2d > board. > > > > I'm doing dd if= astlinux-1.2.10-alix-serial.iso of=/dev/sdb. Then from > the console I get missing NTLDR! > > > > What am I doing wrong? > > > > Regards, > > Twanny. > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > 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...> - 2018-04-17 12:05:20
|
Hi Twanny You need to extract the .img file from ISO and dd to the ALIX compact flash. The ISO is an installer that you place on a USB or CD that writes to internal storage. I think you are not able to boot from USB on the ALIX. PS I would recommend the APU2 as the ALIX is getting pretty old and I have had lots of issues with running out of resources with the later Astlinux versions. https://doc.astlinux-project.org/userdoc:new-install Regards Michael Knill From: twanny Azzopardi <twa...@gm...> Reply-To: AstLinux List <ast...@li...> Date: Tuesday, 17 April 2018 at 9:31 pm To: AstLinux List <ast...@li...> Subject: [Astlinux-users] Installing astlinux-1.2.10-alix-serial.iso Hello astlinux, I'm trying to install astlinux-1.2.10-alix-serial.iso onto my old Alix.2d board. I'm doing dd if= astlinux-1.2.10-alix-serial.iso of=/dev/sdb. Then from the console I get missing NTLDR! What am I doing wrong? Regards, Twanny. |
|
From: Michael K. <li...@mk...> - 2018-04-17 11:50:07
|
> Am 17.04.2018 um 13:21 schrieb twanny Azzopardi <twa...@gm...>: > > Hello astlinux, > > I'm trying to install astlinux-1.2.10-alix-serial.iso onto my old Alix.2d board. > > I'm doing dd if= astlinux-1.2.10-alix-serial.iso of=/dev/sdb. Then from the console I get missing NTLDR! > > What am I doing wrong? > > Regards, > Twanny. Hi Twanny, see: https://doc.astlinux.org/userdoc:new-install In your case: • Mount the ISO Installer image and manually extract the desired .img.gz file from the “os” directory, gunzip and dd to a destination disk. Not the complete ISO as you tried. Michael http://www.mksolutions.info |
|
From: twanny A. <twa...@gm...> - 2018-04-17 11:30:34
|
Hello astlinux, I'm trying to install astlinux-1.2.10-alix-serial.iso onto my old Alix.2d board. I'm doing dd if= astlinux-1.2.10-alix-serial.iso of=/dev/sdb. Then from the console I get missing NTLDR! What am I doing wrong? Regards, Twanny. |
|
From: Josh A. <jm...@ho...> - 2018-04-17 04:17:56
|
I'm on astlinux-1.3.2 i686 - Asterisk 13.18.5 and I'm setting up a new channel bank. I'm unable to run dahdi_cfg; I get the following error after it shows the (correct) channel map as defined in /etc/dahdi/system.conf: Unable to create 'dahdi_cfg' mutex: Read-only file system Here is the output of mount: rootfs on / type rootfs (rw) /dev/root on /oldroot type ext2 (rw,relatime) devtmpfs on /dev type devtmpfs (rw,relatime,size=512k,nr_inodes=221195,mode=755) /dev/sda2 on /oldroot/mnt/asturw type ext2 (rw,noatime,errors=continue) none on /oldroot/mnt/asturo type tmpfs (ro,relatime,size=114012k) none on / type unionfs (rw,relatime,dirs=/oldroot/mnt/asturw=rw:/oldroot/mnt/asturo=ro) none on /proc type proc (rw,relatime) none on /tmp type tmpfs (rw,relatime,size=10000k) none on /var type tmpfs (rw,relatime,size=10000k) none on /sys type sysfs (rw,relatime) none on /dev/pts type devpts (rw,relatime,mode=600) /dev/sdb2 on /mnt/usbhd type ext3 (rw,relatime,errors=continue,barrier=1,data=writeback) /dev/sda1 on /oldroot/cdrom type vfat (ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) I don't really know what's going on. FWIW, the light on my TE122P card is out, but it's showing in up dahdi_hardware: pci:0000:01:06.0 wcte12xp+ d161:8001 Wildcard TE122 And I have DAHDIMODS="wcte12xp" defined in /mnt/kd/rc.conf.d/user.conf. I have a feeling I'm doing (or not doing) something silly. Can someone please help me figure out why I can't run dahdi_cfg? Thanks! |
|
From: Shamus R. <sh...@sr...> - 2018-04-17 01:32:58
|
Here is my scenario. I have an Asterisk 13 server with a publicly accessible IP. On the same server, I’ve installed OpenVPN server. At my office, I have a Ubiquity router running an OpenVPN client to my Asterisk box. My SIP phones are behind this router and I’m trying to get them to register. Any help would be appreciated! Asterisk & OpenVPN server: ip = 142.1.1.1 tun0 = 10.8.8.1 P-t-P: 10.8.8.2 Ubiquity router: vtun0 = 10.8.8.10 Clients behind Ubiquity router: 192.168.2.0/24 sip.conf: [general] … udpbindaddr=0.0.0.0 localnet=10.0.0.0/8 localnet=172.16.0.0/12 localnet=192.168.0.0/16 externaddr=142.1.1.1 … [remotePhoneEntry] ... type=friend host=dynamic nat=force_rport,comedia … On my phones, I have entered the the following: Server = 10.8.8.1 Username = remotePhoneEntry Secret ... |
|
From: Shamus R. <sh...@sr...> - 2018-04-15 14:39:04
|
I learnt something… apparently you need to restart Asterisk for it to re-parse modules.conf. I assumed doing a “core reload” or “module reload” would be sufficient. Thanks for your suggestions! Shamus |
|
From: Michael K. <li...@mk...> - 2018-04-15 10:06:44
|
> Am 15.04.2018 um 01:31 schrieb Michael Knill <mic...@ip...>: > > Hi Shamus > > Not sure what that is but I cant see noload => coreres_pjsip_authenticator_digest.so in the list? > > Regards > Michael Knill I think you need at least "asterisk.conf" in "/etc/asterisk/" to define where Asterisk does look for its files. > On 15/4/18, 4:16 am, "Shamus Rask" <sh...@sr...> wrote: > > I’m running a default installation of Asterisk 13 on Ubuntu 16.04. Currently trying to “skinnify” Asterisk to minimize the attack surface and resource usage. > > In /etc/asterisk, I currently see the following: > total 16 > drwxr-xr-x 3 asterisk asterisk 4096 Apr 14 14:11 . > drwxr-xr-x 96 root root 4096 Apr 13 12:58 .. > drwxrwx--- 3 root root 4096 Apr 14 12:48 default > -rw-r----- 1 asterisk asterisk 3932 Apr 14 14:04 modules.conf > > I’ve purposefully removed all other .conf files. When I reload Asterisk, it is still showing that all modules are being loaded: > server*CLI> module show like res_pjsip > Module Description Use Count Status Support Levelres_pjsip.so Basic SIP resource 29 Running coreres_pjsip_acl.so PJSIP ACL Resource 0 Running coreres_pjsip_authenticator_digest.so PJSIP authentication resource 0 Running coreres_pjsip_caller_id.so PJSIP Caller ID Support 0 Running core > > What am I doing wrong? Why is Asterisk ignoring all of my noloads? > > In modules.conf, I have the following: > [modules] > autoload=yes > > ; Channel Event Logging modules are not used so removed > noload => cel_custom.so > noload => cel_manager.so > noload => cel_odbc.so > noload => cel_sqlite3_custom.so > noload => app_celgenuserevent.so > > ; PJSIP is disabled until we are ready to use it > noload => res_pjproject.so > noload => res_pjsip.so > noload => res_pjsip_acl.so > noload => res_pjsip_authenticator_digest.so > noload => res_pjsip_caller_id.so > noload => res_pjsip_config_wizard.so > noload => res_pjsip_dialog_info_body_generator.so > noload => res_pjsip_diversion.so > noload => res_pjsip_dlg_options.so > noload => res_pjsip_dtmf_info.so > noload => res_pjsip_empty_info.so > noload => res_pjsip_endpoint_identifier_anonymous.so > noload => res_pjsip_endpoint_identifier_ip.so > noload => res_pjsip_endpoint_identifier_user.so > noload => res_pjsip_exten_state.so > noload => res_pjsip_header_funcs.so > noload => res_pjsip_history.so > noload => res_pjsip_logger.so > noload => res_pjsip_messaging.so > noload => res_pjsip_mwi.so > noload => res_pjsip_mwi_body_generator.so > noload => res_pjsip_nat.so > noload => res_pjsip_notify.so > noload => res_pjsip_one_touch_record_info.so > noload => res_pjsip_outbound_authenticator_digest.so > noload => res_pjsip_outbound_publish.so > noload => res_pjsip_outbound_registration.so > noload => res_pjsip_path.so > noload => res_pjsip_pidf_body_generator.so > noload => res_pjsip_pidf_digium_body_supplement.so > noload => res_pjsip_pidf_eyebeam_body_supplement.so > noload => res_pjsip_publish_asterisk.so > noload => res_pjsip_pubsub.so > noload => res_pjsip_refer.so > noload => res_pjsip_registrar.so > noload => res_pjsip_registrar_expire.so > noload => res_pjsip_rfc3326.so > noload => res_pjsip_sdp_rtp.so > noload => res_pjsip_send_to_voicemail.so > noload => res_pjsip_session.so > noload => res_pjsip_sips_contact.so > noload => res_pjsip_t38.so > noload => res_pjsip_transport_management.so > noload => res_pjsip_transport_websocket.so > noload => res_pjsip_xpidf_body_generator.so > noload => func_pjsip_aor.so > noload => func_pjsip_contact.so > noload => func_pjsip_endpoint.so > > ; ARI needs to go to unless I have a need for it > noload => res_ari.so > noload => res_ari_applications.so > noload => res_ari_asterisk.so > noload => res_ari_bridges.so > noload => res_ari_channels.so > noload => res_ari_device_states.so > noload => res_ari_endpoints.so > noload => res_ari_events.so > noload => res_ari_model.so > noload => res_ari_playbacks.so > noload => res_ari_recordings.so > noload => res_ari_sounds.so > > ; We are not using Homer so it is disabled > noload => res_hep.so > noload => res_hep_pjsip.so > noload => res_hep_rtcp.so > > ; Other resource modules currently not needed > noload => res_speech.so > noload => res_phoneprov.so > noload => res_ael_share.so > noload => res_adsi.so > noload => res_smdi.so > noload => res_fax.so > noload => res_fax_spandsp.so > noload => res_stun_monitor.so > noload => res_pktccops.so > > ; PBX modules currently not needed > noload => pbx_ael.so > noload => pbx_dundi.so > > ; Channel modules currently not needed > noload => chan_oss.so > noload => chan_mgcp.so > noload => chan_skinny.so > noload => chan_phone.so > noload => chan_agent.so > noload => chan_unistim.so > noload => chan_alsa.so > noload => chan_iax2.so > > ; Other application modules currently not needed > noload => app_nbscat.so > noload => app_amd.so > noload => app_mp3.so > noload => app_minivm.so > noload => app_zapateller.so > noload => app_ices.so > noload => app_sendtext.so > noload => app_speech_utils.so > noload => app_flash.so > noload => app_getcpeid.so > noload => app_setcallerid.so > noload => app_adsiprog.so > noload => app_forkcdr.so > noload => app_sms.so > noload => app_morsecode.so > noload => app_url.so > noload => app_alarmreceiver.so > noload => app_dahdiras.so > noload => app_senddtmf.so > noload => app_test.so > noload => app_externalivr.so > noload => app_image.so > noload => app_festival.so > > ; Using SQLight3 so get rid of all the others > noload => cdr_csv.so > noload => cdr_custom.so > noload => cdr_manager.so > noload => cdr_syslog.so > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > 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.... > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > 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.... Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2018-04-14 23:47:55
|
Hi Shamus
Not sure what that is but I cant see noload => coreres_pjsip_authenticator_digest.so in the list?
Regards
Michael Knill
On 15/4/18, 4:16 am, "Shamus Rask" <sh...@sr...> wrote:
I’m running a default installation of Asterisk 13 on Ubuntu 16.04. Currently trying to “skinnify” Asterisk to minimize the attack surface and resource usage.
In /etc/asterisk, I currently see the following:
total 16
drwxr-xr-x 3 asterisk asterisk 4096 Apr 14 14:11 .
drwxr-xr-x 96 root root 4096 Apr 13 12:58 ..
drwxrwx--- 3 root root 4096 Apr 14 12:48 default
-rw-r----- 1 asterisk asterisk 3932 Apr 14 14:04 modules.conf
I’ve purposefully removed all other .conf files. When I reload Asterisk, it is still showing that all modules are being loaded:
server*CLI> module show like res_pjsip
Module Description Use Count Status Support Levelres_pjsip.so Basic SIP resource 29 Running coreres_pjsip_acl.so PJSIP ACL Resource 0 Running coreres_pjsip_authenticator_digest.so PJSIP authentication resource 0 Running coreres_pjsip_caller_id.so PJSIP Caller ID Support 0 Running core
What am I doing wrong? Why is Asterisk ignoring all of my noloads?
In modules.conf, I have the following:
[modules]
autoload=yes
; Channel Event Logging modules are not used so removed
noload => cel_custom.so
noload => cel_manager.so
noload => cel_odbc.so
noload => cel_sqlite3_custom.so
noload => app_celgenuserevent.so
; PJSIP is disabled until we are ready to use it
noload => res_pjproject.so
noload => res_pjsip.so
noload => res_pjsip_acl.so
noload => res_pjsip_authenticator_digest.so
noload => res_pjsip_caller_id.so
noload => res_pjsip_config_wizard.so
noload => res_pjsip_dialog_info_body_generator.so
noload => res_pjsip_diversion.so
noload => res_pjsip_dlg_options.so
noload => res_pjsip_dtmf_info.so
noload => res_pjsip_empty_info.so
noload => res_pjsip_endpoint_identifier_anonymous.so
noload => res_pjsip_endpoint_identifier_ip.so
noload => res_pjsip_endpoint_identifier_user.so
noload => res_pjsip_exten_state.so
noload => res_pjsip_header_funcs.so
noload => res_pjsip_history.so
noload => res_pjsip_logger.so
noload => res_pjsip_messaging.so
noload => res_pjsip_mwi.so
noload => res_pjsip_mwi_body_generator.so
noload => res_pjsip_nat.so
noload => res_pjsip_notify.so
noload => res_pjsip_one_touch_record_info.so
noload => res_pjsip_outbound_authenticator_digest.so
noload => res_pjsip_outbound_publish.so
noload => res_pjsip_outbound_registration.so
noload => res_pjsip_path.so
noload => res_pjsip_pidf_body_generator.so
noload => res_pjsip_pidf_digium_body_supplement.so
noload => res_pjsip_pidf_eyebeam_body_supplement.so
noload => res_pjsip_publish_asterisk.so
noload => res_pjsip_pubsub.so
noload => res_pjsip_refer.so
noload => res_pjsip_registrar.so
noload => res_pjsip_registrar_expire.so
noload => res_pjsip_rfc3326.so
noload => res_pjsip_sdp_rtp.so
noload => res_pjsip_send_to_voicemail.so
noload => res_pjsip_session.so
noload => res_pjsip_sips_contact.so
noload => res_pjsip_t38.so
noload => res_pjsip_transport_management.so
noload => res_pjsip_transport_websocket.so
noload => res_pjsip_xpidf_body_generator.so
noload => func_pjsip_aor.so
noload => func_pjsip_contact.so
noload => func_pjsip_endpoint.so
; ARI needs to go to unless I have a need for it
noload => res_ari.so
noload => res_ari_applications.so
noload => res_ari_asterisk.so
noload => res_ari_bridges.so
noload => res_ari_channels.so
noload => res_ari_device_states.so
noload => res_ari_endpoints.so
noload => res_ari_events.so
noload => res_ari_model.so
noload => res_ari_playbacks.so
noload => res_ari_recordings.so
noload => res_ari_sounds.so
; We are not using Homer so it is disabled
noload => res_hep.so
noload => res_hep_pjsip.so
noload => res_hep_rtcp.so
; Other resource modules currently not needed
noload => res_speech.so
noload => res_phoneprov.so
noload => res_ael_share.so
noload => res_adsi.so
noload => res_smdi.so
noload => res_fax.so
noload => res_fax_spandsp.so
noload => res_stun_monitor.so
noload => res_pktccops.so
; PBX modules currently not needed
noload => pbx_ael.so
noload => pbx_dundi.so
; Channel modules currently not needed
noload => chan_oss.so
noload => chan_mgcp.so
noload => chan_skinny.so
noload => chan_phone.so
noload => chan_agent.so
noload => chan_unistim.so
noload => chan_alsa.so
noload => chan_iax2.so
; Other application modules currently not needed
noload => app_nbscat.so
noload => app_amd.so
noload => app_mp3.so
noload => app_minivm.so
noload => app_zapateller.so
noload => app_ices.so
noload => app_sendtext.so
noload => app_speech_utils.so
noload => app_flash.so
noload => app_getcpeid.so
noload => app_setcallerid.so
noload => app_adsiprog.so
noload => app_forkcdr.so
noload => app_sms.so
noload => app_morsecode.so
noload => app_url.so
noload => app_alarmreceiver.so
noload => app_dahdiras.so
noload => app_senddtmf.so
noload => app_test.so
noload => app_externalivr.so
noload => app_image.so
noload => app_festival.so
; Using SQLight3 so get rid of all the others
noload => cdr_csv.so
noload => cdr_custom.so
noload => cdr_manager.so
noload => cdr_syslog.so
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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: Shamus R. <sh...@sr...> - 2018-04-14 18:16:32
|
I’m running a default installation of Asterisk 13 on Ubuntu 16.04. Currently trying to “skinnify” Asterisk to minimize the attack surface and resource usage. In /etc/asterisk, I currently see the following: total 16 drwxr-xr-x 3 asterisk asterisk 4096 Apr 14 14:11 . drwxr-xr-x 96 root root 4096 Apr 13 12:58 .. drwxrwx--- 3 root root 4096 Apr 14 12:48 default -rw-r----- 1 asterisk asterisk 3932 Apr 14 14:04 modules.conf I’ve purposefully removed all other .conf files. When I reload Asterisk, it is still showing that all modules are being loaded: server*CLI> module show like res_pjsip Module Description Use Count Status Support Levelres_pjsip.so Basic SIP resource 29 Running coreres_pjsip_acl.so PJSIP ACL Resource 0 Running coreres_pjsip_authenticator_digest.so PJSIP authentication resource 0 Running coreres_pjsip_caller_id.so PJSIP Caller ID Support 0 Running core What am I doing wrong? Why is Asterisk ignoring all of my noloads? In modules.conf, I have the following: [modules] autoload=yes ; Channel Event Logging modules are not used so removed noload => cel_custom.so noload => cel_manager.so noload => cel_odbc.so noload => cel_sqlite3_custom.so noload => app_celgenuserevent.so ; PJSIP is disabled until we are ready to use it noload => res_pjproject.so noload => res_pjsip.so noload => res_pjsip_acl.so noload => res_pjsip_authenticator_digest.so noload => res_pjsip_caller_id.so noload => res_pjsip_config_wizard.so noload => res_pjsip_dialog_info_body_generator.so noload => res_pjsip_diversion.so noload => res_pjsip_dlg_options.so noload => res_pjsip_dtmf_info.so noload => res_pjsip_empty_info.so noload => res_pjsip_endpoint_identifier_anonymous.so noload => res_pjsip_endpoint_identifier_ip.so noload => res_pjsip_endpoint_identifier_user.so noload => res_pjsip_exten_state.so noload => res_pjsip_header_funcs.so noload => res_pjsip_history.so noload => res_pjsip_logger.so noload => res_pjsip_messaging.so noload => res_pjsip_mwi.so noload => res_pjsip_mwi_body_generator.so noload => res_pjsip_nat.so noload => res_pjsip_notify.so noload => res_pjsip_one_touch_record_info.so noload => res_pjsip_outbound_authenticator_digest.so noload => res_pjsip_outbound_publish.so noload => res_pjsip_outbound_registration.so noload => res_pjsip_path.so noload => res_pjsip_pidf_body_generator.so noload => res_pjsip_pidf_digium_body_supplement.so noload => res_pjsip_pidf_eyebeam_body_supplement.so noload => res_pjsip_publish_asterisk.so noload => res_pjsip_pubsub.so noload => res_pjsip_refer.so noload => res_pjsip_registrar.so noload => res_pjsip_registrar_expire.so noload => res_pjsip_rfc3326.so noload => res_pjsip_sdp_rtp.so noload => res_pjsip_send_to_voicemail.so noload => res_pjsip_session.so noload => res_pjsip_sips_contact.so noload => res_pjsip_t38.so noload => res_pjsip_transport_management.so noload => res_pjsip_transport_websocket.so noload => res_pjsip_xpidf_body_generator.so noload => func_pjsip_aor.so noload => func_pjsip_contact.so noload => func_pjsip_endpoint.so ; ARI needs to go to unless I have a need for it noload => res_ari.so noload => res_ari_applications.so noload => res_ari_asterisk.so noload => res_ari_bridges.so noload => res_ari_channels.so noload => res_ari_device_states.so noload => res_ari_endpoints.so noload => res_ari_events.so noload => res_ari_model.so noload => res_ari_playbacks.so noload => res_ari_recordings.so noload => res_ari_sounds.so ; We are not using Homer so it is disabled noload => res_hep.so noload => res_hep_pjsip.so noload => res_hep_rtcp.so ; Other resource modules currently not needed noload => res_speech.so noload => res_phoneprov.so noload => res_ael_share.so noload => res_adsi.so noload => res_smdi.so noload => res_fax.so noload => res_fax_spandsp.so noload => res_stun_monitor.so noload => res_pktccops.so ; PBX modules currently not needed noload => pbx_ael.so noload => pbx_dundi.so ; Channel modules currently not needed noload => chan_oss.so noload => chan_mgcp.so noload => chan_skinny.so noload => chan_phone.so noload => chan_agent.so noload => chan_unistim.so noload => chan_alsa.so noload => chan_iax2.so ; Other application modules currently not needed noload => app_nbscat.so noload => app_amd.so noload => app_mp3.so noload => app_minivm.so noload => app_zapateller.so noload => app_ices.so noload => app_sendtext.so noload => app_speech_utils.so noload => app_flash.so noload => app_getcpeid.so noload => app_setcallerid.so noload => app_adsiprog.so noload => app_forkcdr.so noload => app_sms.so noload => app_morsecode.so noload => app_url.so noload => app_alarmreceiver.so noload => app_dahdiras.so noload => app_senddtmf.so noload => app_test.so noload => app_externalivr.so noload => app_image.so noload => app_festival.so ; Using SQLight3 so get rid of all the others noload => cdr_csv.so noload => cdr_custom.so noload => cdr_manager.so noload => cdr_syslog.so |
|
From: Michael K. <li...@mk...> - 2018-04-10 12:51:17
|
> Am 10.04.2018 um 13:43 schrieb Michael Keuter <li...@mk...>: > >> >> Am 10.04.2018 um 13:37 schrieb Michael Knill <mic...@ip...>: >> >> Here’s an interesting one as an FYI. >> >> I have one provider that I use (have to unfortunately) that requires registration. >> Very occasionally the trunk lost its registration and it could not receive incoming calls and I couldn't work it out. >> Recently I had this happen which affected all my trunks to this provider so I rang up the provider and found that their SBC cluster had failed over that evening due to a network issue. >> After doing some debugging, I found that Asterisk was not registering any more and would not start again until a reload was done. Why? >> >> Well I found this sip.conf parameter: >> register_retry_403 - This will cause Asterisk to treat 403 responses to registrations as if they were 401 responses and continue retrying according to normal retry rules. It is set to no by default e.g. it will stop trying to register if it gets a 403 – Forbidden ☹ >> >> I got the provider to do a debug from my IP Address after the failover and you guessed it, 403 – Forbidden was sent during the failover which I understand is during the settling period. >> I have now set this to yes and hopefully we don't have this issue again. >> >> Regards >> Michael Knill > > Thanks, that sounds interesting. > I will keep an eye on that, the next time I have registration issues. > > Michael Hi Michael, I found this related: https://community.freepbx.org/t/sip-trunk-turns-to-rejected-and-only-re-registers-after-a-reload/44552 Michael http://www.mksolutions.info |
|
From: Michael K. <li...@mk...> - 2018-04-10 11:43:47
|
> Am 10.04.2018 um 13:37 schrieb Michael Knill <mic...@ip...>: > > Here’s an interesting one as an FYI. > > I have one provider that I use (have to unfortunately) that requires registration. > Very occasionally the trunk lost its registration and it could not receive incoming calls and I couldn't work it out. > Recently I had this happen which affected all my trunks to this provider so I rang up the provider and found that their SBC cluster had failed over that evening due to a network issue. > After doing some debugging, I found that Asterisk was not registering any more and would not start again until a reload was done. Why? > > Well I found this sip.conf parameter: > register_retry_403 - This will cause Asterisk to treat 403 responses to registrations as if they were 401 responses and continue retrying according to normal retry rules. It is set to no by default e.g. it will stop trying to register if it gets a 403 – Forbidden ☹ > > I got the provider to do a debug from my IP Address after the failover and you guessed it, 403 – Forbidden was sent during the failover which I understand is during the settling period. > I have now set this to yes and hopefully we don't have this issue again. > > Regards > Michael Knill Thanks, that sounds interesting. I will keep an eye on that, the next time I have registration issues. Michael http://www.mksolutions.info |
63 messages has been excluded from this view by a project administrator.
