Register Jabber Viceo client to VCS/TMS

[born.jason]

Hi,

i`m trying to register a jabber video client to VCS and/or TMS but its not working. Every time i got

"Wrong username, domain, and/or password." Check spelling and Caps lock.

Don`t know why. What steps do i have to do to register a client with username and password? VCSc and VCSe are configured for access from inside and VCSe from outside.

Is there a guide for Jabber Video clients?

Best regards

Jason

[Martin Koch · Accepted solution]

Hi Jason!

You need either a VCS-Expressway starter pack or TMS (licensed + Movi licenses) and a VCS (with the device provisioning option key).

As you write VCSe and c its most likely that you do not have the starter pack.

It also needs configuration and user creation, so it would not work just out of the box.

The recommended way is the TMSPE, you find the deployment guide here:

http://www.cisco.com/en/US/docs/telepresence/infrastructure/tmspe/install_guide/Cisco_TMSPE_Deployment_Guide_1-0.pdf

If you have older TMS/VCS versions you might need to use this (but I would recomend upgrading and use TMSPE!):

http://www.cisco.com/en/US/docs/telepresence/infrastructure/tms/config_guide/Cisco_TMS_Provisioning_Deployment_Guide_13-0.pdf

Besides that check out the Cisco documentation for TMS, VCS and JabberVideo.

TMS:

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

VCS:

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

JabberVideo:

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

Jason: Please rate the postings and set the thread to answered if it is!

[born.jason]

Hi Martin,

i have all that keys and options like you mentioned.

i have now followed your first step.

The recommended way is the TMSPE, you find the deployment guide here:
http://www.cisco.com/en/US/docs/telepresence/infrastructure/tmspe/install_guide/Cisco_TMSPE_Deployment_Guide_1-0.pdf

I have setup all but i cannot login internal/external.

Lets  try first to log in internally. In the Jabber Video client i have added  the IP of the VCSc, and i hav added the VCSc to the TMS.

Where should i look now for troubleshooting?

[born.jason]

Ok.

now i see "Did not receive provisioning in time" on the Jabber Video Client.

Under "System -> Provisioning -> Devices" i see the Movi device

But if i check the user there is no configuration template assigned and i`m not able to assign a template to the group because i got the error:

But i don`t know where i have to look what server error it is

Any suggestions?

Is this maybe the error that the Video Client cannot log on?

[born.jason]

Ok Martin. i have solved this ->

https://supportforums.cisco.com/thread/2160025

I`m now able to log in internally.

What are the steps to login from external?

VCSc and VCSe are configured to work together but how do i say express to send registrations to VCSc ?

[Jens Didriksen]

Take a look at this guide:

http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Authenticating_Devices_Deployment_Guide_X7-2.pdf

/jens

[born.jason]

Thanks Jens.

I think i miss ome little think but i don`t know what? Do i need a search rule for registration from vcs e to vcs c?

Could you both tell me in short the steps that movi clients an register to TMS through VCSe -> VCSc -> TMS ?

[Tomonori Taniguchi]

Assume provisioning DB run on VCS-C and VCS-E will proxy provisioning request from Jabber Video on external network to VCS-C (also Jabber Video on external network will register on VCS-E).

Then…,

• VCS-E must have a search rule that allow to send subscribe message to VCS-E. For example, search rule with regex “.+@(%localdomains%)” pointing to VCS-C
• VCS-E must have SIP domain configuration and disable “SIP registration proxy mode”
• Authentication policy for Default Zone on VCS-E should configured as “Do not check credential”.
• Authentication policy for Default Zone and Traversal Zone (to VCS-E) on VCS-C should configured as “Check credential” and Default Subzone as either “Check credential” or “Treat as Authenticated”.

With these configuration, Jabber Video on external network which contacting VCS-E able to provisioning on VCS-C via VCS-E.

[born.jason]

Thanks.

How could i verify that VCS-E will proxy provisioning request from Jabber Video on external network to VCS-C ?

[Tomonori Taniguchi]

There is several methods to verify it, but easiest method will be to check SIP message by taking diagnostic log.

Take a diagnostic log (operation is available from Web GUI under > Maintenance > Diagnostic logging.

From VCS-E diagnostic log, you should expect to see incoming SUBSCRIBE SIP message from Jabber Video client and message forward to VCS-C (IP address of VCS-C NAT address).

From VCS-C diagnostic log, you should expect to see incoming SUBSCRIBE SIP message from VCS-E address.

[born.jason]

Hmm such as info. I saw this thread

https://supportforums.cisco.com/message/3794750#3794750

i followed the policys on the picture from Tomonori. But as soon as i configure the DefaultZone on the VCS-C to "check credentials" i cannot logon anymore from inside and outside. If its configured for "Treat as authenticated" i can login from inside.

Maybe this makes the issue more clear  that i`m not able to login from external ?

[Tomonori Taniguchi]

> If its configured for "Treat as authenticated" i can login from inside.
If you configured as “Treat as authenticated”, I believe you should able to login Jabber Video client with different (wrong) password as well…

Definitely something not configured correctly…

[born.jason]

Yes you are right. I tested it and i`m able to log in with wron/without password.

Hmm, if i change to check credentials and its not working. Where should i look first to troubleshoot? :-)

VCS-C is in provisinong mode and i can see all users which are synced with LDAP to TMSPE in VCS-C as users/findme.

So i thought it was already LDAP auth.

[Tomonori Taniguchi · Accepted solution]

Are you importing user account from LDAP server to TMS?

How are you managing password for those account after import the user accounts?

Manually creating on TMS for provisioning account or let VCS to challenge (AD integration by using NTLM)?

[born.jason]

  Here is the Envoirenment:

• Non AD Server as TMSPE Server
• Import User Accounts from AD (LDAP) to TMSPE Server
• VCS-C
  
  • Maintanance - Login accounts LDAP Configuration
    
    • State -> Available (green)
  • VCS Configuration -> Authentication -> Devices -> Configuration
    
    • LDAP Database
    • NTLM -> Auto
  • VCS Configuration -> Authentication -> Devices -> LDAP Configuration
    
    • State -> Active (green)

Do i need more configuration on VCS-C ?

On TMSPE Server i have configured the following:

• Systems -> Provisioning -> Users
  
  • User Import
    
    • User import finished successfully (green)
    • All Users from LDAP are there

Do i missing something for the password creation?