Unable to make outgoing call using DAHDI

Get help with installing, upgrading and running Asterisk.

Moderators: muppetmaster, Moderator, Support

Unable to make outgoing call using DAHDI

Postby harish » Wed Nov 19, 2008 5:50 pm

Hi,

I upgraded to Asterisk-1.6.0.1 and DAHDI-2.0.0. Outgoing calls via DAHDI trunk fails with the following error.
    -- Executing [9123456789@numberplan-custom-1:1] Macro("SIP/160-002113d0", "trunkdial,DAHDI
    /g1/123456789") in new stack
    -- Executing [s@macro-trunkdial:1] Set("SIP/160-002113d0", "CALLERID(all)=") in new stack
    -- Executing [s@macro-trunkdial:2] Dial("SIP/160-002113d0", "DAHDI/g1/123456789,,wW") in n
    ew stack
    WARNING[1765]: app_dial.c:1450 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 34 - Circuit/channel congestion)
    == Everyone is busy/congested at this time (1:0/1/0)
Asterisk is able to recognize the DAHDI channels properly.
    CLI> dahdi show channels
    Chan Extension Context Language MOH Interpret Blocked State
    pseudo default default In Service
    1 default default In Service
    2 default default In Service


Thanks in advance.

Harish
harish
Newsterisk
 
Posts: 16
Joined: Thu Dec 21, 2006 10:56 pm

Postby avelino » Sat Dec 27, 2008 9:57 am

Hi.

I am getting the same error with the B410P PCI card. Have you found the solution?


Thank you very much.
avelino
Newsterisk
 
Posts: 1
Joined: Sat Dec 27, 2008 9:53 am

Postby angler » Sun Dec 28, 2008 12:41 am

What does "dahdi show channel 1" say? Also if PRI what does "pri show span 1" say? I suspect that the channel/circuit is in alarm.
angler
Asterisk Freak
 
Posts: 576
Joined: Thu Dec 21, 2006 10:56 pm

Postby pmlco » Sun Dec 28, 2008 7:23 am

Same problem, which seems to have started after upgrading to dahdi 2.1.0.3 - I can clear the problem by physically unplugging and reconnecting the telephone line.

-- Executing [17005554141@phones:1] Dial("SIP/61-09adb688", "DAHDI/1/17005554141,60,r") in new stack
[Dec 28 08:18:04] WARNING[3803]: app_dial.c:1502 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0 - Unknown)
== Everyone is busy/congested at this time (1:0/0/1)
-- Executing [17005554141@phones:2] Hangup("SIP/61-09adb688", "") in new stack
== Spawn extension (phones, 17005554141, 2) exited non-zero on 'SIP/61-09adb688'

pbx*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret Blocked State
pseudo default default In Service
1 from-pstn default In Service
pbx*CLI> dahdi show channel 1
Channel: 1
File Descriptor: 10
Span: 1>
Extension:
Dialing: no
Context: from-pstn
Caller ID:
Calling TON: 0
Caller ID name:
Mailbox: none
Destroy: 0
InAlarm: 0
Signalling Type: FXS Kewlstart
Radio: 0
Owner: <None>
Real: <None>
Callwait: <None>
Threeway: <None>
Confno: -1
Propagated Conference: -1
Real in conference: 0
DSP: no>
Busy Detection: yes
Busy Count: 5
Busy Pattern: 0,0
TDD: no>
Relax DTMF: no
Dialing/CallwaitCAS: 0/0
Default law: ulaw
Fax Handled: no
Pulse phone: no
DND: no>
Echo Cancellation:
pbx*CLI>128 taps
pbx*CLI>(unless TDM bridged) currently OFF
Actual Confinfo: Num/0, Mode/0x0000
Actual Confmute: No
Hookstate (FXS only): Onhook
pmlco
Oldsterisk
 
Posts: 232
Joined: Sun Apr 06, 2008 3:56 am

Postby angler » Sun Dec 28, 2008 5:28 pm

What version of Zaptel/Dahdi where you using before where this didn't happen? It looks like a possible bug.
angler
Asterisk Freak
 
Posts: 576
Joined: Thu Dec 21, 2006 10:56 pm

Postby pmlco » Mon Dec 29, 2008 10:06 am

What version of Zaptel/Dahdi where you using before where this didn't happen? It looks like a possible bug.


I don't wish to hijack the thread, so if you think I have a different problem I'll start another one. I didn't have this problem with dahdi linux/tools 2.0.0.


Ian
pmlco
Oldsterisk
 
Posts: 232
Joined: Sun Apr 06, 2008 3:56 am


Return to Asterisk Support

Who is online

Users browsing this forum: No registered users and 1 guest