We have deployed the vcs control and expressway solution. For some users the movi client after login disconnects within 5 minutes and takes a long time to reconnect back. All the users are connecting to movi client from the internet segment. users are getting the message "provisioning not received in time" Checked the tms agent diagnostics every thing is fine.
Has any body faced this disconnect problem. The vcs control is runing 6.1 and tms is 13.0. movi client is 4.2.
This happens for some users who are login from their home broadband connection. Also when two movi users connect from home and place a call between themselves, call is getting disconnected. This problem does not exist between movi and e20 or ex90.
does the initial Movi login always succeed, in that the client disconnects after some time, or are you also having problems logging in initially?
Does the eventlog on the VCS-E and/or VCS-C show any entries which might relate to this issue, e.g "Endpoint unresponsive" or any events relating to the traversal zone between the VCS-C and VCS-E?
The symptoms which you describe are usually related to network issues, in which case I'd recommend to get a TAC case opened, since it is likely that logs will have to be collected to get to the bottom of the problem.
We had the same problem with users who were home workers.
The problem we had was the home workers were connecting on VPN back to the office and the MOVI traffic were going through the VPN - Through the Corp Network and then out to the VCSE. Have the home workers disconnect from VPN and try to connect again, I bet this works.
Also to note - If the user disconnects from VPN, connects successfully on MOVI then re-connects to VPN, MOVI will eventually timeout.
I would suggest allowing Split Tunnelling over VPN.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.