{"id":252,"date":"2005-04-11T07:09:55","date_gmt":"2005-04-11T15:09:55","guid":{"rendered":"http:\/\/boulter.com\/blog\/2005\/04\/11\/how-i-killed-my-answering-machine-part-i\/"},"modified":"2005-04-11T07:32:21","modified_gmt":"2005-04-11T15:32:21","slug":"how-i-killed-my-answering-machine-part-i","status":"publish","type":"post","link":"http:\/\/boulter.com\/blog\/2005\/04\/11\/how-i-killed-my-answering-machine-part-i\/","title":{"rendered":"How I Killed My Answering Machine: Part I"},"content":{"rendered":"<p><em>This is the story of how I killed my answering machine. How complicated can it be to replace a simple little device with something a little more geeky? About 17 months, $500 and countless hours &#8211; that&#8217;s how complicated. This story is ridiculously long, technical and includes lots of geeky terminology, so if you&#8217;re not into that sort of thing, check this space in a week for something resembling regularly scheduled programming. I&#8217;ve broken the story up into seven parts because I can&#8217;t imagine someone trying to read the whole thing in one sitting.<\/em><\/p>\n<p><strong>Part I: A Simple Plan of Execution<\/strong><\/p>\n<p>I think it&#8217;s finally dead.<\/p>\n<p><a HREF=\"http:\/\/boulter.com\/blog\/2003\/11\/17\/please-help-me-kill-my-answering-machine\/\">I&#8217;ve hated my answering machine<\/a> for a long time now. In 2003 I hatched a plan to kill it. <\/p>\n<p>The simple idea was to put one of my mostly idle computers to good use and use it as my answering machine. I would get rid of all the annoying buttons and blinky lights and have something nice and usable. I would be able to listen to messages over the web or just have them emailed to me. That&#8217;s all I wanted. <\/p>\n<p>Plan A: Mac OS X<\/p>\n<p>I have a PowerMac G4 that&#8217;s basically my home server and I would love it if Apple included voicemail software with OS X. Sadly the modems in their machines are not voice-capable. I used to have an voice-capable external 56K modem, but I have no idea where it went. Since my last rant on the topic, <a HREF=\"http:\/\/www.parliant.com\/phonevalet\/?l=2\">PhoneValet<\/a> got an upgrade and seems like a good solution for Mac OS X, but it&#8217;s $200!<\/p>\n<p>Plan B: Linux<\/p>\n<p><img SRC='http:\/\/www.vocpsystem.com\/images\/logoVOCP.gif' ALIGN=RIGHT \/> My next best idea was to repurpose an old Pentium II I had lying around as a Linux server and run some software there. <a HREF=\"http:\/\/www.vocpsystem.com\/\">VOCP<\/a> would supposedly do everything I wanted. Great. <\/p>\n<p>First I had to get a Linux distribution on the PC. Hmm, I don&#8217;t have a CD burner on the PC. Thankfully Apple&#8217;s Disk Image utility handles ISO images just fine and I was able to download Red Hat, burn it to two CDs and pop it into the PC. I had it reformat the drive, wiping out XP and setting up its own partitions. The install went fairly smoothly although it asked me way more questions than I really cared to bothered with. In the end I had a working Linux system &#8211; or so it seemed.<\/p>\n<p><img SRC=\"http:\/\/frys.com\/images\/CHARLIshine.gif\" ALIGN=LEFT \/> Meanwhile, I ran over to <a HREF=\"http:\/\/frys.com\/\">Fry&#8217;s<\/a> and bought a modem, carefully avoiding anything that said &#8220;WinModem&#8221;, knowing it probably wouldn&#8217;t work with Linux. I came back home on November 23, 2003 with a Best Data modem for $32.46 and threw that in the machine. <\/p>\n<p>Now the fun was getting the modem drivers working. I played around with all the software and compiled stuff, but it wouldn&#8217;t work. Then I thought that it might be a good idea to see if this modem isn&#8217;t DOA first. Windows drivers came in the box of course. Too bad I wiped out Windows. Red Hat was acting weird anyway. It wouldn&#8217;t download any updates. The registration utility just kept crashing. <\/p>\n<p>I thought I would just install Windows into some free space on the drive. I searched around on the web for answers on how to do this. The answer: you can&#8217;t. You have to install Windows first, then Linux. Doh! Having Windows seemed to be the best course of action, so I copied a few of the files I worked on over to my Mac, reformatted the PC disk and installed Windows XP again. Once that was done, I installed Red Hat into another partition. Great. Now I can dual boot. <\/p>\n<p>Now the good news was that the modem was recognized and worked in Windows. The bad news was that I discovered something about the modem &#8211; it didn&#8217;t seem to have any voice capabilities. I looked up the modem info on the internet and sure enough, it was NOT a voice modem, even if the box said it was. This extended my streak of bad Fry&#8217;s experiences to about 9,000 or so in a row. <\/p>\n<p><img SRC='http:\/\/pics.ebaystatic.com\/aw\/pics\/navbar\/eBayLogoTM.gif' ALIGN=RIGHT \/> After performing the painful return ritual at Fry&#8217;s, I went onto eBay on Nov. 24 and bought another modem.  My consolation was that this modem as about $25 cheaper than the one I got at Fry&#8217;s &#8211; $8. It was an Intel modem, based on the Ambient MD563X-HaM chipset which supposedly would work for voicemail.<\/p>\n<p>A few days later that one arrived and I started playing with it. After messing with AT modem codes for a while in Linux(it&#8217;s been a LONG time since I did that), I gave up and decided to get it working in Windows. This modem was recognized and seemed to work, except it didn&#8217;t show caller ID. (I drove Anne crazy calling our phone over and over to test this.) While the chipset was supposed to support it, it didn&#8217;t work in these modems. Sure enough, the eBay listing didn&#8217;t show caller id as a feature and I didn&#8217;t read it carefully. Back to eBay.<\/p>\n<p><em>Next: Part II, More modems and Windows<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>This is the story of how I killed my answering machine. How complicated can it be to replace a simple little device with something a little more geeky? About 17 months, $500 and countless hours &#8211; that&#8217;s how complicated. This story is ridiculously long, technical and includes lots of geeky terminology, so if you&#8217;re not &#8230;<\/p>\n<p><a href=\"http:\/\/boulter.com\/blog\/2005\/04\/11\/how-i-killed-my-answering-machine-part-i\/\" class=\"more-link\">Continue reading &lsquo;How I Killed My Answering Machine: Part I&rsquo; &raquo;<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-252","post","type-post","status-publish","format-standard","hentry","category-general"],"_links":{"self":[{"href":"http:\/\/boulter.com\/blog\/wp-json\/wp\/v2\/posts\/252","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/boulter.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/boulter.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/boulter.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/boulter.com\/blog\/wp-json\/wp\/v2\/comments?post=252"}],"version-history":[{"count":0,"href":"http:\/\/boulter.com\/blog\/wp-json\/wp\/v2\/posts\/252\/revisions"}],"wp:attachment":[{"href":"http:\/\/boulter.com\/blog\/wp-json\/wp\/v2\/media?parent=252"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/boulter.com\/blog\/wp-json\/wp\/v2\/categories?post=252"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/boulter.com\/blog\/wp-json\/wp\/v2\/tags?post=252"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}