Calls node listener stats

[HiVolt]

I've been running my calls node for a bit over a month, and it seems to be working very well. I used to feed analog audio for a long time, and it was interesting looking at the listener stats.

Does something like this exist for a Calls node, the trunked site being monitored? I haven't been able to find anything just poking around. Only thing I can see is what appears to be current listeners in the public playlists list/search, but no daily/monthly graphs like exist on the analog feed side.

Thanks.

 

[AB5ID]

Something like these statistics would make being a Calls node feed supplier much more interesting. One of the incentives of running a legacy feed is being able to watch listener numbers fluctuate, while also having a personal page with information and links to social media.

 

[HiVolt]

Something like these statistics would make being a Calls node feed supplier much more interesting. One of the incentives of running a legacy feed is being able to watch listener numbers fluctuate, while also having a personal page with information and links to social media.

Yeah, it's like not knowing if anyone is listening at all, or if anyone or how many were listening during an emergency event earlier etc.

Would be a nice feature added.

 

[blantonl]

I'll look into some ways to provide this, but understand that calls is a completely difference architecutre where you are contributing calls and content to an entire "system" - not just a targeted individual feed.

Playlists, and even individual groups, are populated by everyone contributing to the system, not just your node, so I can't really tell you who is "listening" to what your node is providing.

It's similar to adsb viewers... there are thousands of receivers all contributing the same thing and there is a mediation router on the back end which dynamically allocates what is being served for something like an individual airplane.

So, I know what you want to see if something that tells you how your contribution to the calls network is being "utilized" by end users, but the way the system is architected there really isn't a way to do that. You can setup public playlists and have them published by us, and that will tell you how many listeners are on the playlist, but that still isn't going to tell you if they are listening to your node or not.

 

[HiVolt]

Maybe it doesn't have to be active listeners, but like how many "hits" or "calls" were used to feed to a system that someone listened to.

Or maybe just a stat page for the whole system, no matter how many people feed into it.

 

[blantonl]

Maybe it doesn't have to be active listeners, but like how many "hits" or "calls" were used to feed to a system that someone listened to.

Or maybe just a stat page for the whole system, no matter how many people feed into it.

Your calls node already has some stats - that's really all we are able to provide. I'm sorry, but cross-referencing hundreds of thousands of daily sessions to how your node filled it is an enormous exercise in technology data mining and correlation.

 

[HiVolt]

Yeah, i understand.

Thanks for your time.