Ask
Reply
Solution
08-01-2014 10:08 PM - edited 08-01-2014 10:12 PM
I have forwarded the guidance for this router eg MTU at 1500 and port forwarding etc. I have the correct lights on the sure signal - S/N 40134728258.
My download speed is 11.98 with an upload speed of 9.32
I have 3g access for internet on both my phone and my wife's with the suresingal and we can hear callers clearly on my end but we are both muffled and breaking up at their end. My external ip address is 80.95.187.13 which is antrim based in N Ireland. Is their anything I can do for this, I am unable to rung ping results fully as i have a chromebook only.
08-01-2014 11:43 PM
Hi bradenroad,
I've used the same router SScombo before and didn't notice any issues so they are certainly compatible
I assume you have tried the advice in this thread?
Also if you are looking to traceroute or ping from a chromebook the following link may be of use
http://chromespot.com/2011/07/14/tip-of-the-day-how-to-ping-and-tracert-on-chromebook/
09-01-2014 08:45 PM
Thanks for that advice - I have prioritised the lan port for the suresignal on QoS within the router and had MTU at 1500. Ping and tracepath results below. Speedtest this eveing is 9.77 down and 3.1 upload.
crosh> tracepath 80.95.187.13 pid: 9242855E036D38FC58EE02568333865B 1: 192.168.1.6 0.158ms pmtu 1500 1: 192.168.1.1 2.030ms 1: 192.168.1.1 2.022ms 2: 192.168.30.1 2.654ms 3: 80.95.187.13 20.014ms reached Resume: pmtu 1500 hops 3 back 62
crosh> ping 80.95.187.13 pid: D0194FBF296E1A324BA8A4C8965D3396 PING 80.95.187.13 (80.95.187.13) 56(84) bytes of data. 64 bytes from 80.95.187.13: icmp_req=1 ttl=62 time=29.2 ms 64 bytes from 80.95.187.13: icmp_req=2 ttl=62 time=22.8 ms 64 bytes from 80.95.187.13: icmp_req=3 ttl=62 time=72.1 ms 64 bytes from 80.95.187.13: icmp_req=4 ttl=62 time=11.2 ms 64 bytes from 80.95.187.13: icmp_req=5 ttl=62 time=16.5 ms 64 bytes from 80.95.187.13: icmp_req=6 ttl=62 time=10.7 ms 64 bytes from 80.95.187.13: icmp_req=7 ttl=62 time=16.7 ms 64 bytes from 80.95.187.13: icmp_req=8 ttl=62 time=20.7 ms 64 bytes from 80.95.187.13: icmp_req=9 ttl=62 time=10.9 ms 64 bytes from 80.95.187.13: icmp_req=10 ttl=62 time=11.6 ms 64 bytes from 80.95.187.13: icmp_req=11 ttl=62 time=10.8 ms 64 bytes from 80.95.187.13: icmp_req=12 ttl=62 time=7.15 ms 64 bytes from 80.95.187.13: icmp_req=13 ttl=62 time=16.4 ms 64 bytes from 80.95.187.13: icmp_req=14 ttl=62 time=21.1 ms 64 bytes from 80.95.187.13: icmp_req=15 ttl=62 time=12.9 ms 64 bytes from 80.95.187.13: icmp_req=16 ttl=62 time=17.4 ms 64 bytes from 80.95.187.13: icmp_req=17 ttl=62 time=31.1 ms 64 bytes from 80.95.187.13: icmp_req=18 ttl=62 time=14.6 ms 64 bytes from 80.95.187.13: icmp_req=19 ttl=62 time=6.11 ms 64 bytes from 80.95.187.13: icmp_req=20 ttl=62 time=20.2 ms 64 bytes from 80.95.187.13: icmp_req=21 ttl=62 time=12.7 ms 64 bytes from 80.95.187.13: icmp_req=22 ttl=62 time=25.0 ms 64 bytes from 80.95.187.13: icmp_req=23 ttl=62 time=29.2 ms
10-01-2014 12:45 PM
Hi bradenroad,
Please could you post a copy of your Traceroute?
VSS Traceroute command
On a PC:
Click on Start and select Run
Type CMD into the Run box and press enter/click ok
A black box will appear.
In this box type tracert 212.183.133.177 press Enter
Paste the output of this command into your reply.
This will help us get the quickest possible resolution for you.
Thanks
Gemma
10-01-2014 06:44 PM - edited 11-01-2014 12:32 PM
Deleted
11-01-2014 11:36 AM - edited 11-01-2014 12:33 PM
Deleted
11-01-2014 12:33 PM - edited 11-01-2014 12:38 PM
Hi Gemma,
Sorry a Traceroute as requested and latest Ping below
My provider has increased my bandwidth also so I have 17.49 download and 9.45 upload
crosh> tracepath 212.183.133.177 pid: 6CC2E30F6D271C1748A6706BE004592D 1: 192.168.1.6 0.150ms pmtu 1500 1: 192.168.1.1 4.266ms 1: 192.168.1.1 3.997ms 2: 192.168.30.1 3.683ms 3: 192.168.10.1 11.052ms 4: 80.95.187.30 35.442ms 5: gi3-0.br0.heron.bytel.net.uk 56.902ms 6: ae0-1343-xcr1.lnd.cw.net 56.612ms 7: ae0-xcr1.lnt.cw.net 63.525ms 8: vodafone-gw1.cw.net 77.947ms asymm 13
crosh> ping 80.95.187.13 pid: 592CE2142BB49B54F73C042DBB4E80BE PING 80.95.187.13 (80.95.187.13) 56(84) bytes of data. 64 bytes from 80.95.187.13: icmp_req=1 ttl=62 time=12.8 ms 64 bytes from 80.95.187.13: icmp_req=2 ttl=62 time=6.96 ms 64 bytes from 80.95.187.13: icmp_req=3 ttl=62 time=6.48 ms 64 bytes from 80.95.187.13: icmp_req=4 ttl=62 time=8.27 ms 64 bytes from 80.95.187.13: icmp_req=5 ttl=62 time=7.62 ms 64 bytes from 80.95.187.13: icmp_req=6 ttl=62 time=5.94 ms 64 bytes from 80.95.187.13: icmp_req=7 ttl=62 time=5.49 ms 64 bytes from 80.95.187.13: icmp_req=8 ttl=62 time=9.01 ms 64 bytes from 80.95.187.13: icmp_req=9 ttl=62 time=10.7 ms 64 bytes from 80.95.187.13: icmp_req=10 ttl=62 time=7.44 ms 64 bytes from 80.95.187.13: icmp_req=11 ttl=62 time=351 ms 64 bytes from 80.95.187.13: icmp_req=12 ttl=62 time=7.95 ms 64 bytes from 80.95.187.13: icmp_req=13 ttl=62 time=6.12 ms 64 bytes from 80.95.187.13: icmp_req=14 ttl=62 time=5.44 ms 64 bytes from 80.95.187.13: icmp_req=15 ttl=62 time=6.99 ms 64 bytes from 80.95.187.13: icmp_req=16 ttl=62 time=11.3 ms 64 bytes from 80.95.187.13: icmp_req=17 ttl=62 time=18.8 ms 64 bytes from 80.95.187.13: icmp_req=18 ttl=62 time=15.5 ms 64 bytes from 80.95.187.13: icmp_req=19 ttl=62 time=9.17 ms 64 bytes from 80.95.187.13: icmp_req=20 ttl=62 time=9.16 ms 64 bytes from 80.95.187.13: icmp_req=21 ttl=62 time=10.7 ms 64 bytes from 80.95.187.13: icmp_req=22 ttl=62 time=9.22 ms 64 bytes from 80.95.187.13: icmp_req=23 ttl=62 time=8.63 ms 64 bytes from 80.95.187.13: icmp_req=24 ttl=62 time=8.35 ms 64 bytes from 80.95.187.13: icmp_req=25 ttl=62 time=19.8 ms 64 bytes from 80.95.187.13: icmp_req=26 ttl=62 time=6.85 ms 64 bytes from 80.95.187.13: icmp_req=27 ttl=62 time=6.82 ms 64 bytes from 80.95.187.13: icmp_req=28 ttl=62 time=8.12 ms 64 bytes from 80.95.187.13: icmp_req=29 ttl=62 time=5.34 ms 64 bytes from 80.95.187.13: icmp_req=30 ttl=62 time=8.53 ms 64 bytes from 80.95.187.13: icmp_req=31 ttl=62 time=5.73 ms 64 bytes from 80.95.187.13: icmp_req=32 ttl=62 time=6.33 ms 64 bytes from 80.95.187.13: icmp_req=33 ttl=62 time=6.99 ms 64 bytes from 80.95.187.13: icmp_req=34 ttl=62 time=9.47 ms 64 bytes from 80.95.187.13: icmp_req=35 ttl=62 time=8.16 ms 64 bytes from 80.95.187.13: icmp_req=36 ttl=62 time=7.46 ms 64 bytes from 80.95.187.13: icmp_req=37 ttl=62 time=9.07 ms 64 bytes from 80.95.187.13: icmp_req=38 ttl=62 time=7.74 ms 64 bytes from 80.95.187.13: icmp_req=39 ttl=62 time=8.56 ms 64 bytes from 80.95.187.13: icmp_req=40 ttl=62 time=10.0 ms 64 bytes from 80.95.187.13: icmp_req=41 ttl=62 time=5.24 ms 64 bytes from 80.95.187.13: icmp_req=42 ttl=62 time=10.0 ms 64 bytes from 80.95.187.13: icmp_req=43 ttl=62 time=7.24 ms
11-01-2014 04:40 PM
Hi bradenroad,
We need to work out if this issue is with your Sure Signal connection or the receiving ends network.
Please can you make sure that the person at the other end has good coverage.
If this is the case and they’ve tried it in different areas, then the issue will be with your Sure Signal.
When this issue is happening, would it possible for you to try a speed test at the time or immediately after, to see what your upload speed is?
To do this, please go to www.speedtest.net .
Let us know how you get on.
Thanks,
Gemma