[asterisk-bugs] [JIRA] (ASTERISK-25529) (Adaptive)CDR with MySQL Storing LinkedID in Uniqueid column
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Sat Nov 21 12:01:33 CST 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-25529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=228409#comment-228409 ]
Asterisk Team commented on ASTERISK-25529:
------------------------------------------
Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].
[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines
> (Adaptive)CDR with MySQL Storing LinkedID in Uniqueid column
> ------------------------------------------------------------
>
> Key: ASTERISK-25529
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25529
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: CDR/cdr_adaptive_odbc, CDR/General
> Affects Versions: 13.6.0
> Environment: Debian Wheezy VM 2GB Ram 4 Cores
> Reporter: Ryan Rittgarn
> Assignee: Ryan Rittgarn
> Severity: Minor
>
> found this issue while looking at hangup handlers.
> using dialplan, output the different variables, then looked at the call values stored in the DB.
> {noformat}
> same => n,Verbose(CDR ${CDR(uniqueid)} UNQ ${UNIQUEID} ${CDR(linkedid)})
> {noformat}
> Insert query for cdr contains the linkedid instead of uniqueid on incoming calls. If there is no linked channel, uniqueid populates linkedid and is then accurate in cdr.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list