Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Clearwire problems with Skype

  • 13-11-2005 1:40pm
    #1
    Closed Accounts Posts: 5


    To all clearwire users (and to tech support if they're looking)

    I have got clearwire BB for 2 weeks now and it's working great, I'm certainly getting the speeds I expect.

    However, I'm not getting a great experience with Skype so far, but I'm not sure if it is my connection or not. Calls to echo123 have a lot of distortion/cutting out etc, so I'm worried that it is my connection. I don't know how the wireless environment should affect skype.

    How is everyone else's experience of using Skype or other VOIP services with Skype, I would be interested to know!

    I am in Sandyford.

    Thanks,

    Jonathan


Comments

  • Closed Accounts Posts: 5 jd-ie


    Seems to be a little better now actually, when I tried a SkypeOut mobile call


  • Registered Users, Registered Users 2 Posts: 5,259 ✭✭✭Yggr of Asgard


    Call Customer Service and get them to "tweak" your connection for VOIP, certainly worked for me.


  • Registered Users, Registered Users 2 Posts: 8 mcgenius


    I vaguely remember reading about clearwire in the US and how they blocked some VOIP services from competing companies (eg Vonage in the US). I'm not sure if that's what they're up to in Ireland too....http://news.com.com/Vonage+says+Clearwire+interfered+with+VoIP+calls/2100-7352_3-5657386.html

    Looking around I came across one or two other bits....

    http://blog.pff.org/archives/2005/04/voip_blocking_t.html

    And perhaps most tellingly from the Skype forum...

    http://forum.skype.com/viewtopic.php?p=183408


  • Closed Accounts Posts: 2,630 ✭✭✭Blaster99


    They're not blocking VoIP in Ireland.

    Your problems are probably because of packet loss or very high latency. In my [somewhat limited] experience packet loss is the main killer of VoIP.


  • Registered Users, Registered Users 2 Posts: 10,846 ✭✭✭✭eth0_


    The do not block VOIP. I was using Skypeout earlier this evening.

    More than likely your packet loss is so great that skype isn't worth using, as has been the case for a few days now on Clearwire :(


  • Advertisement
  • Closed Accounts Posts: 79 ✭✭sisyphus


    Haven't had any problems myself. I use VoIpCheap (voipcheap.co.uk) for calling land lines in Ireland, Google Talk or Skype for calling friends pc's, and haven't had any problems so far. There was one incident the other night, when my ping response time shot to 400-500 ms to my gateway for some reason, but this only lasted 20-30 mins, and is now fine again.


  • Registered Users, Registered Users 2 Posts: 10,846 ✭✭✭✭eth0_


    Lucky you, i'm getting pings of over 1000ms to boards.ie now :(


  • Closed Accounts Posts: 79 ✭✭sisyphus


    Doesn't make sense eth0. Where are you living exactly? I'm on Haddington Road, and am connecting to FitzWilliam Square. Here's my response times to boards at present:
    Pinging www.boards.ie [82.195.136.250] with 32 bytes of data:
    
    Reply from 82.195.136.250: bytes=32 time=79ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=65ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=38ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=59ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=71ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=78ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=65ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=75ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=78ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=43ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=58ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=137ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=107ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=101ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=87ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=50ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=33ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=49ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=78ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=64ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=33ms TTL=60
    
    Ping statistics for 82.195.136.250:
        Packets: Sent = 21, Received = 21, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 33ms, Maximum = 137ms, Average = 68ms
    
    Pinging ftp.heanet.ie [193.1.193.64] with 32 bytes of data:
    
    Reply from 193.1.193.64: bytes=32 time=54ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=45ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=48ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=102ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=46ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=53ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=48ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=44ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=68ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=61ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=64ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=62ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=132ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=110ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=58ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=79ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=65ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=84ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=45ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=56ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=29ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=66ms TTL=59
    Reply from 193.1.193.64: bytes=32 time=77ms TTL=59
    
    Ping statistics for 193.1.193.64:
        Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 29ms, Maximum = 132ms, Average = 65ms
    
    Pinging 85.134.128.1 with 32 bytes of data:
    
    Reply from 85.134.128.1: bytes=32 time=33ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=96ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=82ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=51ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=50ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=78ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=72ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=104ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=44ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=43ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=68ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=124ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=34ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=45ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=65ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=72ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=87ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=85ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=58ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=43ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=93ms TTL=255
    Reply from 85.134.128.1: bytes=32 time=63ms TTL=255
    
    Ping statistics for 85.134.128.1:
        Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 33ms, Maximum = 124ms, Average = 67ms
    


    Latency is relatively high to boards, ftp.heanet.ie and default gateway, as you can see (Also jumps up and down a good bit), but nowhere near 1000 ms!! That's just nuts!!
    Have you been onto the support team about it?


  • Registered Users, Registered Users 2 Posts: 10,846 ✭✭✭✭eth0_


    I live 2 blocks behind Camden St, near the Meath St hospital.

    They told me i'm on the Harolds X transmitter.

    It looks to me, from the traceroutes, like they don't have the backhaul for all the extra customers who've jumped on board the past few weeks.

    I should be on the 'pro' package, perhaps i'm not. What package are you on?

    Yes, I have contacted support, last Thursday in fact. They ask me for my modem serial number. I don't see what good that is. They've already replaced my modem since I started using Clearwire. They still haven't been able to answer my question as to what package i'm *on*, since they went and replaced the one I signed up with originally with a different package!
    Nor have they provided me with an invoice like I asked.

    Worrying.


  • Registered Users, Registered Users 2 Posts: 10,846 ✭✭✭✭eth0_


    See, it's back to normal now, at 7am when there's not many using the service.

    ping ftp.heanet.ie
    PING ftp.heanet.ie (193.1.193.64): 56 data bytes
    64 bytes from 193.1.193.64: icmp_seq=0 ttl=58 time=57.776 ms
    64 bytes from 193.1.193.64: icmp_seq=1 ttl=58 time=32.166 ms
    64 bytes from 193.1.193.64: icmp_seq=2 ttl=58 time=36.161 ms
    64 bytes from 193.1.193.64: icmp_seq=3 ttl=58 time=30.897 ms
    64 bytes from 193.1.193.64: icmp_seq=4 ttl=58 time=34.840 ms
    64 bytes from 193.1.193.64: icmp_seq=5 ttl=58 time=35.040 ms
    64 bytes from 193.1.193.64: icmp_seq=6 ttl=58 time=43.147 ms
    64 bytes from 193.1.193.64: icmp_seq=7 ttl=58 time=34.616 ms
    64 bytes from 193.1.193.64: icmp_seq=8 ttl=58 time=42.674 ms
    64 bytes from 193.1.193.64: icmp_seq=9 ttl=58 time=46.858 ms
    ^C
    --- ftp.heanet.ie ping statistics ---
    10 packets transmitted, 10 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 30.897/39.417/57.776/7.848 ms

    ping www.boards.ie
    PING www.boards.ie (82.195.136.250): 56 data bytes
    64 bytes from 82.195.136.250: icmp_seq=0 ttl=59 time=55.912 ms
    64 bytes from 82.195.136.250: icmp_seq=1 ttl=59 time=59.956 ms
    64 bytes from 82.195.136.250: icmp_seq=2 ttl=59 time=38.471 ms
    64 bytes from 82.195.136.250: icmp_seq=3 ttl=59 time=38.425 ms
    64 bytes from 82.195.136.250: icmp_seq=4 ttl=59 time=46.484 ms
    64 bytes from 82.195.136.250: icmp_seq=5 ttl=59 time=42.632 ms
    64 bytes from 82.195.136.250: icmp_seq=6 ttl=59 time=36.614 ms
    64 bytes from 82.195.136.250: icmp_seq=7 ttl=59 time=42.907 ms
    64 bytes from 82.195.136.250: icmp_seq=8 ttl=59 time=38.567 ms
    64 bytes from 82.195.136.250: icmp_seq=9 ttl=59 time=37.994 ms
    ^C
    --- www.boards.ie ping statistics ---
    10 packets transmitted, 10 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 36.614/43.796/59.956/7.662 ms


  • Advertisement
Advertisement