1. When re-recording an announcement, always delete the current announcement before recording the new announcement.
2. When recording over an old announcement be sure the announcement is not in use by vectors or hunt groups. If you just record over an announcement that is being used, you will more than likely corrupt the announcement and corrupt the checksum.
3. Always complete the recording of the announcement with the (#). If you fail to complete with a # and you just hang up, its possible to hang the announcement port used to record, for all announcement boards in the switch.
4. When you record and announcement or re-record and announcement, you should not try and access the announcement for at least 10 minutes. When the announcement is recorded, it requires 10 minutes to write to properly to memory. If you fail to do this then you can get locked up ports.
5. If you are unable to save announcements perform the following before escalating the fault: A failure to save announcements is often caused by a faulty system port. Unfortunately, the same system port will be chosen every time the "save announcements" command is executed, causing the command to fail reliably. To find the faulty system port, busy a system port and retry the "save announcements" command. When the command finally works, you've found the faulty system port.
Another point to be aware of : The reason Avaya request announcements are to be deleted before re-recorded is that if you have an announcement that is 10 seconds long and you re-record this announcement and it only lasts for 8 seconds you will have 2 seconds left over and this is stored in an announcement number 0. If you see this on any announcement board the only way to remove this is by erasing the board.