Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I have three subscribers that are too old to upgrade, and apparentlytoo old to take advantage of the new bridge upgrade feature.I have three new servers itching to replacement, but no media thatmatches the vintage running on the old servers.The three...
I am faced with the requirement to consolodate Unity servers from five timezones intoone central system. The user account side of the house is fairly straight forward,just using GSM to move accounts and bulk edit to set the appropriate timezoneand d...
I have a pair of ACE modules installed and maintained through ANM. Westarted with ANM 2.X and recently upgraded to 3.0.The ACE modules were running code A1(6.3) and are now on A2(2.3).ANM is identifying the devices as Device Type ACE v1.0, and devic...
Earlier this week we had a Sup720 fail. It was in a master/slave (SSO?) config and the backup properly took over running the switch.Unfortunately the failed blade did not fail completely, and kept rebooting attempting to reclaim control and then reb...
I am stuck during an upgrade from 4.0(5) to 4.2(1).This is the tenth server using the same media image, and the only one to have a problem. The install claimes that \CD1Support\CommonIWF.txt has a bad path, except the install media does nothave a CD...
We are also using Lync for conferencing and have the unwanted MOH during Lync conferences.I have already setup MGRL and device pools that have no MOH or multicast MOH devices configured.We recently upgraded from 8.0(2) to 9.1(2) and the problem pers...
I hust ran into a similar situation, not involving a group of ports, but arange of networks-object-group network Ahost 10.10.10.1object-group network Brange 192.168.0.0 192.168.4.255ip access-list extended firewallpermit tcp object-group B object-gro...
Thanks for the tip about the COBRAS tool. I am actually finding itbetter to migrate the handlers manually. After close to seven yearsof tweaks and changes, may are either orphaned or nor valid any longer.As for the info about call handler timezone ...
We have been using the T chain/series for a good long time and for a lack of a better reason, we trust it.I was/am willing to consider another chain, if I could find out what features or stability I might give up. I did look to see what was the focu...
At one point I found a note that this feature was also in 12.4(15)T. That document has vanished, and the feature is definately not in that release.I have not been able to get an answer from my rep when/if this feature will go into the T series....