Tom,
The firmware should be in /lib/firmware. Other dahdi firmware is in
that location. Is it possible that the 0.7.0 release had it, but 0.7.1
does not?
Darrick
Tom Chadwin wrote:
> Exactly. Can anyone find where vpmadt032.bin (or whatever) should live
> in a 2.2.1 install? Does anyone el
Exactly. Can anyone find where vpmadt032.bin (or whatever) should live
in a 2.2.1 install? Does anyone else have this hw module?
Tom
On 7 Apr 2010, at 22:24, Darrick Hartman
wrote:
> Lonnie,
>
> He has a hardware echo canceller. Tom does not need to specify an
> echo
> canceller in the
Lonnie,
He has a hardware echo canceller. Tom does not need to specify an echo
canceller in the system.conf file when using a hardware EC. It is
entirely possible that the EC is part of the cause, especially if the
firmware files are not there.
Darrick
Lonnie Abelbeck wrote:
> On Apr 7, 201
On Apr 7, 2010, at 9:45 AM, Tom Chadwin wrote:
> You are getting an explicit timing-related error, but I don't seem to. For
> info, here are my DAHDI configs:
>
> ingrampbx ~ # cat /mnt/kd/dahdi/system.conf
> fxsks=1-2
> loadzone=uk
> defaultzone=uk
>
Tom,
Shouldn't you have "echocanceller" d
On Apr 7, 2010, at 1:05 PM, Michael Keuter wrote:
>> For fun, try "modprobe dahdi_dummy" then "service asterisk start" as
>> Michael suggested, and see if asterisk starts.
>>
>> Lonnie
>
> BTW: How can I setup multiple modules in DAHDIMODS?
> I need "zaphfc dahdi_transcode dahdi_dummy" and in
>On Apr 7, 2010, at 3:42 AM, Tom Chadwin wrote:
>
>> Hello all
>>
>> A major issue with 0.7.1 seems to have transpired. I upgraded six or so
>> boxes last week, two of which use DAHDI. Asterisk seems to have failed to
>> run. When I try to start it from the command line, I get:
>>
>> [Apr 7 0
Physically? I'd have to drive 60 miles to answer that question. Obviously,
since it's hardware, I've got no easy way to disable it in the config. I
suppose I could ditch the VPMADT032 firmware file, though I don't see it in
/lib/firmware any more. Is it no longer in userspace?
Tom
> -Origi
Just to narrow this down, what happens if you pull the echo module off
the card?
On 04/07/2010 12:15 PM, Tom Chadwin wrote:
>>> A major issue with 0.7.1 seems to have transpired. I
>> upgraded six or
>>> so boxes last week, two of which use DAHDI. Asterisk seems to have
>>> failed to run. When I
> > A major issue with 0.7.1 seems to have transpired. I
> upgraded six or
> > so boxes last week, two of which use DAHDI. Asterisk seems to have
> > failed to run. When I try to start it from the command line, I get:
> >
> > [Apr 7 09:40:18] ERROR[2705]: asterisk.c:3099 main: Asterisk has
>
On Apr 7, 2010, at 3:42 AM, Tom Chadwin wrote:
> Hello all
>
> A major issue with 0.7.1 seems to have transpired. I upgraded six or so
> boxes last week, two of which use DAHDI. Asterisk seems to have failed to
> run. When I try to start it from the command line, I get:
>
> [Apr 7 09:40:18] ER
Happy to try a 2.2.1.1 image. I've added notes to:
https://issues.asterisk.org/view.php?id=16814
Any opinion from anyone who, you know, has the faintest idea of what they're
talking about, as to whether this could be the same issue?
Tom
> -Original Message-
> From: Darrick Hartman [ma
On 04/07/2010 10:39 AM, Darrick Hartman wrote:
> On 04/07/2010 09:50 AM, Tom Chadwin wrote:
>> So it's evidently a DAHDI 2.2.1 issue. But what?
>>
>> Tom
>
> 2.2.1.1 may
>
(...cause you to press send before finishing writing the email)
Anyway, we can bump dahdi to 2.2.1.1 and build a test image
On 04/07/2010 09:50 AM, Tom Chadwin wrote:
> Oh, and reverting to 0.7.0 with no changes to dahdi/system.conf or
> chan_dahdi.conf brings the boxes back up. dmesg here gives:
>
> dahdi: Telephony Interface Registered on major 196
> dahdi: Version: 2.2.0.2
> Port 1: Installed -- AUTO FXO (FCC mode)
>
Oh, and reverting to 0.7.0 with no changes to dahdi/system.conf or
chan_dahdi.conf brings the boxes back up. dmesg here gives:
dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.2.0.2
Port 1: Installed -- AUTO FXO (FCC mode)
wctdm24xxp0: Missed interrupt. Increasing latency to 4
You are getting an explicit timing-related error, but I don't seem to. For
info, here are my DAHDI configs:
ingrampbx ~ # cat /mnt/kd/dahdi/system.conf
fxsks=1-2
loadzone=uk
defaultzone=uk
ingrampbx ~ # cat /mnt/kd/asterisk/chan_dahdi.conf
; snipping a lot of content here...
usecallerid=yes
hid
>Hello all
>
>A major issue with 0.7.1 seems to have transpired. I upgraded six or so
>boxes last week, two of which use DAHDI. Asterisk seems to have failed to
>run. When I try to start it from the command line, I get:
>
>[Apr 7 09:40:18] ERROR[2705]: asterisk.c:3099 main: Asterisk has detected a
Hi Darrick
They both have TDM410s (plus hw e/c), using wctdm24xxp. Is there anything I
should check? Looking around this morning, I can find two possibilities:
1. Config is wrong - is there any way in which a DAHDI config which worked
in 0.7.0 would crash Asterisk out in 0.7.1? Did 0.7.1 bump DAH
Tom,
I have several 0.7.1 boxes running DAHDI (mostly with Rhino cards).
What cards are you using?
Darrick
On 04/07/2010 03:42 AM, Tom Chadwin wrote:
> Hello all
>
> A major issue with 0.7.1 seems to have transpired. I upgraded six or so
> boxes last week, two of which use DAHDI. Asterisk seems
Hello all
A major issue with 0.7.1 seems to have transpired. I upgraded six or so
boxes last week, two of which use DAHDI. Asterisk seems to have failed to
run. When I try to start it from the command line, I get:
[Apr 7 09:40:18] ERROR[2705]: asterisk.c:3099 main: Asterisk has detected a
proble
19 matches
Mail list logo
