TMS C20 provisioning models.

Similar Questions

• TMS licensing provision

  Hello

  Can someone explain how the VCS/TMS system manages license Award for customer MOVI?

  For example, we have 25 licenses of provisioning TMS extension. This TMS reports 15 licenses provisioning and 10 used available licenses.

  However, I can see through the VCS that we have at least 18 MOVI registered accounts with only 3 active in calls. I can't understand how the MSDS reports licenses.

  I have to add 100 other users to MOVI and need to understand how many licenses to buy - as appropriate.

  I'm just assuming that customer MOVI uses only licensed in call - and I could have 1000 users registed with MOVI on a TMS 25 provisioning County of license?

  Thank you

  Stem

  Hi Rod,

  I can't speak for why you get the discrepancy in the number of users Jabber (Movi) connected in accordance with the MSDS and VCS, but I can answer the part about how many licenses to purchase.

  Is the way you need to look at, but a lot of people, you expect to connect to Jabber (Movi) at a given time, is license how much you need.  As each person logs in, they will consume a license, detached from all of the available licenses.  When they connect, that licenses they took, will now be free and available to be used by someone else.  Make sense?

  Something to note on the VCS with light records more than what MSD reported as being used and available, is to check if any duplicate records, and look what the address is displayed, such as:

  SIP:[email protected]/ * /: 60248. transport = tls

  SIP:[email protected]/ * /: 60248. transport = tcp

  I saw sometimes a user will register twice, but under different protocols, note the tls and tcp at the end of each pattern to address, as indicated in the State > inscriptions on the VCS.  I can't say for sure, but maybe it's what you see.

  I hope this helps.

  Patrick

• Orders of TMS provisioning models w/Custom

  I know that if you want to use custom commands to a model of TMS implementation you need to have in XML format.

  How can I put in the command "systemtools rootsettings" in XML format?  Otherwise said, we have 20 + systems and I'm trying to keep me from SSH in every single system, if I have to I will, but if I could put that in our model that normally push us when we get new systems, it will save a lot of time and help us greatly.

  SystemTools rootsettings

  use: rootsettings [on/series/off/never/get]

  Command to control the availability of the root user:

  Get the current value

  off root user is not available

  never superuser disabled permanently

  series [password] root user is available on the serial port only

  root user [password] is available on all ports.

  Thank you! Patrick

  Hi Patrik,

  It is not possible. 'systemtools' is not an accessible command through the API as xcommand or xconfiguration.

  You can always write a script, but that is not so easy if you've never done before. part the more difficult it will be to insert the password automatically.

  Good luck!

• EX90 directory provisioning model

  Hello everyone,

  I just check the possibilities to provide endpoint as EX90.

  We have the VCS Control and - Expressway and a TMS (via TMSPE). VCS-Highway I'm proxy SIP registrations. H.323 registrations are on VCS Expressway. I created two models, one with an internal configuration and the other with an external configuration and different users.

  The only thing I changed on the external model is the address of the server SIP and H.323 Gatekeeper.

  When the Government of EX90 internal LAN, the directory is now available.

  But when I register of HomeOffice thanks to the internet, no directory is available. Registration with SIP and H.323 is ok, but no directory is displayed.

  On MSDS, I already checked if the directory is available for both models. Because with Jabber/Movi, the directory is available in recordings transmitted by proxy, I had hope, it is also possible with endpoints. Am I wrong?

  Best regards, Daniel

  The reason is that it does not get synced with before TMS. Forcing full synchronization may also have then solved the problem.

• Device provisioning model for Ex90 or E20 and does not

  Hello team,

  If I want to use an Ex90 or E20 as a device of commissioning, which parameter are required to configure the XML templates? I basically set up the VCS - C,
  VCS address EI and the source of the phone book. But it does not work or could not saved. I added group and a user with the user name and password to attribute the right model, but no registration. In the commissioning of the EX90 Wizard, I configured the way of VCS with domain and user name password and outside Director but no chance to register. How now the ex90 that he sit outside. On the customer movi I internal and external server, but not in the wizard. OK you can solve externally on the field as a vc. domain.com. but no registration
  Thank you for your ideas

  Sent by Cisco Support technique iPhone App

  Hi Rasim

  User name: {user name of the user commissioning}

  Password: {password for user provisioning}

  Domain: {SIP Domain}

  External Manager: {address VCS}

  / Magnus

• 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.

• Provisioning of the TMS - the model schema question

  Hello

  I have read the deployment of TMSPE and tried to find the TMS Provisioning model for new Movi 4.4 schema, however, I could not find anything of cisco.com.

  Please help me where I can download the movi and schema of the model from the other end?

  Thank you

  Hello

  This model should be included in the bundle of jabber, when you download jabber 4.4.

  Sent by Cisco Support technique iPhone App

• TMS Provisioning question

  Hello

  My TMS version is 13.2, new facility.

  I tried to enable the agent TMS under administration-> configuration-> General-> tms tools enable agents. After all, I do not see any process under the status of the activity.

  "If I connect to VCS, under systems > Navigator, selecting the agent VCS and TMS tab, I see"

  Successfully connected to the TMS agent running on the VCS. "" but there is an error message "

  Unable to connect to the agent running locally on this server MSDS MSDS. »

  Any idea on this issue? Thank you

  Hi Curtis

  Since this is a new installation and you are running 13.2 I recommend you to install the tms extension provisioning. The tmsagent is the old model of provisioning.

  https://supportforums.Cisco.com/thread/2145898

  Follow this thread for the document and download links.

  / Magnus

  Sent by Cisco Support technique iPhone App

• TMS directory - contacts AD

  I've recently upgraded to 14.1 and tmspe. During the upgrade, I've migrated my entries inherited TMS in the new solution highlights. The transmission of data contained in 5 groups with the users in each group. When I log in MOVI as legacy user and find the directory entries, everything works as expected.

  The problem I have is this - I created a new group and imported my Active Directory users. I can connect to MOVI as a user of Active Directory however when I try and search for users/end points in MOVI nothing appears.

  I checked for the provisioning directory ticks next to all my other access control entries in the phone book.

  All the world and ideas?

  Thank you

  Stem

  Hi Rod

  The first thing that comes to mind is the configuration information. If you have created a new group you also assigned to this group a provisioning model right? This model is different from other groups? Because other users directories work what is the difference between these users and the users AD?

  Users of AD have the configuration of the directory [email protected] / * /?

  / Magnus

• Research directory movi X7.2.2 VCS & TMS 14.3.1 question

  Hello

  I just upgraded a VCS to X7.2.2 control and the TMS to 14.3.1.  The TMS was previously running 13.1.1 with TMS Agent for the provision to users of Movi.  I foloowed the TMS Cisco upgrade procedure and went to 13.2 and installed TMSPE V1.0.  VCS has moved the TMS Agent Provisioning extension.  After that all the checkups showed OK, TMS has been improved 14.3.1 and TMSPE in version 1.1.

  TMSPE health check shows all green elements and the configured users group has access to the relevant directory.  VCS show all users, entries, contact methods, files and access control was imported from TMS.

  I disabled TLS SIP VCS settings and ran a Wireshark capture on a laptop with the registered customer of Movi.  My search request for [email protected] / * / field can be seen with the search string in the body of the message.  A response is also indicating that no match could be found, despite several exisitng entries in the phone book.

  Any suggestions on how to solve this problem will be received with gratitude.

  Thank you, Paul Richardson

  What Movi version are you running?

  Do you have the schematic for this version in TMSPE and you set up a model based on this scheme?

  What is a single VCS or cluster?

  What type of directory or sources you associate with the phone book?

  I guess you see entries in the directory and source of pb? And these are the entries of type SIP, i.e. [email protected] / * /?

  Sent by Cisco Support technique iPad App

• Error TMS in the newspaper of the events endpoint SX20

  Hi, I took the reins of the telepresence for our company and I see some weird messages to the event log on our endpoints SX20. An example is attached, but basically every 30 seconds there is a generated TMS error event:

  4 Feb 13:25:44.181 a8 appl [1614]: ERROR of TMS 2419780.71: http (this = 0x430cb2f0): failed with (Peer certificate cannot be authenticated by the given certificates of AC)
  4 Feb 13:25:44.182 a8 appl [1614]: 2419780.71 provision() I: MSDS: MSDS query FAILED, length 0
  4 Feb 13:26:14.183 a8 appl [1614]: 2419810.71 TMS I: provision(): http request url /https://142.31.193.100/tms/public/external/management

  The entries go back to yesterday, but I'm not sure if that's when the question began or newspapers are simply reversal and removal of previous entries

  There seems to be no problem with endpoints; they can make fine point to point calls and can be booked through the TMS without problem.

  We have done no firmware update (codecs are on the TC7.1.4 firmware version) or of changes in the environment

  That's what worry?

  Thank you

  Brad

  I see your SX20 is trying to verify the TMS server certificate and is unable to verify the certificate.

  The certificate installed on the TMS server is self-signed by TMS, CA internal to your organization or by a third-party certification authority?  For one who has signed the certificate server TMS, their certification authority is added for the SX20?

  If you don't care to check the MSDS server certificate, you can set NetworkServices > HTTPS > VerifyServerCertificate OFF.  However, if you want to check the certificate, you will need to download the certificate of the CA of the organization who signed the certificate for the TMS server.

• SX-20 and TMS

  Howdy all!

  So, I have an interesting question... I have a MSD 1.3.22 and various models of configuration of the different endpoints throughout our Organization... I can apply the model configuration for the endpoint and they accept and keep the settings changed in the attributed model... Which works very well... I have an end point, however, it's on our Wan which is separated by a small number of firewall when I push the template for her, she will receive the changes and I can log in there to check (it's a SX-20) that it infact change the parameters of said accourding model, but after 5 minutes or so things like the IP management or external Manager IP which have been defined on the endpoint before the model has been applied return back these previous ip settings after 5 minutes... so there as endpoint settings override what TMS said it from the model...? Any ideas?

  Thanks in advance!

  Including SX-20 has a persistent model are attributed to him, which might be the substitution it back to the original settings after you make the changes?

  As you mention the external IP Manager, something to look at would be to check the following settings in Configuration > network settings, within TMS.

  • Advanced network settings for systems on the internal network
  • Network advanced settings for systems on Internet Public/firewall

  If these settings/addresses are different from what you apply in your models, yes TMS replaces the model changes if 'Apply the settings on management systems' is on.

• UPGRADE EX, SERIES C WITH TMS 15.1.0

  I'm in TMS 15.1.0 and started using the upgrade feature.  I am able to upgrade my MXP without problem but failed to get the series EX or C upgrade TC7.3.3.   I have the keys to unlock for TC7.3.5 but when I try to execute an upgrade to the EX60 or C90, it won't work.  they are on TC7.3.3 and I tried it without adding the key, and also with the addition of the key.  I have SSH open to monitor all activity on the codec but nothing?  I perform an upgrade on the EX60 locally of the system itself, and he succeeds, so the file is a .pkg good...

  Are their all the settings on the EX and the C to make sure of? So then what?

  A few more things I can think off on the top of my head you should check/try:

  Your end points have valid DNS servers defined on them which can resolve the domain name of your server TMS?

  If they are not, TMS will be telling them to seek an upgrade of the software, but the end point will never be able to download the software, if it cannot resolve the correct domain name/URL.

  If it is OK, then you can try to enable extended logging endpoint and the launch of an upgrade and see if you can see the upgrade message itself said knock endpoint on the packet capture it performs.

  You can also view the log files of endpoint, you should also see something like this (just to capture on one of my friends):

  2016-04-18T10:19:57.911+09:30 ppc appl[2863]: 4585179.57 TMS I: provision(): ok ! heartbeat 0 ! upgrade yes ! 0 files ! 0 docs
  2016-04-18T10:19:57.912+09:30 ppc appl[2863]: 4585179.57 PROV I: provision(): software upgrade url='https://yourTMSserver/tms/public/data/SystemSoftware/s52000tc7_3_5.pkg' release-key='1TC007-1-FFFFFFFF'
  2016-04-18T10:19:57.948+09:30 ppc appl[2863]: 4585179.60 PROV I: Starting normal download
  2016-04-18T10:19:57.949+09:30 ppc appl[2863]: 4585179.60 PROV I: Starting download from https://yourTMSserver/tms/public/data/SystemSoftware/s52000tc7_3_5.pkg to /upgrade/pkg.tmp
  2016-04-18T10:19:57.951+09:30 ppc appl[2863]: 4585179.61 PROV    HttpDownloader(this=0x232c6c60): initialized

  Another thing you can check is the HTTPS VerifyServerCertificate parameter on the endpoints (under Configuration, Network Services, HTTPS). If it is enabled, change it OFF, just in case one of your server certificates is invalid or expired and try again. If it works, then you know a setting that can make work, or that you have to solve your certificates. Wayne - don't forget the frequency responses and mark your question as answered as appropriate.

• Question TMS and conductor - conferences to improve safety by using conference

  Hi people,

  Currently, I implement some projects involving Cisco Telepresence conductor and I was wondering the benefits that conductor brings to the video network, it's really a great solution!

  Discover the benefits of the conductor, I created the following deployment:

  

  It works very well! The customer is very satisfied with the level of security when using this deployment. Their multi-point conferences is safer now.

  Well, when I created this topology I considered not how the environment would work when planning conferences, with TMS and conductor because this client has yet to TMS. Then, I was just shocked when I opened the TMS deployment guide e conductor and find the following statement:

  Note: The exposed conductor TelePresence conference type is not supported in Cisco TMS. Only models conference using the conference meeting type are supported.

  Page 13 - http://www.cisco.com/en/US/docs/telepresence/infrastructure/tms/config_guide/TelePresence_Conductor_with_Cisco_TMS_Deployment_Guide_XC1-2_TMS14-1.pdf

  I almost jumped the bridge... Now, I know that my great topology no longer works with TMS.

  Well, here are my questions:

  Why do we have this limit?

  That Cisco plans to fix this?

  The guide is related to the conductor XC1-2 and 14-1 TMS, something has changed in TMS 14.2.2 and XC2.1?

  I'd appreciate any help really, really!

  Thanks in advance.

  Paulo Souza

  Please note the answers and mark it as "answered" as appropriate.

  Paulo Souza wrote:
  [...] I am wondered the benefits that Conductor brings to the video network, it is really a great solution!

  Agreed! The driver of the telepresence really is a great product.

  Why do we have this limitation?

  Because the feature was never implemented on the side TMS. It was decided that the other characteristics are more important and should be a priority. There is nothing on the type of conference 'Read' which is inherently incompatible with the TMS, but work needs to be done first.

  Examples:

  • The control of conference centre: you will probably see the entries in double Conference if you are using a 'read' conference
  • TMS does not differentiate between the presidents and guests during the creation of scheduled conferences 'Conference' on the conductor.

  None of them are very difficult to solve from a development point of view, but they are not trivial to apply or test either.

  Does Cisco have plans to fix that?
  

  Nothing specific is planned, don't. As always: if it is a problem to your customer, make a request to feature through your account manager or another Cisco point of contact.

  The guide is related to Conductor XC1-2 and TMS 14-1, has any thing been changed  in TMS 14.2.2 and XC2.1?
  

  Conductor XC 2.1 and TMS 14.2.2 is a combination not supported, but nothing has been changed to

  2.2 XC and 14.3 TMS: types of conference 'Read' are not yet supported.

  Best regards

  Kjetil

• TMS Server installation

  Dear experts,

  Apologies if this has already been asked (and answered). We currently use 13.2 TMS (with Provisioning) installed on the server of Tanderg Management Suite.

  Is it possible to install the v.13.2 on our own TMS MS Windows Server 2003 or Windows Server 2008 that is in line with the requirements of harware and software specified in Cisco_TMS_Install_Getting_Started_Guide_13-1-2. Maybe we need something else?

  Many thanks in advance,

  Nick

  Hi, I can't find the link to the message in this app, but answer the question by Dale Ritchie in another thread if you search for 'device 13 to 14'. I copied in its response:

  The TMS device must be able to handle an upgrade to 14.2.1... although we remove soon supported for Windows Server 2003 and the TMS is EOS/EOLed.

  Therefore, I recommend that migrate you the application MSD and MSD SQL db (aka tmsng) to a customer owned server, HW or VMware.

  And if you 'migrate', note that you will need to get the new release for the TMS key since the TMS release the keys for the first TMS device started with 80Bxxxxx and the sw begins with 80Axxxxx. To do this, refer to the following instructions:

  1. the customer must first order a copy basis of TMS using CTI-TMS-SW-K9. This will provide them with a serial number non-appareil/software-only that will begin with 80Axxxxx. As the basic software, it will come with 10 licenses of system. So they buy actually 10 additional systems of what they had before.

  2. once they have new serial number, call the TAC and ask an SR to be raised with GLO (global operations of licenses). This is a request for re-accommodation for options on their TMS Server device, with a serial number that starts with 80Bxxxxx, to re - host new software serial number alone (again, starting by 80Axxxxx).

  3 GLO will forward the application to the TMS PLM. The PLM TMS usually approves most, if not all of the elements of the application.

  4. the customer will receive back a new PAK (product authorization key) to face their serial number of 80Axxxxx to the cicso.com/go/licensing page. They can then update their existing installation of TMS with the new release key. After pressing the Save, this will update serial number in the lower right of the browser. All they need to do is add keys option one by one, and then tap Save when done.

  Rgds,

  Dale

  Sent by Cisco Support technique iPhone App