- Gold, 750 points or more
Cisco Designated VIP,
2013 Small Business
Hi Support Team,
I have for the first time been attempting to build a UC-560 from scratch using CCA 2.2.4, with no CLI intervention what so ever, so far not as smooth sailing as I hoped for.
Phone Types: SPA509 & SPA504
Phone Load: As per the 8.0.2 Software Pack
CCA Version: 2.2.4
- Configuring Button Assignment on phones Without phone plugged in:
When using CCA and entering the Telephony>Voice> Extension configuration page and proceed to program the extra line keys (Buttons), I hit a major issues, first attempt at assigning them to watch and pointing them to a particular extension yields no results, even though it shows up on the screen that it is sending the information to the UC-560, it also comes up with a pop screen advising that the sending of the information was sucessfull.
However when I monitor this on the Command Line, I see no notification that the system has received configuration, so I do a "sh run | s ephone " on the CLI and notice that no configuration has actually been applied.
So I attempt it again, this time on another user, still same issue, even though CCA gives the all clear, I check the UC-560 still no config applied to the ephone, at all.
- Configuring Button Assignment on phones With phone plugged in:
If I attempt to configure the buttons when the actual phone is plugged in, I get partial success, some of the line keys (buttons) receive the programming, however it seems to miss some of the buttons, and then if I log back into it again and reprogram those ones, they work but then a couple of other ones stop working. If this is not little green gremlins causing this issue I don't know what is, and frankly it is very frustrating.
- Configuration Multiple phones buttons and then applying:
I also discovered that you can not do this, if you configure more then one phone and then apply it, none of them get programmed up at all, i discovered the hard way after sitting there for 1 hour programming them in, that this would not work, so again dropped it back to one at a time and then apply before moving on to the next one, but still suffering the partial programming.
- CCA not configuring the DN's in sequential order:
I also noticed that CCA does not configure the users in sequential order, some where configured in DN Range 20-28, then others in 40-53 and then Others in 100-14, what is with this?? Why wouldn't it program these in sequential order, why does it have to be all over the place? I can handle the fact that CCA puts in an enormous amount of translation rule when running DID on a ISDN circuit, that's fair enough and can deal with it, but the randomness of the DN's does not make sense.
At first I thought this strange so I tried it on the UC-540 that is scheduled in for a build, and it even happened to that one, so it was able to be reproduced on more then one machine and with different scenarios.
I know it is not me, I seen this problem with CCC as well, but surely I can not be the only one to experience this issue right??
I am going to try it again, but this time with all phones plugged in, I will do it onsite when we deploy the equipment. However if it still fails I will fall back to CLI and program it up that way.
I look forward to some feed back.
/* Style Definitions */
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";
Found the root cause and we have committed a fix for one big culprit it on 2.2(5) few mins ago.
Basically, MeetMe, Adhoc, Call Park and Paging Group features will overwrite
Intercom's ephone-dn without this fix.