[Asterisk-Users] Callerid problems with 1.0.5

[Mark Eissler]

I saw the note about the "o" flag. But if I'm not mistaken we have to 
add the "o" flag to get the old behavior back again instead of using 
the "o" flag to get the new behavior. That means our existing (and 
formerly functioning) dialplans will be broken.

It would make more sense IMHO to have a flag that turns on the new 
behavior rather than having one that restores the old behavior. But 
then again, I also think that if a call is bouncing out of call park 
that the caller id should indicate that as opposed to presenting it as 
a brand new call.

-mark

On Feb 4, 2005, at 9:35 PM, mattf wrote:

> Hello,
>
> patching v1.0.5 on my system removed the problem for me. But yes it 
> seems
> strange that this feature was inserted into a final release with very 
> little
> documentation of the wide implications that are caused by the change.
>
> This was corrected in CVS with the addition of a diabling flag for the 
> dial
> command, but maybe this is a message that we should start an official 
> beta
> release period before a release so that people can test pre-releases 
> even
> for just a week to report problems before it is unleashed upon the 
> world as
> an official release
>
--
Mark Eissler, mark at mixtur.com
Mixtur Interactive, Inc. - at - http://www.mixtur.com