EX90 TC6.1.0 to Polycom VSX 7000 without Audio

Similar Questions

• 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

• Cisco MCU 5320 and Polycom vsx

  Hello!

  I have the problem with these devices. Content does not work properly. MCU push content to the same protocol with video endpoint vsx h.261. If the quality of the content are very poor. Is - this intraoperative problem or a software problem?  any other point endpoint it works very well.

  Hello

  You have basic Mode activate on your Polycom endpoint?

  Try to do either disable or enable basic Mode in your devices of Polycom, just to see if you get different behavior. You can find the slot configuration system > admin settings > network > call preferably.

  In addition, the date of issue for MCU version 4.4 indicates some interoperability issues with Polycom HDX endpoints when using content with H261 Protocol, do not know if this limitation also applies to the VSX series.

  In addition, I suggest you check the documentation for Polycom to check if the VSX endpoints are able to share content using protocols H263 or H264 instead of H261, also check if there is some version or configuration required to enable it.

  Concerning

  Paulo Souza

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

• Polycom Viewstion 512 none audio with the SX20 only

  We have implemented several Cisco Telepresence.

  Our problem is that if a Polycom PVS-16XX (or Viewstation 512) makes a video call (H.323) at our SX-20(release 6.3.0), there is no audio transmission for the Polycom.

  Place a video call from the Polycom even to any C-40 or other Polycom, the problem does not appear.

  Any video call to and from the SX-20 C-40 works perfectly

  Hello

  I think that this problem is resolved in TC7.0. However, you can try to run this command on the SX20 and try the call again to see if you get audio from the ViewStation to the SX20.

  Log the SX20 as admin via SSH.

   xConfiguration Experimental CapsetFilter: "AAC-LD"

  Hope this helps

  / Magnus

• dealing with the unwanted incoming call to SX 20 during the Conference

  Could someone help me please with a problem I have with a new system of SX20.

  Is it possible that the system can be set to do not disturb when the first call is in place?

  The Polycom VSX 7000, there is a setting in the option multipoint-to-multipoint auto-répondre calls, no auto answer or reject the call.

  This means that the first call can be set to auto answer mode and all calls will be rejected.

  Is it possible that the SX20 can be put in place in this same mode - auto answer the first call and then dismiss all other incoming calls in "do not disturb" mode

  The only option that seems to work is either reject all calls or unwanted calls "ringing" in the session.

  Thank you very much

  Hello

  You can change default "Allow" on "deny".

  Conference 1 IncomingMultisiteCall Mode: enable

  Deny: An incoming call will be rejected if you are already in a call. You will not be notified
  on the incoming call. However, the call will appear as a missed call in the call history list.

  BR Oleksandr

• The third conference end point Visio restart when you receive a call

  Hello world

  I'm working on a x.8.2 of Cisco Telepresence video Communication Server, I was able to check third-party devices (Polycom VSX 7000 a, software

  Release 9.0.6.1 version) on this subject, but when I try to call these devices, they restart, knowing that I have no problem with endpoints of Cisco.

  Can you help me?

  Thank you, guys, in advance.

  According to the release notes of Polycom for 9.0.6.2 that this has been fixed in the previous version, which is what you run. You may be a 9.0.6.1 early release? I would upgrade to 9.0.6.2. Page 12 of the release notes, you will see this problem.

  http://downloads.Polycom.com/video/VSX/9_0_6_2/vsx_vseries_relnotes.PDF

  Interoperability: Tandberg VCS GK	VIDEO-85528	Previously, when Polycom VSX received order join the restarted control VCS Tandberg, VSX doorman. This problem has been fixed.

• Static severe Audio connection endpoint Polycom HDX series

  Greetings,

  I'm looking for ideas on the question.

  We experience severe (and immedate, connecting) levels of static audio when Cisco (SX20 or C40) endpoint connects to a Polycom HDX endpoint.  Cisco endpoints are running TC7.2.1.  This doesn't happen when you connect between Cisco endpoint to an endpoint of Polycom VSX.

  If HDX endpoint connects to a Cisco endpoint, in addition, there is no problem.  This only happens during a call from Cisco to HDX endpoint.  All connections are made via H.323 SIP not.

  All units are stored on the same device of control VCS.  VCS rolls X8.5.1 and shows no errors or questions.

  Any thoughts would be appreciated.

  Thank you

  -TM

  This is a bug in TC7.2.1

  See here

  CSCuq94402

  CSCur78783

  Symptom
  Get a white noise for audio and not video

  Condition
  Use TC7.2.1 and Polycom with software version 3.0.5 and call using H323 with active encryption.

  Workaround
  Disable encryption, call using SIP, downgrade from TC7.1 or earlier version of Polycom or wait for TC7.3.0 and xConfiguration H323 1 encryption KeySize value profile: Max1024bit

  We have disabled encryption until TC7.3.3 is released.

  7.2.1 is originally models C20 revive the call

  7.1.4 has vulnerability shellshock

• 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

• 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

• Tests EX60 UCM and VCS registration

  Hello

  I did a few test with Cisco EX60 a few days ago a the following infrastructure:

  -UCM 8.6.2

  -Cisco VCS control X7.2.2

  -Cisco EX60 series

  -Csco EX90 series

  -Cisco CPIC

  -Cisco IP Phone

  The goal was to try to save the EX60 in SIP mode with UCM and H.323 mode in VCSC and make some calls with EX60 register in both devices, because I have found no documents where it was stated that only I can save EX60, EX90 in VCS or Complutense University of MADRID, but not in both at the same time.

  I recorded the EX90 in VCS and EX60 in VCS (H.323) and UCM (SIP).

  All calls to H.323 devices EX60 send control VCS and all calls all works fine without any problems. If I try to call EX90 to EX60 in SIP mode, the call will be fails. When the EX90 with EX60 H.323 call is connected, the University Complutense of MADRID and using RTMT I saw that the EX60 was on appeal or in busy state.

  -Audio call of the registered IP phone or CPIC to the AAU to EX60: I saw the call in the call control in the EX60 and RTMT and Complutense University of MADRID, but I did not see the call to the control VCS Cisco. If I try to call to EX90 to EX60 using H.323 right now, I got an EX60 busy tone. Also, if I make an audio call to EX60 for an IP phone I can do another audio EX60 call to an IP phone or an EX90. EX90 try to video negotited but calls finally was audio only.

  -The presence does not work when the EX60 is under appeal with the other end H.323 in the Complutense University of MADRID, too the BLFs do not work and does not appear the call at the Complutense University of MADRID.

  -Si EX60 is videoconferencing with EX90, the EX60 can receive an audio call to UCM get connect and the presence and the BLFs working properly.

  I find no more problems at the moment.

  Kind regards.

  This isn't a Setup program that you want to use, or register them both to the VCSC or

  Let CUCM control your end point, then h323 must be disabled.

• Cannot launch the call to Polycom V700 to Cisco SX20/EX90

  Hello

  I am configuring a Cisco SX20 and a Polycom V700. I can call to Polycom Cisco, but can't call Polycom to Cisco. It proved a mistake, "your call could not be connected because the call was was routed through a network of intermediary that is not service the remote site." Please contact your network administrator. "But I have that in place inside the LAN, and there is no firewall on the inside.

  I've tried with EX90 as well, but it's the same thing.

  Can someone please advise me what I missed?

  Concerning

  Robi

  Hi Robi,

  I'm kinda a waste, then as to why it does not work... If you have enabled IP H.323 gatekeeper OFF, call preference value IP H.323, numbering method with H.323 Auto in 1st preference and all other disabled protocols - it should just really work when you dial an ip address...

  I guess the next thing to look at would be the version of the firmware on the polycom - is recent (or maybe an older buggy)?

  In addition, you could try a factory reset on the device (just to make sure there is not another stuck somewhere setting) and to reconfigure settings you need.

  Wayne

  --

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

• 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

• MCU4500 series and Polycom HDX broadband bandwidth interop

  Hello!

  A customer brought it to my attention and I was not able to determine a good reason for it yet.  First of all, here are the settings;

  -MCU4515 4.4 (3.49) running

  -Polycom HDX (a 7000 and a 8000) running 3.03

  -MCU and endpoints registered to a Porter, no bandwidth restrictions (they say)

  -calls to 1.2 M

  -MCU call termination points, H323

  When connecting endpoints HDX, the incoming bandwidth for the MCU is half of the outgoing bandwidth to the HDX.  I can't find any setting in the MCU which has an effect any on this.  By default the settings of bandwidth on the MCU (inbound and outbound) are set more than the real call rate.

  I tried to test with a 4.4 (3.49) running of the MCU4510 and two Cisco endpoints (EX90 C90), endpoint and saved for a VCS and the MCU points not saved.  The incoming and outgoing call, rate stays.

  Y at - it no unpublished data of interop MCU which has a reference to this issue?  The customer said that wasn't a problem when the MCU was at 4.2 (1.50).

  Thank you!

  Thanks Bob.  The reason why this is happening now is that MCU had some previous issues by honoring the bitrates etc..  This problem has been fixed in MCU 4.4 under CSCuh81255.

  When HDX calls, it always opens LC for ExtendedVideoCapability at the beginning of every call.  This leaves MCU to split the BW cut in two for hand and when the system wants to send the contents of the content.  Given that the already contained open HDX channel to MCU, MCU must reserve the quantity of bioweapons for content when the HDX decides to send and do not exceed 1.25 meg in your case.

  I hope that makes sense to you...

  Let me know if it doesn't.

  VR

  P2

• Problem of SX20 Cisco calling the polycom system

  Hello

  I have a Cisco Tandberg Telepresence SX20 and I am facing a problem with advertising a Polycom video conferencing system.

  I n few problems with my SX20 but I participate in a videoconference accommodation on a Polycom system. But when I try to call this system, my Tadnberg SX20 displays a white rectangle with "no video in" and a timer.

  My firewall, all ports are open.

  What could be the problem?

  Thanks in advance

  Aurélien P.

  Make sure that your SX20 running a recent version of the software (TC7.3.6 or CE8.1.1) and also the end point of Polycom is up-to-date.

  We had a lot of problems over the years during the call to devices of Polycom and pretty well all the cases, the question was an older version of the software on the Polycom.

  If it's an old VSX Polycom, make sure you're on version 9 (9.0.6.2 recommended) lease, and the Polycom HDX endponts should be at least version 3.1.x (3.1.10 is later).

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

• TC6 Firmware - call disconnects after 2 hours

  Hi all

  Our client complains that after the firmware update on the endpoints of telepresence (C40, C60, EX90) to TC6.x, there are two questions:

  1 end with TC6.x points will disconnect after 120 minutes to be connected to any appeal initiated by the remote end.  They will not cut the minute 120 if the TC6.x Unit has initialized the call.

  2 end points with TC6.x cannot connect to units MXP running F6 or earlier.  Since we MXP Codec Software F6 and F5 this is causing problems with the calls point to point.

  They have units with the TC5.1.6 software which have no problem at all. The only thing among others as the routers and switches is a VCS controller.

  Anyone has any ideas on what is the cause?

  Thank you

  John

  In TC6, we turned silently on TCP KeepAlive for the session h225 running with the default time of linux tcp_keepalive_time of 7200 seconds.  That would probably explain the disconnection to 120 minutes which sees the John after moving from TC5.1.6.

  I would also say that if this is the case, there is something which is tcp to the current between the two devices.  The firewall is also my first thought.  Perhaps WAAS on a router?  Sometimes you can get a clue that this is occurring by comparing the tcp ack/seq/windowsize header to see if it is different between the sending to the receiving side for the same package.  Something like 'tcpdump-s0 w /tmp/h225.pcap port 1720' root must limit the collected output.

  The TC6 troubleshooting located here would be a good reference in newspapers and tcpdump to use for troubleshooting signaling related issues:

  http://www.Cisco.com/en/us/docs/Telepresence/endpoint/codec-c-series/TC6/troubleshooting_guide/tc_troubleshooting_guide_tc60.PDF

  The example uses this doc does not filter the traffic and John you do not want to limit the output of tcpdump only for signalling interesting to avoid problems with the size of the OCAP collected file.

  We have a bug open better control KeepAlive on the session h225 (CSCub20591) but not clear if/when it will be executed and for now if there is something that is expire tcp sessions in the network, changes will be made here to avoid this problem.

  For the 2nd question, I'm not aware either a problem with older MXP but your approach Martin to try a later version of the software would also be what I would recommend.  If you need to solve problems with old software MXP TC6, the same troubleshooting guide h323 newspapers are where you want to focus on to see where in the handshake the call fails and compare this output between TC6 and TC5.1.6 as to what has changed that can have an impact on this.