So, I want to make sure I'm doing this right.. I'm building a "mega ingest" that will cover multiple systems and sites (specifically OH MARCS, WV SIRN, and AEP) and I'm planning on sending it to Calls. I put in a couple applications for Calls nodes for Wayne Co to start out.. but I wanted to make sure I'm covering things right. Do I need a separate Calls node for each site or can I send multiple sites to one node, or what is the best way to go about it?
Calls Node covering multiple counties
- Thread starter iceman977th
- Start date
Yes, each site should/must have its own calls node. You should not capture multiple sites and upload them to one node. One node per site
Are you saying each site as in receive site or each tower? Just making sure I'm on the right page. Like you and I talked about, this ingest is up at a tower site and is literally picking up about 15 individual control channels across 3 systems, and I don't know how to differentiate the aliases between, for example, the Missouri Branch tower and Wayne tower on the same talkgroup.Yes, each site should/must have its own calls node. You should not capture multiple sites and upload them to one node. One node per site
For each trunk system site. If you’re monitoring a trunk simulcast, then that counts one node.
In other words, if you’re picking up 15 control channels, those are 15 separate sites. If one of those control channels is for a simulcast that consists of 10 physical sites, they are all using the same control channel, and that’s a single site for BC FY calls purposes
So if you were to look at Ohio MARCS, every one of those listed sites, simulcast, or not, is a site in the eyes of SDR trunk and BCFY calls
And an SDR trunk you can create one alias list for MARCS and use that same alias list for every MARCS site that you are collecting data on. You only need one alias list per system, with Ohio MARCS being a system
