thr3ads.net - asterisk users - [asterisk-users] 1.6.0.9: Now "Unable to create ... 'DAHDI'" [May 2009]

If this information is useful, please help other people find it:
Share via:

sean darcy

2009-May-27 14:46 UTC

[asterisk-users] 1.6.0.9: Now "Unable to create ... 'DAHDI'"

Still trying to upgrade to 1.6.0.9 for 1.4.

It worked - it worked all day yesterday, but this morning:

      -- Executing [646xxxyyyy at longdistance:1] 
Answer("SIP/172-08276a60", "") in new stack
..........
     -- Executing [646xxxyyy at longdistance:6]
Dial("SIP/172-08276a60",
""DAHDI/g2"/1646xxxyyyy") in new stack
May 27 09:56:57] WARNING[16589]: app_dial.c:1468 dial_exec_full: Unable 
to create channel of type 'DAHDI' (cause 0 - Unknown)
   == Everyone is busy/congested at this time (1:0/0/1)

dahdi seems up. I restarted. Rebooted. Now I've reverted to 1.4.

CLI> dahdi show channels
    Chan Extension  Context         Language   MOH Interpret 
Blocked    State
  pseudo            from-pstn       en         default 
        In Service
       1            from-pstn       en         default 
        In Service
       2            from-pstn       en         default 
        In Service
       3            from-pstn       en         default 
        In Service
       4            from-pstn       en         default 
        In Service
       5            from-pstn       en         default 
        In Service
       6            from-pstn       en         default 
        In Service
       7            from-pstn       en         default 
        In Service
       8            from-pstn       en         default 
        In Service

  dahdi show status
Description                              Alarms  IRQ    bpviol CRC4 
Fra Codi Options  LBO
Wildcard TE120P Card 0                   OK      1      0      0 
ESF B8ZS YEL      0 db (CSU)/0-133 feet (DSX-1)

CLI> dahdi show version
DAHDI Version: 2.1.0.4 Echo Canceller: MG2

What should I try next? Any help appreciated.

sean

Tzafrir Cohen

2009-May-27 15:14 UTC

head link

[asterisk-users] 1.6.0.9: Now "Unable to create ... 'DAHDI'"

On Wed, May 27, 2009 at 10:46:39AM -0400, sean darcy
wrote:> Still trying to upgrade to 1.6.0.9 for 1.4.
> 
> It worked - it worked all day yesterday, but this morning:
> 
>       -- Executing [646xxxyyyy at longdistance:1] 
> Answer("SIP/172-08276a60", "") in new stack
> ..........
>      -- Executing [646xxxyyy at longdistance:6]
Dial("SIP/172-08276a60",
> ""DAHDI/g2"/1646xxxyyyy") in new stack
> May 27 09:56:57] WARNING[16589]: app_dial.c:1468 dial_exec_full: Unable 
> to create channel of type 'DAHDI' (cause 0 - Unknown)
>    == Everyone is busy/congested at this time (1:0/0/1)
Is that correct?

ast_verb(2, "Everyone is busy/congested at this time (%d:%d/%d/%d)\n",
numlines, num.busy, num.congestion, num.nochan);

  We have a total of 1 channels, of which:
  - 0 are busy
  - 0 are congested
  - 1 don't exist (failed to be generated?)
> 
> dahdi seems up. I restarted. Rebooted. Now I've reverted to 1.4.
> 
> CLI> dahdi show channels
>     Chan Extension  Context         Language   MOH Interpret 
> Blocked    State
>   pseudo            from-pstn       en         default 
>         In Service
>        1            from-pstn       en         default 
>         In Service
>        2            from-pstn       en         default 
>         In Service
>        3            from-pstn       en         default 
>         In Service
>        4            from-pstn       en         default 
>         In Service
>        5            from-pstn       en         default 
>         In Service
>        6            from-pstn       en         default 
>         In Service
>        7            from-pstn       en         default 
>         In Service
>        8            from-pstn       en         default 
>         In Service
> 
>   dahdi show status
> Description                              Alarms  IRQ    bpviol CRC4 
> Fra Codi Options  LBO
> Wildcard TE120P Card 0                   OK      1      0      0 
> ESF B8ZS YEL      0 db (CSU)/0-133 feet (DSX-1)
Isn't the span in alarm?

Do the channels in group=2 have 'InAlarm: Yes' in 'dahdi show
channel NN'?

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir

Jared Smith

2009-May-27 16:20 UTC

head link

[asterisk-users] 1.6.0.9: Now "Unable to create ... 'DAHDI'"

On Wed, 2009-05-27 at 10:46 -0400, sean darcy wrote:>      -- Executing [646xxxyyy at longdistance:6]
Dial("SIP/172-08276a60",
> ""DAHDI/g2"/1646xxxyyyy") in new stack
It appears you're attempting to dial "DAHDI/g2"/1646xxxyyy instead
of
DAHDI/g2/1646xxxyyyy... Did you mean to put those extra quotes in there?


-- 
Jared Smith
Training Manager
Digium, Inc.

Mike van der Stoop

2009-May-29 16:16 UTC

head link

[asterisk-users] 1.6.0.9: Now "Unable to create ... 'DAHDI'"

sean darcy wrote:> Still trying to upgrade to 1.6.0.9 for 1.4.
>
> It worked - it worked all day yesterday, but this morning:
>
>       -- Executing [646xxxyyyy at longdistance:1] 
> Answer("SIP/172-08276a60", "") in new stack
> ..........
>      -- Executing [646xxxyyy at longdistance:6]
Dial("SIP/172-08276a60",
> ""DAHDI/g2"/1646xxxyyyy") in new stack
> May 27 09:56:57] WARNING[16589]: app_dial.c:1468 dial_exec_full: Unable 
> to create channel of type 'DAHDI' (cause 0 - Unknown)
>    == Everyone is busy/congested at this time (1:0/0/1)
>
> dahdi seems up. I restarted. Rebooted. Now I've reverted to 1.4.
>
> CLI> dahdi show channels
>     Chan Extension  Context         Language   MOH Interpret 
> Blocked    State
>   pseudo            from-pstn       en         default 
>         In Service
>        1            from-pstn       en         default 
>         In Service
>        2            from-pstn       en         default 
>         In Service
>        3            from-pstn       en         default 
>         In Service
>        4            from-pstn       en         default 
>         In Service
>        5            from-pstn       en         default 
>         In Service
>        6            from-pstn       en         default 
>         In Service
>        7            from-pstn       en         default 
>         In Service
>        8            from-pstn       en         default 
>         In Service
>
>   dahdi show status
> Description                              Alarms  IRQ    bpviol CRC4 
> Fra Codi Options  LBO
> Wildcard TE120P Card 0                   OK      1      0      0 
> ESF B8ZS YEL      0 db (CSU)/0-133 feet (DSX-1)
>
> CLI> dahdi show version
> DAHDI Version: 2.1.0.4 Echo Canceller: MG2
>
> What should I try next? Any help appreciated.
>
> sean
>
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>   I've had the same issue with 1.6.0.9, if you can dial in, then dial out 
then you have the same problem.  I turned off hardware DTMF and it works 
so far.
The issue may be https://issues.asterisk.org/view.php?id=14761.

Regards,

Mike v

Reasonably Related Threads

Search for more possibly parallel threads

asterisk users - May 2009 - 1.6.0.9: Now "Unable to create ... 'DAHDI'"

[asterisk-users] 1.6.0.9: Now "Unable to create ... 'DAHDI'"

[asterisk-users] 1.6.0.9: Now "Unable to create ... 'DAHDI'"

[asterisk-users] 1.6.0.9: Now "Unable to create ... 'DAHDI'"

[asterisk-users] 1.6.0.9: Now "Unable to create ... 'DAHDI'"

Reasonably Related Threads