I’m running ASL3.13-1 while monitoring the PAPA System in Southern California. I’ve noticed that users which come in from the PAPA System over RF adhere to the unkeywait time that I have configured in rpt.conf before the CT is sent, but users that come in from nodes connected to that system over AllStar Link (e.g. ClearNodes) have a much shorter wait time before CT is sent…almost immediately. I have telemwait and unkeywait configured identically (value = 2000). Is there another knob somewhere that I need to change in order to make these wait times identical?
unkeywait in the wait-times stanza should be the adjustment for all CTs regardless of the traffic source. I've never noticed any sources not following what I have set for unkeywait.
Keep in mind you're also at the mercy of everyone upstream's configuration for hangtimes, tail closes, etc. You can only control your local node's time between when it pereceives an unkey and when it takes action. Any variances upstream you just have to live with.
Mason - Thanks for confirming how I thought that should be working - I've got unkeywait set to 2000 (2 seconds), so that should be the earliest that I hear the CT. The system I'm listening to has some nets where they do check-ins by how folks are connecting to the system, so it’s easy to get a bunch of AllStar-connected transmissions and hear this. I’ll see if I can find some debugging to turn on to see if I can glean anything.
N8EI - Agreed, but at least in theory, those should be additive to the 2 seconds that I have configured in unkeywait locally?