[arm-allstar] Connection issue

Jay Urish jay at unixwolf.net
Mon Jul 9 13:02:18 EST 2018


David,

I would connect to arlington hub and watch the logs there as you try and 
connect from Brady. It may shed some light on the issue.



On 07/09/2018 12:50 PM, "david--- via arm-allstar" wrote:
> I noticed that the Brady repeater node 47613 was disconnected this 
> morning. I logged in to reconnect it and it would not:
>
> Asterisk 1.4.23-pre.hamvoip-V1.5.3-34-app_rpt-0.327-07/02/2018, 
> Copyright (C) 1999 - 2018 HamVoIP.org and others.
> Created by Mark Spencer <markster at digium.com>
> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' 
> for details.
> This is free software, with components licensed under the GNU General 
> Public
> License version 2 and other licenses; you are welcome to redistribute 
> it under
> certain conditions. Type 'core show license' for details.
> =========================================================================
> Connected to Asterisk 
> 1.4.23-pre.hamvoip-V1.5.3-34-app_rpt-0.327-07/02/2018 currently 
> running on Brady (pid = 337)
> Verbosity was 3 and is now 4
>     -- Hungup 'DAHDI/pseudo-393336362'
> Brady*CLI> rpt fun 47613 *347117
>     -- Call accepted by 47.187.116.32 (format g726aal2)
>     -- Format for call is g726aal2
>     -- Hungup 'IAX2/47.187.116.32:4577-2894'
>     -- Hungup 'DAHDI/pseudo-793169936'
>     -- Hungup 'DAHDI/pseudo-1021286344'
>     -- <DAHDI/pseudo-1051465087> Playing 'rpt/node' (language 'en')
>     -- <DAHDI/pseudo-1051465087> Playing 'digits/4' (language 'en')
>     -- <DAHDI/pseudo-1051465087> Playing 'digits/7' (language 'en')
>     -- <DAHDI/pseudo-1051465087> Playing 'digits/1' (language 'en')
>     -- <DAHDI/pseudo-1051465087> Playing 'digits/1' (language 'en')
>     -- <DAHDI/pseudo-1051465087> Playing 'digits/7' (language 'en')
>     -- <DAHDI/pseudo-1051465087> Playing 'rpt/connection_failed' 
> (language 'en')
>     -- Hungup 'DAHDI/pseudo-1051465087'
>
> I reloaded asterisk, pinged allstarlink successfully and the same 
> error occurred when trying to connect. I figured it be best to boot 
> the node. Since I did not want to wait 2 hours for it to register, I 
> added the DNS setup. I booted the node and  it was insistently 
> registered. I pinged allstarlink, I ran lookup, and tried connecting 
> to different nodes with the same issue. The ping and lookup worked and 
> indicated everything is fine. At this point I do not believe its a 
> registration issue and need help where I should be looking now to 
> correct my issue.
>
> Thanks, David KG5RDF
>
> _______________________________________________
>
> 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



More information about the arm-allstar mailing list