Does anyone actually use CCA? Cisco seems to have several overlapping tools to configure devices. CLI, web interface, etc. I am comfortable working on the cli for routing, switching, but the whole voice side is new to me. Should I even attempt to configure via Cisco Configuration Assistant? It's nice for a quick setup, but it's slow, sometimes it seems like the commands don't take, and there is some features that require the cli anyway. Plus, it seems like all of the documentation, etc is presented in cli format. |
|||
 |
UC500.comCisco Communication Manager Express, UC520, SMB VOIP reference and community |
is cca dependant on the console connection?
Thanks guys.
Also, I was told that it is necessary to connect my computer to the uc500 via comport/serial cable/ console port while running cca or else cca doesn't work correctly?
I was also told that this is necessary for the access cme and cue via the web interfaces.
The idea here is that cca and the web interfaces build scripts that are actually pushed through the console port.
does this make any sense? I hadn't heard about it before, and was asking the person for support, so I didn't want to be to sceptical. But, I don't really understand why it would be this way, how these tools support remote access, or how cca could configure multiple devices if it is dependant on the console connection.
Thanks,
Ben
Miss Information
CCA talks to the UC500 via telnet.... and the Web GUI is hosted locally on the UC500... for both the only connection that you need is to be on the Vlan 1 network
Console will give you direct access to the command line, but neither the web GUI or CCA push information through the console...
CCA
CCA is good for doing the initial configuration.
My process for setting up a UC500 goes something like this;
1. Login via CLI and reconfigure the sub interfaces with the IP address's wanted, I leave CUE as 10.1.10.1, but the local ethernet data & voice VLAN I generally have to change. Modify DHCP pools to suit.
2. Delete all ACL's off the interfaces and then remove the ACL's completely from the config (I never use the UC500 on the internet, all setups are completely private internal networks)
3. Connect all the phones & switches and configure switch IP address's with CCA, configure phone extensions and phone names with CCA. CCA is cool here because it goes ahead and does all the DID mappings, voicemail box's & and assigning lines to buttons
4. Turn off CCA and never open it again. Import the dialplan for this area (Australia) If I open CCA again and modify the telephony section it will add it's own dialplan back which is broken for us.
5. Add's and changes are done from either CLI or the web based GUI.
The major reason for me to use CCA is that most of my deployments are with 7931 handsets which have 24 line buttons and can get a bit difficuilt when trying to do these from the CLI.
Personally I like CCA for
Personally I like CCA for doing incoming indial ranges.
If I have a PRI with a 100 number range that is all DID (to a certain extent) then I find it easiest to go into CCA and put in first number, lastnumber, first extn, last extn and then have it write all the translation rules...
Users/Mailbox/AA etc....... Web GUI
Phone config/outgoing dial pattern etc. CLI
Use the default Ip address.
Use the default Ip address. Then just use CLI along with http://10.1.10.1 GUI for voice. :) Don't use CCA anymore than you have to.
echoing other's comments
While CCA will remain to be the official config tool supported, I would agree that the webGUI for the Voice, along with CLI either via browser or terminal or ssh would be your best bet. I have encountered an issue where I had an orphaned voice user that was not able to configure with CCA, and was only able to access and fix it with the webGUI.