Unable to make outgoing calls using DAHDI

Asterisk Asterisk Support
1

Hi,

I am not able to make out going calls using dahdi & reliance India PRI lines. Please see below configurations and help me to resolve this problem.

Versions :
Asterisk 11.2.1
DAHDI Version: 2.6.2

etc/asterisk/chan_dahdi.conf file

[code][channels]

; include dahdi extensions defined in FreePBX
#include chan_dahdi_additional.conf

; [span_1] [span_2]
pridialplan=unknown
prilocaldialplan=unknown
group=0
signalling=pri_cpe
switchtype=euroisdn
context=from-reliancepri
channel=1-15,17-31[/code]

etc/dahdi/system.conf file

[code]# This file is parsed by the Dahdi Configurator, dahdi_cfg

Span 1: TE4/0/1 “T4XXP (PCI) Card 0 Span 1” (MASTER)

span=1,0,0,ccs,hdb3

termtype: te

bchan=1-15
dchan=16
bchan=17-31
#echocanceller=mg2,1-15,17-31
mulaw=1-15,17-31
[/code]

etc/asterisk/extension.conf file

[from-reliancepri] exten => _X.,1,NoOp(${EXTEN}) same => n,Answer() same => n,Dial(dahdi/i1/09XXXXXX466,,gwW) same => n,Hangup

logs from asterisk CLI

[code] – Accepting call from ‘9XXXXXX749’ to ‘30XXX00’ on channel 0/14, span 1
– Executing [30XXX00@from-reliancepri:1] NoOp(“DAHDI/i1/9XXXXXX749-12”, “30XXX00”) in new stack
– Executing [30XXX00@from-reliancepri:2] Dial(“DAHDI/i1/9XXXXXX749-12”, “dahdi/i1/09XXXXXX466,gwW”) in new stack
– Requested transfer capability: 0x10 - 3K1AUDIO
– Called dahdi/i1/09XXXXXX466
– Span 1: Channel 0/1 got hangup, cause 100
– Hungup ‘DAHDI/i1/09XXXXXX466-13’
== Everyone is busy/congested at this time (1:0/0/1)
– Executing [30XXX00@from-reliancepri:3] Hangup(“DAHDI/i1/9XXXXXX749-12”, “”) in new stack
== Spawn extension (from-reliancepri, 30XXX00, 3) exited non-zero on ‘DAHDI/i1/9XXXXXX749-12’
– Hungup ‘DAHDI/i1/9XXXXXX749-12’

[/code]

Thanks in advance.

Regards,
Anil

2

Cause No. 100 - Invalid information element contents.

(Probably invalid number format, e.g. the system is expecting international without the access code and you are sending local with the access code. Check the type of number code you are sending and what the supplier expects.)

3

[quote=“david55”]Cause No. 100 - Invalid information element contents.

(Probably invalid number format, e.g. the system is expecting international without the access code and you are sending local with the access code. Check the type of number code you are sending and what the supplier expects.)[/quote]

I have tried all formats to dial like
Dial(dahdi/i1/009XXXXXX466,gwW)
Dial(dahdi/i1/00919XXXXXX466,gwW)
Dial(dahdi/i1/+919XXXXXX466,gwW)
Dial(dahdi/i1/09XXXXXX466,gwW)
Dial(dahdi/i1/9XXXXXX466,gwW)

still unable to make out dial. +91 for Indian code.

4

What ISDN interface card are you using? You may find that the manufacturer will provide some support.

Also, you want to check what the TON (type of number) field is being set to.

Note that the ISDN cause code is fairly generic. It could be some other invalid value for a known field.

5

[quote=“david55”]What ISDN interface card are you using? You may find that the manufacturer will provide some support.

Also, you want to check what the TON (type of number) field is being set to.

Note that the ISDN cause code is fairly generic. It could be some other invalid value for a known field.[/quote]

we are using Digium card (Digium TE420: PCI-Express quad-port T1/E1/J1), can you provide configuration for DAHDI using Digium E1.
We tried TON using national and unknown, but still same.

6

Digium’s support for their cards is provided via digium.com/en/support/telephony-cards not via this cummunity peer support forum.

The information you will need will relate to the particular network operator and possibly even to the particular network service product they are supplying. It will not be generic to all E1 installations. (In the worst case, it may depend on to which local exchange you actually connect.)

7

Your settings in /etc/dahdi/system.conf are incorrect.
You use span=>1,0,0 …
It means that you send clocking to the Network.
At the same time, you put
signalling=pri_cpe
in /etc/asterisk/chan_dahdi.conf
Change system.conf to
span=>1,1,0…
or set
signalling=pri_net