Stuck Channels with Broadcast Module

Hello,

I’m running a broadcast campaign where we call out and play a message. The broadcast service stops and at the cli I see constant,
> Got 0ms silence < 1000ms required
> Got 0ms silence < 1000ms required
> Got 0ms silence < 1000ms required
> Got 0ms silence < 1000ms required
> Got 0ms silence < 1000ms required

It appears I have two calls stuck and checking the channels, (changed TN and IP)

SIP/Trunkout-00000 s@broadcast-campaign Up WaitForSilence(1000)
SIP/Trunkout-00000 s@broadcast-campaign Up WaitForSilence(1000)
192.168.1.10 5556523265 470060172062b10 (ulaw) Yes Rx: ACK Trunkout
192.168.1.10 5556548520 305c1c291574869 (ulaw) Yes Rx: ACK Trunkout

I have to manually kill the channels from the cli and then restart the service. Previously, I just started the service and when it stopped at the correct time, there were 5 stuck channels.

PBX Firmware:5.211.65-5
PBX Service Pack:1.0.0.0
Asterisk 11.11

Could be something with amd not sure… I do see that you are about 11 updates behind on your system, 5.22.65-16 is the current stable version in your track.

The firmware version you have 5.211.65-5 was released in January with Asterisk 11.7 , not sure how you got to 11.11 are you using the update scripts to update your system?

http://wiki.freepbx.org/display/FD/5.211.65+Release+Notes

I’ve only been upgrading the modules and didn’t run any freepbx upgrade scripts which I will do right now. Can you tell me if running the upgrade could affect my running campaign? It’s halfway through and only runs in the late afternoon, so time is not a problem but if it were to lose how many calls were left. That would be bad. :stuck_out_tongue:

Upgrade went smoothly,

PBX Firmware:5.211.65-16
PBX Service Pack:1.0.0.0
Asterisk 11.12.0

If you still see issues you would need to provide a way to replicate this and open a bug report at issues.freepbx.org and we can take a look. But broadcast uses the Asterisk AMD which is Answering Machine Detection system and those notices you printed come from that saying its not getting any silence and it needs silence to know when to start the message.

Next time can you barge in and listen to the call and see what you hear?