Hello, All.
We run into a weird problem with the parked calls on a multi-tenant version. Overall it seems working - you may park a call, MOH is played and you even can dial the parking slot and take the call back. But sometimes, for some reason, MOH for parked calls stops playing, especially, when the call bounced back by timeout and it was parked again. The customer thinks that call is hung and hangup. One time in the logs ("parkedcalls show") I've seen negative value for the parking time and this call never was returned back. Also, there are strange ZOMBIE channels in the logs, when I park a call. Does anybody faced such problem? Asterisk version 1.6.2.11. PBX Manager 6.1.1.6
Already updated till the
Already updated till the 1.6.2.20.
It seem that this bug was fixed in the 1.6.2.17
main/features.c: main/features: Use POLLPRI when waiting for
events on parked channels. This change resolves a regression in
the 1.6.2 when converting from select to poll. The DAHDI timers
use POLLPRI to indicate that the timer fired, but features was
not waiting for that flag. The result was no audio for MOH when a
call was parked and res_timing_dahdi was in use. This patch is
slightly modified from the one on the mantis issue. It does not
set an exception on the channel if the POLLPRI flag is set.
(closes issue #18262) Reported by: francesco_r Patches:
patch_park_moh-trunk-2.txt uploaded by cjacobsen (license 1029)
Tested by: francesco_r, rfrantik, one47
The problem very similar to the described one, but I don't receive a feedback if it help. Will see on Monday.
you should not be running
you should not be running anything on 1.6 branch if you use BLF, unless you enjoy system crashes. They didnt fix the bug until 1.8.7
Not enjoying at all.
Not enjoying at all. Especially on the productive systems.
After upgrade from 1.6.2.11 till 1.6.2.20 it started to hung during reloads. This never happens before on the version 1.6.2.11. Finally, yesterday we had a true crash with core file. After this crash we have upgraded till the version 1.8.7.1 (via yum thirdlane repository). All was working until the system just stop to process calls without even reload. Along with the asterisk upgrade, dahdi-linux was upgraded (also, via yum). What do you suggest to do next? Build asterisk and dahdi from sources? Could the upgraded dahdi be a reason of hungs? We are using parking and BLF heavily.
PS. Now I hate upgrades even more than before.
thats why I said you should
thats why I said you should be running off the asterisk 1.8 branch.. they didnt even fix that crash bug untill 1.8.7. that bug started in 1.6.12 and lasted until 1.8.7. However, if you read the changelog, there are obviously other bugs along the way to content with. If you check out asterisk.org you will see a new branch they created as part of their support for the digium DPMA module. As a result they spawned a new branch called 'certified' which has fewer update cycles. So even though the open source branch is hovering around 1.8.14 whereas they built the current certified release off of 1.8.11 with backports of security fixes. I would reccomend running this release. Here is the full info, from the website, about the certified release -
Certified Asterisk is a branch of Asterisk supported by Digium for commercial, SLA customers, entitled under certain Support offerings. Like other branches of Asterisk, it is provided under GPLv2 license and may be used freely by anyone, even users and other customers who are not Digium’s SLA customers.
Releases are made at longer intervals, between 2 and 4 times annually, as opposed to the once-per-month cycle of mainline Asterisk releases; and are curated to minimize change and support longer quality assurance windows. This allows SLA customers to minimize the uncertainty of accepting large or frequent code updates. Each Certified Asterisk release begins as a selected mainline Asterisk point release that undergoes a rigorous and extended internal testing process. At the completion of the testing process, a new release is made, and SLA customers may begin receiving support, as dictated by their support agreements, on that release.
Releases of Certified Asterisk are made against the current Asterisk LTS codebase, presently 1.8, not against Asterisk Standard releases, e.g. 10, and represent a snapshot of the mainline Asterisk LTS release, branched and maintained with SLA customer bugfixes. Each release is versioned according to: asterisk-MainlineBranchPoint-certX, e.g. asterisk-1.8.6-cert1, where MainlineBranchPoint indicates the Asterisk release point at which the branch occurred and X represents the bug-fix release version of a particular release of Certified Asterisk. Bug-fix releases of Certified Asterisk are made for the duration of customer support agreements; and, following 1.8, new releases of Certified Asterisk will be made against the upcoming Asterisk 11 LTS version, and ongoing LTS releases after that. This schedule provides customers the flexibility to migrate from one release to another, with overlapping support between major versions of Certified Asterisk.
out dated asterisk version of almost 2yrs old. update to latest 1.8 branch.