[arm-allstar] Connect time

[James Hause]

Doug, just one other note. According to Allstar Link site, it has the
following info on registering:

To use the new update process, a registration statement is added to the
general section of /etc/asterisk/iax.conf using a text editor such as vi,
emacs, or nano. The format of the register statement is:

register=node:password at register.allstarlink.org

I checked my iax.conf, and it has the following
register => 46738:password at register.allstarlink.org  (Note, I replaced here
my password # with the word password, assume I don't want this public)

Sorry for a dumb question here, but note mine has register =>, where the
example above shows register=, ie no >.



On Wed, Jul 4, 2018 at 11:56 AM, James Hause <hausejd at gmail.com> wrote:

> Thanks Doug for the reply.  I am still learning, will spend some time
> digesting what you sent.
> I have a simplex node on a Pi3, with latest version of hamvoip. I check
> the Allstar Active Nodes page,
> shows me as registered, but I have not executed the command you
> referenced.  I need to do more homework
> on my end, the how to list has provided help, will keep on researching.
> Need to come up to speed on what DNS lookup
> is, how it works, etc.  Call sign is KF5LBT, node is 46738.
>
> On Wed, Jul 4, 2018 at 11:36 AM, "Doug Crompton via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> Jim,
>>
>>   Not sure if you are now using DNS lookup but I if so I can assure you
>> that is not the problem. If you are not and would like to try it let me
>> know. This could also be because you are not registering right away at
>> boot. You should check that using check_reg.sh at the Linux prompt. If you
>> are not registered you will not be able to connect whether or not you are
>> using DNS lookup. There have been sporadic registration issues for quite
>> some time especially with nodes going on and off line often.
>>
>> The classic way of looking up nodes on Allstar has been that you boot,
>> then
>> register, then download the flat file of all nodes mapped to IP addresses.
>> This is around a 150K byte file. So you have the info but the node you are
>> trying to connect to does not until they do a periodic download of the
>> file. This could take up to 15 minutes.
>>
>> Using DNS and assuming that BOTH ends are using it, the information
>> propagates in under 30 seconds and a connection can take place. But if
>> only
>> one end was using DNS lookup the same long delay would apply.
>>
>> So to sum it up you first have to register and be in the database, then
>> you
>> can connect out but the node you are trying to connect to cannot complete
>> the connection until THEY have your connection information.
>>
>> Once the DNS and registration system is fully in place the connection time
>> delay will be immediate at boot between nodes using that method and a lot
>> of the current problems will go away. This is yet another reason to retire
>> your Beaglebone Blacks and update to V1.5 using a Pi!
>>
>>
>> *73 Doug*
>>
>> *WA3DSP*
>>
>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>
>>
>> On Wed, Jul 4, 2018 at 10:01 AM, "James Hause via arm-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>> > For over a week, when I power up my simplex node, I can't connect to any
>> > other nodes until my node has been running for well over 30 minutes to
>> an
>> > hour.  Once I am able to connect, all works fine, can disconnect and
>> > connect just fine.  This have something to do with the DNS lookup?  I
>> know
>> > a change for that is about to be released.
>> > _______________________________________________
>> >
>> > 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
>>
>
>