similar to: Unable to create channel of type 'Zap' with ecmg2 and kernel 2.6.23

Hello, I just bought a TE121 T1/E1 card, and now trying to install it on a 1.4.23.1 asterisk with dahdi 2.1.0.4 Actually first everything went on well and i managed to see my card on dahdi. Here's the output: #asterisk# dahdi_hardware pci:0000:04:08.0 wcte12xp+ d161:8000 Wildcard TE121 and this is the scan: -------------------------- asterisk# dahdi_scan [1] active=yes alarms=RED

Hi, I configured an asterisk box with 1 Digium Wildcard TE110P T1/E1 Card 0 I setup the jumper in e1 position. my zaptel.conf : defaultzone=it loadzone=it #gestione PRI span=1,0,0,ccs,hdb3,crc4,yellow bchan=1-15 # set this to 1-15,17-31 for E1 dchan=16 # set this to 16 for E1 bchan=17-31 # set this to 1-15,17-31 for E1 # Asterisk starts correctly, I see th 30 channels. Anyway I cannot put

I have configured /etc/asterisk/zapata.conf, but now Asterisk refuses to start: Asterisk 1.0.9, Copyright (C) 1999-2004 Digium. Written by Mark Spencer <markster@digium.com> .... [chan_zap.so] => (Zapata Telephony w/PRI) == Parsing '/etc/asterisk/zapata.conf': Found Sep 16 20:36:51 ERROR[6750]: chan_zap.c:6246 mkintf: Unable to get parameters Sep 16 20:36:51 ERROR[6750]:

All, Alright, I've looked around the internet, the voip-info.org wiki, and browsed the contents of this mailing list. While I've found a couple of scenarios that are close to this one, I haven't found one that uses my particular card (T100P). Without further delay -- I have successfully configured internal SIP services between a Snom 200 and a Windows X-Lite client and have

I have spent some time this morning trying to add an Astribank to our current Asterisk, but it failed, so I just removed the hardware, restore the config files to the original setup and started asterisk.; I could see that no Zap channels are started so I did load chan_zap.so: pbx*CLI> module load chan_zap.so [Feb 26 10:32:18] WARNING[3809]: pbx.c:2968 ast_register_application: Already have an

Hi, I have been trying to get a Wildcard TE122 card running here the last couple of days. libpri and zaptel are all installed and configured to E1 specs. The jumper on the card is on, so configured for E1 (I'm in Norway). When running zttool, I get 'Alarms: RED' on the single card installed. Other information in zttool: Current alarms: Red Alarm Sync source: Internally clocked

Hi, My asterisk server was working with a 4-FXO analog card (TDM400P). I recently added two digital cards: a TE120P (1 PRI) and a B410P (4 BRI). The B410P is still unconfigured but inserted in a PCI slot. The TE120P's jumper is set to E1 as it will connect to a commercial PBX's PRI card also configured as E1. My analog channels used to be 1-4 but since I added the new cards I changed

Hi, I am facing problem in configuring D-channel for TE120P card.I did the following things /etc/zaptel.conf span=1,1,0,ccs,hdb3 bchan=1-15,17-31 dchan=16 /etc/asterisk/zaptel.conf group=1 signalling=pri_cpe

Hi, After upgrading to DAHDI 2.4.0 from Zaptel, I noticed a lot of HDLC errors on my console: [Nov 27 01:15:09] NOTICE[2743] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [Nov 27 01:15:09] NOTICE[2743] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 These errors prevented calls from being made and received on my PRI spans. This seems

dahdi_cfg -vvv error `cut: '/sys/bus/dahdi_devices/devices/pci:0000:01:00.0/spantype': No such file or directory` PRI show spans --command not found test call not working. -- dahdi_genconf -vvv Default parameters from /etc/dahdi/genconf_parameters Generating /etc/dahdi/assigned-spans.conf cut: '/sys/bus/dahdi_devices/devices/pci:0000:01:00.0/spantype': No such file or

Still trying to upgrade to 1.6.0.9 for 1.4. It worked - it worked all day yesterday, but this morning: -- Executing [646xxxyyyy at longdistance:1] Answer("SIP/172-08276a60", "") in new stack .......... -- Executing [646xxxyyy at longdistance:6] Dial("SIP/172-08276a60", ""DAHDI/g2"/1646xxxyyyy") in new stack May 27 09:56:57]

Hello, I have a problem with zaptel. I hope you can help me. I installed and configure zaptel. ZAPTEL.CONF span=1,1,0,ccs,hdb3,crc4 bchan=1-15,17-31 dchan=16 loadzone = de defaultzone=de But the output of cat /proc/zaptel/* Span 1: WCT1/0 "Digium Wildcard TE110P T1/E1 Card 0" (MASTER) HDB3/CCS/CRC4 RECOVERING 1 WCT1/0/1 Clear (In use) RED

Hi everybody, I've connected Asterisk 1.2.5 (libpri 1.2.2, zaptel 1.2.4, Linux 2.6.13.2) to an Avaya-Tenovis PBX via a PRI/E1-line. Calls from SIP-phones via * to the PBX work fine. However, incoming calls to * only result in: -- XXX Missing handling for mandatory IE 24 (cs0, Channel Identification) XXX -- which seems to be an * problem, because a Windows-fax-machine works fine on a PRI

Hi, I'm having trouble configuring and E1 link , I know the E1 is a PRI and the switchtype is 5ess. The problem is that everytime I try to dial I got and error saying that it was unable to open the zap channel . Devices are created in the /dev/zap directory and I can open them with a cat /dev/zap/1. I can also see the channels in /proc/zaptel/1. Thanks in advance [zaptel.conf]

I have configured /etc/asterisk/zapata.conf, but now Asterisk refuses to start: Aug 5 10:47:29 ERROR[1076842624]: chan_zap.c:5976 mkintf: Unable to get parameters Aug 5 10:47:29 ERROR[1076842624]: chan_zap.c:9478 setup_zap: Unable to register channel '1-15' Aug 5 10:47:29 WARNING[1076842624]: loader.c:328 ast_load_resource: chan_zap.so: load_module failed, returning -1 == Unregistered

Hi!I've a problem with asterisk,it doesn't start..it's stopped..I used the amportal start command and this is the result: SETTING FILE PERMISSIONS Permissions OK STARTING ASTERISK Asterisk ended with exit status 1 Asterisk died with code 1. Automatically restarting Asterisk. Asterisk ended with exit status 1 Asterisk died with code 1. Automatically restarting Asterisk.

Hello, I am having an issue whereby calls are being dropped randomly. I have an ISDN 30 E1 line going into a Wildcard TE220 (4th Gen). My Asterisk install is based on Trixbox 2.0. However, I have updated the source code to the following. The Asterisk release is asterisk-1.2.20. Zaptel release is zaptel-1.2.18. And libpri release is libpri-1.2.4. I have include an extract from the Asterisk log

> > Hi, Remove usecallingpres=yes busydetect=yes from your zapata.conf file. and the restart asterisk. Hopefully you will not faced drop call issues. Regards, Vidura Senadeera. Message: 3 > Date: Mon, 24 Sep 2007 12:29:40 +0100 > From: "Richard Young" <Richard.Young at intrintech.com> > Subject: [asterisk-users] Asterisk Dropping Calls > To:

I figured it out. The old system (Televantage 3 and 4 I think) has limited specifications on the T1. After setting up the system, I was able to send and recieve calls. I still have some work to do like figuring out faxing and a floating receptionist, but this is a nice start. ----------------------------------------------------Televantage T1 Requirements: Framing: D4 Superframe or Extended

Hi, we are still trying to properly connect a Tenovis PBX to an Asterisk server (asterisk 1.2.6, libpri 1.2.2, zaptel 1.2.5, Digium Wildcard TE110P), this time with QSIG. Calling from a Tenovis phone to a SIP phone (i.e. traditional phone -> Tenovis PBX -> QSIG -> Asterisk -> SIP phone) works with the following messages: --- Don't know what to do if second ROSE component is of