Welcome to Vodafone Community
It may well come to that, seems a shame we are caught in the middle, I have been with Vodafone for ages now but currently due to no network coverage (I live at TN22 3SH which by no means is in the middle of nowhere), it may be time to move. Just got a new i-phone 6 as well, that will be an interesting in contract conversation, still I reckon "Goods not fit for purpose" should kybosh that!!
@ssizen Apologies for the delay in getting back to you.
I can see your Sure Signal has made a successful connection with our server on 6 November 2016 at 1.05pm.
If you're still having trouble, please can you confirm your IP address, as you mentioned in your first post that it changed.
Ok may be help for any other poor sod like me who has spent weeks on this, TP-Link said enable Full-cone NAT, this did NOT work and actually caused the VOIP phone to stop working but as a last resort I then disabled IGMP Proxy and now I have the SS3 working as it should.
Not sure why, MTU is 1480 as default for info
Thanks all for the help given
Red herring, worked for a day or so and back to normal now, no connection, still 5 phones with no signal, not much use to me here so will look for a supplier who can provide network coverage.
Hi I have been reading your posts with interest, i to have been on the vodafone / BT merry-go-round trying to resolve my VR2600 > VSS problem for over 10 days now. Did you need to purchase a new router of have you stumbled on a fix. Any steer in the right direction would be greatly appreciated.
Ended up being a new router, everyone just blamed each other, more the fault is the shocking signal we have round here and we are by no means out in the sticks. Will look for a new company upon renewal with better coverage
It is important to report all failed SureSignal V3 using the links below to:
BBC's Watchdog: https://ssl.bbc.co.uk/programmes/b006mg74/contact
Trading Standards: Call them on 0345 4 040506
Vodafone CEO: http://www.ceoemail.com - (Search Vodafone UK)
Please take a look at our Sure Signal Troubleshooting thread. If this doesn’t resolve your query, please post your reply either below, or in the relevant thread, together with the details requested, including the following information.
VSS Traceroute command
On a PC:
This will help us get the quickest possible resolution for you.
My VSS v3 stopped working on 13th Feb 2017...no changes to internet connection or router. BT blame Vodafone, Vodafone blame BT blocking VPN traffic.
Boss who is on BT and has a sure signal also stopped working at same time (lives next door to the business with the other failed VSS). Other clients who are on BT do not have the issues, so believe its not a general BT issue.
Tracing route to 126.96.36.199 over a maximum of 30 hops
1 90 ms 104 ms 65 ms Vigor.router [192.168.1.253]
2 35 ms 34 ms 34 ms host81-148-96-1.in-addr.btopenworld.com [188.8.131.52]
3 35 ms 35 ms 34 ms 184.108.40.206
4 35 ms 41 ms 35 ms 220.127.116.11
5 35 ms 35 ms 36 ms 18.104.22.168
6 38 ms 36 ms 41 ms 22.214.171.124
7 36 ms 76 ms 115 ms acc1-10gige-0-7-0-5.l-far.21cn-ipp.bt.net [126.96.36.199]
8 36 ms 36 ms 35 ms core4-te0-10-0-26.faraday.ukcore.bt.net [188.8.131.52]
9 35 ms 37 ms 36 ms host213-121-193-183.ukcore.bt.net [184.108.40.206]
10 34 ms 35 ms 38 ms t2c3-et-8-1-0-0.uk-lon1.eu.bt.net [220.127.116.11]
11 35 ms 39 ms 36 ms 166-49-211-254.eu.bt.net [18.104.22.168]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Sure Signal serial number: 43160511556
Download: 12.20Mbps / Upload: 1.72Mbps
Thanks, however I took it home and it worked fine. I then brought it back in to the office this morning and worked fine. If you would have checked the sync logs you would have seen a successful connection a few times since Wednesday.
Lets hope the resync you've done doesnt break it.