similar to: Zap problems

Hi to all. I'm trying to use meetme on asterisk 1.4.22.1. On a debian i've compiled (as i need h323 support) openh323_v1_18_0 pwlib_v1_10_0 dahdi-linux-2.1.0.3 dahdi-tools-2.1.0.2 asterisk-1.4.22.1 All works fine, dahdi status is: asterik:/data/programmi# /etc/init.d/dahdi status ### Span 1: DAHDI_DUMMY/1 "DAHDI_DUMMY/1 (source: RTC) 1" (MASTER) asterik:/data/programmi#

Hello support am trying to install dahdi on centos 7 and am doing the make ommand and below is result any way out this You do not appear to have the sources for the 3.10.0-327.el7.x86_64 kernel installed. uname -a gives me below; Linux localhost.localdomain 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [root at localhost

I updated Asterisk to 1.6.2.7 and now the user introduction in the meetme application is no longer working: [May 27 09:26:51] WARNING[2407]: channel.c:4034 ast_request: No channel type registered for 'DAHDI' -- Created MeetMe conference 1023 for conference '800' [May 27 09:26:51] WARNING[2407]: app_meetme.c:3640 find_conf: No DAHDI channel available for conference, user

Hi Listers, I'm running 1.4.25-rc1 on opensuse 11.0 with dahdi-linux-2.1.0.3, dahdi-tools-2.1.0.2, libpri-1.4.7 and snapdsp.0.0.2. Incoming calls work fine. Outgoing calls made directly (exten => s,1,Dial(DAHDI/G1) then number work fine. The problem I have is trying to let Asterisk make the call (exten => s,1,Dial(DAHDI/G1/5551212,,r). If I use "m" (moh) the

I've got an asterisk 1.4.24 box with dahdi complete 2.1.0.3+2.1.0.2 I've got a 2 port T2XXP card attached with on T1 currently plugged in. Inbound calls work fine, but outbound fail with the rather cryptic: [May 19 17:28:07] WARNING[11360]: app_dial.c:1237 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) There are similar threads I've found on the

Hello oslec make error on RHEL 2.6.9 : Warning: could not find versions for .tmp_versions/dahdi.mod Warning: could not find versions for .tmp_versions/xpd_fxo.mod Warning: could not find versions for .tmp_versions/xpd_fxs.mod Warning: could not find versions for .tmp_versions/xpd_pri.mod Warning: could not find versions for .tmp_versions/xpp.mod Warning: could not find versions for

I installed DAHDI (2.1.0.3) on a machine with asterisk 1.4.22 and libpri 1.4.7 and I am getting the error: -- Requested transfer capability: 0x00 - SPEECH -- Called 23/317506XXXX -- Channel 0/23, span 1 got hangup, cause 99 -- Hungup 'DAHDI/23-1' on DIALING out. Calling in seems to work just fine. Seems like everything is configured fine... system.conf

Yesterday, a low-duty production server that I maintain core-dumped. At the time there were only around 2 calls going through it. The strace on the screen made it look like it was caused by Dahdi. The machine is running asterisk-1.6.0.3 dahdi-linux-2.1.0.3 dahdi-tools-2.1.0.2 asterisk-addons-1.6.0 Kernel version 2.6.28 There is a genuine TDM400P (populated witrh 2xFXO cards and 2xFXS cards.

Hi list, I install dahdi-linux successfully with the module of oslec for the echo, but when I specify it in the system.conf the echo canceller oslec it shows me errors: DAHDI_ATTACH_ECHOCAN failed on channel 4: Invalid argument (22) I see that the echo cancellers is supported: mg2, kb1, sec2, and sec because oslec is not supported?, but he has support to compile it with dahdi_linux! best

So, tweaking configs, rebuilding this and that... restarting, twiddling, it works (yeah!), but fails on re-boot to work at all. Consistently, though. I believe it comes down to this: I can call out only *after* I've received a call. So, cold boot. Then: modprobe dahdi modprobe wctc4xxp modprobe wcfxo dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.1.0.3

Hi, I was able to implement T122p one port PRI and was able to call out, but I am planning to use TE412p (includes echo cancellation) 4 port digital card (PRI), I wanted to know can asterisk support 3 four port PRI cards (12 PRI connections) with proper hardware like dual core quadcore processor and 8gb RAM in one server? Also I was planning to implement using 64 bit architecture with Asterisk:

Because of a kernel upgrade i needed to recompile DAHDI. Dahdi 2.0.0 with 2.0.1 was working ok, after the reboot and compile it doesn't start anymore. Firstly it tells me it is using /etc/zaptel.conf which is deprecated, if i remove that file it complains that this file is missing..... Secondly i get an error about a missing dev file which refers to zap (which seems strange to me because

I am using centos 4.4 ,when I am compiling zapltel using l make linux26 ,error accrued ,what s missing [root@localhost zaptel]# make linux26 grep: /include/linux/autoconf.h: No such file or directory make: *** No rule to make target `linux26'. Stop. Regards ********************************************* No employee or agent is authorized to conclude any binding

I've got a fresh FC2 install and I'm trying to get the symlinks right according to the /usr/src/zaptel/README.Linux26 instructions. I've created two symlinks: /usr/src/linux-2.6 -> /usr/src/linux-2.6.5-1.358 /lib/modules/linux-2.6 -> /lib/modules/2.6.7-1.494.2.2 When I do a "make linux26", I get a million warnings and errors with the result being: make[2]: ***

I am changing a system from zap to DAHDI. I removed everything zap. when doing the command: sh -x /etc/init.d/dahdi start, I see initlog -q -c 'modprobe wct4xxp' sh: /sbin/ztcfg: No such file or directory FATAL: Error running install command for wct4xxp doing updatedb then, locate zap returns me /var/lib/asterisk/sounds/spy-zap.gsm /usr/share/groff/1.18.1.1/font/devps/zapfdr.pfa

I'm trying to get "blind transfer" from an incoming DAHDI line to an external number to work on an * 1.6 install using a T1 from XO. The documentation is very "distributed" and incomplete, so while it's not working, it's definitely more likely my error somehow. Couple questions if anybody is out there who even knows what TBCT is. 1) Is this even

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greets all sorry for the posting but this one has me confused. I compiled Zaptel and am experiencing something strange. I followed the instructions on README.udevs to the tee, set permissions, etc. and I'm confused as to what gives. Zaptel compiled without a problem but no device was made.... [beta@staging ]# uname -a Linux xxx.xxx

Hi All trying to compile asterisk under linux kernel 2.6.6. Currently under zaptel get the following error make linux26 Link /usr/src/linux-2.6 to your kernel sources first! make: *** [linux26] Error 1 as going from the readme. is 2.6 not compatiable with asterisk and should I go back to 2.4.26. Also has anyone got the sipura 3000 working with asterisk, both fxo and the fxs ports on the

Hi all, I'm pretty new to linux and compiling modules, but I've scoured the web for help on compiling the zaptel modules from source and I get the following error... make -C SUBDIRS=/usr/src/modules/zaptel modules make: *** SUBDIRS=/usr/src/modules/zaptel: No such file or directory. Stop. make: *** [linux26] Error 2 Any ideas? /usr/src/modules/zaptel is the dir I'm

Hi, I'm having trouble compiling zaptel 1.4.4 on SUSE 10.1. I'm really only interested in getting ztdummy to work because this is a dev machine with no zaptel h/w. SUSE 10.1 is a 2.6 kernel: asterisk-dev:/home/hugh # uname -r 2.6.16.13-4-default It seems that my problem is related to autoconf.h - I cannot find that file: asterisk-dev:/home/hugh # find / -name 'autoconf.h'