VoIP stopped registering yesterday

[exxos]

It'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

[exxos]

OK SOLVED ?!

I changed Bound Interface: from LAN to ANY_WAN and connected right away. I never even touched that setting before. 

[Simon]

We like people who solve their own problems!   

Funnily enough, assuming this is UBOSS, I did the same with my TP Link VX230v, except I changed the ring time to 30 seconds.  I then couldn't receive incoming calls, which rang once at the callers end then disconnected, and I got a weird message which I can't now remember, when I tried to make a call.  I phoned IDNet and somehow my line had been 'blocked'.  Chloe reset it there and then, but other than adding a couple of numbers to the block list, I've not touched any router settings since. 

[exxos]

We like people who solve their own problems!   

I always jump to forums as a last resort normally emailing technical support is also the last resort   

Randomly changing settings until it works sometimes pays off.. Other times it makes things incredibly worse 

Funnily enough, assuming this is UBOSS, I did the same with my TP Link VX230v, except I changed the ring time to 30 seconds.  I then couldn't receive incoming calls, which rang once at the callers end then disconnected, and I got a weird message which I can't now remember, when I tried to make a call.  I phoned IDNet and somehow my line had been 'blocked'.  Chloe reset it there and then, but other than adding a couple of numbers to the block list, I've not touched any router settings since. 

Strange.

The only thing I did was change the answer time out from 10 seconds to 20 seconds. Didn't work since.

Chloe just kept saying delete and put settings back in.. But these were in the advance box not the general settings for the phone number anyway. So it wasn't helping

Possible when I scrolled down the advanced settings box, if the selected default just happen to select that drop down box when I scrolled, it could have changed the setting without me noticing. But I've been caught out many times like that in the past. So if I saw that and in any doubt, I would have just cancelled and started over, so no risk. Either that it something else messed up. No way to tell.

The annoying thing is that I added some numbers to block just a few hours afterwards so did a firmware backup of the route.. Unknowingly that it had overwritten the backup I had from once again  so now I made a backup of the backup in case something goes wonky again in the future 

In any case I think it's good to have this information on a public forum, in case it catches someone else out in the future...