[aprssig] on a multi-TNC digipeater, which callsign should be traced?

[Kenneth Finnegan]

I can't tell you off hand what aprx does, but if you were to ask me, I'd
say I'd want it to use the outgoing TX callsign, since I made the argument
in my thesis that the last traced callsign may be used as part 97
identification. If I ever notice it doing something else, I would put it on
my list to fix it in aprx.

To give you an unopinionated answer, the specs say nothing on the issue.

Kenneth Finnegan
Maintainer, aprx
On Oct 11, 2015 10:42 AM, "Tom Hayward via aprssig" <aprssig at tapr.org>
wrote:

> I don't know the answer, but you might study what aprx does and implement
> it similarly.
>
> Tom KD7LXL
> On Oct 11, 2015 9:11 AM, "Andrew P. via aprssig" <aprssig at tapr.org> wrote:
>
>> I was just looking at the digipeat tracing code in my APRS program
>> (YAAC), and started wondering which callsign should be used for tracing
>> when doing a cross-band digipeat. For example, if the frame was received on
>> the port with callsign AP0RT-1 and digipeated out both TNC's AP0RT-1 and
>> AP0RT-2, which callsign should be used for the trace on the transmission
>> out AP0RT-2? The receiving port (AP0RT-1)? The transmitting port (AP0RT-2)?
>> Or both in receive-transmit order?
>> Just curious what the behavior should be for this.
>>
>> Andrew, KA2DDO
>> author of YAAC
>>
>> _______________________________________________
>> aprssig mailing list
>> aprssig at tapr.org
>> http://www.tapr.org/mailman/listinfo/aprssig
>>
>>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20151011/d34e0e07/attachment.html>