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!

Communications Manager version

Status
Not open for further replies.

CinciPrius

Programmer
Apr 25, 2003
27
US
OK - stupid question - How do I determine what version of Communications Manager my system is running? I know I've got an 8500 media server and I think I'm on 2.something but the DST upgrades appear to be unique for different 2.x versions.

Thanks
 
type the command "disp capacity" - the software version is on page 12.
 
OK - that shows me:

Software Load: R012x.01.1.414.1
Memory Config: G3xV12
Offer Category: A

How does that relate to the Communication Manager version?
 
Hi CinciPrius,

I just talked to Avaya about this yesterday. They had me do a 'list config software' command, and I saw this:
SOFTWARE VERSIONS

SOFTWARE VERSION
Memory Resident: R013x.01.2.632.1
Disk Resident: R013x.01.2.632.1

TRANSLATION DATE
Memory Resident: 10:00 pm MON FEB 19, 2007
Disk Resident: 10:00 pm MON FEB 19, 2007
Disk Second Copy: good

The R013x.01.2.632.1 tells you its a 3.1.2 version of CM, so I didnt have to do any DST changes. (Take the 3 from the first section, the 1 from the second, and the 2 from the third section)


Hope this Helps

HeatherSuzanne
 
or if in shell mode, command> swversion shows that same info
 
many thanks - the "(Take the 3 from the first section, the 1 from the second, and the 2 from the third section)" explanation was fantastic. I'd never seen it explained and that's a great explanation.

Alan
 
Hi CinciPrius,

That's how Avaya explained it to me, and I was able to apply that to all my CM systems to determine what patches I needed. Glad it helped.

HeatherSuzanne
 
But be careful - that info only tells you the software version of the server you are logged in to, in most cases, the controlling server(s). If you have other sites, in ESS or LSP configs, you should check each site, because they could be on different releases.

We have four sites, the main site has two controlling S8710s, two sites have S8710s in ESS configs, and one site has a S8300 with LSP config. Two of the sites are on 3.0.1, two are on 3.1.1, so different DST patches are needed. (Plus the S8300 is on 3.1.1, and is in Canada, so it has to be upgraded to 3.1.2. The other 3.1.1 is in the US, so it does not have to be patched.) Make sense? Yeah, it doesn't make sense to me either.

To be safe, if you have multiple sites, follow rgtrgt's line of thought and log into each site and look at it from the shell, or from the management web interface...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top