[Asterisk-Dev] app_dial Caller ID behavior

[mattf]

I'm all in favor of having the old behaviour be default. But I thought since
this "feature" was introduced in release 1.0.5 and then taken out in 1.0.6
and 1.0.7 that the feature would not be the default for the next release. I
have installed CVS head several times in the last month and the callerID
handling has been messed with in all sorts of ways. Can we have a directive
from on-high as to what we should plan for in the next major official
release version?

Also, Russell, where is this patch and what version has it been tested
against?

Thanks,

MATT---


-----Original Message-----
From: Russell Bryant [mailto:russelb at CLEMSON.EDU]
Sent: Friday, March 25, 2005 1:54 PM
To: asterisk-dev at lists.digium.com
Subject: [Asterisk-Dev] app_dial Caller ID behavior


Hey folks,

I made a patch to restore the old Caller ID behavior by default, and to 
have an option to set the Caller ID to be the destination extension.

It seems as if the majority of users would expect the old behavior and 
having to add the 'o' option isn't very intuitive.

For those just tuning in, there was a change a couple months ago to make 
the Caller ID of the outbound leg of the call the destination extension 
instead of the Caller ID that was on the inbound leg of the call.  To 
preserve the Caller ID from the inbound leg of the call, you must use 
the 'o' option in app_dial.  See bug 2489 for the original change and 
bug 3490 for the addition of the 'o' option (at that point it was 'p', 
but was soon changed to 'o').

I just wanted to get a little bit of feedback to see if people agreed 
with me on this or not.

Thanks!

Russell
_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev