Un-associate Jabber devices from CURRI using stonelock while locking IP Phone with the same line
Stonelock configured in CURRI
For some customers, it is required to lock IP Phones only and not locking the Jabber as it is accessed remotely
It is required to lock the IP Phone only and not locking the Jabber as it is accessed remotely.
The best trick is to create 2 different CSSs and include Jabber devices to a different CSS than the IP Phones.
In the Sharedline the CSS should be set as "NONE"
However, choose the related CSS in the Device itself (for Jabber and then for the IP Phone)
Create two similar Route Patterns.
One of which where the IP Phone CSS is chosen, enable the ECC (CURRI), leave the other as "none"
This article was:
Thank you for your feedback!
|FAQ and Solutions||Configure Cisco ECC Curri to use HTTPS|