[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=255548#comment-255548 ] 

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

In regards to your comment:

"Further to this in my testing I have noticed that I have to restart asterisk if I change the callerid for the endpoint as a reload isn't sufficient. Sorry this is perhaps a different issue but I bring attention to it so show that perhaps something is broken in regards to the callerid code."

This is because you have an active call to the endpoint, until a new call is placed from the endpoint the old callerid will be used. It is not updated in realtime across all active channels from an endpoint upon configuration change.

I also think your problem is not really a problem, but the way that connected line updates and originate works. Asterisk 1.4 did not have such functionality and also had completely different agents functionality. Upon answer the agent information is given to the other side of the call, which is what is doing your dialling. One thing that comes to mind as a potential solution is to set your own variables for callerid information, and then before doing the Dial() to change callerid.

> 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: Unassigned
>              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)