Hi everyone, Does someone know why the solution for bug 13115 (https://issues.asterisk.org/bug_view_advanced_page.php?bug_id=13115) was made only for trunk? Having that this bug went solved more than a year ago, it means that all the 1.6.X.X branches have it applied already? Can this be backported to the 1.4 branch? This could be another good reason to upgrade to 1.6.0.16 after I do some good testing...
I'm having this issue on asterisk 1.4.22, this is a quick grep for ERROR of the last lines of /var/log/asterisk/messages file: [Sep 23 10:51:45] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-ad66bcf8! [Sep 23 10:51:45] ERROR[26172] chan_sip.c: SIP transaction failed: 57d7bbb010e5b40105f0fe5b43644...@192.168.130.25 [Sep 23 10:51:45] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-ad66bcf8! [Sep 23 10:51:45] ERROR[26172] chan_sip.c: SIP transaction failed: 57d7bbb010e5b40105f0fe5b43644...@192.168.130.25 [Sep 23 10:51:47] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/512-ab3bec38! [Sep 23 10:51:47] ERROR[26172] chan_sip.c: SIP transaction failed: ODc5N2NiNWQxMmJmNjhhMjE2ZjUwYmNhMmZkOGQ0ZjY. [Sep 23 10:51:50] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-09c5a400! [Sep 23 10:51:50] ERROR[26172] chan_sip.c: SIP transaction failed: 36959dc8707e78a3660a1bdc22a01...@192.168.130.26 [Sep 23 10:52:48] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-09d5cae8! [Sep 23 10:52:48] ERROR[26172] chan_sip.c: SIP transaction failed: 595fdb4e33e821df52940e716f1d4...@192.168.130.26 [Sep 23 10:52:48] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-09d5cae8! [Sep 23 10:52:48] ERROR[26172] chan_sip.c: SIP transaction failed: 595fdb4e33e821df52940e716f1d4...@192.168.130.26 [Sep 23 10:52:50] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-09d5cae8! [Sep 23 10:52:50] ERROR[26172] chan_sip.c: SIP transaction failed: 595fdb4e33e821df52940e716f1d4...@192.168.130.26 [Sep 23 10:53:01] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-ad51b0c0! [Sep 23 10:53:01] ERROR[26172] chan_sip.c: SIP transaction failed: 0f90abe5604baaed4e52aff222143...@192.168.130.25 [Sep 23 10:53:02] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-ad51b0c0! [Sep 23 10:53:02] ERROR[26172] chan_sip.c: SIP transaction failed: 0f90abe5604baaed4e52aff222143...@192.168.130.25 [Sep 23 10:53:03] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-ad51b0c0! [Sep 23 10:53:03] ERROR[26172] chan_sip.c: SIP transaction failed: 0f90abe5604baaed4e52aff222143...@192.168.130.25 [Sep 23 10:53:04] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-ad51b0c0! [Sep 23 10:53:04] ERROR[26172] chan_sip.c: SIP transaction failed: 0f90abe5604baaed4e52aff222143...@192.168.130.25 [Sep 23 10:53:08] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-ad51b0c0! [Sep 23 10:53:09] ERROR[26172] chan_sip.c: SIP transaction failed: 0f90abe5604baaed4e52aff222143...@192.168.130.25 [Sep 23 10:53:11] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-ab3c2bb0! [Sep 23 10:53:11] ERROR[26172] chan_sip.c: SIP transaction failed: 5a950b092204a55a686b4e1b0c0a4...@192.168.130.25 [Sep 23 10:55:48] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-ad56a9a0! [Sep 23 10:55:48] ERROR[26172] chan_sip.c: SIP transaction failed: 3779df8e48834898534a09c576389...@192.168.130.25 [Sep 23 10:55:50] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-ad606448! [Sep 23 10:55:50] ERROR[26172] chan_sip.c: SIP transaction failed: 0fd7662648a103195b9d01a047e7e...@192.168.130.25 [Sep 23 10:55:53] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-ad56a9a0! [Sep 23 10:55:53] ERROR[26172] chan_sip.c: SIP transaction failed: 3779df8e48834898534a09c576389...@192.168.130.25 [Sep 23 10:55:54] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-ad56a9a0! [Sep 23 10:55:54] ERROR[26172] chan_sip.c: SIP transaction failed: 3779df8e48834898534a09c576389...@192.168.130.25 [Sep 23 10:56:01] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/TRUNK_SWITCH4PRI-ad56a9a0! [Sep 23 10:56:01] ERROR[26172] chan_sip.c: SIP transaction failed: 3779df8e48834898534a09c576389...@192.168.130.25 [Sep 23 10:58:32] ERROR[26172] chan_sip.c: We could NOT get the channel lock for SIP/200-ad136a78! [Sep 23 10:58:32] ERROR[26172] chan_sip.c: SIP transaction failed: NWExZjI5NDM2ZjQ4N2U5OGMzM2VmZGNiYjk5MzQyMGI. On the time where the error appeared, the CPU consumption of the asterisk was sky high and were in trouble because of choppy calls. Memory usage of the asterisk process tends to increase a lot too when this situation occurs every 7-10 days... Thanks for any pointers or help. Cheers, -- Ing. Miguel Molina Grupo de Tecnología Millenium Phone Center _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2009 - October 13 - 15 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
