Calls - Listening via Individual Nodes no longer available

[rcid1971]

Every man has his breaking point rcid1971. It's not nice to come in and throw stones in peoples homes, all the while not really having a good leg to stand on.

I take to heart feedback, but those that have taken the stance that our decision to move away from listening to individual nodes are dying on the dumbest hill possible in the face of overwhelming information and contradicts all the evidence to the contrary. We've beat this to death. Your use of the phrase "Major Fail" is... obtuse. everything suggests otherwise.

I'll go back to your original reply and take that at face value and ignore the rest.

Look you’re right, major fail was a poor word choice, and I didn’t fully appreciate how sensitive some would be to that.

The pushback to losing nodes access should be noteworthy to how users really enjoyed the calls system. It’s just really unfortunate how the best features of these products and services lead to their detriment. The concept of full access to a remote receive site in relative real time was a major win for the subscriber.

 

[rcid1971]

Duplicate

 

[blantonl]

It’s just really unfortunate how the best features of these products and services lead to their detriment.

Well, the statistics, traffic, revenue, and the facts do not prove this out. This is simply your opinion, and if I have to drag you kicking and screaming into agreement, I will. The community as a whole is moving forward with or without you.

Look around you, things are working out really well. Our products and services have never been stronger than they are today.

 

[egftechman]

How would an area playlist have enough capacity to include Tac 32?

You can always listen to systemwide calls... Like Baltimore City - All Calls Live or Baltimore County - All Calls Live if you want the "firehose".

 

[Napalm]

Yeah, we had a playlist tactically generated and made available to the public within minutes later that morning with hundreds of listeners, covering 3 totally separate wide area trunking systems, and we had a new record for Broadcastify Calls users yesterday.

It might have been the best use of the calls platform and ease of use for monitoring such a complex incident in the history of the platform.

I was touting calls on that dispatch video you commented on. Some dude complaining about Uniden and noise lol.

 

[Napalm]

Look you’re right, major fail was a poor word choice, and I didn’t fully appreciate how sensitive some would be to that.

The pushback to losing nodes access should be noteworthy to how users really enjoyed the calls system. It’s just really unfortunate how the best features of these products and services lead to their detriment. The concept of full access to a remote receive site in relative real time was a major win for the subscriber.

See, you're not understanding. There can be MULTIPLE nodes uploading to calls. If you're listening to just ONE node, you WILL miss calls. The algorithm dictates which call gets accepted from which node.

With a playlist, it takes the call from whichever node the algorithm votes on. You will not miss a call.

I'm not connected to RR in any way except I am a calls uploader.

 

[rcid1971]

See, you're not understanding. There can be MULTIPLE nodes uploading to calls. If you're listening to just ONE node, you WILL miss calls. The algorithm dictates which call gets accepted from which node.

With a playlist, it takes the call from whichever node the algorithm votes on. You will not miss a call.

I'm not connected to RR in any way except I am a calls uploader.

When seeking information from the specific geography of a specific node, it allowed the user to intentionally listen to AVOID calls from non-relevant talk groups. Does that make sense? The beauty of the way it once worked was you had a very specific region with which to focus your listening, not a systemwide playlist of every talk group on the system unrelated to the geography of your listen at that moment.

 

[blantonl]

When seeking information from the specific geography of a specific node, it allowed the user to intentionally listen to AVOID calls from non-relevant talk groups. Does that make sense? The beauty of the way it once worked was you had a very specific region with which to focus your listening, not a systemwide playlist of every talk group on the system unrelated to the geography of your listen at that moment.

The problem is there are multiple nodes that could be providing the same talkgroup and we vote between nodes for individual talkgroups.

If there is a node 250 miles away with a better quality ranking providing the talkgroup, trying to listen could result in you never seeing that talkgroup active, because you decided to choose a node that MIGHT be providing the group, but wasn't actually providing it. What part of this are you not getting?

You're simply not looking at the big picture, and arguing a point that I've literally refuted multiple times, but you still want to believe your own versions of how things are designed and architected here. You need to give it up. Let it go. I'm begging you from the bottom of my heart. As calls grows more and more, and more and more nodes are joining the system, this will become more apparent. But it just baffles the mind you still continue to want to belabor this after I, as the designer of this system, has repeatedly told you it is not the correct approach to take. It's maddening. I can't even believe it. What is the problem?

 

[rcid1971]

The problem is there are multiple nodes that could be providing the same talkgroup and we vote between nodes for individual talkgroups.

If there is a node 250 miles away with a better quality ranking providing the talkgroup, trying to listen could result in you never seeing that talkgroup active, because you decided to choose a node that MIGHT be providing the group, but wasn't actually providing it. What part of this are you not getting?

You're simply not looking at the big picture, and arguing a point that I've literally refuted multiple times, but you still want to believe your own versions of how things are designed and architected here. You need to give it up. Let it go. I'm begging you from the bottom of my heart. As calls grows more and more, and more and more nodes are joining the system, this will become more apparent. But it just baffles the mind you still continue to want to belabor this after I, as the designer of this system, has repeatedly told you it is not the correct approach to take. It's maddening. I can't even believe it. What is the problem?

Why would a fire tactical channel localized to a single department be playing on a node 250 miles away? That’s precisely why I’d choose to monitor a single node versus a systemwide live playlist. The tunnel vision answers provided here are astonishing.

You had customers that preferred the previous iteration of nodes for their own personal reasons. Just accept that.

Whether it was a hack, or a side effect of the previous programming. It worked for what some users needed. Now it doesn’t exist. I can accept that. It’s an exploit I used to like. Sorry for liking node access.

 

[blantonl]

Why would a fire tactical channel localized to a single department be playing on a node 250 miles away? That’s precisely why I’d choose to monitor a single node versus a systemwide live playlist. The tunnel vision answers provided here are astonishing.

Well, for one, during a major incident, people will turn on their radios and affiliate to that talkgroup from all over the system to hear what is going on. If a node that is a slightly better quality node gets promoted to providing that talkgroup on calls, you are NOT going to see that talkgroup on the more "local" node that you expected. Period. End of story. It might be the most critical talkgroup the entire incident is being handled on, and it also might be an interop talkgroup which means all the users on the wide-area system could indeed affiliate that talkgroup to a site 100's of miles away.

Did you think of that scenario champ? Nope. Ya didn't.

You had customers that preferred the previous iteration of nodes for their own personal reasons. Just accept that.

And as I've explained to you, THIS WILL NOT WORK. Listening via an individual node will generate massive confusion (why isn't a talkgroup being captured by this expected node???) and a ton of support requests for someone who attempts to do exactly what you propose.

You do NOT know what you are talking about, and you DO NOT understand how wide area systems work, the behavior of their users, and what happens during major incidents.

The tunnel vision answers provided here are astonishing.

This is so rich. You may not like to hear this, but you have absolutely no idea what you are talking about. Just accept that. Let us not forget that you previously saw "Tac 32" and thought there were 32 tac channels on the system which would exceed the playlist max of 30. This is the level of mentality you're presenting in public.

I could not have originally picked a more appropriate word to describe your approach to this entire discussion.

obtuse.
a : lacking sharpness or quickness of sensibility or intellect
b : difficult to comprehend : not clear or precise in thought or expression

 

[RenoHuskerDu]

If I go here, I hear traffic. Police Ch. 1 Dispatch/Burnet County - Burnet Group Calls Live

If I go to the Playlist I built, using your instructions, which includes this TG, I hear nothing. "No Calls Seen in the Past 10 Minutes"

2 weeks now, same results. Do I need to have Feed Dashboards defined?

 

[RaleighGuy]

If I go here, I hear traffic. Police Ch. 1 Dispatch/Burnet County - Burnet Group Calls Live

If I go to the Playlist I built, using your instructions, which includes this TG, I hear nothing. "No Calls Seen in the Past 10 Minutes"

2 weeks now, same results. Do I need to have Feed Dashboards defined?

Built a test playlist and it works fine, was able to hear a call in minutes and didn't do anything special or with a dashboard

 

[krokus]

If I go here, I hear traffic. Police Ch. 1 Dispatch/Burnet County - Burnet Group Calls Live

If I go to the Playlist I built, using your instructions, which includes this TG, I hear nothing. "No Calls Seen in the Past 10 Minutes"

2 weeks now, same results. Do I need to have Feed Dashboards defined?

I just tried the above link, and there were multiple transmissions in the window. Are you logged in to that side of the system?

 

[RenoHuskerDu]

I just tried the above link, and there were multiple transmissions in the window. Are you logged in to that side of the system?

How would I log in to a certain side of the system? I'm not aware of that. I just login to RR and Broadcastify as always.

 

[RenoHuskerDu]

I just tried the above link, and there were multiple transmissions in the window. Are you logged in to that side of the system?

I can hear the TG, but once it's put in my playlist, it's silent. Here are two screenshots. Could be be that I need to define a feed dashboard, whatever that is? I certainly don't want to be labeled obtuse. But I wish we could monitor nodes again.

 

[RaleighGuy]

How would I log in to a certain side of the system? I'm not aware of that. I just login to RR and Broadcastify as always.

There is several ways, if you want to search by coverage area use this link HERE

If you want to go to a particular TG, like the one you mentioned above go HERE

And you can always start at the begining HERE

Remember to log in

 

[RaleighGuy]

I can hear the TG, but once it's put in my playlist, it's silent. Here are two screenshots. Could be be that I need to define a feed dashboard, whatever that is? I certainly don't want to be labeled obtuse. But I wish we could monitor nodes again.

Keep in mind, that is not a busy system. If you look at recent calls there is a 30 minute gap with no calls between 6:50 and 7:23 tonight. It works fine in play lists, I showed you that yesterday.

 

[krokus]

How would I log in to a certain side of the system? I'm not aware of that. I just login to RR and Broadcastify as always.

I meant Broadcastify. It's a separate server, with separate login sessions. I thought you might not have signed in to the streaming server.

 

[RenoHuskerDu]

I meant Broadcastify. It's a separate server, with separate login sessions. I thought you might not have signed in to the streaming server.

Broadcastify is all I use, on an android, to listen mobile. So I'm logged in there and on RR. I'll be out again today, doing church security duty, and try to listen to local LE realtime. Maybe it will work this time.

Burnet City PD recently moved its Dispatch from Burnet Co SO to Marble Falls PD, a neighboring city. I wonder if that is a factor. I believe the move was in March.

 

[slhorne]

Curious as to how the Calls system 'picks' which node it accepts traffic on a particular TG from. My area now has more than one node that picks up traffic (at times), but it seems to be picking the other node, which misses traffic and has worse audio quality, even though my node is catching all the traffic.
Does it pick based on time delay? Any other factors we can know about to improve things on the provider end?