[cisco-voip] IOS / CM

[Nick Matthews]

Generally the correlation is pretty loose.  MGCP sometimes is a little
more version dependent since the control is tigher.  H.323 is by the
the loosest, and a slightly higher correlation with SIP because
features are added/changed so quickly.

I would say the IOS versions really become more important when you
start running SCCP on the router for media resources (conferencing,
MTP, transcoding) or when you do SCCP controlled FXS ports (VG224).

If you're running 12.4(20)T or later I personally wouldn't upgrade any
of the routers unless I had trouble.

-nick

On Mon, Jul 19, 2010 at 2:01 PM, Matthew Linsemier
<mlinsemier at apassurance.com> wrote:
> I’m curious about this document as it only lists the IOS version required
> for CME / SRST.  We still are UCM 7.1(5a) with IOS 12.4(24)T3 and aren’t
> having any issues.  However, we haven’t done a whole lot of SRST testing...
> Maybe I should do more.
>
> Matt
>
>
> On 7/19/10 1:17 PM, "Scott Voll" <svoll.voip at gmail.com> wrote:
>
> So we are moving from CM 4.2 to 7.1.5.
>
> according to
> this: http://www.cisco.com/en/US/customer/docs/voice_ip_comm/uc_system/unified/communications/system/versions/IPTMtrix.html#wp1016708
> we need all our Router up to 15.0.1M for CM 7.1.3
>
> my questions:
>
> 1.  What about 7.1.5?
> 2.  Why do you need to upgrade to a 15.0 IOS?  Could 12.4T work?
> 3.  If we upgrade IOS to 15.0 will the Routers (VGWs) still work on CM 4.2?
>
> If you have any info on the relationship between IOS and CM I would like to
> understand it more completely.  I have both H323 and MGCP VGW's.  Since some
> of them are H323 does the IOS requirements go out the window?
>
> Thanks
>
> Scott
>
>
> ________________________________
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ________________________________
>
> CONFIDENTIALITY STATEMENT
> This communication and any attachments are CONFIDENTIAL and may be protected
> by one or more legal privileges. It is intended solely for the use of the
> addressee identified above. If you are not the intended recipient, any use,
> disclosure, copying or distribution of this communication is UNAUTHORIZED.
> Neither this information block, the typed name of the sender, nor anything
> else in this message is intended to constitute an electronic signature
> unless a specific statement to the contrary is included in this message. If
> you have received this communication in error, please immediately contact me
> and delete this communication from your computer. Thank you.
>
> ________________________________
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>