calls only working on first channel of each dahdi span

[frank220]

been loosing hair on this one

version 2.4-357a

build 120125-2107
supermicro xeon , sangoma a102, 32gb gam single server install

had to change from sip trunking to 2 x E1 pri isdn due to customers sip service being withdrawn

however can only get a maximum of 2 calls out in the group

I changed isdn card to a digium te220 but made no difference so have changed back to the sangoma

can call out on chan 1 and 32 no problem at all - all other channels fail as below (set it up to try to use channel 6)

-- Executing [601823432426@default:3] Dial("SIP/cc101-00000033", "DAHDI/6/60xxxxxxxx||tTor") in new stack (my mobile concealed)
[Jan 12 16:41:24] WARNING[24962]: app_dial.c:1310 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 [60xxxxxxxxx@default:4] Hangup("SIP/cc101-00000033", "") in new stack
== Spawn extension (default, 60xxxxxxxxxxx, 4) exited non-zero on 'SIP/cc101-00000033'
-- Executing [h@default:1] DeadAGI("SIP/cc101-00000033", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----CHANUNAVAIL----------") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0




chan dahdi conf

;autogenerated by /usr/sbin/wancfg_dahdi do not hand edit
;autogenrated on 2014-01-12
;Dahdi Channels Configurations
;For detailed Dahdi options, view /etc/asterisk/chan_dahdi.conf.bak

[trunkgroups]

[channels]
context=default
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
relaxdtmf=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no

;Sangoma A102 port 1 [slot:4 bus:6 span:1] <wanpipe1>
switchtype=euroisdn
context=trunkinbound
group=0
echocancel=yes
signalling=pri_cpe
channel =>1-15,17-31

;Sangoma A102 port 2 [slot:4 bus:6 span:2] <wanpipe2>
switchtype=euroisdn
context=trunkinbound
group=0
echocancel=yes
signalling=pri_cpe
channel =>32-46,48-62

pri show spans
PRI span 1/0: Provisioned, Up, Active
PRI span 2/0: Provisioned, Up, Active


mail*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret
pseudo default default
1 trunkinbound default
2 trunkinbound default
3 trunkinbound default
4 trunkinbound default
5 trunkinbound default
6 trunkinbound default
7 trunkinbound default
8 trunkinbound default
9 trunkinbound default
10 trunkinbound default
11 trunkinbound default
12 trunkinbound default
13 trunkinbound default
14 trunkinbound default
15 trunkinbound default
17 trunkinbound default
18 trunkinbound default
19 trunkinbound default
20 trunkinbound default
21 trunkinbound default
22 trunkinbound default
23 trunkinbound default
24 trunkinbound default
25 trunkinbound default
26 trunkinbound default
27 trunkinbound default
28 trunkinbound default
29 trunkinbound default
30 trunkinbound default
31 trunkinbound default
32 trunkinbound default
33 trunkinbound default
34 trunkinbound default
35 trunkinbound default
36 trunkinbound default
37 trunkinbound default
38 trunkinbound default
39 trunkinbound default
40 trunkinbound default
41 trunkinbound default
42 trunkinbound default
43 trunkinbound default
44 trunkinbound default
45 trunkinbound default
46 trunkinbound default
48 trunkinbound default
49 trunkinbound default
50 trunkinbound default
51 trunkinbound default
52 trunkinbound default
53 trunkinbound default
54 trunkinbound default
55 trunkinbound default
56 trunkinbound default
57 trunkinbound default
58 trunkinbound default
59 trunkinbound default
60 trunkinbound default
61 trunkinbound default
62 trunkinbound default




mail*CLI> dahdi show status
Description Alarms IRQ bpviol CRC4
wanpipe1 card 0 OK 0 0 0
wanpipe2 card 1 OK 0 0 0

any ideas would be useful

[williamconley]

suggest you ignore Vicidial and go with Asterisk forums OR contact the seller of the hardware (often have a tech that will talk you through asterisk configuration to avoid loss of the sale) or the PRI provider (same concept, if you can't use it they lose the customer).

AFTER you get it working in Asterisk ... vicidial will be easy.

[frank220]

cheers bill - thought id give you guys a try first
as i say it works for fine on first channel of pri span in asterisk but for everything else, disapears up its own rear
will have to get hold of telcos in the morning - that will be most of the day lost!

[williamconley]

search the net for switchtype=euroisdn and your telco to see if there are any published settings that are different. and of course be sure you're not connected to a two-channel pri (with the rest as internet). depends on how it was ordered. not all PRIs are purely telephone channels.

[frank220]

the pain of this is
its actually a sip solution by uk's british telecom
however they will not allow direct sip setup from asterisk
instead they insist on installing a ubigate ibg1004 by samsung which is isdn -> sip gateway
which then means installing a 2x e1 card in the dialler
so the eventual path is sip --> asterisk -->isdn cpe -->isdn net --> sip --->telco
(please dont have an accident laughing)

[williamconley]

so the eventual path is sip --> asterisk -->isdn cpe -->isdn net --> sip --->telco

How do you know

Code: Select all

 -->isdn net --> sip --->telco

when all you see is

Code: Select all

 sip --> asterisk -->isdn cpe

?

[frank220]

wireshark has its uses - the ibg1004 actually sits behind customer firewall in its own dmz

[williamconley]

but if you are sending via e1 to the isdn, your target is over e1 and you don't have an IP destination to prove that the ibg1004 is the destination of your e1 sending unit.

are you saying that you can see e1 packets in your isdn outbound e1 with wireshark? and they contain IP address information (public IP ones at that) instead of a private networking address (leased lines, last I knew, did not use the Internet to route packets ...?)

[striker]

Hi frank

Can you post the dialplan used to dialout via PRI.

As the error shows you lack of Channels within asterisk
and also i can see DAHDI/6/ , Are you using DAHDI/g0 or DAHDI/6 in your dialplan.

-- Executing [601823432426@default:3] Dial("SIP/cc101-00000033", "DAHDI/6/60xxxxxxxx||tTor") in new stack (my mobile concealed)
[Jan 12 16:41:24] WARNING[24962]: app_dial.c:1310 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0 - Unknown)

If you use g0 it will utilize all the channels,
if you use 6 it will use only one channel ie channel 6

you both the pri trunk channels are groupped as 0 , so use g0 or G0 or r0 or R0 in dialplan instead of DAHDI/6 use DAHDI/g0