[cisco-voip] RTMT versions and product compatibility

[Ryan Ratliff]

I'd love to see where that rumor got started.  I have no less than 4 versions of RTMT installed on my PC right now.  I'm pretty sure the introduction of the RTMT version into the program has alleviated the multiple install issues.  Of course having 3 different program groups under Programs->Cisco for various incarnations is fun too.

In general I use the latest and assume it's backwards compatible, at least for what I need it for (pulling traces).  Some of the advanced features may not be reliable with older versions and you should never expect an older RTMT to work with newer CUCM.

As for one RTMT for various products I'm thinking the move to Unified Serviceability with RTMT 8.7 and 8.8 is a signal that there is a desire for that to work.  Whether it does or not I've not tested.

-Ryan

On Apr 1, 2011, at 10:16 AM, Mac GroupStudy wrote:

Rumor has it Cisco TAC uses ONE version of RTMT for access to all of our versions of CUCM. Why can't we have that.

On Fri, Apr 1, 2011 at 2:31 AM, Garrett Skjelstad <garrett at skjelstad.org> wrote:
I think I'd prefer versions to be backwards compatible and simply a drop down box allowing me to choose which version I was going to be operating against. This would allow the UI to be fresh with whatever the latest version is, but allow backwards compatibility against previous revisions of software.

Sent from my iPhone

On Mar 31, 2011, at 22:38, Paul <asobihoudai at yahoo.com> wrote:

> I'd normally agree but seeing how RTMT must be changed according to each
> modification to the application, I think it's not completely unreasonable to
> upgrade/downgrade RTMT for the sake of strict compatibility...plus it doesn't
> even require a reboot!
>
> Think of cases where a piece of software maintains backwards compatibility for
> the long haul...that's where you get software like MS Windows where cruft is
> built upon cruft upon cruft...you get the picture. I think I'd rather have RTMT
> not require 1GB+ memory/HDD just for the sake of having one version to work with
> all versions.
>
>
>
> ----- Original Message ----
> From: Jason Aarons (US) <jason.aarons at us.didata.com>
> To: Ovidiu Popa <ovi.popa at gmail.com>; "cisco-voip at puck.nether.net"
> <cisco-voip at puck.nether.net>
> Sent: Thu, March 31, 2011 6:47:30 PM
> Subject: Re: [cisco-voip] RTMT versions and product compatibility
>
>
> At RTMT  install change the folder name to something else c:\program
> files\rtmtv8 vs c:\program files\rtmtv85
>
> Surely this complaint must be at some Product Manager within Cisco working hard
> to get a resolution.  It's truly a headache and a mystery as deep as  "Where is
> Jimmy Hoffa?" and "Who really shot JFK?"
>
> I vote for 1 version of RTMT. Anyone want to second that motion?
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ovidiu Popa
> Sent: Thursday, March 31, 2011 5:34 PM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] RTMT versions and product compatibility
>
> Hello everyone
>
> I have a couple of questions related to RTMT:
>
> - what is the relationship between RTMT versions and software product versions
> (CUCM, CUPS etc): Can we use a newer version of RTMT to connect to older
> versions of software e.g. using RTMT from CUCM 8 to connect to CUCM version 7?
>
> - can we use a CUPS RTMT to connect to CUCM or the other way around?
>
> - Why the different versions of RTMT don't play nice i.e if they detect another
> version will not let you install the new version until you get rid of the old
> one? Has anyone found a solution to install multiple RTMT from different
> products on the same workstation?
>
> By default RTMT uses different directories but even with different directories
> they will not let you install multiple versions:
> C:\Program Files\Cisco\Unified Communications Manager Serviceability\ C:\Program
> Files\Cisco\Presence Serviceability\JRtmt
>
> Thanks
> Ovidiu
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> -----------------------------------------
> Disclaimer:
>
> This e-mail communication and any attachments may contain
> confidential and privileged information and is for use by the
> designated addressee(s) named above only.  If you are not the
> intended addressee, you are hereby notified that you have received
> this communication in error and that any use or reproduction of
> this email or its contents is strictly prohibited and may be
> unlawful.  If you have received this communication in error, please
> notify us immediately by replying to this message and deleting it
> from your computer. Thank you.
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110401/b1414163/attachment.html>