I'm sure we're all running different CM versions, but in the 6.3.x world has anyone really settled in on a specific version? They seem to be coming out with patches pretty frequent in this version. I'm running 6.3.5 and wondering if there's a version above that has proven to be really stable with the inclusion of worthwhile features. I guess I'm looking for the CM5.2.1 equiv in the 6.3 world. I see 6.3.11 is out and I went from being semi current not too long ago to already being pretty behind.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
CM Version
- Thread starter wpetilli
- Start date
You basically settle on what's right for you.
If you're not living with bugs, stay with it for a while. As more SIP stuff and features get hammered in, more patches are needed to fix those bugs.
Just as an example, if you were current on 6.3.5 and had a bug, they'd write you a custom patch of 6.3.5+bugfix A and B - but bugfix A and B wouldn't be committed until 6.3.8, so 6.3.6 and 7 wouldn't help you, etc.
Don't be a guinea pig if you don't have to be!
If you're not living with bugs, stay with it for a while. As more SIP stuff and features get hammered in, more patches are needed to fix those bugs.
Just as an example, if you were current on 6.3.5 and had a bug, they'd write you a custom patch of 6.3.5+bugfix A and B - but bugfix A and B wouldn't be committed until 6.3.8, so 6.3.6 and 7 wouldn't help you, etc.
Don't be a guinea pig if you don't have to be!
jimbojimbo
Vendor
CM 6.3.9.1 or 6.3.11. Look at the release notes and PSN/PSN notes and see if there is anything which may impact your system. For example the heartbeat reset (see PSN 20190). Or modifications to the core architecture you find beneficial such as the changes to the restart strategy (see PSN 20191).
If you get too far behind it becomes a major issue when trying to get support from Avaya. First answer is always "upgrade to the latest patch".
Unfortunately Avaya release levels have become completely disconnected. Compatibility needs to be checked to the "X" degree 6.3.x. Unfortunately whoever is writing the interfaces doesn't seem to understand version compatibility and testing seems to be questionable. For example when going to CM6.3.11 you should be on AES 6.3.3 however this could technically require an upgrade to IC or Call Recording (Client SDK 4.2 was deprecated in AES 6.3). Don't ask me why they didn't do this at the major release level.
CM7 should become available tomorrow so sometime next year the 6.3 extended support release should be finalized.
If you get too far behind it becomes a major issue when trying to get support from Avaya. First answer is always "upgrade to the latest patch".
Unfortunately Avaya release levels have become completely disconnected. Compatibility needs to be checked to the "X" degree 6.3.x. Unfortunately whoever is writing the interfaces doesn't seem to understand version compatibility and testing seems to be questionable. For example when going to CM6.3.11 you should be on AES 6.3.3 however this could technically require an upgrade to IC or Call Recording (Client SDK 4.2 was deprecated in AES 6.3). Don't ask me why they didn't do this at the major release level.
CM7 should become available tomorrow so sometime next year the 6.3 extended support release should be finalized.
Just in case you didn't know you can get system manager to go off and find all the latest , patches firmware etc etc as long as you have the device configured, you can then deploy at will , doesn't really answer your original question , we usually install to major release upgrade to the service pack available at that time , then continue to deploy that release and sp across the estate , until we come across bug or a new major release is introduced. It just keeps a little consistency and unless you are hitting bugs that sp, s specifically address it's easy to keep track of where you are and in some cases fault find,
Avaya say upgrade to X to fix that , but hang on no sp, s detail a fix for the issue I'm having and I have six other identical pieces of equipment that are not having the issue etc etc I'm sure you get the idea , but it's usually down to acceptable downtime expectations and personal preference.
Avaya say upgrade to X to fix that , but hang on no sp, s detail a fix for the issue I'm having and I have six other identical pieces of equipment that are not having the issue etc etc I'm sure you get the idea , but it's usually down to acceptable downtime expectations and personal preference.
- Status