[asterisk-bugs] [JIRA] (ASTERISK-29509) Callerid not being set via AMI Originate

[Daniel Harper (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-29509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255637#comment-255637 ] 

Daniel Harper commented on ASTERISK-29509:
------------------------------------------

I tested this and I do see the callerid set correctly in the tcg-queue context. So perhaps its is indeed the new agents functionality at play here. I am still coming to grips will all the changes since 1.4. I can workaround this issue by using a variable in the originate command. Hopefully this might help someone else.

Thanks Daniel

> Callerid not being set via AMI Originate
> ----------------------------------------
>
>                 Key: ASTERISK-29509
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29509
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/CallerID
>    Affects Versions: 16.19.0
>         Environment: CentOS Linux release 7.9.2009 (Core)
>            Reporter: Daniel Harper
>            Assignee: Daniel Harper
>              Labels: fax, webrtc
>         Attachments: full
>
>
> When issuing an Originate via AMI with a Callerid parameter the parameter is being ignored and the callerid name is not being set.
> I was testing previously on 16.18.0 but on this version the endpoints callerid was being ignored and the name an num were the extension number. I upgrade to 16.19.0 and this issue is fixed but now the callerid parameter sent via the AMI Originate is being ignored (as it was also in 16.18.0)



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