Calls Node with multiple sources, one is terrible but always "wins"

[nick0909]

I run one of the San Diego City sytem calls nodes, node 17.
There is someone else that feeds the same system on node 3685.

3685 always uploads the calls first and my uploads are all rejected. The problem is, 3685 is only decoding a portion of the call, normally 0-2 seconds worth, and then having some error and uploading the result. But because it gets there first, my completed recordings are rejected. This results in basically making the entire system unlistable, as all the recordings are cut short. You can hear an example just by trying to listen to fire dispatch, which should all be 20-30 seconds long: Fire Dispatch/Fire/EMS Group Calls Live

Is there anything that can be done to not accept the other node's recordings until their reception problem can be fixed?

 

[mtindor]

I run one of the San Diego City sytem calls nodes, node 17.
There is someone else that feeds the same system on node 3685.

3685 always uploads the calls first and my uploads are all rejected. The problem is, 3685 is only decoding a portion of the call, normally 0-2 seconds worth, and then having some error and uploading the result. But because it gets there first, my completed recordings are rejected. This results in basically making the entire system unlistable, as all the recordings are cut short. You can hear an example just by trying to listen to fire dispatch, which should all be 20-30 seconds long: Fire Dispatch/Fire/EMS Group Calls Live

Is there anything that can be done to not accept the other node's recordings until their reception problem can be fixed?

You probably first need to exhaust the route of reporting the issue to the node provider. Then if the node provider does not do anything about it, get a hold of Lindsay.

 

[nick0909]

You probably first need to exhaust the route of reporting the issue to the node provider. Then if the node provider does not do anything about it, get a hold of Lindsay.

I reported it a while ago and it seems to only have gotten worse at decoding since then. How should I proceed?

 

[mtindor]

I reported it a while ago and it seems to only have gotten worse at decoding since then. How should I proceed?

If I were you, I would contact lindsay@radioreference.com with as full of a description as you can give (you did pretty good above) including the node in question, etc. Instead of pointing him to your thread here, I'd actually repeat it all in an email to him.

Lindsay is the only one who could take any action at all, and he has always been willing to listen to my node complaints.

Mike