-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot connect to CISCO CUCM v.11 #88
Comments
What .NET version are you using? Have you tried the solution from StackOverflow? |
Thank you for reply ForNeVeR. I have targeted all projects in the solution to .Net 4.6.2 as recommended in StackOverflow :"It is worth noting that .NET 4.6 will use the correct protocol by default and does not require either solution." I have not done anything with 'SslStream' and 'System.Net.ServicePointManager.SecurityProtocol' as I am not familiar with these things. Maybe I set incorrectly the login parameters?
-- Tab 1: Basic -- Tab 2: Network -- Other two tab: left the default values
----If I disable SSL I get this error: At this point I am not sure if the values I input are correct. For instance, I didn't figure out whether ActiveDirectoryAndDNSServer is required or not. Thank you, |
Could you try the options mentioned in the documentation? I.e. |
Thank you for suggestion. I was not sure where to implement OnIvalidCertificate, so I took a shortcut and, in the class AsyncSocket, I have modified UntrustedRootOK to return always "true". It didn't work, and, unfortunately I have now to move to other project. Will try to come back to give it another try when I have a little bit of time Thank you for your prompt support! |
I have an environment where Pidgin and Cisco Jabber clients connect to a local Cisco Unified Communications Manager (CUCM) server.
I have then tried to connect to the same Cisco server with Jabber-Net, (JabberNet.Example.exe ) but got this error when hit the button in the login form:
I suppose that this problem is not related to the certificates, because Pidgin and Jabber work fine.
The text was updated successfully, but these errors were encountered: