John Novack wrote:
What backwards thinking put the information there, and in addition changed the way jumps used to work as the default?
Could you be slightly more abusive with your questions? Your attitude will certainly encourage people to want to help you solve your problems...
The information is there because the change was intended to be entirely backwards compatible and invisible to users unless they replaced their extensions.conf with the sample file; if they do that without reading it, that's their own fault. As long as 'priorityjumping=no' (or the equivalent) is not present in extensions.conf, the behavior is supposed to be unchanged from all previous versions.
However, the change was implemented improperly, and the default did change. This was fixed late on October 13th, and is now corrected in CVS HEAD. This is exactly the reason that we make beta releases and ask for CVS testers, because otherwise problems don't get found until real releases are made. Interestingly, there have been _zero_ previous reports of this behavior changing on people, so I can only assume that everyone else that has tested 1.2.0-beta1 or recent CVS HEAD were aware of the change (either by staying on top of the changes via asterisk-cvs and/or the bug tracker, or by reading the sample config file and taking advantage of the new, much easier to use behavior).
If more time were spent on fixing things that were broken, and making the interface to the existing PSTN analog lines work smoother there might be more acceptance.
Acceptance of what? If there are specific issues you are referring to (rather than just ranting), have you made an effort to get anyone to solve those problems? You do realize that 90% of the Asterisk community does what they do on a volunteer basis, right? Noone can dictate what they work on, what they fix or don't fix, or anything else. If you have specific problems that need solving (that don't relate to Digium hardware, since you can contact Digium support to get those problems resolved), then you either need to figure out how to solve them yourself or make your case known and convince others in the community that your problems need solving. This is not a commercial software project, noone owes you any attention or particular software behavior... but we certainly are happy to help those who can demonstrate specific problems and help us find the cures for them.
We have been handling somewhere between 200 and 400 bugs per month through our bug tracker for the past 4-5 months... if you think that a better job could be done, how about providing some constructive help rather than ambiguous ranting?
_______________________________________________ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
