sign in movi camera

[rashmi.kumari]

Hi,

Please can you resolve a problem of signing in a movi camera with the help of TMS.Which username and password we need to give during sign in?

Thanks for the  reply in advance

Rashmi

[Andrew Vasel]

Rashmi,

Have you provisioned an account under Provisioning Directory (found under Systems)? When you create the account, you can manually create the user ID and password (if not syncing to AD) and send those credentials to the user from that same section in TMS ('Send Account Info').

[rashmi.kumari]

Andrew,

Do we need to do any configuration settings in vcs and tms to run movi cameras?

[Andrew Vasel]

In TMS, you need to enable TMS Agent Data Replication under the TMS Agent tab for the VCS (in other words, enabling provisioning).

Additionally in TMS, under Systems - Provisioning Directory, you create Movi accounts where the SIP server (VCS) is defined.

At a bare minimum on the VCS, you need to enable and configured SIP as well as define a SIP domain.

From Movi itself, you will log in using the credentials created in TMS (under Advanced settings, enter the VCS address or hostname under Internal VCS and enter the SIP domain that you defined on the VCS).

[Martin Koch]

The question is what rashmi really tries to archive, as "movi camera" does not exist, it could also be something

what we do not get right now :-)

If its really related to movi and the provisioning I would strongly recommend reading the VCS, TMS and Movi

documentation:

http://www.cisco.com/en/US/products/ps11337/tsd_products_support_series_home.html

http://www.cisco.com/en/US/products/ps11338/tsd_products_support_series_home.html

http://www.cisco.com/en/US/products/ps11328/tsd_products_support_series_home.html

And then especially the provisioning deployment guide:

http://www.tandberg.com/collateral/documentation/Deployment_Guides/Cisco_TMS_Provisioning_Guide_13_and_12-6.pdf

[rashmi.kumari]

Hi Andrew,

In TMS I am trying to unable TMS agent data replication under tms  agent tab for vcs but i am unable to do so.I have attached the screen  shot of tms.Plz help.

tms ver 13.1

vcs ver X6.0

Regards

Rashmi

[Jens Didriksen]

Do you have the Device Provisioning option key installed on the VCS ?

[rashmi.kumari]

Hi Jens

Yes,Device provisioning option key is installed on the vcs.

[Andrew Vasel]

Rashmi,

Do you have a host name for the IP address of the VCS? You need to add a hostname under the connection tab for the VCS (i.e. hostname.domain.com). Add that and then try to check the box for enabling agent data replication again.

[Martin Koch]

Before flying blind here my recommendation still stands, follow the documentation,

especially check that everything is set up as described in the deployment guide:

http://www.tandberg.com/collateral/documentation/Deployment_Guides/Cisco_TMS_Provisioning_Guide_13_and_12-6.pdf

For example if the pre-requirements are not matched problems are most likely going to occur.

In addition I would upgrade the VCS to X6.1

If you still have issues try to purge the vcs from the tms database and add it again.

(statistics and other settings might get lost when purging a system from TMS)

If you then still have issues, ask here again or escalate the issue to TAC.

If you fixed the issue please let us know what was the cause and how you solved it.

Please vote the answers.

[yusufbudi]

Hi Expert

I have similar problem to enable TMS Agent Data Replication.

when i Submit the save setting I have received the error message

Unable to enable replication for 'vcsc.vcsc.demo'. A DNS lookup of the TMS host name on this VCS does not match the TMS IP address.

please kindly help me

thanks

Yusuf

[Magnus Ohm]

Hi

This message is for a DNS lookup of the TMS server FQDN on the VCS. Make sure the TMS server has a valid A record that is resolvable as well. It should match the FQDN of the TMS server (server name + dns suffix, if the server is part of a domain no more actions would be needed).

Then when you can resolve both the VCS and the TMS hostnames, from the TMS and VCS respectively try to enable replication again.

If it still fails, go to the VCS in TMS (Systems navigator) and select the connections tab and make sure the host name is typed in correctly and that the VCS is tracked by Hostname.

Save and make sure TMS can resolve the hostname, if you can save it succesfully its fine.

If you do any changes to the TMS server name, you have to reboot the server. If it still fails after this, try to reboot the VCS and re-enable replication.