[asterisk-bugs] [JIRA] (ASTERISK-19165) Empty CDR userfield and wrong UniqueID values stored in Master.csv when using Originate from AMI

[Joshua Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-19165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Colp updated ASTERISK-19165:
-----------------------------------

    Assignee: Alex
      Status: Waiting for Feedback  (was: Open)

CDR support has been completely rewritten in Asterisk 13. Do you still experience this problem there?

> Empty CDR userfield and wrong UniqueID values stored in Master.csv when using Originate from AMI
> ------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-19165
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19165
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/General
>    Affects Versions: 1.8.8.1
>            Reporter: Alex
>            Assignee: Alex
>
> When originating calls using AMI, CDR userfield isn't set for the second leg. Also invalid call UniqueId is stored in the CDR.
> The problem can be reproduced in the following way:
> 1. connect two SIP softphones to Asterisk (let's say phone1 and phone2),
> 2. add this dialplan:
> [test-firstleg]
> exten => _X.,1,Set(CDR(userfield)=test)
> exten => _X.,n,Dial(SIP/phone1)
> [test-secondleg]
> exten => _X.,1,Verbose(My uniqueid is ${UNIQUEID})
> exten => _X.,n,Set(CDR(userfield)=test)
> exten => _X.,n,Dial(SIP/phone2)
> 3. execute this action via AMI:
> action: originate
> channel: Local/123 at test-firstleg
> context: test-secondleg
> exten: 123
> priority: 1
> The CDR record in Master.csv for the second leg will not contain userfield value "test" (userfield will be empty). UniqueId value stored in CDR record will be different than the one printed out by "Verbose(My uniqueid is ${UNIQUEID})" in dialplan.
> Could you please advice how to avoid these two issues?



--
This message was sent by Atlassian JIRA
(v6.2#6252)