No. This has absolutely nothing to do with school
okay, if you say so. This has been in the planning stages for quite some time now. Engineering meetings go back a year+No. This has absolutely nothing to do with school safety.
No. This has absolutely nothing to do with school
okay, if you say so. This has been in the planning stages for quite some time now. Engineering meetings go back a year+No. This has absolutely nothing to do with school safety.
as of now you are correctThe data stream is identical on all towers on a simulcast system. It can't be different or it would cause reception errors.
From what I have heard, third hand and unconfirmed, ESB may be only active site.
Yes the CC has stayed the same since Aug. 1st. The CC's on the NYCICN system haven't changed for at least a year, so it's not unusual it seems.TV 16 has been rolling in frequently as of late. I have watched numerous times, however not continuously. I have not seen the 483.xxx CC roll. Has anyone?
View attachment 168302
Submissions should be based on confirmed information, not speculation.Regarding this system:
New York City Police Department (NYPD) Trunking System, New York City, New York
It appears that their TGID Scheme is rather simple and follows this channel layout almost to a T
CW1=301
SI CW1=302
CW2=303
...
Man 1/5/7=101
Man 6/9=102
...
Brx 40/41=110
Brx 42/44=111
...
Bkyn 60/61=116
Bkyn 62/68=117
...
Qns 100/101=127
Qns 102/106=128
etc.
Is this something worth submitting as an update or not because it's unconfirmed that's the actual traffic being passed on that TG? Seems like it's just incremental following the precinct number.
So how do we know that 104 is MTS/17/MTM if it's encrypted? Would be pretty difficult to tell from strictly RIDsSubmissions should be based on confirmed information, not speculation.
yesHas anyone heard any actual activity on this system within the last week?
What talk groups have you heard activity on?
The issue is that the system is still apparently in the buildout and testing phase and not in service. There is no reliable information about the actual intended use of the system or if traffic heard now is only for test purposes. If it was actually in service, activity on the encrypted TG could by matched with activity on the suspected associated UHF channel to confirm continued use.So how do we know that 104 is MTS/17/MTM if it's encrypted? Would be pretty difficult to tell from strictly RIDs
If the P25t is simulcasted with UHF, sure. But if they are standalone or trunking is a replacement for conventional, there's no sure fire way to tell that this TG is being used for x purpose if it's encrypted unless someone personally verifies that info with a subscriber.The issue is that the system is still apparently in the buildout and testing phase and not in service. There is no reliable information about the actual intended use of the system or if traffic heard now is only for test purposes. If it was actually in service, activity on the encrypted TG could by matched with activity on the suspected associated UHF channel to confirm continued use.
There is a strong possibility, even when the system is actually in service, activity on any TG may be sporadic since it will be active only when a subscriber unit is affiliated regardless of activity on the associated UHF channel.
Terrible logic.If the P25t is simulcasted with UHF, sure. But if they are standalone or trunking is a replacement for conventional, there's no sure fire way to tell that this TG is being used for x purpose if it's encrypted unless someone personally verifies that info with a subscriber.
Is this something worth submitting as an update or not because it's unconfirmed that's the actual traffic being passed on that TG? Seems like it's just incremental following the precinct number.
If the P25t is simulcasted with UHF, sure. But if they are standalone or trunking is a replacement for conventional, there's no sure fire way to tell that this TG is being used for x purpose if it's encrypted unless someone personally verifies that info with a subscriber.
We are interested in the following information that you have personally gathered and confirmed to be accurate, either on your own or as a group, but please keep in mind that we do not accept data drawn directly from the FCC database. You must personally verify that a frequency is in use before you submit it.
Following known RIDs is the best way to identify encrypted talkgroups.So how do we know that 104 is MTS/17/MTM if it's encrypted? Would be pretty difficult to tell from strictly RIDs
How would any RIDs be known since this is a new system if it totally encrypted?Following known RIDs is the best way to identify encrypted talkgroups.
A good place for unconfirmed, but potential info to be posted is in the wiki. Not sure if there is one for this system yet, but since submissions are intended to be confirmed information only, I find the wikis are a good place to share and crowdsource info such as this until it is confirmed accurate.Regarding this system:
New York City Police Department (NYPD) Trunking System, New York City, New York
It appears that their TGID Scheme is rather simple and follows this channel layout almost to a T
CW1=301
SI CW1=302
CW2=303
...
Man 1/5/7=101
Man 6/9=102
...
Brx 40/41=110
Brx 42/44=111
...
Bkyn 60/61=116
Bkyn 62/68=117
...
Qns 100/101=127
Qns 102/106=128
etc.
Is this something worth submitting as an update or not because it's unconfirmed that's the actual traffic being passed on that TG? Seems like it's just incremental following the precinct number.
They wouldn't. On systems that are partially encrypted, or part-time encrypted, my comment stands. However, one of the previous posters said that the talkgroup was previously in the clear, so there was an opportunity to identify RIDs before encryption.How would any RIDs be known since this is a new system if it totally encrypted?