Summary:ASTERISK-08467: Call dropped with "FRAME_CONTROL (5)" message
Reporter:mimmo (mimmo)Labels:
Date Opened:2007-01-03 08:09:48.000-0600Date Closed:2007-01-29 13:24:33.000-0600
Versions:Frequency of
Environment:Attachments:( 0) pridebug.log
Description:I have an Asterisk box connected to a PRI line in Italy. Randomly, in progress calls are dropped with this message in /var/log/asterisk/full:
 channel.c: Got a FRAME_CONTROL (5) frame on channel Zap/...
This happens 4-6 time every 100-150 daily calls.
All components updated to latest versions.
Comments:By: Serge Vecher (serge-v) 2007-01-03 09:11:38.000-0600

I think you should attach the output of 'pri debug' log.

By: mimmo (mimmo) 2007-01-03 09:33:38.000-0600

Bug is not reproducible. Do I need to keep 'pri debug' enabled all the time?

By: Serge Vecher (serge-v) 2007-01-03 09:43:06.000-0600

if there is no way to link the appearance of those messages to certain events, then yes.

By: mimmo (mimmo) 2007-01-03 09:55:47.000-0600

Tomorrow I will keep 'pri debug span 1' enabled for the whole day, using 'Session Log' feature of my terminal application. Then I hope to be able to correlate event in the log file to the huge crop of 'pri debug'!

By: mimmo (mimmo) 2007-01-04 10:15:12.000-0600


By: Serge Vecher (serge-v) 2007-01-04 10:32:34.000-0600

mattf: any further diagnosis required here?

By: Matthew Fredrickson (mattf) 2007-01-04 10:42:20.000-0600

Do you have callprogress in zapata.conf set to anything else other than no?  I suspect that you have that enabled when you shouldn't have it.

By: Matthew Fredrickson (mattf) 2007-01-04 10:43:32.000-0600

Oh, this could be the busydetect option as well.  Make sure both are disabled.

By: mimmo (mimmo) 2007-01-05 02:02:33.000-0600

I have no settings for both busydetect and callprogress for zapata.conf sections related to PRI channels: if their default value is yes, this can be the culprit?
I have callprogress=yes for section related to channel-bank.

By: Serge Vecher (serge-v) 2007-01-05 08:34:08.000-0600

what happens if you set that to "no"?

By: mimmo (mimmo) 2007-01-05 08:39:19.000-0600

I set callprogress=no and busydetect=no for all zapata channels.
Allow me two working days to test this.


By: mimmo (mimmo) 2007-01-09 09:07:20.000-0600

No, setting 'callprogress=no' and 'busydetect=no' didn't solve the problem.
Today I had three calls dropped with FRAME_CONTROL (5)

By: Joshua C. Colp (jcolp) 2007-01-22 22:38:55.000-0600

For reference the number 5 indicates this is a control frame indicating busy.

By: mimmo (mimmo) 2007-01-23 03:20:09.000-0600

During latest days, problems disappeared.

By: Matthew Fredrickson (mattf) 2007-01-23 13:21:40.000-0600

Probably configuration issue