Hi, guys!
Good day to you!
This topic describes the solution to unable to create new SIP UAs in eSpace U1960.
Issue Description
The customer has an eSpace U1960 PBX with firmware version V200R003C00SPC700B010.
Each SIP UA created "consumes" (1) license, usually if deleted via eSpace web GUI this immediately "free" a user license, allowing a new extension to be created. Customer deleted extensions via CLI interface of U1960 - eSpace WEB GUI now shows a total of 478 users created. However, license information shows 500/500 licenses consumed & he is unable to configure new extensions.
Below are the informational screenshots from the customer:
Handling Process
After a close investigation in our lab environment, it seems that the customer did not apply the recommended steps in deleting the SIP UAs from Huawei eSpace U1960.
As we know, that every subscriber has associated a SIPUE. When you remove the SIP UA from the CLI you also need to remove the SIPUE associated with the SIP UA on the web GUI of eSpace PBX.
Please refer below to the correct way in removing a subscriber:
Below we have the license status of our lab U1911:
From a total of 5 users configured we want to exemplify how to correctly remove it and then check the status also in the CLI. Below is a screenshot from the GUI and another one from the CLI (screenshots taken before the removal):
The only and proper operation is to delete the subscribers only from the web GUI instead of CLI.
NOTE:
Please note that the operation of removing the SIPUA from GUI automatically removes the SIPUE associated with it.
In the CLI you are only able to delete the SIPUE and not the SIPUA, therefore if the SIPUE is removed on the CLI, the associated SIPUA will still occupy a license slot in the web GUI and this is the reason why another new user cannot be added (if you are at the limit of the license resources).
After deletion will show like this
Verification can be done by running the command "show sipue" over CLI, and you will observe that the SIPUE is not there anymore:
Testing phase. Moreover, in the latest firmware version, the R&D Team developed the CLI command "config delete sipue eid" which is a way to prompt you that you need to delete the SIPUA (subscriber) first, just to avoid these types of situations, as per the below example:
Root Cause
You need to know that for this operation you also need to delete the sipue and not only the UA subscribers from the CLI.
That is why you cannot add any other subscribers.
Every subscriber added is associated with a SIPUE, and when you remove a sip UA you also need to remove the issue of it.
Solution
The only and proper operation is to delete the subscribers only from the web GUI instead of CLI.
NOTE: Please note that the operation of removing the SIPUA from GUI, automatically removes the SIPUE associated with it.
In the CLI you are only able to delete the SIPUE and not the SIPUA, therefore if the SIPUE is removed on the CLI, the associated SIPUA will still occupy a license slot in the web GUI and this is the reason why another new user cannot be added (if you are at the limit of the license resources).
Thanks for reading!
