VCS/AD/MOVI Authentication Questions

Answered Question
Apr 17th, 2012

Hey all,

Got a customer with X6.1 on his VCS-E & VCS-C.  MOVI was working perfectly fine.  We then added the VCS-C to the domain and enabled NTLM authentication.  MOVI still works using the new AD credentials, however we have (2) issues.

(1) Customer was using MOVI v4.2 and everything works fine.  Customer downloads Jabber v4.4 and they can no longer log in.  Looks like it does not even query the VCS-C, seems to jump right to the VCS-E.

(2) When MOVI v4.2 or Jabber v4.4 try to connect to the VCS-E they are unable to authenticate.  What are the required auth zone policies for the VCS-E & VCS-C when using the NTML authentication?



I have this problem too.
0 votes
Correct Answer by Alok Jaiswal about 3 years 7 months ago

Hi Justin,

check the other threads on the CSC. To answer your queries:

case 1: if the Jabber is not able to get a reply in the definite timeperiod then it will  jump to expressway.

case 2:  check the below links



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Justin Ferello Tue, 04/17/2012 - 10:04


Thanks for the information.  Your link did answer question (1) but I am still trying to work thru question (2).  I understand that it will timeout and go to the VCS-E.  The question is why MOVI v4.2 connects right away to the VCS-C but Jabber v4.4 times out on the VCS-C and then connects fine via the VCS-E.



Alok Jaiswal Tue, 04/17/2012 - 10:27

Also for testing purpose forcenosrtp parameter to verify the wireshark logs.



This Discussion