[asterisk-bugs] [Asterisk 0012748]: [patch] multiparking, "WARNING[6006]: channel.c:2065 __ast_read: ..." fixed

noreply at bugs.digium.com noreply at bugs.digium.com
Thu May 29 14:06:39 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12748 
====================================================================== 
Reported By:                nreinartz
Assigned To:                mvanbaak
====================================================================== 
Project:                    Asterisk
Issue ID:                   12748
Category:                   Core/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 118614 
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             05-29-2008 05:14 CDT
Last Modified:              05-29-2008 14:06 CDT
====================================================================== 
Summary:                    [patch] multiparking, "WARNING[6006]: channel.c:2065
__ast_read: ..." fixed
Description: 
I had a look at the multiparking feature and did some tests. To be fair I
have to say that I tested multiparking with a patched version of 1.4.20.1 
http://bugs.digium.com/view.php?id=12740.
As the logic is the same in 1.6 trunk as in my patched version of 1.4 the
described failure also should occure in 1.6 trunk.

I always get this warning starting with the second call if core debug
level is set to 10:
>>>>>>
[May 29 10:40:44] WARNING[6006]: channel.c:2065 __ast_read: Exception flag
set on 'SIP/5555-081fddf0', but no exception handler
Really destroying SIP dialog '3c49a803c2b3-6bdvxzki22wa' Method: ACK
<<<<<<

Szenario:
 - Start asterisk.
 - A calls B (1st call).
 - B gets the call.
 - A parks B.
 - B hangs up, A hangs up.
 - A calls B (2nd call).
 - B gets the call.
 - A parks B.
  --> I get the warning described above!!

Logging output is included in attached file "logging.txt".

The problem is that filedescriptor sets nrfds and nefds in
main/features.c, do_parking_thread() aren't initialized to have zero bits
each time before the loop to call manage_parkinglot() is entered.
The attached patch
"asterisk-multiparking_initialize_filedescr_sets-0.0.1.patch" fixes this
bug.
====================================================================== 

---------------------------------------------------------------------- 
 svnbot - 05-29-08 14:06  
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 119016

_U  branches/1.6.0/

------------------------------------------------------------------------
r119016 | mvanbaak | 2008-05-29 14:06:39 -0500 (Thu, 29 May 2008) | 17
lines

Blocked revisions 119015 via svnmerge

........
r119015 | mvanbaak | 2008-05-29 21:10:31 +0200 (Thu, 29 May 2008) | 10
lines

Make sure the nrfds and nefds are reset to NULL
before we enter manage_parkinglot.
This will get rid of CLI warnings like:
__ast_read: Exception flag set on 'SIP/<NUMBER>-<ID>', but no exception
handler

(closes issue http://bugs.digium.com/view.php?id=12748)
Reported by: nreinartz
Patches:
      asterisk-multiparking_initialize_filedescr_sets-0.0.1.patch uploaded
by nreinartz (license 452)

........

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=119016 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-29-08 14:06  svnbot         Checkin                                      
05-29-08 14:06  svnbot         Note Added: 0087505                          
======================================================================




More information about the asterisk-bugs mailing list