Hi,
I went through something similar because an earlier version of CCA had created a VLAN without assigning an IP, I start to use the 3.2.1 and as I entered on the screens went wrong; I had to do a careful work of CLI to satisfy CCA :-)
In your case I might have followed another path, but I throw there without having tried it ... assuming that everything is via DHCP: I created a new VLAN with a new class of IP and a DHCP pool and only after the active flag "default voice vlan" and restart the phones.
Just last week I made a renumbering of the vlan data and in the end I opted to switch from the CLI because,
among other, by inserting the secondary address on the interface and with a series of steps I was able to operate without interruption of service ... Then I cleaned everything and I have been happy CCA .
Ok, CCA is practical, but is slow and limits the possibilities. I remember, perhaps with the previous version, I have had an absurd error because I had to use an internal networks smaller than a Class C (256 IP): and, for example, reported (non-existent) conflicts between VLANs!!! That said, I would not like you have that problem because CCA is expected as the voice VLAN 100 and enough (despite the flag)!
73,
Arturo.
