On Wed, 2007-12-26 at 17:47 +0200, Tzafrir Cohen wrote: > On Wed, Dec 26, 2007 at 08:38:31AM -0600, Bob Smither wrote: > > On Wed, 2007-12-26 at 07:27 +0200, Tzafrir Cohen wrote: > > > > > Just to stress the point: you mention that you don't see the card on > > > lspci. If this is so: the problem is not with Zaptel - it is below. > > > Zaptel doesn't even get a chance. > > > > Thanks Tzafrir. The last thing I tried was to downgrade Zaptel and > > during the boot, Zaptel reported success(*). > > What version of Zaptel reported success? Which version has failed?
After some frustrating times, I began to suspect the cards. Doing more careful testing, keeping track of the cards, confirmed that two of four cards I was trying had problems. I am able to get the two working cards to be properly configured and they seem to work well. Thanks for the trouble shooting suggestions from this list! One last question if someone has an answer - Using Kwelstart signaling * can detect incoming calls and can detect hang ups, but doesn't seem to be able to detect when an outgoing (over a Zap channel) call is answered. Is this correct, or have I not configured something? I am comparing this to what I have seen with IAX channels. When using call files, when the IAX channel answers that event in noted on the CLI. I don't see this with the Zap channel using call files. Thanks! _______________________________________________ --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
