[Home]

Summary:ASTERISK-29309: Transfered Calls CDR Issues
Reporter:cagdas kopuz (cagdas)Labels:
Date Opened:2021-02-22 08:57:17.000-0600Date Closed:2021-02-22 08:57:18.000-0600
Priority:CriticalRegression?
Status:Closed/CompleteComponents:CDR/cdr_adaptive_odbc
Versions:GIT 16.16.1 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Hi,
We are using cdr_adaptive_odbc for asterisk  cdr. When an agent makes outgoing calls via [macro-dialout] context, If this calls answered asterisk write one line rows to the cdr tables. Eveything is ok. But when an agent(101) makes outbound calls and makes it attented transfer to the other agent (102) when the call terminated asterisk write two rows to the cdr one of this;

1) src : 101 dst: +90507XXXXXXX duration : 150 sec.
and other one ;
2) src : 101 dst : 102 duration : 15 sec. (101 says to 102 I will transfer the call to you.)
After this, I can not find the cdr  between 102 and  dst: +90507XXXXXXX. There is no cdr row in the table.
Where is the mistake ? How can I handle correctly transfered calls ?
Kind Regards.

Comments:By: Asterisk Team (asteriskteam) 2021-02-22 08:57:18.484-0600

We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum.

The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors.

If this issue is actually a bug please use the Bug issue type instead.

Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines
By: Asterisk Team (asteriskteam) 2021-02-22 08:57:19.440-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].