[asterisk-bugs] [JIRA] (ASTERISK-29166) CDR_PROP, setting party_a, and expectations
Kevin Harwell (JIRA)
noreply at issues.asterisk.org
Mon Nov 16 11:48:16 CST 2020
Kevin Harwell created ASTERISK-29166:
----------------------------------------
Summary: CDR_PROP, setting party_a, and expectations
Key: ASTERISK-29166
URL: https://issues.asterisk.org/jira/browse/ASTERISK-29166
Project: Asterisk
Issue Type: Bug
Security Level: None
Components: CDR/General, Functions/func_cdr
Affects Versions: 18.0.1, 16.14.1, 12.0.0
Reporter: Kevin Harwell
Severity: Trivial
The [CDR_PROP|https://wiki.asterisk.org/wiki/display/AST/Asterisk+18+Function_CDR_PROP] function seemingly allows one to specify which channel is to be _party_a_. However in practice this does not seem to be the case. Or at least it allows picking in such a limited capacity to be of almost no use.
So this is kind of a two-parter:
1) Figure out the use case(s) for when _party_a_ can be set via the function, and actually effect a record. If found then update the documentation. If possible fix any bugs related to setting _party_a_ on a given channel.
2) Potentially make it so setting _party_a_ using the function overrides even the dialer/dialed.
To the second part, that's more of a new feature and after some preliminary code perusal possibly quite invasive. As is, a dialing channel is always _party_a_ and the dialed channel is _party_b_. In order to override this behavior one would have to "swap" the _party_a_ and _party_b_ snapshots on the cdr structure. Finding the various places to do that is not trivial, and a basic swap probably has unforeseen circumstances (we are talking about CDRs here after all).
As a side note, I put Asterisk 12.0.0. as an affected version since it seems like things have been this way since the rewrite.
Current CDR "spec":
https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list