[asterisk-bugs] [JIRA] (ASTERISK-25529) (Adaptive)CDR with MySQL Storing LinkedID in Uniqueid column
Ryan Rittgarn (JIRA)
noreply at issues.asterisk.org
Fri Nov 6 10:32:32 CST 2015
Ryan Rittgarn created ASTERISK-25529:
----------------------------------------
Summary: (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
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.
same => n,Verbose(CDR ${CDR(uniqueid)} UNQ ${UNIQUEID} ${CDR(linkedid)})
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