This is very helpful. Thanks. I was worried I’d have to worry about this, but for now, it looks like I don’t have to.
Awesome sauce! From: Anthony Holloway <avholloway+cisco-v...@gmail.com> Sent: Monday, January 13, 2020 5:02 PM To: Lelio Fulgenzi <le...@uoguelph.ca> Cc: voyp list, cisco-voip (cisco-voip@puck.nether.net) <cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] setting primary phone for Jabber users without a physical phone - licensing You mentioned Primary Phone, so I thought I understood you, but I guess not. "If I'm not mistaken, in this case, and, in any case where a primary phone is not set, more licenses are used then would need to be." The primary phone field does not play a role in licensing anymore. It's simply the owner user id set on the phone. As for the workings of UCL: 1 device (regardless of user association) = 1 enhanced* 2 devices with 1 user = 1 enhanced plus 3 - 10 devices all with 1 owner user id = 1 cuwl 11+ devices all with 1 owner user id = 1+ cuwl (e.g., 34 devices + 1 user = 4 cuwl) *unless you purchased a cheap phone, then it might be basic or essential Don't forget the borrowing that happens, so technically, a single device with no user could consume a cuwl license. E.g., Anthony with no physical phone but does have: CSF + BOT + TAB + TCT will consume 1 cuwl license, with no primary phone set, just the owner user id on all 4 devices. On Mon, Jan 13, 2020 at 2:13 PM Lelio Fulgenzi <le...@uoguelph.ca<mailto:le...@uoguelph.ca>> wrote: Yes, no DLUs, but there’s still licenses. So, what I was afraid of was that instead of one CUWL license, it would use 4 separate enhanced licenses. But, I’m guessing because it’s all one userID, it uses the license based on the number of devices. So, if I have 4 Jabber devices to one userID, it uses CUWL, but if it uses 2 jabber devices, it uses enhanced? From: Anthony Holloway <avholloway+cisco-v...@gmail.com<mailto:avholloway%2bcisco-v...@gmail.com>> Sent: Monday, January 13, 2020 2:39 PM To: Lelio Fulgenzi <le...@uoguelph.ca<mailto:le...@uoguelph.ca>> Cc: voyp list, cisco-voip (cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>) <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>> Subject: Re: [cisco-voip] setting primary phone for Jabber users without a physical phone - licensing We have *not* had DLUs since... On Mon, Jan 13, 2020 at 1:38 PM Anthony Holloway <avholloway+cisco-v...@gmail.com<mailto:avholloway%2bcisco-v...@gmail.com>> wrote: I might be saying something completely crazy here, but the Primary Phone field does nothing for you ever since CUCM 9x User Connect Licenses (UCL). Here's what the help says for that field: Choose the physical phone that will be associated with the application, such as IP communicator or Cisco Unified Personal Communicator. When you choose a primary phone, the application consumes fewer device license units and is considered an "adjunct" license (to the primary phone). We have had DLUs since 8x, so, unless you're on version 8.x, you can ignore this field. On Mon, Jan 13, 2020 at 12:29 PM Lelio Fulgenzi <le...@uoguelph.ca<mailto:le...@uoguelph.ca>> wrote: I'm trying to setup an easy to replicate (troubleshoot/reconcile) system in place for our Jabber deployment. We've decided to assign each Jabber device type to each user so there's no end-user support issues when they want to use it on another device and/or move from one device type to another. If I'm not mistaken, in this case, and, in any case where a primary phone is not set, more licenses are used then would need to be. The issue at hand here, is what happens when we deploy Jabber without a physical phone? I'm already finding that the quick/add feature really only works when a phone is configured (although I have to work through that). So, I'm wondering, is it worthwhile to configure a "dummy" phone for Jabber users and set the primary phone for all Jabber clients to this dummy phone? Or should I ask them to pick the CSF jabber device as the primary phone for example? What have others done? Lelio _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
