Solved: I can't believe you guys are - Page 4

Magnus Ohm · ‎04-07-2014

I am pleased to announce that TC7.1.0 is released and can be downloaded on http://www.cisco.com.

Please read the release notes:
http://www.cisco.com/en/US/docs/telepresence/endpoint/software/tc7/release_notes/tc-software-release-notes-tc7.pdf

Regards,
Magnus Ohm

Steve Kapinos · ‎04-11-2014

"I wonder if there are any plans within the VC world outside of call manager to simplify a SIP dialling pattern without the need for complicated transforms and Enum DNS setups, outside of CUCM that is"

Essentially every pbx is doing what you are asking... making dialing plans with just DNs and following PSTN-type conventions. If your dial plan is fixed, this is pretty straight forward. The value in ENUM and DNS is to allow direct routing without previous direct associations defined.

Martin Koch · ‎04-11-2014

Hello David and also Steve,

that is off topic in this thread which is already long and confusing enough

for the TC7 related parts.

If there is more to be said discussed about that, please open a new thread

Please remember to rate helpful responses and identify

Justin Ferello · ‎04-10-2014

Cisco,

I don't believe that the local contacts & TC console settings are backed up using the web based backup, correct? I only get a text file with xconfig commands....

Also, will TAC just generate the token for us, or will there be a case opened, multiple questions asked and or hesitation from the technician?

Thanks,

Justin

Thank you,
Justin Ferello
Technical Support Specialist, ScanSource KBZ

Wayne DeNardi · ‎04-10-2014

Hi Justin,

For your first question, I think you're correct - I can't see that the TC Console settings are backed up anywhere. I've kept a copy of all my TC Console .xml files that I've uploaded in case I ever need them again. I can't see any of the local contacts/favorites in any of the backup either, it's just the xconfig. I'm with you - this is something that needs to be addressed in the future.

For the 2nd part - As with everything that you log with the TAC, it seems you get a different experience depending on the technician who picks up the job - You do need to logged a call with the TAC to get the password from the Token . I generated a token on one of my C60s - the call was responded to ~30 minutes after I logged it - directly with the password, no hesitation (apart from the time delay). Again, your mileage may vary depending on who you get (as per other issues such as release keys to address security vulnerabilities) but hopefully you shouldn't need to jump through hoops.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

Martin Koch · ‎04-10-2014

Some words about the root access.

I see multiple impacts here. There are some things regards security which might not have been ideal.

Like root accounts without or weak passwords. Also the usage for the root account where it should not have been used.

So I can at least understand that there are some points to improve that.

Benefits on the root account are that we are the boss of the device (as long as we do not suspect that there is some "root kit present".

I must say as an admin I prefer, that I can trace what ever I want, have access to all processes, everything is more or less transparent.

But now, this is gone and the implementation is not ideal neither. Maybe a root option key and strict passwords would have been the better way.

Using different unix accounts with different permission settings could have been a better answer as well (you do not need to be root to do tcpdump as long as you have the right permissions).

I wonder also what happens if there is no service contract or if the system is EOL.

We were part of the EFT and I was shocked when I saw it and reported it back as a critical issue.

Like I said, I can understand the need for security improvements, but the remotesupport user is not how I would like to see it.

Please remember to rate helpful responses and identify

Chris Swinney · ‎04-11-2014

I wonder also what happens if there is no service contract or if the system is EOL.

+1 on this one as well Martin. Whilst I know that Cisco's answer will be, "well, as we're a bunch of money grabbin ...., you should all stump up the cash to keep us getting fat"

Unfortunately, a lot of sites we support are in Education such as schools and small colleges or charitable institutions. They cannot afford the continued maintenance but WE have (er, had) the ability to provide the majority of the support they need. Sure, if the hardware goes wrong then they might be stuffed, but now you are limiting our troubleshooting options.

Chris

Andrew Vasel · ‎04-11-2014

I can't believe you guys are removing our ability to easily upgrade our codecs using WinSCP. Given that we upgrade our hundreds of codecs a few times a year utilizing WinSCP (which has been by far the most reliable method for upgrading), I can't even begin to imagine what approach we will take for upgrading. If the remotesupport user has be to be activated by TAC every time we need to upgrade... This is quite unbelievable to me.

Wayne DeNardi · ‎04-17-2014

Do you know if there are any plans to release a new version of TC Console soon as the current 6.2 version no longer works with TC7.1.x? Or if a new TC7.x is going to be released that lets TC Console 6.2 work again?

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

jrandby · ‎05-13-2014

Hi Wayne

You can download TC Console for TC7.1 from ftp://ftp.tandberg.com/pub/software/endpoints/tc_console/

Regards,

Johan

Wayne DeNardi · ‎05-13-2014

Thanks Johan.

TAC sent me that last week, and TCConsole 7.1.1 too - both available at https://developer.cisco.com/site/collaboration/telepresence/av-integrator/tools/tc-console/tc-console.gsp.

I've posted an issue I have in your other TCConsole 7.1 thread.

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

Michael Stark · ‎05-12-2014

I cannot believe Cisco have stopped the root login. We support major customers and we have to commonly perform tcpdumps and assess captures to verify issues in the customer environments. We try to close cases without wasting the time of Cisco TAC - in actual fact if we raise too many cases Cisco generally do not like that . Now we need to raise a case just to get root access to perform tcpdumps? This is terrible and needs to be fixed.

Wayne DeNardi · ‎05-12-2014

Root access is gone - and it's likely will never return.

There are other ways, as mentioned in Magnus' Endorsed Post, to run a tcpdump - and you can do so without having to log a call with the TAC.

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

Michael Stark · ‎05-12-2014

Sorry what do you mean by upload the package in the tmp folder using the remote support account?

Do you need to upload a package to get tcpdump access or is there by default once I login as admin using SSH?

Wayne DeNardi · ‎05-12-2014

The "upload the package" bit was referring to the question about how to upgrade an endpoint via WinSCP, not anything to do with the tcpdump.

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

c.montfort · ‎09-10-2014

I've been using WinSCP to share a common phone book between ex90's in our organization (seperate networks with different TMS instances, some home units not managed by TMS and others registered to Polycom gateways). Using the favorites/local contacts is easiest until we roll into one TMS instance. Can I still upload the pb.xml to the /config/ folder with the remoteuser account?

TC7.1 is now released and available on Cisco.com