similar to: First go at a stock 1.8 install -- where's DAHDI?

Hey, all. Just added an analog card to our dual-T1 system... and clearly I'm doing something wrong. Less interested in having the specifics pointed out than in finding out how/why certain things work. So, really, three things: * What the bloody Hell is the difference between dahdi-channels.conf and chan_dahdi.conf? (And who thought it was a good idea to have two files with,

Hey, all. I quoted a customer about $100 for some cheap SIP phones. I was planning on using the BT-102's, but he called said they look like "Princess phones," and I have to admit that he has a point. Some of the other inexpensive phones look decent, but (for example) the SPA-841's wiki entry says the remote end gets a lot of static. Since it'll be being used from a noisy

Hey, all. I'm seriously thinking about doing the VoIP thing at home. The perfect platform seemed to be the Sheeva "wall wart" (http://www.marvell.com/products/embedded_processors/developer/kirkwood/sheevaplug.jsp). It's a cute little doohicky with USB, SD-card, Ethernet, and runs on an ARM CPU. I'd like to avoid SIP to my provider, just 'cause it's always such a

Hey, all. Just wondering if there's a GUI out there -- preferably OSS, but I'll take what-have-you -- that a) can run on an Ubuntu/Debian box, and b) allows a receptionist to see what calls are in-process, and forward calls from their phone to somewhere else. Thanks! -Ken -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

I'd *really* like to be able to have a call ring three different cell phones; then, if someone answers, they have to somehow acknowledge the call for it to be directed to them. That way, if one of the phones is off, or out of range, it doesn't go straight to that phone's voicemail. Asterisk 1.4 -- though I could probably upgrade. Suggestions on how to make this happen? Thanks!

Hello, I'm experiencing some weird problems on my server: - 1) The following messages are filling up my logs: [Sep 29 08:24:59] WARNING[7077]: chan_dahdi.c:2789 pri_find_dchan: No D-channels available! Using Primary channel 140 as D-channel anyway! [Sep 29 08:24:59] WARNING[7078]: chan_dahdi.c:2789 pri_find_dchan: No D-channels available! Using Primary channel 171 as D-channel anyway!

Hey, all. I'm planning on migrating a W2K3 server to a Linux solution. It needs to be AD-aware, support ACLs, etc. This isn't something I'm doing Right Now(tm), so I can wait a little bit. A couple questions: 1) Are there any known issues with BTRFS? 2) Which version of Samba would be most appropriate for this? 3) AD integration: I've never really done it (with success); any

Greetings folks- I'm experiencing issues with a freshly installed box. When a call comes in via PRI (Sangoma AFT-A104), I see this in my logs: [Dec 15 14:26:10] WARNING[23546] chan_dahdi.c: Unable to enable echo cancellation on channel 12 (Invalid argument) [Dec 15 14:26:10] WARNING[23546] chan_dahdi.c: Unable to enable echo cancellation on channel 8 (Invalid argument) [Dec 15 14:26:10]

Hi, I'm using a two-years old installation script for the first time on a Squeeze (linux 2.6.32) platform. For an unknown reason (might be an obvious one), Dahdi can't be loaded anymore. 1. First of all, it seems /dev/dahdi content was previously (ie in Lenny) owned by asterisk:asterisk (asterisk is run as asterisk). Now it is owned by root. Any clue about this ? 2. Secondly, I changed

Some recent issues I had with hardware seem to come back to not understanding two very similarly named files: /etc/asterisk/dahdi-channels.conf /etc/asterisk/chan_dahdi.conf I've modified the chan_dahdi.conf to work now, but it would appear all I needed to do was include dahdi-channels.conf in chan_dahdi.conf and the problem would not have persisted? Is it me or is that a bit Monty Python?

after installing asterisk 1.4.23.1 and dahdi-linux-2.1.0.4 and at CLI> module load chan_dahdi.so receive the following: signalling must be specified before any channels are. CLI> Warning [4663]: chan_dahdi.c:11627 process_dahdi: Ignoring signalling Error[4663]: chan_dahdi.c:10946 build_channels: Unable to reconfigure channel '1' Error[4663]:

http://downloads.polycom.com/voice/voip/sip_sw_releases_matrix.html Howdy, all. What's the difference between "split" and "combined" firmware, which can be seen at the above link? I've googled to no avail, I'm afraid. Thanks! -Ken -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

Hi All, I must be doing something really stupid as I can't get DAHDi working in Asterisk. It is loaded and working in Linux fine. *CLI> module load chan_dahdi Unable to load module chan_dahdi Command 'module load chan_dahdi' failed. [2010-03-08 14:05:34 CST] WARNING[26926]: loader.c:393 load_dynamic_module: Error loading module 'chan_dahdi': libpri.so.1.4: cannot

Hi again! I tried to attach two VoIP-phones to my new Asterisk 13.14.1 on a Banana PI with Armbian/Debian 9. First test was to call a test service that say the time. Works! Second test was to record my voice and play it again. Works! Third test was to call the other VoIP-phone. It does NOT work... :( Then I noticed that, by starting, Asterisk says the following messages: [Feb 15 18:42:54]

Looking for some help from the UK please. I backed up all my Asterisk configuration before re-installing the server from 32 -> 64 bit. Unfortunately I did not transfer the backup to another machine!!!!! I now have a TDM400P that is not picking up the line. Can you see what I have done wrong when I have rebuilt the config please: dahdi_scan ---------- [1] active=yes alarms=OK

I have Asterisk 1.4.24 en a Digium TDM410 with EC and with 3 FXO modules. When I plug one PSTN-line into a FXO-port I am able to receive calls on this line and I can also make calls from an internal SIP-phone to the external PSTN-network. Still I am bothered about something that appears on the CLI when I do a reload chan_dahdi.so : asterisk*CLI> reload chan_dahdi.so -- Reloading module

Hi, I know it sounds weird, and this is part of the reason I have not reported that sooner. As I upgraded from 1.6.2.x to 1.8.x several months ago I am experiencing this problem. If a call is initiated from a DAHDI extension after no DAHDI extensions were used for some time, arbitrary DTMF digits are skipped and the call fails. If the call is redialed it goes through. Normally just one (1)

Hi, I've always used dahdi-genconf to just create the dahdi-channels.conf and since our PRI is fairly simple (just dump all the channels into one group) it works with dialing with dahdi/g1/(number). I'm trying to understand the file though for my own reference. It seems the file looks like this: group=0,11 context=from-pstn switchtype = national signalling = pri_cpe channel => 1-23

Seems like I post about this about once a year, when it's time to upgrade Fedora. I first got this error trying to compile a patched version of dahdi-linux-2.11.1; I noticed that there is now a dahdi-linux-complete-3.0.0+3.0.0, so I tried that one with the same result. If I compile it while running kernel-4.16.8-300.fc28.x86_64, it compiles fine, but when I try to compile it while running

Hi! I have an analog line connected to my asterisk and when I try to answer a call I get this -- Starting simple switch on 'DAHDI/7-1' -- Executing [s at from-pstn:1] Answer("DAHDI/7-1", "") in new stack -- Executing [s at from-pstn:2] Playback("DAHDI/7-1", "vm-intro") in new stack -- <DAHDI/7-1> Playing 'vm-intro' (language