[App_rpt-users] Update on registration

Mr. Possum (Bill) flatpossum1231 at yahoo.com
Tue Aug 14 13:31:20 UTC 2018


Bryan,
I went and looked at the /var/lib/asterisk/rpt_extnodes file and it had nothing in it...  Nada...  And my main hub node keeps registering as 209.112.233.252:1127 when it SHOULD be 209.112.233.252:4571...
I've got a few nodes registering like this...  and the rpt_extnodes is a 1KB file dated 4/3/2015?

Can you hand me a clue?

Thanks!
Bill - N5MBMwww.texasrepeaternetwork.net

      From: Bryan Fields <Bryan at bryanfields.net>
 To: Users of Asterisk app_rpt <app_rpt-users at lists.allstarlink.org> 
 Sent: Tuesday, August 14, 2018 8:17 AM
 Subject: [App_rpt-users] Update on registration
   
We still have about ~200 nodes trying to register to the old server; please
check your node and reboot it if it's not registering.  Enabling dnsmgr will
prevent this in the future and allow asterisk to failover to other servers.
Please enable dnsmgr.  We've tried to email most of these we can identify, but
several have bounced back as the email on file is different.

The vast majority of nodes (90%) came back up fine on Sunday, but we were
having some serious issues with call number exhaustion from nodes which don't
authenticate, and then hammer the server over and over again.  Once you're out
of call numbers on IAX, even valid nodes cannot authenticate.  I think we've
resolved this enough for now, there will be a better fix coming, but it's in
test.  As these are on a per IP basis, we didn't see this in testing as only
about 200 hosts tested the cluster even though we had each host registering
100 nodes.

The other unplanned event was nodes behind broken NAT.  IAX requires a full
cone nat to work and we tested with this, and everything worked.  What was
unplanned was when nat was broken, and Tim was able to come up with a fix to
the nodes script for this.  This script was completely rewritten and optimized
with a 10 second cache, allowing us to generate it every 10 seconds across
many servers.  Previously the delta between the database and the nodes scripts
was about 5 minutes, so this greatly speeds it up.

If you look in /var/lib/asterisk/rpt-extnodes you'll see the cache info and
which server generated it.
Example:
;Generated 2574 records in 0.059 seconds.
;Served in 0.015 seconds.
;Served from cache: Yes
;Generated at 2018-08-14 13:01:26 UTC by register-ord.allstarlink.org

In the above example there are 2574 nodes online, and it was served from cache
by the Chicago server.

The phone portal has been tweaked, and no longer reads back the invalid
numbers at first call in.  We've been doing much testing with it, and it's
much much better as there are no longer 2900 nodes registering to it as well.
I've yet to hear it stutter.

73's

-- 
Bryan Fields

727-409-1194 - Voice
http://bryanfields.net
_______________________________________________
App_rpt-users mailing list
App_rpt-users at lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. 


   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20180814/0edd7d35/attachment.html>


More information about the App_rpt-users mailing list