<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Topic &#x27;Call screening touch tone feature on Home Phone line&#x27; in forum &#x27;TekSavvy&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Call-screening-touch-tone-feature-on-Home-Phone-line-26970776</link>
<description></description>
<language>en</language>
<pubDate>Sun, 26 May 2013 04:06:17 EDT</pubDate>
<lastBuildDate>Sun, 26 May 2013 04:06:17 EDT</lastBuildDate>

<item>
<title>Call screening touch tone feature on Home Phone line</title>
<link>http://www.dslreports.com/forum/Call-screening-touch-tone-feature-on-Home-Phone-line-26970776</link>
<description><![CDATA[wally_walrus posted : I receive repeated phone calls from certain numbers (telemarketers)  that won't stop even though I told them I am not interested in their offers (stupid me for putting my numbers on the Do Not Call List). So tired of all this, I decided to order the Call Screening feature available for the Home Phone POTS service. Feature was activated the next day, but it seems that I cannot add the numbers I want to the screening list. I'm on the phone with support right now, but googling I found this:<br><br>&raquo;<A HREF="http://support.bell.ca/en-on/HomePhone/Calling_features/I_can_t_add_a_number_to_my_Call_Screen_list" >support.bell.ca/en-on/HomePhone/&middot;&middot;&middot;een_list</A><br><br>Given more and more numbers are VOIP, cell phones, etc the feature becomes useless. Actually the support rep just came back saying that Bell confirmed the above limitations are true (saying it was designed in the 80s when they owned all the numbers). Why they cannot update the feature to support newer phone line types is beyond me. And who would actually order such a useless service nowadays?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Call-screening-touch-tone-feature-on-Home-Phone-line-26970776</guid>
<pubDate>Mon, 05 Mar 2012 17:22:57 EDT</pubDate>
</item>

</channel>
</rss>
