• Effective immediately we will be deleting, without notice, any negative threads or posts that deal with the use of encryption and streaming of scanner audio.

    We've noticed a huge increase in rants and negative posts that revolve around agencies going to encryption due to the broadcasting of scanner audio on the internet. It's now worn out and continues to be the same recycled rants. These rants hijack the threads and derail the conversation. They no longer have a place anywhere on this forum other than in the designated threads in the Rants forum in the Tavern.

    If you violate these guidelines your post will be deleted without notice and an infraction will be issued. We are not against discussion of this issue. You just need to do it in the right place. For example:

996T UASD / Multisite Bandplan question??

Not open for further replies.


Dec 19, 2002
Los Altos, CA
My understanding from Wayne (the resident TRS expert) is that a multisite system must share a common base/step/offset...

It is with this understanding that I ask...

Why does UASD support different b/s/o for each site in a multisite system??


Forums Veteran
Super Moderator
Dec 16, 2000
Sitting in an airport somewhere
I believe it's just been passed down from earlier development. It provides flexibility in case things change. A safer approach if you will...

In reality there can be multiple base and offsets but that only exists in a SZ OmniLink network. Each Zone (differentiated by system id) will have its own b/s/o. Look at the Aussie GRN network for example. Though each Zone/SysID has its own ZC and its own subscriber database. So you may or may not want to link OmniLink sites; some systems it won't matter as they'll config them to work together and not rely on tresspassing.

(For the anally retarted we're speaking strictly of 3600 here.)

Not open for further replies.