No outgoing calls on B410P

[kyanmedia]

Hi

I am having a problem getting outgoing calls working using a B140P card and Asterisk 1.6.1.8. Any help would be much appriciated.

I get the following in the cli:

-- Executing [s@macro-dialout-trunk:19] Dial("SIP/201-b6042758", "ZAP/g1/0XXXXXXXX,300,") in new stack

== Everyone is busy/congested at this time (1:0/0/1)
– Executing [s@macro-dialout-trunk:20] Goto(“SIP/201-b6042758”, “s-CHANUNAVAIL,1”) in new stack
– Goto (macro-dialout-trunk,s-CHANUNAVAIL,1)
– Executing [s-CHANUNAVAIL@macro-dialout-trunk:1] GotoIf(“SIP/201-b6042758”, “1?noreport”) in new stack
– Goto (macro-dialout-trunk,s-CHANUNAVAIL,3)
– Executing [s-CHANUNAVAIL@macro-dialout-trunk:3] NoOp(“SIP/201-b6042758”, “TRUNK Dial failed due to CHANUNAVAIL (hangupcause: 66) - failing through to other trunks”) in new stack
– Executing [90XXXXXXXX@from-internal:5] Macro(“SIP/201-b6042758”, “outisbusy,”) in new stack

Incoming and internal call are working fine. I have configured DAHDI and all seems fine:

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

pandora*CLI> dahdi show status
Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO
B4XXP (PCI) Card 0 Span 1 OK 0 0 0 CCS AMI YEL 0 db (CSU)/0-133 feet (DSX-1)
B4XXP (PCI) Card 0 Span 2 OK 0 0 0 CCS AMI YEL 0 db (CSU)/0-133 feet (DSX-1)
B4XXP (PCI) Card 0 Span 3 RED 0 0 0 CAS Unk YEL 0 db (CSU)/0-133 feet (DSX-1)
B4XXP (PCI) Card 0 Span 4 RED 0 0 0 CAS Unk YEL 0 db (CSU)/0-133 feet (DSX-1)

/etc/dahdi/system.conf

loadzone = uk
defaultzone = uk

span = 1,1,0,ccs,ami
bchan = 1,2
hardhdlc = 3

span = 2,0,0,ccs,ami
bchan = 4,5
hardhdlc = 6

/etc/asterisk/chan_dahdi.conf

[channels]
language=en

signalling = bri_cpe
switchtype = euroisdn
group = 1
;context = incoming
context = from-pstn
echocancel = yes
channel => 1,2,4,5

Thanks
Nick

[kyanmedia]

Fixed it, trunk was set up as ZAP not DAHDI

[system]

hello,
how do you resolved ?
i’m stuck in the same problem. can you plaese post your config ?
Best regards

[kyanmedia]

The issue was due to my trunk being set up as a ZAP trunk instead of a DAHDI trunk. I’m using FreePBX so removing the ZAP trunk and replacing it with a custom one which was set up to use DAHDI fixed the issue.

The trunk I created looked like this: DAHDI/g1/$OUTNUM$

Hope this helps