Can't connect Movi to VCS in-house

Unanswered Question
Feb 1st, 2012

I cant seem to get Movi working in-house.  I've got 4.3 (Jabber) loaded on my Dell laptop (Windows 7).  I enter in the IP address of the VCS Control with no luck.  I also use the DNS name of the Control and I get a DNS lookup error.  But when I go to our DNS server, the name is correct.  What am I missing?

Thanks.

Jeremy

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
aljaiswa Wed, 02/01/2012 - 09:33

Hi Jeremy,

Please ignore my previous reply..it was a typo error...

One important thing you didn't tell us is about the deployment scenario for MOVI. You are using provisoning database to authenticate or you are authenticating the MOVI using AD.

Thanks

Alok

jdmickies Wed, 02/01/2012 - 09:38

I did upload the latest XML and created a user with login/password.

Garvan Long Wed, 02/01/2012 - 14:41

Have you specified a SIP server in the Movi provisioning configuration on TMS  ?

jdmickies Thu, 02/02/2012 - 09:16

I spent a couple hours in a WebX with Cisco yesterday and seems there's an issue in the VCS regarding the TMS Agent replication...

Actions

Login or Register to take actions

This Discussion

Posted February 1, 2012 at 6:41 AM
Updated May 16, 2012 at 11:40 AM
Stats:
Replies:5 Overall Rating:
Views:799 Votes:0
Shares:0
Categories: Jabber for Windows
+

Related Content