{"id":253,"date":"2005-04-12T07:51:26","date_gmt":"2005-04-12T15:51:26","guid":{"rendered":"http:\/\/boulter.com\/blog\/2005\/04\/11\/253\/"},"modified":"2005-04-11T20:52:51","modified_gmt":"2005-04-12T04:52:51","slug":"how-i-killed-my-answering-machine-part-ii","status":"publish","type":"post","link":"http:\/\/boulter.com\/blog\/2005\/04\/12\/how-i-killed-my-answering-machine-part-ii\/","title":{"rendered":"How I Killed My Answering Machine: Part II"},"content":{"rendered":"<p><em>This is the second of seven parts of 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\u00e2\u20ac\u2122s how complicated. <\/em><\/p>\n<p><strong>Part II: More Modems and Windows<\/strong><\/p>\n<p>On December 16, 2003 I bought a Lucent 56K V92 PCI Modem off eBay for $9. This was a software-based (controllerless) modem, but supposedly there were Linux drivers as well. By this time I had pretty much given up on Linux. Between poor driver support and trouble just getting the voicemail software installed, it just wasn&#8217;t worth it. Instead, I stumbled across <a HREF=\"http:\/\/www.callsoftpro.com\">CallSoft<\/a> (via a paid link on Google no less) which was amazingly feature-rich and configurable. Best of all I could just install it and forget about it.<\/p>\n<p>Plan C: Windows<\/p>\n<p><img SRC=\"http:\/\/www.microsoft.com\/windows\/images\/homepage\/products\/winFamLogo_XP.gif\" ALIGN=\"RIGHT\" \/>But even using real drivers on Windows, I found a problem. The caller ID worked, but only when there was a name with the number. So if caller ID just returned a number, it didn&#8217;t show anything at all. Useless. I installed, uninstalled and reinstalled the drivers on windows over and over again but didn&#8217;t have any better luck.<\/p>\n<p>CallSoft seemed to be working well though, so I registered it on Jan 6, 2004 for $50. It still didn&#8217;t like the modem though, so I broke down and bought one of the <a HREF=\"http:\/\/www.callsoftpro.com\/callsoft\/modems.html\">recommended modems<\/a> for CallSoft.  <a HREF=\"http:\/\/store.yahoo.com\/directron\/mdm-aopen-56-pci.html\">Modem #4<\/a> was purchased for $29 on Jan 22.<\/p>\n<p>This new modem finally worked well. It worked for voicemail, the caller ID worked and CallSoft liked it. The only annoying problem is that it displayed an &#8220;O&#8221; as the caller&#8217;s name when only a number was returned from caller ID, but I could live with that.<\/p>\n<p>I also turned on the speech support and downloaded the professional voices from IBM. When a call came in, it would speak the name and number loudly from our office and send a windows popup to my laptop with the number. Voicemail would be recorded and sent via email as an MP3 attachment. For solicitors, I could play a &#8220;do not call&#8221; message back to them, targed by caller id. I also found that by turning down up the number of rings before answer to 6 or so, most telemarketers wouldn&#8217;t wait that long to place a message. This was pretty sweet. I had myself a 40-pound, 120-watt uber-answering machine. I put the old answering machine up in the attic.<\/p>\n<p>Too bad the new machine wasn&#8217;t reliable. Sometimes I would come home and find that CallSoft had crashed or just didn&#8217;t pick up. After a while the speech stuff stopped working too and it just wouldn&#8217;t speak when a call came in. I &#8220;fixed&#8221; CallSoft&#8217;s reliability problems by installing <a HREF=\"http:\/\/yasoft.km.ru\/eng\/switchoff\/\">SwitchOff<\/a>, a little utility that rebooted my &#8220;answering machine&#8221; every night. It was very annoying that I couldn&#8217;t trust my answering machine though. Random people would tell us that our answering machine was broken or didn&#8217;t pick up. We always knew when it was 10 pm because we&#8217;d hear the &#8220;answering machine&#8221; reboot from the study.<\/p>\n<p><img ALIGN=LEFT SRC=\"http:\/\/scd.mm-a.yimg.com\/image\/930920919\" \/>In September I found myself with a Sharper Image gift certificate, so I got myself one of those <a HREF=\"http:\/\/www.sharperimage.com\/us\/en\/catalog\/productview\/sku=WI701&#038;cm_ven=inkt&#038;cm_cat=Media&#038;cm_ite=WI701\">spinning info globes<\/a>, purely as a highly-visible caller id display. That works pretty well actually and had some additional coolness factor, even if it does make noise all the time. It sure beat running over to a phone and squinting at the LCD.<\/p>\n<p>In October, I got tired of getting kicked off my wireless network every time the phone rang, so I upgraded to a <a HREF=\"http:\/\/www.amazon.com\/exec\/obidos\/ASIN\/B0000CDELC\/thescrabblera-20\/104-7198839-3467968\">Motorola 5.8 Ghz phone system<\/a> with <a HREF=\"http:\/\/www.amazon.com\/exec\/obidos\/ASIN\/B0000CDEJU\/thescrabblera-20\/104-7198839-3467968\">two extra handsets<\/a>. This was great because I could now put the handsets wherever I wanted them rather than where the phone outlets were. I had set up some power line adapters, but because of the how the circuits are laid out in the house, I still had to run a long phone line to get the phone where I wanted it to be. No more. And I now had a phone with lounging reach of the couch. I still occasionally have problems with interference when my phone rings, but I&#8217;m not sure it&#8217;s worth fixing at this point. <img SRC=\"http:\/\/images.amazon.com\/images\/P\/B0000CDELC.01-A1YEXO1PH1L14S.TZZZZZZZ.jpg\" ALIGN=RIGHT \/><\/p>\n<p>These purchases had nothing to do with voicemail per se, but they did solve some of my telephony problems, even if CallSoft wasn&#8217;t still doing what I wanted.<\/p>\n<p><em>Next, Part III: Lingo<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>This is the second of seven parts of 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\u00e2\u20ac\u2122s how complicated. Part II: More Modems and Windows On December 16, 2003 &#8230;<\/p>\n<p><a href=\"http:\/\/boulter.com\/blog\/2005\/04\/12\/how-i-killed-my-answering-machine-part-ii\/\" class=\"more-link\">Continue reading &lsquo;How I Killed My Answering Machine: Part II&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-253","post","type-post","status-publish","format-standard","hentry","category-general"],"_links":{"self":[{"href":"http:\/\/boulter.com\/blog\/wp-json\/wp\/v2\/posts\/253","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=253"}],"version-history":[{"count":0,"href":"http:\/\/boulter.com\/blog\/wp-json\/wp\/v2\/posts\/253\/revisions"}],"wp:attachment":[{"href":"http:\/\/boulter.com\/blog\/wp-json\/wp\/v2\/media?parent=253"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/boulter.com\/blog\/wp-json\/wp\/v2\/categories?post=253"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/boulter.com\/blog\/wp-json\/wp\/v2\/tags?post=253"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}