[Home]

Summary:ASTERISK-17240: [regression] Local channel: Caller ID in .call file ignored
Reporter:Kirill Katsnelson (kkm)Labels:
Date Opened:2011-01-13 09:04:01.000-0600Date Closed:2011-06-07 14:04:45
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_local
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) 18614.ael
( 1) 18614.call
Description:A .call file used to originate a call with CalledID set. The caller ID is available in the inner script of the Local channel but not in its outer script.

1.6 did not have that problem.

****** STEPS TO REPRODUCE ******

== AEL: ==

context test-local {
 _[!-z]. => {
   NoCDR();
   Verbose(1,test-local extension ${EXTEN} caller id [${CALLERID(num)}]);
   Dial(SIP/250);
 }
};

context test-remote {
 _[!-z]. => {
   NoCDR();
   Verbose(1,test-remote extension ${EXTEN} caller id [${CALLERID(num)}]);
 }
};

== .call file ==

CallerID: "" <8885550101>
Channel: Local/Sample@test-local
Extension: 13105550202
Priority: 1
Context: test-remote
WaitTime: 120

== Verbose output: ==

test-local extension Sample caller id [8885550101]
test-remote extension 13105550202 caller id []


****** ADDITIONAL INFORMATION ******

AMI Originate does not seem to have that problem, but I am not very certain.
Comments:By: Timothy M. Rodriguez (timothy055) 2011-01-25 16:46:54.000-0600

I am also experiencing this issue via AMI or when using a call file in Asterisk 1.8.1.1.
By: Chatri Khatfan (chatri) 2011-01-29 15:35:56.000-0600

I also had the same problem using call files with "channel_local" on Asterisk 1.8.1.1 and in Asterisk 1.8.2.3.


By: Alex Barzinsky (sunshine) 2011-02-18 05:09:12.000-0600

I have that trouble too.
By: Kirill Katsnelson (kkm) 2011-02-18 06:13:20.000-0600

As an obvious workaround, I am passing the called ID in a variable to assign later in the dialplan.
By: Chatri Khatfan (chatri) 2011-02-18 11:27:22.000-0600

@kkm that's what I've been doing as a temporary solution too but hoping someone will look into this.
By: Richard Mudgett (rmudgett) 2011-04-05 16:34:59

This is not a bug but an expected behaviour when the call is answered.

The CallerID is being updated when the first call is answered because of
the connected line feature.  Please read about the connected line and
digit manipulation features on the Asterisk wiki.

https://wiki.asterisk.org/wiki/display/AST/Manipulating+Party+ID+Information

For your test configuration, you can simply use the 'I' option on the
Dial() application.