2.2(6) and 8.0.5 issues on UC520

[dharig]

How is this CCA team still employeed?   Seriously?

Issue 1.

Upgraded from CCA 2.2.(5) to 2.2.(6) on three different machines now  2 x Win7(32bit) and 1 x Win7(64bit).  On all three upgrade instances when the upgrade was done there was a restart button presented in a pop-up box.  On all three instances the restart button did not work, nor did closing the app, forcing me to go into the task manager and terminate the process.   Not a good start, however when I relaunched CCA it did load up showing 2.2(6) despite the snafu durring upgrade.

Issue 2. I have tried to upgrade my UC520 to 8.0.5 using CCA 2.2(6) and each time the process gets stuck on "Analyzing Phone Loads In Software Pack"

I have tried this from the same three machines I upgraded in issue 1.  This process stays there for at least 2 hours (the longest I have waited it out). m I have redownloaded 8.0.,5 several times, confirmed MD5's, installed 2.2(6) from scratch all with no sucess.

I called TAC and they said " Whatever you do don;t use CCA,  it is a big combersome application that only causes issues"   What does that say?

I have screamed so many times on this forum.   CCA team<<< You are inept!   PERIOD!    I have watched you fumble-frock your way though this software evolution for two years now.   I have never met one TAC agent, partner, dealer or user with a single good thing to say about your product.   This latest debockle is just the latestest in a VERY long line debockles.

Anyone else sucessfull with 2.2(6) and 8.0.5 on a U520 with Win7 OS?

[Steven DiStefano]

Hi David,

I really think you are usually more cheerful than this :-)  Sorry you are having trouble.

Three areas I would like to discuss.

1)  SWP 8.0.5 for UC520 was/is corrupt.  It downloads, but if I try to unzip it, I get errors.   This was as of 6PM last night.  The BU got UC540 and UC560 corrected, but I wonder if you have a bad 8.0.5 causing all this?

2) The CCA doesnt come with a PC so we are often stuck at the short end of a stick when it doesnt work on someones PC(s).  I know you know the datasheet calls for 2G RAM.  Do you have at least that?

It also specifies:Windows: Windows XP Professional (Service Pack 2  or later), Windows Vista Ultimate (32 bit or 64 bit), or Windows 7(32  bit or 64 bit)

Microsoft Internet  Explorer 8.0 or later recommended, with Adobe Flash Player 10 or later.

Also, Rob Castillo just added a note about Windows 7 to the Prerequisite check.  There are other things you should check for in this link, but I pasted in his Windows 7 findings...

https://supportforums.cisco.com/docs/DOC-9779

Windows 7 Issues

If using a Windows 7 pc or laptop with CCA on it make sure  you are aware of 2 things.

1) Turn off User Access Control, where  basically the standard question is “Are you sure?”; this will pause the  process when performing a reload of the UC via CCA.

2) Enable Telnet; this is off by  default.

As a side note, make sure that Norton  Firewall doesn’t enable itself when you disable the Windows Firewall and  that it does not disable FTP.

3) TAC (UC520) versus SBSC (UC540/UC560)

I am not sure how the TAC Engineer who thinks that because he/she never became proficient with CCA, that they can make such comments?

That really bothers me.  Backbone TAC never really embraced CCA since the fist 20,000 usints went without any reliance on CCA.  After studying the TAC Cases and PDI Help desk cases and costs, we introduced new platforms (540/560) and a separate support center 9SBSC) to try to overcome the natural behavior and process a TAC Case goes through to get reolved using CLI by a SME for the area of support call (example, a crypto map expert will fix your VPN issue with CLI very fast and is rated and paid on how fast they solve cases across many platforms with that expertise).  This usually (generally) means they dont rely on CCA since it has limited use (Only UC500 and they support so much more).   But most Partners want lower total cost of maintaining a practice in small business with UC500 and cant afford to staff a team of CLI experts of their own to understand &  maintain CLI configuration (hacking sometimes) to have a repeatable practice.  I realize you may not be one of these, and I meet many who are CCIE and want to use their skill and experience and I understand that.  In fact many on this community are very advanced users and are also frustrated by what is perceived as a limit using CCA, but it really makes the business owners more successful.  When you have an issue, I understand that you have Smartnet on your UC520 and call TAC, and we are kinda stuck in what I just described.  I think going forward, UC520 will be pure CLI.

You can always come to the community to ask for help and we will try to help as best we can.    I would personally appreciate it if you treated us more professionally though as I think we can work better together that way.  Like you, we all come to work every day to do a good job and try our best to keep your satisfaction with Cisco where it makes us all successful.

Steve DiStefano

[dharig]

After the corrupt upgrade file 8.0.5 issue was resolved by Cisco
I decided to take my hand at a fresh install and reconfiguration of My UC520
with the 2.2(6) CCA application as I was confident this time the CCA team got
it right .  ;)     O hel-NO

 

I could not have been more ginger with this thing if I
tried, doing only one config at a time, never going into CLI (even the approved
out of band commands), working with a freshly defaulted UC520 and clean install
of CCA 2.2(6) on a  clean install of Win7 on a brand new HP laptop. I am dead serious here, these are the measures I have been forced to resort to even have a chance to manage the UC520 with CCA.

Here was my experience and issues so FAR after 24 hours!

1)   
Started by walking  my way through the configuration wizard
(figured no harm there).  Wong, after
following the wizard to the end and applying my config (an hours work) it threw
an error at the 6% mark saying the ACL group was conflicting.  Hmmmmmmmmmm

2)     Screw-it I said, cancel the wizard and start with a non-wizard config.

a.      Issue
1.  I set it up for a 4 digit PBX style
Voice config,  yet every other time CCA loads
the voice data it says (Voicemail pilot number not set) despite setting it dozens
of times and sees my 4 digit extensions configured and creates errors on the
bottom saying the extensions need to be three digits.  When I re-load the Voice screen the 4 digit extensions
are recognized.   It seems to alternate
every other time with that error.   It has something to do with the voicemail pilot number popup box that keeps prompting me so I log into CUE and guess what,  no voicemail
boxes listed!!!!!   WOW!     CCA is configuring them and listing them
out yet CUE does not even see them.  

b.     Various divulge boxes minimize bellow error display area and they can’t be recovered
forcing CCA to be terminated in task manager

c.      Page configuration is requiring 3 digits when it should be 4 a set up in system

[Steven DiStefano]

For #1, this is concerning and I think you need to open a case and get the log (CCA menu  HELP: SUPPORT INFORMATION: Generate troubleshooting Log).  The factory default ACLs are these below, and CCA should not have a problem with them.  Its almost as if there were some additional ACLs CCA may have had a problem reading.

access-list 1 remark SDM_ACL Category=2
access-list 1 permit 10.1.1.0 0.0.0.255
access-list 1 permit 192.168.10.0 0.0.0.255
access-list 1 permit 10.1.10.0 0.0.0.3
access-list 100 remark auto generated by SDM firewall configuration
access-list 100 remark SDM_ACL Category=1
access-list 100 deny   ip 192.168.10.0 0.0.0.255 any
access-list 100 deny   ip host 255.255.255.255 any
access-list 100 deny   ip 127.0.0.0 0.255.255.255 any
access-list 100 permit ip any any
access-list 101 remark auto generated by SDM firewall configuration
access-list 101 remark SDM_ACL Category=1
access-list 101 permit tcp 10.1.1.0 0.0.0.255 eq 2000 any
access-list 101 permit udp 10.1.1.0 0.0.0.255 eq 2000 any
access-list 101 deny   ip 192.168.10.0 0.0.0.255 any
access-list 101 deny   ip 10.1.1.0 0.0.0.255 any
access-list 101 deny   ip host 255.255.255.255 any
access-list 101 deny   ip 127.0.0.0 0.255.255.255 any
access-list 101 permit ip any any
access-list 102 remark auto generated by SDM firewall configuration
access-list 102 remark SDM_ACL Category=1
access-list 102 deny   ip 10.1.10.0 0.0.0.3 any
access-list 102 deny   ip 10.1.1.0 0.0.0.255 any
access-list 102 deny   ip host 255.255.255.255 any
access-list 102 deny   ip 127.0.0.0 0.255.255.255 any
access-list 102 permit ip any any
access-list 103 remark auto generated by SDM firewall configuration
access-list 103 remark SDM_ACL Category=1
access-list 103 permit tcp 10.1.10.0 0.0.0.3 any eq 2000
access-list 103 permit udp 10.1.10.0 0.0.0.3 any eq 2000
access-list 103 permit udp  any 10.1.10.0 0.0.0.3 range 16384 32767
access-list 103 permit udp  10.1.10.0 0.0.0.3 range 16384 32767 any
access-list 103 deny   ip 192.168.10.0 0.0.0.255 any
access-list 103 deny   ip host 255.255.255.255 any
access-list 103 deny   ip 127.0.0.0 0.255.255.255 any
access-list 103 permit ip any any
access-list 104 remark auto generated by SDM firewall configuration
access-list 104 remark SDM_ACL Category=1
access-list 104 deny   ip 10.1.10.0 0.0.0.3 any
access-list 104 deny   ip 192.168.10.0 0.0.0.255 any
access-list 104 deny   ip 10.1.1.0 0.0.0.255 any
access-list 104 permit udp any eq bootps any eq bootpc
access-list 104 permit icmp any any echo-reply
access-list 104 permit icmp any any time-exceeded
access-list 104 permit icmp any any unreachable
access-list 104 deny   ip 10.0.0.0 0.255.255.255 any
access-list 104 deny   ip 172.16.0.0 0.15.255.255 any
access-list 104 deny   ip 192.168.0.0 0.0.255.255 any
access-list 104 deny   ip 127.0.0.0 0.255.255.255 any
access-list 104 deny   ip host 255.255.255.255 any
access-list 104 deny   ip any any
!

For Issue #2a:   The 2.2.6 release notes list thie caveat: http://www.cisco.com/en/US/docs/net_mgmt/cisco_configuration_assistant/version2_2_6/release/notes/cca_226_relnotes.html.

CSCte99064

Telephony Setup Wizard: Four digit extensions work, but subsequent  phones get 3 digits Symptom The UC540 is configured with 4-digit extensions using the Telephony  Setup  wizard in CCA, which works correctly. However, when you add a new phone  to the  network, it automatically receives a 3-digit extension number instead of  a 4-digit  extension number. Workaround On the User Extensions tab in the Voice window in  CCA, manually re-configure the phones to assign 4-digit extensions.

But since you didnt use TSW, And you used the pop up to set the extension length, it shouldnt have been a problem.  I think we need to identify this as a case with Logs too please.

Issue 2C is probably also related.  Logs will help.

[Steven DiStefano]

I am going to try this now in my lab as well.

[Steven DiStefano]

I have a UC520 16 user system with FXO

My PC was plugged into its switchport and no other NICs active (no wireless...nothin else)

I factory Reset (Applied Default COnfiguration as part of the SWP Upgrade to 8.0.5 (It was on 8.0.2)

This took about 45 minutes.

The TSW Poped open when CCA reconnected after upgrade and factory reset.

I noticed I had to select 'custom' for Locale and select NorthAmerica 10 (or I could have selected 7) and United States for Call progress Tones.

This is not in the release notes, but probably should be.  If you use default, you would end up with Argentina.

I added 9 users (various phone models for which I select phone loads to put on flash in the opening SW Upgrade dialog) and they were not plugged in (staging simulation and the way I build these as a best practice)

I selected 4 digit extensions

I used extensions 2001-2007 and an FXS 2020 and another phone 2028

Voice Mail set to 3099

AA set to 4000

AA Prompt manager set to 4500

Blast group 5001

Longest idel hunt group 5002

4:18PM EST:  I just completed entering data for the TSW and its applying now.  Since I  adjusted time zone it will take at least 20-30 more minutes (CUE has to  reload with timezone change from default PST).  Its 4:18PM EST

I hit F2 and F3 keys on my PC to watch it push the CLI.  I saw it create users in CME and CUE.  I saw it push AA scripts and promots I recorded during TSW to CUE.  BTW, I also see CCA using an Apache FTP service, so make sure you dont have any TFTP or FTP services binding to the required ports (use that connection prerequisite check list I passed you yesterday for details).

At around 53% I saw severl socket connection timeous occur, when I believe CCA was tring to get to CUE.

I manually jumped on a telnet and checked its status:

UC520#service-module integrated-Service-Engine 0/0 status
Service Module is Cisco Integrated-Service-Engine0/0
Service Module supports session via TTY line 2
Service Module is in Steady state
Service Module heartbeat-reset is enabled
Getting status from the Service Module, please wait..

Cisco Unity Express 8.0.3
CUE is on UC500UC500

At 71% after 4-5 retries, it got connected. Not sure what happened there, but I have the logs.  Good news is it keeps trying (about 5 minutes)

COmpleted after 40 minutes.

All worked.  I didnt even see the digit extension issue in release notes.

(click on that image to enlarge)

I am not seeing the problem, which means we need to isolate your issue with logs....

I am thinking you need to try without plugging phones in, since they will auto register and get default 3 digit extensions.  Do what I do, and it will probably work for you.

This tool me about 2 hours.  Can I get any more screen shots?   I checked VOICE and it was fine, except for a seven eighty five model that was on the swicth and I didnt know it.  It auto registered as 201.  But I chaged it easily to 2010.  Apply and it is there now too.  Voice mail is fine too.

Steve

[Steven DiStefano]

I checked Page Groups.  All 1001-1010.

When I clicked to enable one, I got that error at the bottom.  It said the leading digit is the same as the voice mail prefix.  So I unchecked 1001 page group 1 (the error disappeared.   CLosed the window.  Opened voice mail.  Sure enough, it was set to 1 (thats not cool for a default).  I changed it to 6.

This is what you use to dial as a prefix to hit the bosses email when he is on the phone and doesnt want more calls.

Went back to page groups.  Added all users to 1001 group 1 (emergency group) and applied.

That worked fine too.

I think there is a learning curve using CCA, but its much less than learning CLI, I assure you.

Steve