Summary:ASTERISK-03369: [patch] stop app_dial from changing caller*id
Reporter:k3v (k3v)Labels:
Date Opened:2005-01-27 17:31:00.000-0600Date Closed:2011-06-07 14:11:58
Versions:Frequency of
Environment:Attachments:( 0) app-dial-no-callerid-changing.patch.txt
Description:App_dial changes caller*id to the current exten/macroexten in the dialplan upon successful call.  This is messing with my operator panel application's identification of the caller, since manager spouts these Newcallerid events (and I do need to observe them).  Is there some purpose for this behavior?  Channels (tested SIP and Zap) do not present this altered info to their peers, I assume because the CID change happens after ring.


disclaimer on file
Comments:By: k3v (k3v) 2005-01-27 17:37:38.000-0600

Looks like I'm trying to reverse bug ASTERISK-2451.  That change is causing me problems.  I kinda need best of both worlds, though, since it's nice to have it show the correct caller.  How about having app_dial set the channel directly, instead of calling ast_set_callerid()?  Add an option to ast_set_callerid() for not sending manager event?  Input?

edited on: 01-27-05 18:01

By: Mark Spencer (markster) 2005-01-27 18:30:59.000-0600

Makes no sense to change the callerid without having Asterisk send the manager event.  You can just follow the bridged channel.

By: k3v (k3v) 2005-01-27 18:42:13.000-0600

nevermind.  I changed my app to deal with the new behavior.

By: Mark Spencer (markster) 2005-01-27 23:41:38.000-0600

cool :)