- Welcome to IDNetters Forums.
Recent posts
#31
IDNet Help / Re: VoIP stopped registering y...
Last post by exxos - Apr 21, 2026, 19:28:43OK SOLVED ?!
I changed Bound Interface: from LAN to ANY_WAN and connected right away. I never even touched that setting before.
I changed Bound Interface: from LAN to ANY_WAN and connected right away. I never even touched that setting before.
#32
IDNet Help / VoIP stopped registering yeste...
Last post by exxos - Apr 21, 2026, 18:19:40It's been working fine for months. Yesterday I changed the No Answer Time from 10 to 20 seconds. May or may not be coincidental, but the phone hasn't worked since. Calls to our landline from a mobile beep a couple of times and drop; outbound calls do similar.
In the router "Telephone Numbers" page there's a grey circle with a cross — VoIP isn't registering. Router log says "every IP of the domain has been tried, but we didn't find the correct one!" — retrying every 30s, all failing.
IDNet support has asked me to delete and re-add the config, done that (and rebooted), no change.
A few other things I've checked:
DNS resolves sbc.insmartcloud.com to 83.137.183.171 consistently (AdGuard and Google resolvers both return the same single IP, no failover).
Ping to that IP gets nothing back — but I know that might just be ICMP filtering at the SBC.
Checked from another UK line on a different ISP — same ping timeout.
check-host.net shows the IP unreachable from 54 global test nodes (again, could just be ICMP filtering).
Tracert dies at Cogent (149.14.250.234) before reaching the destination network.
The IP belongs to DRD Communications plc / QUDO platform (ASN 34967), not IDNet directly — I'm guessing it's their wholesale VoIP upstream.
Internet is otherwise fine.
Anyone else seeing this, or any ideas what to try next?
Thanks,
Chris
In the router "Telephone Numbers" page there's a grey circle with a cross — VoIP isn't registering. Router log says "every IP of the domain has been tried, but we didn't find the correct one!" — retrying every 30s, all failing.
IDNet support has asked me to delete and re-add the config, done that (and rebooted), no change.
A few other things I've checked:
DNS resolves sbc.insmartcloud.com to 83.137.183.171 consistently (AdGuard and Google resolvers both return the same single IP, no failover).
Ping to that IP gets nothing back — but I know that might just be ICMP filtering at the SBC.
Checked from another UK line on a different ISP — same ping timeout.
check-host.net shows the IP unreachable from 54 global test nodes (again, could just be ICMP filtering).
Tracert dies at Cogent (149.14.250.234) before reaching the destination network.
The IP belongs to DRD Communications plc / QUDO platform (ASN 34967), not IDNet directly — I'm guessing it's their wholesale VoIP upstream.
Internet is otherwise fine.
Anyone else seeing this, or any ideas what to try next?
Thanks,
Chris
#33
IDNet Help / Re: IdNet Down?
Last post by peasblossom - Apr 16, 2026, 10:59:06This is a useful site to c+p any url into to check. It'll say when a site is having problems too.
downforeveryoneorjustme
downforeveryoneorjustme
#34
IDNet Help / Re: IdNet Down?
Last post by Bill - Apr 14, 2026, 16:44:19Haven't seen any issues here, but I haven't been using it much this afternoon.
#35
IDNet Help / Re: IdNet Down?
Last post by zappaDPJ - Apr 14, 2026, 15:57:11Something doesn't seem right but I'm not sure what the problem is. I've been getting sporadic search failures and the inability to download files from certain sites this afternoon. I thought it was WiFi related but perhaps not.
#37
IDNet Help / IdNet Down?
Last post by Arctophile - Apr 14, 2026, 13:37:16Is it just me or is IdNet's website and email down.
Broadband is OK
Broadband is OK
#38
IDNet Help / Re: Move to SoGEA & VoIP
Last post by Tacitus - Apr 13, 2026, 11:35:10Just to wrap this up, it appears the problem was at iDNet's end. Phoned them this morning and Chloe fiddled with the settings and it all now works. Thankfully I don't need to fiddle with port forwarding. The Fritz is a decent router but for someone used to Drayteks the UI is rather confusing.
Thank you both for the suggestions.
Thank you both for the suggestions.
#39
IDNet Help / Re: Move to SoGEA & VoIP
Last post by nowster - Apr 13, 2026, 11:28:10Quote from: Tacitus on Apr 12, 2026, 19:12:53If all else fails I shall have to move the telephony to Voipfone.You might find A&A more reliable and cheaper. (£12 porting cost, £1.80/month rental)
Even if you don't, their support page might be helpful for examples:
https://support.aa.net.uk/VoIP_Phones_-_Grandstream_HT8xx
Note that if the ATA has two ethernet ports, you can by default only access the admin pages when connected to the "inside" interface.
#40
IDNet Help / Re: Move to SoGEA & VoIP
Last post by Tacitus - Apr 12, 2026, 19:12:53@Nowster: Whilst rummaging round the Internet for help on UBoss, I did find the Voipfone settings for a Fritz. These were helpful, but I still need the actual UBoss settings from iDNet so I'll give them a ring in the morning.
I have tried to get to the UI of the ATA - Grandstream 801v2. It is visible on the network so I tried to use the IP to access the UI but was locked out. "Server busy - try later". Can't see anything in the router settings that might explain this.
If all else fails I shall have to move the telephony to Voipfone. The Uboss is only a one month contract so not a great loss, albeit annoying. They have a decent reputation and appear to have knowledge of the FritzBox.
As I said in my original post, I'm not keen on the TP-Link and would rather keep the Fritz if I can since it will also cope with full fibre if that ever appears round here.
I have tried to get to the UI of the ATA - Grandstream 801v2. It is visible on the network so I tried to use the IP to access the UI but was locked out. "Server busy - try later". Can't see anything in the router settings that might explain this.
If all else fails I shall have to move the telephony to Voipfone. The Uboss is only a one month contract so not a great loss, albeit annoying. They have a decent reputation and appear to have knowledge of the FritzBox.
As I said in my original post, I'm not keen on the TP-Link and would rather keep the Fritz if I can since it will also cope with full fibre if that ever appears round here.