astlinux-users — AstLinux Users Mailing List

Re: [Astlinux-users] 4G backup

[David K. <da...@ke...>]

Thanks to last nights storm that hit the northeast, I spent what spare time
I had today investigating WAN failover.  It took a while to get working,
though exactly why I don't know because what I ended up with as a working
config is exactly what Lonnie has documented!  I suspect my testing was
impacted by trying to do it from my basement (where I get one bar of 4G on
AT&T, (aka 3.5G in the rest of the world, not LTE).  Upstairs I get a
decent 3 bars LTE.

I found an old TP-LINK WiFi in a drawer which supports bridge mode.  So
what I have is APU2 eth2 -> TL-WR702N -> iPhone -> AT&T.  As  I write this
it is my active connection as power and internet are not back yet.  This is
okay as an occasional use setup as the WiFi link to iPhone does not appear
to connect automatically. I seem to need to go into the router (bridge) web
interface and scan for the iPhone hotspot and connect to it... the issue
seams to be that the iPhone can decide to change WiFi channel, and the
router wants me to select a specific channel (it has an auto setting, but
doesn't seem to like it if I select that -- though further testing
required).

Which got me googling and I landed on the same Netgear modem.  They have a
LB1121 version (adds PoE support, you need to buy your own PoE injector)
which I find attractive because PoE would give me flexibility to place the
modem anywhere in my house and have it powered from my large UPS that
Astlinux is connected to.  So for as long as I have enough battery to power
AstLinux, I will have a cell connection.  I can last about 8 hours on that
UPS.

So much now-a-days depends on a network connection that I am tempted to buy.

Now I would need to figure out entries for the failover script.  For
example, I would want to block all traffic from my NAS (which has online
backup setup), so some firewall rules to block all traffic from certain
internal IP's.  I might also want to block selected ports which I know are
used for an online backup that is installed on my work laptop.  Would be
nice if I could block youtube too (kids, you know), and maybe dropbox,
etc.  Basically I want to keep network activity to the essentials.  Any
ideas?

David

On Wed, May 16, 2018 at 6:15 PM, Lonnie Abelbeck <li...@lo...>
wrote:

> > The Netgear LB1120 didn't specifically mention it can operate in Bridge
> Mode which is a must for me. I had trouble finding many that could actually.
>
> It appears the Netgear LB1120 does with a bug fixed in firmware update:
> NTG9X07C_12.09.05.27
>
> https://community.netgear.com/t5/Mobile-Routers-Hotspots-
> Modems/LB1120-Bridge-Mode-No-Connectivity/m-p/1404666#M3431
>
> Though if all your traffic is over a WireGuard VPN, Bridge Mode is not as
> much of an issue, but Bridge Mode is best.
>
> Lonnie
>
>
>
>
> > On May 16, 2018, at 5:04 PM, Michael Knill <michael.knill@ipcsolutions.
> com.au> wrote:
> >
> > Thanks Lonnie
> >
> > The Netgear LB1120 didn't specifically mention it can operate in Bridge
> Mode which is a must for me. I had trouble finding many that could actually.
> > Whoops WireGuard VPN. My bad. Im looking forward to testing it out.
> >
> > Regards
> > Michael Knill
> >
> > On 17/5/18, 7:52 am, "Lonnie Abelbeck" <li...@lo...>
> wrote:
> >
> >    Hi Michael,
> >
> >    Very interesting, should work ... as usual the devil is in the detail.
> >
> >    I would use a WireGuard VPN to utilize static addresses across your
> AstLinux box network.  Works nicely for me.
> >
> >    I did a quick search and the Netgear LB1120 4G LTE Modem ($95 USD) is
> an all in one box with a 4G/LTE radio included, no USB dongles required.
> The Amazon reviews are mostly good, no idea if your carriers support it.
> Just the idea if a simple box with one NIC seems like a good KISS
> solution.  There may be other "4G LTE Modem" devices out there as well.
> >
> >    Here in the US this 4G/LTE connection can get expensive with a lot of
> data over it.
> >
> >    Sounds fun to test.
> >
> >    Lonnie
> >
> >
> >
> >
> >
> >> On May 16, 2018, at 3:47 PM, Michael Knill <michael.knill@ipcsolutions.
> com.au> wrote:
> >>
> >> Hi Group
> >>
> >> Ok so I am about to start developing a 4G backup solution for my
> systems utilising Astlinux WAN Failover and the Dovado 4G Tiny AC (
> http://www.dovado.com/en/products) operating in bridge mode.
> >> To overcome the hassle of NAT and providing a Public IP on the 4G
> network, I plan on establishing an OpenVPN or Wireline VPN tunnel to
> another hosted Astlinux box via the 4G network. This will give me access to
> the onsite Astlinux box if there is a primary WAN failure and I can also
> pass voice traffic if this is desired.
> >>
> >> Can anyone see any gotchas with this setup?
> >>
> >> Regards
> >> Michael Knill
> >> ------------------------------------------------------------
> ------------------
> >> 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....
> >
> >
> > ------------------------------------------------------------
> ------------------
> > 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....

Re: [Astlinux-users] 4G backup

[Lonnie A. <li...@lo...>]

> The Netgear LB1120 didn't specifically mention it can operate in Bridge Mode which is a must for me. I had trouble finding many that could actually.

It appears the Netgear LB1120 does with a bug fixed in firmware update: NTG9X07C_12.09.05.27

https://community.netgear.com/t5/Mobile-Routers-Hotspots-Modems/LB1120-Bridge-Mode-No-Connectivity/m-p/1404666#M3431

Though if all your traffic is over a WireGuard VPN, Bridge Mode is not as much of an issue, but Bridge Mode is best.

Lonnie




> On May 16, 2018, at 5:04 PM, Michael Knill <mic...@ip...> wrote:
> 
> Thanks Lonnie
> 
> The Netgear LB1120 didn't specifically mention it can operate in Bridge Mode which is a must for me. I had trouble finding many that could actually.
> Whoops WireGuard VPN. My bad. Im looking forward to testing it out.
> 
> Regards
> Michael Knill
> 
> On 17/5/18, 7:52 am, "Lonnie Abelbeck" <li...@lo...> wrote:
> 
>    Hi Michael,
> 
>    Very interesting, should work ... as usual the devil is in the detail.
> 
>    I would use a WireGuard VPN to utilize static addresses across your AstLinux box network.  Works nicely for me.
> 
>    I did a quick search and the Netgear LB1120 4G LTE Modem ($95 USD) is an all in one box with a 4G/LTE radio included, no USB dongles required.  The Amazon reviews are mostly good, no idea if your carriers support it.  Just the idea if a simple box with one NIC seems like a good KISS solution.  There may be other "4G LTE Modem" devices out there as well.
> 
>    Here in the US this 4G/LTE connection can get expensive with a lot of data over it.
> 
>    Sounds fun to test.
> 
>    Lonnie
> 
> 
> 
> 
> 
>> On May 16, 2018, at 3:47 PM, Michael Knill <mic...@ip...> wrote:
>> 
>> Hi Group
>> 
>> Ok so I am about to start developing a 4G backup solution for my systems utilising Astlinux WAN Failover and the Dovado 4G Tiny AC (http://www.dovado.com/en/products) operating in bridge mode.
>> To overcome the hassle of NAT and providing a Public IP on the 4G network, I plan on establishing an OpenVPN or Wireline VPN tunnel to another hosted Astlinux box via the 4G network. This will give me access to the onsite Astlinux box if there is a primary WAN failure and I can also pass voice traffic if this is desired.
>> 
>> Can anyone see any gotchas with this setup?
>> 
>> Regards
>> Michael Knill
>> ------------------------------------------------------------------------------
>> 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....
> 
> 
> ------------------------------------------------------------------------------
> 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....

Re: [Astlinux-users] 4G backup

[Michael K. <mic...@ip...>]

Thanks Lonnie

The Netgear LB1120 didn't specifically mention it can operate in Bridge Mode which is a must for me. I had trouble finding many that could actually.
Whoops WireGuard VPN. My bad. Im looking forward to testing it out.

Regards
Michael Knill

On 17/5/18, 7:52 am, "Lonnie Abelbeck" <li...@lo...> wrote:

    Hi Michael,
    
    Very interesting, should work ... as usual the devil is in the detail.
    
    I would use a WireGuard VPN to utilize static addresses across your AstLinux box network.  Works nicely for me.
    
    I did a quick search and the Netgear LB1120 4G LTE Modem ($95 USD) is an all in one box with a 4G/LTE radio included, no USB dongles required.  The Amazon reviews are mostly good, no idea if your carriers support it.  Just the idea if a simple box with one NIC seems like a good KISS solution.  There may be other "4G LTE Modem" devices out there as well.
    
    Here in the US this 4G/LTE connection can get expensive with a lot of data over it.
    
    Sounds fun to test.
    
    Lonnie
    
    
    
    
    
    > On May 16, 2018, at 3:47 PM, Michael Knill <mic...@ip...> wrote:
    > 
    > Hi Group
    >  
    > Ok so I am about to start developing a 4G backup solution for my systems utilising Astlinux WAN Failover and the Dovado 4G Tiny AC (http://www.dovado.com/en/products) operating in bridge mode.
    > To overcome the hassle of NAT and providing a Public IP on the 4G network, I plan on establishing an OpenVPN or Wireline VPN tunnel to another hosted Astlinux box via the 4G network. This will give me access to the onsite Astlinux box if there is a primary WAN failure and I can also pass voice traffic if this is desired.
    >  
    > Can anyone see any gotchas with this setup?
    >  
    > Regards
    > Michael Knill
    > ------------------------------------------------------------------------------
    > 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....
    

Re: [Astlinux-users] 4G backup

[Lonnie A. <li...@lo...>]

Hi Michael,

Very interesting, should work ... as usual the devil is in the detail.

I would use a WireGuard VPN to utilize static addresses across your AstLinux box network.  Works nicely for me.

I did a quick search and the Netgear LB1120 4G LTE Modem ($95 USD) is an all in one box with a 4G/LTE radio included, no USB dongles required.  The Amazon reviews are mostly good, no idea if your carriers support it.  Just the idea if a simple box with one NIC seems like a good KISS solution.  There may be other "4G LTE Modem" devices out there as well.

Here in the US this 4G/LTE connection can get expensive with a lot of data over it.

Sounds fun to test.

Lonnie





> On May 16, 2018, at 3:47 PM, Michael Knill <mic...@ip...> wrote:
> 
> Hi Group
>  
> Ok so I am about to start developing a 4G backup solution for my systems utilising Astlinux WAN Failover and the Dovado 4G Tiny AC (http://www.dovado.com/en/products) operating in bridge mode.
> To overcome the hassle of NAT and providing a Public IP on the 4G network, I plan on establishing an OpenVPN or Wireline VPN tunnel to another hosted Astlinux box via the 4G network. This will give me access to the onsite Astlinux box if there is a primary WAN failure and I can also pass voice traffic if this is desired.
>  
> Can anyone see any gotchas with this setup?
>  
> Regards
> Michael Knill
> ------------------------------------------------------------------------------
> 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....

[Astlinux-users] 4G backup

[Michael K. <mic...@ip...>]

Hi Group

Ok so I am about to start developing a 4G backup solution for my systems utilising Astlinux WAN Failover and the Dovado 4G Tiny AC (http://www.dovado.com/en/products) operating in bridge mode.
To overcome the hassle of NAT and providing a Public IP on the 4G network, I plan on establishing an OpenVPN or Wireline VPN tunnel to another hosted Astlinux box via the 4G network. This will give me access to the onsite Astlinux box if there is a primary WAN failure and I can also pass voice traffic if this is desired.

Can anyone see any gotchas with this setup?

Regards
Michael Knill

Re: [Astlinux-users] FOP2 with AstLinux (Licensing errors)

[Michael K. <li...@mk...>]

> Am 13.05.2018 um 23:58 schrieb Michael Knill <mic...@ip...>:
> 
> No Sorry Michael
> 
> Maybe its something like licensing based on something which could change after reboot e.g. MAC Address possibly?

No, they MAC address stays the same, I cheched that. And on the same AstLinux installation FOP2 2.31.05 runs fine.

> Regards
> Michael Knill
> 
> On 13/5/18, 12:48 am, "Michael Keuter" <li...@mk...> wrote:
> 
>    Hi list,
> 
>    I want to ask you about your experiences with licensed FOP2 versions running under AstLinux.
> 
>    I shortly had a new installation of AstLinux on a VMWare VM. I installed the latest FOP2 2.31.17 version, bought a basic license and registered it.
>    But after every restart of FOP2 or a reboot of AstLinux FOP2 was unregistered again. At some point I couldn't ever reregister FOP2 with this license again.
> 
>    Luckily Nicolas from FOP2 revoked the license, so I could try to "use" it again. 
>    Since I had no such issues with older FOP2 2.31.xx versions, I installed version 2.31.5, registered this version at it runs fine since then.
>    I need to run the FOP2 installation on that customer in production, so I didn't tested any further on this VM. 
>    I informed Nicolas from FOP2 about my findings and asked if something regarding the licensing has changed between 2.31.5 and 2.31.17, but I didn't get any answer yet :-(.
>    Maybe this is a issue only on Virtual Machines, maybe newer versions doesn't run licensed on AstLinux at all.
> 
>    Does anyone of you have experiences with licensed versions of FOP2 newer than 2.31.5?
> 
>    Michael

Michael

http://www.mksolutions.info

Re: [Astlinux-users] FOP2 with AstLinux (Licensing errors)

[Michael K. <mic...@ip...>]

No Sorry Michael

Maybe its something like licensing based on something which could change after reboot e.g. MAC Address possibly?

Regards
Michael Knill

On 13/5/18, 12:48 am, "Michael Keuter" <li...@mk...> wrote:

    Hi list,
    
    I want to ask you about your experiences with licensed FOP2 versions running under AstLinux.
    
    I shortly had a new installation of AstLinux on a VMWare VM. I installed the latest FOP2 2.31.17 version, bought a basic license and registered it.
    But after every restart of FOP2 or a reboot of AstLinux FOP2 was unregistered again. At some point I couldn't ever reregister FOP2 with this license again.
    
    Luckily Nicolas from FOP2 revoked the license, so I could try to "use" it again. 
    Since I had no such issues with older FOP2 2.31.xx versions, I installed version 2.31.5, registered this version at it runs fine since then.
    I need to run the FOP2 installation on that customer in production, so I didn't tested any further on this VM. 
    I informed Nicolas from FOP2 about my findings and asked if something regarding the licensing has changed between 2.31.5 and 2.31.17, but I didn't get any answer yet :-(.
    Maybe this is a issue only on Virtual Machines, maybe newer versions doesn't run licensed on AstLinux at all.
    
    Does anyone of you have experiences with licensed versions of FOP2 newer than 2.31.5?
    
    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....
    

[Astlinux-users] FOP2 with AstLinux (Licensing errors)

[Michael K. <li...@mk...>]

Hi list,

I want to ask you about your experiences with licensed FOP2 versions running under AstLinux.

I shortly had a new installation of AstLinux on a VMWare VM. I installed the latest FOP2 2.31.17 version, bought a basic license and registered it.
But after every restart of FOP2 or a reboot of AstLinux FOP2 was unregistered again. At some point I couldn't ever reregister FOP2 with this license again.

Luckily Nicolas from FOP2 revoked the license, so I could try to "use" it again. 
Since I had no such issues with older FOP2 2.31.xx versions, I installed version 2.31.5, registered this version at it runs fine since then.
I need to run the FOP2 installation on that customer in production, so I didn't tested any further on this VM. 
I informed Nicolas from FOP2 about my findings and asked if something regarding the licensing has changed between 2.31.5 and 2.31.17, but I didn't get any answer yet :-(.
Maybe this is a issue only on Virtual Machines, maybe newer versions doesn't run licensed on AstLinux at all.

Does anyone of you have experiences with licensed versions of FOP2 newer than 2.31.5?

Michael

http://www.mksolutions.info

Re: [Astlinux-users] QueueMetrics Live

[Michael K. <mic...@ip...>]

Well QueueMetrics has now been in production for a couple of days on Astlinux and all seems to be working well.
The customer is pretty excited about it as it has significantly improved their customer service and finally given them some metrics.

Regards
Michael Knill

On 25/4/18, 11:41 pm, "Lonnie Abelbeck" <li...@lo...> wrote:

    Hi Michael.au, :-)
    
    > It is proprietary as far as I can gather but it does seem to work and appears to be fairly autonomous. Is there anything I should be watching out for?
    
    I did a "ldd" of uniloader_amd64
    --
    	linux-vdso.so.1 (0x00007ffe4bd71000)
    	libpthread.so.0 => /lib/libpthread.so.0 (0x00007f13a07ad000)
    	libc.so.6 => /lib/libc.so.6 (0x00007f13a0435000)
    	/lib64/ld-linux-x86-64.so.2 (0x00007f13a09c9000)
    --
    and a 'strace' as it started and did not see anything alarming.
    
    Though I'd be interested how they did their crypto, it must be statically linked within their binary.
    
    The Loway folks have a github presence:
    https://github.com/Loway
    
    They really should make their source public, even if it has a "sole purpose of using" license as Tarsnap does
    https://github.com/Tarsnap/tarsnap/blob/master/COPYING
    
    
    > I will let you know how I go.
    
    Please do.
    
    Lonnie
    
    
    On Apr 24, 2018, at 9:03 PM, Michael Knill <mic...@ip...> wrote:
    
    > Hi thanks Lonnie
    > 
    > Whoops there is a --pid option so I should use that in the init script then. "killall uniloader" did work too.
    > I will also put it in rc.local thanks. So would it be best to kill the process in rc.local.stop? Is this best practices?
    > It is proprietary as far as I can gather but it does seem to work and appears to be fairly autonomous. Is there anything I should be watching out for?
    > I guess the proof is when I install it in production. I will let you know how I go.
    > 
    > Thanks again.
    > 
    > Regards
    > Michael Knill
    > 
    > On 25/4/18, 9:45 am, "Lonnie Abelbeck" <li...@lo...> wrote:
    > 
    >    Michael, comments inline ...
    > 
    >    On Apr 24, 2018, at 6:10 PM, Michael Knill <mic...@ip...> wrote:
    > 
    >> Hi thanks Lonnie and Michael for the info.
    >> 
    >> As I don't know of any stop requirements for uniloader I was thinking of doing the following (eventually):
    > 
    >    It is always good to implement stop, "killall uniloader" might do it.
    > 
    >> - Have a queuemetrics.conf file in /mnt/kd which contains all the parameters required for the uniloader including whether it is enabled or not
    >> - Build a script which is included permanently in rc.elocal which reads this config file and runs the application if enabled with the read parameters
    > 
    >    rc.elocal runs quite early in the boot process, you might want to use /mnt/kd/rc.local and /mnt/kd/rc.local.stop which occurs near the end of the boot process.
    > 
    >> - I will also try to monitor the application with monit which restarts it using the above script if it crashes
    > 
    >    Again, you want to implement 'stop'
    > 
    >> 
    >> How does this sound? Am I missing something?
    >> Should I place the uniloader bin file in /usr/sbin or would I put it in /mnt/kd/bin or somewhere else?
    > 
    >    Definitely don't use /usr/sbin space, using /mnt/kd/bin would be fine and all under your control.
    > 
    >> PS I will also be running up the unitracker which is included in the uniloader which monitors outgoing calls as well!
    > 
    >    Question, are these proprietary binary blobs ?  Or can they be compiled ?
    > 
    > 
    >> 
    >> Thanks so much.
    > 
    >    Lonnie
    > 
    > 
    > 
    >> 
    >> Regards
    >> Michael Knill
    >> 
    >> On 24/4/18, 10:39 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
    >> 
    >> 
    >>   On Apr 24, 2018, at 2:16 AM, Michael Keuter <li...@mk...> wrote:
    >> 
    >>> 
    >>>> Am 24.04.2018 um 04:13 schrieb Michael Knill <mic...@ip...>:
    >>>> 
    >>>> Hi All
    >>>> 
    >>>> I am now currently testing QueueMetrics V17 with the uniloader application and it does appear to be working.
    >>>> More testing is required but I was just wondering where I should be putting this file, how to start it on bootup and how to restart it if it crashes.
    >>>> 
    >>>> The command to load is recommended as (and I used):
    >>>> nohup nice ./uniloader -s /var/log/asterisk/queue_log upload --uri "mysql:tcp([qmserver ip address]:3306)/queuemetrics?allowOldPasswords=1" --login [loginname] --pass [password]e --token P001  >> /var/log/uniloader.log &
    >>>> 
    >>>> Thanks. I will let you know how I go.
    >>> 
    >>> I would put the above command into its own script (e.g. in /mnt/kd/bin/) and then start it from "/mnt/kd/rc.local", which runs at the end of the boot process.
    >>> Maybe you can track it then from Monit.
    >>> 
    >>> If you need to do something on reboot/shutdown, you could use "/mnt/kd/rc.local.stop" as well.
    >> 
    >>   Totally agree with Michael.
    >> 
    >>   Model your /mnt/kd/bin/ script after a simple /etc/init.d/ script like /etc/init.d/acpid and call it as Michael suggests from /mnt/kd/rc.local and /mnt/kd/rc.local.stop.
    >> 
    >>   Lonnie
    >> 
    >> 
    >>   ------------------------------------------------------------------------------
    >>   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....
    > 
    > 
    >    ------------------------------------------------------------------------------
    >    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....
    
    
    ------------------------------------------------------------------------------
    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....

Re: [Astlinux-users] Issue periodically my Astlinux can't register and show me rejected

[Lonnie A. <li...@lo...>]

> Thanks for the answer,
> Do you mean that will fix this issue wit the registering? Or is this for testing only why мy astlinux not register?

I'm suggesting this could solve a failed register (and qualify=yes) after a period of time.  Though I'd try Michael's register_retry_403=yes suggestion first.


> Can you please check my script for Ip change.


The first problem I see is your "externip" sip.conf should be "externaddr", so replace all externip with externaddr in your /mnt/kd/checksetexternip.sh .

Second, you are assuming externaddr occurs at the beginning of the line, so do that with ^ in your grep and match consistently as with your sed later ...
--
OLDEXTERNIP=`grep "^externaddr *=" /etc/asterisk/sip.conf | cut -d"=" -f2`
--

BTW, the 
--
;        externhost=foo.dyndns.net       ; refreshed periodically
;        externrefresh=180               ; change the refresh interval
--
used in conjunction with a dynamicdns service may be a better approach, *if* this is really needed.  This is only needed of you have external devices registering.


Lonnie



> On May 10, 2018, at 2:34 AM, nedi <ne...@gm...> wrote:
> 
> Hi Lonnie,
> 
> Thanks for the answer,
> Do you mean that will fix this issue wit the registering? Or is this for testing only why мy astlinux not register?
> 
> The Michael has the same issue with clustered registrar.. 
> My Provider told me that is not provider issue, and I’m confused, I have one Gigaset SIP Phone as backup line  registered inside the same network to this same number that I used on astlinux ( SIP-Forking) and if  I have this registering issue  the gigaset sip phone is still  registered astlinux not. At the first I will trying this with register_retry_403=yes and waiting.
> 
> I have this issue in my case only with one internet provider swisscom.ch and one VOIP Provider Sipcall.ch  If I have  more different  provider on the same pbx usually only the one VOIP Provider in my case sipcall(voipgateway.org) have the status  „rejected" or *send request" 
> 
> Can you please check my script for Ip change.
> I have this script running on the pbx but if I checking  my sip.conf I can't notice any change with this script.
> The script is executable and running but my sip.conf not change as sample if I put manually in my sip.conf any ip adress  under general.
> I put wrong external IP adress in sip.conf general and run the script  but nothing changing. I think there is something wrong or I not understood this.
> As sample I put wrong external  IP Adress under general  and runing the script.
> externip=94.128.12.12
> 
> I have this script under /mnt/kd/checksetexternip.sh
> 
> 
> This is the script I’m try ti using to overcome this problem. It should check the
> external IP and update the sip.conf with the new IP . I Run this script as
> cronjob every 5 minutes. But I can’t notice any change I my sip.conf.
> 
> #!/bin/bash
> # checksetexternip.sh
> # Author: John Cahill email at johncahill.net
> # Licence: GPL v3
> # Description: script that queries checkip.dyndns.com to find the server's
> external IP address. Updates asterisk's externip value and does a sip
> reload if necessary.
> # Last modified 06/02/2012
> 
> is_ip(){
> 
>    input=$1
>    octet1=$(echo $input | cut -d "." -f1)
>    octet2=$(echo $input | cut -d "." -f2)
>    octet3=$(echo $input | cut -d "." -f3)
>    octet4=$(echo $input | cut -d "." -f4)
>    stat=1
> 
> if [[ $input =~ ^[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}$ ]] && [
> $octet1 -le 255 ] && [ $octet2 -le 255 ] && [ $octet3 -le 255 ] && [
> $octet4 -le 255 ];
>  then
>    stat=0
> fi
> 
> return  $stat
> 
> }
> 
> EXTERNIP=`wget -qO- http://checkip.dyndns.com | awk '{print $6}'| cut -d"<"
> -f1`
> is_ip $EXTERNIP
> if [ $? -ne 0 ]
>        then
>                logger -s "checksetexternip.sh: External IP address invalid
> or unavailable, exiting."
>                exit 1
> fi
> 
> OLDEXTERNIP=`grep externip /etc/asterisk/sip.conf | cut -d"=" -f2`
> if [ "$EXTERNIP" = "$OLDEXTERNIP" ]
>        then
>                logger -s "checksetexternip.sh: External IP address is the
> same, nothing to do exiting."
>                exit 0
>        else
>                logger -s "checksetexternip.sh: External IP address has
> changed, changing /etc/asterisk/sip.conf"
>                #grep -v "externip" /etc/asterisk/sip.conf >
> /etc/asterisk/sip.conf.tmp
>                #echo "externip=$EXTERNIP" >> /etc/asterisk/sip.conf.tmp
>                #cp /etc/asterisk/sip.conf.tmp /etc/asterisk/sip.conf
>                #rm /etc/asterisk/sip.conf.tmp
> sed -i -e "s/^externip *=.*/externip=$EXTERNIP/" /etc/asterisk/sip.conf
>                logger -s "Doing asterisk -rx "sip reload""
>                asterisk -rx "sip reload"
> 
> Regards nedi
> 
> 
> 
> 
>> Am 10.05.2018 um 05:23 schrieb Lonnie Abelbeck <li...@lo...>:
>> 
>> Hi Nedi,
>> 
>> I appreciate your detailed description and for the record I feel your frustration.
>> 
>> I seem to recall Michael Knill described a similar situation in the recent past.
>> 
>> My educated guess is this is a firewall statefull-inspection "stuck-state" somewhere in the network path.  AstLinux's firewall is not the issue otherwise a reboot would solve the problem.
>> 
>> Long story short, as a test, I would determine a time of day where shutting down asterisk is acceptable (say 2:00 am) and keep asterisk down for 10 minutes or so, something like:
>> 
>> -- cron at 2:00 am or so --
>> service asterisk stop
>> sleep 600
>> service asterisk init
>> --
>> (make sure you don't have any other background scripts looking to restart asterisk other than the cron script)
>> 
>> Possibly 5 minutes is all that is needed, but I would start at 10 minutes.  Most any firewall UDP state should expire in 10 minutes.
>> 
>> Sadly, this test may take weeks to confirm if it helps.
>> 
>> If you are already using cron to rewrite the sip.conf this test will be a simple addition by delaying starting up asterisk.
>> 
>> Lonnie
>> 
>> 
>> 
>> 
>>> On May 9, 2018, at 6:58 PM, nedi <ne...@gm...> wrote:
>>> 
>>> Hi,
>>> 
>>> I have some Astlinux boxes as local pbx after Modem with standard firewall inside modems , Astlinux have different Releases,  and since years I have this issue and can’t fix that:  
>>> After a week or month and sometimes longer  the voip number can’t be registered and Status show me „rejected“ 
>>> 
>>> Reboot can’t help - Aterisk Reload can’t help - I can’t reproduce that for testing. 
>>> If I have this problem only change the SIP Server to another Sipcall sip server can help to fix that issues. 
>>> 
>>> As sample if I was registered to business1.voipgateway.org I must change registrar  to business2.voipgateway.org and I can save and reload to  register without reboot.
>>> 
>>> I have tried  instead of registrar name to  use the ip adress but this not fixed my problem. 
>>> I use Sipcall DNS IP’s to in the Astlinux Network setting that don’t help, 
>>> I don’t use IPV6.  IPV6 is disabled in the Network Settings.
>>> Nat and Firewall in Astlinux are enabled and.
>>> 
>>> I found  that I have this issue only with the provider Sipcall.ch ( if registered on different subdomains of  voipgateay.org ) and only if I use Swisscom as Internet Provider. On others provider on the same astlinux and at the same time I don’ t have this issues.
>>> On the same Astlinux box by some customer I have different provider and sipcall on the same astlinux box and only the Sipcall have this all other provider worked onlythe the Sipcall account get rejected. 
>>> 
>>> At now I use Alix Board and AstLinux Release astlinux-1.2.6.1 i586 - Asterisk 1.8.32.3, but i had this issues with oter astlinux release to.
>>> 
>>> Some of my customer changed to internet with fix ip adress and  there are this issue not so often.before with Dynamic IP Adress i had this issues oftener.
>>> 
>>> The Sipcall support told me that is not the problem on the Sipcall site.  Some times the Sipcall told me Astlinux trying to register with old IP Adress and sometimes they told me Astlinux don’t try to register for some hours or days and they don’t  getting inquiry from pbx to register)
>>> 
>>> I tried to change some settings in my sip.conf and  there is nothing what helped me to resolve the issue.
>>> 
>>> egisterattempts=0
>>> registertimeout=20
>>> maxexpiry=3600
>>> defaultexpiry=600
>>> qualify=2500
>>> srvlookup=no
>>> nat=yes
>>> 
>>> I use a cron script if external IP changed and update the sip.conf with the new IP for dynamic IP and  again I have this problem, that not helped me great.
>>> 
>>> The PBX can work for weeks and months without problem but after some time I get that again.  
>>> 
>>> I don’t know have this issue something with Astlinux firewall or with swisscom modem or with Sipcall.
>>> 
>>> I think when, for some reason the registry fail and the state of the registry becomes REJECTED, asterisk stops trying to register. Can someone help me figuring out why this occur and a way to prevent asterisk from stop sending the registration requests. 
>>> 
>>> Does anybody have an idea about that problem ? How can we configure Asterisk to retry after some time in case of rejection ?
>>> 
>>> 
>>> Im my sip.conf I have this:
>>> 
>>> 
>>> I use a cron script to change the IP Adress in Astlinux  if external ip adress was changed and  again I have this problem that  some customer get rejected.
>>> 
>>> The PBX can work for weeks and months without problem but after some time I get that again.  
>>> 
>>> I don’t know have this issue something with Astlinux firewall or with swisscom modem or with Sipcall.
>>> 
>>> I think when, for some reason the registry fail and the state of the registry becomes REJECTED, asterisk stops trying to register. Can someone help me figuring out why this occur and a way to prevent asterisk from stop sending the registration requests. 
>>> 
>>> Does anybody have an idea about that problem ? How can we configure Asterisk to retry after some time in case of rejection ?
>>> 
>>> 
>>> Im my sip.conf I have this:
>>> 
>>> [general]
>>> useragent=mypbxname
>>> port=5060   
>>> context = from-sip-external; send unknown sip callers to this context
>>> alwaysauthreject=yes
>>> deny = 0.0.0.0/0.0.0.0
>>> permit = 10.0.0.0/255.255.255.0
>>> permit = 10.8.0.6/255.255.255.0
>>> allowguest=no
>>> disallow=all 
>>> allow=alaw
>>> allow=ulaw
>>> language=de
>>> registerattempts=0
>>> registertimeout=20
>>> maxexpiry=3600
>>> defaultexpiry=600
>>> qualify=2500
>>> notifycid=yes
>>> srvlookup=no
>>> nat=yes
>>> allow subscribe = yes
>>> subscribecontext = hints
>>> trustrpid=yes
>>> sendrpid=yes
>>> ;t38pt_udptl = yes
>>> faxdetect=yes
>>> 
>>> register => 4171511xxxx:2345678@212.117.203.35/4171511xxxx
>>> 
>>> [071511xxxx]
>>> type=peer
>>> username=4171511xxxx
>>> secret=2345678
>>> host=212.117.203.35
>>> ;fromuser=4171511xxxx
>>> fromdomain=212.117.203.35
>>> directmedia=no
>>> insecure=port,invite
>>> disallow=all 
>>> allow=alaw
>>> allow=ulaw
>>> context=incoming212.117.203.35
>>> dtmfmode=info
>>> trustrpid=yes
>>> sendrpid=pai
>>> 
>>> 
>>> 
>>> Best regards
>>> Nedi
>>> 
>>> ------------------------------------------------------------------------------
>>> 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....
> 
> 
> ------------------------------------------------------------------------------
> 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....

Re: [Astlinux-users] Issue periodically my Astlinux can't register and show me rejected

[Lonnie A. <li...@lo...>]

> On May 9, 2018, at 10:41 PM, Michael Knill <mic...@ip...> wrote:
> I have found this problem only recently and I think it may be what you are experiencing. Providers with clustered SBC's (which yours sounds like), when they fail over for some reason, any registration attempts to the standby SBC responds with a 403 Forbidden. This was proved by my provider with a packet capture. By default Asterisk views a 403 Forbidden as an authentication failure and stops trying to register. If you set register_retry_403=yes in sip.conf it fixes this problem.

Thanks for sharing Michael !!!

--
;register_retry_403=yes         ; Treat 403 responses to registrations as if they were
                                ; 401 responses and continue retrying according to normal
                                ; retry rules.
--

Lonnie




> On May 9, 2018, at 10:41 PM, Michael Knill <mic...@ip...> wrote:
> 
> Hi Nedi
> 
> This is what I have found:
> 1) If you are registering to a DNS name, if the address changes Asterisk does not know about it unless you are using srvlookup=yes in sip.conf. PS I don't use it as it does a lookup for every call and I don't like this. I instead use dnsmgr.conf to check periodically. Nate that this only affects SIP registration and not SIP OPTIONS (qualify). For this I actually use a Monit script but the cause of this problem is not what you are experiencing.
> 2) Yes using the IP Address solves 1) but if you have a provider with multiple IP Addresses then this is not the best approach.
> 3) I have found this problem only recently and I think it may be what you are experiencing. Providers with clustered SBC's (which yours sounds like), when they fail over for some reason, any registration attempts to the standby SBC responds with a 403 Forbidden. This was proved by my provider with a packet capture. By default Asterisk views a 403 Forbidden as an authentication failure and stops trying to register. If you set register_retry_403=yes in sip.conf it fixes this problem.
> 
> Good luck. 
> 
> Regards
> Michael Knill
> 
> On 10/5/18, 1:24 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
> 
>    Hi Nedi,
> 
>    I appreciate your detailed description and for the record I feel your frustration.
> 
>    I seem to recall Michael Knill described a similar situation in the recent past.
> 
>    My educated guess is this is a firewall statefull-inspection "stuck-state" somewhere in the network path.  AstLinux's firewall is not the issue otherwise a reboot would solve the problem.
> 
>    Long story short, as a test, I would determine a time of day where shutting down asterisk is acceptable (say 2:00 am) and keep asterisk down for 10 minutes or so, something like:
> 
>    -- cron at 2:00 am or so --
>    service asterisk stop
>    sleep 600
>    service asterisk init
>    --
>    (make sure you don't have any other background scripts looking to restart asterisk other than the cron script)
> 
>    Possibly 5 minutes is all that is needed, but I would start at 10 minutes.  Most any firewall UDP state should expire in 10 minutes.
> 
>    Sadly, this test may take weeks to confirm if it helps.
> 
>    If you are already using cron to rewrite the sip.conf this test will be a simple addition by delaying starting up asterisk.
> 
>    Lonnie
> 
> 
> 
> 
>> On May 9, 2018, at 6:58 PM, nedi <ne...@gm...> wrote:
>> 
>> Hi,
>> 
>> I have some Astlinux boxes as local pbx after Modem with standard firewall inside modems , Astlinux have different Releases,  and since years I have this issue and can’t fix that:  
>> After a week or month and sometimes longer  the voip number can’t be registered and Status show me „rejected“ 
>> 
>> Reboot can’t help - Aterisk Reload can’t help - I can’t reproduce that for testing. 
>> If I have this problem only change the SIP Server to another Sipcall sip server can help to fix that issues. 
>> 
>> As sample if I was registered to business1.voipgateway.org I must change registrar  to business2.voipgateway.org and I can save and reload to  register without reboot.
>> 
>> I have tried  instead of registrar name to  use the ip adress but this not fixed my problem. 
>> I use Sipcall DNS IP’s to in the Astlinux Network setting that don’t help, 
>> I don’t use IPV6.  IPV6 is disabled in the Network Settings.
>> Nat and Firewall in Astlinux are enabled and.
>> 
>> I found  that I have this issue only with the provider Sipcall.ch ( if registered on different subdomains of  voipgateay.org ) and only if I use Swisscom as Internet Provider. On others provider on the same astlinux and at the same time I don’ t have this issues.
>> On the same Astlinux box by some customer I have different provider and sipcall on the same astlinux box and only the Sipcall have this all other provider worked onlythe the Sipcall account get rejected. 
>> 
>> At now I use Alix Board and AstLinux Release astlinux-1.2.6.1 i586 - Asterisk 1.8.32.3, but i had this issues with oter astlinux release to.
>> 
>> Some of my customer changed to internet with fix ip adress and  there are this issue not so often.before with Dynamic IP Adress i had this issues oftener.
>> 
>> The Sipcall support told me that is not the problem on the Sipcall site.  Some times the Sipcall told me Astlinux trying to register with old IP Adress and sometimes they told me Astlinux don’t try to register for some hours or days and they don’t  getting inquiry from pbx to register)
>> 
>> I tried to change some settings in my sip.conf and  there is nothing what helped me to resolve the issue.
>> 
>> egisterattempts=0
>> registertimeout=20
>> maxexpiry=3600
>> defaultexpiry=600
>> qualify=2500
>> srvlookup=no
>> nat=yes
>> 
>> I use a cron script if external IP changed and update the sip.conf with the new IP for dynamic IP and  again I have this problem, that not helped me great.
>> 
>> The PBX can work for weeks and months without problem but after some time I get that again.  
>> 
>> I don’t know have this issue something with Astlinux firewall or with swisscom modem or with Sipcall.
>> 
>> I think when, for some reason the registry fail and the state of the registry becomes REJECTED, asterisk stops trying to register. Can someone help me figuring out why this occur and a way to prevent asterisk from stop sending the registration requests. 
>> 
>> Does anybody have an idea about that problem ? How can we configure Asterisk to retry after some time in case of rejection ?
>> 
>> 
>> Im my sip.conf I have this:
>> 
>> 
>> I use a cron script to change the IP Adress in Astlinux  if external ip adress was changed and  again I have this problem that  some customer get rejected.
>> 
>> The PBX can work for weeks and months without problem but after some time I get that again.  
>> 
>> I don’t know have this issue something with Astlinux firewall or with swisscom modem or with Sipcall.
>> 
>> I think when, for some reason the registry fail and the state of the registry becomes REJECTED, asterisk stops trying to register. Can someone help me figuring out why this occur and a way to prevent asterisk from stop sending the registration requests. 
>> 
>> Does anybody have an idea about that problem ? How can we configure Asterisk to retry after some time in case of rejection ?
>> 
>> 
>> Im my sip.conf I have this:
>> 
>> [general]
>> useragent=mypbxname
>> port=5060   
>> context = from-sip-external; send unknown sip callers to this context
>> alwaysauthreject=yes
>> deny = 0.0.0.0/0.0.0.0
>> permit = 10.0.0.0/255.255.255.0
>> permit = 10.8.0.6/255.255.255.0
>> allowguest=no
>> disallow=all 
>> allow=alaw
>> allow=ulaw
>> language=de
>> registerattempts=0
>> registertimeout=20
>> maxexpiry=3600
>> defaultexpiry=600
>> qualify=2500
>> notifycid=yes
>> srvlookup=no
>> nat=yes
>> allow subscribe = yes
>> subscribecontext = hints
>> trustrpid=yes
>> sendrpid=yes
>> ;t38pt_udptl = yes
>> faxdetect=yes
>> 
>> register => 4171511xxxx:2345678@212.117.203.35/4171511xxxx
>> 
>> [071511xxxx]
>> type=peer
>> username=4171511xxxx
>> secret=2345678
>> host=212.117.203.35
>> ;fromuser=4171511xxxx
>> fromdomain=212.117.203.35
>> directmedia=no
>> insecure=port,invite
>> disallow=all 
>> allow=alaw
>> allow=ulaw
>> context=incoming212.117.203.35
>> dtmfmode=info
>> trustrpid=yes
>> sendrpid=pai
>> 
>> 
>> 
>> Best regards
>> Nedi
>> 
>> ------------------------------------------------------------------------------
>> 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....
> 
> ------------------------------------------------------------------------------
> 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....

Re: [Astlinux-users] Issue periodically my Astlinux can't register and show me rejected

[nedi <ne...@gm...>]

Hi Michael, thanks for the Answer, 
I will trying this register_retry_403=yes in sip.conf I hope that will fix my issue to.

Best regards
Nedi

> Am 10.05.2018 um 05:41 schrieb Michael Knill <mic...@ip...>:
> 
> Hi Nedi
> 
> This is what I have found:
> 1) If you are registering to a DNS name, if the address changes Asterisk does not know about it unless you are using srvlookup=yes in sip.conf. PS I don't use it as it does a lookup for every call and I don't like this. I instead use dnsmgr.conf to check periodically. Nate that this only affects SIP registration and not SIP OPTIONS (qualify). For this I actually use a Monit script but the cause of this problem is not what you are experiencing.
> 2) Yes using the IP Address solves 1) but if you have a provider with multiple IP Addresses then this is not the best approach.
> 3) I have found this problem only recently and I think it may be what you are experiencing. Providers with clustered SBC's (which yours sounds like), when they fail over for some reason, any registration attempts to the standby SBC responds with a 403 Forbidden. This was proved by my provider with a packet capture. By default Asterisk views a 403 Forbidden as an authentication failure and stops trying to register. If you set register_retry_403=yes in sip.conf it fixes this problem.
> 
> Good luck. 
> 
> Regards
> Michael Knill
> 
> On 10/5/18, 1:24 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
> 
>    Hi Nedi,
> 
>    I appreciate your detailed description and for the record I feel your frustration.
> 
>    I seem to recall Michael Knill described a similar situation in the recent past.
> 
>    My educated guess is this is a firewall statefull-inspection "stuck-state" somewhere in the network path.  AstLinux's firewall is not the issue otherwise a reboot would solve the problem.
> 
>    Long story short, as a test, I would determine a time of day where shutting down asterisk is acceptable (say 2:00 am) and keep asterisk down for 10 minutes or so, something like:
> 
>    -- cron at 2:00 am or so --
>    service asterisk stop
>    sleep 600
>    service asterisk init
>    --
>    (make sure you don't have any other background scripts looking to restart asterisk other than the cron script)
> 
>    Possibly 5 minutes is all that is needed, but I would start at 10 minutes.  Most any firewall UDP state should expire in 10 minutes.
> 
>    Sadly, this test may take weeks to confirm if it helps.
> 
>    If you are already using cron to rewrite the sip.conf this test will be a simple addition by delaying starting up asterisk.
> 
>    Lonnie
> 
> 
> 
> 
>> On May 9, 2018, at 6:58 PM, nedi <ne...@gm...> wrote:
>> 
>> Hi,
>> 
>> I have some Astlinux boxes as local pbx after Modem with standard firewall inside modems , Astlinux have different Releases,  and since years I have this issue and can’t fix that:  
>> After a week or month and sometimes longer  the voip number can’t be registered and Status show me „rejected“ 
>> 
>> Reboot can’t help - Aterisk Reload can’t help - I can’t reproduce that for testing. 
>> If I have this problem only change the SIP Server to another Sipcall sip server can help to fix that issues. 
>> 
>> As sample if I was registered to business1.voipgateway.org I must change registrar  to business2.voipgateway.org and I can save and reload to  register without reboot.
>> 
>> I have tried  instead of registrar name to  use the ip adress but this not fixed my problem. 
>> I use Sipcall DNS IP’s to in the Astlinux Network setting that don’t help, 
>> I don’t use IPV6.  IPV6 is disabled in the Network Settings.
>> Nat and Firewall in Astlinux are enabled and.
>> 
>> I found  that I have this issue only with the provider Sipcall.ch ( if registered on different subdomains of  voipgateay.org ) and only if I use Swisscom as Internet Provider. On others provider on the same astlinux and at the same time I don’ t have this issues.
>> On the same Astlinux box by some customer I have different provider and sipcall on the same astlinux box and only the Sipcall have this all other provider worked onlythe the Sipcall account get rejected. 
>> 
>> At now I use Alix Board and AstLinux Release astlinux-1.2.6.1 i586 - Asterisk 1.8.32.3, but i had this issues with oter astlinux release to.
>> 
>> Some of my customer changed to internet with fix ip adress and  there are this issue not so often.before with Dynamic IP Adress i had this issues oftener.
>> 
>> The Sipcall support told me that is not the problem on the Sipcall site.  Some times the Sipcall told me Astlinux trying to register with old IP Adress and sometimes they told me Astlinux don’t try to register for some hours or days and they don’t  getting inquiry from pbx to register)
>> 
>> I tried to change some settings in my sip.conf and  there is nothing what helped me to resolve the issue.
>> 
>> egisterattempts=0
>> registertimeout=20
>> maxexpiry=3600
>> defaultexpiry=600
>> qualify=2500
>> srvlookup=no
>> nat=yes
>> 
>> I use a cron script if external IP changed and update the sip.conf with the new IP for dynamic IP and  again I have this problem, that not helped me great.
>> 
>> The PBX can work for weeks and months without problem but after some time I get that again.  
>> 
>> I don’t know have this issue something with Astlinux firewall or with swisscom modem or with Sipcall.
>> 
>> I think when, for some reason the registry fail and the state of the registry becomes REJECTED, asterisk stops trying to register. Can someone help me figuring out why this occur and a way to prevent asterisk from stop sending the registration requests. 
>> 
>> Does anybody have an idea about that problem ? How can we configure Asterisk to retry after some time in case of rejection ?
>> 
>> 
>> Im my sip.conf I have this:
>> 
>> 
>> I use a cron script to change the IP Adress in Astlinux  if external ip adress was changed and  again I have this problem that  some customer get rejected.
>> 
>> The PBX can work for weeks and months without problem but after some time I get that again.  
>> 
>> I don’t know have this issue something with Astlinux firewall or with swisscom modem or with Sipcall.
>> 
>> I think when, for some reason the registry fail and the state of the registry becomes REJECTED, asterisk stops trying to register. Can someone help me figuring out why this occur and a way to prevent asterisk from stop sending the registration requests. 
>> 
>> Does anybody have an idea about that problem ? How can we configure Asterisk to retry after some time in case of rejection ?
>> 
>> 
>> Im my sip.conf I have this:
>> 
>> [general]
>> useragent=mypbxname
>> port=5060   
>> context = from-sip-external; send unknown sip callers to this context
>> alwaysauthreject=yes
>> deny = 0.0.0.0/0.0.0.0
>> permit = 10.0.0.0/255.255.255.0
>> permit = 10.8.0.6/255.255.255.0
>> allowguest=no
>> disallow=all 
>> allow=alaw
>> allow=ulaw
>> language=de
>> registerattempts=0
>> registertimeout=20
>> maxexpiry=3600
>> defaultexpiry=600
>> qualify=2500
>> notifycid=yes
>> srvlookup=no
>> nat=yes
>> allow subscribe = yes
>> subscribecontext = hints
>> trustrpid=yes
>> sendrpid=yes
>> ;t38pt_udptl = yes
>> faxdetect=yes
>> 
>> register => 4171511xxxx:2345678@212.117.203.35/4171511xxxx
>> 
>> [071511xxxx]
>> type=peer
>> username=4171511xxxx
>> secret=2345678
>> host=212.117.203.35
>> ;fromuser=4171511xxxx
>> fromdomain=212.117.203.35
>> directmedia=no
>> insecure=port,invite
>> disallow=all 
>> allow=alaw
>> allow=ulaw
>> context=incoming212.117.203.35
>> dtmfmode=info
>> trustrpid=yes
>> sendrpid=pai
>> 
>> 
>> 
>> Best regards
>> Nedi
>> 
>> ------------------------------------------------------------------------------
>> 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....
> 
> ------------------------------------------------------------------------------
> 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....

Re: [Astlinux-users] Issue periodically my Astlinux can't register and show me rejected

[nedi <ne...@gm...>]

Hi Lonnie,

Thanks for the answer,
Do you mean that will fix this issue wit the registering? Or is this for testing only why мy astlinux not register?

The Michael has the same issue with clustered registrar.. 
My Provider told me that is not provider issue, and I’m confused, I have one Gigaset SIP Phone as backup line  registered inside the same network to this same number that I used on astlinux ( SIP-Forking) and if  I have this registering issue  the gigaset sip phone is still  registered astlinux not. At the first I will trying this with register_retry_403=yes and waiting.

I have this issue in my case only with one internet provider swisscom.ch and one VOIP Provider Sipcall.ch  If I have  more different  provider on the same pbx usually only the one VOIP Provider in my case sipcall(voipgateway.org) have the status  „rejected" or *send request" 

Can you please check my script for Ip change.
I have this script running on the pbx but if I checking  my sip.conf I can't notice any change with this script.
The script is executable and running but my sip.conf not change as sample if I put manually in my sip.conf any ip adress  under general.
I put wrong external IP adress in sip.conf general and run the script  but nothing changing. I think there is something wrong or I not understood this.
As sample I put wrong external  IP Adress under general  and runing the script.
externip=94.128.12.12

I have this script under /mnt/kd/checksetexternip.sh


This is the script I’m try ti using to overcome this problem. It should check the
external IP and update the sip.conf with the new IP . I Run this script as
cronjob every 5 minutes. But I can’t notice any change I my sip.conf.

#!/bin/bash
# checksetexternip.sh
# Author: John Cahill email at johncahill.net
# Licence: GPL v3
# Description: script that queries checkip.dyndns.com to find the server's
external IP address. Updates asterisk's externip value and does a sip
reload if necessary.
# Last modified 06/02/2012

is_ip(){

    input=$1
    octet1=$(echo $input | cut -d "." -f1)
    octet2=$(echo $input | cut -d "." -f2)
    octet3=$(echo $input | cut -d "." -f3)
    octet4=$(echo $input | cut -d "." -f4)
    stat=1

if [[ $input =~ ^[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}$ ]] && [
$octet1 -le 255 ] && [ $octet2 -le 255 ] && [ $octet3 -le 255 ] && [
$octet4 -le 255 ];
  then
    stat=0
fi

return  $stat

}

EXTERNIP=`wget -qO- http://checkip.dyndns.com | awk '{print $6}'| cut -d"<"
-f1`
is_ip $EXTERNIP
if [ $? -ne 0 ]
        then
                logger -s "checksetexternip.sh: External IP address invalid
or unavailable, exiting."
                exit 1
fi

OLDEXTERNIP=`grep externip /etc/asterisk/sip.conf | cut -d"=" -f2`
if [ "$EXTERNIP" = "$OLDEXTERNIP" ]
        then
                logger -s "checksetexternip.sh: External IP address is the
same, nothing to do exiting."
                exit 0
        else
                logger -s "checksetexternip.sh: External IP address has
changed, changing /etc/asterisk/sip.conf"
                #grep -v "externip" /etc/asterisk/sip.conf >
/etc/asterisk/sip.conf.tmp
                #echo "externip=$EXTERNIP" >> /etc/asterisk/sip.conf.tmp
                #cp /etc/asterisk/sip.conf.tmp /etc/asterisk/sip.conf
                #rm /etc/asterisk/sip.conf.tmp
sed -i -e "s/^externip *=.*/externip=$EXTERNIP/" /etc/asterisk/sip.conf
                logger -s "Doing asterisk -rx "sip reload""
                asterisk -rx "sip reload"

Regards nedi




> Am 10.05.2018 um 05:23 schrieb Lonnie Abelbeck <li...@lo...>:
> 
> Hi Nedi,
> 
> I appreciate your detailed description and for the record I feel your frustration.
> 
> I seem to recall Michael Knill described a similar situation in the recent past.
> 
> My educated guess is this is a firewall statefull-inspection "stuck-state" somewhere in the network path.  AstLinux's firewall is not the issue otherwise a reboot would solve the problem.
> 
> Long story short, as a test, I would determine a time of day where shutting down asterisk is acceptable (say 2:00 am) and keep asterisk down for 10 minutes or so, something like:
> 
> -- cron at 2:00 am or so --
> service asterisk stop
> sleep 600
> service asterisk init
> --
> (make sure you don't have any other background scripts looking to restart asterisk other than the cron script)
> 
> Possibly 5 minutes is all that is needed, but I would start at 10 minutes.  Most any firewall UDP state should expire in 10 minutes.
> 
> Sadly, this test may take weeks to confirm if it helps.
> 
> If you are already using cron to rewrite the sip.conf this test will be a simple addition by delaying starting up asterisk.
> 
> Lonnie
> 
> 
> 
> 
>> On May 9, 2018, at 6:58 PM, nedi <ne...@gm...> wrote:
>> 
>> Hi,
>> 
>> I have some Astlinux boxes as local pbx after Modem with standard firewall inside modems , Astlinux have different Releases,  and since years I have this issue and can’t fix that:  
>> After a week or month and sometimes longer  the voip number can’t be registered and Status show me „rejected“ 
>> 
>> Reboot can’t help - Aterisk Reload can’t help - I can’t reproduce that for testing. 
>> If I have this problem only change the SIP Server to another Sipcall sip server can help to fix that issues. 
>> 
>> As sample if I was registered to business1.voipgateway.org I must change registrar  to business2.voipgateway.org and I can save and reload to  register without reboot.
>> 
>> I have tried  instead of registrar name to  use the ip adress but this not fixed my problem. 
>> I use Sipcall DNS IP’s to in the Astlinux Network setting that don’t help, 
>> I don’t use IPV6.  IPV6 is disabled in the Network Settings.
>> Nat and Firewall in Astlinux are enabled and.
>> 
>> I found  that I have this issue only with the provider Sipcall.ch ( if registered on different subdomains of  voipgateay.org ) and only if I use Swisscom as Internet Provider. On others provider on the same astlinux and at the same time I don’ t have this issues.
>> On the same Astlinux box by some customer I have different provider and sipcall on the same astlinux box and only the Sipcall have this all other provider worked onlythe the Sipcall account get rejected. 
>> 
>> At now I use Alix Board and AstLinux Release astlinux-1.2.6.1 i586 - Asterisk 1.8.32.3, but i had this issues with oter astlinux release to.
>> 
>> Some of my customer changed to internet with fix ip adress and  there are this issue not so often.before with Dynamic IP Adress i had this issues oftener.
>> 
>> The Sipcall support told me that is not the problem on the Sipcall site.  Some times the Sipcall told me Astlinux trying to register with old IP Adress and sometimes they told me Astlinux don’t try to register for some hours or days and they don’t  getting inquiry from pbx to register)
>> 
>> I tried to change some settings in my sip.conf and  there is nothing what helped me to resolve the issue.
>> 
>> egisterattempts=0
>> registertimeout=20
>> maxexpiry=3600
>> defaultexpiry=600
>> qualify=2500
>> srvlookup=no
>> nat=yes
>> 
>> I use a cron script if external IP changed and update the sip.conf with the new IP for dynamic IP and  again I have this problem, that not helped me great.
>> 
>> The PBX can work for weeks and months without problem but after some time I get that again.  
>> 
>> I don’t know have this issue something with Astlinux firewall or with swisscom modem or with Sipcall.
>> 
>> I think when, for some reason the registry fail and the state of the registry becomes REJECTED, asterisk stops trying to register. Can someone help me figuring out why this occur and a way to prevent asterisk from stop sending the registration requests. 
>> 
>> Does anybody have an idea about that problem ? How can we configure Asterisk to retry after some time in case of rejection ?
>> 
>> 
>> Im my sip.conf I have this:
>> 
>> 
>> I use a cron script to change the IP Adress in Astlinux  if external ip adress was changed and  again I have this problem that  some customer get rejected.
>> 
>> The PBX can work for weeks and months without problem but after some time I get that again.  
>> 
>> I don’t know have this issue something with Astlinux firewall or with swisscom modem or with Sipcall.
>> 
>> I think when, for some reason the registry fail and the state of the registry becomes REJECTED, asterisk stops trying to register. Can someone help me figuring out why this occur and a way to prevent asterisk from stop sending the registration requests. 
>> 
>> Does anybody have an idea about that problem ? How can we configure Asterisk to retry after some time in case of rejection ?
>> 
>> 
>> Im my sip.conf I have this:
>> 
>> [general]
>> useragent=mypbxname
>> port=5060   
>> context = from-sip-external; send unknown sip callers to this context
>> alwaysauthreject=yes
>> deny = 0.0.0.0/0.0.0.0
>> permit = 10.0.0.0/255.255.255.0
>> permit = 10.8.0.6/255.255.255.0
>> allowguest=no
>> disallow=all 
>> allow=alaw
>> allow=ulaw
>> language=de
>> registerattempts=0
>> registertimeout=20
>> maxexpiry=3600
>> defaultexpiry=600
>> qualify=2500
>> notifycid=yes
>> srvlookup=no
>> nat=yes
>> allow subscribe = yes
>> subscribecontext = hints
>> trustrpid=yes
>> sendrpid=yes
>> ;t38pt_udptl = yes
>> faxdetect=yes
>> 
>> register => 4171511xxxx:2345678@212.117.203.35/4171511xxxx
>> 
>> [071511xxxx]
>> type=peer
>> username=4171511xxxx
>> secret=2345678
>> host=212.117.203.35
>> ;fromuser=4171511xxxx
>> fromdomain=212.117.203.35
>> directmedia=no
>> insecure=port,invite
>> disallow=all 
>> allow=alaw
>> allow=ulaw
>> context=incoming212.117.203.35
>> dtmfmode=info
>> trustrpid=yes
>> sendrpid=pai
>> 
>> 
>> 
>> Best regards
>> Nedi
>> 
>> ------------------------------------------------------------------------------
>> 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....

Re: [Astlinux-users] Issue periodically my Astlinux can't register and show me rejected

[Michael K. <mic...@ip...>]

Hi Nedi

This is what I have found:
1) If you are registering to a DNS name, if the address changes Asterisk does not know about it unless you are using srvlookup=yes in sip.conf. PS I don't use it as it does a lookup for every call and I don't like this. I instead use dnsmgr.conf to check periodically. Nate that this only affects SIP registration and not SIP OPTIONS (qualify). For this I actually use a Monit script but the cause of this problem is not what you are experiencing.
2) Yes using the IP Address solves 1) but if you have a provider with multiple IP Addresses then this is not the best approach.
3) I have found this problem only recently and I think it may be what you are experiencing. Providers with clustered SBC's (which yours sounds like), when they fail over for some reason, any registration attempts to the standby SBC responds with a 403 Forbidden. This was proved by my provider with a packet capture. By default Asterisk views a 403 Forbidden as an authentication failure and stops trying to register. If you set register_retry_403=yes in sip.conf it fixes this problem.

Good luck. 

Regards
Michael Knill

On 10/5/18, 1:24 pm, "Lonnie Abelbeck" <li...@lo...> wrote:

    Hi Nedi,
    
    I appreciate your detailed description and for the record I feel your frustration.
    
    I seem to recall Michael Knill described a similar situation in the recent past.
    
    My educated guess is this is a firewall statefull-inspection "stuck-state" somewhere in the network path.  AstLinux's firewall is not the issue otherwise a reboot would solve the problem.
    
    Long story short, as a test, I would determine a time of day where shutting down asterisk is acceptable (say 2:00 am) and keep asterisk down for 10 minutes or so, something like:
    
    -- cron at 2:00 am or so --
    service asterisk stop
    sleep 600
    service asterisk init
    --
    (make sure you don't have any other background scripts looking to restart asterisk other than the cron script)
    
    Possibly 5 minutes is all that is needed, but I would start at 10 minutes.  Most any firewall UDP state should expire in 10 minutes.
    
    Sadly, this test may take weeks to confirm if it helps.
    
    If you are already using cron to rewrite the sip.conf this test will be a simple addition by delaying starting up asterisk.
    
    Lonnie
    
    
    
    
    > On May 9, 2018, at 6:58 PM, nedi <ne...@gm...> wrote:
    > 
    > Hi,
    > 
    > I have some Astlinux boxes as local pbx after Modem with standard firewall inside modems , Astlinux have different Releases,  and since years I have this issue and can’t fix that:  
    > After a week or month and sometimes longer  the voip number can’t be registered and Status show me „rejected“ 
    > 
    > Reboot can’t help - Aterisk Reload can’t help - I can’t reproduce that for testing. 
    > If I have this problem only change the SIP Server to another Sipcall sip server can help to fix that issues. 
    > 
    > As sample if I was registered to business1.voipgateway.org I must change registrar  to business2.voipgateway.org and I can save and reload to  register without reboot.
    > 
    > I have tried  instead of registrar name to  use the ip adress but this not fixed my problem. 
    > I use Sipcall DNS IP’s to in the Astlinux Network setting that don’t help, 
    > I don’t use IPV6.  IPV6 is disabled in the Network Settings.
    > Nat and Firewall in Astlinux are enabled and.
    > 
    > I found  that I have this issue only with the provider Sipcall.ch ( if registered on different subdomains of  voipgateay.org ) and only if I use Swisscom as Internet Provider. On others provider on the same astlinux and at the same time I don’ t have this issues.
    > On the same Astlinux box by some customer I have different provider and sipcall on the same astlinux box and only the Sipcall have this all other provider worked onlythe the Sipcall account get rejected. 
    > 
    > At now I use Alix Board and AstLinux Release astlinux-1.2.6.1 i586 - Asterisk 1.8.32.3, but i had this issues with oter astlinux release to.
    > 
    > Some of my customer changed to internet with fix ip adress and  there are this issue not so often.before with Dynamic IP Adress i had this issues oftener.
    > 
    > The Sipcall support told me that is not the problem on the Sipcall site.  Some times the Sipcall told me Astlinux trying to register with old IP Adress and sometimes they told me Astlinux don’t try to register for some hours or days and they don’t  getting inquiry from pbx to register)
    > 
    > I tried to change some settings in my sip.conf and  there is nothing what helped me to resolve the issue.
    > 
    > egisterattempts=0
    > registertimeout=20
    > maxexpiry=3600
    > defaultexpiry=600
    > qualify=2500
    > srvlookup=no
    > nat=yes
    > 
    > I use a cron script if external IP changed and update the sip.conf with the new IP for dynamic IP and  again I have this problem, that not helped me great.
    > 
    > The PBX can work for weeks and months without problem but after some time I get that again.  
    > 
    > I don’t know have this issue something with Astlinux firewall or with swisscom modem or with Sipcall.
    > 
    > I think when, for some reason the registry fail and the state of the registry becomes REJECTED, asterisk stops trying to register. Can someone help me figuring out why this occur and a way to prevent asterisk from stop sending the registration requests. 
    > 
    > Does anybody have an idea about that problem ? How can we configure Asterisk to retry after some time in case of rejection ?
    > 
    > 
    > Im my sip.conf I have this:
    > 
    > 
    > I use a cron script to change the IP Adress in Astlinux  if external ip adress was changed and  again I have this problem that  some customer get rejected.
    > 
    > The PBX can work for weeks and months without problem but after some time I get that again.  
    > 
    > I don’t know have this issue something with Astlinux firewall or with swisscom modem or with Sipcall.
    > 
    > I think when, for some reason the registry fail and the state of the registry becomes REJECTED, asterisk stops trying to register. Can someone help me figuring out why this occur and a way to prevent asterisk from stop sending the registration requests. 
    > 
    > Does anybody have an idea about that problem ? How can we configure Asterisk to retry after some time in case of rejection ?
    > 
    > 
    > Im my sip.conf I have this:
    > 
    > [general]
    > useragent=mypbxname
    > port=5060   
    > context = from-sip-external; send unknown sip callers to this context
    > alwaysauthreject=yes
    > deny = 0.0.0.0/0.0.0.0
    > permit = 10.0.0.0/255.255.255.0
    > permit = 10.8.0.6/255.255.255.0
    > allowguest=no
    > disallow=all 
    > allow=alaw
    > allow=ulaw
    > language=de
    > registerattempts=0
    > registertimeout=20
    > maxexpiry=3600
    > defaultexpiry=600
    > qualify=2500
    > notifycid=yes
    > srvlookup=no
    > nat=yes
    > allow subscribe = yes
    > subscribecontext = hints
    > trustrpid=yes
    > sendrpid=yes
    > ;t38pt_udptl = yes
    > faxdetect=yes
    > 
    > register => 4171511xxxx:2345678@212.117.203.35/4171511xxxx
    > 
    > [071511xxxx]
    > type=peer
    > username=4171511xxxx
    > secret=2345678
    > host=212.117.203.35
    > ;fromuser=4171511xxxx
    > fromdomain=212.117.203.35
    > directmedia=no
    > insecure=port,invite
    > disallow=all 
    > allow=alaw
    > allow=ulaw
    > context=incoming212.117.203.35
    > dtmfmode=info
    > trustrpid=yes
    > sendrpid=pai
    > 
    > 
    > 
    > Best regards
    > Nedi
    > 
    > ------------------------------------------------------------------------------
    > 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....

Re: [Astlinux-users] Issue periodically my Astlinux can't register and show me rejected

[Lonnie A. <li...@lo...>]

Hi Nedi,

I appreciate your detailed description and for the record I feel your frustration.

I seem to recall Michael Knill described a similar situation in the recent past.

My educated guess is this is a firewall statefull-inspection "stuck-state" somewhere in the network path.  AstLinux's firewall is not the issue otherwise a reboot would solve the problem.

Long story short, as a test, I would determine a time of day where shutting down asterisk is acceptable (say 2:00 am) and keep asterisk down for 10 minutes or so, something like:

-- cron at 2:00 am or so --
service asterisk stop
sleep 600
service asterisk init
--
(make sure you don't have any other background scripts looking to restart asterisk other than the cron script)

Possibly 5 minutes is all that is needed, but I would start at 10 minutes.  Most any firewall UDP state should expire in 10 minutes.

Sadly, this test may take weeks to confirm if it helps.

If you are already using cron to rewrite the sip.conf this test will be a simple addition by delaying starting up asterisk.

Lonnie




> On May 9, 2018, at 6:58 PM, nedi <ne...@gm...> wrote:
> 
> Hi,
> 
> I have some Astlinux boxes as local pbx after Modem with standard firewall inside modems , Astlinux have different Releases,  and since years I have this issue and can’t fix that:  
> After a week or month and sometimes longer  the voip number can’t be registered and Status show me „rejected“ 
> 
> Reboot can’t help - Aterisk Reload can’t help - I can’t reproduce that for testing. 
> If I have this problem only change the SIP Server to another Sipcall sip server can help to fix that issues. 
> 
> As sample if I was registered to business1.voipgateway.org I must change registrar  to business2.voipgateway.org and I can save and reload to  register without reboot.
> 
> I have tried  instead of registrar name to  use the ip adress but this not fixed my problem. 
> I use Sipcall DNS IP’s to in the Astlinux Network setting that don’t help, 
> I don’t use IPV6.  IPV6 is disabled in the Network Settings.
> Nat and Firewall in Astlinux are enabled and.
> 
> I found  that I have this issue only with the provider Sipcall.ch ( if registered on different subdomains of  voipgateay.org ) and only if I use Swisscom as Internet Provider. On others provider on the same astlinux and at the same time I don’ t have this issues.
> On the same Astlinux box by some customer I have different provider and sipcall on the same astlinux box and only the Sipcall have this all other provider worked onlythe the Sipcall account get rejected. 
> 
> At now I use Alix Board and AstLinux Release astlinux-1.2.6.1 i586 - Asterisk 1.8.32.3, but i had this issues with oter astlinux release to.
> 
> Some of my customer changed to internet with fix ip adress and  there are this issue not so often.before with Dynamic IP Adress i had this issues oftener.
> 
> The Sipcall support told me that is not the problem on the Sipcall site.  Some times the Sipcall told me Astlinux trying to register with old IP Adress and sometimes they told me Astlinux don’t try to register for some hours or days and they don’t  getting inquiry from pbx to register)
> 
> I tried to change some settings in my sip.conf and  there is nothing what helped me to resolve the issue.
> 
> egisterattempts=0
> registertimeout=20
> maxexpiry=3600
> defaultexpiry=600
> qualify=2500
> srvlookup=no
> nat=yes
> 
> I use a cron script if external IP changed and update the sip.conf with the new IP for dynamic IP and  again I have this problem, that not helped me great.
> 
> The PBX can work for weeks and months without problem but after some time I get that again.  
> 
> I don’t know have this issue something with Astlinux firewall or with swisscom modem or with Sipcall.
> 
> I think when, for some reason the registry fail and the state of the registry becomes REJECTED, asterisk stops trying to register. Can someone help me figuring out why this occur and a way to prevent asterisk from stop sending the registration requests. 
> 
> Does anybody have an idea about that problem ? How can we configure Asterisk to retry after some time in case of rejection ?
> 
> 
> Im my sip.conf I have this:
> 
> 
> I use a cron script to change the IP Adress in Astlinux  if external ip adress was changed and  again I have this problem that  some customer get rejected.
> 
> The PBX can work for weeks and months without problem but after some time I get that again.  
> 
> I don’t know have this issue something with Astlinux firewall or with swisscom modem or with Sipcall.
> 
> I think when, for some reason the registry fail and the state of the registry becomes REJECTED, asterisk stops trying to register. Can someone help me figuring out why this occur and a way to prevent asterisk from stop sending the registration requests. 
> 
> Does anybody have an idea about that problem ? How can we configure Asterisk to retry after some time in case of rejection ?
> 
> 
> Im my sip.conf I have this:
> 
> [general]
> useragent=mypbxname
> port=5060   
> context = from-sip-external; send unknown sip callers to this context
> alwaysauthreject=yes
> deny = 0.0.0.0/0.0.0.0
> permit = 10.0.0.0/255.255.255.0
> permit = 10.8.0.6/255.255.255.0
> allowguest=no
> disallow=all 
> allow=alaw
> allow=ulaw
> language=de
> registerattempts=0
> registertimeout=20
> maxexpiry=3600
> defaultexpiry=600
> qualify=2500
> notifycid=yes
> srvlookup=no
> nat=yes
> allow subscribe = yes
> subscribecontext = hints
> trustrpid=yes
> sendrpid=yes
> ;t38pt_udptl = yes
> faxdetect=yes
> 
> register => 4171511xxxx:2345678@212.117.203.35/4171511xxxx
> 
> [071511xxxx]
> type=peer
> username=4171511xxxx
> secret=2345678
> host=212.117.203.35
> ;fromuser=4171511xxxx
> fromdomain=212.117.203.35
> directmedia=no
> insecure=port,invite
> disallow=all 
> allow=alaw
> allow=ulaw
> context=incoming212.117.203.35
> dtmfmode=info
> trustrpid=yes
> sendrpid=pai
> 
> 
> 
> Best regards
> Nedi
> 
> ------------------------------------------------------------------------------
> 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....

[Astlinux-users] Issue periodically my Astlinux can't register and show me rejected

[nedi <ne...@gm...>]

Hi,

I have some Astlinux boxes as local pbx after Modem with standard firewall inside modems , Astlinux have different Releases,  and since years I have this issue and can’t fix that:  
After a week or month and sometimes longer  the voip number can’t be registered and Status show me „rejected“ 

Reboot can’t help - Aterisk Reload can’t help - I can’t reproduce that for testing. 
If I have this problem only change the SIP Server to another Sipcall sip server can help to fix that issues. 

As sample if I was registered to business1.voipgateway.org <http://business1.voipgateway.org/> I must change registrar  to business2.voipgateway.org <http://business2.voipgateway.org/> and I can save and reload to  register without reboot.

I have tried  instead of registrar name to  use the ip adress but this not fixed my problem. 
I use Sipcall DNS IP’s to in the Astlinux Network setting that don’t help, 
I don’t use IPV6.  IPV6 is disabled in the Network Settings.
Nat and Firewall in Astlinux are enabled and.

I found  that I have this issue only with the provider Sipcall.ch <http://sipcall.ch/> ( if registered on different subdomains of  voipgateay.org <http://voipgateay.org/> ) and only if I use Swisscom as Internet Provider. On others provider on the same astlinux and at the same time I don’ t have this issues.
On the same Astlinux box by some customer I have different provider and sipcall on the same astlinux box and only the Sipcall have this all other provider worked onlythe the Sipcall account get rejected. 

At now I use Alix Board and AstLinux Release astlinux-1.2.6.1 i586 - Asterisk 1.8.32.3, but i had this issues with oter astlinux release to.

Some of my customer changed to internet with fix ip adress and  there are this issue not so often.before with Dynamic IP Adress i had this issues oftener.

The Sipcall support told me that is not the problem on the Sipcall site.  Some times the Sipcall told me Astlinux trying to register with old IP Adress and sometimes they told me Astlinux don’t try to register for some hours or days and they don’t  getting inquiry from pbx to register)

I tried to change some settings in my sip.conf and  there is nothing what helped me to resolve the issue.

egisterattempts=0
registertimeout=20
maxexpiry=3600
defaultexpiry=600
qualify=2500
srvlookup=no
nat=yes

I use a cron script if external IP changed and update the sip.conf with the new IP for dynamic IP and  again I have this problem, that not helped me great.

The PBX can work for weeks and months without problem but after some time I get that again.  

I don’t know have this issue something with Astlinux firewall or with swisscom modem or with Sipcall.

I think when, for some reason the registry fail and the state of the registry becomes REJECTED, asterisk stops trying to register. Can someone help me figuring out why this occur and a way to prevent asterisk from stop sending the registration requests. 

Does anybody have an idea about that problem ? How can we configure Asterisk to retry after some time in case of rejection ?


Im my sip.conf I have this:


I use a cron script to change the IP Adress in Astlinux  if external ip adress was changed and  again I have this problem that  some customer get rejected.

The PBX can work for weeks and months without problem but after some time I get that again.  

I don’t know have this issue something with Astlinux firewall or with swisscom modem or with Sipcall.

I think when, for some reason the registry fail and the state of the registry becomes REJECTED, asterisk stops trying to register. Can someone help me figuring out why this occur and a way to prevent asterisk from stop sending the registration requests. 

Does anybody have an idea about that problem ? How can we configure Asterisk to retry after some time in case of rejection ?


Im my sip.conf I have this:

[general]
useragent=mypbxname
port=5060   
context = from-sip-external; send unknown sip callers to this context
alwaysauthreject=yes
deny = 0.0.0.0/0.0.0.0
permit = 10.0.0.0/255.255.255.0
permit = 10.8.0.6/255.255.255.0
allowguest=no
disallow=all 
allow=alaw
allow=ulaw
language=de
registerattempts=0
registertimeout=20
maxexpiry=3600
defaultexpiry=600
qualify=2500
notifycid=yes
srvlookup=no
nat=yes
allow subscribe = yes
subscribecontext = hints
trustrpid=yes
sendrpid=yes
;t38pt_udptl = yes
faxdetect=yes

register => 4171511xxxx:2345678@212.117.203.35 <mailto:2345678@212.117.203.35>/4171511xxxx

[071511xxxx]
type=peer
username=4171511xxxx
secret=2345678
host=212.117.203.35
;fromuser=4171511xxxx
fromdomain=212.117.203.35
directmedia=no
insecure=port,invite
disallow=all 
allow=alaw
allow=ulaw
context=incoming212.117.203.35
dtmfmode=info
trustrpid=yes
sendrpid=pai



Best regards
Nedi

[Astlinux-users] AstLinux Pre-Release: astlinux-1.3-3721-36d261

[Lonnie A. <li...@lo...>]

Announcing Pre-Release Version: astlinux-1.3-3721-36d261

The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own.

-- Linux Kernel 3.16.54, security and bug fixes.

-- getdns/stubby, new package, version 1.4.1/0.2.2, encrypts local DNS queries forwarded to upstream recursive DNS-TLS servers
http://doc.astlinux-project.org/userdoc:tt_dns_tls_proxy

-- zabbix, version bump to 3.0.14, adds TLS encryption support
Note: Now requires a Zabbix server with version 3.0 or greater.

-- system-vendor, new command to identify common hardware.

-- Fossil, version bump to 2.5, adds numerous enhancements to the look and feel of the web interface.

-- util-linux, major version bump to 2.28.2

-- Asterisk 13 version bump to 13.20.0

These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project.

The "AstLinux Pre-Release ChangeLog" and "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

While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems.

If you should come across an issue, please report back here.

AstLinux Team

Re: [Astlinux-users] QueueMetrics Live

[Lonnie A. <li...@lo...>]

Hi Michael.au, :-)

> It is proprietary as far as I can gather but it does seem to work and appears to be fairly autonomous. Is there anything I should be watching out for?

I did a "ldd" of uniloader_amd64
--
	linux-vdso.so.1 (0x00007ffe4bd71000)
	libpthread.so.0 => /lib/libpthread.so.0 (0x00007f13a07ad000)
	libc.so.6 => /lib/libc.so.6 (0x00007f13a0435000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f13a09c9000)
--
and a 'strace' as it started and did not see anything alarming.

Though I'd be interested how they did their crypto, it must be statically linked within their binary.

The Loway folks have a github presence:
https://github.com/Loway

They really should make their source public, even if it has a "sole purpose of using" license as Tarsnap does
https://github.com/Tarsnap/tarsnap/blob/master/COPYING


> I will let you know how I go.

Please do.

Lonnie


On Apr 24, 2018, at 9:03 PM, Michael Knill <mic...@ip...> wrote:

> Hi thanks Lonnie
> 
> Whoops there is a --pid option so I should use that in the init script then. "killall uniloader" did work too.
> I will also put it in rc.local thanks. So would it be best to kill the process in rc.local.stop? Is this best practices?
> It is proprietary as far as I can gather but it does seem to work and appears to be fairly autonomous. Is there anything I should be watching out for?
> I guess the proof is when I install it in production. I will let you know how I go.
> 
> Thanks again.
> 
> Regards
> Michael Knill
> 
> On 25/4/18, 9:45 am, "Lonnie Abelbeck" <li...@lo...> wrote:
> 
>    Michael, comments inline ...
> 
>    On Apr 24, 2018, at 6:10 PM, Michael Knill <mic...@ip...> wrote:
> 
>> Hi thanks Lonnie and Michael for the info.
>> 
>> As I don't know of any stop requirements for uniloader I was thinking of doing the following (eventually):
> 
>    It is always good to implement stop, "killall uniloader" might do it.
> 
>> - Have a queuemetrics.conf file in /mnt/kd which contains all the parameters required for the uniloader including whether it is enabled or not
>> - Build a script which is included permanently in rc.elocal which reads this config file and runs the application if enabled with the read parameters
> 
>    rc.elocal runs quite early in the boot process, you might want to use /mnt/kd/rc.local and /mnt/kd/rc.local.stop which occurs near the end of the boot process.
> 
>> - I will also try to monitor the application with monit which restarts it using the above script if it crashes
> 
>    Again, you want to implement 'stop'
> 
>> 
>> How does this sound? Am I missing something?
>> Should I place the uniloader bin file in /usr/sbin or would I put it in /mnt/kd/bin or somewhere else?
> 
>    Definitely don't use /usr/sbin space, using /mnt/kd/bin would be fine and all under your control.
> 
>> PS I will also be running up the unitracker which is included in the uniloader which monitors outgoing calls as well!
> 
>    Question, are these proprietary binary blobs ?  Or can they be compiled ?
> 
> 
>> 
>> Thanks so much.
> 
>    Lonnie
> 
> 
> 
>> 
>> Regards
>> Michael Knill
>> 
>> On 24/4/18, 10:39 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
>> 
>> 
>>   On Apr 24, 2018, at 2:16 AM, Michael Keuter <li...@mk...> wrote:
>> 
>>> 
>>>> Am 24.04.2018 um 04:13 schrieb Michael Knill <mic...@ip...>:
>>>> 
>>>> Hi All
>>>> 
>>>> I am now currently testing QueueMetrics V17 with the uniloader application and it does appear to be working.
>>>> More testing is required but I was just wondering where I should be putting this file, how to start it on bootup and how to restart it if it crashes.
>>>> 
>>>> The command to load is recommended as (and I used):
>>>> nohup nice ./uniloader -s /var/log/asterisk/queue_log upload --uri "mysql:tcp([qmserver ip address]:3306)/queuemetrics?allowOldPasswords=1" --login [loginname] --pass [password]e --token P001  >> /var/log/uniloader.log &
>>>> 
>>>> Thanks. I will let you know how I go.
>>> 
>>> I would put the above command into its own script (e.g. in /mnt/kd/bin/) and then start it from "/mnt/kd/rc.local", which runs at the end of the boot process.
>>> Maybe you can track it then from Monit.
>>> 
>>> If you need to do something on reboot/shutdown, you could use "/mnt/kd/rc.local.stop" as well.
>> 
>>   Totally agree with Michael.
>> 
>>   Model your /mnt/kd/bin/ script after a simple /etc/init.d/ script like /etc/init.d/acpid and call it as Michael suggests from /mnt/kd/rc.local and /mnt/kd/rc.local.stop.
>> 
>>   Lonnie
>> 
>> 
>>   ------------------------------------------------------------------------------
>>   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....
> 
> 
>    ------------------------------------------------------------------------------
>    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....

Re: [Astlinux-users] QueueMetrics Live

[Michael K. <mic...@ip...>]

Hi thanks Lonnie

Whoops there is a --pid option so I should use that in the init script then. "killall uniloader" did work too.
I will also put it in rc.local thanks. So would it be best to kill the process in rc.local.stop? Is this best practices?
It is proprietary as far as I can gather but it does seem to work and appears to be fairly autonomous. Is there anything I should be watching out for?
I guess the proof is when I install it in production. I will let you know how I go.

Thanks again.

Regards
Michael Knill

On 25/4/18, 9:45 am, "Lonnie Abelbeck" <li...@lo...> wrote:

    Michael, comments inline ...
    
    On Apr 24, 2018, at 6:10 PM, Michael Knill <mic...@ip...> wrote:
    
    > Hi thanks Lonnie and Michael for the info.
    > 
    > As I don't know of any stop requirements for uniloader I was thinking of doing the following (eventually):
    
    It is always good to implement stop, "killall uniloader" might do it.
    
    > - Have a queuemetrics.conf file in /mnt/kd which contains all the parameters required for the uniloader including whether it is enabled or not
    > - Build a script which is included permanently in rc.elocal which reads this config file and runs the application if enabled with the read parameters
    
    rc.elocal runs quite early in the boot process, you might want to use /mnt/kd/rc.local and /mnt/kd/rc.local.stop which occurs near the end of the boot process.
    
    > - I will also try to monitor the application with monit which restarts it using the above script if it crashes
    
    Again, you want to implement 'stop'
    
    > 
    > How does this sound? Am I missing something?
    > Should I place the uniloader bin file in /usr/sbin or would I put it in /mnt/kd/bin or somewhere else?
    
    Definitely don't use /usr/sbin space, using /mnt/kd/bin would be fine and all under your control.
    
    > PS I will also be running up the unitracker which is included in the uniloader which monitors outgoing calls as well!
    
    Question, are these proprietary binary blobs ?  Or can they be compiled ?
    
    
    > 
    > Thanks so much.
    
    Lonnie
    
    
    
    > 
    > Regards
    > Michael Knill
    > 
    > On 24/4/18, 10:39 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
    > 
    > 
    >    On Apr 24, 2018, at 2:16 AM, Michael Keuter <li...@mk...> wrote:
    > 
    >> 
    >>> Am 24.04.2018 um 04:13 schrieb Michael Knill <mic...@ip...>:
    >>> 
    >>> Hi All
    >>> 
    >>> I am now currently testing QueueMetrics V17 with the uniloader application and it does appear to be working.
    >>> More testing is required but I was just wondering where I should be putting this file, how to start it on bootup and how to restart it if it crashes.
    >>> 
    >>> The command to load is recommended as (and I used):
    >>> nohup nice ./uniloader -s /var/log/asterisk/queue_log upload --uri "mysql:tcp([qmserver ip address]:3306)/queuemetrics?allowOldPasswords=1" --login [loginname] --pass [password]e --token P001  >> /var/log/uniloader.log &
    >>> 
    >>> Thanks. I will let you know how I go.
    >> 
    >> I would put the above command into its own script (e.g. in /mnt/kd/bin/) and then start it from "/mnt/kd/rc.local", which runs at the end of the boot process.
    >> Maybe you can track it then from Monit.
    >> 
    >> If you need to do something on reboot/shutdown, you could use "/mnt/kd/rc.local.stop" as well.
    > 
    >    Totally agree with Michael.
    > 
    >    Model your /mnt/kd/bin/ script after a simple /etc/init.d/ script like /etc/init.d/acpid and call it as Michael suggests from /mnt/kd/rc.local and /mnt/kd/rc.local.stop.
    > 
    >    Lonnie
    > 
    > 
    >    ------------------------------------------------------------------------------
    >    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....
    
    
    ------------------------------------------------------------------------------
    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....

Re: [Astlinux-users] QueueMetrics Live

[Lonnie A. <li...@lo...>]

Michael, comments inline ...

On Apr 24, 2018, at 6:10 PM, Michael Knill <mic...@ip...> wrote:

> Hi thanks Lonnie and Michael for the info.
> 
> As I don't know of any stop requirements for uniloader I was thinking of doing the following (eventually):

It is always good to implement stop, "killall uniloader" might do it.

> - Have a queuemetrics.conf file in /mnt/kd which contains all the parameters required for the uniloader including whether it is enabled or not
> - Build a script which is included permanently in rc.elocal which reads this config file and runs the application if enabled with the read parameters

rc.elocal runs quite early in the boot process, you might want to use /mnt/kd/rc.local and /mnt/kd/rc.local.stop which occurs near the end of the boot process.

> - I will also try to monitor the application with monit which restarts it using the above script if it crashes

Again, you want to implement 'stop'

> 
> How does this sound? Am I missing something?
> Should I place the uniloader bin file in /usr/sbin or would I put it in /mnt/kd/bin or somewhere else?

Definitely don't use /usr/sbin space, using /mnt/kd/bin would be fine and all under your control.

> PS I will also be running up the unitracker which is included in the uniloader which monitors outgoing calls as well!

Question, are these proprietary binary blobs ?  Or can they be compiled ?


> 
> Thanks so much.

Lonnie



> 
> Regards
> Michael Knill
> 
> On 24/4/18, 10:39 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
> 
> 
>    On Apr 24, 2018, at 2:16 AM, Michael Keuter <li...@mk...> wrote:
> 
>> 
>>> Am 24.04.2018 um 04:13 schrieb Michael Knill <mic...@ip...>:
>>> 
>>> Hi All
>>> 
>>> I am now currently testing QueueMetrics V17 with the uniloader application and it does appear to be working.
>>> More testing is required but I was just wondering where I should be putting this file, how to start it on bootup and how to restart it if it crashes.
>>> 
>>> The command to load is recommended as (and I used):
>>> nohup nice ./uniloader -s /var/log/asterisk/queue_log upload --uri "mysql:tcp([qmserver ip address]:3306)/queuemetrics?allowOldPasswords=1" --login [loginname] --pass [password]e --token P001  >> /var/log/uniloader.log &
>>> 
>>> Thanks. I will let you know how I go.
>> 
>> I would put the above command into its own script (e.g. in /mnt/kd/bin/) and then start it from "/mnt/kd/rc.local", which runs at the end of the boot process.
>> Maybe you can track it then from Monit.
>> 
>> If you need to do something on reboot/shutdown, you could use "/mnt/kd/rc.local.stop" as well.
> 
>    Totally agree with Michael.
> 
>    Model your /mnt/kd/bin/ script after a simple /etc/init.d/ script like /etc/init.d/acpid and call it as Michael suggests from /mnt/kd/rc.local and /mnt/kd/rc.local.stop.
> 
>    Lonnie
> 
> 
>    ------------------------------------------------------------------------------
>    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....

Re: [Astlinux-users] QueueMetrics Live

[Michael K. <mic...@ip...>]

Hi thanks Lonnie and Michael for the info.

As I don't know of any stop requirements for uniloader I was thinking of doing the following (eventually):
- Have a queuemetrics.conf file in /mnt/kd which contains all the parameters required for the uniloader including whether it is enabled or not
- Build a script which is included permanently in rc.elocal which reads this config file and runs the application if enabled with the read parameters
- I will also try to monitor the application with monit which restarts it using the above script if it crashes

How does this sound? Am I missing something?
Should I place the uniloader bin file in /usr/sbin or would I put it in /mnt/kd/bin or somewhere else?

PS I will also be running up the unitracker which is included in the uniloader which monitors outgoing calls as well!

Thanks so much.

Regards
Michael Knill

On 24/4/18, 10:39 pm, "Lonnie Abelbeck" <li...@lo...> wrote:

    
    On Apr 24, 2018, at 2:16 AM, Michael Keuter <li...@mk...> wrote:
    
    > 
    >> Am 24.04.2018 um 04:13 schrieb Michael Knill <mic...@ip...>:
    >> 
    >> Hi All
    >> 
    >> I am now currently testing QueueMetrics V17 with the uniloader application and it does appear to be working.
    >> More testing is required but I was just wondering where I should be putting this file, how to start it on bootup and how to restart it if it crashes.
    >> 
    >> The command to load is recommended as (and I used):
    >> nohup nice ./uniloader -s /var/log/asterisk/queue_log upload --uri "mysql:tcp([qmserver ip address]:3306)/queuemetrics?allowOldPasswords=1" --login [loginname] --pass [password]e --token P001  >> /var/log/uniloader.log &
    >> 
    >> Thanks. I will let you know how I go.
    > 
    > I would put the above command into its own script (e.g. in /mnt/kd/bin/) and then start it from "/mnt/kd/rc.local", which runs at the end of the boot process.
    > Maybe you can track it then from Monit.
    > 
    > If you need to do something on reboot/shutdown, you could use "/mnt/kd/rc.local.stop" as well.
    
    Totally agree with Michael.
    
    Model your /mnt/kd/bin/ script after a simple /etc/init.d/ script like /etc/init.d/acpid and call it as Michael suggests from /mnt/kd/rc.local and /mnt/kd/rc.local.stop.
    
    Lonnie
    
    
    ------------------------------------------------------------------------------
    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....
    

Re: [Astlinux-users] QueueMetrics Live

[Lonnie A. <li...@lo...>]

On Apr 24, 2018, at 2:16 AM, Michael Keuter <li...@mk...> wrote:

> 
>> Am 24.04.2018 um 04:13 schrieb Michael Knill <mic...@ip...>:
>> 
>> Hi All
>> 
>> I am now currently testing QueueMetrics V17 with the uniloader application and it does appear to be working.
>> More testing is required but I was just wondering where I should be putting this file, how to start it on bootup and how to restart it if it crashes.
>> 
>> The command to load is recommended as (and I used):
>> nohup nice ./uniloader -s /var/log/asterisk/queue_log upload --uri "mysql:tcp([qmserver ip address]:3306)/queuemetrics?allowOldPasswords=1" --login [loginname] --pass [password]e --token P001  >> /var/log/uniloader.log &
>> 
>> Thanks. I will let you know how I go.
> 
> I would put the above command into its own script (e.g. in /mnt/kd/bin/) and then start it from "/mnt/kd/rc.local", which runs at the end of the boot process.
> Maybe you can track it then from Monit.
> 
> If you need to do something on reboot/shutdown, you could use "/mnt/kd/rc.local.stop" as well.

Totally agree with Michael.

Model your /mnt/kd/bin/ script after a simple /etc/init.d/ script like /etc/init.d/acpid and call it as Michael suggests from /mnt/kd/rc.local and /mnt/kd/rc.local.stop.

Lonnie

Re: [Astlinux-users] QueueMetrics Live

[Michael K. <mic...@ip...>]

Cool yes I forgot Monit can do that. Thanks for that.

Regards
Michael Knill
On 24/4/18, 5:16 pm, "Michael Keuter" <li...@mk...> wrote:

    
    > Am 24.04.2018 um 04:13 schrieb Michael Knill <mic...@ip...>:
    > 
    > Hi All
    >  
    > I am now currently testing QueueMetrics V17 with the uniloader application and it does appear to be working.
    > More testing is required but I was just wondering where I should be putting this file, how to start it on bootup and how to restart it if it crashes.
    >  
    > The command to load is recommended as (and I used):
    > nohup nice ./uniloader -s /var/log/asterisk/queue_log upload --uri "mysql:tcp([qmserver ip address]:3306)/queuemetrics?allowOldPasswords=1" --login [loginname] --pass [password]e --token P001  >> /var/log/uniloader.log &
    >  
    > Thanks. I will let you know how I go.
    
    I would put the above command into its own script (e.g. in /mnt/kd/bin/) and then start it from "/mnt/kd/rc.local", which runs at the end of the boot process.
    Maybe you can track it then from Monit.
    
    If you need to do something on reboot/shutdown, you could use "/mnt/kd/rc.local.stop" as well.
     
    > Regards
    > Michael Knill
    > From: Michael Keuter <li...@mk...>
    > Reply-To: AstLinux List <ast...@li...>
    > Date: Thursday, 5 October 2017 at 7:33 am
    > To: AstLinux List <ast...@li...>
    > Subject: Re: [Astlinux-users] QueueMetrics Live
    >  
    > And, have you tried to run the uniloader binary from /mnt/kd/ and adjust the rc.local part?
    > 
    > Sent from a mobile device. 
    >  
    > Michael Keuter
    > 
    > Am 04.10.2017 um 20:44 schrieb Michael Knill <mic...@ip...>:
    > 
    > Thanks Michael
    >  
    > Unfortunately QueueMetrics Live, which is their hosted service does not support this script. Only the new uniloader binary described here.
    >  
    > Regards
    > Michael Knill
    >  
    > From: Michael Keuter <li...@mk...>
    > Reply-To: AstLinux List <ast...@li...>
    > Date: Thursday, 5 October 2017 at 12:08 am
    > To: AstLinux List <ast...@li...>
    > Subject: Re: [Astlinux-users] QueueMetrics Live
    >  
    > Michael,
    >  
    > you would need an external server/VM with a MySQL server to install Queuemetrics on.
    >  
    > Years ago I had a conversation with Lenz about AstLinux and Queuemetrics.
    > At least on older versions a "qloaderd" Perl script was needed on the AstLinux side to periodically update the  SQL database with the data from Asterisk (queue_log and CDR). Maybe additional Perl modules might be needed in AstLinux.
    >  
    > http://manuals.loway.ch/QLoader-chunked/ar01s01.html
    > 
    > Sent from a mobile device.
    >  
    > Michael Keuter
    > 
    > Am 04.10.2017 um 13:17 schrieb Michael Knill <mic...@ip...>:
    > 
    > Should this work with Astlinux?
    >  
    > https://www.queuemetrics-live.com/install.jsp
    >  
    > Regards
    > Michael Knill
    
    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....
    

Re: [Astlinux-users] QueueMetrics Live

[Michael K. <li...@mk...>]

> Am 24.04.2018 um 04:13 schrieb Michael Knill <mic...@ip...>:
> 
> Hi All
>  
> I am now currently testing QueueMetrics V17 with the uniloader application and it does appear to be working.
> More testing is required but I was just wondering where I should be putting this file, how to start it on bootup and how to restart it if it crashes.
>  
> The command to load is recommended as (and I used):
> nohup nice ./uniloader -s /var/log/asterisk/queue_log upload --uri "mysql:tcp([qmserver ip address]:3306)/queuemetrics?allowOldPasswords=1" --login [loginname] --pass [password]e --token P001  >> /var/log/uniloader.log &
>  
> Thanks. I will let you know how I go.

I would put the above command into its own script (e.g. in /mnt/kd/bin/) and then start it from "/mnt/kd/rc.local", which runs at the end of the boot process.
Maybe you can track it then from Monit.

If you need to do something on reboot/shutdown, you could use "/mnt/kd/rc.local.stop" as well.
 
> Regards
> Michael Knill
> From: Michael Keuter <li...@mk...>
> Reply-To: AstLinux List <ast...@li...>
> Date: Thursday, 5 October 2017 at 7:33 am
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] QueueMetrics Live
>  
> And, have you tried to run the uniloader binary from /mnt/kd/ and adjust the rc.local part?
> 
> Sent from a mobile device. 
>  
> Michael Keuter
> 
> Am 04.10.2017 um 20:44 schrieb Michael Knill <mic...@ip...>:
> 
> Thanks Michael
>  
> Unfortunately QueueMetrics Live, which is their hosted service does not support this script. Only the new uniloader binary described here.
>  
> Regards
> Michael Knill
>  
> From: Michael Keuter <li...@mk...>
> Reply-To: AstLinux List <ast...@li...>
> Date: Thursday, 5 October 2017 at 12:08 am
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] QueueMetrics Live
>  
> Michael,
>  
> you would need an external server/VM with a MySQL server to install Queuemetrics on.
>  
> Years ago I had a conversation with Lenz about AstLinux and Queuemetrics.
> At least on older versions a "qloaderd" Perl script was needed on the AstLinux side to periodically update the  SQL database with the data from Asterisk (queue_log and CDR). Maybe additional Perl modules might be needed in AstLinux.
>  
> http://manuals.loway.ch/QLoader-chunked/ar01s01.html
> 
> Sent from a mobile device.
>  
> Michael Keuter
> 
> Am 04.10.2017 um 13:17 schrieb Michael Knill <mic...@ip...>:
> 
> Should this work with Astlinux?
>  
> https://www.queuemetrics-live.com/install.jsp
>  
> Regards
> Michael Knill

Michael

http://www.mksolutions.info

Re: [Astlinux-users] QueueMetrics Live

[Michael K. <mic...@ip...>]

Hi All

I am now currently testing QueueMetrics V17 with the uniloader application and it does appear to be working.
More testing is required but I was just wondering where I should be putting this file, how to start it on bootup and how to restart it if it crashes.

The command to load is recommended as (and I used):
nohup nice ./uniloader -s /var/log/asterisk/queue_log upload --uri "mysql:tcp([qmserver ip address]:3306)/queuemetrics?allowOldPasswords=1" --login [loginname] --pass [password]e --token P001  >> /var/log/uniloader.log &

Thanks. I will let you know how I go.

Regards
Michael Knill
From: Michael Keuter <li...@mk...>
Reply-To: AstLinux List <ast...@li...>
Date: Thursday, 5 October 2017 at 7:33 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] QueueMetrics Live

And, have you tried to run the uniloader binary from /mnt/kd/ and adjust the rc.local part?

Sent from a mobile device.

Michael Keuter

Am 04.10.2017 um 20:44 schrieb Michael Knill <mic...@ip...<mailto:mic...@ip...>>:
Thanks Michael

Unfortunately QueueMetrics Live, which is their hosted service does not support this script. Only the new uniloader binary described here.

Regards
Michael Knill

From: Michael Keuter <li...@mk...<mailto:li...@mk...>>
Reply-To: AstLinux List <ast...@li...<mailto:ast...@li...>>
Date: Thursday, 5 October 2017 at 12:08 am
To: AstLinux List <ast...@li...<mailto:ast...@li...>>
Subject: Re: [Astlinux-users] QueueMetrics Live

Michael,

you would need an external server/VM with a MySQL server to install Queuemetrics on.

Years ago I had a conversation with Lenz about AstLinux and Queuemetrics.
At least on older versions a "qloaderd" Perl script was needed on the AstLinux side to periodically update the  SQL database with the data from Asterisk (queue_log and CDR). Maybe additional Perl modules might be needed in AstLinux.

http://manuals.loway.ch/QLoader-chunked/ar01s01.html
Sent from a mobile device.

Michael Keuter

Am 04.10.2017 um 13:17 schrieb Michael Knill <mic...@ip...<mailto:mic...@ip...>>:
Should this work with Astlinux?

https://www.queuemetrics-live.com/install.jsp

Regards
Michael Knill
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org<http://Slashdot.org>! http://sdm.link/slashdot
_______________________________________________
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...>.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org<http://Slashdot.org>! http://sdm.link/slashdot
_______________________________________________
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...>.