VoIP does not generate a lot of traffic, what it DOES generate is traffic that can not afford to wait or be dropped. With 1000 phones at my employer, we just barely generate 10 meg of traffic. It can not be put in a 10 meg pipe however as no packet can afford to wait its turn, we run it in 100 meg and gig trunks so it never needs to wait.
I have no trouble visualizing VoIP over a 'modern' 10 meg with QOS and ideally full duplex to end user devices, so long as the upstream aggregate trunks are 100 meg or better.
I do worry that a 10/100 card may (not knowing they are on Cat3) try to acheive 100/full and fail, you may need managed switches to allow you to hard code 10 meg at the switch, but you want switch management to enforce QOS anyway
10/Auto at the switch, and Auto at the card over Cat 3 is ugly but doable, if the switch can't do 10/auto 10/Full at the switch and 10/Full at the card is even uglier but doable. ( you would have to hand configure every station, rather than just the switches)
If I had to accept 10/Half at the Card and Auto at the switch I would start using weasel words with my bosses about how well this would work. (when I started VoIP with Nortel their gear was 10/Half, so it can work, but you need to really eleminate all other traffic)
You need to stress that there can be no hubs or unmanaged switches anywhere in the network that does VoIP, if your company has folks who add to the network without supervision you will start finding them all over when you begin doing VoIP, look for multiple MAC addresses on what you thought was a single port.
I tried to remain child-like, all I acheived was childish.