Downgrade to TC5 TC6 SX20

Similar Questions

• SNMP does more work with TC6.0.1

  Hello

  After an upgrade to TC6.0.1, one of our doesn´t of endpoint SX20 responding to SNMP requests. After downgrading to TC5.1.7, it works again.

  I did a tcpdump and a netstat under root: codec listening always port 161, but doesn´t respond to SNMP requests.

  Anyone with the same problem?

  Thank you

  Tino

  Hello

  My SX20 shows the same question. Release TC6.0.1 running. snmpwalk returns nothing.

  Sweet-infusion-7: / home/dderidde # snmpwalk - v2c-c 144.254.13.42 public

  Timeout: No response from 144.254.13.42

  Sweet-infusion-7: / home/dderidde #.

  In the console log, I see:

  SNMPD - Invalid read, s 0xffffffff

  SNMPD - Invalid read, s 0xffffffff

  SNMPD - Invalid read, s 0xffffffff

  There is clearly something wrong here.

  I opened a DDT. CSCuf89304 - SX20 does not respond to SNMP requests

• Upgrade C40

  Hello

  Currently our Codec C40 is 4.2.1 version, I can go directly to the 5.1? We require a license for the new version?

  I already downloaded the s52000tc5_1_7.pkg.

  Our VCS is X7.1.

  TNX

  Bobby

  The upgrade to software version TE6 you won't need to enter a key license but for any major update as of TC4 TC5 and TC5 TC6 in requires a valid license key.

• Firmware upgrade quick adjustment TC6.2 in TC 7.0.2 SX20

  Hi all

  I ve got a question about a Quick Set SX20 Codec.

  I would like to make an update of TC6.2 TC 7.0.2 but I don't know how to back up and restore the unlock key and press the option key.

  And my TMS worm 14.3.2, worm X7.2 VCS system, if I update the firmeware TC7.02 codec SX20--> is it supports?

  wolud be thankul for your help.

  You must have an active service contract on your device to you give right to the upgrade of the software of TC.

  You will not need a new key to unlocking with the version TC6.1 or later (you can pass TC6.2 to TC7.0.2 without requiring a new sense key).  You have no need to "backup and restore" the keys either because they are not affected by an upgrade (although it is always good to have noticed them somewhere just in case).

  If you have the SX20 TC7.0.2 software available in your TMS, you should be able to deploy it to your device without any problem, or to install new software via another method (Web Interface / WinSCP / etc).

  And, Yes, there is no problem of support when you use TMS version 14.3.2 with VCS X7.2 TC7.0.2.

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

• SX20 and link ISDN with TC6

  Hi guys,.

  I recently upgraded a SX20 and link ISDN to the new TC6 and after the upgrade, I can't make ISDN call.

  I can see and manage the ISDN link from the SX20 configuration web page, but the status of the ISDN connection is: error, SIP not saved.

  I use H323 network and I don't use SIP between SX20 and ISDN link and with the old version, I could receive and make calls. Now when I try to dial the ISDN using the new interface TC6 endpoint indicates that it does not find the ISDN link.

  Thank you for your help,

  Adrian

  Hi Adrien, Valentine's day.  Theres something happens with outgoing enabled on the link and the Codec for this, and we have two CDETS opened on them.  There are always SIP service is enabled on the Codec with link and link itself.  Codec uses IPV6 local links for the link itself.  Even if the sip xstatus on the codec has its inactive etc, the codec message still SIP REGISTER to the device registration link.  Link runs a FWD SIP process that handles the request.  Sorta like a mini SIP registrar if you want.  Codec will send the message to REGISTER using link-local IPV6 address.  Example of message is less than 200 Ok.

  77582.64 SipPacket PacketDump: Proto: SIP, name: REGISTER sip: [0000::000:0000:0000:cd39]: 15070 SIP/2.0, Direction: outgoing, RemoteAddress: [0000::000:0000:0000:cd39]: 15070, GroupEntity: b27d07c1f5f298c492db68040b320ca6, time: 77582634 content:!

  77582.64 SipPacket REGISTER sip: [0000::000:0000:0000:cd39]: 15070 SIP/2.0

  77582.64 SipPacket Via: SIP/2.0/TLS [fe80::250:60ff:fe83:c52a]: 5061 branch; = z9hG4bK45a7681a50ebbdc5b98e2f91bff6b438.1; rport

  77582.64 SipPacket Call-ID: b27d07c1f5f298c492db68040b320ca6

  77582.64 SipPacket CSeq: 47083 REGISTRY

  77582.64 SipPacket Contact:

  «': 5061; transport = tls >; + sip.instance =»

  77582.64 SipPacket of:; tag = 116a994ac2281c72

  77582.64 SipPacket to:

  77582.64 SipPacket Max-Forwards: 70

  Road to SipPacket 77582.64:

  77582.64 SipPacket allow: INVITE, ACK, CANCEL, BYE, update, INFO, OPTIONS, CONSULT, INFORM

  77582.64 SipPacket User-Agent: TANDBERG/518 (TC6.0.0.876266)

  77582.64 SipPacket expires: 3600

  77582.64 SipPacket authorization: Digest-nonce = "d9605a7da8be22af8c0e7f52b3de4a5f5125fcd3", domain = "MARCIE", qop is auth, username = "djkvvknn", uri is "sip: [0000::000:0000:0000:cd39]"

  ", response ="3b27b753cb9bcf38cc2431b767bce643", algorithm is MD5, nc = 00000002, cnonce ="84addca2a68f6c5f9b657a94653a4bae"

  77582.64 SipPacket supported: replaces, timer, 100rel, gruu, way, way out

  77582.64 SipPacket Content-Length: 0

  77582.64 SipPacket

  77582.64 SipPacket >!

  -----------------------------------------------------------------------------------------------

  77582.65 SipPacket SIP/2.0 200 OK

  77582.65 SipPacket Via: SIP/2.0/TLS [fe80::250:60ff:fe83:c52a]: 5061 branch; = z9hG4bK45a7681a50ebbdc5b98e2f91bff6b438.1; rport = 41246; receipts = 0000::000:0000:0000:c52a

  77582.65 SipPacket Call-ID: b27d07c1f5f298c492db68040b320ca6

  77582.65 SipPacket CSeq: 47083 REGISTRY

  77582.65 SipPacket of:; tag = 116a994ac2281c72

  77582.65 SipPacket to:; tag = e84d13204776ebc2

  77582.65 SipPacket server: fwd

  77582.65 SipPacket Contact:; (+ sip.instance =""

  77582.65 SipPacket Content-Length: 0

  77582.65 SipPacket

  77582.65 SipPacket >!

  -------------------------------------------------

  I removed my own addresses, so you get the picture here.

  It is the same for the link.  Link will send REGISTRY as well to himself.

  Even if your using H320 as outgoing Protocol call, messaging between the codec and the liaison unit is still SIP as the outgoing call is still SIP of the codec for the link even if you chose H320.

  You can see all happening all by running: Journal ctx sippacket debug 9 and connect the output to see the messaging back and forth between devices.  This is why the Service SIP on the codec cannot be disabled.

  The outgoing enabled on both devices and it records not as what Adrian has met is odd. So the question has been filed and is under investigation.

  CSCue57128 - SIP in a strange state connecting to link ISDN (Codec)

  CSCue73049 - outbound SIP on ISDN link activation causes lose her registration (link)

  These are new, so the visibility may not be there yet.

  If you see a problem with the link is not not able to register, check to see if outgoing SIP are enabled on the link.  If so, turn it off and start.

  Do the same on the codec as well.  Disable outgoing SIP and restart the computer.  There may be some cases, you do not see this, as the investigation continues with the bug above two ID's

  I hope this helps.

  VR

  Patrick

• Downgrade TC5.1.4 5.1.2?

  Hello

  Is there a way to downgrade to a software earlier than TC5.1.4? I ve tried and it works, but the camera (precision HD 4xS2) doesn´t send a videostream. Then it seams I have to downgrade the FW-camera too.

  any suggestions?

  Thank you

  Tino

  Hello

  a downgrade of the codec from TC5.1.4 to the earlier version should not affect the device firmware. The codec check the firmware of the device. If the package of the camera is less than the current software of the camera, the camera will remain at its most recent firmware level. That is a downgrade of the codec will leave camera at the last level that was the package of the camera comes with TC5.1.4 in your case.

  So, why the camera doesn't work?

  I would check xstatus camera where is the camera number, from 1 to N in the interpreter of admin commands or through your GUI.

  XStatus camera 1

  * the camera 1 s: true

  * s camera 1 HardwareID: "52000000."

  * 1s camera manufacturer: "TANDBERG".

  * 1s camera model: "PrecisionHDMC 1080 p 4 X.

  * s camera 1 ID of the software: "S01752 - 2.0FINAL [ID:20012] 2012-08-29.

  * SerialNumber 1s camera: "A1AT07E00477."

  * s camera 1 IpAddress:

  * s camera 1 MacAddress:

  * s camera Position Pan 1: 64

  * s camera Position Tilt 1: 64

  * s camera Position Zoom 1: 4096

  * Focus 1 post s camera: 133

  * s camera 1 capacity Options: 'ptzf '.

  * s 1 Flip camera: 'Stop'

  * end

  Also check the camera, for input, for example, when the device is connected to HDMI1:

  Ok

  xcommand disable put to sleep

  * r DeactivateResult (status = OK):

  * end

  Ok

  XStatus video input HDMI 1

  * s video input HDMI 1: true

  * s video input HDMI 1 SignalState: OK

  * end

  Ok

  Are you sure that the camera is a precision HD 4xS2? We have a notice of field for 4XS1 cameras.

  http://www.Cisco.com/en/us/partner/TS/fn/635/fn63534.html

• SX 20 TC5.1.3 to TC7.3.7 upgrade, need to release key

  I get an error message saying missing key release when I'm doing an update via the Web interface on our Sx20 to version TC7.3.7 of TC5.1.3. I think that the use of the output in version 6.1.3 key but it seems that I still need a release key when upgrading v5.1.3. No idea how to get there?

  releasekey.PNG

  

  Hello

  You need a key to unlock if you go directly from TC5 to TC7 or u to level 6 TC5

  But if you upgrade to TC7 TC6, then u will not need a key to unlock.

  regds,
  Aman

• C20 TC6.0.1 update: fan fails test

  Hi all

  Anyone else have an indication of the failure of test tan on the homepage of the web on a codec C20 interface, updated since TC5 to TC6.0.1 freshly made?

  I mean on the system information page / general tab, Fans report 1 or 2 test failed on one or two fans. The error is not reported in the pages of diagnosis, but only on the system information.

  In addition, it is not systematic. We have 3 cases on about 15-20 codecs but it's worrying, the customer who fears for overheating.

  I have tried factory reset, downgrade/upgrade, but can recover a positive test of fan.

  Any help would be appreciated.

  Kind regards

  Guillaume

  Hello

  This looks like a cosmetic error as I can find it on many devices. but the absolutely perfect fucntions device

  It could be a sensor failure or could be a mistake.

  ambient up to 70-72 C shall be operable temperature if its goes beyond that, then it can be treated like overheating.

  You can check the actual temperature of the device in xstatus / / temp.

  If the peripheral rebootes after a long use could then be a problem that must be addressed.

  Thank you

  Ravi Kr.

• CTS calling not of C series running software TC5

  I'm having a problem where the calls of CTS does not call Tangberd C series exploiting TC5.1 software.

  Here's the whole upward;

  CTS registered series CUCM and C registered in VCS

  There is a trunk between CUCM and VCS.

  Version

  CTS - 1.8.1, sereis C - TC5.1, CUCM 7.1 VCS 8.6.2,

  CTS is not a call to the endpoint TC5 but if I downgrade to TC4. the call goes thru.

  Everyone is run in this kind of problem? If so, can you share me your solution please?

  Hi Zaw,

  I saw a similar question in the past on CUCM 8.6.2 where the present of a URI in the SIP contact header and the CUCM TC5 endpoint tries a DNS reverse lookup on the server of the URI that fails and pulls the call.

  I would need to see traces CUCM to confirm, it comes to the question, but if I remember well him endpoint CTS would a 503 Service Unavailable message.

  If you control the DNS server that the CUCM is pointed, so you could try adding a fake a record for your SIP on VCS domain to see if it helps.

  It may be preferable to prosecute in order to explore all the options your TAC.

  Thank you

  Paul

• SX20 resume question

  Hi all

  SX20 does not display video after taking over a call with Polycom real presence (DPR) Desktop for Windows.

  Is this a known issue?

  1. Enter the IP address of the SX20 RPD on H323.

  2. press the HOLD button on SX20 (using Cisco Touch).

  3. Press button RESUME the SX20 (using Cisco Touch).

  -Online Can RPD SX20's video display, but SX20 displays no video of RPD.

  Best regards

  Kotaro Hashimoto

  HI Kotaro.  Sorry it took so long on that.  You wanted to try some different versions on it.  Went back to TC5.1.8 EX60 and again I have seen the same behavior.

  You may want to approach Polycom on it.  Reason is when the call is held/recovery by EX60 or SX20 in your case, MasterSlaveDetermination should be renegotiated AFTER sleep.  What I see in the RPD package route, is that AFTER sleep, he wants to open FRONT LC MSD.  MSD should also occur in the curriculum vitae.  EX rejects the OLC for audio and video in this case.

  It's something you can take with Polycom to study if possible.

  VR

  Patrick

• Cisco telepresence sx20

  Dear support team,

  I want to know how to configure cisco telepresence sx20.

  any body can help pls...

  Configuration Cisco Telepresence Sx20 is not easy to do. I think below link will help you for configuration.

  http://www.Cisco.com/c/dam/en/us/TD/docs/Telepresence/endpoint/quick-set-SX20/TC5/administrator_guide/sx20_quickset_administrator_guide_tc51.PDF

• How to load firmware on SX20?

  Someone at - it a link to the documentation on loading the firmware on the SX20. I'm having a difficult time finding. With the download release notes don't say much.

  Any help would be much appreciate.

  Thank you.

  The whole process is the same, but slightly different on where in the web interface, you'd download software.  Take a look at the "Upgrade of the system software" section of the SX20 Administration Guide for the version of the software you are currently using.

  If the SX20 is running TC6.0 or on the bottom and you're upgrading to the foregoing TC6.1, you will need a key to unlock, can be obtained from the Cisco Licensing Portal > obtain other Licenses > telepresence Software Release Key.  Note, after TC6.1, release keys are no longer required, only an active service contract is required to download the software of Cisco.com.  If you you are upgrading within the same major version, such as TC7.0 to TC7.3.3, you do not need a key to unlock.

• cannot SX20 one access via web or factory can put it

  Hi all

  We have a SX20 unit that worked very well as autonomous, then we bought BE6000S and wanted to connect the SX20 to the BE6000S.

  However the next day when want to start the configuration, we cannot access the SX20 thru web even if there is a response through ping... I tried the rest of the factory the SX20, and when I followed the steps from the rest when I press the power button 2 times it will turn off...

  is it possible that I can do the rest via a remote control or no Internet?

  the SX20 software version is TC6.3.0.3d8e7d1

  Hello

  1. check connectivity between your PC and the SX20.

  Open a cmd prompt and telnet address IP of the SX20 with port 80/443

  Telnet 80

  or

  Telnet 443

  Cmd it goes blank if these ports are open.

  2. check setting by using the remote control:

  Settings > admin settings > Network Services

  HTTP mode: WE

  Also check the settings of the proxy network on your PC. It shouldn't proxy configurations.

  Check out this guide to the administrator on how to factory reset the SX20 codec using the power button. See page 125.

  http://www.Cisco.com/c/dam/en/us/TD/docs/Telepresence/endpoint/quick-set-SX20/TC6/administration_guide/SX20-QuickSet-Administrator-Guide-tc63.PDF

  Kind regards

  Acevirgil

• Cisco SIP of SX20 registration failed

  Hello

  I want to share the issue we encountered on an endpoint Cisco SX20 fails to register on a VCS control using the SIP.

  Endpoint is running version TCNC6.2.0. The other points of current endpoint of running on TC5x.x, TC6.x.x, TC7.x.x has no problem.

  The endpoint can register on the VCS, but when we try to call one of the other endpoints, the call is not successful. Endpoint will ring and when we accept the call, there is no audio and video, then call disconnects. After disconnecting the call, endpoint failed to register on the VCS.

  We have tried to re - register again, restart the system, then tried to make another call. Same problem again.

  On the VCS, we tried to create a subzone of this specific endpoint (subnet) with treat as authenticated policy. Problem persists.

  We also tried to restore the codec to factory default settings, but did not solve the problem.

  Search for your advice.

  Thanks for the help in advance.

  Thanks & best regards,

  Acevirgil

  Since you are using the version code TCNC, any encryption will not work for calls, if force you encryption anywhere on the VCS or see the call to try like TLS in the call history?

• SX20 UNLOCK KEY

  OK Please help... CISCO began...

  The EX and C series upgrade procedure is so easy... Add version key and then you spend...

  I thought I was going to be a good guy and accesses the SX Series... 'ERROR'... we order and pay for a kit SX20 and install and start it and low and behold... NO INSTALLED RELEASE KEY.

  Then I go to the site of CISCO license and get what I believe to be a key.  Open a browser and 'NO PLACE TO add THE KEY'...

  HHHEELLLPP!

  I'm a fool cause I can't find the place to add the key to unlock for TC7.3.1...

  Where is TANDBERG... :(

  YEP FRUSTRATED AND ANGRY...

  Thank you.

  Watching the SX20 Admin Guide on pg 49, starting with TC7, they removed the option key to liberation from the web interface.  I guess because they have changed the way unblocking keys work after TC6.1, that they did not see the need to maintain the option in the web interface, because netering a key to unlocking to make software updates is now irrelevant.  You can always use SSH to enter the key to unblocking if.

  xCommand SystemUnit ReleaseKey Add Key