I like many others have struggled to get Caller ID working in VMC using a x64 bit server. I had this licked for a while when my main PC was 32-bit, but I upgraded to x64 and was stuck using the old box for caller id -- until now!
See this post for the 32-bit solution: http://thegreenbutton.com/forums/thread/254068.aspx
Here's how I got the x64 caller ID love:
Hardware
Software
HKLM/Software/YAC/Device Agere Systems PCI-SV92PP Soft Modem
HKLM/Software/YAC/StartUpSelectDevice 0
HKLM/Software/YAC/PlaySounds 0
Finally, for good measure I suppose, I executed the .cmd file (as administrator) that comes with MCE-YAC and got 'success' messages all-around (not so prior to the manual copying).
Don't forget to add your listeners to the YAC server settings. (These seem to work, as they are written a .ini file)
Drawbacks
Otherwise, it's a good solution. If you find a decent client, or solve the logging issue, please post here. Hope this helps!
SUPER-STABLE SETUP
System: Windows 7 64-bit; MSI 785GTM-E45; AMD Phenom II X6 1045T (95W)Hardware: 1.5TB WD Green HDD; 4GB (2x2GB) DDR2 800 SDRAM; Silverstone Grandia GD04B; Scythe Shuriken Rev B.Tuners: HD HomeRun; Ceton InfiniTV 4Networking: Linksys DMA2100 (x2); Xbox 360; Netgear WNDR4000 Router; WHS (Acer EasyStore AH341);Display: Samsung HP-R4252
Update...
I changed the permissions on the on both the log and the .ini file, giving user 'everyone' full control. YAC now seems to correctly write to these files.
Thanks for this. I had issues getting the Rosewill modem caller ID to work under Server 2008 x64, and that utility did the trick. Funny, I found this through Google not TGB search, but still ... thank you.
FWIW, you can add TapiRex to the list of things this works with. You only need to set it for "Data Modem" on the server after you've done all the above steps.