It make complete sense, why would anyone fiddle with a production box. I think Cisco did a good job in locking down the root access to the box. He was not aware of he could delete using CUCM OS CLI ‘file delete activelog blah.’ command but contented to get shell access to CUCM. He replied, I recently upgraded CUCM from v5 to 6x and the disk space creped up on and want to clear up some files. I asked why do u want to access the root shell to start with. You got the point! One of my friends asked me last week – is there anyway to get access to the CUCM root shell.
#Cisco uccx editor for mac os x skin
Well you are eating the banana but eating the skin too, not so tasty :(. Without native shell accessing CUCM files or other thing using Cisco recommended method (CUCM OS) is like eating a banana without peeling it.
Many of us Linux geeks sometime want to jump onto the CUCM Linux shell, just like we natively access any other *NIX based server.Oh yeah, much more fun and seriously you can debug and troubleshoot things quicker. Quite often, when we are working on a production (or Lab) server and need a shell access to CUCM, we had to call Cisco TAC and wait for ages before we get access to the CUCM root shell. This is only for lab and learning purpose!
If you perform this on your production CUCM box, you may voiding Cisco contract. Warning:Before you read this post, please note -do not try to apply it on your production server. My mind got crazy and then I thought to play with my new toy – CCM version 6.x. This is so boring as I can’t do any outdoor activities. It’s 42 degree outside here in Sydney today and is also a long weekend. Oh it’s hot hot hot….not chilly hot but hot hot! An error has occurred the feed is probably down.
0 kommentar(er)
