The LTR-NET system is being replaced by NXDN.  Many sites may be deprecated. Sites remaining on the air appear to be stand-alone LTR and not networked. Traffic may be data only.  I am not depreacting inactive sites since some control channels occasionally return, apparently during migration to NXDN.

Trumansburg CSD is the only known remaing subscriber.

This is an LTR-Net network that spans most of upstate New York.

Each site has a Home Status Channel that continuously transmits an idle signal.  You may encounter mobile radios occasionally using this channel for voice communications. The Home Status Channel for each site is highlighted in red on this site, as if it were a control channel.

Each site's Home Status Channel and each of the traffic channels transmit a repeating set of messages to define the Locality number, up to 6 neighboring locality numbers, site channel map, transmit frequency for each of the channels, and receive frequency for each of the channels. Roaming mobile radios use this messaging to self-configure the radio for operation on the roaming site.  Additionally, there are LTR-Net messages for addressing specific users for sending data messages and reprogramming mobile radios over the air.

You can monitor each of the sites in this system with an LTR-capable scanner, however you may not see any of the LTR-Net specific messaging/signaling.  LTR-Analyzer version 3.0 or higher displays both the LTR and the LTR-Net signalling.

Many of the subscribers are using Fleetsync 1200 for ANI during calls.  At least one (Tully site LCN9) has a dedicated Fleetsync data channel.  The system notifies individual radios to temporarily tune to the data channel by sending an LTR x-xx-253 talkgroup message, coupled with an LTR-Net 17 unique radio id message. Fleetsync GPS, selcall, short and long data messaging occur on the data channel.  Some of the fleets have each of their subscribers broadcast their GPS position on the data channel every 6 minutes, while operating.

Some site frequencies are being shared between the Mobiletech NEXEDGE 4800 and LTR-NET system. The LTR-NET CCs are remaining but other LTR-NET site frequencies are alternately used for NXDN. It appears that the active NXDN CC frequency is busied out on LTR and the voice channels alternate between the two systems. Additional new site frequencies are dedicated to NXDN. The NXDN CCs may rotate, seemingly at random times.