I fixed the problem by uncommenting the line #define ZERO_BATT_RING in wcfxo.c in zaptel-1.0.4.
And by changing the battery debounce time by modifying those lines: #define BATT_DEBOUNCE 700 /* Battery debounce (in ms) */
I compiled back zaptel, reloaded the modules and voila! It is now working. It is FINALLY detecting the ring/hangup EVEN when in voicemail.


Now, I still need to figureout why maxsilence and silencethreshold isn't working.

:)

Oh and by the way, the wildcard x100p was sharing an irq with an ethernet adapter so I switch them to different PCI slots and now it is on it's own IRQ.

Thank you for your discussion... it was entertaining.

Dave




David Hill wrote:

Hello there,

I tried to found documentation about openloop disconnect on Asterisk/Zaptel. And up to now, I didn't find anything. Is openloop disconnect supported by zaptel/wcfxo drivers?

Other question: maxsilence and silencethreshold don't seem to have any effect on voicemail. Could it be possible that in certain situation it just wont work? I tried adding some verbose in app.c to have the totalsilent variable printed out and it remains a 0 forever.

Finaly, does callprogress=yes should be working down here in Canada? Actually, everything seems to be broken (the wildcard x100p or the zaptel drivers plus a combination of many libraries/etc).


Thank you for your quick answer,

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




_______________________________________________ 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