Posted: Wed May 27, 2009 1:51 pm Post subject: [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@longdistance:1]
Answer("SIP/172-08276a60", "") in new stack
..........
-- Executing [646xxxyyy@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 --
Posted: Wed May 27, 2009 2:19 pm Post subject: [asterisk-users] 1.6.0.9: Now "Unable to create ... 'DAHDI'"
On Wed, May 27, 2009 at 10:46:39AM -0400, sean darcy wrote:
Quote:
Still trying to upgrade to 1.6.0.9 for 1.4.
It worked - it worked all day yesterday, but this morning:
-- Executing [646xxxyyyy@longdistance:1]
Answer("SIP/172-08276a60", "") in new stack
..........
-- Executing [646xxxyyy@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?)
Quote:
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'?
Posted: Wed May 27, 2009 3:58 pm Post subject: [asterisk-users] 1.6.0.9: Now "Unable to create ... 'DAHDI'"
Jared Smith wrote:
Quote:
On Wed, 2009-05-27 at 10:46 -0400, sean darcy wrote:
> -- Executing [646xxxyyy@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?
Of course not! They were off in a definition in extensions.ael( which
seems to override the definitions in extensions.conf, BTW) TRUNK
="DAHDI/g2" . Commented out the extensions.ael TRUNK definition, and
we're good to go.
Thanks for the great eyes. I owe you a beer, at the least.
sean
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
Posted: Fri May 29, 2009 3:23 pm Post subject: [asterisk-users] 1.6.0.9: Now "Unable to create ... 'DAHDI'"
sean darcy wrote:
Quote:
Still trying to upgrade to 1.6.0.9 for 1.4.
It worked - it worked all day yesterday, but this morning:
-- Executing [646xxxyyyy@longdistance:1]
Answer("SIP/172-08276a60", "") in new stack
..........
-- Executing [646xxxyyy@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 --
Posted: Fri May 29, 2009 4:05 pm Post subject: [asterisk-users] 1.6.0.9: Now "Unable to create ... 'DAHDI'"
On Fri, May 29, 2009 at 12:16:55PM -0400, Mike van der Stoop wrote:
Quote:
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.
Are you sure? I thought you had an issue with Asterisk 1.6.1 . The
"hardware DTMF mute" issue is not present in 1.6.0.
On Fri, May 29, 2009 at 12:16:55PM -0400, Mike van der Stoop wrote:
> 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.
>
Are you sure? I thought you had an issue with Asterisk 1.6.1 . The
"hardware DTMF mute" issue is not present in 1.6.0.
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
