![]() Check Audit.log and make sure that the username and domain used for the login attempt are correct. ![]() Login failed with wrong username, domain, and/or password message, you should check following point. If Jabber Client doesn’t register even Default Zone set to “Treat as Authenticated”, then highly suspect there is other misconfiguration on provisioning setting. If you have properly configured VCS and TMS provisioning and have valid account (but have an issue with user authentication), Jabber Video client should register. What happen if you change Default Zone configuration on VCS Control to “Treat as Authenticated”?Ĭhanging this parameter to “Treat as Authenticated” will skip user credential authentication and proceed subscribe request, transmitting notify message with provisioning information, then proceed registration request from client. How can i solve this auth problem?ĭefault Zone on VCS Control should configure as “Check Credentials” to VCS to challenge user authentication by using provisioning DB replicate from TMS.ĭefault Subzone on VCS Control should configure as either “Check Credentials” or “Treat as Authenticated”.įor VCS Expressway, both Default Zone and Default Subzone should configured as “Do not check credentials” if provisioning DB sync between VCS Control and TMS (VCS-E forward subscribe request to VCS-C and VCS-C to handle provisioning process). I don´t understand why both source and destination ip addresses are 127.0.0.1. I am trying to get access through jabber video 4.4 but i always getting login failed, wrong user or password ![]() I have a VCS expressway (X6.1) and VCS control (X6.1), i have followed a cisco document to configure those devices.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |