[Allstar Digital] DMRGateway failure

Thu Apr 6 11:56:20 EDT 2017

Hello Steve, I haven't installed DMRGateway yet. You guys move too fast for
me. Should I try and install to test it or hold off.

David

On Thu, Apr 6, 2017 at 6:03 AM, Steve Zingman <szingman at msgstor.com> wrote:

> OK,
> So Mike and I had a QSO from ASL <---> DMR Working in both directions
> without errors. This is on the current version of DMRlink and updated
> ambe_audio. This is on a c-Bridge. We are connected from the c-Bridge to BM
> on TS2 TG 3167.
> I'm going to do some looking at logs. After that I'm going to move to a BM
> Master. That will be the ONLY change I'll make. If that works, The next
> step will be to add a second DMRLink connection to BM. Time will tell.
>
> Steve
>
> On 4/6/2017 8:48 AM, Robert Newberry wrote:
>
> I didn't mind drawing a picture it was in my mind the easiest way to show
> my network...haha.
>
> N1XBM
> Apparare Scientor
> Paratus Communicare
> Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657
> www.radioguysrepeaternetwork.com
>
> On Apr 6, 2017 8:41 AM, "Steve Zingman" <szingman at msgstor.com> wrote:
>
>> How do you think we feel, trying to understand you network before I can
>> even begin to troubleshoot.
>>
>> On 4/6/2017 8:39 AM, Robert Newberry wrote:
>>
>> Wow, Steve and Mike I sure appreciate  (and others I assume) your
>> efforts. I was surely confused. It took me two days to fully wrap my arms
>> around the issue to be able to formulate a semi coherent question and even
>> then I still had to draw a picture!
>>
>> N1XBM
>> Apparare Scientor
>> Paratus Communicare
>> Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657
>> www.radioguysrepeaternetwork.com
>>
>> On Apr 6, 2017 8:30 AM, "Steve Zingman" <szingman at msgstor.com> wrote:
>>
>>> We thing we are seeing the same issue with other DMRlink installs. As of
>>> right now, I don't know for sure where the bug is. I have my suspensions.
>>> We have moved testing from BM to a c-Bridge. The testing is with the
>>> current version of DMRlink and ambe_audio.
>>> I do not think it's in ambe_audio since I'm seeing some of the same
>>> symptoms on DMRlink without ambe_audio. Since it APPEARS the bug is
>>> happening to existing "older" installs as well as the current version, I do
>>> not think the bug is in DMRlink.
>>> Once we complete testing on c-Bridge, I'll move back to BM with the
>>> exact same configuration and see what we get. Software is fun!
>>>
>>> 73, Steve N4IRS
>>>
>>> On 4/5/2017 3:50 PM, Robert Newberry wrote:
>>>
>>> Steve,
>>>
>>> I'm not sure it will help, but I made a picture in PDF and e-mailed it
>>> direct to you.
>>>
>>> On Wed, Apr 5, 2017 at 3:30 PM, Steve Zingman <szingman at msgstor.com>
>>> wrote:
>>>
>>>> OK, So,
>>>> 2 Masters, 1 Peer.
>>>> Peer connected to BM?
>>>> Repeater1 connected to Master1?
>>>> Repeater2 connected to Master2?
>>>> "2 masters then each repeater is peered to one master." ????
>>>>
>>>>
>>>>
>>>>
>>>> On 4/5/2017 3:24 PM, Robert Newberry wrote:
>>>>
>>>> -No Actually 2 masters then each repeater is peered to one master. I
>>>> had to do this because of NAT hairpining. I then have the Masters talking
>>>> to each others to have both repeaters "linked"
>>>>
>>>> -Yes I am Peered to BM.
>>>>
>>>> - Yes my repeaters each have their own Masters withing DMRlink.
>>>>
>>>> -No AMBE_AUDIO is peered directly to BM.
>>>>
>>>> On Wed, Apr 5, 2017 at 3:13 PM, Steve Zingman <szingman at msgstor.com>
>>>> wrote:
>>>>
>>>>> I know you are running a bridge. Can I assume 1 Master and 1 Peer?
>>>>> The Peer is connected to BM?
>>>>> Your Repeaters connect to the Master?
>>>>> The dmrlink / ambe_audio is connected to the Master?
>>>>>
>>>>> On 4/5/2017 2:18 PM, Robert Newberry wrote:
>>>>>
>>>>> I've encountered a strange problem on my existing system that has been
>>>>> working for over a year without problem. I have not recently updated the
>>>>> software nor have I made any changes. The day I noticed it stopped working
>>>>> correctly I probably haven't even logged into it for weeks. I did all of
>>>>> the simple stuff like rebooting/ removing power to repeaters, routers,
>>>>> RPI's still hasn't fixed the problem.
>>>>>
>>>>> Here is the problem.
>>>>>
>>>>> -When I TX on my local DMR repeater it is heard on BM by my test
>>>>> subject on an open spot, but the audio is not being heard on Allstar
>>>>> -When I TX on Allstar it goes up to BM and is heard by my test subject
>>>>> on his open spot, but the audio does not repeat on  my local DMR repeater.
>>>>> -When my test subject TX's on his open spot I hear it on Allstar and
>>>>> DMR.
>>>>>
>>>>> This never used to work this way, If I TX'd on my DMR repeater it was
>>>>> heard on Allstar, and in the opposite if I TX'd on Allstar it would be
>>>>> heard on my DMR repeater locally.
>>>>>
>>>>> I hope that I formulated my question in a way that makes sense. I am
>>>>> unsure how to trouble shoot this because it appears that DMRGateway works
>>>>> in both directions...sort of.
>>>>>
>>>>> Does anyone have any suggestions on how I should start troubleshooting
>>>>> this?
>>>>>
>>>>>
>>>>> --
>>>>> N1XBM
>>>>> Apparare Scientor
>>>>> Paratus Communicare
>>>>> Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657
>>>>> www.radioguysrepeaternetwork.com
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Allstar-Digital mailing listAllstar-Digital at lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>>>>
>>>>> _______________________________________________ Allstar-Digital
>>>>> mailing list Allstar-Digital at lists.keekles.org
>>>>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>>>
>>>> --
>>>> N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086,
>>>> 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
>>>>
>>>> _______________________________________________
>>>> Allstar-Digital mailing listAllstar-Digital at lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>>>
>>>> _______________________________________________ Allstar-Digital
>>>> mailing list Allstar-Digital at lists.keekles.org
>>>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>>
>>> --
>>> N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540,
>>> 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
>>>
>>> _______________________________________________
>>> Allstar-Digital mailing listAllstar-Digital at lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>>
>>> _______________________________________________ Allstar-Digital mailing
>>> list Allstar-Digital at lists.keekles.org http://lists.keekles.org/cgi-b
>>> in/mailman/listinfo/allstar-digital
>>
>> _______________________________________________
>> Allstar-Digital mailing listAllstar-Digital at lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>
>> _______________________________________________ Allstar-Digital mailing
>> list Allstar-Digital at lists.keekles.org http://lists.keekles.org/cgi-b
>> in/mailman/listinfo/allstar-digital
>
> _______________________________________________
> Allstar-Digital mailing listAllstar-Digital at lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>
>
> _______________________________________________
> Allstar-Digital mailing list
> Allstar-Digital at lists.keekles.org
> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/allstar-digital/attachments/20170406/ab9bd605/attachment.html>