<!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 bgcolor="#ffffff" text="#000000">
CM also generates the config for router download. There is potential
for difference in global config for the boxes in which case ccm-manager
config would cause problems. It may work as a short term workaround,
but it's not scalable (read: likely to break in a future upgrade).<br>
<br>
/Wes<br>
<br>
On Thursday, August 12, 2010 4:58:23 PM, Nick Matthews
<a class="moz-txt-link-rfc2396E" href="mailto:matthnick@gmail.com"><matthnick@gmail.com></a> wrote:<br>
<blockquote
cite="mid:AANLkTinXtPAe_gZw0P8x6BRY_cqxtGJgqbJk4=gShrn+@mail.gmail.com"
type="cite">So here's the thing with this, which I know isn't really
documented anywhere(assuming MGCP):<br>
<br>
Those pull downs for the routers and the cards are just for MGCP
endpoint formatting (to my knowledge, not a developer).<br>
<br>
The format of AALN/S0/SU1/0@<em> fv</em> is a mixup of the platform and
the cards so CUCM can put the slot and subslot in the correct format.<br>
<br>
In theory, if you just put in a 2800 in the same way you would a 2900,
I would expect this to work. I can't think of any reasons on why CUCM
would keep a separate MGCP stack for each router. If you look at some
of the older routers and cards there were not determinable, it actually
had you fill in the port/slots. <br>
<br>
If you're talking SIP/H.323 the integration is so loose, I would not
even worry about the difference on the latest software.<br>
<br>
-nick<br>
<br>
<div class="gmail_quote">On Thu, Aug 12, 2010 at 4:18 PM, Countryman,
Edward <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:Edward.Countryman@provena.org">Edward.Countryman@provena.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Here
the response I received from TAC on this question:<br>
<br>
"The 2900 series routers, being the newest release from Cisco, are not<br>
supported on older versions of CallManager since you don't even have the<br>
option to add them. These routers are supported on CallManager version<br>
7.1.3 and above<br>
Since CUCM 6.X is now in its end of life stage, there will be no more<br>
upgrades for the version, except for the engineering specials or any<br>
necessary patches.<br>
Related with the upgrade path, the recommended version would be CUCM<br>
7.1.5.10000-12 since it's the latest version."<br>
<div class="im"><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 Countryman,<br>
Edward<br>
Sent: Thursday, August 12, 2010 1:27 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] 29xx routers and CCM 6.1?<br>
<br>
</div>
<div>
<div class="h5">Our networking has started to deploy 29xx routers
in our environment, I<br>
noticed there are no options in my 6.1 call manager to configure these.<br>
Does anyone know if they are supported on 6.1 or can I just select the<br>
equivalent 28xx version????<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>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
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>