[Home]

Summary:DAHLIN-00149: dahdi module doesn't work well
Reporter:Balgansuren Batsukh (balgaa)Labels:
Date Opened:2009-09-29 11:08:15Date Closed:2009-12-22 08:23:03.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:dahdi (the module)
Versions:2.2.0.2 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Hello,

After upgrade to asterisk branch 1.6.2 and dahdi-linux svn, it seems dahdi doesn't work well.

after sometime when i try to run command

pbx*CLI> dahdi restart
pbx*CLI> dahdi channels
pbx*CLI> dahdi show version

no any result come up when i run above commands.

then need to run /etc/init.d/asterisk stop and start to get work above commands.

after stop/start i can get

pbx*CLI> dahdi restart
Destroying channels and reloading DAHDI configuration.
      > Initial softhangup of all DAHDI channels complete.
      > Final softhangup of all DAHDI channels complete.
 == Unregistered channel -2
 == Unregistered channel 1
 == Unregistered channel 2
 == Unregistered channel 3
 == Unregistered channel 4
 == Unregistered channel 5
 == Unregistered channel 6
 == Unregistered channel 7
 == Unregistered channel 8
 == Unregistered channel 9
 == Unregistered channel 10
 == Unregistered channel 11
 == Unregistered channel 12
 == Parsing '/etc/asterisk/chan_dahdi.conf':   == Found
 == Parsing '/etc/asterisk/zapata-channels.conf':   == Found
 == Parsing '/etc/asterisk/users.conf':   == Found
   -- Reconfigured channel 1, FXS Kewlstart signalling
[Oct  1 22:09:57] WARNING[25717]: chan_dahdi.c:5681 handle_alarms: Detected alarm on channel 2: Red Alarm
   -- Reconfigured channel 2, FXS Kewlstart signalling
[Oct  1 22:09:57] WARNING[25717]: chan_dahdi.c:5681 handle_alarms: Detected alarm on channel 3: Red Alarm
   -- Reconfigured channel 3, FXS Kewlstart signalling
[Oct  1 22:09:57] WARNING[25717]: chan_dahdi.c:5681 handle_alarms: Detected alarm on channel 4: Red Alarm
   -- Reconfigured channel 4, FXS Kewlstart signalling
[Oct  1 22:09:57] WARNING[25717]: chan_dahdi.c:5681 handle_alarms: Detected alarm on channel 5: Red Alarm
   -- Reconfigured channel 5, FXS Kewlstart signalling
   -- Reconfigured channel 6, FXS Kewlstart signalling
   -- Reconfigured channel 7, FXS Kewlstart signalling
   -- Reconfigured channel 8, FXS Kewlstart signalling
   -- Reconfigured channel 9, FXO Kewlstart signalling
   -- Reconfigured channel 10, FXO Kewlstart signalling
   -- Reconfigured channel 11, FXO Kewlstart signalling
   -- Reconfigured channel 12, FXO Kewlstart signalling
   -- Automatically generated pseudo channel
[Oct  1 22:09:57] WARNING[25717]: chan_dahdi.c:16988 process_dahdi: Ignoring any changes to 'userbase' (on reload) at line 23.
[Oct  1 22:09:57] WARNING[25717]: chan_dahdi.c:16988 process_dahdi: Ignoring any changes to 'vmsecret' (on reload) at line 31.
[Oct  1 22:09:57] WARNING[25717]: chan_dahdi.c:16988 process_dahdi: Ignoring any changes to 'hassip' (on reload) at line 35.
[Oct  1 22:09:57] WARNING[25717]: chan_dahdi.c:16988 process_dahdi: Ignoring any changes to 'hasiax' (on reload) at line 39.
[Oct  1 22:09:57] WARNING[25717]: chan_dahdi.c:16988 process_dahdi: Ignoring any changes to 'hasmanager' (on reload) at line 47.
pbx*CLI> dahdi show version
DAHDI Version: SVN-branch-2.2-r7039 Echo Canceller: MG2
pbx*CLI> dahdi show status
Description                              Alarms  IRQ    bpviol CRC4   Fra Codi Options  LBO
Wildcard TDM400P REV E/F Board 5         OK      0      0      0      CAS Unk  YEL      0 db (CSU)/0-133 feet (DSX-1)
Wildcard TDM400P REV I Board 5           OK      0      0      0      CAS Unk  YEL      0 db (CSU)/0-133 feet (DSX-1)
Wildcard TDM400P REV E/F Board 5         OK      0      0      0      CAS Unk  YEL      0 db (CSU)/0-133 feet (DSX-1)
DAHDI_DUMMY/1 (source: Linux26) 1        UNCONFI 0      0      0      CAS Unk  YEL      0 db (CSU)/0-133 feet (DSX-1)
pbx*CLI> dahdi show channels
  Chan Extension  Context         Language   MOH Interpret        Blocked    State
pseudo            default                    default                         In Service
     1            boldsoft                   default                         In Service
     2            towerfax                   default                         In Service
     3            from-pstn                  default                         In Service
     4            from-pstn                  default                         In Service
     5            lawyer                     default                         In Service
     6            heegii                     default                         In Service
     7            inter                      default                         In Service
     8            tower                      default                         In Service
     9            heegii                     default                         In Service
    10            tower                      default                         In Service
    11            lawyer                     default                         In Service
    12            boldsoft                   default                         In Service
pbx*CLI> dahdi restart
Destroying channels and reloading DAHDI configuration.
      > Initial softhangup of all DAHDI channels complete.
      > Final softhangup of all DAHDI channels complete.
 == Unregistered channel -2
 == Unregistered channel 1
 == Unregistered channel 2
 == Unregistered channel 3
 == Unregistered channel 4
 == Unregistered channel 5
 == Unregistered channel 6
 == Unregistered channel 7
 == Unregistered channel 8
 == Unregistered channel 9
 == Unregistered channel 10
 == Unregistered channel 11
 == Unregistered channel 12
 == Parsing '/etc/asterisk/chan_dahdi.conf':   == Found
 == Parsing '/etc/asterisk/zapata-channels.conf':   == Found
 == Parsing '/etc/asterisk/users.conf':   == Found
   -- Reconfigured channel 1, FXS Kewlstart signalling
[Oct  1 22:10:49] WARNING[25717]: chan_dahdi.c:5681 handle_alarms: Detected alarm on channel 2: Red Alarm
   -- Reconfigured channel 2, FXS Kewlstart signalling
[Oct  1 22:10:49] WARNING[25717]: chan_dahdi.c:5681 handle_alarms: Detected alarm on channel 3: Red Alarm
   -- Reconfigured channel 3, FXS Kewlstart signalling
[Oct  1 22:10:49] WARNING[25717]: chan_dahdi.c:5681 handle_alarms: Detected alarm on channel 4: Red Alarm
   -- Reconfigured channel 4, FXS Kewlstart signalling
[Oct  1 22:10:49] WARNING[25717]: chan_dahdi.c:5681 handle_alarms: Detected alarm on channel 5: Red Alarm
   -- Reconfigured channel 5, FXS Kewlstart signalling
   -- Reconfigured channel 6, FXS Kewlstart signalling
   -- Reconfigured channel 7, FXS Kewlstart signalling
   -- Reconfigured channel 8, FXS Kewlstart signalling
   -- Reconfigured channel 9, FXO Kewlstart signalling
   -- Reconfigured channel 10, FXO Kewlstart signalling
   -- Reconfigured channel 11, FXO Kewlstart signalling
   -- Reconfigured channel 12, FXO Kewlstart signalling
   -- Automatically generated pseudo channel
[Oct  1 22:10:49] WARNING[25717]: chan_dahdi.c:16988 process_dahdi: Ignoring any changes to 'userbase' (on reload) at line 23.
[Oct  1 22:10:49] WARNING[25717]: chan_dahdi.c:16988 process_dahdi: Ignoring any changes to 'vmsecret' (on reload) at line 31.
[Oct  1 22:10:49] WARNING[25717]: chan_dahdi.c:16988 process_dahdi: Ignoring any changes to 'hassip' (on reload) at line 35.
[Oct  1 22:10:49] WARNING[25717]: chan_dahdi.c:16988 process_dahdi: Ignoring any changes to 'hasiax' (on reload) at line 39.
[Oct  1 22:10:49] WARNING[25717]: chan_dahdi.c:16988 process_dahdi: Ignoring any changes to 'hasmanager' (on reload) at line 47.

Regards,
Balgaa
Comments:By: Leif Madsen (lmadsen) 2009-09-30 09:21:44

This is probably an issue you're better off calling the Digium support people for help with (presuming you have Digium hardware).

Otherwise, please use the asterisk-users mailing list.
By: Balgansuren Batsukh (balgaa) 2009-09-30 09:43:28

Hardware is working fine with Asterisk-1.4.21 and Zaptel-1.12.1
By: Leif Madsen (lmadsen) 2009-10-01 08:40:58

Per IRC:

<d-k-t> What he has put in suggests to me that either his CLI session has broken, or chan_dahdi has died in some way prior to his attempts to query it... I'd say that at the very least, debug (or any) logging from the point it stops working would be kind of useful...
By: Balgansuren Batsukh (balgaa) 2009-10-01 23:43:23

can you suggest me compile time option for debugging?

I can do it to find out problem with dahdi.

Currently, I moved back to 1.4.21, Zaptel-1.4.12.1 because encounter problem described in 15985 too.
By: Leif Madsen (lmadsen) 2009-10-26 10:02:32

I think he just means enabling 'debug' in the logger.conf file and capturing the console output with something like 'tee'
By: Balgansuren Batsukh (balgaa) 2009-10-26 12:08:46

later i will to do debug on console.
By: Leif Madsen (lmadsen) 2009-12-21 09:37:28.000-0600

Pinging reporter prior to suspending issue.
By: Balgansuren Batsukh (balgaa) 2009-12-21 21:47:48.000-0600

I will test it later, get back to you.

Please close issue.
By: Leif Madsen (lmadsen) 2009-12-22 08:23:03.000-0600

Closed per the reporter.