[aprssig] CW stations and ui-view igate

[Andrew Rich]

In fact my igate login is m/100 (100 kms radius)

This lets VK4* and CW* stations in as IGATE Traffic.

VK4*=ALL passes thru fine to RF
CW*=ALL does not pass at all to RF



-----Original Message-----
From: Steve Dimse [mailto:steve at dimse.com]
Sent: Thursday, 16 June 2005 8:44 PM
To: TAPR APRS Mailing List
Subject: Re: [aprssig] CW stations and ui-view igate



On Jun 16, 2005, at 6:24 AM, AE5PL Lists wrote:

> CW stations use an unverified login (see post in other thread  
> describing
> these) which I would guess UI-View recognizes as non-ham and  
> refuses to
> gate them to RF.
>

I do not know specifically about UI-V, but some other IGates will  
pass unverified packets when the call is specifically included in the  
list. Obviously using CW* in this situation would be a disaster, but  
specific local CW stations would not cause excessive QRM. Speaking  
only of US rules, this is not illegal. Under the Automatic message  
forwarding system rules, unless a verification is made, the first  
station to transmit a message on RF assumes responsibility for the  
content of the message. If it is a CW station, the risk to an IGate  
operators license is small, but still real. This is why the default  
behavior of the system is to exclude unverified packets.

So just to fine tune your statement in the previous message, the  
verification does not PREVENT those packets from being IGated to RF,  
but rather allows the IGate operator to decide for him/herself  
whether to assume responsibility for those messages.

Steve K4HG

_______________________________________________
aprssig mailing list
aprssig at lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig