Снятие блокировки с приложения JTAPI:
http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-contact-center-express/91203-mutex-lock-error.html
Note: You need to log into the DC Directory Manager as a Directory Manager in order to make the necessary changes. //иначе не будет прав на редактирования, ошибкок впрочем тоже выдаваться не будет, прекрасный повод потупить.
-
In the DC Directory LDAP, choose CCN Apps > clusters >
[profile] > Locks > Locks.00000000 and confirm that
these mutex lock entries are named as this list shows:
lockApplicant?empty
lockOwner?empty
lockUsage?empty,
lockUserInfo?empty
lockUserTimestamp?empty
2.If any of the entries in step 1 are missing the ?empty suffix in their name, then they need to be renamed to exactly match the list in step 1.
Note: You can ignore the lockExpiration entry. It does not need the ?empty suffix in the name.
3.If any of the lock____?empty entries are missing completely, you must add them manually. In order to add the entry, complete these steps:
Note: The lockApplicant?empty value is used for illustration purposes only.
a.Right-click on Locks.00000000 and select New > ciscoCCNocConfigInfoCES.
b.Enter the name as lockApplicant?empty and press Enter.
c.In the next window, click Add and enter x in the Enter String value box. Then click OK.
d.Click OK again.
4.Once you have confirmed that all of these entries are named properly, confirm that these entries have the value configured as x (lowercase x):
lockApplicant?empty
lockOwner?empty
lockUsage?empty,
lockUserInfo?empty
lockUserTimestamp?emptyNote: Ignore the lockExpiration entry in this step. Its value should not be x.
If any of these lock entry values is not configured as x, then configure them as x.
for information.