* You are viewing Posts Tagged ‘Dahdi’

DAHDI Loading Issue On Asterisk

Try starting Asterisk with the -f option. It will NOT fork into the background so you will see all messages on startup (including any that might not end up in the log file). Search for DAHDI errors which will likely be there.

Also, if you configure everything and start DAHDI but don’t start Asterisk and run “dahdi_tool”, is it showing you the circuits in an “OK” state?

Josh

Archlinux Dahdi Start Script

I asked a similar question yesterday but unfortunately I somehow got disconnected from this group and I may have missed a response.

Wanting a systemd start script for dahdi for archlinux. The install does not seem to make one. Has anyone created one or is there a way to create one from the make config scripts? I really don’t need to load any modules other than dahdi itself for my application so I guess it oculd be as simple as ‘modprobe dahdi’ for the load.

Also I have not built asterisk yet in archlinux. Does it create a systemd script with its make config?

Possible Dahdi Compile Problem

I am having problems with system crashes in a dahdi/asterisk compile.

Dahdi + Dlink Du128ta

hello everyone,


I do have a usb ISDN modem that I would like to make it work with dahdi. is it possible?
I am running debian 7, with dahdi 2.9, asterisk 11.8
dahdi cannot find it at the moment, unless there is something else to be done.

DAHDI Tor2 Trouble On Intel Atom (D510) ?

E911 Signalling

Hi,



We’ve got a dedicated T1 with two trunks running into our ILECs selective router for 911. Split out of the T1 into two MF CAMA trunks on ILEC side.



I’m trying to use asterisks e911 signaling, but I’m having trouble with the dial command. (== Everyone is busy/congested at this time (1:1/0/0))



I’m missing something and I’m thinking it has to do with the hookstate of the dahdi channel.



If anyone has a similar situation and want to provide some guidance, I’d sure appreciate it.



Thanks!



Adam





Here’s my config:



DAHDI version 2.8.0.1



[root@e911 dahdi]# dahdi_hardware

pci:0000:02:01.0 wct1xxp+ e159:0001 Digium Wildcard T100P T1/PRI
or E100P E1/PRA Board



e911*CLI> core show version

Asterisk 11.7.0 built by root @ e911 on a x86_64 running Linux on
2014-01-28 15:50:19 UTC



/etc/dahdi/system.conf

span=1,1,0,esf,b8zs

e&m=1-2



/etc/asterisk/chan_dahdi.conf



[channels]

group=1

signalling=e911

channel=>1-2



/etc/asterisk/extensions.conf

[InFromSIP]

exten => s,1,dial(DAHDI/1/${CALLERID(num)})



e911*CLI> dahdi show status

Description Alarms IRQ bpviol CRC
Fra Codi Options LBO

Digium Wildcard T100P T1/PRI Card 0 OK 0 0 0
ESF B8ZS 0 db (CSU)/0-133 feet (DSX-1)



e911*CLI> dahdi show channels

Chan Extension Context Language MOH Interpret Blocked State Description

pseudo default default In Service

1 public default In Service

2 public default In Service



e911*CLI> dahdi show channel 1

Channel: 1

Description:

File Descriptor: 7

Span: 1

Extension:

Dialing: no

Context: public

Caller ID:

Calling TON: 0

Caller ID name:

Mailbox: none

Destroy: 0

InAlarm: 0

Signalling Type: E911 (MF)

Radio: 0

Owner:

Real:

Callwait:

Threeway:

Confno: -1

Propagated Conference: -1

Real in conference: 0

DSP: no

Busy Detection: no

TDD: no

Relax DTMF: no

Dialing/CallwaitCAS: 0/0

Default law: ulaw

Fax Handled: no

Pulse phone: no

Gains (RX/TX): 0.00/0.00

Dynamic Range Compression (RX/TX): 0.00/0.00

DND: no

Echo Cancellation:

128 taps

currently OFF

Wait for dialtone: 0ms

Actual Confinfo: Num/0, Mode/0×0000

Actual Confmute: No

Hookstate (FXS only): Offhook











Here’s a debug from a 911 call.



[Jan 31 11:29:53] DEBUG[9876][C-00000005]: pbx.c:4890
pbx_extension_helper: Launching ‘Dial’

— Executing [s@InFromSIP:1] Dial(“SIP/SIP-00000005″,
“DAHDI/1/2177772001″) in new stack

[Jan 31 11:29:53] DEBUG[9876][C-00000005]: sig_analog.c:820
analog_available: analog_available 1

[Jan 31 11:29:53] DEBUG[9876][C-00000005]: sig_analog.c:845
analog_available: Channel 1 off hook, can’t use

[Jan 31 11:29:53] WARNING[9876][C-00000005]: app_dial.c:2437
dial_exec_full: Unable to create channel of type ‘DAHDI’ (cause 17 -
User busy)

== Everyone is busy/congested at this time (1:1/0/0)

[Jan 31 11:29:53] DEBUG[9876][C-00000005]: app_dial.c:3100
dial_exec_full: Exiting with DIALSTATUS=BUSY.

— Auto fallthrough, channel ‘SIP/SIP-00000005′ status is ‘BUSY’