Main Menu

Recent posts

#31
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.
#32
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.
#33
;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. 
#34
You'll be telling me your bread fell butter side up next :)x
#35
Well, it all seems to be up and running.  Caller Display working as normal.  Names are displayed. 
#36
I took the plunge and my PSTN line is being switched over to UBOSS VoIP tomorrow.  Well, actually, today now. 

Not sure how I'll know when it's actually switched.  The 'Phone' light is on on my TP Link VX230v router, which apparently means 'The SIP account is registered successfully', but the ported phone number hasn't appeared in the router settings yet, and the PSTN line was still connected as of about an hour ago.  I assume this is a manual process and someone at IDNet will flick a switch and send the configuration to my router?
#37
Networking & Routers / Re: Asus RT-AX57 router drivin...
Last post by nowster - Jan 10, 2026, 23:44:12
I use dedicated WiFi APs rather than using a router with WiFi attached.

For up to 100Mbps, I've been using GL-iNet GL-SFT1200 travel routers set to be dedicated WiFi APs. If you're lucky you can get them for under £30 each. They're currently £33 on Amazon.
#38
Networking & Routers / Re: Asus RT-AX57 router drivin...
Last post by robinc - Jan 09, 2026, 08:14:34
Anyhoo, I have swapped the 2.4 Ghz to Channel 11 as that is marginally less crowded in the immediate area according to LinSSID
#39
Networking & Routers / Re: Asus RT-AX57 router drivin...
Last post by Arctophile - Jan 08, 2026, 16:06:09
Try performing a hard reset.

https://www.asus.com/support/faq/1039078/
(Expand the model list to confirm that this is the correct method for your device.)

Before resetting make a note of all your personal settings.

Then completely reconfigure the device manually.
Do not export/import your existing configuration, you may end up re-importing the original problem.

#40
Networking & Routers / Asus RT-AX57 router driving me...
Last post by robinc - Jan 07, 2026, 17:24:29
Moved house in September - first time on FTTP.
Ordered ASUS RT-AX57 from Idnet at the same time.
Once it had all settled in I was getting 100 down and 20 up (in round numbers)
Some of my machines can work with 5 Ghz, some are dual and some only 2.4 Ghz.
It has now reached the stage where I have to hard reboot the router about once a week to keep the speed up above 45 for download. My old Billion 8800 on ADSL ran for months without needing a soft restart.
The slowdown is always accompanied by connection problems to various sites.
Firmware is on auto update.
Any ideas on where to start looking for what may be causing this please?