<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1479" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>What sort of memory did you have before? I think our TFTP
server is at 1GB.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=WCarter@sentinel.com href="mailto:WCarter@sentinel.com">Carter,
Bill</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=Craig.Watson@CommerceBank.com
href="mailto:Craig.Watson@CommerceBank.com">Watson, Craig</A> ; <A
title=lelio@uoguelph.ca href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A> ;
<A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, December 14, 2004 11:58
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [cisco-voip] CM 4.1</DIV>
<DIV><BR></DIV>We have been very happy with 4.1(2). 4.0X had some
problems. You<BR>should really consider a DRAM upgrade, 4.X appears to
consume more<BR>memory that
3.3(4)X.<BR>________________________________<BR><BR>From: Watson, Craig
[mailto:Craig.Watson@CommerceBank.com] <BR>Sent: Monday, December 13, 2004
5:06 PM<BR>To: Lelio Fulgenzi; <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>Subject:
RE: [cisco-voip] CM 4.1<BR><BR><BR><BR>I am actually very interested in this
as well, as far as the differences<BR>people are seeing in going to
4.1(x). We are rolling out a new Cisco<BR>VoIP network and the
consideration to roll out with a brand new version<BR>of CCM was very tempting
to us because of the features and functionality<BR>inherit in the new version
that most resembled what the Telecom team<BR>here was used to. But
because we really didn't want to deal with both<BR>the complexity of a brand
new phone system and a brand new version of<BR>CallManager that was untested,
our pain-threshold limited us to going to<BR>4.0.
<BR><BR> <BR><BR>We are definitely looking to migrate and upgrade to 4.1
in the near<BR>future, after further rollouts are done and more testing has
been made.<BR>If any of you have tested or are making the transition to 4.1,
please do<BR>share your experiences. I will do the same once we get to
that
point.<BR><BR> <BR><BR>Thanks,<BR><BR> <BR><BR>Craig<BR><BR> <BR><BR>________________________________<BR><BR>From:
<A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A><BR>[mailto:cisco-voip-bounces@puck.nether.net]
On Behalf Of Lelio Fulgenzi<BR>Sent: Monday, December 13, 2004 4:51 PM<BR>To:
<A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>Subject:
Re: [cisco-voip] CM 4.1<BR><BR> <BR><BR>We are planning on going from
3.3(3)sr4a to 4.1(2)srX in April. It's<BR>rumoured 4.1(3) will be out at that
time, but we won't have had enough<BR>time to test to implement
that.<BR><BR> <BR><BR>The biggest problem will be that you have to read
all the release notes<BR>from your version and on. Going from 3.3(4) poses a
bit of an issue,<BR>since there were features released in 3.3(4) that were not
included in<BR>4.0(x). You'll have to check with your Acct.Team/TAC to make
sure that<BR>every new feature you are using in 3.3(4) is included.
<BR><BR> <BR><BR>One problem we will face is the asthetic difference on
the phones for<BR>the new loads. What makes it more difficult is that many of
those<BR>difference are not documented (nor does it sound like they will
be).<BR>I've got a case open with the TAC to confirm whether or not these
were<BR>missed or simply not documented. And if not documented, what is
the<BR>chance of documenting these in the future. We can't be expected
to<BR>upgrade phone loads without being prepared for whatever differences
they<BR>may bring. For example, I'm upgrading to the latest 7912 firmware and
it<BR>changes the menu spacing which forces the directory application off
to<BR>the next page. <BR><BR> <BR><BR>I'm hoping the list will share any
'gotchas' during/after the upgrade<BR>process. One I know of is that voicemail
ports are handled a little<BR>differently and require reconfiguration before
voicemail access is 100%<BR>available after an
upgrade.<BR><BR> <BR><BR>-----<BR>-----<BR>Lelio Fulgenzi, B.A.<BR><A
href="mailto:lelio@uoguelph.ca.eh">lelio@uoguelph.ca.eh</A><BR>Network Analyst
(CCS)<BR>University of
Guelph
FAX:(519) 767-1060 JNHN<BR>Guelph, Ontario N1G
2W1
TEL:(519)
824-4120<BR>x56354<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>^^<BR>
remove the 1st letter of the canadian alphabet from my email, eh!<BR><BR>-----
Original Message ----- <BR><BR>From: Voll, Scott <<A
href="mailto:Scott.Voll@wesd.org">mailto:Scott.Voll@wesd.org</A>>
<BR><BR>To: <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
<BR><BR>Sent: Monday, December 13, 2004 5:40 PM<BR><BR>Subject: [cisco-voip]
CM 4.1<BR><BR><BR><BR>Anyone on the list using CM 4.1? Did you upgrade
from 3.3.4?<BR>If so,<BR>any problems upgrading? I'm going to upgrade as
soon as it<BR>comes off<BR>limited deployment.
<BR><BR>Thanks<BR><BR>Scott<BR><BR><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR><BR><BR><BR><BR><BR>***********************************************************************<BR>NOTICE:
This electronic mail message and any attached files are
<BR>confidential. The information is exclusively for the use of the
<BR>individual or entity intended as the recipient. If you are not the
<BR>intended recipient, any use, copying, printing, reviewing, retention,
<BR>disclosure, distribution or forwarding of the message or any attached
<BR>file is not authorized and is strictly prohibited. If you have
received<BR><BR>this electronic mail message in error, please advise the
sender by reply<BR><BR>electronic mail immediately and permanently delete the
original <BR>transmission, any attachments and any copies of this message from
your <BR>computer
system.<BR>***********************************************************************<BR><BR></BLOCKQUOTE></BODY></HTML>