Summary:ASTERISK-17271: DAHDI channel becomes busy/unusable after it's called and not picked up
Reporter:David Gonzalez (dgonzalezh)Labels:
Date Opened:2011-01-22 15:54:51.000-0600Date Closed:2011-01-24 08:48:40.000-0600
Versions:1.8.4 Frequency of
Environment:Attachments:( 0) call_trace.txt
( 1) call_trace-2.txt
Description:I'm using ClearOS 5.2 x86 (CentOS 5.2) withan Openvox A1200P card with just two modules 1 FXS and 1 FXO on slots 1 and 4 respectively. I'm also using DAHDI 2.40
DAHDI Version: 2.4.0
Echo Canceller(s): OSLEC

I have some SIP and IAX extensions and trunks which work well also the FXO port doesn't suffer from this behaviour.

I start dahdi using service dahdi start and then asterisk using amportal start, when I call extension 101 which is the on the FXS module 1 the phone rings

and this shows

   -- Called 1
   -- DAHDI/1-1 is ringing
   -- DAHDI/1-1 is ringing
   -- DAHDI/1-1 is ringing
   -- DAHDI/1-1 is ringing
   -- Nobody picked up in 15000 ms
   -- Hungup 'DAHDI/1-1'

[Jan 22 16:44:29] WARNING[9040]: chan_dahdi.c:2911 dahdi_set_hook: DAHDI hook failed returned -1 (trying 1): Device or resource busy
   -- User disconnected

After this the modules/extension becomes unusable and all the time I get the "busy" voicemail message for that extension.

I have to shutdown asterisk and then unload dahdi and re-load it and restart Asterisk and I can make a call again but then this issue comes up again.

This began happening since I upgraded to + DAHDI linux complete 2.4.0+2.4.0

****** STEPS TO REPRODUCE ******

Load dahdi
Start Asterisk amportal start
Dial the extension on the FXS module
Comments:By: Leif Madsen (lmadsen) 2011-01-24 08:48:40.000-0600

Please request support from your hardware vendor.