SX TC6.1.1

Similar Questions

• Question of presentation TC6.3.0

  Hi all

  We found that we cannot display resolution XGA presentation when we choose presentation layout as simple and overlay in a call.

  It can easily reach with the following procedure.

  1. connect to an endpoint farend.

  2. run the presentation on a PC with a XGA resolution.

  3. press the remote button on the page and change the layout to the presentation superimposition or simple.

  (In equality and Prominent, it can display the screen of the PC)

  In addition, when we use the source of presentation HD resolution, it doesn't not.

  Anyone know if this will be fixed in a future software update?

  Best regards

  Kotaro Hashimoto

  Hello

  I see the same question what you describe in the laboratory.   Both TC6.3 and TC7.0.1.

  But I tested with TC7.0.2 beta1 and can't see this problem.

  In the meantime, if you need this, I suggest to you that use TC6.2.1 first.

  Kind regards

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

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

• 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

• EX90 TC6.1.0 to Polycom VSX 7000 without Audio

  We just loaded TC6.1.0 on a couple of our EX90s to test.

  When we connect (H.323) at one of our Polycom VSX7000 endpoints (running the most recent 9.0.6.2 - 103 firmware) we get no audio on our EX90.

  The interesting thing is if we put the EX90 in diagnostic (settings/Diagnostics/market) mode and make the same exact dial, we get audio.

  The two ends are on the same subnet, connected to the same VCS - C.  Decommissioning of the EX90 to TC6.0.1 or 5.1.7 solves the issue as well.

  Anyone else have the same problem, or know a simple fix?

  Hi Wayne.  Thanks for the update.  Is it possible for you to post your device packet trace?  I would like to see signs here point of view H323 if its possible.  A work and not work if possible.  If you don't want to post here, you can private message me if you want.  Let me know.  Thank you.

  VR

  Patrick

• Downgrade to TC5 TC6 SX20

  Hello

  We received a new SX20 with installed TC6.0.0.

  Is it possible to downgrade to TC5.1.7 without a Releasekey for TC5?

  The reason is that we still lack TMS 13.2.1 (with a planned upgrade to 14 in the near future) on Windows Server 2003.

  Currently, we do not want to install the Patch on our server as described in this thread: https://supportforums.cisco.com/thread/2219410?tstart=90

  only this unique system, due to the upgrade planned for 14 TMS on Windows Server 2008 R2.

  Thank you

  Concerning

  Ingo

  Hi Ingo,

  If the keys for TC 5.X never entered on the device, then Yes, you need to enter to downgrade.

  Go to the license on cisco.com page

  https://Tools.Cisco.com/swift/LicensingUI/QuickStart

  and generate the keys

  device must be in an active contract

  Thank you

  Ravi kr.

• Cisco C, series SX TC6.2 Programmable buttons programmable appeal reserved by system

  After the TC6.2, I noticed that all 4 first slots for the mode of APPEAL programmable programmable buttons are now reserved by the system.

  The user guide on the other hand always details that all five of them should be available.

  No explanation by Cisco engineers why this is so?

  Thank you and best wishes,

  Mihail

  Hello

  I think that you have a multiway configured in your system.   In this mode, the buttons are reserved for functions such as hold, RESUME, fusion, new calls.

  This was as it's been for multiway is introduced, not only TC6.2 version.

  Concerning

• 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

• MX200 (TC6.2) cannot save with SIP TLS for control of VCS

  Hi all

  I just got a brand-new MX200 in our laboratories.

  We will evaluate at the moment the overall upgrade to the version sw TC6.2.

  The MX200 was delivered with TC6.1.1.7. Check in the control of VCS with SIP TLS works without any problem at all.

  VCS - C eventlog:

  "26 aout 14:16: 47 tvcs: event ="Accepted for registration"Service ="SIP"Src - ip ="172.18.93.88"Src-port ="5061"Protocol ="TLS"AOR ="[email protected] / * /"Contact =" sip:[email protected]/ * /: 5061; transport\ = tls"duration ="60"Level = '1' elements UTCTime = '2013-08-26 14:16:47, 833'

  "26 aout 14:16: 47 tvcs: event ="The requested record"Service ="SIP"Src - ip ="172.18.93.88"Src-port ="5061"Protocol ="TLS"AOR ="[email protected] / * /"Contact =" sip:[email protected]/ * /: 5061; transport\ = tls"duration ="60"Level = '1' elements UTCTime = '2013-08-26 14:16:47, 831'

  After registration TC6.2 update fails.

  The 26 aout 14:36: 26 tvcs: event = "Rejected registration" reason = "Received no authenticated source" Service = "SIP" Src - ip = "172.18.93.88" Src-port = "36545" Protocol = "TLS" AOR = "sip:DOMAIN.com" Contact ="<>[email protected]"/ * /: 5061;transport\=tls>;+sip.instance\= '"" duration = '3600' level = '1' elements UTCTime = "2013-08-26 14:36:26, 481"

  26 aout 14:36: 26 tvcs: event = "The requested record" Service = "SIP" Src - ip = "172.18.93.88" Src-port = "36545" Protocol = "TLS" AOR = "sip:DOMAIN.com" Contact ="<>[email protected]"/ * /: 5061;transport\=tls>;+sip.instance\= '"" duration = '3600' level = '1' elements UTCTime = "2013-08-26 14:36:26, 481"

  As far as I can see there's something doesn't quite work with the protocoll in relationship with the SIP URI (AOR). Miss me the prefix "[email protected] / * /"

  All other systems (profile, ex, sx) work properly with TC6.2.

  Anyone have an idea?

  Hi adil,.

  Since the inscription "AOR" is only said AOR = "sip:DOMAIN.com"

  I belive you must have some sort of rule research on the VCS the sip domain and pointing to the crossing or a nearby area and the policy setting must be "audit powers.

  and since there is no name of user and password available the record attempts will fail with the message "from source" unauthenticated

  did you recently create transformations on the VCS? also, check your configuration of endpoint.

  You can create a rule to send this registration through local area message passing in turn to the subzone to registration. Please note the subfield must be set on "treat as authenticated" If you do not use authentication.

  Rgds

  Alok

• TMS 14.3.1 Config templates and TC6.3

  I get an error in my configuration for a MX 300 model that I'm under TC6.3.  I get in the activity of Configuration models as it is the only possible output: a value model was rejected by the name of the unit. Geographical area: /Configuration [1] / [1] reason

  Someone at - he seen elsewhere or know where I can dig to find out exactly what is a failure?

  Hi Patrick,

  It's 'Conference PacketLossResilience Mode', which is the origin of the problem. I don't know why, but there is no more this setting in tc6.3.

• Tactile TC6 - presentation by default secondary camera

  After upgrading my C40 to TC6, when I do a presentation of the touch screen defaults to the secondary camera (source 2) instead of PC (source 3). The parameters DefaultPresentationSource affects only the remote standard and probably Call Control in the Web GUI.

  Is there a way to get this back to normal without downgrading or the purchase of new HDMI-VGA cables?

  It is a problem in the TC6.0 release and had a bug in TC6.1 (alpha version now).

• Commissioning of new users on TC6.2 CLI

  Hi all

  We use CUCM for provisioning where as far as I know, all users, except admin, should be configured manually to form endpoints.

  Would it not possible to supply new users through endpoints TC6.2 CLI. Currently we are able to add users only via the Web interface in "Configuration > User Administration > add a new user...". ».

  I crossed Administrator's guide and the guide to the API and found nothing on this subject. Can someone help me?

  Concerning

  Ondrej

  Ondrej salvation,

  Currently, it is not possible to create the users of TC endpoints from the web interface. Cisco has even removed the 'adduser' from the root so CLI command. So it's really not possible.

  If you really need to add users from the web interface, I suggest you to raise a feature request.  =)

  Concerning

  Paulo Souza

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

• Question of lighttpd after upgrade TC6

  All,

  Does anyone else have problems with lighttpd after upgrade to TC6?  I had a client yesterday upgrade to TC6 and after the upgrade they could access is no longer the codec via HTTP or HTTPS.  After further investigation, I found that the service of lighttpd was not working and when I tried to start it I'd get an SSL error.  In addition, I found that the default certificate that comes with the codec was named 'migration.pem' instead of 'selfsigned.pem '.

  I managed to solve the problem by deleting the "migration.pem" cert, then I started the lighttpd service that auto generated a new cert called 'selfsigned.pem' in the correct folder, now they can access through HTTP, the codec again.

  What is a bug by accident or just a single thing?

  Thank you

  Justin Ferello
  Technical Support Specialist
  KBZ, a Cisco authorized dealer
  http://www.KBZ.com
  e/v: [email protected] / * /

  CSCue52815 - Lighthttpd not dΘmarre, if verifyclientcert is enabled and no cert is inst

  $ /etc/init.d/S75lighttpd restart Stopping lighttpd Starting lighttpd 2013-02-07 11:24:17: (network.c.590) SSL: error:00000000:lib(0):func(0):reason(0) /config/certs/ca/default.pem Failed to start the web server.

  Workaround

  Turn off CA list verification using the following command: xConfiguration NetworkServices HTTPS VerifyClientCertificate: Off Once this is off, you can access the web server (after a reboot) of the unit and upload the CA list before you optionally turn this feature back on.

  Fixed TC 6.1

  / Magnus

• Telnet TC6.0

  Hello

  We must maintain codec using telnet

  Before moving to TC6.0, connected codec using telnet.

  But after the TC6.0 update, cannot

  Message:
  Getnameinfo(3): localhost: success
  Temporary failure in name resolution: success

  (don't have the name of the server)

  We need the server name for the use of telnet?

  or what is another method?

  Thanks for your help always

  Hi Soohyung,

  I confirmed the issue on our EX60 happned, too.

  It seems that the configuration of the TC6.0 operating system error causes this.

  I guess we have to wait for versions of Cisco TC6.0.1.

  Anyway, we can use SSH instead, as a workaround.

  Kotaro Hashimoto