Digital Voice issues

[JonnyManc]

Hi

Recently migrated from another isp for my fttp 500mb with digital Voice.

Fttp is working great, but having issues with maintaining digital Voice.

After a couple of weeks faffing, I got it sorted (registering phone etc) at it was ok, but this week callers can't hear me, nor can I hear them.... The phone rings and there is a dial tone.....

Any ideas guys?

Thanks

[JimM11]

@Gelert5 They are rolling out thick and fast.... And to add long running post now, what a difference a year makes.!

Just a quick note, although still back 4 FW updates, event logging is currently about the page per day that's been the norm did soft restart day 86 wife nagging, and up 11 day's so far. Certainly way quicker web manager page's but sure that's what you get when you clear out the log's.

[pst99]

Yep, appears I got it too (r2.68.18-R-1303195-PROD-83002).

My experience is the same, I've not had to reset to restore voice since the newer updates started rolling out...and the last two firmware updates needed no intervention from me to reconnect extenders etc.

I have had 1 anecdotal report from the missus of a call where she could hear the caller but they couldn't hear her...but they hung up, called back and everything was golden....so for now I'm chalking that one as 'random' - that was on the previous firmware (r2.68.16-R-1296172-PROD-83002)

Phil

[Andy_65]

I haven't had the issue since before Christmas, but before these recent firmware updates I had gone up to 60 days without the problem occurring and as short as 7 days.  It's very early days in my opinion,  if I don't have any further occurrences of it by the end of May then that'll be when l'll take it as being fixed. 

[sp1949]

I'm still on 16-R  since the 29/12. Digital Voice has been exemplary since "new handsets" sent out and set up on 26th Dec. Longest working time since I was changed from BT to EE., Dec/2023 or Jan/2024. Still no verbal update!!!

[SMJ001]

OK, was working OK for a while, but this morning (19-02-2025) modem stuck in a solid green with the occasional white flash (polling resilience I guess)  mode. No Broadband, Ethernet or WiFi as it's stuck in a boot recycle. System reset button not doing anything so I'm giving it a very long power-down at the moment.

Currently reverted to data only on a Draytek 2762, so no VoIP.

[SMJ001]

Update to above

Reboot successful after 10 or so attempts. Only logged error is a DSL drop for 2 minutes or so just before 0900 this morning. Seemed it could not recover from that by itself.

Don't know if there was a firmware upgrade to cause it but now on r2.68.18-R-1303195-PROD-83002

See how long it lasts this time.

[Gelert5]

@SMJ001 

r2.68.18-R-1303195-PROD-83002 was rolled out to me on 11th February.

[JimM11]

@Gelert5 And all there was EE staff member posted but did not mention which/what FW so have linked the post just incase there is another rapid change all to do with the Parental controls side so the 16 to 18 version may have been the hold. Just so hard to pin it all down. Rollout has recommenced with user's getting the 18 version FW, posted again this morning.

Information: Smart Hub Parental Controls not working properly with some browsers - Page 5 - The EE C...

[SMJ001]

Update to 19/02/2025

Appologies, this is going to be a bit of a moan after continued frustration of moving from BT and analogue POTS to EE & DV.

After r2.68.18-R-1303195-PROD-83002 the SH31B will not reboot reliably after a web interface reboot, power off, or a commanded remote reboot (which I have no control over). The hub appears to be unable to recover from a DSL line drop without a power off too. During reboot it gets stuck in a 10sec Green, white flash, 5 sec green then off sequence until powered off again. The reset switch appears to have no function in changing the likely-hood of a successful boot either, only a time period without power seems to work. The current reboot success is about 5% and several hours are wasted baby sitting the device waiting in hope that after leaving the power off with no connections for 15 minutes or so, the next attempted 'power on' is successful, . This is particularly frustrating as when DV malfunctions, the first solution suggested is to reboot the hub and phone adapter, so the whole sorry sequence begins again. The lack of persistent logging or a syslog facility across reset & reboot does not help either.

The 'lock-in' with BT/EE modems and DV ensures the frustration remains - at least I have a spare Draytek that is used while I wait for the SH31B to boot successfully to get on line, but no DV of course. Unfortunately, the 'land line' number is a must due to family reasons. Does anyone know if a Draytek xxxxV with VoIP would work with the EE infrastructure? 

[JimM11]

@SMJ001 The version off FW you have posted does seem to still be the latest at present and no one has posted any different yet, take it that when you connect the draytek back on the line it appears to work fine, is there anyway you can look at that to see if there is any potential line issue, also when you set the EE aside and power it on, are you waiting to see it go steady orange light that indicates now it will look like connection is going to be possible on the DSL line. The latest FW fixing whatever EE thinks ie one does appear to be more stable DV operation at least not seeing postings up against that, but will agree it does have a lot to answer for whatever they did and are trying to fix.

As for getting any other VOIP style router to work there is NO way, BT/EE and like all other ISP's doing digital landline are keeping the info closely guarded so it makes it that EE router HAS to be used, BT Smarthub2 may work off the bat but not sure if EE would have to do anything to set it up for use with the number.

I have only rebooted the router once since the FW update and that was a day after it was done, but did notice that after EE applied the update then HALF off my network was gone. Got it semi stable now but i am on FF since NOV so TOO many DSL reset's would not have to worry incase it DSLAM'd the router.