I guess you can discount the last two posts (and this one) because I seem to have cleared up the issue, but I have no idea why it works like it does.
With the scan option in Scan List mode, and Secondary Priority set to NONE, I am not hearing the replies from the dispatcher (over ISSI) to native (on-system) calls. Consistently. Callers from the system (i.e. two portable radios, a portable and mobile, etc) work fine. It is NEVER the native call that is missed, it is ALWAYS the dispatch call. If the dispatcher speaks long enough that the hang-time of the scan ends and the radio resumes scanning, it will immediately pick up the dispatcher's conversation (late entry) and play it.
If I change Secondary Priority to Operator Select, the dispatcher's comms come in like normal, like all these radios did with fw 2.50. That's the part I don't understand.
I had someone suggest to me that when set to NONE, the radio is possibly checking priority (or not) and misses the dispatcher's continuation message, but I'm not sure how much I buy that idea because I would think it would happen much more intermittently and it wouldn't always be the dispatcher that was missed.
So long as it's working now, I guess we can chalk it up to gremlins or voodoo magic or something.
With the scan option in Scan List mode, and Secondary Priority set to NONE, I am not hearing the replies from the dispatcher (over ISSI) to native (on-system) calls. Consistently. Callers from the system (i.e. two portable radios, a portable and mobile, etc) work fine. It is NEVER the native call that is missed, it is ALWAYS the dispatch call. If the dispatcher speaks long enough that the hang-time of the scan ends and the radio resumes scanning, it will immediately pick up the dispatcher's conversation (late entry) and play it.
If I change Secondary Priority to Operator Select, the dispatcher's comms come in like normal, like all these radios did with fw 2.50. That's the part I don't understand.
I had someone suggest to me that when set to NONE, the radio is possibly checking priority (or not) and misses the dispatcher's continuation message, but I'm not sure how much I buy that idea because I would think it would happen much more intermittently and it wouldn't always be the dispatcher that was missed.
So long as it's working now, I guess we can chalk it up to gremlins or voodoo magic or something.