Unless I have a very good lab environment I try to stick with what we know works unless a major issue shows up or the vendor refuses to support the product on a given code. I always prefer stability to bleeding edge. That said sometimes there really are new features that will provide new revenue opportunities that will make it worth upgrading. How many of us, especially smaller carriers, have true lab environments that can test all the features and functions of our Class4/5 switches for something like a major code upgrade without effecting the production network at all? This would include carrier A links and ISUP trunks (at least simulated), LNP/CNAM dips, etc. -Scott -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of David Hiers Sent: Thursday, December 17, 2009 11:29 AM To: VoiceOps at voiceops.org Subject: [VoiceOps] Old code vs bold code I've been snooping around our production systems, and the base code version for everything that we run in the call path is between 2 and 3 years old. It is patched to a fare-thee-well, and the stuff runs quite well. We use only top-tier vendors, yet can't recall ever being happy on code that is less than 1 year old. Too many bleeding edge bugs for my current medication level. How 'bout you guys? How long do you let a codebase steep before you're happy with running it in production? Thanks, David _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops