Today was an eventful day. Talisa was acting obnoxious, although I managed to get on with it. I wanted to go to the store, but didn’t make it. I was however able to get my SIP line optimized. I also found a service that would work well with not only SIP Broker, but eNUM as well. In anticipation with the installation of the FiOS phone service, I am setting up dialing rules. These dialing rules will tell the phone which account to use when a call is made. For example, if someone calls 911 from the house phone, it will use the Verizon line since it supports 911. This is one of the things that I worked on.
I also worked on a couple of the pages on my Wish List. It wasn’t anything fancy, but still wanted to make some adjustments. I also had a small headache which I am sure I will recover from. Otherwise, this day was pretty quiet. I did a couple of other things, mostly technical in trying to resolve a problem with a SIP line. As for plans for tomorrow, I would need to make it to the grocery store, and the post office. It would seem as if my morning would be gone. I would have a couple of other things to take care of, and eventually seek to move a couple of things in preparation for the upgraded service that would happen on Tuesday.
With the news that AT&T is going to buy out T-Mobile, unless the US Regulatory stops it (like that would happen), it would seem as if I would end up paying more than I would like for phone service. If I was to go with AT&T choosing either a locked up iPhone, or just as locked up Android phone, it would seem as if no matter what, I would have to consider trying to reduce my demands. So far, the best option is to use an IAX server, along with a dedicated Google Voice account.
However, the problem is to find a budget friendly, and resource friendly system. In goals to try to keep things to less than $150, it would mean I would have to rely on used systems that are either lacking in capability, and/or power hungry. One example is a 160 watt Dell Optiplex which only has 256MB of memory for about $90. Now, mind you – the system won’t be running at 160 watts all of the time, but as with all servers, it should be running 24/7. Even at 100 watts, this would mean that every day, the server will cost 2.4kw. In a month, that would be 72kw per month. On someone that has to pay for electricity, and on a tight budget, that is discouraging. This is one reason I am not considering commissioning my desktop to the task. I’m assuming 3¢ per kilowatt as I hadn’t received my first electric bill yet, this could mean an extra $30 per year just to make phone calls While this may not sound like much, keep in mind that I am on a tight budget, and there is a refrigerator that runs 24/7 as well as an iPod dock that runs nearly 24/7. Either dock is only 10 watts per hour which means that the iPod dock would require 10 days of 24/7 usage for it to rack up the same power demands the server will require in 1 day. Thankfully, servers don’t require monitors beyond the initial setup. A better option will be an HP that is used in a smaller package, but with a slightly faster CPU, and more memory.
Continue reading Easier Said than Done