Finally getting around to setting my main ingest up and added a few towers today. Looks like there's 3 talkgroups that I've seen in the Ashland KY area so far.
3200 - Sounds like Kentucky DDC, have received traffic on this TG but haven't heard any addresses yet to correlate a location/area
2266 - Looks like an Ohio talkgroup, no traffic to Rdio yet
4206 - I assume a WV talkgroup, no traffic to Rdio yet
Once I have some more details on these I'll submit them to the DB and get things sending to Calls. Also seems like I've seen traffic on the Ironton and South Point towers, have not seen any traffic on Catlettsburg or Greenup yet even though I'm fully locked on. West Portsmouth is iffy right now and I haven't tried punching in any more WV sites or additional KY sites yet.
Sounds great. I'm looking forward to hearing the new nodes online.
If I may make some suggestions:
1. When you set up the Calls feed for each AEP node, set the Down notification time to 8 hours or more
If you don't, you'll get driven crazy by the false Up/Down notifications that you will get when there are 3-4 or even 8 hours since a last transmission. Unlike a standard feed, a Calls Feed is "offline" when it isn't sending any audio for a period of time. And on these AEP sites the audio is often scarce. I set mine to 8 hours, and I get notified EVERY night that it is down, and then back up in the morning. I could have set it to 12 or 24 hours, but I don't want to be aware if is actually down. So I set to 8 hours of no audio, then it's down.
2. SDRTrunk will display radio aliases
OH#### for Ohio
APO#### for Appalachian Power
Unfortunately, every one I have ever seen is generic, making it impossible to identify anything other than which part of the AEP system they are from. Forget about using the OTA aliases to determine general location or type of activity.
3. You'll notice that the feed isn't always visible in the Node list, depending upon how recently actual audio has been sent to that node.
Mike