asterisk users - Aug 2010 - Why does Digium not respect their own development guidelines?

As recent as 2008 "Asterisk 1.4 is feature frozen" if that is the case
how come now CallingToken support is added? I don't really know what
this is but all I know is:

1) Callingtoken adds new options to the config files
2) Callingtoken is some new protocol in IAX?
3) Upgrading asterisk 1.4 breaks previous IAX connections.

So why was this added? I have 1 machine that is set not to log these
messages on the console and am pulling my hair out after upgrading
Asterisk 1.4 to a new release. It is not anything I would look into
normally since "Asterisk 1.4 is feature frozen"  so why would I look
to troubleshoot a feature that isn't supposed to be there?

On Saturday 28 August 2010 20:27:23 Andrew Joakimsen
trolled:
> As recent as 2008 "Asterisk 1.4 is feature frozen" if that is the
case
> how come now CallingToken support is added? I don't really know what
> this is but all I know is:
>
> 1) Callingtoken adds new options to the config files
> 2) Callingtoken is some new protocol in IAX?
> 3) Upgrading asterisk 1.4 breaks previous IAX connections.
>
> So why was this added? I have 1 machine that is set not to log these
> messages on the console and am pulling my hair out after upgrading
> Asterisk 1.4 to a new release. It is not anything I would look into
> normally since "Asterisk 1.4 is feature frozen"  so why would I
look
> to troubleshoot a feature that isn't supposed to be there?
http://downloads.asterisk.org/pub/security/AST-2009-006.html

-- 
Tilghman Lesher
Digium, Inc. | Senior Software Developer
twitter: Corydon76 | IRC: Corydon76-dig (Freenode)
Check us out at: www.digium.com & www.asterisk.org