How do I free up a license from a deleted IP phone?

[jburggraf]

I deleted an IP phone from one of our 3300 MXe III systems using the User and Device Configuration form. However, when I attempt to add the same device back into the system, I get an error indicating that I have no available licenses. When I check the License and Option Selection form, I see that the Locally Allocated and Locally Consumed both = 37, with Available for Allocation = 0. How do I free up the license from the device that was deleted from the system?

 

[augustD2]

When you delete the IP Phone, the extension become free.

 

[nekminnit]

From the license and option selection form > Change > Retrieve Licenses

That might apply any recent licenses to your controller

 

[kwbMitel]

I've seen systems allow over allOcation

More than likely you had 38 programmed before deleting

**********************************************
What's most important is that you realise ... There is no spoon.

 

[jburggraf]

Nekminnit: I tried your suggestion but no change.

kwbMitel: I actually just checked and I only have 35 devices programmed (one is a SIP device), but the system shows that I have 37 licenses - all allocated.

 

[augustD2]

You can try in maintenance the command:

SYSTEM TOTALS

 

[jburggraf]

p011406: I did the command and got the following:

TOTAL TRUNKS 5 TOTAL STATIONS 36
TOTAL ATTENDANTS 0

Embedded ASU LS Trunks 5

IP Stations 36


Not sure why, given this information, my license information shows 37 allocated?

 

[augustD2]

How many IP device do you see in the form : IP Telephone - ALL

You can check your database to make sure there is no error:

In Maintenace:

DBMS CHECK FULL

 

[jburggraf]

p011406: The IP Phone count is 36 and matches in both the "IP Telephones" form and the "User and Device Configuration" form. (As a reminder, we have 37 IP Licenses and 37 shown as being allocated). However, here are two pieces of information that may impact licensing (??):

A. One of the IP Phones does not physically exist in this building - it is a resilient set that resides in another building served by its own 3300.

B: One of the IP Phones is a "Generic SIP Phone".

 

[jburggraf]

p011406: Ooops... I forgot to mention that the DBMS CHECK FULL resulted in no errors detected.

 

[augustD2]

What is your software rls?

 

[jburggraf]

It is a 33300 MXe III running release 5.0

 

[augustD2]

These are all the things that need a licence:

IP phone user (SIP or Minet)
CITELink phone
Wireless phone (SpectraLink)
Wireless phone (IP DECT - EMEA)
5602 or 5606 Wireless Handset (IP DECT - Global)
Hot Desk user
Unified Communicator Mobile (One IP device license and one IP user license for each line monitor, call agent, and TUI agent used in the Unified Communicator Mobile Server)
Unified Communicator Advanced Softphone
NuPoint
Teleworker
Customer Interaction Solutions (One IP user license per port to 3300 ICP)
Speech Server
Messaging Server

 

[jburggraf]

This is all informational but I am still not able to activate a 37th phone even though I have 37 licenses. What is required for the resilient phone?

 

[kwbMitel]

Resiliency no longer requires any licensing

Other than a console, I cannot think of any device that would consume a license and not appear in the user and config form

Have you manually counted all devices in user and config?

Have you not counted any for any reason? e.g. Analog Main Board extensions

**********************************************
What's most important is that you realise ... There is no spoon.

 

[jburggraf]

I physically counted everything that has a device type listed and only have 36. I do have a ring group in this 3300 - no device type, but does that by chance take up any licenses? I'm grasping at straws I know...

 

[wireman50]

Would it be worth doing a database save and restore? Even though it is showing no errors.

Anything showing in unprogrammed telephones?

 

[slapin]

Also a system reboot may help. The numbers which come from the database may not be the same as stored by the application in memory.
Also the system log should have some sort of a message explaining what it does not like.