Since you have both tx and rx available it is the F-Bus. In this case the baud rate is 115,200, there are 8 bits per transaction + 1 stop bit and no parity bit. DTR must be set and RTS must be cleared for data to be sent/received. This DTR/RTS pair supplies power.
So first you have to set your terminal program for these settings. I don't know what terminal you are using but I know that RealTerm(Free) is a good one that gives full control and is intuitive. Make sure you also use the right COM port, possibly COM1 if you have only one port on your PC.
Make sure that the RX from the MAX 232 is connected to TX on the PC and TX is connected to RX. This can be done at the connector end. Crossover cables do this for you, but since you will most likely cut the other end of the cable to connect to the phone make sure what I said is taken care of by testing with a continuity checker or ohm meter. Also make sure DTR/RTS are connected with two wires for power. And don't forget the GND wire. Finally make sure the MAX232 has proper power and GND, although I'm sure you have done this.
After these steps are taken you have to send 'U' or hex 0x55 128 times to sync the transceiver. Then it should work and reply to Nokia Commands given at **broken link removed** . I don't know if it works with AT commands. These should be the only problems that are making the comm fail; check each one of them thoroughly as any one of them will cause comm failure.
If after doing the above you still receive no reply, you should use a sniffer to see what is being sent from the terminal and phone. A sniffer can be made with another terminal/Serial Port/cable combo attached in parallel with the original link. In this case the sniffer RX can be connected to the TX of the PC to listen to PC to phone transactions and to the RX of the PC to listen to stuff coming back from the phone.
Let me know how it goes.