Cause and Solution to the Chirp Sound
The chirp is not in the recording. It's actually before the recorded greeting starts.
The chirp sound at the beginning when the VoicePro goes off hook answering a call is a result of a high-voltage spike from the ring voltage that overloads a protective capacitor. The capacitor quickly disperses the voltage, causing the chirp.
The problem occurs in isolated cases and we have found it to be reported at customers sites who never had the problem before, until some recent equipment changes were introduced by their local phone companies using digital technology to send the calls long distances and then changing to analog at the CO for the final leg to the customer's site.
We also found it to relate to poorly designed VoIP adapters that use a higher ring voltage.
The solution is to let the VoicePro wait until the first ring as stopped. That way the transient voltage spike is missed and does not cause a chirp.
This can be accomplished with a simple programming change. Use Function 30 to set the rings before auto attendant to 1, not zero. That's all. The chirp is gone.
There is a side effect, however. Since you now programmed it to answer after one ring, that first ring will pass through to your extensions. The VP206 is preset so that line 1 rings extension 10 and line 2 rings extension 11. The VP412 also continues with line 3 ringing ext 12 and line 4 ringing ext 13.
You might ask why the VoicePro does this. There are situations where one may want to have incoming calls ring to extensions before the auto attendant answers. So they set Function 30 to a much higher ring count and either use the preset ring assignment or they assign their own with Function 4.
If you want to eliminate the single ring, you can program your VoicePro to assign all lines to ring to an unused extension. Example: Say you don't have a phone connected to ext 15. Then use Function 4 to assign CO line 1 to extension 15 and also CO line 2 to extension 15. With the VP412 you also need to assign CO lines 3 and 4 to extension 15. That solves that issue as well and you are good to go.
