I assume you guys are using 1.6.0, yeah? Looks like there was some
sort of confusion about dahdi in 1.6.0... I just saw this because of
Sean Darcy's question about 1.6.0.1 in a different thread. This is
from the 1.6.0.1 changelog:
2008-10-08 Russell Bryant <[EMAIL PROTECTED]>
* Asterisk 1.6.0.1 released.
* configs/chan_dahdi.conf.sample: Remove mention of configuration
sections for defining channels in chan_dahdi.conf. This code
is in 1.6.1, and was not merged into 1.6.0.
Maybe that explains why dahdi won't work right? I don't know for sure,
just noticed this and thought it may be applicable.
Brendan Martens
On Oct 9, 2008, at 11:00 PM, Tzafrir Cohen wrote:
On Thu, Oct 09, 2008 at 08:12:46PM -0400, Alex Balashov wrote:
Good point.
I have a T100P that will not be seen by DAHDI for anything, but works
fabulously with Zaptel.
Which driver does it use?
Is it shown by dahdi_hardware / zaptel_hardware ? (for
zaptel_hardware:
try in zaptel 1.4.12 and above) .
--
Tzafrir Cohen
icq#16849755 jabber:[EMAIL PROTECTED]
+972-50-7952406 mailto:[EMAIL PROTECTED]
http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
