Anyone? could Tom's Sangoma issue be a wanpipe - DAHDI issue, since 0.7 is
built using DAHDI ?
Tom, possibly your wanpipe1.conf needs to be changed reconfigured for DAHDI ?
0.7 uses wanpipe version 3.4.4
Lonnie
On Nov 14, 2009, at 11:26 PM, Darrick Hartman wrote:
Tom,
Do you happen to
Hi devs,
can someone please update the www.astlinux.org website, mentioning
that 0.6.8 is released, but only available via System Firmware
Upgrade. This could be also noted as news at Sourceforge project
site.
What about making more promotion for Astlinux in general:
E.g. links at the
All,
This is the first time I've upgraded AstLinux from the GUI. Wow! That's
really slick.
I'm noticing only one little problem, the following error is reported under
Active Channels:
The manager.conf file does not have the [webinterface] user defined properly.
The webinterface section of
Darrick,
I have reverted back to 0.6.8 for the moment, so there is no sense of urgency
at this point. While I don't have a spare Sangoma system available for testing
I'm comfortable allowing one of the core developers ssh access when convenient.
-tm
-Original Message-
From: Darrick
This may be the problem. However with my original 0.6 system I needed to
prepare the wanpipe1.conf file off line because wancfg wouldn't run with
astlinux. The sangoma site says to run /usr/sbin/wancfg_dahdi, will I have the
same problems with wancfg under 0.7, or has that problem been fixed?
As I recall wancfg requires several perl modules. The config files must
be hand-generated as it's not feasible for us to include more than
'mini-perl' in AstLinux.
Tom Mazzotta wrote:
This may be the problem. However with my original 0.6 system I needed to
prepare the wanpipe1.conf file
I thought that was the case. One thing I did try doing was to cp my zaptel.conf
to chan_dahdi.conf. I'm sure that at least part of the problem was that I
didn't have dahdi configured. However, after doing that dahdi is still not
functional so I'm back on 0.6.8:
Nov 15 12:46:57 pbx local0.warn
Correction to my last post, I copied zapata.conf to chan_dahdi.conf.
I also tested my remote system which contains a TDM400P and it logs the same
dahdi warnings/errors, which leads me to believe that my problem has more to do
with the dahdi configuration. In doing more Google searching, it
Tom,
DAHDI files should be located as /mnt/kd/dahdi/*.conf
A reboot is required for DAHDI to see them. Also, after such files are
created, they may be edited via the Edit tab.
While this is painful, clearly DAHDI is the future, and the transition from
ZAPTEL needs to occur.
Lonnie
On Nov
I should have also added...
Define DAHDIMODS= for any modules that need to be modprob'ed, as ZAPMODS of
the past.
Use /stat/etc/dahdi/system.conf as a template to create your
/mnt/kd/dahdi/system.conf file.
Configure chan_dahdi.conf in asterisk as needed.
Lonnie
On Nov 15, 2009, at 1:51
Lonnie,
These tips helped me make a lot of progress. On the remote system with the TDM
card, dahdi show status is recognizing the card. However, my local system
with the Sangoma board is still a problem. My concern is the message wanpipe1:
Error: TDM VOICE prot not compiled reported by dmesg
This would imply that the define CONFIG_PRODUCT_WANPIPE_TDM_VOICE is not set
when wanpipe is build.
This is definitely a Philip question...
Lonnie
On Nov 15, 2009, at 3:35 PM, Tom Mazzotta wrote:
Lonnie,
These tips helped me make a lot of progress. On the remote system with the
TDM
This would imply that the define CONFIG_PRODUCT_WANPIPE_TDM_VOICE
is not set when wanpipe is build.
This is definitely a Philip question...
Lonnie
Maybe it is even more complicated:
When you look at ftp://ftp.sangoma.com/linux/current_wanpipe/ChangeLog.3.4
you'll see that Dahdi 2.2 support was
13 matches
Mail list logo
