Hi! > For codecs use CHANNEL function, but you will only get CallLegA > codecs. Without hacking Asterisk, you will not be able to get CallLegB > codecs. Patch for Asterisk 1.4.33.1 attached to get such info.
Thank you! In the meanwhile I found that with the help of the M option to Dial (macro called right after connect) it is possible to access also the bridged CHANNEL variables including "audionativeformat" - but those variables will already be destroyed before you get to the h extension. Now I would like to find a way how to add some "adaptive" functionality to MySQL CDR in asterisk-addons for Asterisk 1.4 that can append self- chosen fields to the cdr table (like: codec). It appears that patch 11642 doesn't - anymore - do that successfully: https://issues.asterisk.org/view.php?id=11642 So far I do not want to switch to ODBC (Tilghman was so kind to make a backport available). Note: asterisk-addons for Asterisk 1.6 is not compatible with Asterisk 1.4. I'd also prefer to avoid to write to MySQL (or AstDB as a means to export variables from the bridged channel to the originating channel) directly from the dialplan. Philipp -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
