[arm-allstar] Permanent link failing

Thu Jun 29 13:54:36 EST 2017

Doug,
I don't think this is a new issue but something that has been lurking in 
the code for a long time.
It happened to me a year or two ago.

At the time I only had 2 nodes connected together full time (permanent 
link) on boot up.
On 3 or 4 occasions say node 1 would transmit link audio from node 2 but 
node 2 would not transmit link audio from node 1.
Node 2 would transmit audio out the transmitter. It was like node 1 was 
in monitor mode, not transceive mode.

I never took the time to try to debug the issue. I think all I did was 
to reboot the node 2 and all was well again.

It's very possible that at the time I may have had some network issues 
back then but I would not think that would cause that kind of problem.

  Like I said, it's not that the link was not connected, it was like one 
node went into monitor mode.

73's
LaRoy McCann / K5TW

On 6/29/2017 11:59 AM, "Doug Crompton via arm-allstar" wrote:
> OK, so before everyone all of the sudden has the same problem let me say I
> run a hub with 30+ sometimes 40+ connections with at least 60% of them
> permanent. These are all direct 24/7 connections to me. I also run several
> outgoing permanent connections from me. This is a busy hub with
> broadcastify and Echolink running. I have never seen this problem. I
> suspect it is isolated to some special case or perhaps a misunderstanding
> of what a permanent connection is.
>
> When node A makes a permanent connection to node B and anything goes down
> between node A and B it will re-establish. This includes node B restarting
> or rebooting. It does not include node A, the originating node. If node A
> goes down, restarts, reboots or has some similar SW issue the connection
> will cease. Both node A and node B can terminate the connection manually.
>
> When I restart my hub, which is rare, within a few minutes all permanent
> connections are re-established.
>
> I would also say that as Dave pointed out before, this could be a codec
> problem. I limit codecs on connections to my hub to ulaw and g726. You can
> limit codec use in iax.conf by commenting the codecs you don't want in the
> general and radio sections. Transcoding (converting from one codec format
> to another) is processor intensive and you want to limit that as much as
> possible especially when you have many connections. For point to point
> connections like repeater links where BW is not an issue ulaw is often used.
>
> Open an asterisk client window and open the screen up wide. Do  'iax2 show
> channels'  This will give you a good indication of channel quality due to
> lag (rtt) and jitter. If these are above 200ms you could have problems.
> Typically they run considerably less than 100ms on a good circuit, This
> also shows what codec is being used once the circuit passes data.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
> On Thu, Jun 29, 2017 at 11:12 AM, "Justin Reed via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> I've been having the same issue. As a workaround I'm going back to the
>> method that avoided problems on irlp.  At 3am I disconnect and at 3:05am
>> reconnect. Since doing this I haven't been seeing the issue.
>>
>> Regards,
>> Justin
>>
>>> On Jun 29, 2017, at 9:42 AM, Eric Harrison via arm-allstar <
>> arm-allstar at hamvoip.org> wrote:
>>> I have recently experience the same issue. Permanent connected node for
>> several days on the network is only giving one way audio.
>>>   Eric (N7JYS)
>>> Marshall's Communications
>>>
>>>       From: C B via arm-allstar <arm-allstar at hamvoip.org>
>>> To: "doug at crompton.com" <doug at crompton.com>
>>> Cc: C B <harvard5362 at yahoo.com>; ARM Allstar <arm-allstar at hamvoip.org>
>>> Sent: Thursday, June 29, 2017 8:58 AM
>>> Subject: Re: [arm-allstar] Permanent link failing
>>>
>>> Hi
>>> the same problem happened again this time 2 nodes connected on the same
>> HP 2920 switch, thus no way for this to be a connectivity issue.
>>> the link only passed audio and signaling in one direction.
>>> dialing *70 both nodes reported connected and transceive.
>>> droping the link with *71XXXXX and restoring with *73XXXXX cleared the
>> issue
>>> i was not near a computer and the net was about to begin thus i could
>> not look at the asterisk CLI for any errors.
>>> upon review of the logs at /var/logs/asterisk/messages there where no
>> messages during the time that this error occurred on either node.
>>> Please i do really need some help with this.
>>> Chris
>>>
>>>
>>>
>>>        From: Doug Crompton <wa3dsp at gmail.com>
>>> To: C B <harvard5362 at yahoo.com>
>>> Cc: ARM Allstar <arm-allstar at hamvoip.org>
>>> Sent: Wednesday, June 21, 2017 10:03 AM
>>> Subject: Re: [arm-allstar] Permanent link failing
>>>
>>> Chris,
>>>
>>>   Unfortunately I don't really have an answer for your problem. Sometimes
>> what you think is a reliable connection is really not. It it was a private
>> 100% up link then a non permanent connection should stay up. Did you try
>> that and determine if it stays up any length of time.
>>> Also monitor the logs in the client or at /var/log/asterisk/messages.
>>>
>>> 73 Doug
>>> WA3DSP
>>> http://www.crompton.com/ hamradio
>>>
>>>
>>> On Wed, Jun 21, 2017 at 12:29 PM, C B <harvard5362 at yahoo.com> wrote:
>>>
>>> Thanks for the quick response.
>>> All nodes involved here are my nodes.
>>> All are your code on PI-3's with the latest updates.
>>> Very stable on my microwave.
>>> Not relying on the /tmp/rpt_extnodes file  as all are hard coded in the
>> rpt.conf file with the ip address and port number as my nodes are all on
>> the same private sub-net. Below is a example of what is in the rpt.conf
>> file i only pasted the first 3 lines. i commented out 1999 as it is not
>> used. Information for all of my nodes are in the rpt.conf as they all have
>> a differnt port and are behing the same firewall.
>>> 43816 = radio at 127.0.0.1/43816,NONE;1999 = radio at 127.0.0.1/1999,NONE27008
>> = radio at 10.0.1.22:4568/27008, NONE
>>> The nodes think they are connected as allmon2 reports them as connected
>> and if i am not mistaken allmon2 gets its connection information from each
>> node.
>>> this issue is very intermittent and not easily repeated. It occurs
>> anywhere from a few days to a few months, and as it does not show up as an
>> issue on allmon2 it is hard to know when it has occurred.
>>> Thank you again for your help.
>>>
>>>
>>>
>>>        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: Wednesday, June 21, 2017 9:05 AM
>>> Subject: Re: [arm-allstar] Permanent link failing
>>>
>>> Chris,
>>>
>>>    I have not seen this problem here and I run several permanent
>>> connections. Keep in mind that whoever you are connecting to can manually
>>> disconnect a permanent link to them. So if the node you are connecting to
>>> is not yours or it is yours and you are not sure if someone could be
>>> disconnecting from the other end check to see if that might be the case.
>>>
>>> To better understand why this might be happening we would need more info.
>>> Are the links generally reliable or are they constantly
>>> disconnecting/reconnecting? What code version is a BOTH end? Is there any
>>> situation that you can identify when this happens? You can go into the
>>> Asterisk client (ADMIN menu item 11) and view the log to see if
>> reconnects
>>> are taking place.
>>>
>>> Asterisk requires that both ends have knowledge of the other ends IP
>>> address. This is done through the /tmp/rpt_extnodes file. If one end
>> (your
>>> end) had the connection list and the other end did not the connection
>> would
>>> fail and your end would continue to try and reconnect forever until
>> either
>>> you restarted/rebooted or you execute a permanent disconnect. During this
>>> period if you had previously been connected the connection list would
>>> probably still show connected.
>>>
>>>
>>> *73 Doug*
>>>
>>> *WA3DSP*
>>>
>>> *http://www.crompton.com/ hamradio <http://www.crompton.com/ hamradio>*
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Jun 21, 2017 at 11:23 AM, "C B via arm-allstar" <
>>> arm-allstar at hamvoip.org> wrote:
>>>
>>>>
>>>>
>>>> Randomly my Permanent links are acting as if they are notconnected.
>> Almon2
>>>> still shows them as connected however the signals to not passthru.
>>>>
>>>>
>>>> Background on my configuration.
>>>>
>>>>
>>>> There are more than 30 nodes in the system that is connectedon the same
>>>> private sub net, on a vlan on the wide area intranet; this
>> intranetconsists
>>>> mostly of IP microwave.  All nodessit behind a router. There are also
>> nodes
>>>> connected via the public internet.
>>>>
>>>>
>>>> Each node has a unique port number, there is a line in eachnode in the
>>>> prt.conf so that the private ip address and port are known for eachof
>> the
>>>> nosed on the same subnet of the wide area intranet. Thus this is
>> notrelying
>>>> on a hairpin thru the router for connectivity.
>>>>
>>>>
>>>> The nodes Permanent link is set up by having a
>> startup_macro=*73xxxxxxxxin
>>>> the rpt.conf
>>>>
>>>>
>>>> Every so often a node no longer is linked but it still showslinked in
>>>> allmon2.
>>>>
>>>>
>>>> Restarting asterisk resolved this issue.
>>>>
>>>>
>>>> Any idea on what can be done here to make this more reliable?
>>>>
>>>>
>>>> Thank you in advance for any help.
>>>>
>>>>
>>>> Chris
>>>>
>>>> ______________________________ _________________
>>>>
>>>> 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
>> _______________________________________________
>>
>> 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
>

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus