Denny et al..Great job as a start. Couple of issues:1) What's the deal with using XVPN for access to radioreference ? My firewall policy doesn't like this. Not sure why it would be needed. Currently blocking API calls to radioreference.
2) On large P25 system lookups in Radio Reference, sometimes the buffers in TG View / Categories don't clear... need to go to a small P25 system to clear out the buffers and then go back to the large system to reload the TG Categories. This could be because SDRT hasn't processed the P25 system initially from RR?
3) Being able to import the v4 TG data should be separate app, but a needed one! A lot of work in those v3-4 configs. Would be a nice feature in the Playlist editor.
4) After spending hours reconfiguring TGs... I was wondering why channels could not be configured to blocking by default, with the alias list acting as an inclusion list. On large P25 systems, with hundreds of agencies, spending hours to add TGs to only disable them to "block" them just doesn't work. On simple systems... it's not a big deal. On statewide and regional systems... it's a nightmare. With the addition of the RR features to enable TGs, I would think it would be easier for users to only add TGs of interest and expect only those TGs for traffic. Having to manually block thousands of TGs is a major pain.
5) I do like the System View Create Channels feature.... nice and easy Channel creation from RR!
6) Really miss the multi TG editing features of v3-4. I like the new layout... I got used to it. But editing single TGs one at a time is ugly to simply set priorities, color, icon, save... etc.
7) Need a find "TG" feature. Was trying to track down if I was blocking TGs in my numerous block lists, but can't search for TG ID in Alias or Identifier tabs (although Identifier lists the TG IDs).
Ron, thanks for the feedback. Responses below ...
On Tuesday, June 9, 2020 at 5:59:13 PM UTC-4, Ron Benoit wrote:Denny et al..Great job as a start. Couple of issues:1) What's the deal with using XVPN for access to radioreference ? My firewall policy doesn't like this. Not sure why it would be needed. Currently blocking API calls to radioreference.I use straight HTTP Port 80 connections for the radio reference database API and HTTPS SSL Port 443 connections to the broadcastify calls API. Not sure what would be using XVPN.
2) On large P25 system lookups in Radio Reference, sometimes the buffers in TG View / Categories don't clear... need to go to a small P25 system to clear out the buffers and then go back to the large system to reload the TG Categories. This could be because SDRT hasn't processed the P25 system initially from RR?I think I need to lock the system selection combo box until the data is fully downloaded from radio reference. It sounds like (as you suspect) that aditional results from a previous system selection might still be arriving and contaminating the list and combo box.
3) Being able to import the v4 TG data should be separate app, but a needed one! A lot of work in those v3-4 configs. Would be a nice feature in the Playlist editor.You should be able to 'Add' these V3 and V4 playlists in the Playlists tab to the list of usable playlists. ONce there, click the Select button to use them. If not, please let me know what, if any, errors are preventing this?
4) After spending hours reconfiguring TGs... I was wondering why channels could not be configured to blocking by default, with the alias list acting as an inclusion list. On large P25 systems, with hundreds of agencies, spending hours to add TGs to only disable them to "block" them just doesn't work. On simple systems... it's not a big deal. On statewide and regional systems... it's a nightmare. With the addition of the RR features to enable TGs, I would think it would be easier for users to only add TGs of interest and expect only those TGs for traffic. Having to manually block thousands of TGs is a major pain.You can accomplish this by creating a single blacklist alias with a talkgroup range of 1 to 65535. The additional talkgroups that you alias (not blocked) shouldn't interfere. When looking up an alias for a talkgroup, it matches discrete talkgroup values first, and then talkgroup ranges.
5) I do like the System View Create Channels feature.... nice and easy Channel creation from RR!Good.6) Really miss the multi TG editing features of v3-4. I like the new layout... I got used to it. But editing single TGs one at a time is ugly to simply set priorities, color, icon, save... etc.That's been added. It will be in the next release.
7) Need a find "TG" feature. Was trying to track down if I was blocking TGs in my numerous block lists, but can't search for TG ID in Alias or Identifier tabs (although Identifier lists the TG IDs).Would adding a simple search box to the Alias Identifiers tab meet this need? You could type the talkgroup value and/or protocol and it would filter the list.
Also, 2nd a motion to be able to change Channel settings between P25 I and II systems... many seem to state they are Type 2 (in RR) when they are actually still Type 1... and you have to delete and manually re-add to correct the problem.
Couple of things from the packet captures:a) Seems like RR maybe called when the Configuration window is not open... on startup? Any reason why?b) There seems to be some connection flow issues... I don't think sessions are terminating or timing out soon enough when actions are taken by the stupid user (me) in the user interface (moving around rapidly... I'm impatient). I think it wise to terminate each connection when user actions are performed or block those user interactions with a modal progress bar dialog that has an abort option (which seems more appropriate and easier to manage... or maybe not).c) In some cases I get an error dialog from SDRT that it can't connect to RR. But the dialog is not modal or top level, so it was behind other windows and late to appear (no audio alarm either I beleive). This only occurs when I get the Java IO exceptions.