[cisco-voip] CUCM ver 8.x to 10.x licensing conversion

[Erick]

The other thing to keep in mind is CUCM sets the license type used by device/ owner assignment. CUCM currently doesn't use cuwl pro directly. 

Use the license count tool to plan. It will pull data from existing ccm and show you the breakdown in user license types for your 8.x setup and you can adjust.

Typically,

If you have the same owner for 2-10 devices it will use cuwl standard. 

1 phone is enhanced license type 

1 phone , SNR/remote destination profile , jabber csf device is enhanced plus license type with same owner on the 3 devices. 

That's from my experience ... 

What are you guys seeing -- heavy on enhanced plus or cuwl and loaning downward? Just curious now that's it's been awhile. 


Sent from my iPhone

> On Mar 10, 2015, at 3:37 PM, Matthew Loraditch <MLoraditch at heliontechnologies.com> wrote:
> 
> A user being a CUWL user is based on the Owner User ID field alone. The user could have 10 extension on 10 different phones. As long as the user is the owner  of all those phones you are legit.
>  
> From a completely technical standpoint the system calculates only on that field and doesn’t care about anything else. You can have a dummy user own 10 phones and from an ELM/PLM standpoint be ok. Now that wouldn’t be licensing legit and shouldn’t be done as anything but a temporary workaround.
>  
> Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA
> Network Engineer
> Direct Voice: 443.541.1518
> 
> Facebook | Twitter | LinkedIn | G+
>  
> From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Countryman, Edward
> Sent: Tuesday, March 10, 2015 4:15 PM
> To: Cisco VOIP
> Subject: [cisco-voip] CUCM ver 8.x to 10.x licensing conversion
>  
> We are in the process of planning our upgrade from 8.6 to 10.5 which means we need to plan for a conversion of our DLU’s to the new licensing model.
>  
> Does anyone know if a CUWL user license has to have the same extension on all of their devices? 
>  
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150312/4c13a3e4/attachment.html>