[arm-allstar] CW ID

[Fredric Moses]

You rang?  Gestapo REF9050/REF9360 owner here :)

Yea on the 9050 main channel with some 40-50 irlp nodes connected and some of those nodes are linked to multi-site repeater systems the other admins/node owners will probably jump little if a node is sending cw to the rest of the network when it’s not needed gets some of those east coasters pissy for sure..

It was the strict IRLP rules have to use this and only this that made us drop most of our IRLP nodes on our Michigan stuff for APP_RPT gear a few years ago now..  I did purchase a micro-node just so i could do testing of the IRLP reflectors from around the house.  With the number of RTCM’s we purchased could not go wrong with his other products.  Echolink is starting to get worse then IRLP though.. $40 per conference ID and now they are hunting for non-standard echo-link nodes.. IE chan_el stuff and banning the nodes if it allows more then one person to connect to the node.. This is for -l and -r nodes…  So when they ban mine will just remove those channel drivers as app_rpt is just fine with us…  Of the 3 echolink reflectors I have ran over the past 13 some years I am only going to keep one *USA* as it’s cross-linked to one of my irlp reflectors, not 9050 but 9369.  I should add allstar, dstar and our dmr cross patch to REF9369 really piss people off..

Gestapo fits with me fine I think… We call our DMR Network MI5 and our ham microwave network MI6WAN :)

--
Fredric Moses - W8FSM - WQOG498
fred at moses.bz

> 
>> On Apr 16, 2015, at 10:04 PM, Doug Crompton <doug at crompton.com <mailto:doug at crompton.com>> wrote:
>> 
>> I guess I did not explain that well. duplex=0 | 1  would ID but only to the local connected radio so no one connected should hear it.  But there are all kinds of ways you can get ID on the Internet side with a repeater by not setting things up properly. Especially when you are using a simplex node into a repeater remotely. In that case the repeater output PL has to follow the input signal. Then you would not generally hear the ID unless the repeater ID'ed over the incoming signal.
>> 
>> I have to a agree though. IRLP is a PITA. Most IRLP reflector gestapo administrators will jump on you for the slightest infraction. That includes the reflector that was mentioned. But that being said you would not want a local ID going out to the connected nodes in any voip system.
>> 
>> So the facts are, you need ID on a local RF node to be legal, it does not go out to the Internet from Allstar, If someone is hearing it you probably have something misconfigured outside of Allstar or it is coming from another node.
>> 
>> I would suggest that you connect to another Allstar node and force your ID - *80 - and see if they hear it. If the IRLP guys would work with you on this then maybe they could test.
>> 
>> On the IRLP/Echolink connect issue. That is their issue not ours. Echolink is a part of the Allstar releases and it is often used incoming to Allstar and it is at times a useful tool.  There are also several IRLP to Allstar gateways that are used daily. The Alaska Morning net is an example. While not explicitly condoned they are tolerated and again useful. Officially they don't want us to connect but unless it is abused I doubt there will be anything done. The reasons I have heard is that echolink thinks we don't check well enough for non-amateur use and IRLP's moto is nothing but radio connections - no computer, phone, etc.  Now you know why Allstar rules!
>> 
>> 73 Doug
>> WA3DSP
>> http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150417/76e749ff/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150417/76e749ff/attachment.pgp>