Broadcastify Calls Not Going Through to Server

[RaleighGuy]

My calls feed Node 1225 is running fine, recordings are being made and attempted to be sent, my internet is good, but for some reason the server they are being sent to is not accepting my recordings, just started a few hours ago.

UPDATE: When I cleared calls in que waiting to be uploaded it corrected itself and started working again.

Any suggestions on what caused this or how to prevent it in the future?

 

[blantonl]

What are you using to broadcast?

Possibly your system got backed up and your skew on calls was greater than allowed by the system causing them to be rejected

 

[RaleighGuy]

What are you using to broadcast?

Possibly your system got backed up and your skew on calls was greater than allowed by the system causing them to be rejected

Unitrunker V2 to Trunking Recorder via ethernet

 

[GTR8000]

I experienced the same thing a few hours ago. Restarted SDRTrunk and it seems fine now. Chalked up to a momentary glitch, unless it happens again. Will continue to monitor.

 

[RaleighGuy]

Yeah it is doing it again, get got notification.

77 calls in Call Queue as soon as I cleared it it started working again. Not sure what is causing this issue.

 

[jasonk]

Like Lindsay mentioned - your Skew got behind and the calls were rejected. I had the same issue recently when there were a bunch of captured transmissions in the queue. You need to find the bottleneck and correct it or this will continue to happen.

 

[RaleighGuy]

You need to find the bottleneck and correct it or this will continue to happen.

And for those of us not tech savvy, how does one find it? This just started happening today, after years of running the feed.

 

[GTR8000]

Like Lindsay mentioned - your Skew got behind and the calls were rejected. I had the same issue recently when there were a bunch of captured transmissions in the queue. You need to find the bottleneck and correct it or this will continue to happen.

Well, no. I'm well aware of the call skew issue, and that's not what was going on in my case. First of all, SDRTrunk logs each time a call skew rejection occurs, and there were none logged. Secondly, I have an NTP client running that syncs the time every 15 minutes. Lastly, the node upload issue lasted 25 minutes, so it was no "call skew" glitch.

 

[louisik1]

Well, no. I'm well aware of the call skew issue, and that's not what was going on in my case. First of all, SDRTrunk logs each time a call skew rejection occurs, and there were none logged. Secondly, I have an NTP client running that syncs the time every 15 minutes. Lastly, the node upload issue lasted 25 minutes, so it was no "call skew" glitch.

I'm having an issue right now. When I connect to Broadcastify (to listen to my own feed, 40212), the feed starts then stops, then starts again, plays a broadcast, then stops.. I've just started looking at it, and it seems weird enough to maybe be a server issue. I'm still investigating.

 

[RaleighGuy]

I'm having an issue right now. When I connect to Broadcastify (to listen to my own feed, 40212), the feed starts then stops, then starts again, plays a broadcast, then stops.. I've just started looking at it, and it seems weird enough to maybe be a server issue. I'm still investigating.

Is this on Calls Platform or regular feed?

 

[louisik1]

Is this on Calls Platform or regular feed?

This is a regular feed. Interestingly, if I connect with the android broadcastify app, i dont experience the problem, bu ti fi go to another computer and try listening from the browser, i have the same issue i described above. Do you experience it with your browser? The problem usually shows up within 15 seconds. Seattle Police and Fire (PSERN) Live Audio Feed

 

[RaleighGuy]

This is a regular feed. Interestingly, if I connect with the android broadcastify app, i dont experience the problem, bu ti fi go to another computer and try listening from the browser, i have the same issue i described above. Do you experience it with your browser? The problem usually shows up within 15 seconds. Seattle Police and Fire (PSERN) Live Audio Feed

Okay this is a totally different issue, unrelated to the thread. But thanks for mentioning it.

 

[jasonk]

Well, no. I'm well aware of the call skew issue, and that's not what was going on in my case. First of all, SDRTrunk logs each time a call skew rejection occurs, and there were none logged. Secondly, I have an NTP client running that syncs the time every 15 minutes. Lastly, the node upload issue lasted 25 minutes, so it was no "call skew" glitch.

Since I wasnt answering you .... thanks for the info. If you figure out your specific issue (Not related to the OP issue - please let us know) And yes - if he is queuing 77 calls - it will get blocked once they try to upload with an out of whack time stamp ...