search for: channeled

Displaying 20 results from an estimated 25526 matches for "channeled".

2007 May 03
2
Wildcard TE410P problem
Hello all, I'm using Wildcard TE410P card. Here is a zaptel.cfg loadzone=se defaultzone=se span=1,1,0,ccs,hdb3,crc4 bchan=1-15 dchan=16 bchan=17-31 span=2,0,0,ccs,hdb3,crc4 bchan=32-46 dchan=47 bchan=48-62 span=3,0,0,ccs,hdb3,crc4 bchan=63-77 dchan=78 bchan=79-93 span=4,0,0,ccs,hdb3,crc4 bchan=94-108 dchan=109 bchan=110-124 # ztcfg -vvv Zaptel Configuration ====================== SPAN 1:
2010 Nov 02
0
Noise while passing channel using tde205p card
Hello, I have an Asterisk box with a digium TDE205p card. The problem is that I have several "Goto(s-${DIALSTATUS}" sentences and while the call is trying to find a free channel to establish the call, I get a little noise in each "Zap/... is proceeding passing it to Zap/..." line. My configuration is: Digium card: TE205P Asterisk Version: 1.4.21.2
2008 Oct 15
0
phoniceq e400p driver for DAHDI
Hello everyone, We have an E400P Card from phoniceq.? There is a DAHDI Driver posted at: http://e400p.phoniceq.com/driver/dahdi-tor2-tormenta3-e1.tgz but, it doesn't work.? The author (martin (or marcin) pycko) says that it isn't finished. I've e-mailed martin, and he stated that he would fix the driver AFTER we order 10 more cards, not before.? I have a difficult time ordering
2005 Mar 04
2
TE110P module woes
Hi, I have been using asterisk for a couple of months now and for thee most part, I love it. However, I'm having a problem with the drivers of the Digium TE110P. I have tried both the Debian package and the CVS. I have tried several kernels, and am now at 2.6.11. This has been working before (with 2.6.8.1), but after a reboot it stopped working and I am not able to consistently make
2009 Feb 25
4
TE121 on Asterisk
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
2009 Sep 01
7
Dahdi configuraion / error
Hello I just updated the kernel, dahdi-linux and dahdi-tools Im also using now asterisk 1.4.26.1 And im still with a red light (not RED/YELLOW anymore): [root at catumbela ~]# /etc/rc.d/init.d/dahdi status ### Span 1: TE4/0/1 "T4XXP (PCI) Card 0 Span 1" (MASTER) HDB3/ RED 1 PRI CAS RED 2 PRI CAS RED 3 PRI CAS RED 4 PRI
2007 Jun 13
6
problem starting asterisk, unable to load chan_zap
Hi all, I am running asterisk 1.2.18, zaptel 1.2.18, libpri 1.2.4. on a suse 10.2, running kernel 2.6.18.2-34-default. The zaptel drivers are loaded on boot via /etc/init.d/zaptel, but Asterisk is unable to start. It ends with the following message: [chan_zap.so] => (Zapata Telephony w/PRI) Jun 13 13:05:41 VERBOSE[3356] logger.c: == Parsing '/etc/asterisk/zapata.conf': Found
2007 Jan 04
2
[Fwd: PRI Problems]
<Correction in my zapata.conf file I used> Hey Everyone, So this is a problem I've been having for sometime now. I sent a few messages to the list with no luck. The problem is that when people dial into the Asterisk system using DID numbers, it works the first time or 2, then I get busy signals. A friend recommended I clear out the zapata and zaptel, start over, and recreate my
2004 Dec 02
4
TE110P + Asterisk
Hi, I've just got a TE110P card and installed at Asterisk. I configured zapata.conf, according to www.digium.com/index.php?menu=configuration, but the following error is happening: ... ... ... [chan_phone.so] => (Linux Telephony API Support) == Parsing '/etc/asterisk/phone.conf': Found == Registered channel type 'Phone' (Standard Linux Telephony API Driver)
2006 Jun 03
3
Sangoma A101 configuration
Im trying to install and configure sangoma ... every thing is OK but when type the command "wanrouter start" the following error apears: wan Driver not found. Thanks for any help
2006 Dec 18
2
Digium TE405P with French E1 => Red Alert
Hi anyone have a idea for debug my digium TE405P card ? My zaptel.conf: span=1,1,0,ccs,hdb3 bchan=1-15,17-31 dchan=16 loadzone = fr defaultzone = fr My Zapata.conf: [channels] language=fr context=from-E1 switchtype = euroisdn pridialplan = unknown signalling = pri_cpe usecallerid=yes hidecallerid=no callwaiting=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes
2008 Dec 11
1
DAHDI help
I was running : asterisk 1.2.24 zaptel 1.2.21 libpri 1.2.6 I remove zaptel and compiled asterisk 1.4.22 libpri 1.4.7 dahdi 2.1.0 dahdi_cfg -vvv DAHDI Tools Version - 2.1.0 DAHDI Version: 2.1.0 Echo Canceller(s): Configuration ====================== SPAN 1: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1) Channel map: Channel 01: Clear channel (Default) (Slaves: 01) Channel 02: Clear channel
2004 Dec 21
2
TE405P E1 coax cables with balun
Hi, I am new with asterisk. I am setting a Wildcard TE405P. E1s in Italy come in on a pair of RG-59 coax cables with BNC connectors. So I need an adapter/balun http://www.allcomtlc.com/al_g703n3.htm . I have It but I am not sure that It works. I have configured my asterisk in this way: zaptel.conf span=1,1,0,ccs,hdb3,crc4 dchan=16 bchan=1-15,17-31 loadzone=it defaultzone=it zapata.conf
2011 Jan 14
2
DEBUG[27654] channel.c: Avoiding deadlock for channel '0x114af2c0'
Hello list, today I experienced the following for the first time : [Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock for channel '0x114af2c0' [Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock for channel '0x114af2c0' [Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock for channel '0x114af2c0' [Jan 14 11:26:18] DEBUG[27654] channel.c:
2009 Aug 25
2
Echo
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> I recently upgraded my Asterisk system to Dahdi and now I have an echo <br> problem. <br> <br> I am running Asterisk 1.4.25 with Dahdi Complete 2.2.0, on a Digium <br> TE121B PCI express
2020 Sep 06
0
dahdi_cfg -vvv error , PRI show spans command not found
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
2005 Oct 06
3
WCFXO and T1 PRI Card?
Can I have a TDM400 and a T100P in the same machine? I am using AAH and trying to combine two boxes. If so, can anyone tell me the proper config for zaptel.conf and zapata.conf? Thanks! Wiley -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20051006/061d9d84/attachment.htm
2010 Mar 17
7
Asterisk DIES with no trace. PLEASE HELP!
Hello my friends We are having seriously problems with our asterisk server, our versions are as follows: WANPIPE Release: 3.4.7 Asterisk 1.4.21.2 Zaptel Version: 1.4.11 libpri version: 1.4.10.2 The symptoms are very weird, the CLI stop working suddenly, a core show channels shows MANY channels FREEZED, the incoming and outgoing calls stop working, the internal calls stop working, in resume we
2007 Jan 04
0
PRI Problems
Hey Everyone, So this is a problem I've been having for sometime now. I sent a few messages to the list with no luck. The problem is that when people dial into the Asterisk system using DID numbers, it works the first time or 2, then I get busy signals. A friend recommended I clear out the zapata and zaptel, start over, and recreate my wanpipe stuff. He thought the problem was with the spans
2010 Apr 01
2
Problem with Sangoma A104 and euroisdn pri
Hi all, My problem boils down to these errors: ... Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) == Everyone is busy/congested at this time This is triggered by lines in extentions.conf such as: exten => _X.,1,Dial(ZAP/g1/${EXTEN},,W) The system is CentOS v5.2 with Asterisk 1.4.23 (druid-asterisk-1.4.23.1-2), a Sangoma A104