[cisco-voip] ensuring component compatibility with IOS version

Tue Feb 7 11:44:44 EST 2012

Why would you get rid of some of the best and most stable gateways ever?  6608s were great!

Be careful about putting eggs in the CUE/SRSV basket.

I am hoping that when it comes time to replace my 3845 it will be SIP trunking time, so the DSP cost would diminish.

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Tuesday, February 07, 2012 9:21 AM
To: Nate VanMaren
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] ensuring component compatibility with IOS version

I have a project in the works to migrate some MGCP gateways from 6608's (stop laughing Scott) to the 3945s. I'm thinking now is the time to migrate to 15.x(y)M especially because of the shorter support cycle on the T code.

My biggest issue will be to ensure that the Unity Express modules will support the SRST version in that IOS code.

Thanks again.

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)

________________________________
From: "Nate VanMaren" <VanMarenNP at ldschurch.org<mailto:VanMarenNP at ldschurch.org>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Tuesday, February 7, 2012 11:03:41 AM
Subject: RE: [cisco-voip] ensuring component compatibility with IOS version

I thought you were getting it.

There’s no reason to “stick with T code”  T and M are the same, so if you’re not needing new features in a newer release ( like 15.2) going with the 15.1 latest which happens to be called a M release is great.

15.1.4 does have 100 rules.

Also, I had trouble with 15.2 last week running SIP, it would stop sending media after a phone did a transfer.  I back reved to 15.1.4M and it worked.  I did not have time to figure out what the problem was.

-Nate

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]<mailto:[mailto:lelio at uoguelph.ca]>
Sent: Tuesday, February 07, 2012 8:58 AM
To: Nate VanMaren
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] ensuring component compatibility with IOS version

Thanks Nate, this is helping.

So because there is/was no 15.1.4T, we'll have to go to the next T version if we want to stick with T code. The release dates seem to help now as well.

15.1(3)T Release Date: 17/NOV/2010
15.1(4)M Release Date: 25/MAR/2011
15.2(1)T Release Date: 22/JUL/2011

Of course, with this change, there's really no reason to go with the T code unless there's some new feature that you need that hasn't made it to the M code. And now it's easier to distinguish that.

Anyone with 15.2(1)T want to confirm that you can add 100 voice translation rules?
________________________________
From: "Nate VanMaren" <VanMarenNP at ldschurch.org<mailto:VanMarenNP at ldschurch.org>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Tuesday, February 7, 2012 10:25:12 AM
Subject: RE: [cisco-voip] ensuring component compatibility with IOS version

Yes there was only M releases of 15.0.
In 15.1
15.1.1T
15.1.2T
15.1.3T
15.1.4M

So they developed the features and stability in 15.1(1-3) then called it M in 15.1.4M, with features increasing thought the releases.

-Nate

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]<mailto:[mailto:lelio at uoguelph.ca]>
Sent: Tuesday, February 07, 2012 8:19 AM
To: Nate VanMaren
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>; Matthew Loraditch
Subject: Re: [cisco-voip] ensuring component compatibility with IOS version

It's confusing to say the least, especially when the first M version was 15.0 and the first T version was 15.1 and that figure 4 is mislabeled.

It almost sounds like anything in 15.(x)M will be in 15.(x+1)T.

Of course, I'm likely wrong, but it's just not clearly documented.

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)
________________________________
From: "Nate VanMaren" <VanMarenNP at ldschurch.org<mailto:VanMarenNP at ldschurch.org>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>, "Matthew Loraditch" <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Tuesday, February 7, 2012 10:02:59 AM
Subject: RE: [cisco-voip] ensuring component compatibility with IOS version

Lelio,

The T and M are the same train.  Say something comes out in 17.1.0M anything with a number greater than that will have the feature 7.1.5T or 17.1.9M.

M just means they think you should be able to stay on the code longer.

This is completely different from what T used to mean, but I believe they've gotten rid of the GD/LD/ED stuff.

-Nate

________________________________
From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [cisco-voip-bounces at puck.nether.net] on behalf of Lelio Fulgenzi [lelio at uoguelph.ca]
Sent: Monday, February 06, 2012 1:08 PM
To: Matthew Loraditch
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] ensuring component compatibility with IOS version
While that does explain how they handle the trains differently, still doesn't help with respect to knowing for sure whether a module is supported in a specific train.

I recalled a similar discussion we had with the translation limit and how it was increased in a particular M train but not sure in which T train it was in. This link was shared:

http://www.cisco.com/en/US/prod/collateral/iosswrel/ps8802/ps10587/ps10591/ps10621/qa_c67_561940.html

http://www.cisco.com/en/US/prod/collateral/iosswrel/ps8802/ps10587/ps10591/ps10621/qa_c67_561940.pdf (PDF)

This link explains things a bit more, but still, does not clearly indicate in which T train version a certain M train feature is included.

It looks as though both trains will incorporate new features that may or may not be included in the other train. Which simply adds to the confusion.

While it's pretty easy to look up IOS commands in references, module support is not as easy.

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)
________________________________
From: "Matthew Loraditch" <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>, cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Monday, February 6, 2012 12:25:30 PM
Subject: RE: [cisco-voip] ensuring component compatibility with IOS version
Take a look here, trains don’t work like they used to: http://www.cisco.com/en/US/prod/collateral/iosswrel/ps8802/ps5460/product_bulletin_c25-557281_ps5854_Products_Bulletin.html
You should be fine, that was a brand new ISR G2 part, and no EOL has been announced.

Matthew G. Loraditch - CCVP, CCNA, CCDA

1965 Greenspring Drive
Timonium, MD 21093

voice. 410.252.8830
fax.  410.252.9284

Twitter<http://twitter.com/heliontech>  |  Facebook<http://www.facebook.com/#%21/pages/Helion/252157915296>  | Website<http://www.heliontechnologies.com/>  |  Email Support<mailto:support at heliontechnologies.com?subject=Technical%20Support%20Request>

From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net]<mailto:[mailto:cisco-voip-bounces at puck.nether.net]> On Behalf Of Lelio Fulgenzi
Sent: Monday, February 06, 2012 12:01 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] ensuring component compatibility with IOS version

What's the easiest way to ensure a component is compatible with the IOS version you are running?

For example, ISM-SRE-300-K9 says minimum version is 15.0(1)M, but I want to know which T train it's supported in. Rather than trying to figure out which T train version 15.0(1)M was included in, I'd like to just see a compatibility tool.

All I can find is feature navigator and that doesn't list components.

Thoughts?

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)

NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

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