bridging and transfers are channel.c and res_features.c. res_features.c is
certainly being tweaked at the moment (probably by murf). I noticed the
following block on line 233 has been removed from it between 1.4.19 to
1.4.22.
if (tobj->chan->cdr) {
ast_cdr_reset(tobj->chan->cdr, NULL);
ast_cdr_setdestchan(tobj->chan->cdr, tobj->peer->name);
}
if (tobj->peer->cdr) {
ast_cdr_reset(tobj->peer->cdr, NULL);
ast_cdr_setdestchan(tobj->peer->cdr, tobj->chan->name);
}
1.4.19 actually produces a CDR per channel as I'm suggesting it's just
that the information in them is not correct.
As far as your license pending it's a manual process and someone from
Digium will check and approve your license at some point. Just as a word of
caution don't build up too high an expectation about getting patches
accepted. I'm not meaning to discourage a contribution by any means but
I've seen a very useful patch not accepted because it weren't deemed
"necessary" due to future improvements providing an alternative. The
particular patch was not as close to the core of Asterisk as what we're
talking about here. That's the reason I'm so keen to get buy off on a
design decision, cutting the code for this will be hard but doing it and
then seeing it sit outside the main code base and having to apply it for
each release would be even harder.
Issue History
Date Modified Username Field Change
======================================================================
2008-11-02 07:58 greyvoip Note Added: 0094503
======================================================================