Decent UK Caller ID Modem

I have been using a rather ancient Pace voice modem, and also experimented with a Crucible Meteor dedicated CLI device. The Pace modem was OK, but it's not on the UPS and if it power cycles the Cortex PC doesn't recognise it as present when it starts up again. For various reasons it is not on the UPS that protects the PC. The Crucible device is consistent, but unfortunately not supported by Cortex, so it's data cannot be used.

Since I was building a more powerful PC to allow for CCTV monitoring, I launched into a search , not really expecting much. But I did come across mentions of successful use of a Zoom modem model, although most references were from 2005. Surprisingly I found an almost identical model in PC World going at about £19 for the PCI internal version. It was model 3025-72-00CF, not exactly the one recommended, which didn't have the 'F'. Although tiny model variations can often spell the difference between success and failure with UK CLI support, and since I knew the 'L' variant definitely did not work, I took the risk and bought it.

To cut a long story short, it works, but you do need to follow the instructions I found here.

So, no guarantees, since Zoom might sneak in a change, but if you are willing to gamble £20, the Zoom 3025-72-00CF may well do the job.

Update
Unfortunately I have found the modem won't do audio output via TAPI. So although it will do CLI very well, it's no use for providing the answering machine functions and remote control capability for Cortex. It seems the success reports found on the web relate to it being used with the dedicated voice program supplied with it. This is something to do with IS-101 support only, it seems.

Update
Well, never believe what you read on the web. I've done a bit more debugging of the voice support with this modem. It seems that enabling the CLID using the driver string hack leads to a later problem when the modem tries to switch to voice mode. The modem command manual is, frankly, not very helpful.

The modem log shows that an error is returned when the

at+vls=1

command is executed. This command switches the modem into voice mode, but it seems that it conflicts with the CLID mode. After some experimentation I found that I could edit the driver strings to turn CLID off. I found that this needs to be done at the beginning of the sequence:

HKR,  VoiceAnswer,            1,,   "at+vcid=0"

HKR,  VoiceAnswer,            2,,   "at+fclass=8"

HKR,  VoiceAnswer,            3,,   "at+vtd=10"

HKR,  VoiceAnswer,            4,,   "at+vsm=130,8000,0,0"

HKR,  VoiceAnswer,            5,,   "at+vit=6"

HKR,  VoiceAnswer,            6,,   "at+vls=1"

However, I still find that the modem is not getting answered automatically by Cortex. Both the modem log and the Cortex log show that ringing is detected. Manually answering then correctly goes into wave play and record. I probably need to try and use one of the supported voice programs and log the command sequence through the COM port. But modem testing is intrusive since I have to keep stopping and starting Cortex to release the modem and reboot the machine to update the driver. So I have removed the modem for the time being and will experiment some more with a test machine.