Thanks for sharing your thoughts, I'm afraid I don't agree that changing to Teamspeak is necessary though.
This is for everyone's benefit - not just mine! Nobody wants to hear your dog-barking or your phone ringing or BF2 coming out of your Speakers!
People seem to have great difficulty finding a suitable Push To Talk key. It's really not that hard if you put a little effort in and are willing to be creative / change a BF2 key. CAPS Lock / CTRL are good choices if you are struggling. Some people use their Mouse Scroll Wheel Click which is usually Mouse Button 3.
Following what S_h_a_r_k_93
told you, it seems like you had your Sensitivity configured incorrectly anyway. It doesn't sound like you are in a position to compare VOIP software if you haven't even configured the settings, you are not giving Ventrilo a fair chance...
This is fair enough, Ventrilo is more common in communities for other games like Counter-Strike. However, that's not a reason to switch. We have a simple Install / Setup Guide for Ventrilo. If people want to take their vocal communication beyond In-Game VOIP with Commander/Squad they can download it.
It really depends what time you check, I'm often on Ventrilo in the evening or later and we have had quite a few different people in Ventrilo at times. Civilains, Enlisted Soldiers, [LS] Members & Admin all together. Ventrilo gets more usage than you realise.
Low Sound Quality & Many Security Vulnerabilities.
why did I never think of this before? I'll get to work on that right away...
Whilst I do think your intentions are good, I feel like you are on a bit of a personal crusade against Ventrilo because you're a Teamspeak lover / Ventrilo hater. Teamspeak is really not good quality VOIP software as far as I'm concerned, if you get used to Vent you'll realise it's superior too. There are 5 main reasons why I prefer Ventrilo:
1) Financial, we host the Ventrilo Server ourselves, we'd have to pay for Teamspeak
2) Sound Quality
3) I already did a lot of work coding to integrate Ventrilo into the site
4) Security Vulnerabilities in Teamspeak
5) Teamspeak's ugly interface