On Mon, May 04, 2009 at 07:55:04PM -0500, Atlanticnynex wrote:
I don't like DAHDI anyway... even if it is just the name. Gets me
confused with DUNDi and other fail acronyms.
What's there not to like about DAHDI? It's a fun game:
Tzafrir Cohen wrote:
On Mon, May 04, 2009 at 07:55:04PM -0500, Atlanticnynex wrote:
I don't like DAHDI anyway... even if it is just the name. Gets me
confused with DUNDi and other fail acronyms.
What's there not to like about DAHDI? It's a fun game:
It doesn't support my linecard (I know
On Tue, May 05, 2009 at 10:12:54AM +0100, Thomas Kenyon wrote:
Tzafrir Cohen wrote:
What's there not to like about DAHDI?
It doesn't support my linecard (I know it's not digium's fault) so I'm
stuck using an old version of asterisk.
Which card is it?
--
Tzafrir Cohen
*resolved*
I had forgotten to load the zaptel drivers prior to the running conf wancfg.
I ended up having to go back to Zaptel, I couldn't get wanpipe to work
with DAHDI.
I don't like DAHDI anyway... even if it is just the name. Gets me
confused with DUNDi and other fail acronyms.
0_0
On Sun,
Atlanticnynex wrote:
3.4.1 was the first I tried. Gives me the same error.
Then I'd suggest that you file a bug report with Sangoma.
Doug
--
Ben Franklin quote:
Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety.
On Sun, May 3, 2009 at 6:08 AM, Doug Lytle supp...@drdos.info wrote:
Atlanticnynex wrote:
3.4.1 was the first I tried. Gives me the same error.
Then I'd suggest that you file a bug report with Sangoma.
Doug
This is probably a compilation error due to changes in DAHDI headers,
since DAHDI
Okay. I've downloaded the lastest release of DAHDI and now I get this error:
# Sangoma Wanpipe #
#Dahdi/Zaptel/SMG/TDMAPI/BOOT Configuration Script #
#
[14177.069426] dahdi: Version: 2.2.0-rc2
Are you sure you're using the latest stable release of Dahdi and not the rc?
- Noah
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or
Most likely you screwed up and just compiled dahdi release but you
still have loaded the rc dahdi kernel modules.
cat /sys/module/dahdi/version
That will tell you for sure which dahdi module version is loaded.
--
Moises Silva
Software Developer
Sangoma Technologies Inc. | 50 McIntosh Drive,
I'm trying to get my Sangoma B600 working with Asterisk 1.6.1 and DAHDI 2.2.
I've tried running ./Setup dahdi (and with --64-bit_4GB flag, running amd64)
and the compile fails with this for many versions of the driver (incl.
3.3.16, 3.3.16.22, and 3.4.1):
Building modules, stage 2.
MODPOST 1
Atlanticnynex wrote:
I'm trying to get my Sangoma B600 working with Asterisk 1.6.1 and
DAHDI 2.2.
I got the following email today:
Sangoma Linux 3.4.1 Driver Location
http://wiki.sangoma.com/wanpipe-linux-drivers
Note:
This release is the first Official Stable release based on
3.4.1 was the first I tried. Gives me the same error.
--
Doug Lytle wrote:
Atlanticnynex wrote:
I'm trying to get my Sangoma B600 working with Asterisk 1.6.1 and
DAHDI 2.2.
I got the following email today:
Sangoma Linux 3.4.1 Driver Location
12 matches
Mail list logo
