<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
Hi Lelio,
<div><br>
</div>
<div>I believe the provisioning improvement you are referring too is the ability for end users to ‘self-provision’. My understanding it enables end users to setup a fresh phone on their desk as part of an initial deployment etc. basically a replacement for
TAPS. They login to their phone using their UCM User details (aka AD user if integrated) and a pre-loaded profile is deployed to the phone.</div>
<div><br>
</div>
<div>ASAIK it’s a phone firmware level feature that as long as the phone is on the desired software level it uses the new User Data Service (UDS) API to authenticate and configure the device.</div>
<div><br>
</div>
<div>Personally I’m keen to see how this feature is implemented, i.e. will the user have to login twice if extension mobility is enabled ;)</div>
<div><br>
<div apple-content-edited="true">
<div style="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-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
<div style="font-size: 12px;">Kind Regards.<br>
<font color="#0f61c8"><br>
</font><span style="font-size: inherit; orphans: 2; text-align: -webkit-auto; widows: 2; ">Stephen Welsh</span></div>
</div>
<span style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><br class="Apple-interchange-newline">
<span><img height="16" width="100" apple-inline="yes" id="098E31D4-FC02-4FA5-9A92-BFB0656A516F" apple-width="yes" apple-height="yes" src="cid:image001.png@01CEAFE6.C53903B0"></span>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; 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; -webkit-text-stroke-width: 0px; text-align: start;">
<br>
</div>
</span></div>
<div>
<div>On 20 Jan 2014, at 14:39, Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div style="font-family: verdana, helvetica, sans-serif; font-size: 10pt;">Yup, I totally hear ya there. It did sound genuine though. They basically said they've done themselves a disservice with their new numbering scheme, with people staying away from "dot
oh". Oh well. What are ya gonna do?<br>
<br>
Apparently there are going to be some provisioning improvements in v10, but I'm not sure what those will entail. No data sheet out yet, but the front page of v10 mentions: "Offering end-user self-provisioning and self-care"<br>
<br>
<div><span name="x"></span>---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst, Network Infrastructure<br>
Computing and Communications Services (CCS)<br>
University of Guelph<br>
<br>
519‐824‐4120 Ext 56354<br>
<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a><br>
<a href="http://www.uoguelph.ca/ccs">www.uoguelph.ca/ccs</a><br>
Room 037, Animal Science and Nutrition Building<br>
Guelph, Ontario, N1G 2W1<span name="x"></span><br>
</div>
<br>
<hr id="zwchr">
<div style="font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica, Arial, sans-serif; font-size: 12pt;">
<b>From:<span class="Apple-converted-space"> </span></b>"Ted Nugent" <<a href="mailto:tednugent73@gmail.com">tednugent73@gmail.com</a>><br>
<b>To:<span class="Apple-converted-space"> </span></b>"Lelio Fulgenzi" <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>><br>
<b>Cc:<span class="Apple-converted-space"> </span></b>"Scott Voll" <<a href="mailto:svoll.voip@gmail.com">svoll.voip@gmail.com</a>>,
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Sent:<span class="Apple-converted-space"> </span></b>Sunday, January 19, 2014 12:59:46 PM<br>
<b>Subject:<span class="Apple-converted-space"> </span></b>Re: [cisco-voip] CM 8.6 to 9.1<br>
<br>
<div dir="ltr">
<div><font face="arial, sans-serif">I've heard that speech from Cisco AMs and SEs every X.0 release and I end up having to talk reality to customer that had a bit to much coolaid for the week .. </font><span style="font-family: arial, sans-serif;">I learned
my lesson</span><span style="font-family: arial, sans-serif;"> with 4.0...</span></div>
<div><span style="font-family: arial, sans-serif;">My clients don't need to be a test bed for Cisco, we'll wait until a few SRs are out or until 10.1</span></div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Sat, Jan 18, 2014 at 4:24 PM, Lelio Fulgenzi<span class="Apple-converted-space"> </span><span dir="ltr"><<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>></span><span class="Apple-converted-space"> </span>wrote:<br>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;">
We are planning on moving from v7 to v9 in April, ahead of the UCCx v7 EOS date.<br>
<br>
I'm planning on using a modified jump upgrade, going from MCS (equivalent) servers to MCS (equivalent) servers.<br>
<br>
I've prepared my offline network with the servers required, i.e. NTP, DNS, sFTP, etc. I don't have AD, so I will simply turn on AD sync.<br>
<br>
I'm currently working on a rough migration and blackout test plan. Once I've got those hammered down, I will share with the list for comment.<br>
<br>
We were strongly encouraged to go to v10, but third party interoperability (as well as CUE) prevents us from doing so. I had the same concerns of going to a dot oh release, but our account team commented that the versioning has changed the concept, ten dot
oh, is not necessarily a rewrite, or has huge changes. I was 'this' close to asking, then why do I need UCSS for it? ;)<br>
<br>
<br>
<br>
Sent from my iPhone<br>
<div>
<div class="h5"><br>
On 2014-01-17, at 11:44 PM, Scott Voll <<a href="mailto:svoll.voip@gmail.com" target="_blank">svoll.voip@gmail.com</a>> wrote:<br>
<br>
> how many people have made the switch to 9.x?<br>
><br>
> I hear a lot about ELM. But how bad is it?<br>
><br>
> we are looking at going from physical servers to VM's. we would like to do the "jump" upgrade were we build the new VM's and migrate users over. Have people been doing this? how has it worked. What are things that were gotcha's? Are you glad you upgraded?<br>
><br>
> I'm not a fan of going to a x.0 release but would it be good to look at 10.0?<br>
><br>
> TIA<br>
><br>
> Happy Weekend<br>
><br>
> Scott<br>
</div>
</div>
> _______________________________________________<br>
> cisco-voip mailing list<br>
><span class="Apple-converted-space"> </span><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
><span class="Apple-converted-space"> </span><a 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 href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
</div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
https://puck.nether.net/mailman/listinfo/cisco-voip</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>