Kip AE5IB wrote...
The UI-View system is AE5IB-13
So in the ALIAS is it AE5IB, or AE5IB-13?
If you are using AE5IB-13 in the station setup, I would use the same SSID in the SUBST_ALIAS setting. Having your callsign in the alias list will allow you can digipeat when someone uses your actual callsign in the path. If you had an alias of AE5IB-13, you would digipeat a beacon if the first un-used path was AE5IB-13. This might be useful sometimes for selective digipeating. For most mobile stations, they would be better off starting their path with WIDE1-1.
Same question with the SUBST_ALIAS is it
AE5IB, or AE5IB-13?
By entering your callsign in the Aliase(s) section, your station will disigipeat on the station callsign. No one will be using a path of AE5IB-13 unless they have specifically entered it. It won't hurt anything if you enter it and no one uses it. However, adding WIDE1-1 will digipeat if the beacon heard has a path that starts off with an un-used WIDE1-1, in other words you would be acting as a fill-in digi.
If Alias Substitution is checked, beacons digipeated by your station will have the alias entered in SUBST_ALIAS embedded in the digipeated beacon, making it traceable, showing that it was digipeated by you.
Out of the box, UI-View was set up for an untraceable WIDEn-N and a traceable TRACEn-N. The changes I suggested for the the [DIGI_OPTIONS] section set UI-View up so the user can enable or disable a traceable WIDEn-N and help with state or province flooding... e.g. TXn-N for Texas. The old TRACEn-N has been deprecated.
For someone wanting to do "state flooding", it would be good if they used a path starting with WIDE1-1... e.g. WIDE1-1,WIDE7-7. This will make the first hop traceable. It would be an 8 hop path. Someone would only use it if they had something urgent that they needed to spread such as an emergency bulletin. Of course, a path including TXn-N won't go anywhere unless there are digipeaters in the area supporting it.
--
73 Keith VE7GDH
"I may be lost, but I know exactly where I am!"
