I don't really trust VOIP over wireless bridges.
It'd probably work, and if you were going to do it, you'd probably want to invest in g729 licenses, but I still don't like it. Then again, I know nothing about your VOIP implementation and your vendor may have some kind of proprietary implementation already.
The main thing you have to watch out for, though, is latency. The VOIP call is going to use about 150Kbps bandwidth, but when you get above about 200ms in latency, you'll notice some serious call quality issues.
If the only goal is to get an IP Phone at the remote location, you might consider looking into an ATA, such as the Linksys PAP2T. Put those on the close side and run a standard analog cable to the otherside. Those'll work with any standard SIP PBX and can be had pretty cheap. With that, you simply use any standard analog phone. Depending on your PBX, you may or may not be able to get any of the features. On the PBX that I sell and implement, we can offer full transfer, record, hold, call waiting, etc features to analog phones and even cell phones.
Alternatively, if you want a more advanced solution, you could look at something like the Citel Portico TVA, which is effectively a bridge from a SIP proxy server to a digital handset. These will give you some more advanced features, such as BLF, and allow you to tie back into your brand new SIP PBX. The Portico TVA is really a cool device with a lot of features. With it on the near side, you can use your existing CAT3 runs to get to your old digital phones (or buy a used digital phone...the Portico TVA supports a wide variety of phone emulation types).
There's all kinds of solutions to your problem. A wireless bridge might work, and if the only traffic you have is for the VOIP phone, you'll probably be OK...but if there's a lot more traffic going over it, you'll probably want to look into an alternative wired mechanism for the phone. Some spikes in latency are generally OK for a computer application, but for a VOIP phone call, they're not tolerable.