[asterisk-dev] Re: why 'o' (preserve original callerid) is not default in app_dial.c ?

John Lange j.lange at epic.ca
Wed Nov 1 09:01:15 MST 2006


On Wed, 2006-11-01 at 03:15 -0800, Luigi Rizzo wrote:

> I think (and the comments on this thread convince me even more)
> that the root of the problem is that we have one slot in the channel
> descriptor (callerid) to represent at least two (possibly more if
> we want to record the "routing" of the call) pieces of information:
> the source and the destination.
> 
> Until we make these two separate entries, there will always be confusion
> on what information is there - as you show, sometimes you need the
> source (e.g. when presenting 'who is calling me?' info to the destination),
> sometimes you need the destination (e.g. when rerouting, or deciding
> which voice-mailbox to use, etc.)

I think Asterisk could stand to have a (much?) expanded set of internal
variables accessible in the dialplan.

Just one simple example would be the username of the calling party (when
available). Doing dialplan logic based on callerid is sometimes very
problematic.

John




More information about the asterisk-dev mailing list