[asterisk-users] Manager Originate and Callerid ?

[Kevin P. Fleming]

On 01/26/2012 09:23 AM, Russell Brown wrote:
>
> I'm using Manager API Originate to initiate calls from SIP channels (via
> phpagi FWIW) and it all works well except....
>
> ...the CallerID for the SIP channel specified in users.conf isn't set for
> the call :-(
>
> If I explicitly set the Callerid in the Manager Originate API call then
> it works but the API is actually being run from another server which
> doesn't 'know' the correct Callerid number and name for any given SIP
> phone so can't set them.
>
> I'm calling the Manager API with the following:-
>
> Action: Originate
> Channel: SIP/101
> Context: from-sip
> Exten: 01234567890
> Priority: 1
> Timeout: 20000
> ActionID: foo
>
> This results in the Callerid(name) and Callerid(num) being blank for the
> call.
>
> The 'from-sip' context is exactly the same as my SIP phones are using
> and when manually dialing the Callerid info is correctly picked up from
> users.conf.
>
> Any ideas why this is and how I can get the Manager API Originate call
> to use the correct Callerid info?

It can't. The Caller ID is provided by chan_sip when an incoming call 
*arrives* over SIP, and it can match the caller to the entry in sip.conf 
(or users.conf in your case).

An outgoing call originated by AMI will not be matched up to any 
sip.conf entries for Caller ID purposes.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming at digium.com | SIP: kpfleming at digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org