[cisco-voip] Feature Request to fix Licensing issues with EM

Tim Smith tim.smith at enject.com.au
Sun Sep 27 21:15:22 EDT 2015


Could it be simpler?

You have 1000 UCL standard users and 500 phones
Phone licensing is in credit essentially here, so it doesn’t even need to count them

You have 500 UCL standard users and 1000 phones
User licensing doesn’t cover the phone count, you’d need to add either 500 more users, or the additional 500 phones are lobby / anonymous types (truly common space – not extension mobility phones)
Might be more realistic if this was something like 900 users and 1000 phones.

Cheers,

Tim.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Scott Voll
Sent: Friday, 18 September 2015 4:29 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Feature Request to fix Licensing issues with EM

OK, everyone has complained about the licensing nightmare that EM plays in CM 9 and 10.

My coworker has come up with a fix......


In thinking this all through, I thought about how I would like it all to work mechanically.  Here is what I would like to request as a Feature/Enhancement Request:

When I log into a device for the first time with Extension Mobility, I am assigned as the device owner.  That ownership is retained until one of two things happen:
1.        I log into another like device (i.e.: I have a 8861 at my desk, and I log into Scott’s 8861 at his desk)
2.        Someone else logged into my device.

This way, the ownership of the device is always assigned by the extension mobility profile and follows the user.  If I have an iPhone, IPad or Jabber or other such device, since those all require a user to log in, the ownership would be added in the same way.  This would mitigate the licensing issues caused by extension mobility (in my opinion).

Using this would really simplify the licensing requirements in my thinking.

Any thoughts?

Thanks

Scott

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150928/19966edd/attachment.html>


More information about the cisco-voip mailing list