As far as I can see, AD authentication doesn't have an option to restrict it to a specific group, meaning that all AD users will be able to authenticate if they are using a simple SIP client with NTLM authentication because this connection would bypass TMSPE.
If I am using the H.350 authentication then there is an option to restrict it to a specific group, however, in this case passwords need to be stored in the LDAP as clear text and VCS will not use AD username nor AD password. So this option seems useless as well.
Is there a way to configure authentication on the VCS in such a way that it would be limited to a certain group in the AD/LDAP, check against AD username and password and work without relying on the provisioning server?
I want users with other than MOVI clients, any SIP client to be exact, to be able to authenticate using their own username and password stored in AD and I want those users to belong to a certain group. Is that an option at all?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...