TMS - Polycom

Similar Questions

• Problem of update of the directory between TMS & Polycom (HDX, VSX)

  Hello

  We have deployed MSDS and other cisco devices in a business.

  The company already has several devices of Polycom (HDX (3.0.5), VSX (8.5.3)) and we connected those to TMS (14.3.1) for the Organization of directories.

  Everything looks very well, we were able to see the directories of TMS on Polycome devices

  However, the question comes out when we update the directory.

  Any change of MSDS, these devices of ploycom updated their own changes meaning TMS and devices of polycom is interoperability.

  But when it comes to avian (GDS) directory, we find no changes to this directory, even its own changes.

  And these changes are correctly updated for Cisco devices.

  For example,.

  We have 1 HDX, 1VSX, 1 SX20 and MSDS.

  We changed the names of these three system with TMS.

  You could see the name changed in the information system on all devices category. (Even devices polycom names have been changed in this category)

  But if I go to GDS (Global Directory) in Polycome devices, there is no change. It comes even as before. (Even the name change itself)

  I want to ask:

  (1) why this has happened?

  (2) what can I do to fix this?

  Reference the following default:

  CSCuj42053

• Adding the Polycom HDX to the TMS system

  How can I add a Polycom HDX system in TMS to manage?  What, if any configuration on the Polycom system must be made, or in the TMS?  Can't seem to find any documentation about it.

  http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/TMS/interoperability/Cisco_TMS_Product_Support.PDF

• 14.3.1 TMS version and Polycom 700 series group

  Hello world

  I just wanted to know if the TMS version 14.3.1 lets add Polycom group series 700 as a breakpoint or not.

  Here to talk, it shows an error of unsupported Type System. Not sure if this is a bug or compatibility issue. I was wondering if any document matrix compatibility is available for it or not.

  I greately appreciate your help.

  Thank you.

  Rgds,

  Bushra

  Not supported. However, and as with any other system not directly supported in TMS, you can add it as a 'House' system in the TMS.

  Sent by Cisco Support technique iPad App

• TMS and Polycom VSX

  Hello

  One of our customers uses some VSXes Polycom and Cisco VC systems. They have created a directory on Cisco TMS. This directory includes also a few records. C20s, they can see the files on the phone book. But on the Polycom VSXes, they can not see the records. They see all the addresses in the same directory in order from A to Z. Don't you know that it is possible to separate with VSX records or not? If so, how?

  Best regards

  Chambers oumar

  Hello

  Polycom units does not support this unless they were included in a new software at least they did not support this before. Only a directory flat as we see. Use cisco endpoints

  Sent by Cisco Support technique iPhone App

• Polycom end points do not display information SIP in TMS

  I have a mixed environment of Cisco and Polycom endpoints. In TMS, the endpoints of cisco have H323 and SIP addresses under control panel. However, all points from polycom endpoints have not their SIP addresses. I have polycom endpoints registerd to the VCS w / SIP and H323 parameters. VCS and TMS are connected.

  Any ideas on how I can get the Polycom SIP addresses appears in TMS/directories?

  According to the worksheet of compatibility (even if it's a little old, not much has changed) and as mentioned in this thread , it seems not be any support for SIP in TMS for devices of Polycom.  There are two workaround solutions mentioned in this thread, which may or may not work in your environment.

  Wayne

  --

  Remember the frequency responses and mark your question as answered as appropriate.

• License TMS for Polycom integration [command]

  Hello

  My customer has existing Polycom HDX7000 series and they need to use TMS for the planning meeting.

  Should I order the license 'Cisco Network TMS integration Extension (Polycom, Radvision ViaIP, MGC, Cisco 3540)' on TMS for the support of this solution?

  IF THE ANSWER IS "YES"; my client has 10 points from polycom endpoints, should I order this license for 10?

  Please help me :D

  Thank you

  Yada.

  No, this option is for third-party MCU. The comma between Polycom and MGC is a typo.

  You can simply add the HDXs MSDS and they consume a system standard license only.

  Sent by Cisco Support technique iPad App

• TMS and AVAYA scopia endpoint interoperability

  Hello

  I have the management console of the TMS version 13.2. It is not the latest version, but I wonder if AVAYA SCOPIA XT-4300 products are compatible for integration in the TMS. It's like the product POLYCOM HDX?

  Y at - it a document on which products are supported?

  Thank you very much!

  For TMS 13.2, you can take a look at the Documentation of integrated systems, specifically Product Support and documents using the feature to see what Cisco and 3 third-party products are supported.

  Note, for the most recent releases TMS, you will need to look at the admin guides as well as Telepresence interoperability of data because there are no available detailed compatibility document, similar to those mentioned above, for the version beyond TMS 13.2.

• Problem with the Polycom endpoint dial string via VCS

  Greetings,

  Currently I have an environment using a set of standalone Polycom endpoints (mixture of VSX/HDX units).  We have recently installed VCS - c / VCS-e / TMS and despite a few problems with the SIP registration on some of the older endpoints and management through TMS, all support works well.  The only remaining problem is when there are a number of business partners using the extensions in their chains of H.323 dialing that works very well for the Polycoms during the use not VCS - c as a guard in the numbering of the format #.  When you use this same dial string and endpoints are registered in VCS - c then the only thing it is indicated in the call history is a number of , which fails.

  I am aware that different manufacturers have historically managed extension dialing differently since ISDN only and has apparently been perpetuated until today.  However, it's a pretty critical need still at this stage and I am looking for input on chipboard VCS supports the use of extension component in the dial string (or did once the call is connected to a gateway is the host).  If so, is there a specific format for this connection string which can support both the end points of Polycom and VCS able to interpret correctly?  Does anyone have this working?

  Latest versions of software are on all components.

  Thank you in advance for any thoughts you may have!

  Hi Readamson,

  using the syntax of "device-IP-address ##extension" to compose a H323 device isn't a way standard of doing things, it is approach of Polycom extension numbering that VCS does not understand without changing the alias of a '[email protected] / * /' format.

  Assuming that the address-IP-receives the message SETUP H225 VCS-E, he does the SETUP message? Is there a way that you can configure this device to end to remove the [email protected]/ * /' part of the route the call to the post and the dialed number?

  Visit this link:

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

  Best regards, Ahmad

• TMS - add a mistake to endpoint systems

  Hello

  I am trying to add endpoints Polycom HDX 7000 HD in my TMS, but I find some problems.

  (1) the hardware is recognized and connected, but in the end, the process of adding the following message is displayed:

  System already exists under a different system of TMS; Updated but not added to the file system.

  (2) locate the device with 'systems - Purge', I remove the material and try to add one more time, then the message:

  The start tag of 'meta' on the position of the 20 24 line does not match the end of "script" tag Line 22, position 7.

  I wonder if this equipment is stored in another place, in a different database, or I have to perform another procedure of

  exclude them completely the system.

  TMS version: 13.2.1

  Polycom Version: 3.0.3 (other material from the same version are added)

  Hello

  I found a bug on this. Here is the workaround

  Workaround solution:

  * Install endpoint HDX HDX 3.0.3.1 version at least

  Disable the setting "Select lists of Session" on the Polycom system (since the local interface, go to system > Admin settings > General settings > Security > security settings.) From the web interface, go to settings Admin > settings > Security > security settings)

  Please let me know if it worked.

  / Magnus

• Unavailability TMS

  Simple question to help a client to determine the value / worth to deploy a TMS HA (either via the balancer load or active / standby)...

  What functionality would be lost in delays that TMS became unavailable for a reason any?  Suppose that all infrastructure and endpoint devices have been added to the system as managed devices, Movi/Jabber clients have been supplied, phone books have been published and distributed and conferences on demand. In other words, the system is completely configured/stable and TMS breaks down. In this period before it recovery/reconstruction:

  Y have an effect on existing managed devices, or that they would continue to function 100% with their current configurations and directories?

  -What would be the effect on the scheduled conferences? I think that this may depend on the type of conference, that "auto connect" (for example) require MSDS inaugurate the conference call from the endpoint, but this appointment perhaps or conferences BBFRR would work always as usual without TMS being available - need to confirm on this.

  Thank you!

  All types of multi-point conference will be affected by MSD downhill. This is because MSDS does not have a 'conference.create' on the MCU control until the conference will start.

  "Manual connection": the prompt for the master VC to start the Conference is sent by TMS, so you will lose this type of conference, as well as BBFRR and 'auto connect '.

  'Booking' is not route the call and book the ports and gateways, these conferences should therefore be affected by MSD become unavailable.

  Specifically, if I schedule a conference of MC, is this information down thrust to the endpoint where it is resident RAM unless there is a restart of endpoint (and therefore not affected by the failure of TMS)?

  It depends on the software version of endpoint. Information is pushed to the new endpoints of TC and TE so that they are visible in the sections 'meetings' on touchscreens, but nothing is ever being pushed to TC/TE on older software (pre 5.0, I think) or MXP, etc. Polycoms.

  I don't know why the people of endpoint chose clear the list of meetings to restart the device. It's actually an issue for endpoints CUCM recorded in TMS, where the start event will the CUCM and non MSDS. Thus, we cannot guarantee that the meetings are back after a start.

• TMS 14.3 - auto connect problem - multiple call attempts

  Hi people,

  I have a client with an environment with TMS 14.3, conductor XC 2.2, VCS 7.2.2 TP Server 3.1 and CUCM 8.6.2. They have several items on VCS and several endpoints of CTS/TX registered to CUCM Cisco and Polycom endpoints. There is a trunk SIP between CUCM and VCS. Conductor is integrated with VCS by using the B2BUA deployment model. TP server is behind the driver used as multipoint resource only for conferences scheduled through TMS.

  We are having problems when planning a Conference at TMS using type "Auto-connect" and setting driver to dial a number to the selected participants. For some end points when the meeting starts, conductor made several calls try to participants, even after participants answering the call. For example, conductor connects to an endpoint 3000 CTS, CTS answers the call and connect to the meeting, but a few seconds later, conductor's call another attempt at the endpoint, then endpoint answers the second call and put the first call on hold.

  This problem occurs for the following parameters:

  • Endpoints of Polycom HDX series
  • CUCM items of endpoint CTS/TX
  • Outside dial participants (those selected on the tab 'External' to the planning page)

  The problem does not occur for any endpoint TC registered in VCS.

  As a troubleshooting step, the client was trying to configure TMS to try to connect to the participants once (using the "Attempts to connect for scheduled calls" setting value 1), but the issue still occur.

  Tomorrow, I'll be on the customer's site to check if this strange behavior has been generated by TMS or by the chef himself. I really think that it is some sort of bug. I don't know that their environment has been configured properly according to the Cisco documentation, because I was the person who made the project.

  I'd appreciate any suggestions really.   =)

  Thanks in advance.

  Paulo Souza

  My answer was helpful? Please note the useful answers and do not forget to mark questions resolved as "responded."

  Hi Paulo,

  a few days back we had seen this problem and I filed the bug "CSCui90143."

  Currently, we anticipate that this problem occurs because the MSD is not able to understand the message of feedback from the conductor.

  I hope that clarifies. I don't have to if you want to be able to access the bug or not.

  Rgds

  Alok

• Systems supported for TMS 13.2.1 and Release 14

  Hello, I would like to know if there is a document somewhere showing what are the systems could be registered with TMS 13.2.1 and TMS 14, because we thought the upgrade of TMS or not, we have also a lot of systems, the 'old' too, which we are not sure if can be saved as a type system instead of a room.

  We had this band:

  Tandberg 1000MXP, 3000MXP, 75MXP, 770MXP, 880MXP, 95MXP, 990MXP, Maestro.

  Polycom Viewstation 128, Viewstation, VSX7000A.

  LifeSize MX.

  I think that the MXP series can be recorded without any problems, but I'm not sure of the Polycom VSX, Viewstations, Lifesize MX and Tandberg Maestro (even if it's still a Tandberg).

  Kind regards.

  Hello

  Here is the document for at least 13

  http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/TMS/interoperability/Cisco_TMS_Product_Support.PDF

  / Magnus

• TMS 14.3.2 a HDX7000

  Hello

  We acquired 3 Polycom HDX7000 via a merger. I tried to discover with TMS, but TMS learns only H323 configurations. He doesn't learn the SIP configuration. How can I fix this?

  SIP is not supported for these types of devices in the TMS - only H.323 and H.320 for devices of Polycom.

• Possible bug in battery Toshiba BT: Polycom Voicestation 500 does not ring

  I have Polycom Voicestation 500 speaker that is compatible bluetooth. When Polycom Voicestation 500 is connected to the Skype by BT dongle/battery Toshiba (i.e. just after the reboot) first, it does not at all sound. I think it's because the "wave of Bluetooth (voice)" is selected as the ringing device. The correct ring device must be "Bluetooth Wave" not "Bluetooth Wave (voice)". However, I could not find "Bluetooth wave" under device ringtone so I couldn't choose "Wave Bluetooth" as a ringtone... It seems that the Toshiba BT stack does not detect that the 'Bluetooth' wave is supported in the device of ring sometimes. BT stack incorrectly detects "Wave of Bluetooth (voice)" as a ringtone.

  If I disconnect the Voicestation and plug it in again by Toshiba Bluetooth Manager, most of the time, I'll find the 'wave of Bluetooth' on device ringtone. I think it's matter of battery Toshiba BT. I look please v6.10.10 latest Toshiba BT stack in this.

  If someone has recommended all at the same time, please let me know. Thank you.

  Have you tried the battery Microsoft Bluetooth instead?