Due to a bug in the DAHDI/asterisk interaction there is quite a large probability that after a reboot one will be unable to establish outbound calls after a reboot. This is due to the fact that the hookstate was never ignored by asterisk but abused as a way of checking whether there is battery on the line or not, this check should in fact happen against the alarm state (which will be red if the line is down), and seeing that this check is already performed higher up in the code (for ISDN), the attached patch just kills off the code unless an explicit DAHDI_CHECK_HOOKSTATE define is set - which should never be set. Reproducible: Always Steps to Reproduce:
Created attachment 201237 [details] dahdi-fxsks-hookstate.patch Applies cleanly with patch -p0 against all versions of asterisk 1.6.* as far as I can tell. I just merged it against asterisk 1.6.1.1-r1 as in the tree.
bump. Still required for 1.6.1.5, patch still applies cleanly.
And upstream still isn't happy with your fix yet. Ping me when you've got your fix upstream and I'll carry it until it makes it into the next release.
+*asterisk-1.6.1.6-r1 (22 Oct 2009) + + 22 Oct 2009; <chainsaw@gentoo.org> +asterisk-1.6.1.6-r1.ebuild, + +files/1.6.1/asterisk-1.6.1.6-fxsks-hookstate.patch, + +files/1.6.1/asterisk.initd, -asterisk-1.2.32.ebuild, + +files/1.6.1/asterisk-1.6.1.6-transfer-segfault.patch: + Revision bump. Init script now depends on dahdi, not zaptel (bug #279436). + FXO ports can now carry outbound calls immediately, without requiring an + inbound call first (bug #281467) and transferring queue calls no longer + segfaults. With thanks to Jaco Kroon. Troublesome H323 support removed due + to pwlib dependency in openh323 (bug #290065) and IMAP support removed as + it never worked right (bug #265567). Bug reports on either only accepted + with patches.
