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

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp commented on ASTERISK-29509:
-------------------------------------------

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected and the location of documentation that led you to that expectation.
3. The behavior you actually encountered.

To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

[2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information



> 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
>            Severity: Major
>
> 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)