[Allstar Digital] hb_ambe_audio

Tue Apr 25 14:32:40 EDT 2017

Short answer, no. But, DMRlink conference bridge and I think HBlink 
conference bridge do reduce the keyups going out on the target network. 
Conference bridge supports User Activated TGs. BUT, the connection is 
not made until the carrier drops. So, the keyup never goes out the 
network. The next transmission is bridged.

Steve

On 4/25/2017 2:26 PM, Neil k8it wrote:
> thanks for that explaination.
> would this approach offer some methods to resolbe the constant keyups 
> from stations trying to connect to a tg?
> could the audio vbe delayed just enough to detect balid audio from a 
> local station, while masking just keyups.
> since this approach offers more sysop control, maybe the connect 
> requests/ disconects can handled via another ip port etc...
> Thanks
> 73 Neil Sablatzky  K8IT
> Allstar Node 41838 KITLINK
> Allstar Node 42087 KITLINK HUB
> IRLP Node exp0068
> Echolink K8IT-L
> WIRES-X K8IT 11479 Room 21479
>
> *From:* Steve Zingman <mailto:szingman at msgstor.com>
> *Sent:* Tuesday, April 25, 2017 1:13 PM
> *To:* Digital linking using Asterisk and app_rpt 
> <mailto:allstar-digital at lists.keekles.org>
> *Subject:* Re: [Allstar Digital] hb_ambe_audio
>
> hb_ambe_audio does the same job for HBlink as ambe_audio does for DMRlink.
>
> The advantage of using HBlink instead of DMRlink with BrandMeister is 
> that with DMRlink / BM you need a BM admin to setup a static TS/TG 
> path for a specific Radio ID. With HBlink / BM you can define the 
> TS/TG and Radio ID yourself.
>
> Think of it this way, DMRlink looks to BM as a SmartPTT connection and 
> requires BM admin intervention. HBlink looks to BM as a MMDVM 
> connection and requires no BM admin intervention (other then making 
> you a sysop of that radio ID.
>
> 73, Steve N4IRS
>
> On 4/25/2017 12:46 PM, Neil k8it wrote:
>> can someone please explain what this
>> hv-ambe-audio is about.
>> what hardware is it using
>> wwhat is the purpose of using it
>> etc...
>> Thanks
>> 73 Neil Sablatzky  K8IT
>> Allstar Node 41838 KITLINK
>> Allstar Node 42087 KITLINK HUB
>> IRLP Node exp0068
>> Echolink K8IT-L
>> WIRES-X K8IT 11479 Room 21479
>>
>> *From:* Mike Zingman <mailto:mike.zingman at gmail.com>
>> *Sent:* Tuesday, April 25, 2017 8:39 AM
>> *To:* Digital linking using Asterisk and app_rpt 
>> <mailto:allstar-digital at lists.keekles.org>
>> *Subject:* Re: [Allstar Digital] hb_ambe_audio
>>
>> BTW, had some great QSOs yesterday in "dongle mode", which is using 
>> hb_ambe_audio + DMRGateway + mic/speaker.  Worked great.
>>
>>
>> On Sun, Apr 23, 2017 at 12:45 PM, Steve Zingman <szingman at msgstor.com 
>> <mailto:szingman at msgstor.com>> wrote:
>>
>>     Mike and I are beta testing ambe_audio and DMRGateway for HBlink.
>>     So far so good. The issues with fluttering analog signals and
>>     fast keyups has been addressed.
>>     This should resolve the issue of the outbound DMR signal lagging
>>     behind the analog signal more then a short normal display.
>>
>>     This is BETA testing. It is not ready to be released. I am
>>     connecting to a number of high activity ASL hubs to test
>>     operation. Right one I have it in receive ONLY so we have one way
>>     ASL ---> DMR. I am testing on BM The DMR ID is 1311222 and the TG
>>     311222. The ASL node connected is 2135. Let's see how this goes.
>>
>>     One advantage to hb_audio is that there is no longer a need to
>>     involve BM sysadmins to setup static routing for your connection
>>     to BM.
>>     hb_ambe_audio also supports smaller local networks of MMDVM based
>>     devices without the need for a BM server or a c-Bridge.
>>
>>     hb_ambe_audio and hb_parrot provides us insight into connecting
>>     other devices to a HBlink network.
>>
>>     for DVSwitch, 73 Steve N4IRS
>>
>>     -- 
>>     ---
>>     "Real programmers use vi, that's why I use nano."
>>
>>     _______________________________________________
>>     Allstar-Digital mailing list
>>     Allstar-Digital at lists.keekles.org
>>     <mailto:Allstar-Digital at lists.keekles.org>
>>     http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>     <http://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
>> ------------------------------------------------------------------------
>>
>> No virus found in this message.
>> Checked by AVG - www.avg.com <http://www.avg.com/email-signature>
>> Version: 2016.0.8013 / Virus Database: 4776/14382 - Release Date: 
>> 04/25/17
>>
>>
>>
>> _______________________________________________
>> Allstar-Digital mailing list
>> Allstar-Digital at lists.keekles.org
>> http://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
>
> ------------------------------------------------------------------------
>
> No virus found in this message.
> Checked by AVG - www.avg.com <http://www.avg.com/email-signature>
> Version: 2016.0.8013 / Virus Database: 4776/14382 - Release Date: 04/25/17
>
>
>
> _______________________________________________
> 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/20170425/13b54bcc/attachment.html>