Main Menu

Recent posts

#51
Of course, if your box doesn't like seeing Caller ID numbers starting +44, it probably won't work.

(A&A get this right. You can select either +44 or 0 as incoming number prefix. It wouldn't affect me, as I would be able to manipulate the caller ID inside Asterisk.)
#52
Quote from: Simon on Jan 14, 2026, 18:39:58I just tried it.  To my surprise, the call blocker was powered by the router, but clearly the system doesn't like it as it's not letting me receive calls.  It either blocks them, or the phone doesn't ring then the call goes straight to voicemail.  So I think it's probably best left alone. 
You might need to make sure that the router is sending out the right format of callerid. Many phones will cope with different variants, especially the US type "bellcore".

You'll want one that's labelled BT or UK. Again, on a Grandstream ATA, the options look like this:

#53
Quote from: Simon on Jan 14, 2026, 10:09:20I didn't think it could.  Does the router port provide power, like a PSTN socket does?
It should. A few tens of milliamps.

On a Grandstream the config looks like this:



and the bottom one can be set to either 20mA or 30mA.
#54
Quote from: nowster on Jan 14, 2026, 00:20:38Can't the new router power your call blocker device just like your phone line did?

I just tried it.  To my surprise, the call blocker was powered by the router, but clearly the system doesn't like it as it's not letting me receive calls.  It either blocks them, or the phone doesn't ring then the call goes straight to voicemail.  So I think it's probably best left alone. 
#55
Quote from: nowster on Jan 14, 2026, 00:20:38Can't the new router power your call blocker device just like your phone line did?

I didn't think it could.  Does the router port provide power, like a PSTN socket does?
#56
Can't the new router power your call blocker device just like your phone line did?
#57
Yes, that's definitely a more complex set up than mine. 

The one thing that does concern me a bit is call blocking.  I'd had over 70 scam / spam numbers blocked in my old CPR Call Blocker, but that was powered by the phone line, and has no AC power ability, so it's had to go.  I've yet to see if any of those numbers are still active (I suspect not), but the call blocking function seems clunky at best.  IDNet have said I'd need to email them each time I want to block a number, but there is a facility within the TP Link VX230v router settings to add numbers to a block list.  I don't know what reason there might be for this not to work, and for me to have to contact IDNet, which could soon become tedious.
#58
Dad switched over to VoIP (A&A) yesterday.

It's a bit more complex than your setup, of course:

  • The Raspberry Pi 4 which is acting as router is now also running a VoIP exchange software called Asterisk.
  • The extension wiring is now connected to a Grandstream HT812v2 ATA using an RJ11 to RJ11 cable (from DSL modem) into an old OpenReach NTE5 with split VDSL faceplate. That provides the RJ11 socket (for DSL) and also punchdown terminals for the extension wiring with a BT socket on the front. The internals of the faceplate also provide the ring capacitor.
  • Switching over from PSTN was done by wiring the extensions into the new socket on Sunday, then using an old modem's BT-to-RJ11 cable to connect from existing OpenReach socket to new VoIP socket, with instructions given to my sister to replace one labelled RJ11 cable with a different RJ11 cable when the switch had completed.

There were a few minor hiccoughs:

  • I'd asked for a particular date for the port, but because I'd gone through the One Touch Switch process, that didn't stick, so the port was arranged for a week before I'd requested.
  • The Grandstream ATA has developed an internal fault which means there's a buzz on the lines. I suspect a dead capacitor in the DC-DC converter inside. It's still within the Christmas free returns period so I've already got and configured a replacement which I'll fit next week.
  • My understanding of Asterisk's PJSIP syntax was incorrect, so outgoing calls weren't working. "PJSIP/trunkname/01632960960" is not the same as (the correct) "PJSIP/01632960960@trunkname"
  • The actual port didn't happen until about 16:55, which made us think it wasn't going to succeed.

Caller ID works fine, and was something we didn't get by default on the IDNet PSTN service. I've even got it matching some incoming numbers to display the names.

I've set up a few short codes for dialling friends and relatives in Ireland and Australia. I also have set up an IAX trunk back over VPN to my own place, which allows a few novelties:

123 gets the Pat Simmons speaking clock. https://github.com/paulseward/asterisk-tim
160 gets a "Dial A Disc" which is my own private radio station automation system.

So, the cost of the phone line has gone down from £220 per year (inc VAT) to £22 per year (inc VAT). The £400 Ecoflow Delta 2 (1kWh) battery pack to keep it all running when the power goes out doesn't factor into it.  :whistle:

From tests the battery will keep things going for a minimum of 2½ days and has options to charge from solar power or a car battery as well as the mains. It came in useful today when the electrician turned off the fusebox for an hour to wire in an electric shower.
#59
;D

I'm just waiting for IDNet to come back to me to confirm my number withheld setting.  The only slight niggle with this is that things like that have to be done by them, rather than a setting in the router, but once it's done it's done.  If I'd know it would be this simple I'd have done it ages ago and saved a bit of money as it's cheaper than the PSTN line, with all calls included. 
#60
You'll be telling me your bread fell butter side up next :)x