<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: BT Call Guardian suddenly challenging 'Allowed' numbers. in Everything else</title>
    <link>https://community.plus.net/t5/Everything-else/BT-Call-Guardian-suddenly-challenging-Allowed-numbers/m-p/2012133#M38705</link>
    <description>&lt;P&gt;Thank you for responding.&lt;/P&gt;
&lt;P&gt;I understand what you mean, and it's entirely plausible - but in this case I'm not convinced it is the explanation, because almost always (as far as I can remember) I had entered the contact into the phone book and relied on that to make it "allowed". The difference was, having cleared out the allowed list and the phone book,&amp;nbsp;&lt;EM&gt;&lt;STRONG&gt;I&lt;/STRONG&gt;&lt;/EM&gt; put the number into the allowed list (which allowed the call through unchallenged),&amp;nbsp;&lt;STRONG&gt;&lt;EM&gt;then&lt;/EM&gt;&lt;/STRONG&gt; manually entered name and number into the phone book (which changed the display from a number to a name).&amp;nbsp; My analysis is the software in the base got corrupted and lost the link between phone book and allowed list for at least three contacts - so I assumed it was universal and re-entered all.&lt;/P&gt;</description>
    <pubDate>Sat, 28 Jun 2025 11:17:25 GMT</pubDate>
    <dc:creator>Robot</dc:creator>
    <dc:date>2025-06-28T11:17:25Z</dc:date>
    <item>
      <title>BT Call Guardian suddenly challenging 'Allowed' numbers.</title>
      <link>https://community.plus.net/t5/Everything-else/BT-Call-Guardian-suddenly-challenging-Allowed-numbers/m-p/2011284#M38689</link>
      <description>&lt;P&gt;I've had a BT8600 cordless phone for many years, working faultlessly until a few days ago when it challenged a close relative whose number was in the phone's directory and thus an "Allowed" number. Then I discovered it did the same to my own mobile number too.&lt;/P&gt;
&lt;P&gt;After some Internet searches - one of which blamed the ADSL filter (not that), I tried various things. &lt;FONT face="Helvetica, Arial, sans-serif"&gt;First,&amp;nbsp;I tried adding myself as an 'Allowed number', and it wouldn't let me - it was already allowed (being in the phone's directory). So I deleted myself and added myself back - still the same, I got the challenge. &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Helvetica, Arial, sans-serif"&gt;Then having a devious brain, I deleted myself from the directory and added my number to the allowed list. It took it and the phone rang - displaying the mobile number (but of course it didn't know it was "Me", I wasn't in the directory at this point). &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Helvetica, Arial, sans-serif"&gt;This was encouraging. I then added myself back to the directory and it worked as it should, ringing straight away without the challenge and displaying "Me".&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Helvetica, Arial, sans-serif"&gt;The same procedure worked for my relative.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;I hope this helps someone - from my research, it appears to be a not uncommon fault.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jun 2025 14:23:40 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/BT-Call-Guardian-suddenly-challenging-Allowed-numbers/m-p/2011284#M38689</guid>
      <dc:creator>Robot</dc:creator>
      <dc:date>2025-06-19T14:23:40Z</dc:date>
    </item>
    <item>
      <title>Re: BT Call Guardian suddenly challenging 'Allowed' numbers.</title>
      <link>https://community.plus.net/t5/Everything-else/BT-Call-Guardian-suddenly-challenging-Allowed-numbers/m-p/2012130#M38704</link>
      <description>&lt;P&gt;Best guess is that, for some reason, the "presented" number changed (from say 0789 xxxxxxx to +44 789 xxxxxxx) and thus was seen as different.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I've had this with remembered mobile numbers in my mobile phone.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Porting to a different network or even an equipment update by an existing network might cause this.&lt;/P&gt;</description>
      <pubDate>Sat, 28 Jun 2025 09:55:54 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/BT-Call-Guardian-suddenly-challenging-Allowed-numbers/m-p/2012130#M38704</guid>
      <dc:creator>markhawkin</dc:creator>
      <dc:date>2025-06-28T09:55:54Z</dc:date>
    </item>
    <item>
      <title>Re: BT Call Guardian suddenly challenging 'Allowed' numbers.</title>
      <link>https://community.plus.net/t5/Everything-else/BT-Call-Guardian-suddenly-challenging-Allowed-numbers/m-p/2012133#M38705</link>
      <description>&lt;P&gt;Thank you for responding.&lt;/P&gt;
&lt;P&gt;I understand what you mean, and it's entirely plausible - but in this case I'm not convinced it is the explanation, because almost always (as far as I can remember) I had entered the contact into the phone book and relied on that to make it "allowed". The difference was, having cleared out the allowed list and the phone book,&amp;nbsp;&lt;EM&gt;&lt;STRONG&gt;I&lt;/STRONG&gt;&lt;/EM&gt; put the number into the allowed list (which allowed the call through unchallenged),&amp;nbsp;&lt;STRONG&gt;&lt;EM&gt;then&lt;/EM&gt;&lt;/STRONG&gt; manually entered name and number into the phone book (which changed the display from a number to a name).&amp;nbsp; My analysis is the software in the base got corrupted and lost the link between phone book and allowed list for at least three contacts - so I assumed it was universal and re-entered all.&lt;/P&gt;</description>
      <pubDate>Sat, 28 Jun 2025 11:17:25 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/BT-Call-Guardian-suddenly-challenging-Allowed-numbers/m-p/2012133#M38705</guid>
      <dc:creator>Robot</dc:creator>
      <dc:date>2025-06-28T11:17:25Z</dc:date>
    </item>
  </channel>
</rss>

