Recent Posts

Pages: [1] 2 3 ... 10
1
Thanks for the links.  Should have been more thorough in my searching......
 
The need for an ATA adaptor or a router with one built in is what prompted this post.  My existing modem is showing signs of age and it would make sense for any new one to have a built in ATA function.  There seems to be relatively few around at present:  Draytek, Fritzbox and the latest BT smart hub are the only ones I've seen, although no doubt there will be several more over the next few years.

I'm on O2 which is the only viable signal round here, although some people have had success with Vodafone.  Three is non existent although claiming an excellent signal, whilst EE barely reaches one bar on a good day....   I suspect these latter are only transmitting 4G, whereas O2 are still doing 2G/3G.  Once they drop this, it will become a mobile not-spot and reliant on voice over WiFi, which won't work in a power cut.  Isn't progress wonderful :)

I would advise against getting a router with built-in ATA (VoIP) as it limits your choices and may not be as well tested or supported as a purpose built device.  A router is becoming a jack of all trades and potentially a master of none. 

Getting something standalone is probably the better option in my opinion, that also means you can swap out your router as and when required without worrying about the phone aspect.  Something like a DECT VoIP base station and a couple of handsets or an ATA if you wish to plug in a corded phone.
2
IDNet Help / Re: FTTC - line drops
« Last post by Gary on Today at 09:39:26 »
To close this out here is what I found, in case this is helpful to anyone else.

After lots of logging the evidence points firmly that the problem being related to the DSL physical link.  The Vigor130 would drop to TRAINING and then restart the DSL session (SHOWTIME) causing the router PPPoE session to drop.  DSL link errors didn't point to a clear cause other than what you might expect from copper cable. Modem was connected to the test socket with a DSL filter, no phone or internal cabling.  Diagnostics and online checker show that my DSL cab is Huawei Broadcom based.

My previous fault call with Draytek didn't highlight any known issues.
Support tickets with IDNET revealed no obvious faults being recorded.

I took a punt and bought an old Openreach Huawei EchoLife HG612 modem, flashed it with the recommended custom firmware.  Been running DSLstats on it, and the link has remained up for several weeks.  Frequency response has some odd notches in it but it seems that the HG612 copes better with this line than the Vigor130.

Link speeds are slightly different now - higher DL, lower UL (by about 10%), response times remain excellent, and stability is far better now.

What I conclude from this is that if your modem has a different chipset to the DSL cab and you are having trouble then it is worth trying different equipment.  I had hoped that IDNET would have knowlege like this, and ideally to be able to lend kit for testing and verification.  In fairness they did suggest trying different equipment, but since this is a stock answer from many sources it doesn't carry the weight that perhaps it should, and for most people this will be an unreasonable request to just try something out.

Ultimately fault is a problem with the Draytek Vigor130 not working reliably with my line - back where I started!  New fault call to be logged, as a certified product it should work.

Nevertheless, I now have a working service so £20 well spent, even if it did take 4 months to work out.
The Vigor 130 if on a ECI cab should use the second modem code and vectoring should be turned off via telnet. That stops the dropout and improves throughput.

https://community.plus.net/t5/Fibre-Broadband/Draytek-vigor-130-Can-t-hold-a-connection-for-long/td-p/1541232/page/2
3
Thanks for the links.  Should have been more thorough in my searching......
 
The need for an ATA adaptor or a router with one built in is what prompted this post.  My existing modem is showing signs of age and it would make sense for any new one to have a built in ATA function.  There seems to be relatively few around at present:  Draytek, Fritzbox and the latest BT smart hub are the only ones I've seen, although no doubt there will be several more over the next few years.

I'm on O2 which is the only viable signal round here, although some people have had success with Vodafone.  Three is non existent although claiming an excellent signal, whilst EE barely reaches one bar on a good day....   I suspect these latter are only transmitting 4G, whereas O2 are still doing 2G/3G.  Once they drop this, it will become a mobile not-spot and reliant on voice over WiFi, which won't work in a power cut.  Isn't progress wonderful :)
I was on O2 - rural location - and very happy too. However they are firmware locked when it comes to VoWifi. EE only gives me one or two bars on the meter, I don't know exactly what that is displaying but I think it is 2G strength until something else is used. However VoLTE is still there and 4G is good enough. With VoWifi as well it's a good compromise. I'm not sure about 2G - I have a feeling it is going to be with us a lot longer and hopefully the 4G /5G network will expand more in the next couple of years.
4
Networking & Routers / Re: Billion 8800NL R2 - vulnerable?
« Last post by nowster on Yesterday at 19:25:27 »
My parents now have a 8800NL R2, but it is actually running the most recent firmware. (I got them it after their previous modem was zapped by a lightning strike.)

However, it has no net connectivity other than internal as it's being used in PPPoE Bridge mode, and a Raspberry Pi (with lots of firewall rules, and a small screen used for status reports) is what actually terminates the link. As the fastest they can connect is less than 5Mbps, the RasPi is more than adequate to the job.

They also have a backup system consisting of a mini-router and a USB 4G modem.
5
There is a lengthy discussion on this subject here:-
https://www.idnetters.co.uk/forums/index.php/topic,33961.0.html
and more recently here:-
https://www.idnetters.co.uk/forums/index.php/topic,34020.0.html

Thanks for the links.  Should have been more thorough in my searching......

The general assumption in ISP land is that service providers will supply ATA adapters (if required as many routers have the function built in) FOC. We have yet to see how IDNet will be doing this.
 
The need for an ATA adaptor or a router with one built in is what prompted this post.  My existing modem is showing signs of age and it would make sense for any new one to have a built in ATA function.  There seems to be relatively few around at present:  Draytek, Fritzbox and the latest BT smart hub are the only ones I've seen, although no doubt there will be several more over the next few years.

On the basis that I do not want another box to manage (or for my wife to try to manage if/when I drop off my perch) I have instead swapped our mobiles over to BT which allows VoLTE that does work even though our 2G signal is poor. It also gives us VoWifi if needed - these are non-BT specific phones. I think that will have to do and at least something will work when we get our localised power cuts. If towers go down - well tough I guess. Get in the car and head for the hills. :dunno:

I'm on O2 which is the only viable signal round here, although some people have had success with Vodafone.  Three is non existent although claiming an excellent signal, whilst EE barely reaches one bar on a good day....   I suspect these latter are only transmitting 4G, whereas O2 are still doing 2G/3G.  Once they drop this, it will become a mobile not-spot and reliant on voice over WiFi, which won't work in a power cut.  Isn't progress wonderful :)
6
There is a lengthy discussion on this subject here:-

https://www.idnetters.co.uk/forums/index.php/topic,33961.0.html

and more recently here:-

https://www.idnetters.co.uk/forums/index.php/topic,34020.0.html

The general assumption in ISP land is that service providers will supply ATA adapters (if required as many routers have the function built in) FOC. We have yet to see how IDNet will be doing this.

On the basis that I do not want another box to manage (or for my wife to try to manage if/when I drop off my perch) I have instead swapped our mobiles over to BT which allows VoLTE that does work even though our 2G signal is poor. It also gives us VoWifi if needed - these are non-BT specific phones. I think that will have to do and at least something will work when we get our localised power cuts. If towers go down - well tough I guess. Get in the car and head for the hills. :dunno:

7
Broadband, Internet & General Computer News & Discussion / iDNet and VOIP
« Last post by Tacitus on Yesterday at 14:29:31 »
Has anyone any inside info on how iDNet propose to deal with the upcoming switch off of POTS?  I see they're offering SOGEA lines and business VOIP, but I couldn't find anything on whether they propose to offer voip to domestic users.  Admittedly iDNet are mainly a business provider but they must have a fair number of purely domestic users for  Broadband and voice (POTS). 

At present their POTS call charges on a PAYG basis include a call set up charge of 9.6p which is ridiculous when most of the voip providers are charging purely on a minute basis.  For example voipfone charge 1.2p/min with a minimum charge of 1 minute.  I believe Port 5060 charge even less. 

With the POTS switch off due to be complete by 2025, now might be a good time to decide on how to deal with it, perhaps with Broadband from iDNet and a separate VOIP provider such as Sipgate or Voipfone.
8
IDNet Help / Re: FTTC - line drops
« Last post by Simon on Yesterday at 10:36:18 »
In fairness to IDNet, if they can't see a problem on the network then I guess the first port of call is always to look at the user's equipment, but I get what you're saying about it being a stock reply.  They have sent out test routers in the past, so not sure why they wouldn't be doing so now.
9
IDNet Help / Re: FTTC - line drops
« Last post by jrw on Yesterday at 09:39:48 »
To close this out here is what I found, in case this is helpful to anyone else.

After lots of logging the evidence points firmly that the problem being related to the DSL physical link.  The Vigor130 would drop to TRAINING and then restart the DSL session (SHOWTIME) causing the router PPPoE session to drop.  DSL link errors didn't point to a clear cause other than what you might expect from copper cable. Modem was connected to the test socket with a DSL filter, no phone or internal cabling.  Diagnostics and online checker show that my DSL cab is Huawei Broadcom based.

My previous fault call with Draytek didn't highlight any known issues.
Support tickets with IDNET revealed no obvious faults being recorded.

I took a punt and bought an old Openreach Huawei EchoLife HG612 modem, flashed it with the recommended custom firmware.  Been running DSLstats on it, and the link has remained up for several weeks.  Frequency response has some odd notches in it but it seems that the HG612 copes better with this line than the Vigor130.

Link speeds are slightly different now - higher DL, lower UL (by about 10%), response times remain excellent, and stability is far better now.

What I conclude from this is that if your modem has a different chipset to the DSL cab and you are having trouble then it is worth trying different equipment.  I had hoped that IDNET would have knowlege like this, and ideally to be able to lend kit for testing and verification.  In fairness they did suggest trying different equipment, but since this is a stock answer from many sources it doesn't carry the weight that perhaps it should, and for most people this will be an unreasonable request to just try something out.

Ultimately fault is a problem with the Draytek Vigor130 not working reliably with my line - back where I started!  New fault call to be logged, as a certified product it should work.

Nevertheless, I now have a working service so £20 well spent, even if it did take 4 months to work out.
10
Networking & Routers / Re: Billion 8800NL R2 - vulnerable?
« Last post by robinc on May 12, 2021, 06:05:45 »
OK - finally bit the bullet. The only disturbing bit was after hitting Continue on the Upgrade page I wound up with a page of raw html in the Billion frame.

Odd - left it for a while and nothing happened so hit refresh and came back to router login page  - from there on all went as expected as it takes you through the bits it wants in a wizard. The only bit I had to change was the DHCP range and the http port for the interface which defaults to port 80.
Pages: [1] 2 3 ... 10

Any information and links published in the forum are posted in good faith, but the forum staff and
owners cannot and do not accept responsibility for the content and accuracy of external websites.