Jabber provisioning on VCSE

Similar Questions

• Jabber (Internet) video->->->-> Jabber CUCM VCSC VCSE for windows

  First of all, I tried Jabber Video (Intranet)->->-> Jabber CUCM VCSC for windows, video and audio are fine, by establishing a SIP trunk between VCSC and CUCM and Zone rule settings and VCSC research.

  Secondly, Jabber (Internet) Video-> VCSE-> VCSC-> Video (Intranet) Jabber, audio and video are very well by estalishing TraversalZone between VCSE and VCSC, as well as the search area in VCSE and VCSC rule.

  There is an obvious idea comes... Jabber (Internet) video->-> VCSC VCSE-> CUCM-> Jabber for windows.

  I tried by two means:

  Option A: I try through Jabber video (Internet)-> VCSE-> TraversalZone-> VCSC-> SIP Trunk-> CUCM-> Jabber for windows, acutally, there isn't any configuration required in VCSE/VCSC/CUCM, because when you dial [email protected] / * /, the VCSE will route the call to the VCSC and then it will move the call to CUCM, but I couldn't get to this subject, the logging of the VCSC He always showed in the message below:

  1. received VCSC VCSE SIP protocol prompt, call [email protected] / * /

  2 VCSC answered VCSE SIP 407 Proxy authentication required.

  3 VCSE answered the VCSC SIP ACK

  I don't know what is the problem here, or additional configuration required, but the call to certainly VCSC already, but I don't know what is the way of the authentication of 407 proxy here... If the Jabber (Internet) Video-> VCSE->-> Video (Intrante) Jabber VCSC, it isn't this 407 proxy authentication in logging.

  Option b: I'm going through Jabber video (Internet)-> VCSE-> SIP Trunk-> CUCM-> Jabber for windows, with the rule of necessary research, in this way, when Jabber (internet Video) composition Jabber for windows, it sounds, and when picked up, one way audio (from Jabber for windows to Jabber video) set up, no video.

  It is normally an authentication problem. I think that you run a software X7.x on your SPRDD? If so, try to activate "treat as authenticated" on the crossing area 'Authentication policy' (both directions, if it is set to "do not verify the credentials") and see if you get the P - asserted-Identity "authenticated" a header then and make a call from the internet, routed throug the VCS - c to your CUCM.

  Are your rules of research on the VCS - c, the value "request must be authenticated = Yes"?

  Hope this helps,

  Arne

• Internet of Jabber Clients through VCSe calls

  Hi Experts,

  We have provisioned on CUCM 8.6.2 Jabber clients and Movi customers supplied on VCS control (X 7.0) and TMS (13.2.1)

  We will deploy VCSexpressway soon to our society.

  My request is that it will be possible for the Jabber Clients on CUCM to call outside our company. I know Movi would work, but not sure of Jabber clients.

  Could someone help me? If it can work, how it is possible?

  Thank you

  Saurabh

  Slim,

  It should work very well. !! Once you make a call to jabber client that calls flow would be to track Express VCS de VCS control and then again in venture capital control of CUCM on the sip trunk.

  the only thing is that you must develop with the numbering plan so that it should not conflict with other numbering on the vcs control plans.

  Rgds,

  Alok

• MOVI with Mix AD and LDAP authentication?

  Hi all

  Is it possible to configure VCS for authentication in mode mix MOVI.

  I have a situation in which some MOVI users are not in the ad.

  Now I woul like authenticate this MOVI via the local ldap on the highway-VCS database.

  Because I put all subarea them and area on the VCS-E with "verify the credentials" and authenticate the user MOVI via AD, works fine, no problem, but now I have the problem with the no user AD Movi.

  Anbody has any idea?

  any input appreciated.

  Best regards

  Georg

  Hi, George,

  It is possible but you need to use 2 separate VCS - C to do, where VCS - 1 c is attached to the AD domain and configured for NTLM for Video Movi/Jabber authentication requests for commissioning, and where the other VCS - C is configured to use the authentication of local/LDAP database for Video Movi/Jabber provisioning requests.

  In addition, you need to create two separate records in MSD Provisioning directory, where a single folder houses users of the AD and the other folder is home users not AD.

  Finally, you must configure the server setting internal on video Movi/Jabber, so that the AD users get their configuration in the VCS - C service which is configured for NTLM, while users non AD get their provisioning for the non - NTLM VCS - C configuration.

  Now, if you bring a VCS-E in the mixture, so that the two AD and no AD users will be connecting via VCS-E, this will get a lot more complicated, since you would have to somehow ensure that provisioning a user AD request gets by proxy via NTLM - activated VCS - c while queries for configuration of users not AD get by proxy through the non - NTLM VCS - C. This could be done with smart search rules, but that requires that you have a URI scheme for your users to provisioning, which allows you to determine whether or not a request for service comes from a user AD.

  In summary, it is possible, but it adds a significant administrative burden and would probably complicate troubleshooting a bit if it is still necessary and I strongly suggest you try instead of getting all the user provisioning in AD if possible.

  Concerning

  Andreas

• VCSE Jabber presence does not

  Hello

  I have some problems with the presence, through the VCSE for a jabber client registered to one subarea other than failing the VCSE subzone.  In addition the environment uses AD for authentication of the client so the VCSE has the default area, sub-area by default and traversal area set to "do not check references" for auth policy.  When the customer registers to the subarea of default, presence works properly.  When I create a subzone to isolate a specific group of jabber clients, register of customers using their credentials of the AD (checked this incorrect password causes failures) but I get an error 403 policy updates to presence.  I need to create this subarea, so I can use a search rule that matches the subfield as source and then replaces the alias with a non routable target so this client group can only receive calls.  I tried to use the local list of CPL to do this, but once again because the VCSE does not all identifications CPL rules do not apply.  If it is a bug in X7.2?

  Jarrod Hey,.

  You can do so by implementing the following:

  The information below should help you get Jabber to authenticate correctly on the highway even if you push the control. Jabber must authenticate properly for the presence at work. After this is implemented your search rule should work as you wish as well as the presence and authentication.

  In a secure design, the VCS (control and Highway) would require identification for registration information. Here is a drawing that is not described in the guides of the admin, but has been used successfully.

  The Control of VCS would have Active Directory Service active and joins the Active Directory domain. For VCS authenticate the credentials of Movi/Jabber on Active Directory before the SUBSCRIPTION for the supply is sent to the service of commissioning, the default Zone would be set to verify the credentials. For requests for SUBSCRIPTION from the highway, the area on the VCS control would also to verify the credentials. It handles authentication for the provision.

  The next part is the record of the Movi/Jabber client. The subzone to which the customer will register must also be set to verify the credentials. Here's everything you need for internal records (registration to the VCS control).

  For the Highway, things get a little more complicated. For commissioning subscription, the SUBSCRIPTION is forwarded to the VCS control. With the area on the VCS game to check the credentials, you're all set. Now on registration to the highway. The subzone to which the customer will register to must be defined to check credentials. From the motorway VCS don't have direct access to Active Directory, we use local credentials on the highway. A set of credentials should be configured in VCS Configuration > authentication > devices > local database. You will create a single name and password all Movi/Jabber clients will use. The end user has NO need to know these credentials. The username and password is provided to the Movi/Jabber client via configuration data it has received. To set up these data, MSDS, you must configure a SIP of authentication user name and password for SIP authentication in the configuration of the commissioning. For these options to be available, you must ensure that you have downloaded the configuration template xml for the Movi/Jabber version you are using. The xml file is included in the zip package full of the client which can be downloaded on www.cisco.com. So, who will be recording from the highway. Now, this creates an interesting situation with VCS control. The internal Movi/Jabber client will receive the same provisioning configuration and will attempt to use those same credentials when you register for the control of VCS. The VCS control is already set to authenticate against Active Directory and Active Directory ONLY registration.

  You will need to create an account in Active Directory corresponding to these credentials. The Active Directory account didn't need special access. It is used only for authentication purposes. A few things to keep in mind: SIP authentication user name and password for SIP authentication are stored in clear text configuration configuration. This means that the data is sent in clear text. To be sure that these data are not compromised on the wire, do not forget that you are using for your communication SIP Movi/Jabber TLS.

  Thank you, Adam

• Jabber for iPad - model provisioning of TMS

  First of all, I didn't know where to post this... in the Jabber for iPad or article of telepresence.  So I thought as it comes to the TMS, I would put it here.

  Where can we download the MSDS provisioning model for the new Jabber for the release of the iPad, trying to set it up for the video?  It provides a link to where you can download the template, but there is no section for iPad.  Documentation on setting up with the TMS and VCS is linked below, it's just as if we were video configuration Jabber for telepresence (Windows/MAC).

  http://www.Cisco.com/en/us/docs/voice_ip_comm/Jabber/iPad/Admin_doc/output/b_Jabber_for_iPad_admin_guide_chapter_011.html#concept_2A3A1909CB6E43F19BECF9F04F765B75

  Thanks, Patrick

  Hi Tom and all,.

  The TMS Provisioning model is attached. It should be posted the ORC in the coming days.

  Thank you

  Paul

  Edit: The model of commissioning has been posted here on the EAC:

  http://download.Cisco.com/SWC/ESD/06/284288351/contract/jabbertablet_provisioning_template.XML

  Release notes are here:

  http://www.Cisco.com/en/us/docs/voice_ip_comm/Jabber/iPad/Release_notes/output/b_release_notes.html

  The attachment is deleted.

• Video of Jabber Cisco Telepresence band bandwidth provisioning

  Hello

  We have deployed video jabber cisco for telepresence 4.5 with VCS 7.2 and TMS 13.2.2.  We use jabber to take interviews. The candidates will be sent the link to download the jabber with the required authentication settings. The Jabber is configured with the Public Max and minimum bandwidth of 768 Kbps.

  My question is related to the downspeed of bandwidth. If we configure the bandwidth of 768 Kbps prvosining and internet bandwidth of candidates is less than 768 Kbps will be the Downspeed VCS to accroding appeal to the bandwidth of the network of candidates.

  for example if my internet connection from home is just 512 Kbps and the use of the jabber to make a call to ex90 in my office. Bandwidth settings is preconfigured in the jabber as 768 Kbps. When the call is established will be VCS downspeed the call at 512 Kbps.

  Krishna.

  You cannot configure a minimum bandwidth, which is always the maximum bandwidth jabbervideo will use.

  The user can only set this value downward but not upward, but as the client detects a loss and stores a database

  with information on used networks recently and its quality.

  So, should not be a big problem the faster speeds available and allow the customer to do magic.

  I woud recommend to (re) read the Jabber_Video_Administrator_Guide

  http://www.Cisco.com/en/us/docs/Telepresence/endpoint/MOVI/admin_guide/Jabber_Video_Administrator_Guide_4-5.PDF

  This gives you more information concerning automatic bandwidth adaptation and capabilies of bandwidth detection.

• Jabber presence doesn't work not between VCSe and Express, but works if you are registered to the same VCS...

  Hello

  I have a problem where the presence does not work between users registered on the VCSC and the VCSe.

  If a user on the VCSe registers, they cannot see the presence of VCSe registered users, and even, registered on the VCSC users see only the presence of records on the VCSC.

  TMS is running 14.1.1 with TMSPE

  VCSC and VCSe run every two X7.2.

  Both the VCSC and and VCSe each with authentication Active Directory (direct)

  Wouldn't be better to have control of VCS and VCS Expressway with authentication Active Directory (directly) on the control of VCS?

  Thank you very much

  Rob

  Hello

  in most cases, you want the VCS control to contain the presence information and VCS Highway to simply forward requests for control of VCS.
  Should be set to the 'on' presence User Agent and server on your control and only the User Agent of the presence on the highway in position 'on '.

  You can find more details in the VCS Administrator's guide.

  Sent by Cisco Support technique iPhone App

• TMS Provisioning Extension required for Jabber Video

  All,

  I'd check that commissioning Extension is not required for TMS (14.x) allow video exterenal Jabber users to participate in a video conference on a microcontroller.  These will be not registered in VCS video external Jabber users.

  Thank you

  John

  I guess video Jabber users will be registered to someone else is VCS or using the free video by Cisco Jabber service?  If so, that Yes, you don't need TMSPE, it is only necessary if YOU are commissioning and providing video Jabber service to others.

• VCSC and without VPN VCSe Jabber

  Can these two devices cause the same domain configured?

  Thank you

  Alex

  Yes, its possible.

• Registration for authentication and crossing area of Jabber

  Hello

  I used TMS 13.1.2 as authentication source LDAP for VCS-control and VCS Expressway, but noticed, that not all passwords are synchronized correctly in the LDAP H.350 MSDS database, because the user is recorded in two entries. I went to the local authentication, including the database configuration on VCS - C and the local database with the transmission by proxy SIP VSC-E to the VCS - C records. It works fine and I am able to make calls.

  I created the search on VCS highway rules to replace all aliases MCU to an auto attendant external special. Stored locally on the VCS-E endpoint points are allowed to call internal aliases. I tried to do the same for the Jabber Clients, which is recorded in the crossing area of the VCS - C. This works as expected, because the Jabber Clients are not enrolled in a local area and SIP GUEST is not in dispute.

  I expect that all the Jabber client message will be challenged by the VCSE, but this isn't the case. Accordingly, the guest of the SIP protocol is treated as an external user and not an intern.

  May 9 10:11:28     tvcs: UTCTime="2012-05-09 08:11:28,425" Module="network.search" Level="INFO": Detail="Search rule 'my.domain proxy registrations' did not match destination alias [email protected]/* */'"
May 9 10:11:28     tvcs: UTCTime="2012-05-09 08:11:28,423" Module="network.sip" Level="INFO": Dst-ip="84.113.206.194" Dst-port="62503" Detail="Sending Response Code=100, Method=INVITE, To=sip:[email protected]/* */, [email protected]/* */"
May 9 10:11:28     tvcs: UTCTime="2012-05-09 08:11:28,419" Module="network.sip" Level="INFO": Src-ip="84.113.206.194" Src-port="62503" Detail="Receive Request Method=INVITE, Request-URI=sip:[email protected]/* */, [email protected]/* */"

  These are the rules of research that I was talking about:

  110     Enabled     "local registered to Traversal"     LocalZone      No      Alias pattern match      Regex      ^(.*)@my.domain$      Leave      Continue      TraverselZone
115     Enabled     "authenticated to internal"     Any      Yes      Alias pattern match      Regex      ^(.*)@my.domain$      Leave      Continue      TraverselZone
120     Enabled     "mcu all to 899"     Any      No      Alias pattern match      Regex      ^(900\d*|conference)@nts\.eu$      Replace      Stop      TraverselZone

  Is it possible to allow the Jabber Clients to be authenticated on the VCS-E, so a search rule can aply?

  Thanks for your help!

  You get the 'Preparation device' key for your VCS-E so its free.

  It may require a valid service contract.

  I have the provisioning again running on a cluster of VCS - E in my lab, works very well.

  In ancient times that the deployment has not officially supported, it was running great in any case :-)

  Did not check if its now a deployment with support.

  I don't know enough about your deployment to say what would be the best for you.

  There will be some scenarios where not all features can be deployed together for some reason any.

  Maybe someone can help you by looking at how implementation could be done better.

  If you have authentication and integration of ads, that you need to connect

  the VCS-E announced as well. Endpoints (at least for now) is not auth via AD, but you could

  use a database of h.350 (could also be hosted with AD) or the local authentication database.

  Now, which is also spread by TMS, could be an answer to your question as well.

• VCS VCS - E, TMS, TMSPE, Jabber/Movi authentication

  Just trying to figure the best way to approach this.

  I have read the documentation and the best approach seems to get to the VCS VCS-E to Active Directory and the synchronization of the TMS with AD for user account creation. This would avoid the need to records movi proxy for control of VCS and would ensure that all (SIP and H323) registration for the VCS-E would be authenticated.

  I don't think that my client will allow the VCS-E talk to AD.

  So, what are my options?

  If I SIP proxy of VCS-E records the VCS control, how are they managing H323? I don't want just any point endpoint h323 register with the VCS-E. I need to authenticate them. The customer has exernal h323 endpoints that they would like to sign up for VCS - E. I know I could put registration rules to restrict only some URI SIP, H323 IDs etc but it's really just security by obscurity.

  The local on VCS and VCS-E database can be used for authentication Movi/SIP and H323 records? I know that I would have to duplicate accounts and passwords on both.

  What books commissioning and address through registration to the VCS-E? Would it still work?

  Any suggestions on the best way to handle this in the safest way possible without breaking things?

  If I go with the control of VCS and VCS Expressway with authentication Active Directory (directly) on the control method of the VCS as described in the guide of authentication devices, I'm looking for the reality that I will not be able to restrict who can register for the VCS-E? At this time should I just seek to restrict the search for rules to only authenticated users?

  Thank you

  Jon

  Hey Jon,

  MOVI/Jabber you won't have to worry about authenticating H323. With your endpoints however you can just use the database local to authenticate or H350 (more can be read about in the guide of the Provisioning device referred to as Tomo). You can create a different generic for all your endpoints (less secure if which is discovered). But by combining this feature with a political appeal will ensure better security.

  I highly doubt that your client will allow you to leave the talk VCSE in AD. For movi/jabber users, you can create another subfield and use a regex pattern for point movi/jabber users to authenticate it as. * (\.movi)@domain.com. In addition, you can refer to this fragment and others have used in the past.

  In a secure design, the VCS (control and Highway) would require identification for registration information.

  The Control of VCS would have Active Directory Service active and joins the Active Directory domain. For VCS authenticate the credentials of Movi/Jabber on Active Directory before the SUBSCRIPTION for the supply is sent to the service of commissioning, the default Zone would be set to verify the credentials. For requests for SUBSCRIPTION from the highway, the area on the VCS control would also to verify the credentials. It handles authentication for the provision.

  The next part is the record of the Movi/Jabber client. The subzone to which the customer will register must also be set to verify the credentials. Here's everything you need for internal records (registration to the VCS control).

  For the Highway, things get a little more complicated. For commissioning subscription, the SUBSCRIPTION is forwarded to the VCS control. With the area on the VCS game to check the credentials, you're all set. Now on registration to the highway. The subzone to which the customer will register to must be defined to check credentials. From the motorway VCS don't have direct access to Active Directory, we use local credentials on the highway. A set of credentials should be configured in VCS Configuration > authentication > devices > local database. You will create a single name and password all Movi/Jabber clients will use. The end user has NO need to know these credentials. The username and password is provided to the Movi/Jabber client via configuration data it has received. To set up these data, MSDS, you must configure a SIP of authentication user name and password for SIP authentication in the configuration of the commissioning. For these options to be available, you must ensure that you have downloaded the configuration template xml for the Movi/Jabber version you are using. The xml file is included in the zip package full of the client which can be downloaded on www.cisco.com. So, who will be recording from the highway. Now, this creates an interesting situation with VCS control. The internal Movi/Jabber client will receive the same provisioning configuration and will attempt to use those same credentials when you register for the control of VCS. The VCS control is already set to authenticate against Active Directory and Active Directory ONLY registration.

  You will need to create an account in Active Directory corresponding to these credentials. The Active Directory account didn't need special access. It is used only for authentication purposes. A few things to keep in mind: SIP authentication user name and password for SIP authentication are stored in clear text configuration configuration. This means that the data is sent in clear text. To be sure that these data are not compromised on the wire, do not forget that you are using for your communication SIP Movi/Jabber TLS.

  With this directories will always work as jabber should be authenticated in order to receive directories. Your physical endpoint points will work differently with how they receive books and whether or not they are able to communicate with MSDS (unless you choose to configure endpoints also if those you are capable).

  It is in no way the design as safe as possible. It is to you to ensure that your environment is as secure as possible and therefore tested. The best way to fix everything is a well-defined appeal policy designed with your specific needs.

  The foregoing is in no way a recommendation but just a little more information to chew while looking to choose and implement what is best for you.

  Adam

• Random Jabber disconnections of MCU calls

  Good afternoon

  Hope you can help me. I've seen a few posts with these error messages in but they are not quite what is happening here

  My customer is having a problem, where a number of their Jabber users (for windows) is randomly calls MCU is disconnected on their server of telepresence. The disconnection occurs in less than a minute.

  None of the presentations are shared when this happens.

  The errors are:

  Operation BYE failed because the network error

  End of appeal because INVITE it transaction timeout

  Call due to the failure of closing invitations

  GST 320 - software version: 4.0 (2.8)

  Made - known Jabber clients versions 4.4 and 4.7

  Currently waiting for the client to update me on MSDS, blade of conductor and versions of software VCSE and VCSC

  event_log_screenshot.PNG

  

  telepresence_server_status.PNG

  

  I hope you can help

  Thank you very much

  Luke

  In general, this is because of a network problem, where SIP messages are not sent correctly between Jabber and reliable TP server, in this case, I'm guessing the OK/acknowledgement of receipt are not sent to the head of the Orchestra/TP server and the server TP is disconnecting the call. Is there a firewall in the mixture, do you SIP ALG turned on? If I look at the firewall and disable SIP algo

• Cisco Jabber for iPad released 9.2, dns issue

  Hello!

  Is there an administrator's guide for the new version of the iPad? I can only find one for version 9.1:

  http://www.Cisco.com/en/us/docs/voice_ip_comm/Jabber/iPad/9_1/Admin/JABP_BK_J3C828CB_00_jabber-for-iPad-Admin-9-1-1.html

  which does not describe the function of automatic discovery for the style connection "e-mail."

  I can see there are some research carried out:

  TXT? domain.com.
  SRV? _cuplogin._tcp.domain.com.
  SRV? _xmpp-client._tcp.domain.com.
  SRV? _cisco-phone-tftp._tcp.domain.com.
  SRV? _cisco-phone-http._tcp.domain.com.
  SRV? _sips._tcp.internal.domain.com.
  SRV? _sip._tcp.internal.domain.com.
  SRV? _sips._tcp.external.domain.com.
  SRV? _sip._tcp.external.domain.com.
  SRV? _ciscoedge._tcp.domain.com.
  SRV? _ciscowtp._tcp.domain.com.
  SRV? _ciscowtp._tcp.jabber.com.
  SRV? _ciscowtp._tcp.webex.com.
  

  It works fine for me if I put the _sips._tcp.external.domain.com. pointing to my vcse.

  One explanation could be useful, expecially did what research TXT.

  Hello Martin!

  I know that your question is a couple of weeks and I think since the Jabber for iPad team has posted the last administration guide which has been updated to version 9.2.  See the section 'Setup DNS SRV' as it could explain what you are looking for - I know not how this article differs from the previous guide...

  For the benefit of third parties who have Jabber for the iPad from the specific questions, please note that the community of Jabber Clients is available.

  HTH,

  Paula

• UPDATE to VCSE VCS Starter Pack Express

  Hello community support.

  just a quick question for the upgrade process. With this key:

   Video Communication Server Starter Pack Upgrade to VCS Expressway - TMS, Cisco Jabber Video for TelePresence 100 users CTI-VCSE-SPUPG-K9 TTC2-04

  I can add as an option on my VCSESTRTPACK and remove the pack before starter option. After that, I have a VCSE without refueling.

  But what of the Jabber user? How did the license provided for me?

  Can I install just the touch option even on MSDS and this will add 100 user of Jabber for her? Or do I have to buy a separate license for this?

  Thank you for the support :)

  From what I found online:

  • You can convert the Starter Pack, either a control or highway depending on what part number you use (CTI-VCSC-SPUPG-K9 or CTI-VCSE-SPUPG-K9).
  • You will lose the integrated supply management and Jabber video/Movi licenses.
  • You will retain licensing additional call that have been purchased on top of the base call licenses.
  • You will receive basic application of TMS + 100 licenses video/Movi Jabber.