Hi, I'm looking for some assistance as we start to add 5520's and 8.2 code to our 5508 environment running 8.0 code.  We have 3 campuses with 10 buildings and 8 5508's.  AP's have L2 access to controllers and we have a centralized anchored guest network.  We allow / want roaming on each campus. In reading the 8.2 release notes it talks about new mobility.  The notes and/or TAC state that the 5508 will only support new mobility as an anchor and not a foreign controller.  They stated that the 5520 cannot act as a mobility controller in the new mobility mode and they also state the 5508 cannot function as a mobility controller. FYI we have some Catalyst 3850's in our environment, but it's mostly 3750's.  We do not plan to use these for MC or MA functions at this time. It's confusing as to what is possible and have yet to find documentation that explains this well enough to understand how to phase in 8.2 code and 5520's.  Does anyone have any experience with this and recommendations? Also, aside from this - in a campus environment does it make sense to centralize controllers and move AP's from local mode to FlexConnect? This could be a whole other posting, but maybe it can be limited for now to whether or not it plays a part in how we configure mobility and upgrade our environment. Thanks, Jason ... View more

I'm testing CUCM 9.0.1 and had a phone from a 8.6 environment I placed on the system.  When the phone runs the upgrade it gives an "Auth Failed" messasge.  From what I understand the phone may need an intermediate phone load version to upgrade to?  Is this documented anywhere?  I have uploaded the 9-2-3 phone load cop file and that upgrades fine, then I edit the device load information and change it to 9-3-1-1 which ships with CUCM 9.0.1 and it again fails. I also have a 9951 phone that states it has the 9-3-1-33 load on the inactive load and 9-2-1 on the active.  However, this phone acts dead, although it shows up as unregistered with an IP address I can ping. Jason ... View more