[App_rpt-users] Registry re-requests

David Shaw shawpbx at gmail.com
Thu Mar 23 15:59:17 UTC 2017 

Hello Bill,

Yes, Asterisk registers every 50 seconds. You can see that the Refresh rate
"60" is shown in iax2 show registered.
Here is what my node shows.

2063*CLI> iax2 show registry
Host                  dnsmgr  Username    Perceived             Refresh
 State
67.215.233.178:4569   Y       2064        76.91.82.94:4570           60
 Registered
67.215.233.178:4569   Y       2063        76.91.82.94:4570           60
 Registered



[Mar 23 08:28:38] WARNING[1128]: chan_iax2.c:10127 iax2_do_register:
REGISTER-LOG: Sending registration request for '2064'
[Mar 23 08:28:38] WARNING[1129]: chan_iax2.c:10127 iax2_do_register:
REGISTER-LOG: Sending registration request for '2063'
[Mar 23 08:28:38] WARNING[1130]: chan_iax2.c:7690 registry_rerequest:
REGISTER-LOG: registry rereqquest
[Mar 23 08:28:38] WARNING[1123]: chan_iax2.c:7690 registry_rerequest:
REGISTER-LOG: registry rereqquest
  == Parsing '/etc/asterisk/gps.conf': Found
  == Parsing '/etc/asterisk/gps.conf': Found
[Mar 23 08:29:27] NOTICE[1119]: chan_echolink.c:2179 sendcmd: Received OK
from Echolink server server1.echolink.org
[Mar 23 08:29:27] NOTICE[1119]: chan_echolink.c:2484 do_el_directory:
Directory pgm done downloading(partial,compressed), 915 records
[Mar 23 08:29:28] WARNING[1129]: chan_iax2.c:10127 iax2_do_register:
REGISTER-LOG: Sending registration request for '2064'
[Mar 23 08:29:28] WARNING[1121]: chan_iax2.c:7690 registry_rerequest:
REGISTER-LOG: registry rereqquest
[Mar 23 08:29:28] WARNING[1122]: chan_iax2.c:10127 iax2_do_register:
REGISTER-LOG: Sending registration request for '2063'
[Mar 23 08:29:28] WARNING[1125]: chan_iax2.c:7690 registry_rerequest:
REGISTER-LOG: registry rereqquest

After reading all the post. I don't think this is a OS problem (N4IRS can
chime in) but more of network or USB problem. I'm using good old Limey
Linux and a 4 port pci card.
Allstar uses UDP. Drop a UDP packet and that will drop out on the repeater.
SSH and SNMP uses TCP. Drop out a TCP packet. It will send a replacement
packet. No loss of data but slower.


Are you using both WiFi and Ethernet at the same time? I would try using
just one mode to access the internet. How are you connecting to the
Internet? i.e. WiFi to a cell hotspot or WiFi to a Mesh Network? What kind
of local network?

"Modular connectors and Cat-7 cable for the interface with snap-on chokes
at both ends
Pi is connected to the local network via Wifi (We are prepared to move this
to Ethernet, but need approval of the host to do so)"

If this is a network problem. I would use the mrt command to test your
network to the ASL server. Google Linux MRT and Linux MRT save to a file.

Let us know.
David
KE6UPI



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither
inclined nor determined to commit crimes. Such laws make things worse for
the assaulted and better for the assailants; they serve rather to encourage
than prevent homicides, for an unarmed man may be attacked with greater
confidence than an armed one."
Thomas Jefferson

On Wed, Mar 22, 2017 at 9:17 AM, William Higgins <higgins.ws at gmail.com>
wrote:

> Steve,
>
> I have felt that it was ok.  I seem to be able to get to it remotely via
> SSH at will and I have not noticed any loss of SNMP data.
>
> One more interesting note.  I took a look at my simplex multinode (43758
> and 43936) here at my QTH and it's doing exactly the same thing.  That
> system is a mini ITX PC based DIAL system.  The only things these two
> systems have in common are:  1.) I was the builder, 2.) they're both using
> RIM LITE style interfaces, and 3.) they are both behind NAT routers (with
> the appropriate ports forwarded of course).
>
> Bill
>
>
> >William,
> >Have you verified good connectivity from your node to the net? I am
> >watching the reregistration server now to see I can catch any hints.
> >
> >73, Steve
> >
> >On 03/21/2017 05:52 PM, William Higgins wrote:
> > Still on a quest to find out why my repeater node is behaving badly
> > re: audio dropouts, I decided to look with more depth at the events in
> > asterisk.
> >
> > I set verbose level to 6 and saw this recurring pattern.
> >
> > A section of the log output to the console follows:
> >
> > [Mar 21 16:36:58] WARNING[818]: chan_iax2.c:10127 iax2_do_register:
> > REGISTER-LOG: Sending registration request for '44011'
> > [Mar 21 16:37:00] WARNING[822]: chan_iax2.c:7690 registry_rerequest:
> > REGISTER-LOG: registry rereqquest
> > [Mar 21 16:37:50] WARNING[815]: chan_iax2.c:10127 iax2_do_register:
> > REGISTER-LOG: Sending registration request for '44011'
> > [Mar 21 16:37:52] WARNING[818]: chan_iax2.c:7690 registry_rerequest:
> > REGISTER-LOG: registry rereqquest
> >     -- Received OK from Echolink server nawest.echolink.org
> > <http://nawest.echolink.org/>
> >     -- Received OK from Echolink server nawest.echolink.org
> > <http://nawest.echolink.org/>
>
> >     -- Directory pgm done downloading(partial,compressed), 394 records
> > [Mar 21 16:38:42] WARNING[819]: chan_iax2.c:10127 iax2_do_register:
> > REGISTER-LOG: Sending registration request for '44011'
> > [Mar 21 16:38:44] WARNING[815]: chan_iax2.c:7690 registry_rerequest:
> > REGISTER-LOG: registry rereqquest
> > [Mar 21 16:39:34] WARNING[816]: chan_iax2.c:10127 iax2_do_register:
> > REGISTER-LOG: Sending registration request for '44011'
> > [Mar 21 16:39:36] WARNING[819]: chan_iax2.c:7690 registry_rerequest:
> > REGISTER-LOG: registry rereqquest
> >
> > After looking at it for a while, I noticed that the time delta between
> > the "registry rerequests" and the following "do_register" is exactly
> > 50 seconds.  Is this normal?  Does it really need to re-register that
> > often or does it indicate a network problem with the Rpi's connection
> > to the outside world?
> >
> > My configuration again is:
> >
> > Raspberry Pi 3 with DIAL RAT_RC1.img
> > Repeater Builder RB-USB Rim Lite Interface
> > Vertex VXR-7000 Repeater
> > Metallic case for the Pi
> > Modular connectors and Cat-7 cable for the interface with snap-on
> > chokes at both ends
> > Pi is connected to the local network via Wifi (We are prepared to move
> > this to Ethernet, but need approval of the host to do so)
> > Pi is connected to an external server via OpenVPN for collection of
> > mgmt. statistics via SNMP
> > Pi also runs Apache2 and Allmon2
> > Echolink is enabled (Node 746074)
> > AllStarLink of course (Node 44011)
> >
> > Thanks for any insight you might be able to lend!
> >
> > Bill Higgins
> > N0NOE
>
> _______________________________________________
> 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/20170323/c9940c42/attachment.html>

More information about the App_rpt-users mailing list