Results 1 to 5 of 5

Thread: sip.voipwelcome.com - 408 REQUEST TIMEOUT

  1. #1
    Join Date
    Feb 2007
    Posts
    270

    Default sip.voipwelcome.com - 408 REQUEST TIMEOUT

    partial tracert
    Code:
    Tracing route to sip.voipwelcome.com [74.52.58.50]
    over a maximum of 30 hops:
    ....
     3     5 ms     4 ms     4 ms  loopback0.gw8.dca5.alter.net [137.39.2.73]
     4     4 ms     4 ms     4 ms  0.ge-7-2-0.xt2.dca5.alter.net [152.63.40.14]
     5     4 ms     4 ms     4 ms  0.so-7-0-0.br2.dca5.alter.net [152.63.34.105]
     6     5 ms     5 ms     5 ms  204.255.169.186
     7    13 ms     6 ms     6 ms  ae-0.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.17]
     8    50 ms    50 ms    45 ms  as-1.r20.dllstx09.us.bb.gin.ntt.net [129.250.3.42]
     9   268 ms   236 ms   216 ms  po-1.r02.dllstx09.us.bb.gin.ntt.net [129.250.2.154]
    10    49 ms    49 ms    49 ms  xe-4-4.r03.dllstx09.us.ce.gin.ntt.net [157.238.225.6]
    11    48 ms    49 ms    49 ms  te7-1.dsr01.dllstx3.theplanet.com [70.87.253.2]
    12    52 ms    49 ms    49 ms  76.fd.5746.static.theplanet.com [70.87.253.118]
    13   271 ms    98 ms   251 ms  vl1.car02.dllstx6.theplanet.com [12.96.160.23]
    14  zeus.voipwelcome.com [74.52.58.50]  reports: Destination protocol unreachable.
    
    Trace complete.

  2. #2
    VOIPoRay Guest

    Default Re: sip.voipwelcome.com - 408 REQUEST TIMEOUT

    You get the "Destination protocol unreachable" because we're blocking ICMP packets at the server. so pings should always fail and running tracert will be misleading.


    If you're seeing a 408 Timeout in your Call Logs, then there are a few different possible reasons for it... In order to give you an accurate account of what's happening, we'll need a few more details. Is this on a call to your ATA or from it? and what did the caller experience? (fast busy, system error message, etc)

  3. #3
    Join Date
    Feb 2007
    Posts
    270

    Default Re: sip.voipwelcome.com - 408 REQUEST TIMEOUT

    Quote Originally Posted by VOIPoRay View Post
    You get the "Destination protocol unreachable" because we're blocking ICMP packets at the server. so pings should always fail and running tracert will be misleading.


    If you're seeing a 408 Timeout in your Call Logs, then there are a few different possible reasons for it... In order to give you an accurate account of what's happening, we'll need a few more details. Is this on a call to your ATA or from it? and what did the caller experience? (fast busy, system error message, etc)
    It started yesterday evening, my Nokia E51 could not register (home ISP)
    I tried
    Xlite, same thing (Xlite did say "408 REQUEST TIMEOUT") (home ISP)
    tracert, "zeus.voipwelcome.com [74.52.58.50] reports: Destination protocol unreachable."
    FWIW, the tracert in the 1st post were from my work ISP
    Check your PM in a few minutes for a wireshark cap

  4. #4
    VOIPoNorm Guest

    Default Re: sip.voipwelcome.com - 408 REQUEST TIMEOUT

    I've just set up a SIP profile on Nokia N82 using sip.voipwelcome.com and was able to complete Internet calls.

    Regards,
    Norm

  5. #5
    Join Date
    Feb 2007
    Posts
    270

    Default Re: sip.voipwelcome.com - 408 REQUEST TIMEOUT

    from VoIPo Support Team:
    This should be taken care of now, we were adjusting some DNS records and such that caused a couple of issues while updating.

    Let us know if this problem persists.

    Regards,
    VoIPo Support Team
    support@voipo.com
    http://support.voipo.com
    Thanks to VoIPo Support Team both E51 and Xlite registered fine now

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •