<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
    <title></title>
  </head>
  <body text="#000000" bgcolor="#ffffff">
    Hello Ryan<br>
    <br>
    Here are the "rumor" details:<br>
    RTMT from CUCM 8.0.3.20000-2 installed on my machine on C:\Program
    Files\Cisco\Unified Communications Manager Serviceability<br>
    RTMT from CUPS  8.5.1.10000-35 to be installed at C:\Program
    Files\Cisco\Presence Serviceability\JRtmt<br>
    <br>
    I think the warning message is pretty self-explanatory:<br>
    <br>
    "<br>
    Warning: You have a RTMT of version 8.5.0.0 already installed. You
    are not allowed to install more than one copy of RTMT of same
    version on the same machine <br>
    ...<br>
    Warning: Existing RTMT version 8.5.0.0 will be uninstalled if the
    current installation is continued.<br>
    "<br>
    <br>
    Attched the screenshots.<br>
    <br>
    Regards,<br>
    Ovidiu<br>
    <br>
    <br>
    <br>
    On 01/Apr/11 7:54 PM, Ryan Ratliff wrote:
    <blockquote
      cite="mid:26F50B3F-3D6F-427F-81AE-80EB5B15BF17@cisco.com"
      type="cite">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.
      <div><br>
      </div>
      <div>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.</div>
      <div><br>
      </div>
      <div>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.</div>
      <div><br>
        <div>
          <span class="Apple-style-span" style="border-collapse:
            separate; color: rgb(0, 0, 0); font-family: Helvetica;
            font-size: medium; font-style: normal; font-variant: normal;
            font-weight: normal; letter-spacing: normal; line-height:
            normal; orphans: 2; text-indent: 0px; text-transform: none;
            white-space: normal; widows: 2; word-spacing: 0px;">
            <div>-Ryan</div>
          </span>
        </div>
        <br>
        <div>
          <div>On Apr 1, 2011, at 10:16 AM, Mac GroupStudy wrote:</div>
          <br class="Apple-interchange-newline">
          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.<br>
          <br>
          <div class="gmail_quote">On Fri, Apr 1, 2011 at 2:31 AM,
            Garrett Skjelstad <span dir="ltr"><<a
                moz-do-not-send="true"
                href="mailto:garrett@skjelstad.org">garrett@skjelstad.org</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
              0.8ex; border-left: 1px solid rgb(204, 204, 204);
              padding-left: 1ex;">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.<br>
              <br>
              Sent from my iPhone<br>
              <div>
                <div class="h5"><br>
                  On Mar 31, 2011, at 22:38, Paul <<a
                    moz-do-not-send="true"
                    href="mailto:asobihoudai@yahoo.com">asobihoudai@yahoo.com</a>>
                  wrote:<br>
                  <br>
                  > I'd normally agree but seeing how RTMT must be
                  changed according to each<br>
                  > modification to the application, I think it's not
                  completely unreasonable to<br>
                  > upgrade/downgrade RTMT for the sake of strict
                  compatibility...plus it doesn't<br>
                  > even require a reboot!<br>
                  ><br>
                  > Think of cases where a piece of software
                  maintains backwards compatibility for<br>
                  > the long haul...that's where you get software
                  like MS Windows where cruft is<br>
                  > built upon cruft upon cruft...you get the
                  picture. I think I'd rather have RTMT<br>
                  > not require 1GB+ memory/HDD just for the sake of
                  having one version to work with<br>
                  > all versions.<br>
                  ><br>
                  ><br>
                  ><br>
                  > ----- Original Message ----<br>
                  > From: Jason Aarons (US) <<a
                    moz-do-not-send="true"
                    href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>><br>
                  > To: Ovidiu Popa <<a moz-do-not-send="true"
                    href="mailto:ovi.popa@gmail.com">ovi.popa@gmail.com</a>>;
                  "<a moz-do-not-send="true"
                    href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>"<br>
                  > <<a moz-do-not-send="true"
                    href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
                  > Sent: Thu, March 31, 2011 6:47:30 PM<br>
                  > Subject: Re: [cisco-voip] RTMT versions and
                  product compatibility<br>
                  ><br>
                  ><br>
                  > At RTMT  install change the folder name to
                  something else c:\program<br>
                  > files\rtmtv8 vs c:\program files\rtmtv85<br>
                  ><br>
                  > Surely this complaint must be at some Product
                  Manager within Cisco working hard<br>
                  > to get a resolution.  It's truly a headache and a
                  mystery as deep as  "Where is<br>
                  > Jimmy Hoffa?" and "Who really shot JFK?"<br>
                  ><br>
                  > I vote for 1 version of RTMT. Anyone want to
                  second that motion?<br>
                  ><br>
                  > -----Original Message-----<br>
                  > From: <a moz-do-not-send="true"
                    href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
                  > [mailto:<a moz-do-not-send="true"
                    href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]
                  On Behalf Of Ovidiu Popa<br>
                  > Sent: Thursday, March 31, 2011 5:34 PM<br>
                  > To: <a moz-do-not-send="true"
                    href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
                  > Subject: [cisco-voip] RTMT versions and product
                  compatibility<br>
                  ><br>
                  > Hello everyone<br>
                  ><br>
                  > I have a couple of questions related to RTMT:<br>
                  ><br>
                  > - what is the relationship between RTMT versions
                  and software product versions<br>
                  > (CUCM, CUPS etc): Can we use a newer version of
                  RTMT to connect to older<br>
                  > versions of software e.g. using RTMT from CUCM 8
                  to connect to CUCM version 7?<br>
                  ><br>
                  > - can we use a CUPS RTMT to connect to CUCM or
                  the other way around?<br>
                  ><br>
                  > - Why the different versions of RTMT don't play
                  nice i.e if they detect another<br>
                  > version will not let you install the new version
                  until you get rid of the old<br>
                  > one? Has anyone found a solution to install
                  multiple RTMT from different<br>
                  > products on the same workstation?<br>
                  ><br>
                  > By default RTMT uses different directories but
                  even with different directories<br>
                  > they will not let you install multiple versions:<br>
                  > C:\Program Files\Cisco\Unified Communications
                  Manager Serviceability\ C:\Program<br>
                  > Files\Cisco\Presence Serviceability\JRtmt<br>
                  ><br>
                  > Thanks<br>
                  > Ovidiu<br>
                  > _______________________________________________<br>
                  > cisco-voip mailing list<br>
                  > <a moz-do-not-send="true"
                    href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
                  > <a moz-do-not-send="true"
                    href="https://puck.nether.net/mailman/listinfo/cisco-voip"
                    target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
                  > -----------------------------------------<br>
                  > Disclaimer:<br>
                  ><br>
                  > This e-mail communication and any attachments may
                  contain<br>
                  > confidential and privileged information and is
                  for use by the<br>
                  > designated addressee(s) named above only.  If you
                  are not the<br>
                  > intended addressee, you are hereby notified that
                  you have received<br>
                  > this communication in error and that any use or
                  reproduction of<br>
                  > this email or its contents is strictly prohibited
                  and may be<br>
                  > unlawful.  If you have received this
                  communication in error, please<br>
                  > notify us immediately by replying to this message
                  and deleting it<br>
                  > from your computer. Thank you.<br>
                  ><br>
                  > _______________________________________________<br>
                  > cisco-voip mailing list<br>
                  > <a moz-do-not-send="true"
                    href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
                  > <a moz-do-not-send="true"
                    href="https://puck.nether.net/mailman/listinfo/cisco-voip"
                    target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
                  ><br>
                  > _______________________________________________<br>
                  > cisco-voip mailing list<br>
                  > <a moz-do-not-send="true"
                    href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
                  > <a moz-do-not-send="true"
                    href="https://puck.nether.net/mailman/listinfo/cisco-voip"
                    target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
                  <br>
                  _______________________________________________<br>
                  cisco-voip mailing list<br>
                  <a moz-do-not-send="true"
                    href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
                  <a moz-do-not-send="true"
                    href="https://puck.nether.net/mailman/listinfo/cisco-voip"
                    target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
          _______________________________________________<br>
          cisco-voip mailing list<br>
          <a moz-do-not-send="true"
            href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
          <a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
        </div>
        <br>
      </div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>