WSP (9CC) and JIWN (715)

[batdude]

again, this is just an observation because it caught my eye - I did a quick search in the WA forum and didn't see a post that made this connection so I figured I would post it in a new thread.

I am a bit familiar with the JIWN (although I still use the old term IJWN...LOL) - from some of my DC trips.

here is a quick DSD+ dump from the WSP King County Simulcast site (2.1)

///////////

2021/02/24 01:26:09 Current site: 2.1
2021/02/24 01:26:09 Current network: BEE00.9CC Washington State Patrol
2021/02/24 01:26:09 Patch Supergroup: TG=59208 [ (TDMA)]
2021/02/24 01:26:09 Patch Subgroup: TG=59209
2021/02/24 01:26:10 Current site: BEE00.9CC-2.1
2021/02/24 01:26:11 Patch Supergroup: TG=59208 [ (TDMA)]
2021/02/24 01:26:11 Patch Subgroup: TG=59209
2021/02/24 01:26:11 BEE00.9CC-2.1 neighbor: Site BEE0A.715-1.52; CC=0-2607 168.58750
2021/02/24 01:26:12 BEE00.9CC-2.1 neighbor: Site BEE0A.715-1.64; CC=0-2849 171.61250
2021/02/24 01:26:12 BEE00.9CC-2.1 neighbor: Site BEE00.9CC-2.3; CC=1-1928 774.05625
2021/02/24 01:26:13 BEE00.9CC-2.1 neighbor: Site BEE00.9CC-2.2; CC=1-1768 773.05625
2021/02/24 01:26:14 BEE00.9CC-2.1 neighbor: Site BEE00.9CC-2.5; CC=1-1772 773.08125
2021/02/24 01:26:14 BEE00.9CC-2.1 neighbor: Site BEE0A.715-1.6; CC=0-2503 167.28750
2021/02/24 01:26:15 BEE00.9CC-2.1 neighbor: Site BEE0A.715-1.7; CC=0-2535 167.68750
2021/02/24 01:26:17 BEE00.9CC-2.1 neighbor: Site BEE0A.715-1.9; CC=0-2633 168.91250
2021/02/24 01:26:19 BEE00.9CC-2.1 neighbor: Site BEE00.9CC-2.4; CC=1-1766 773.04375
2021/02/24 01:26:23 BEE00.9CC-2.1 neighbor: Site BEE0A.715-1.8; CC=0-2529 167.61250
2021/02/24 01:26:24 BEE00.9CC-2.1 neighbor: Site BEE0A.715-1.17; CC=0-2815 171.18750

///////////////

two things --- I was very surprised to see JIWN sites tied to a state system. This has to be one of a just a few systems that are supporting this type of interoperability (we did see this briefly in Tampa with the new 700/800 P25 system they put on the air, but the linked site (which was VHF) has since been turned off)

the second thing that caught my eye was the call out of JIWN sites that are not in the RR dB - like 1.6, 1.7, 1.8 and 1.9. ALTHOUGH -- break / break -- 167.2875 reported by the controller as "site 1.6" is active - but it's active for site 1.75 -- most odd. same goes for 167.6875 -- it's active, but it's reporting Site 1.76.... perhaps the system controller was never updated with the right info... don't know ....(?)

I would say the chances are VERY good that if the sites are being reported by the controller that they are indeed active and on-the-air - however, per the above, this may be a system setup/programming error in the infrastructure... don't know.

As usual, just an observation.


doug

 

[devicelab]

I was very surprised to see JIWN sites tied to a state system.

The new 9CC system was initially part of IWN and then the FBI figured out how bad (or poorly managed the IWN network has been over the years) and required major security upgrades (if I remember the docs correctly.) They upgraded the IWN controllers in Yakima and then split the two systems off again; however, there is still some limited WSP patching done on a per unit basis. The patched TGIDs are random.

The 9CC system has had some interopability issues over the last couple of years.

the second thing that caught my eye was the call out of JIWN sites that are not in the RR dB - like 1.6, 1.7, 1.8 and 1.9. ALTHOUGH -- break / break -- 167.2875 reported by the controller as "site 1.6" is active - but it's active for site 1.75 -- most odd. same goes for 167.6875 -- it's active, but it's reporting Site 1.76.... perhaps the system controller was never updated with the right info... don't know ....(?)

Most of the IWN sites locally have had their site IDs moved higher for whatever reason. This started I think about a year ago, IIRC. As you noted they were updated in the database.