Yes. rfcomm bind doesn't survive a reboot.

BTW, I discovered a problem with opening /dev/rfcomm*. If the bluetooth GPS receiver is not turned on, the user interfce hangs while the kernel is attemting to bind to the device. Makes the user interface pause for the timeout period between every UI event. Click .... timeout .... click .... timeout .... click. I usually just turn off "Enable GPS" if I'm going to leave the GPS receiver off.