Ask
Reply
Solution
06-10-2010 04:31 PM - last edited on 14-07-2014 04:50 PM by Jenny
This issue presents the following symptoms:
For version 1 Sure Signal (the one with four lights on the front):
For version 2 Sure Signal (the one with 3 lights on the front):
For version 3 Sure Signal (the plug in version):
Troubleshooting steps:
Check that your broadband connection meets our minimum requirements.
Please run the broadband speed checker.
If your connection fails any part of the test, this indicates an issue with your Internet Service Provider (ISP) and you’ll need to contact them to discuss this.
Your connection speed will vary throughout the day, so we recommend running it at various times to get an accurate reading.
To ensure the Sure Signal broadcasts at the correct frequency, it sends and receives small amounts of data to a Network Time Protocol Server hosted by ourselves. If these packets of data take longer than 240ms to make a round-trip, the accuracy can no longer be ensured and so the Sure Signal will automatically stop broadcasting and light four will go out.
Check for planned maintenance.
Planned maintenance can cause periods of downtime, so check the forum for any planned maintenance. If there is, this will be announced at the top of the Sure Signal forum.
Reset your Sure Signal:
The Sure Signal will be back online in around 1 hour.
Configure your Router Firewall.
The IP address and ports used for NTP (Network Time Protocol) synchronisation are listed below. You may need these to configure the correct firewall settings on your router.
This step isn’t usually necessary, but it may help if you’re using a complex network (such as a corporate or office LAN), or a complex router.
We recommend contacting your ISP or router manufacturer directly for detailed instructions on exactly how to change your router settings. Alternatively, select your router make and model over at http://portforward.com and follow the default guide there.
Destination IP addresses:
Please note that in the list of IP addresses above, the notation "212.183.131.128/26"means the entire range of IP addresses between 212.183.131.128 and 212.183.131.191
Perform a PathPing to our server.
In order to check if the Sure Signal's able to communicate with our NTP server, a PathPing can be performed as a test. In order to do this, you'll need to open the command prompt in Windows as follows:
Once you're in the command prompt, type in PathPing 212.183.133.181. This will perform a trace route to the NTP server and will show you the route it took to get there. One of the columns will display packet loss, if this occurs before hitting our server, you'll need to contact your ISP for further assistance.
If you've completed all the troubleshooting steps above and not identified the cause of the issue, your Sure Signal may be faulty. Please post in this thread and we can look into it further.
Thanks,
Jenny
Solved! Go to best answer.
15-01-2014 03:38 PM - edited 15-01-2014 05:15 PM
Hello
serial number 21224717989 version 1
the sure signal stopped working a few days ago after a lont internet outage (2 hours), presented with only light 1 flashing.
I have done a little troubleshooting and have now manged to get to light 1 and 2 solid.
how is it looking from your end?
Internet speed >5 Mbps ping normally <55ms.
pathping
C:\WINDOWS\system32>pathping 212.183.133.181
Tracing route to 212.183.133.181 over a maximum of 30 hops
0 XPS-M133064BIT.int.hillblock.com [192.168.1.104]1 WRT54GL [192.168.1.251]2 192.168.1.2503 losubs.subs.dsl5.wh-man.zen.net.uk [62.3.83.10]4 no-dns-yet-62-3-86-29.zen.co.uk [62.3.86.29]5 ge-2-0-0-0.cr1.wh-man.zen.net.uk [62.3.80.49]6 ge-3-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.45]7 ldngw1.arcor-ip.net [195.66.224.209]8 85.205.116.149 * * *Computing statistics for 200 seconds...Source to Here This Node/LinkHop RTT Lost/Sent = Pct Lost/Sent = Pct Address0 XPS-M133064BIT.int.hillblock.com [192.168.1.104]0/ 100 = 0% |1 1ms 0/ 100 = 0% 0/ 100 = 0% WRT54GL [192.168.1.251]0/ 100 = 0% |2 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.2501/ 100 = 1% |3 44ms 2/ 100 = 2% 1/ 100 = 1% losubs.subs.dsl5.wh-man.zen.net.uk [62.3.83.10]0/ 100 = 0% |4 45ms 1/ 100 = 1% 0/ 100 = 0% no-dns-yet-62-3-86-29.zen.co.uk [62.3.86.29]0/ 100 = 0% |5 46ms 1/ 100 = 1% 0/ 100 = 0% ge-2-0-0-0.cr1.wh-man.zen.net.uk [62.3.80.49]1/ 100 = 1% |6 54ms 2/ 100 = 2% 0/ 100 = 0% ge-3-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.45]0/ 100 = 0% |7 54ms 2/ 100 = 2% 0/ 100 = 0% ldngw1.arcor-ip.net [195.66.224.209]98/ 100 = 98% |8 --- 100/ 100 =100% 0/ 100 = 0% 85.205.116.14
Trace complete.
Can you see the sure signal from your end?
Thanks in advance
IAn
FIXED
Came back about an hour later and it is working OK
Don't you just hate it when that happens
Ian
02-10-2014 11:52 AM
EE are launching WiFi Calling soon. Maybe that's the answer.
02-10-2014 01:34 PM
Hi everyone,
Apologies, the link has now been updated.
Please see here, for the most recent information on this.
Thanks,
Sarah
02-10-2014 06:24 PM
02-10-2014 07:02 PM
Come on Sarah. The link is still dead and giving an "unexpected error" message. We need a resolution to this or at least an update and estimated fix time.
Thanks.
05-10-2014 08:14 AM
13-10-2014 12:08 PM
Here are my tracert results for the two ip addresses previously mentioned:
Tracing route to cluster4.vap.vodafone.co.uk [212.183.133.177]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Vigor.router [192.168.161.1]
2 32 ms 31 ms 32 ms losubs.subs.dsl1.th-lon.zen.net.uk [62.3.84.17]
3 16 ms 17 ms 16 ms ge-2-1-0-125.cr2.th-lon.zen.net.uk [62.3.84.229]
4 21 ms 16 ms 17 ms ldngw1.arcor-ip.net [195.66.224.209]
5 17 ms 20 ms 17 ms 85.205.0.86
6 * * * Request timed out.
7 * * * Request timed out.
And this:
Tracing route to 212.183.133.181 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Vigor.router [192.168.161.1]
2 32 ms 32 ms 32 ms losubs.subs.dsl1.th-lon.zen.net.uk [62.3.84.17]
3 32 ms 33 ms 32 ms ge-2-1-0-127.cr2.th-lon.zen.net.uk [62.3.84.237]
4 34 ms 33 ms 34 ms ldngw1.arcor-ip.net [195.66.224.209]
5 34 ms 34 ms 33 ms 85.205.0.93
6 * * * Request timed out.
I've been in touch with my ISP (Zen) and they have checked this. The two 85.205.0.* addresses belong to Vodafone. So it looks like everything is fine in terms of connectivity until the SureSignal gets to the Vodafone network.
Please can you confirm that there is a problem at Vodafone with the the SureSignal servers?
14-10-2014 01:23 PM
14-10-2014 03:23 PM
Sarah,
My Sure Signal serial number is 21818505568
16-10-2014 03:12 PM
Hi simon_perkins,
I can see a move of location was picked up, but hadn't completed.
I've rectified this and pushed through a resync.
Please reset your Sure Signal, wait up to six hours and then reset any phones struggling to connect.
Visual voicemail is something we've never offered, but there are many apps available for this.
We don't currently have any news about Wi-Fi calling.
Hi Rx7aiii,
The light sequence you've given indicates that the Sure Signal isn't transmitting.
Please check the ports are like this:
Hi JulieBuckmaster,
Please follow the troubleshooting steps here.
Thanks,
Ian
17-10-2014 01:58 PM
Ian,
My Sure Signal is still not working.
Is the lack of acess past 85.205.0.* on the tracert a red herring or does it really indicate a problem?