[arm-allstar] Trouble connecting to nodes at start up

Sun Nov 19 09:38:08 EST 2017

Jim,

 Well I don't think your problem is the same as Chris. He was registered
but not receiving node updates. I take it you applied for a node number and
have heard nothing back? That is another issue. How long has it been since
you applied?

*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Sun, Nov 19, 2017 at 6:41 AM, "James Hause via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Hi Doug,
>    Hey I received the email trail you have with Chris.  I seem to have the
> same problem, and saw you were going to private email Chris back.
> I applied t get registered on ARM-Allstar, and haven't got my email back
> yet with approval,
> Sure would like to know what the solution is.
>
> On Sat, Nov 18, 2017 at 4:21 PM, "Doug Crompton via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Chris,
> >
> >  Yes, I will email you privately about this.
> >
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> >
> > On Sat, Nov 18, 2017 at 4:54 PM, Chris Souleles <csouleles at prodigy.net>
> > wrote:
> >
> > > Did the suggested checks and here are the results.
> > >
> > > Node is registered.  Checked several times and it always comes up
> > > registered.
> > >
> > > When it won't connect I get "no such file or directory" when I execute
> > the grep
> > > 40000 /tmp/rpt_extnodes command with any node number inserted replacing
> > the
> > > 40000.
> > >
> > > When it will connect I get a routing response for any node number I
> > insert
> > > when I execute the command.
> > >
> > > So it appears when it won't connect it doesn't have the
> /tmp/rpt_extnodes
> > > file and when it does connect it has it.
> > >
> > > Is there something I can do to make sure it always has the
> > /tmp/rpt_extnodes
> > > file after start up?
> > >
> > > Chris - W6CS - 73.
> > > ------------------------------
> > > *From:* Doug Crompton via arm-allstar <arm-allstar at hamvoip.org>
> > > *To:* ARM Allstar <arm-allstar at hamvoip.org>
> > > *Cc:* Doug Crompton <wa3dsp at gmail.com>
> > > *Sent:* Saturday, November 18, 2017 8:21 AM
> > > *Subject:* Re: [arm-allstar] Trouble connecting to nodes at start up
> > >
> > > Chris,
> > >
> > >   You checked quite a few things and that is good but there are a few
> > other
> > > things to check. Make sure you have you are registered. You can run
> > >
> > > check_reg.sh
> > >
> > > at the Linux prompt.
> > >
> > > Then make sure you have the /tmp/rpt_extnodes file and that it has the
> > info
> > > for the node you want to connect to. You can type
> > >
> > > grep 40000 /tmp/rpt_extnodes
> > >
> > > at the linux prompt, where 40000 is replaced with the node number you
> > want
> > > to check. This will return the routing info for that node or nothing if
> > it
> > > does not exisit.
> > >
> > > Also how the system responds when you do a connect tells you a little
> > about
> > > what is going on. If you just get a beep or nothing in response to a
> > > connect it means you have no info for that node and probably no
> > rpt_exnodes
> > > file. If you get a failure to connect it could mean many things but one
> > > could be that the other end does not have node information for you.
> > >
> > > I would also say try and run your node wired if you can to see if there
> > is
> > > a difference.
> > >
> > > We are about to roll out the DNS node lookup code which should
> eliminate
> > > many of these problems but until then the rpt_extnodes file must be
> there
> > > and the node you want to connect to must be listed in it.
> > >
> > > Let us know what you find out.
> > >
> > >
> > > *73 Doug*
> > >
> > > *WA3DSP*
> > >
> > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Sat, Nov 18, 2017 at 10:39 AM, "Chris Souleles via arm-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > > >
> > > > I've been having trouble getting my node to connect to other nodes
> > after
> > > > start up. I wait 10 or fifteen minutes after start up and there is no
> > > > response when I try to connect to another node.  I have to halt and
> > turn
> > > > power on and off a few times to get it to work.  Once it connects to
> a
> > > > node, then after that everything is normal and I can connect and
> > > disconnect
> > > > with no problem.
> > > > It properly reports the IP address. Asterisk shows the proper DTMF
> > > > commands. Wireless status indicates the proper wireless network and
> the
> > > > correct IP address. The echo command will echo my voice. COS and PTT
> > > work.
> > > > My cable modem and wireless network work for everything else.
> > > > My configuration is RPI 3, URIx, BF888, simplex node, and I
> downloaded
> > > the
> > > > hamvoip 1.5 a couple weeks ago so it is pretty current.  I'm
> connected
> > > > wireless.  Any ideas?
> > > > Chris - W6CS - 73
> > > > Simple USB parameters:Card is:        0Name is:        usbRx Level:
> > > >  500Rx no-delay:    0Rx audio-delay:  5Tx A Level:      300Tx B
> Level:
> > > >  0preemphasis:    nodeemphasis:      noplfilter:        yesrxboost:
> > > >    yesPTT:            Active LOWPTT status:      Un-KeyedCTCSS
> (input):
> > > >  IgnoredCOS (input):    CM108/CM119 Active HIGHCOS (test):
> > > > Un-KeyedCOS (composite): Un-Keyed
> > > > Web error log (from Supermon) showed the following.  I don't know if
> it
> > > is
> > > > relevant.AH00558: httpd: Could not reliably determine the server's
> > fully
> > > > qualified domain name, using 127.0.0.2. Set the 'ServerName'
> directive
> > > > globally to suppress this message[Fri Nov 17 20:17:00.884764 2017]
> > > > [lbmethod_heartbeat:notice] [pid 345] AH02282: No slotmem from
> > > > mod_heartmonitor[Fri Nov 17 20:17:01.164689 2017]
> [mpm_prefork:notice]
> > > [pid
> > > > 345] AH00163: Apache/2.4.18 (Unix) PHP/7.0.4 configured -- resuming
> > > normal
> > > > operations[Fri Nov 17 20:17:01.164882 2017] [core:notice] [pid 345]
> > > > AH00094: Command line: '/usr/bin/httpd -D FOREGROUND'
> > > > _______________________________________________
> > > >
> > > > arm-allstar mailing list
> > > > arm-allstar at hamvoip.org
> > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > >
> > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >
> > > _______________________________________________
> > >
> > > arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >
> > >
> > >
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>