It started with a desire to make pre-ring caller ID work Right and then to use spandsp for caller ID handling. But the more I look at chan_zap the more bugs and, um, "strangeness" I find...
This should make caller ID (incoming on FXO and outgoing on FXS) JFW (Just Work) for the vast majority with only default configuration regardless of whether you do Bell, V23 or DTMF pre-ring, post-ring or both. Read the updated example zapata.conf, get rid of unnecessary config options and just enjoy. Note in particular the new options "polarityevents" (for those with X100s or who live with really annoying telcos), "exten" (for everyone that hates having a separate context for every FXO), and the "dring<n>*" changes (for everyone who values their sanity). So... it's a fair sized patch and _needs_ testers. Please! Especially if you have a PRI (to check I haven't broken anthing), are in a country that uses DTMF caller ID, are in a country that sends pre-ring caller ID with no polarity reversal, or have hardware (X10xP) that just doesn't recognise polarity reversals. Yes, that means YOU! The patch is at: http://www.callweaver.org/ticket/21 If you use a TDM400P somewhere that uses polarity reversals to signal call start and pre-ring caller ID you will need: http://bugs.digium.com/view.php?id=9264 If you use a TDM2400P you'll need to make a similar change to that driver (I don't have one) Mike -- Mike Jagdis Web: http://www.eris-associates.co.uk Eris Associates Limited Tel: +44 7780 608 368 Reading, England Fax: +44 118 926 6974 _______________________________________________ Callweaver-dev mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-dev
