"Do Not Monitor" Calls being decoded on P25 Trunking System about sdrtrunk HOT 3 CLOSED

Some questions:

1. When this happens, are you decoding the control channel and the do not monitor talkgroup is a channel grant, or are you decoding a traffic channel and the do not monitor talkgroup becomes active?

2. The Do Not Monitor alias that you setup, which Talkgroup Alias ID are you using, the talkgroup value (4 characters) or the radio ID (6 characters)?

3. Does the full conversation get played over the mixer/speakers, or does it appear that the audio manager recognizes that the talkgroup is flagged and stops the audio in mid-call?

4. In the 'Events' tab, how does the system classify the event: 'Call' or 'Call-Do Not Monitor'? Does the call event show the talkgroup in either the TO or FROM column, that you identified as a do not monitor talkgroup?

Thanks, Denny

from sdrtrunk.

1. Decoding a traffic channel for a monitored talkgroup and the do not monitor talkgroup becomes active at the tail of the regular group call
2. I am using the talkgroup value for alias id
3. It seems to recognize the talkgroup and stop the audio mid-call
4. In the events log the call shows up as a Group Call, with the talkgroup id showing in the TO column

from sdrtrunk.

I think this issue should be resolved with this commit: ddfefe4

There were several instances where I was starting the audio before the TO/FROM metadata had been dispatched to the AudioManager, causing the audio to start before it had any of the aliases. I reordered the timing so that the AudioManager should get the correct metadata with the start of the call, so that it can better make the 'Do Not Monitor' determination.

Please advise if this issue persists after the next beta release (0.2.0.beta4).

from sdrtrunk.