similar to: convert zaptel to dahdi?

We recently updated our Asterisk (1.4.24) box from Zaptel (1.4.12.1) to Dahdi (2.1.0.4). Everything seemed to go smooth with the exception of meetme. Meetme seems to not be able to find a zap channel for conferencing. We use voice introductions in our conference bridge and it seems to break that feature. The error from the console is.... # app_meetme.c:2593 find_conf: No Zap channel available for

Is there a way to busy out a Zap channel? I have a customer who is having problems with a line connected to a TDM800 card and we would like to busy out that line. Since that line is the head of the hunt group I cannot simply disable that channel, I need to busy the line so calls will come over the other lines. -- ?Telecomunicaciones Abiertas de M?xico S.A. de C.V. Carlos Ch?vez Prats Director

Hello, I am installing dahdi on a machine lspci 00:00.0 Host bridge: Intel Corporation 3200/3210 Chipset DRAM Controller (rev 01) 00:01.0 PCI bridge: Intel Corporation 3200/3210 Chipset Host-Primary PCI Express Bridge (rev 01) 00:06.0 PCI bridge: Intel Corporation 3210 Chipset Host-Secondary PCI Express Bridge (rev 01) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI

lspci | grep Digium 03:05.0 Ethernet controller: Digium, Inc. Wildcard TE122 single-span T1/E1/J1 card (rev 11) dahdi_scan So I have a card in a box - lspci shows it... dahdi_scan reports nothing. Is my card dead? Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello, I am missing any description of zaptel/DAHDI alarms. The TE200 series user manual contains only a description of LEDs states. These alarms states are visible in zttool/dahditool or in astersick CLI (zap show status) and I wonder what is the real meaning of these alarms for E1 channel. Possible alarm states (based on zaptel.h 1.2): 1. No alarms 2. Recovering from alarm 3. In loopback

Hi, I have a tdm22b (2 fxs / 2 fxo) When Asterisk is just started, outbound calls routing to fxo port, do not working with error: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) Inbound calls to fxo port work fine. After first inbound call, the outbound calls starts working. CentOS 5.4 asterisk 1.6.0.21-1 dahdi 2.2.1.-1 Can anybody help me to identify what is the

I have a TDM800 that is installed and working. (TDM800 + 2 X QUAD FXO). Zttool says it is configured, ok, and there are no issues. Ztcfg -vvv shows that all the channels are configured. Zap show channels in the CLI show all 8 channels configured as they are supposed to be. When I plug in a pots line from the telco and make a call to that line, asterisk does not respond. (No Starting

Hi, I have a problem with polarity reverse this my dahdi config [channels] context=default usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes canpark=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes relaxdtmf=yes rxgain=0.0 txgain=0.0 group=1 callgroup=1 pickupgroup=1

I have recently built a single-T1 Asterisk box using an HP DL120G6 with a Digium TE122 card. I was finding that I was getting missed interrupts on the TE122, causing the driver to report that it was increasing latency. It kept doing this until the T1 did not work reliably. I tried my usual procedure of disabling the USB subsystem in the BIOS (or so I thought), but I found that the USB drivers

*Problem I want to solve:* We have 3 sites: A, B, and C. Network admins should have access to all three. (this works as-is). Desktop support should only have access to their site. (Tech A to site A, Tech B to site B, Tech C to site C). *How I think I can do it:* Working with keys? Admin's public key will be on all the client machines, and thus, the client machines will always

I have setup a asterisk with freepbx, a TE122 and i have an ISDN. My problem now is that callers are experiencing echo. checked on dmesg i saw this: # dmesg -c dahdi: Disabled echo canceller NLP because of CED rx detected on channel 2 i searched google but found no soolution and i have no idea what that error means. below are other details that might be of value. # dahdi_hardware

Hello, I have previously open a topic on the mailing list about deadlocking on Asterisk 1.2.35. After upgrading to 1.4.29.1 we still experienced the same problem : Mar 5 12:05:56] DEBUG[8647] channel.c: Avoiding initial deadlock for channel '0xb7689840' [Mar 5 12:06:41] DEBUG[7130] channel.c: Avoiding deadlock for channel '0xb7c04788' [Mar 5 12:06:41] DEBUG[7130]

Does anyone have an (overhead) paging system that they like that works with SIP? We've got a client with an old paging system that (supposedly) just takes an rj11 POTS connection, but when we put an SPA Cisco adapter on it, it doesn't auto-answer the call, so paging never happens. [cid:image001.png at 01D4DFF6.9C1F1AA0] Michael J. Munger, dCAP, MCPS, MCNPS, MBSS Microsoft Certified

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

You need more than an ATA. You need something with an FSO and FXO. I've used Linksys/SPA3102-3.3.6 and been happy with it. From: asterisk-users <asterisk-users-bounces at lists.digium.com> On Behalf Of Sebastian Nielsen Sent: Thursday, March 21, 2019 3:01 PM To: 'Asterisk Users Mailing List - Non-Commercial Discussion' <asterisk-users at lists.digium.com> Subject: Re:

Dear All, How can we know the On board supports echo cancellation I have *Digium, Inc. Wildcard TE410P quad-span T1/E1/J1 card 3.3V (rev 02)*board all working fine but sometimes i got echo when user are calling a PRI. is there any way to know on board echo cancellation . regards Dhaval -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I have just recently been using DAHDI, and I wanted to know how to monitor capacity. Let's say I have two DS1 (23 channels) coming in, one for Florida (let's say) and one for New York. How can I get a reading of how many channels of each T1 port is being used at any given moment? Ideally, have two values, one for each T1. dahdi show channels doesn't show outgoing

Problem: I have four networks, A, B, C, and D Networks B, C, and D should not be able to see each other. Network A should be able to see all of them. A - 172.16.1.1/24 B - 172.16.2.1/24 C - 172.16.3.1/24 D - 172.16.0.1/24 For host machine X, which is at 172.16.1.100/24 (network A), I added a route for it to ping a machine (Y) on the network B:     ip route add 172.16.2.0/24 via

Hello I was editing files manually, and noticed that if I include the familiar "fxsks=1" in /etc/dahdi/system.conf, Dahdi fails loading: ===================== # cat /etc/dahdi/system.conf loadzone = fr defaultzone = fr fxsks=1 ===================== # /etc/init.d/dahdi start Loading DAHDI hardware modules: wctdm: [ OK ] /usr/share/dahdi/waitfor_xpds: Missing

I am in the process of buying a TDM800 card from Yeastar ( http://www.yeastar.com/products.asp?TypeName=TDM800%20PCI%20Card&cTypeName=1 ) Any one has tested this cards? How reliable are them? I am specially interested in the FXO/FXS module. -- Gustavo Felisberto (HumpBack) Web: http://dev.gentoo.org/~humpback Blog: http://blog.felisberto.net/ ------------ It's most certainly GNU/Linux,