On Fri, Jan 29, 2010 at 05:48:53PM -0500, sean darcy wrote:
listu...@spamomania.co.uk wrote:
On Thu, 2010-01-28 at 23:11 -0600, Karl Fife wrote:
Appears completely resolved!
No more home-spun patches!
Thanks!
-K
It's *not* fixed here:
DAHDI Version: 2.2.1 Echo Canceller: MG2
listu...@spamomania.co.uk wrote:
On Thu, 2010-01-28 at 23:11 -0600, Karl Fife wrote:
Appears completely resolved!
No more home-spun patches!
Thanks!
-K
It's *not* fixed here:
DAHDI Version: 2.2.1 Echo Canceller: MG2
But as is depressingly the 'norm' for Asterisk it comes back to
On 30/01/10 11:48 AM, sean darcy wrote:
Sigh.
OK you don't like asterisk - sorry. Obviously some other software works
better for you. I'm glad.
Don't worry, he/she's trolling, second post like that for the day :)
Obviously has an issue with something, but rather than try and get it
sorted
I have had the exact same problem for over a year on my server sporting the
TDM800 but NOT on my server with the TE212P. Both servers run the same
version of Linux, Asterisk and DHADI.
The problem has remained consistent through all versions of DAHDI 2.0.x
through 2.2.0.2, and every version
Interesting. I had the same problem last Sept with a TDM800, DAHDI 2.2.0.2.
Shaun Ruffel of Digium pointed me to
https://issues.asterisk.org/file_download.php?file_id=22725type=bug
which fixed it for me. This fix is already in 2.2.1.
--
Barry
On Thu, Jan 28, 2010 at 07:30:57PM -0600, Karl
: [asterisk-users] Unable to create channel of type 'DAHDI'(cause
0- Unknown)
Interesting. I had the same problem last Sept with a TDM800, DAHDI
2.2.0.2.
Shaun Ruffel of Digium pointed me to
https://issues.asterisk.org/file_download.php?file_id=22725type=bug
which fixed it for me. This fix
On Thu, 2010-01-28 at 23:11 -0600, Karl Fife wrote:
Appears completely resolved!
No more home-spun patches!
Thanks!
-K
It's *not* fixed here:
DAHDI Version: 2.2.1 Echo Canceller: MG2
But as is depressingly the 'norm' for Asterisk it comes back to bitching
about hardware 'buy an expensive
The reason for this is that 1.6.0 does not support dahdi. It was a
mistake when it was listed as an included feature. The documentation
for it has been removed in 1.6.0.1. If you need dahdi you need to go
to 1.6.1.
This is documented in this changelog:
Brendan Martens wrote:
The reason for this is that 1.6.0 does not support dahdi. It was a
mistake when it was listed as an included feature. The documentation
for it has been removed in 1.6.0.1. If you need dahdi you need to go
to 1.6.1.
That is incorrect. There was one small feature
I see, Thank you for the clarification.
Brendan Martens
On Oct 10, 2008, at 9:31 AM, Kevin P. Fleming wrote:
Brendan Martens wrote:
The reason for this is that 1.6.0 does not support dahdi. It was a
mistake when it was listed as an included feature. The documentation
for it has been removed
Inbound calls on DAHDI work fine.
At some point, outbound starts working. I just cannot figure out what
the trigger is. At first, I thought the trigger was receiving at least
one inbound call. But that isn't always true. Once it starts working,
it seems to continue until a restart.
11 matches
Mail list logo
