Hi Jason,
You are correct - CTI Route Points don't work with BAT. Is it possible to use a wildcard pattern to cover the number needed?
We started to go down the road of inputting about 150 CTI Route Points. Way before we finished the system admin web page slowed to a painful crawl. We backed out and instead used a wildcard CTI Route Point such as 51XXX. Any phone with a more specific extension (51222) won't be affected since the exact extension is a better match than the 51XXX wildcard. The only thing we had to account for in the script is if someone dialed a 51XXX number that was not in service (since it does get picked up by the script).
HTH, Rob.