Summary: | ASTERISK-11935: I get the error below | ||
Reporter: | Private Name (falves11) | Labels: | |
Date Opened: | 2008-04-28 20:02:35 | Date Closed: | 2011-06-07 14:02:54 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_sip/Interoperability |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | We could NOT get the channel lock for SIP/66.28.190.225-0ea34c1c! SIP transaction failed: 3f4ea5b12cea317556840faa3f8ce532@minixel We could NOT get the channel lock for SIP/66.28.190.225-0ea34c1c! SIP transaction failed: 3f4ea5b12cea317556840faa3f8ce532@minixel ****** ADDITIONAL INFORMATION ****** The major point for this box is that all calls come in h323 and leave SIP. So that is the different. Also I have this message a lot: Unable to handle indication 3 for 'H323/ip$6 maybe the interaction between SIP and H323 needs work | ||
Comments: | By: Brandon Kruse (bkruse) 2008-04-30 09:24:18 Could you attach debug? Does this problem happen in 1.4? What is the scenario in which this happens? -bk By: Private Name (falves11) 2008-04-30 09:41:25 Dear develeoper: The problem is only one: chan_h323. It is a deffective software, at least in 64 bits. Without it Asterisk is perfect. I had to remove it because every time I typed "core show channels", it locks up and I need to disconnect and reconnect. Furthermore, it must have a memoryleak, for there are two kernel-wide variables variable called numothersock and dgramrcvbuf that keep growing for ever when chan_h323 is used a lot. With SIP-to-SIP none of this happens. It seems to use-up resources but does not release them. It may not be even chan_h323's fault, but the openh323 libraries. I am looking for a replacement for chan_h323 and the libraries. I don't know how to debug it and I cannot certainly risk more downtime. After a few hours Asterisk becomes unresponsive, maybe because the resources have been exhausted. Valgrind cannot be used because it does not understand the multimedia instructions used by the codec translators. I already filed a bug and Julian (the valgrind creator) os looking at it. Please close the case, unless somebody wants to take control of the box and I can send a few thousand h323 calls and we can get to te bottom of this. I feel, though, that Asterisk does not consider h323 important, but there are hundreds of dialers out there that use H3323, exclusively. |