Hi Cisco Staff,
Before i go on, i wish to request that my post be not viewed as a complaint but more of an observation and or concern, i have pretty much exhausted Dave Harpers ears, and i really do not want to burn him out because of my gripes with CCA, so i figured i should raise this up with the rest of the Cisco Engineers. It is also quite possible that i was spoilt a little to much being apart of the CCC beta testing, which i found to be Cisco's best efforts thus far in designing a fully fledged system for managing, and maintaining the UC-500 series system.
I have been experiencing some unusual issues with CCA (Latest Build) that i just can not ignor any longer, they end up forcing me to have to revert back to CLI, using a TXT editor and doing a hell of a lot of copy and pasting, which i belive the purpose of the GUI system to is to make things much easier and more stream lined, it becomes even worse when you are onsite and CCA does some very unusual things without even giving warning (You can see it actively working when you run Term Mon for the CLI).
CCA Configures the full amount of available DN's that the system is licensed for, this in my opinion should not happen, it not only creates confusions but since using it to build the last 4 systems, i have found it creates the following problems:
- During the Telephony Setup Wizard, i choose 3XX extension range, then i go through and change it to use extension number 1XX up too the amount of phones being deployed, this is change from it's suggested number range of 2XX, it appears to allow it right through the whole wizard, and even up to the apply section, click apply and then watch it on the console do its business, here is where the funny stuff happens;
- If you go back through to make adjustments to the extensions, in the Configure>>>Telephony>>>Voice>>>User section, it just outright refuses to adjust the new configuration or requests, or so it seems. After hitting apply and then going into the CLI, i noticed that it leaves the previous config Ephone-DN 10 onwards in place, and then go to the next available DN selection that is not in use, and re-creates the whole damn lot, ok so i thought i would try it again, this time changing it from a Dual-line to an Octo-line, WOW it re-created theme all over again this time leaving the last 2 configuration behind. If i am not mistaken the procedure should be to delete the previous configuration as you would when going from Dual to Octo, and then re-create them in the same position, this was not the case in 4 different installations.
- As per the second point, i noticed it doing the same thing with the Voice Mail module, it just does not clean up any code it simply leaves it there, this forces either a manual removal, or going through the CUE gui and hope that the CUE gui detects the redundant mailboxes and allow you to remove it that way.
- Further to the points above, it is noticed that you can not make more then one change at a time, for instance if i change extensions 100 I.E make modifications to the buttons from being empty to watching other extensions, and then without applying go and configure other extensions, it does not apply the full amount of changes, in fact it goes and does something totaly opposite and random, this is normally verified by going to the CLI and capturing the running config after it has been applied by CCA, if i do them one by one in 90% of the cases it applied them successfully, however if a problem was detected in the choices and i was to go back and fix it up, it then goes through and modifies some other extensions randomly ??? I have no idea why it does this, there is no information that i can see except that when i am monitoring via the console i see multiple modifications coming from CCA when i have not applied any further changes.
Is it possible that CCA gives the user the option to either deploy the full amount of DN's or to just create them on the fly, i can understand and appreciate that in some instances this can be usefull to some people, but really CCA has some odd quirks and the current issues it is dealing out, puts me in a position with the last 4 deployments to remove all DN's entered and associated Ephones, re-create them in a text file and then dump them across, thus cleaning up the copious amounts of code deposited by CCA.
(NOTE) This was never experienced with CCC, i am not sure if this was intentional or if this programming was left out for a reason.
I am noticing CCA making adjustments to the system when it is exploring the system for information when it is loading up for the first time logging into the box, it was by accident that i discovered this when i was consoled in and i could see the modification notices popping up, mind you nothing was changed by me, so i have to assume that CCA made some changes to the system without my explicit permission, but i have noticed it does the following:
- Adds new access lists entries when no instruction to do so has been given, or even permissions
- Deletes entries in the access list during the discovery process that might have been manually entered (Not sure if this is because they might not be in-line with OOB guide lines???, but even still it should not remove it without permission first)
- Removed VPN settings without permission (The system i was logged into was built with CCA V1.8 by another organization), this effectively took away the VPN services which had to be rebuilt, not impressed with this issue
Is it possible to have CCA advise you that it would like to make changes to the system before anything is even touched, and if possible it tells you what it would like to change and where in the config it would like to change it. I understand that it should ask your permission before doing anything but i can say with absolute confidence this is not the case, it does though at times come up with a dialogue box informing you about the firewall and if you want to keep it or remove it as it does not recognize it, but this is the only time i see any such warnings come up.
Doing upgrades to systems for their IOS and CUE respectively is a bit of an issue at times, again i have noticed on the last 4 systems i have used CCA on that when i go to the upgrade section, click upgrade it advises me to wait for the Voice discovery process to finish, so i wait 10-15 minutes still nothing, it tells me to keep waiting, so i close CCA and try it again, this gives me about an 80% chance of it working this time, but not always sometimes it takes me 3 or 4 attempts to get it to allow me to do the upgrade.
With doing the upgrade at times it also advises me that the UC-500 does not meet pre-conditions to carry out the upgrade (First time i have seen this issue, did not see this in 2.0(mon), this only happens if i choose to do a full upgrade, if i log out and then restart CCA and chose IOS only, the upgrade then works, and then i have to do the CUE manually.
There are more funny quirky issues, but looking at my post it is already getting to be too long, i have raised these issues with Dave Harper in the past, and some of his suggestions have worked without issues, however the ones listed here just keep happening.
I am fairly confident that i am following correct CCA procedures, and have since gone through and read the material again just to make sure i am doing things right, i was not able to find resolution to the above problems, they just seem to be right out of the field to normal operation.
For now i will continue to use CCA for the telephony wizard as this is fast and efficient, even though i am still required to do manual editing after to clean it up it is still quicker then building it from a template config.
My apologies for the long post, and i am fairly certain no one else has raised these issues up, it might just be me that is having these problems and knowing my luck it will be, but regardless i do applaud the great work the engineering and staff working on the CCA project are doing, it all improved the Cisco experience regardless.