vicidial.org

can someone help me? im having issues with my vicidial web dialer associated with zoiper it started last thursday... other websites are good but very high pings for vicidial which causes 3 second delays in audio restarted my pc twice nothing happens my ISP tech went here yesterday but there is no trouble found on their end

here is the sample of my ping test
C:\Users\jazzmine>ping google

Pinging google[120.28.26.104] with 32 bytes of data:
Reply from 120.28.26.104: bytes=32 time=43ms TTL=56
Reply from 120.28.26.104: bytes=32 time=43ms TTL=56
Reply from 120.28.26.104: bytes=32 time=43ms TTL=56
Reply from 120.28.26.104: bytes=32 time=43ms TTL=56

Ping statistics for 120.28.26.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 43ms, Average = 43ms

C:\Users\jazzmine>ping youtube

Pinging youtube [120.28.5.177] with 32 bytes of data:
Reply from 120.28.5.177: bytes=32 time=33ms TTL=56
Reply from 120.28.5.177: bytes=32 time=29ms TTL=56
Reply from 120.28.5.177: bytes=32 time=31ms TTL=56
Reply from 120.28.5.177: bytes=32 time=32ms TTL=56

Ping statistics for 120.28.5.177:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 33ms, Average = 31ms

C:\Users\jazzmine>ping 166.78.102.104

Pinging 166.78.102.104 with 32 bytes of data:
Reply from 166.78.102.104: bytes=32 time=1421ms TTL=50
Reply from 166.78.102.104: bytes=32 time=1388ms TTL=50
Reply from 166.78.102.104: bytes=32 time=1363ms TTL=50
Reply from 166.78.102.104: bytes=32 time=1430ms TTL=50

Ping statistics for 166.78.102.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1363ms, Maximum = 1430ms, Average = 1400ms

C:\Users\jazzmine>

as you can see the 166.78.102.104 is the vicidial web dialler pls help!

run a traceroute on the site

C:\Users\jazzmine>tracert 166.78.102.104

Tracing route to 166.78.102.104 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms 192.168.254.254
2 27 ms 27 ms 27 ms 10.188.44.219
3 26 ms 27 ms 27 ms 10.188.45.158
4 28 ms 28 ms 38 ms 112.198.191.1
5 31 ms 28 ms 30 ms 120.28.10.106
6 57 ms 57 ms 64 ms 120.28.4.222
7 65 ms 60 ms 77 ms ix-8-3-2-445.tcore2.SVW-Singapore.as6453. net [18
0.87.15.9]
8 268 ms 266 ms 267 ms if-2-2.tcore1.SVW-Singapore.as6453. net [180.87.1
2.1]
9 272 ms 271 ms 271 ms if-6-2.tcore2.TV2-Tokyo.as6453. net [180.87.12.11
0]
10 270 ms 269 ms 269 ms if-2-2.tcore1.TV2-Tokyo.as6453. net [180.87.180.1
]
11 * 272 ms * if-9-2.tcore2.PDI-Palo-Alto.as6453. net [180.87.1
80.17]
12 273 ms 273 ms 272 ms if-11-3.tcore2.CT8-Chicago.as6453. net [66.198.14
4.58]
13 281 ms 273 ms 274 ms 64.86.79.38
14 1547 ms 1536 ms 1565 ms 10.25.0.69
15 1565 ms 1637 ms 1595 ms czi1-tunnel4.ord1.rackspace. net [50.56.6.163]
16 1606 ms 1555 ms 1547 ms coreb-core5.ord1.rackspace. net [50.56.6.131]
17 269 ms 270 ms 269 ms aggr1501a-2-core5.ord1.rackspace. net [50.56.6.11
7]
18 1646 ms 1604 ms 1564 ms 166.78.102.104

Trace complete.

Help me out please!

my setup is vici dial VERSION: 2.7-370c BUILD: 130508-2255 and zoiper 3.6.25251 32 bit i'm experiencing 4 - 5 seconds audio delay like if you say hello to your customer he/she can hear it after 4 - 5 seconds. and here's what i've found after 2:00 EST the ping will go down to 300 ms and there will be no delays in audio can anyone help?

it seems like no one is replying in this forum...

Well, what kind of answer are you expecting to see, especially with issues not related at all to ViciDial ?!
Besides, multiple threads for the same issue are not nice.

Anyway, two things you could do, just common sense:
1) Ping other server in the same network as the vicidial server to rule out it's not the server itself
2) Find out with your internet provider to the vicidial server what is happening

BTW, a quick test from home if helps:

Code: Select all

C:\>ping -t 166.78.102.104

Pinging 166.78.102.104 with 32 bytes of data:
Reply from 166.78.102.104: bytes=32 time=111ms TTL=47
Reply from 166.78.102.104: bytes=32 time=113ms TTL=47
Reply from 166.78.102.104: bytes=32 time=116ms TTL=47
Reply from 166.78.102.104: bytes=32 time=127ms TTL=47
Reply from 166.78.102.104: bytes=32 time=126ms TTL=47
Reply from 166.78.102.104: bytes=32 time=116ms TTL=47
Reply from 166.78.102.104: bytes=32 time=112ms TTL=47
Reply from 166.78.102.104: bytes=32 time=121ms TTL=47
Reply from 166.78.102.104: bytes=32 time=112ms TTL=47
Reply from 166.78.102.104: bytes=32 time=127ms TTL=47
Reply from 166.78.102.104: bytes=32 time=151ms TTL=47
Reply from 166.78.102.104: bytes=32 time=117ms TTL=47
Reply from 166.78.102.104: bytes=32 time=112ms TTL=47
Reply from 166.78.102.104: bytes=32 time=116ms TTL=47
Reply from 166.78.102.104: bytes=32 time=114ms TTL=47
Reply from 166.78.102.104: bytes=32 time=115ms TTL=47
Reply from 166.78.102.104: bytes=32 time=114ms TTL=47
Reply from 166.78.102.104: bytes=32 time=133ms TTL=47
Reply from 166.78.102.104: bytes=32 time=111ms TTL=47
Reply from 166.78.102.104: bytes=32 time=122ms TTL=47
Reply from 166.78.102.104: bytes=32 time=110ms TTL=47
Reply from 166.78.102.104: bytes=32 time=117ms TTL=47

Ping statistics for 166.78.102.104:
    Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 110ms, Maximum = 151ms, Average = 118ms
Control-C
^C

do you have the link for the other server that you are talking about?

days24 wrote:do you have the link for the other server that you are talking about?

you obviously don't understand basic networking, I can try to explain what okli means:
If you got an other server next to 166.78.102.104 then try to ping that one.
but both okli and me have no problem with slow response from the server, I too get about 120ms. Its probably the connection you are connecting from that are slow.
or maybe temporary slow responses from a gateway on the route.
because on the traceroute you posted it seams like on hop 15 (10.25.0.69) there is where you started to get unusually slow responses.

contact your providers (both for the server connection and the connection you were at when this happened), this is not related to vicidial at all

try installing a new network card.