<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2014/1/23 Matthew Jordan <span dir="ltr"><<a href="mailto:mjordan@digium.com" target="_blank">mjordan@digium.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">On Thu, Jan 23, 2014 at 12:44 PM, Leandro Dardini <<a href="mailto:ldardini@gmail.com">ldardini@gmail.com</a>> wrote:<br>
> When you use a product which version number is 11 or even 12, you might go<br>
> with the assumption all big bugs are fixed and then you find there is a<br>
> huge, important, expensive bug still running in the code we are relaying<br>
> upon...<br>
<br>
</div>First, not all versions in 11 are the same. Bugs do get fixed. What<br>
version of Asterisk 11 are you using?<br></blockquote><div><br></div><div>I am using asterisk 11.6 and searching for "CDR transfer" in the issue tracker return unfixed bugs</div><div><br></div><div><a href="https://issues.asterisk.org/jira/browse/ASTERISK-11309">https://issues.asterisk.org/jira/browse/ASTERISK-11309</a><br>
</div><div><a href="https://issues.asterisk.org/jira/browse/ASTERISK-21822">https://issues.asterisk.org/jira/browse/ASTERISK-21822</a><br></div><div><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Second, CDRs are not the same in Asterisk 12. Due to extensive changes<br>
in the bridging core, CDRs were re-worked heavily. You may want to<br>
take a look at the notes on the Asterisk wiki [1] for Asterisk 12, as<br>
well as the CDR specification for Asterisk 12 [2].<br></blockquote><div><br></div><div>That seems great! Asterisk 12 really solved the CDR problem when transferring!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im"><br>
> The problem is simple. If you transfer a call, that dialing will be not<br>
> reported in the CDR, so no billing will happen. This is a simple example:<br>
<br>
</div>And how did you do the transfer? Via DTMF features? Via a particular<br>
channel driver technology? If so, which channel drivers were involved?<br></blockquote><div><br></div><div>Transfer was made using the "transfer" button of the phone and the result was the same with blind or attended transfer</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
What kind of transfer was it? Blind? Attended? Failed attended (the<br>
notorious blonde transfer)?<br>
<div class="im"><br>
><br>
> Extension 100 calls extension 101<br>
> After 10 seconds, extension 100 transfer the call to<br>
> 00VERYEXPENSIVEDESTINATION<br>
> After 100 seconds, extension 101 hangup the call<br>
><br>
> What do you find in the CDR? Just one record for a call from extension 100<br>
> to extension 101 lasting 10 seconds. What about the 100 seconds call from<br>
> 100 to 00VERYEXPENSIVEDESTINATION? It will never get billed.<br>
><br>
> How do you manage these cases?<br>
><br>
<br>
</div>I'm not sure if there is a bug report filed against CDRs for the<br>
currently maintained branches for lost records during a blind or<br>
attended transfer that matches your issue. There is ASTERISK-17826,<br>
which may or may not be your issue: the noted lack of information<br>
makes it a bit hard to tell. The last issue that I'm aware of that we<br>
fixed regarding lost CDRs during a transfer was ASTERISK-21394, which<br>
was fixed in 11.4.0.<br>
<br>
So, if you're using a version prior to 11.4.0, you may want to<br>
consider upgrading. Again, due to the lack of information, it's hard<br>
to tell whether or not that would help you.<br>
<br>
Finally, CDRs in versions of Asterisk prior to 12 are subject to the<br>
whims of channel masquerades. This has historically made it difficult,<br>
if not impossible, to guarantee correctness during all transfer<br>
operations. Additionally, even if we could guarantee a particular set<br>
of behaviour in all circumstances, the lack of any clear agreement as<br>
to what a CDR should look like after an attended transfer (or in any<br>
situation that involved multiple parties) made the problem impossible<br>
to solve to the satisfaction of everyone. This particular reason is<br>
why CEL was created. If you continue to have problems with the billing<br>
records, you may want to consider moving your billing logic to CEL.<br>
<br>
Note that since (a) Asterisk 12 re-architected using a consistent<br>
bridging framework, which killed visible channel masquerades; and (b)<br>
we decided to not try and please everyone and just defined CDRs for<br>
how we thought they should work; the behaviour of CDRs in Asterisk 12<br>
and in future versions should be substantially more predictable.<br>
<br>
Matt<br></blockquote><div><br></div><div>Thank you a lot! I am going to move ahead with asterisk 12!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
[1] <a href="https://wiki.asterisk.org/wiki/display/AST/New+in+12" target="_blank">https://wiki.asterisk.org/wiki/display/AST/New+in+12</a><br>
[2] <a href="https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification" target="_blank">https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification</a><br>
<span class=""><font color="#888888"><br>
--<br>
Matthew Jordan<br>
Digium, Inc. | Engineering Manager<br>
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA<br>
Check us out at: <a href="http://digium.com" target="_blank">http://digium.com</a> & <a href="http://asterisk.org" target="_blank">http://asterisk.org</a><br>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</font></span></blockquote></div><br></div></div>