User comments on ISPs
  >> BT Broadband


Register (or login) on our website and you will not see this ad.


Pages in this thread: 1 | [2] | >> (show all)   Print Thread
Standard User ukhardy07
(knowledge is power) Sat 28-May-16 21:42:36
Print Post

Re: BT infinity 1 re-syncing


[re: DYMO] [link to this post]
 
In reply to a post by DYMO:
yes ggremlin i have swapped over with my daughters router both hh5 mine was a 5a hers is a 5b,i have read that there are better modems out there do you think that getting one would improve things


Getting a different modem is not necessary, the homehub does not drop 15 times in an hour unless there is a definite line fault / poor wiring internally (does not seem to be the case) / electrical interference in the property (again does not seem to be the case).

BT are very poor at accepting a fault and getting engineers out in my experience. Is the landline all clear or is there audible noise on the line. You stand a better chance reporting a voice fault a lot of the time, as this impacts the broadband, usually where there are broadband issues there is fuzz on the line which BT have to resolve.
Standard User RobertoS
(elder) Sat 28-May-16 23:56:20
Print Post

Re: BT infinity 1 re-syncing


[re: DYMO] [link to this post]
 
Ahhh, in their 80s.

Maybe one of these.

(Note the icon on the post).

Kindness isn't going to cure the world of all its awfulness but it's a good place to begin. Daisy Ridley.
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 59500/14989kbps @ 600m. - BQM
Standard User DYMO
(regular) Sun 29-May-16 12:43:48
Print Post

Re: BT infinity 1 re-syncing


[re: ukhardy07] [link to this post]
 
hi ukhardy07...the line is clear and as you say BT are very poor at accepting a fault and getting engineers out,the last time i contacted them they said there was a line fault and they would monitor it for 72hrs when questioned why as a fault was present he said it was procedure
so 72hrs later they said line was clear ?????


Register (or login) on our website and you will not see this ad.

Standard User DYMO
(regular) Sun 29-May-16 12:46:06
Print Post

Re: BT infinity 1 re-syncing


[re: RobertoS] [link to this post]
 
haha Robertos yes there is one next door but has been there for some time lol
Standard User MHC
(sensei) Sun 29-May-16 13:04:28
Print Post

Re: BT infinity 1 re-syncing


[re: DYMO] [link to this post]
 
A motor characteristic can suddenly change. If for example the brushes are wearing, when they get fully worn down there could be arcing, or if one partially break, the same can happen. Do not discount it, just because it has been there for years.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

M H C


taurus excreta cerebrum vincit
Standard User DYMO
(regular) Sat 04-Jun-16 20:32:11
Print Post

Re: BT infinity 1 re-syncing


[re: MHC] [link to this post]
 
Hi anyone any idea what is happening here?

00:56:41, 04 Jun. (36505.330000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.100000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.090000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.080000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.070000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.060000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.050000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.040000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.030000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.020000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.010000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36505.000000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.990000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.980000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.970000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.960000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.950000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.940000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.930000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.920000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.910000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.900000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.890000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.880000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.870000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.860000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.850000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.840000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.830000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.820000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.810000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.800000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.790000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.780000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.770000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.760000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.750000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.740000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.730000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.720000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.710000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.700000) CWMP: Initializing transaction for event code 2 PERIODIC
00:56:40, 04 Jun. (36504.680000) CWMP: Initializing transaction for event code 2 PERIODIC
Standard User epyon
(experienced) Sun 05-Jun-16 06:44:04
Print Post

Re: BT infinity 1 re-syncing


[re: DYMO] [link to this post]
 
the hub is sending a termination request ?

BT Infinity 2 - 80/20
BT Infinity 2 Speedtest *Huawei HG635*
BT Mobile - 4G
BT Mobile 4G Speedtest *Huawei PLK-L01*
Standard User ukhardy07
(knowledge is power) Sun 05-Jun-16 10:50:29
Print Post

Re: BT infinity 1 re-syncing


[re: DYMO] [link to this post]
 
That's just a code 2 periodic session which is standard when the hub contacts the BT server, often to check for new firmwares etc.

As for the line, there does appear to be a significant issue.
Standard User DYMO
(regular) Sun 05-Jun-16 11:55:11
Print Post

Re: BT infinity 1 re-syncing


[re: epyon] [link to this post]
 
ok thanks both
Pages in this thread: 1 | [2] | >> (show all)   Print Thread

Jump to