As a practical matter, you should think about sending the text messages.

First off, what's the backup plan if your cell phone is off or you're out of range? Where do they get sent next?

Second, is this your personal cell phone or a company phone? Does your cell provider charge for text messages? It would really suck to have a month plagued with server outages and then get a $100 bill for 1000 text messages. If your company requires that you be on call 24/7, and answering text messages at 4 am is part of the job, they should be paying for the phone. Make sure they know about your plan.

Third, make sure that the phone number is stored in an easily-accessable variable, preferably in a config file, rather than hard-coded. If you move to another company or position or go on vacation, you don't want to keep getting messages.

Fourth, since this code is going to live on 12 different servers, revision control is going to be very important. If you aren't already familiar with CVS, now would be a good time to learn.

-Logan
"What do I want? I'm an American. I want more."