The issue wasn't with the zaptel drivers, it was with the Asterisk code. In asterisk 1.0.9 it would not recognize the card and the spans never got out of red alarm. In cvs v1.0 the card loaded fine but when asterisk started up the first time it would seg fault with the error mentioned above, then I could start it a second time, but with in a few minutes of calls it would seg fault again. When I looked at the code for dsp.c in cvs v1.0 and v1.2 I noticed many differences and I'm really not familiar enough with that bunch of the code base to try to fix it myself.

Another note, this exact machine with a v1 TE405P three days ago worked just fine with the exact same settings under asterisk 1.0.9

MATT---

On 9/2/05, Kevin P. Fleming <[EMAIL PROTECTED]> wrote:
Matt Florell wrote:
> I have resolved my manager API issues with 1.2 beta1 and used the system for
> about 14000 calls today with no major problems. After talking to Digium
> support staff I learned that they are not backporting a lot of the
> optimizations for this card to the v1.0 tree anyway, so CVS_HEAD and
> 1.2b1are the only options.

That is not true; the CVS HEAD and CVS v1-0 drivers for the TE4XX cards
are identical, and will be kept that way. Please email me  off-list to
let me know who told you that.
_______________________________________________
--Bandwidth and Colocation sponsored by Easynews.com --

Asterisk-Users mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

_______________________________________________
--Bandwidth and Colocation sponsored by Easynews.com --

Asterisk-Users mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to