In reply to a post by Pheasant:

I really dislike ISP supplied routers with a passion.

Likewise, but if the world of POTS moves to ISP supplied routers, then replacing is going to be hard. Those of us on this forum are likely to be aware, and may use alternative VoIP suppliers, but the majority will probably go with the ISP supplied.

interestingly the Virgin Media hub 3 in modem mode still supports their propriatory VoIP.

I've seen that and it is similar to what I am seeing.

However, the Business Hub is the older SmartHub 1 - there may be some commonality of software modules if they are from the same supplier.

The one that works is actually a Smart Hub 2- consumer which is the one users claim has issues. Have it available but not fitted so that when a new Business Hub arrives I can check that and see, then if 35Mbps again, put the SH2 in place to confirm still 50, what I don't want is for the SH2 to update.

I'll be checking the firmware version on the new hub before install and then first off will be a speed test. And then wait to see if it updates.

No doubt yes. I'd expect in the fullness of time, that some folks may cotton on to the fact that an independent VOIP provider could be a good thing (cheaper, not tied-in with CP so more 'portable', etc, etc).

I suppose it doesn't really matter as long as the CP doesn't either lock-in or block / make it punitive or technically awkward for their end users to run another third party VOIP over the top of their service.

Did you ever get 50Meg up on testing, directly into the back of the ONT from your PC/laptop?

Edited by Pheasant (Mon 12-Apr-21 12:57:01)

Never managed to get and try it, however the BT Tech did on Friday And he left his Cat5e cable behind!.

I run two other VOIP services along side the BT cloud - but that is a networked base and handset. They all play happily together.

In reply to a post by MHC:

Never managed to get and try it, however the BT Tech did on Friday And he left his Cat5e cable behind!.

Minor compensation for the hassle

Definitely then your business hub at fault if BT chap could get 50 out of the box. Not a profile issue.

Edited by Pheasant (Mon 12-Apr-21 13:05:43)

Tbh, they're not as bad as they used to be, and to say you get the SH2 free with some BT packages, that's not bad!

Nice new business hub arrived today.

Powered up and checked firmware version without connecting to the ONT - an older version than my current hub.

I did a full set of tests: Wireless and Wired to the hub. BT Wholesale Test, Fast.com, TBB, speedtest.net - so 8 tests, on my original hub, the Residential Hub, and new (earlier firmware) business hub.

In every case the difference between wired and wireless was negligible and could be ignored. On downstream the speed seen from each tester was consistent irrespective of the hub and always 300Mbps and above (Fast gave one at 320Mbps).

However, with upstream, the original business hub gave 35Mbps on BT and around 32Mbps on the others. Moving to the Residential Hub saw the speeds jump right up with 51-52 on BT and 48-50 on the others. Then changed to the new Business hub - straight back down to the low 30s.

It appears that the Business hub is the problem ... at present, BT are unsure on how to progress as we know the profile and service are correct and 50Mbps is achievable.


Another attempt late to get my PC talking to the ONT.


Any other suggestions?

Well it’s purely a BT business hub firmware bug/issue. Totally up to them to resolve. In the meantime you’re owed pro-rated compensation for all the days your service is under delivering. Not much probably in the grand scheme of things, but it may help to focus minds if you remind them.

It would appear at least on the surface that it’s the same/related speed profile bug in the firmware of the business hub as they were known to have mid last year in their residential hubs.

Presumably this would affect other business hub customers, as it did residential hub customers although (again presumably) the outright numbers may be lower and hence this issue is not widely realised nor indeed been addressed. In any event BT support teams need to escalate the issue to the appropriate folk internally to resolve.