Site NAC Question

devicelab

Whacker Extraordinaire
Joined
Jul 18, 2016
Messages
1,661
Location
Nowhere in WA
So this isn't really an issue since there's an easy workaround, but I'm just curious why trunk users wouldn't be transmitting a valid NAC from their radios? So in my local Phase 2 trunk about 50% of the time there's a valid NAC received. The other 50% it's just 000h (or no NAC) -- but why? Is this an infrastructure issue in the system? (There's no obvious pattern -- it happens with random users, on all sites, all TGIDs, etc.)

I've confirmed (with my SDS-100) that if I enforce the Site NAC then I won't hear users that are getting a NAC of 000h. Obviously, the only solution is to turn off the enforcement of the Site NAC feature.
 

Attachments

  • nac.jpg
    nac.jpg
    59.5 KB · Views: 22

GTR8000

NY/NJ Database Guy
Database Admin
Joined
Oct 4, 2007
Messages
15,997
Location
BEE00
The repeaters transmit the NAC with every transmission, not the "trunk users". In other words, it has nothing to do with a subscriber keying up, as they would be transmitting on the input anyway, which you're not monitoring. I'm going to go out on a limb and say that this is a Uniden issue, not a system issue. Have you monitored the same site using something else, like software, to confirm the presence or absence of the NAC each time a repeater keys up? That's probably where I would start if I were trying to figure out why my scanner isn't accurately representing what the system is actually broadcasting.
 

KevinC

The big K
Super Moderator
Joined
Jan 7, 2001
Messages
12,462
Location
1 point
The site NAC on a P2 VC feature is broken, it has never functioned properly. FDMA on the other hand works just fine.
 

GTR8000

NY/NJ Database Guy
Database Admin
Joined
Oct 4, 2007
Messages
15,997
Location
BEE00
The site NAC on a P2 VC feature is broken, it has never functioned properly. FDMA on the other hand works just fine.
Oh yeah, that too. So many bugs, so little time. 3 years...help me help you! 🤡
 

GTR8000

NY/NJ Database Guy
Database Admin
Joined
Oct 4, 2007
Messages
15,997
Location
BEE00
The site NAC on a P2 VC feature is broken, it has never functioned properly. FDMA on the other hand works just fine.
Err wait, don't you mean P25P2 color codes? 😵😆
 

devicelab

Whacker Extraordinaire
Joined
Jul 18, 2016
Messages
1,661
Location
Nowhere in WA
Have you monitored the same site using something else, like software, to confirm the presence or absence of the NAC each time a repeater keys up?
Yes but since DSD+ has changed recently it's a lot harder to read the output data than ever before. I went ahead and used the combined VC/CC monitor using FMPA and managed to capture output from a TGID that the SDS-200 said was using NAC 000h.

It looks like the system is using the proper NAC, or am I reading this output wrong? (See the last line...)


Code:
2023.12.19  0:36:00  Sync:+P25p2 MAC_ACTIVE    Group Voice Channel User                   Slot#1 PRI4 TG=1183 RID=12923
2023.12.19  0:36:00              [F0S1-4V]]
2023.12.19  0:36:00              (F1S2-4V)
2023.12.19  0:36:00              [F2S1-2V]  e:1
2023.12.19  0:36:00              (F3S2-4V)
2023.12.19  0:36:00              MAC_ACTIVE    Group Voice Channel User                   Slot#1 PRI4 TG=1183 RID=12923
2023.12.19  0:36:00              (F5S2-4V)
2023.12.19  0:36:00              MAC_HANGTIME  Group Voice Channel Grant Update           [TG=1821 ch=851.6375-2] [TG=3771 ch=853.775-2]
2023.12.19  0:36:00              (F7S2-4V)
2023.12.19  0:36:00              MAC_HANGTIME  Adjacent Status Broadcast                  SysID=3AB LRA=0 RFSS=1 Site=26 CC=854.6375 SC=70 CFVA=3: Networked
2023.12.19  0:36:00              (F9S2-2V)     ES: MI:000000000000000000  KID: 0000 (0)  AlgID: 80 - CLEAR
2023.12.19  0:36:00              MAC_ACTIVE    Group Voice Channel Grant Update           [TG=207 ch=851.6375-1]
2023.12.19  0:36:00              MAC_HANGTIME  Group Voice Channel User                   Slot#1 PRI4 TG=1183 RID=0
2023.12.19  0:36:00              MAC_HANGTIME  Group Voice Channel Grant Update           [TG=2327 ch=852.1625-1] [TG=3771 ch=853.775-2]
2023.12.19  0:36:00              (F1S2-4V)
2023.12.19  0:36:00              MAC_HANGTIME  Adjacent Status Broadcast                  SysID=3AB LRA=0 RFSS=1 Site=34 CC=860.9625 SC=70 CFVA=3: Networked
2023.12.19  0:36:00              (F3S2-4V)
2023.12.19  0:36:00              MAC_HANGTIME  Adjacent Status Broadcast                  SysID=3AB LRA=0 RFSS=1 Site=31 CC=858.7125 SC=70 CFVA=3: Networked
2023.12.19  0:36:00              (F5S2-4V)
2023.12.19  0:36:00              MAC_HANGTIME  Adjacent Status Broadcast                  SysID=3AB LRA=0 RFSS=1 Site=29 CC=858.7125 SC=70 CFVA=3: Networked
2023.12.19  0:36:01              (F7S2-4V)
2023.12.19  0:36:01              MAC_HANGTIME  Adjacent Status Broadcast                  SysID=3AB LRA=0 RFSS=1 Site=28 CC=851.4625 SC=70 CFVA=3: Networked
2023.12.19  0:36:01              (F9S2-2V)     ES: MI:000000000000000000  KID: 0000 (0)  AlgID: 80 - CLEAR
2023.12.19  0:36:01              MAC_ACTIVE    Group Voice Channel User                   Slot#2 PRI4 TG=3771 RID=0
2023.12.19  0:36:01              MAC_HANGTIME  Group Voice Channel User                   Slot#1 PRI4 TG=1183 RID=0
2023.12.19  0:36:01              MAC_HANGTIME  Group Voice Channel Grant Update           [TG=207 ch=851.6375-1] [TG=3771 ch=853.775-2]
2023.12.19  0:36:01              (F1S2-4V)
2023.12.19  0:36:01              Bad Frame Data
2023.12.19  0:36:01              (F3S2-4V)
2023.12.19  0:36:01              MAC_HANGTIME  Group Voice Channel Grant Update           [TG=3771 ch=853.775-2]
2023.12.19  0:36:01              (F5S2-4V)
2023.12.19  0:36:01              MAC_HANGTIME  Group Voice Channel Grant Update           [TG=3771 ch=853.775-2]
2023.12.19  0:36:01              (F7S2-4V)
2023.12.19  0:36:01              MAC_HANGTIME  Adjacent Status Broadcast                  SysID=3AB LRA=0 RFSS=1 Site=32 CC=858.2375 SC=70 CFVA=3: Networked
2023.12.19  0:36:01              (F9S2-2V)     ES: MI:000000000000000000  KID: 0000 (0)  AlgID: 80 - CLEAR
2023.12.19  0:36:01              MAC_ACTIVE    Group Voice Channel User                   Slot#2 PRI4 TG=3771 RID=64772
2023.12.19  0:36:01              MAC_HANGTIME  Group Voice Channel User                   Slot#1 PRI4 TG=1183 RID=0
2023.12.19  0:36:01              MAC_HANGTIME  Group Voice Channel Grant Update           [TG=3771 ch=853.775-2] [TG=207 ch=851.6375-1]
2023.12.19  0:36:01              (F1S2-4V)
2023.12.19  0:36:01              MAC_HANGTIME  Group Voice Channel Grant Update           [TG=3771 ch=853.775-2]
2023.12.19  0:36:01              (F3S2-4V)
2023.12.19  0:36:01              MAC_HANGTIME  Adjacent Status Broadcast                  SysID=3AB LRA=0 RFSS=1 Site=33 CC=860.7125 SC=70 CFVA=3: Networked
2023.12.19  0:36:01              (F5S2-4V)
2023.12.19  0:36:01              MAC_HANGTIME  Adjacent Status Broadcast                  SysID=3AB LRA=0 RFSS=1 Site=30 CC=859.4625 SC=70 CFVA=3: Networked
2023.12.19  0:36:01              (F7S2-4V)
2023.12.19  0:36:01              MAC_HANGTIME  Adjacent Status Broadcast                  SysID=3AB LRA=0 RFSS=1 Site=27 CC=854.4875 SC=70 CFVA=3: Networked
2023.12.19  0:36:01              (F9S2-2V)     ES: MI:000000000000000000  KID: 0000 (0)  AlgID: 80 - CLEAR
2023.12.19  0:36:01              MAC_ACTIVE    Group Voice Channel User                   Slot#2 PRI4 TG=3771 RID=64772
2023.12.19  0:36:01              MAC_END_PTT   DCC=3A5 Tgt=1183 Src=16777215
 

dave3825

* * * * * * * * * * * *
Premium Subscriber
Joined
Feb 17, 2003
Messages
8,592
Location
Suffolk County NY
since DSD+ has changed recently it's a lot harder to read the output data than ever before.
DSDPlus help said;
DSD+ 2.448

Logging options:
>file Create log file
>>file Append to log file
-t Time stamp console log file entries
-T Time stamp console log file entries and console screen data
-E Add frequency/NAC/RAN/DCC/RAS data to event log file entries
-F<num> Filename modifier; use to avoid filename collisions [F0]

DSDPlus help said;
DSD+ 2.345

Added Console Log Verbosity Level setting to Misc menu.

Enable logging and set it to highest level.
 
Top