Call Failed - Cisco TELEPRESENCE MANAGEMENT SUITE PROVISIONING - TROUBLESHOOTING GUIDE 13.0 Troubleshooting Manual

Could not find server in DNS
Look at Audit.log. Did Movi receive provisioning data from server before the error occurred?
If the error occurred before receiving provisioning data, make sure that Movi is trying to connect
to the correct VCS. This is configured in Movi's Advanced settings, but can be read from
Audit.log. If a setting has not been configured, Audit.log will note it as <empty>.
If the error occurred after receiving provisioning data, go to Systems > Provisioning >
Directory and verify that the SIP Server Address configuration is present and correct.
Go to Administrative Tools > TMS Agent Diagnostics and verify that replication between the Cisco
TMS and Cisco VCS works by running Verifies that users created on the Local TMS Agent
replicates to all the TMS Agent LDAP databases in the cluster.
Unable to connect to server
Look at Audit.log. Did Movi receive provisioning data from server before the error occurred?
If the error occurred before receiving provisioning data, make sure that Movi is trying to connect
to the correct VCS. This is configured in Movi's Advanced settings, but can be read from
Audit.log. If a setting has not been configured, Audit.log will note it as <empty>.
If the error occurred after receiving provisioning data, go to Systems > Provisioning >
Directory and verify that the SIP Server Address configuration is present and correct.
On the VCS, go to VCS configuration > Protocols > SIP > Configuration
Verify that TCP and TLS are both set to On.
Make sure Cisco VCS is listening on the ports Movi is trying to access, by default 5060 for TCP
and 5061 for TLS.
Go to Administrative Tools > TMS Agent Diagnostics and verify that replication between the Cisco
TMS and Cisco VCS works by running Verifies that users created on the Local TMS Agent
replicates to all the TMS Agent LDAP databases in the cluster.

Call failed

Your call was denied due to mismatching encryption settings
In Movi's Advanced settings, the Transport options are Auto, TLS, and TCP. The default setting in Movi
is Auto. If the caller or the receiver has TLS enabled and the other party uses TCP, the call will fail. This
problem can only be solved by changing the Transport setting for either party.
The user could not be found. The user is offline or does not exist.
The user has probably either:
tried to reach someone who is currently offline
mistyped a SIP address
tried to reach someone not available in their network
The user could not be found
Check the Cisco VCS routing configurations.
The user could not be reached. Please try again later.
The user did not respond.
Cisco TMS Provisioning Administrator Guide
Movi troubleshooting
Page 10 of 16