Main Menu

Recent posts

#21
IDNet Help / Re: iDNet and email
Last post by Tacitus - Apr 22, 2026, 17:34:11
Quote from: Simon on Apr 22, 2026, 17:07:28That must be why they say they only support equipment purchased from them.  I don't know why they went with UBOSS as a VoIP provider, as others seem more competitively priced, and are presumably also more user configurable. 
I must admit I can't see why the went with UBOSS.  Voipfone do a white lable service and I would have thought iDNet could have got a good deal if they brought all of their clients over to that service.

Presumably UBOSS also supply the preconfigured TP-Link routers although I find that surprising since it would also include the iDNet part of the setup.  Dunno  🤷
#22
IDNet Help / Re: iDNet and email
Last post by Tacitus - Apr 22, 2026, 17:29:29
Quote from: Tacitus on Apr 22, 2026, 12:44:53No worries Simon.  I've had this stuff going round a round. 
The Mac Mail client is set exactly as it was before with "automatically manage the connection settings"  A quick peek showed there was no authentication set for outgoing.  So much for the automatic management....
I've now input a username and password and so far so good.  I'll give it while to settle down and hopefully she'll not have any more trouble.
I think what may have been happening is that authentication wasn't needed in the past since she would have an iDNet IP address.  That would no longer apply once she moved to Zen, and it now requires authentication.  I naturally assumed no mods would be needed to the Apple Mail client and spent ages doing my head in trying to persuade it to work. Never thought of it needing authentication  :) 
#23
IDNet Help / Re: iDNet and email
Last post by Simon - Apr 22, 2026, 17:07:28
Quote from: Tacitus on Apr 22, 2026, 15:46:46Just one point.  According to iDNet they can't supply the configuration details for Uboss VoIP.  I can believe the ATAs arrive as a sealed box but what happens if you wish to set up your own router?  EG the FritzBox can do VoIP if you input the settings.

That must be why they say they only support equipment purchased from them.  I don't know why they went with UBOSS as a VoIP provider, as others seem more competitively priced, and are presumably also more user configurable.  We've seen from other recent posts on here that fiddling with the Telephony settings in the router can cause problems, and I was even told that I couldn't add numbers to the block list myself without emailing them to IDNet, but that, however, does seem to work with my router.
#24
IDNet Help / Re: iDNet and email
Last post by Tacitus - Apr 22, 2026, 15:46:46
FWIW her move to Zen was faultess.  She was on ADSL so it meant the installation of an ONT and a move to VoIP.  Just in case the existing phone failed to work, she purchased one of the FritzFon handsets to go with the Fritz router. 

The contractor arrived on time and the whole process was faultless.  The only minor niggle was the phone interface was in German, but that was soon sorted. 

I'm still on FTTC and around the same time I had to move to SoGEA and VoIP.  The Broadband part was trouble free but the ATA for the Uboss VoIP service went astray as it had the wrong address.  Once that was sorted everything went OK.

Just one point.  According to iDNet they can't supply the configuration details for Uboss VoIP.  I can believe the ATAs arrive as a sealed box but what happens if you wish to set up your own router?  EG the FritzBox can do VoIP if you input the settings.
#25
IDNet Help / Re: VoIP stopped registering y...
Last post by exxos - Apr 22, 2026, 13:02:20
Quote from: Simon on Apr 21, 2026, 19:55:59We like people who solve their own problems!  :thumb:  ;D

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

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

Quote from: Simon on Apr 21, 2026, 19:55:59Funnily 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  :eek4: so now I made a backup of the backup in case something goes wonky again in the future  :)x

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...

#26
IDNet Help / Re: iDNet and email
Last post by Tacitus - Apr 22, 2026, 12:44:53
Quote from: Simon on Apr 22, 2026, 12:09:24Without wishing to state the bleedin' obvious, is Authentication enabled for both incoming and outgoing mail in her IDNet account settings in her mail client?
No worries Simon.  I've had this stuff going round a round. 
The Mac Mail client is set exactly as it was before with "automatically manage the connection settings"  A quick peek showed there was no authentication set for outgoing.  So much for the automatic management....

I've now input a username and password and so far so good.  I'll give it while to settle down and hopefully she'll not have any more trouble.

Thanks very much Simon.  It really was driving me mad  ;D
#27
IDNet Help / Re: iDNet and email
Last post by Simon - Apr 22, 2026, 12:09:24
Without wishing to state the bleedin' obvious, is Authentication enabled for both incoming and outgoing mail in her IDNet account settings in her mail client?
#28
IDNet Help / iDNet and email
Last post by Tacitus - Apr 22, 2026, 11:54:03
Following her move to Zen, a relative signed up for iDNet's "continuation" email service including spam/malware protection.

However she's been unable to connect using POP3/SMTP using her old credentials- they've remained exactly as before.  Zen say the iDNet servers are regarding her as a spam bot and refuse to connect her.  She can use iDNet webmail via a browser.

Has anyone used this "continuation" email service, or know of anyone who has used it successfully.  My feeling is the iDNet servers are blocking Zen IP addresses.  Nowhere do iDNet make it clear it is a webmail only service so the assumption is there is something wrong with her Mail app settings and endless hours have been wasted trying to sort it......

Any help appreciated  :)
#29
IDNet Help / Re: VoIP stopped registering y...
Last post by Simon - Apr 21, 2026, 19:55:59
We like people who solve their own problems!  :thumb:  ;D

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. 
#30
IDNet Help / Re: VoIP stopped registering y...
Last post by exxos - Apr 21, 2026, 19:28:43
OK SOLVED ?!

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