Elegir servidor - VoIP.ms Wiki

Elegir servidor

From VoIP.ms Wiki

Jump to: navigation, search
VoIP.ms servers

Contents

Elegir un Servidor

VoIP.ms le ofrece la posibilidad de conectarse a diferentes servidores, pero ¿cuál es el que debe elegir? Es común pensar que se debe elegir el servidor más cercano a su localidad, sin embargo esto no es necesario en la mayoría de las veces. Si usted está en Estados Unidos, cualquier servidor en EEUU le debe dar un buen resultado en latencia y calidad. También es de utilidad saber que hay una herramienta que le puede ayudar a seleccionar el mejor servidor a usar, este normalmente se llama "ping", el cual le provee la latencia entre usted y el servidor, así usted opcionalmente puede elegir específicamente el servidor que le provea una menor latencia.

Nota: Tenga en cuenta que es posible que algunos servidores no estén disponibles para que su número DID se utilice como POP (Punto de presencia) en la sección "Administrar DID". 
      Asegúrese de que su dispositivo SIP / IAX y su número de teléfono apunten al mismo servidor.


IPs

  • Canada
    • Montreal 1, QC (montreal.voip.ms) 192.175.96.73
    • Montreal 2, QC (montreal2.voip.ms) 192.175.96.74
    • Montreal 3, QC (montreal3.voip.ms) 192.175.96.68
    • Montreal 4, QC (montreal4.voip.ms) 67.205.74.179
    • Montreal 5, QC (montreal5.voip.ms) 192.175.96.69
    • Montreal 6, QC (montreal6.voip.ms) 192.175.96.70
    • Montreal 7, QC (montreal7.voip.ms) 192.175.96.71
    • Montreal 8, QC (montreal8.voip.ms) 192.175.96.72
    • Montreal 9, QC (montreal9.voip.ms) 67.205.74.184
    • Montreal 10, QC (montreal10.voip.ms) 67.205.74.187
    • Toronto 1, ON (toronto.voip.ms) 158.85.70.148
    • Toronto 2, ON (toronto2.voip.ms) 158.85.70.149
    • Toronto 3, ON (toronto3.voip.ms) 158.85.70.150
    • Toronto 4, ON (toronto4.voip.ms) 158.85.70.151
    • Toronto 5, ON (toronto5.voip.ms) 184.75.215.106
    • Toronto 6, ON (toronto6.voip.ms) 184.75.215.114
    • Toronto 7, ON (toronto7.voip.ms) 184.75.215.146
    • Toronto 8, ON (toronto8.voip.ms) 184.75.213.210
    • Toronto 9, ON (toronto9.voip.ms) 158.85.70.154
    • Toronto 10, ON (toronto10.voip.ms) 158.85.70.158
    • Vancouver 1, BC (vancouver.voip.ms) 162.213.157.220
    • Vancouver 2, BC (vancouver2.voip.ms) 162.213.157.117
    • Vancouver 3, BC (vancouver3.voip.ms) 162.213.157.82
  • Estados Unidos
    • Atlanta 1, GA (atlanta.voip.ms) 75.127.65.130
    • Atlanta 2, GA (atlanta2.voip.ms) 209.217.224.50
    • Chicago 1, IL (chicago.voip.ms) 208.100.39.52
    • Chicago 2, IL (chicago2.voip.ms) 208.100.39.53
    • Chicago 3, IL (chicago3.voip.ms) 208.100.39.54
    • Chicago 4, IL (chicago4.voip.ms) 208.100.39.55
    • Chicago 5, IL (chicago5.voip.ms) 50.31.115.149
    • Chicago 6, IL (chicago6.voip.ms) 50.31.115.150
    • Chicago 7, IL (chicago7.voip.ms) 50.31.115.151
    • Dallas, TX (dallas.voip.ms) 158.85.149.162
    • Dallas 2, TX (dallas2.voip.ms) 158.85.149.163
    • Denver 1, CO (denver.voip.ms) 23.239.211.90
    • Denver 2, CO (denver2.voip.ms) 64.27.52.226
    • Houston, TX (houston.voip.ms) 173.193.85.18
    • Houston 2, TX (houston2.voip.ms) 173.193.85.19
    • Los Angeles 1, CA (losangeles.voip.ms) 96.44.149.186
    • Los Angeles 2, CA (losangeles2.voip.ms) 96.44.149.202
    • Los Angeles 3, CA (losangeles3.voip.ms) 64.188.6.162
    • Los Angeles 4, CA (losangeles4.voip.ms) 64.188.6.170
    • New York 1, NY (newyork.voip.ms) 72.251.239.196
    • New York 2, NY (newyork2.voip.ms) 72.251.239.205
    • New York 3, NY (newyork3.voip.ms) 72.251.239.206
    • New York 4, NY (newyork4.voip.ms) 72.251.239.207
    • New York 5, NY (newyork5.voip.ms) 23.29.136.28
    • New York 6, NY (newyork6.voip.ms) 23.29.136.29
    • New York 7, NY (newyork7.voip.ms) 23.29.136.38
    • New York 8, NY (newyork8.voip.ms) 23.29.136.40
    • San Jose, CA (sanjose.voip.ms) 23.246.247.146
    • San Jose 2, CA (sanjose2.voip.ms) 23.246.247.147
    • Seattle 1, WA (seattle.voip.ms) 50.23.160.53
    • Seattle 2, WA (seattle2.voip.ms) 50.23.149.166
    • Seattle 3, WA (seattle3.voip.ms) 50.23.160.54
    • Tampa, FL (tampa.voip.ms) 162.254.144.173
    • Tampa 2, FL (tampa2.voip.ms) 162.254.144.176
    • Tampa 3, FL (tampa3.voip.ms) 23.111.187.139
    • Tampa 4, FL (tampa4.voip.ms) 23.111.166.202
    • Washington 1, DC (washington.voip.ms) 208.43.234.226
    • Washington 2, DC (washington2.voip.ms) 208.43.234.227
  • Internacional
    • Amsterdam, NL (amsterdam.voip.ms) 37.58.88.242
    • London, UK (london.voip.ms) 159.8.157.212
    • Melbourne, AU (melbourne.voip.ms) 168.1.73.84
    • Paris, FR (paris.voip.ms) 159.8.85.180

Dominios del Servidor

Para IOS, haga clic aquí Server Realms para obtener el nombre de dominio para el servidor que planea usar, esto puede diferir del nombre de dominio que se está utilizando.

¿Qué es un Ping?

Ping es la herramienta estándar usada para probar la latencia (demora) en conexiones en red. Normalmente es usada para determinar si un servidor o dispositivo puede ser alcanzado a través de la red y su tiempo de latencia (tiempo que toma en enviarse un paquete a su destino y regresar a su origen) para responder.

La herramienta Ping es parte de Windows, MAC OS y Linux, también se puede encontrar en algunos ruteadores.


¿Cómo funciona la herramienta Ping?

Esta envía mensajes de petición a un una dirección de red determinada o nombres DNS en ciertos intervalos de tiempo y contabiliza el tiempo que tarda en recibirse un mensaje de respuesta. (mejor conocido como tiempo de latencia)


¿Cómo hacer un ping en una PC?

Hacer ping es un comando que le dice si la conexión entre su computadora y un dominio en particular está funcionando correctamente.

En Windows, seleccione Inicio> Programas> Accesorios> Símbolo del sistema. Esto le dará una ventana como la de abajo.

Ingrese la palabra ping, seguida de un espacio, luego el nombre de dominio (montreal.voip.ms) en este caso, el dominio es el nombre de nuestro servidor.

Si los resultados muestran una serie de respuestas, la conexión está funcionando. El tiempo te muestra qué tan rápida es la conexión. Si ves un error de "tiempo de espera agotado" en lugar de una respuesta, hay una falla en algún lugar entre tu computadora y el dominio.

Ping


¿Cómo enviar un ping a una MAC?

1- Haga click en el buscador en la barra de herramientas.

2- Haga click en aplicaciones.

3- Haga click en utilidades (usos / configuraciones).

4- Haga doble-click en utilidades de red.*

*En OS X Mavericks (10.9.x), esta aplicación de utilidad cambió de ubicación. En su lugar, inícielo desde Spotlight, presione "comando" + "barra espaciadora" o haga clic en Spotlight directamente (icono de lupa en la parte superior derecha de la pantalla), escriba "utilidad de red" y presione "regresar"

5- En la ventana de utilidades de red, haga click en el el cuadro de ping.

6- En el campo debajo "Ingresese la direccion de red para hacer ping," como montreal.voip.ms

Si el ping resulta no ser consistente, puede tener un problema de jitter (variación del tiempo que tardan en llegar los paquetes debido a una congestión en la red o a diferentes rutas tomadas). Para tratar este problema, puede ajustar el nivel de jitter en su configuración del dispositivo VoIP (si cuenta con esta opción). Normalmente es recomendado un ping por debajo de 150ms para tener una buena calidad de audio durante la llamada. El tiempo de latencia del servidor es importante, sin embargo hay otros factores importantes a tomar en cuenta para la calidad de las llamadas como son la pérdida de paquetes (las comunicaciones VoIP son muy sensibles a esto) y el nivel de jitter de su conexión a Internet.

El siguiente es el resultado de ejecutar ping con el destino losangeles.voip.ms.

#ping losangeles.voip.ms
Ping to losangeles.voip.ms [67.215.241.250] with 32 bytes de datos:
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
Response from 67.215.241.250: bytes=32 time=69ms TTL=52
Response from 67.215.241.250: bytes=32 time=68ms TTL=52
Response from 67.215.241.250: bytes=32 time=67ms TTL=52
ping statistics from 67.215.241.250:
4 packets transmitted, 4 received, 0% packet lost. rtt min/avg/max/mdev = 67ms, 69ms, 67ms

Ejemplo de salida de ping en Windows:

C:\Windows\system32>ping montreal.voip.ms

Pinging montreal.voip.ms [67.205.74.184] with 32 bytes of data:
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=86ms TTL=49
Reply from 67.205.74.184: bytes=32 time=85ms TTL=49

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

Scripts de prueba de latencia (enviados por el usuario)

Todos los siguientes scripts fueron producidos por usuarios de voip.ms que sintieron que otros también podrían beneficiarse del resultado de sus esfuerzos. Se escribieron durante un período de años y probablemente deban ajustarse antes de usarlos, para adaptarse a los cambios en los servidores a lo largo del tiempo y los cambios en las políticas (como no probar servidores muy suscritos que no están abiertos a nuevos registros)

Si no está satisfecho con la seguridad de los scripts o simplemente no le gusta la forma en que aparecen sintácticamente, aún puede hacer ping manualmente a una selección de servidores y elegir un servidor en función de la mejor latencia. Los siguientes scripts son esencialmente envoltorios del comando ping que admiten listas de servidores para enviar a ping y presentar la salida en un formato legible.

Si cree que tiene un script más simple y limpio que funcione para otra plataforma o idioma, agréguelo a este wiki a través de un ticket de soporte.

Script de Bash para manejar el formato de salida de ping de Mac

Para hacer uso de este script (1) guárdelo como un archivo de texto sin formato (2) establezca los permisos del archivo en ejecutable (3) invoque el script p.ej. Guarde el script a continuación usando su editor favorito como pingVoipMS.sh (2) chmod u + x pingVoipMS.sh (3) ./pingVoipMS.sh Este es un script bash 3.x, por lo que también funciona en Linux, simplemente cambie el campo de pérdida de paquetes de ping de 7 a 6 en el ciclo final a continuación (o donde sea que el campo de pérdida esté en su formato de salida de ping). Dependiendo de su distribución, es posible que tenga que cambiar el curl a wget.

#!/bin/bash
# Ping several servers and display Latency, Jitter and Packet Loss
#      Usage: [-c <count>][-i <wait time>][-r test restricted servers][<server list file>]
#
# The optional server list text file should be formatted with one host name per line.
# The list of voip.ms servers is available at https://wiki.voip.ms/article/Choosing_Server
# If no args are supplied, this script will scrape a ping server list from voip.ms
#
USER_FILE=""
COUNT=3; INTERVAL=5; RESTRICTED=0
restrictedList=(atlanta.voip.ms chicago.voip.ms
                montreal.voip.ms montreal2.voip.ms montreal3.voip.ms montreal4.voip.ms
                newyork.voip.ms newyork4.voip.ms seattle.voip.ms
                toronto.voip.ms toronto2.voip.ms toronto3.voip.ms toronto4.voip.ms)

# Handle any passed in script arguments
while getopts c:i:r parm
do
    case $parm in
        c)count_opt=$OPTARG;;
        i)interval_opt=$OPTARG;;
        r)RESTRICTED=1;;
        *)echo -e "Invalid arg\nUsage:\t[ -c <count of ECHO_REQUESTs to Tx, default 3> ] \
                  \n\t[ -i <wait time (s) between datagrams, default 5> ]                \
                  \n\t[ -r ] Include restricted servers in latency test                  \
                  \n\t[FILE <ping server list> ]";exit 1;;
    esac
done

# Test if an option was specified and whether it's a +ve non-zero integer
[[ -n $count_opt    && ($count_opt =~ ^[[:digit:]]+$)    && $count_opt -gt 0 ]] &&
        COUNT=$count_opt
[[ -n $interval_opt && ($interval_opt =~ ^[[:digit:]]+$) && $interval_opt -gt 0 ]] &&
        INTERVAL=$interval_opt

shift $((OPTIND - 1))

# Validate supplied file (server list)
[[ -n $1 && ! (-f $1 && -r $1) ]] &&
        { echo "\"$1\" file does not exist or is not readable"; exit 1; }
[[ -n $1 && -f $1 && -r $1 ]] && USER_FILE="$1"

if [[ -n $USER_FILE ]]
then
# Bash 3.x in macOS does not support readarray, need to do cumbersome array loops instead
    while IFS= read -r servers; do
        serverList+=( "$servers" )
    done < <(grep -Eo '^\b[[:alpha:]]+?[[:alnum:]]\.voip\.ms\b$' "$USER_FILE" | \
             grep -v '^\s*#' | awk NF | sort)
else
# N.B. The script looks for the html boldface tags <b> </b> inside a bracket
# If the website alters and the parse fails, manually create the list and
# supply as a script arg (or perhaps update the parsing to work again :)
    while IFS= read -r servers; do
        serverList+=( "$servers" )
    done < <(curl -sm 10 https://wiki.voip.ms/article/Choosing_Server | \
             grep -E '(<b>[[:alpha:]]+?[[:alnum:]]\.voip\.ms</b>)'    | \
             tr "<>" " " | awk '{print $(NF-3)}' | sort                 )
fi

# Newer voip.ms clients can't register onto these over-subscribed servers
# Don't test the restricted list unless explicitly asked (with the -r cmd line option)
if [[ $RESTRICTED -eq 0 ]]
then
    for server in "${restrictedList[@]}"
    do
        ix=$(printf "%s\n" "${serverList[@]}" | grep -n "^${server}" | cut -d ":" -f1)
        while IFS= read -ra idx; do
            keys+=( "${idx[@]}" )
        done < <([[ $ix -gt 0 ]] && echo $((ix-1)))
    done
    for ((i=${#keys[@]} - 1; i >= 0; i--)); do unset "serverList[keys[i]]"; done
fi

if [[ ${#serverList[@]} -eq 0 ]]
then
    echo "No unrestricted Voip.ms servers could be found, please supply a server list"
    exit 1
fi

runTime=$((COUNT * INTERVAL * ${#serverList[@]}))

echo "PING will send $COUNT packet(s) with a wait of $INTERVAL sec(s) between each packet"
echo "Change the PING options by invoking this script with -c and/or -i, default \"-c 3 -i 5\""
echo "Over $((${#serverList[@]})) server(s) the estimated script Run Time will be $runTime seconds"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s   %s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss" "Countdown"
echo "================================================================  (seconds)"

for myLn in "${serverList[@]}"
do
     while IFS=$'\n' read -r pings; do
         pingList+=( "$pings" )
         printf "%-64s %5d   %2d/%-2d\n" "$pings" \
                "$((runTime - COUNT * INTERVAL * ${#pingList[@]}))" \
                "${#pingList[@]}" "${#serverList[@]}"
     done < <( ping -c "$COUNT" -i "$INTERVAL" -q "$myLn" | awk \
     '
        /^PING / {myH=$2}
        /^PING / {
            IP = substr($3,2,15)
            split(IP,myIP,")") }
        /packet loss/ {myPL=$7}
        /min\/avg\/max/ {
            split($4,myS,"/")
            printf("%-20s %-18s %7.3f %8.3f %6s\n",
                    myH, myIP[1], myS[2], myS[4], myPL ) }
     ' )
done

echo "================================================================"
echo -e "\nMost appropriate server listed in order of best latency\n"
echo "================================================================"
printf "%-20s %-18s %7s %8s %6s\n" "VoIP Server" "IP Address" "Latency" "Jitter" "Loss"
echo "================================================================"
printf "%s\n" "${pingList[@]}" | LC_ALL=C sort -n -k 3,3 -k 5,5 -k 4,4 | \
        awk '{printf("%s    \(%2d\)\n",$0, NR)}'
echo "================================================================"

Perl Script

Lista de ping de servidores voip.ms round robin con archivo csv de salida opcional.

   # usage ping_voip.ms.pl <number of times> <seconds in between> <output.csv>
   use Net::Ping;
   use Time::HiRes;
   use strict;
   
   # input list 
   my @hosts = qw(
       atlanta.voip.ms
       atlanta2.voip.ms
       chicago.voip.ms
       chicago2.voip.ms
       chicago3.voip.ms
       chicago4.voip.ms
       dallas.voip.ms
       denver.voip.ms
       denver2.voip.ms
       houston.voip.ms
       losangeles.voip.ms
       losangeles2.voip.ms
       newyork.voip.ms
       newyork2.voip.ms
       newyork3.voip.ms
       newyork4.voip.ms
       seattle.voip.ms
       seattle2.voip.ms
       seattle3.voip.ms
       tampa.voip.ms
       washington.voip.ms
       washington2.voip.ms
       montreal.voip.ms
       montreal2.voip.ms
       montreal3.voip.ms
       montreal4.voip.ms
       toronto2.voip.ms
       toronto3.voip.ms
       toronto4.voip.ms
       toronto.voip.ms
       london.voip.ms
   );
   
   $| = 1; #autoflush
   # High precision syntax (requires Time::HiRes)
   my $p = Net::Ping->new("icmp",1);
   $p->hires();
   my $max_name_length = (reverse sort { $a <=> $b } map { length($_) } @hosts)[0];
   my $count = 4; # number of times to ping
   my $interval = 5; # seconds between ping rounds
   my $output_file = "";
   my @data;
   
   # check for arguments
   my $num_args = @ARGV;
   if ($num_args >= 1) {$count = $ARGV[0];}
   if ($num_args >= 2) {$interval = $ARGV[1];}
   if ($num_args >= 3) {$output_file = $ARGV[2];}
   
   # check argument validity
   $0 =~ /^.*\\(.*)$/;
   my $script = $1;
   if ($count !~ /^\d+$/ or $interval !~ /^\d+$/) {die "Usage: $script <number of rounds> <seconds between rounds> <output.csv>\n";}
   if (length($output_file) > 0 and $output_file !~ /\.csv$/) {$output_file .= ".csv";}
   
   # main loop
   for my $i (1..$count)
   {
       sleep $interval unless $i == 1;
       print "Round $i\n";
       my $host_num=0;
       foreach my $host (@hosts)
       {
           (my $ret, my $duration, my $ip) = $p->ping($host);
           $ip =~ /(\d+)\.(\d+)\.(\d+)\.(\d+)/; 
           if ($ret)
           {
               printf("%*s [ip: %3s.%3s.%3s.%3s] is alive (%6.2f ms)\n", $max_name_length, $host, $1, $2, $3, $4, $duration*1000);
               $data[$host_num][$i]=$duration*1000;
           }
           else
           {
               printf("%*s [ip: %3s.%3s.%3s.%3s] is dead\n", $max_name_length, $host, $1, $2, $3, $4);
           }
           $host_num++;
       }
       print "\n";
   }
   $p->close();
   
   # if output file name given
   if (length($output_file)>0)
   {
       # print output to file
       open FILE, ">$output_file" or die "$!\n";
       
       # print column headers
       print FILE "Server\\Round";
       for my $i (1..$count)
       {
           print FILE ", $i";
       }
       print FILE ", Average\n";
       
       # print data
       my $i = 0;
       foreach my $host (@hosts)
       {
           print FILE "$host";
           my $sum = 0;
           for my $j (1..$count)
           {
               $sum += $data[$i][$j];
               printf FILE ", %8.4f",$data[$i][$j];
           }
           printf FILE ", %8.4f\n",$sum/$count;
           $i++;
       }
       
       close FILE;
       print "Data written to $output_file\n";
   }
   
   # print summary to screen
   my $i = 0;
   printf("%-*s Average (ms)\n", $max_name_length, "Server");
   foreach my $host (@hosts)
   {
       my $sum = 0;
       for my $j (1..$count)
       {
           $sum += $data[$i][$j];
       }
       printf("%-*s %8.4f\n", $max_name_length+1, $host, $sum/$count);
       $i++;
   }


Salidas:

   Round 1
       atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.97 ms)
      atlanta2.voip.ms [ip:  72.  9.246.170] is alive ( 92.99 ms)
       chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.70 ms)
      chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.76 ms)
      chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.53 ms)
      chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.73 ms)
        dallas.voip.ms [ip:  74. 54. 54.178] is alive ( 94.99 ms)
        denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.05 ms)
       denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.13 ms)
       houston.voip.ms [ip: 209. 62.  1.  2] is alive (102.87 ms)
    losangeles.voip.ms [ip:  96. 44.149.186] is alive ( 64.92 ms)
   losangeles2.voip.ms [ip:  96. 44.149.202] is alive ( 63.41 ms)
       newyork.voip.ms [ip:  74. 63. 41.218] is alive (131.75 ms)
      newyork2.voip.ms [ip: 107.  6. 67.236] is alive (120.64 ms)
      newyork3.voip.ms [ip: 107.  6. 67.237] is alive (120.49 ms)
      newyork4.voip.ms [ip: 107.  6. 67.238] is alive (111.43 ms)
       seattle.voip.ms [ip:  50. 23.160. 50] is alive ( 94.25 ms)
      seattle2.voip.ms [ip:  50. 23.160. 51] is alive ( 95.86 ms)
      seattle3.voip.ms [ip:  50. 23.160. 52] is alive ( 90.85 ms)
         tampa.voip.ms [ip:  68.233.226. 97] is alive (123.29 ms)
    washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.71 ms)
   washington2.voip.ms [ip: 208. 43.234.227] is alive (101.19 ms)
      montreal.voip.ms [ip:  67.205. 74.184] is alive ( 81.82 ms)
     montreal2.voip.ms [ip:  67.205. 74.187] is alive ( 86.13 ms)
     montreal3.voip.ms [ip:  72. 55.168. 18] is alive ( 77.09 ms)
     montreal4.voip.ms [ip:  67.205. 74.179] is alive ( 96.18 ms)
      toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.70 ms)
      toronto3.voip.ms [ip: 184. 75.215.146] is alive (131.27 ms)
      toronto4.voip.ms [ip: 184. 75.213.210] is alive (125.13 ms)
       toronto.voip.ms [ip: 184. 75.215.106] is alive (103.26 ms)
        london.voip.ms [ip:   5. 77. 36.136] is alive (152.77 ms)
   
   Round 2
       atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.14 ms)
      atlanta2.voip.ms [ip:  72.  9.246.170] is alive ( 92.86 ms)
       chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 50.03 ms)
      chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 59.44 ms)
      chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.33 ms)
      chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.22 ms)
        dallas.voip.ms [ip:  74. 54. 54.178] is alive ( 95.58 ms)
        denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.94 ms)
       denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.29 ms)
       houston.voip.ms [ip: 209. 62.  1.  2] is alive (102.73 ms)
    losangeles.voip.ms [ip:  96. 44.149.186] is alive ( 65.59 ms)
   losangeles2.voip.ms [ip:  96. 44.149.202] is alive ( 64.27 ms)
       newyork.voip.ms [ip:  74. 63. 41.218] is alive (112.74 ms)
      newyork2.voip.ms [ip: 107.  6. 67.236] is alive (121.22 ms)
      newyork3.voip.ms [ip: 107.  6. 67.237] is alive (121.34 ms)
      newyork4.voip.ms [ip: 107.  6. 67.238] is alive (110.75 ms)
       seattle.voip.ms [ip:  50. 23.160. 50] is alive ( 94.06 ms)
      seattle2.voip.ms [ip:  50. 23.160. 51] is alive ( 95.33 ms)
      seattle3.voip.ms [ip:  50. 23.160. 52] is alive ( 91.58 ms)
         tampa.voip.ms [ip:  68.233.226. 97] is alive (122.94 ms)
    washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.28 ms)
   washington2.voip.ms [ip: 208. 43.234.227] is alive (101.40 ms)
      montreal.voip.ms [ip:  67.205. 74.184] is alive ( 81.91 ms)
     montreal2.voip.ms [ip:  67.205. 74.187] is alive ( 85.64 ms)
     montreal3.voip.ms [ip:  72. 55.168. 18] is alive ( 75.15 ms)
     montreal4.voip.ms [ip:  67.205. 74.179] is alive ( 96.79 ms)
      toronto2.voip.ms [ip: 184. 75.215.114] is alive (103.10 ms)
      toronto3.voip.ms [ip: 184. 75.215.146] is alive (150.85 ms)
      toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.40 ms)
       toronto.voip.ms [ip: 184. 75.215.106] is alive (103.45 ms)
        london.voip.ms [ip:   5. 77. 36.136] is alive (170.79 ms)
   
   Round 3
       atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 88.76 ms)
      atlanta2.voip.ms [ip:  72.  9.246.170] is alive ( 92.86 ms)
       chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.65 ms)
      chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.01 ms)
      chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.05 ms)
      chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 49.53 ms)
        dallas.voip.ms [ip:  74. 54. 54.178] is alive ( 95.82 ms)
        denver.voip.ms [ip: 173.248.161. 90] is alive ( 95.02 ms)
       denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.60 ms)
       houston.voip.ms [ip: 209. 62.  1.  2] is alive (103.35 ms)
    losangeles.voip.ms [ip:  96. 44.149.186] is alive ( 65.79 ms)
   losangeles2.voip.ms [ip:  96. 44.149.202] is alive ( 64.05 ms)
       newyork.voip.ms [ip:  74. 63. 41.218] is alive (113.01 ms)
      newyork2.voip.ms [ip: 107.  6. 67.236] is alive (121.41 ms)
      newyork3.voip.ms [ip: 107.  6. 67.237] is alive (122.23 ms)
      newyork4.voip.ms [ip: 107.  6. 67.238] is alive (110.62 ms)
       seattle.voip.ms [ip:  50. 23.160. 50] is alive ( 93.65 ms)
      seattle2.voip.ms [ip:  50. 23.160. 51] is alive ( 95.19 ms)
      seattle3.voip.ms [ip:  50. 23.160. 52] is alive ( 90.75 ms)
         tampa.voip.ms [ip:  68.233.226. 97] is alive (125.12 ms)
    washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.19 ms)
   washington2.voip.ms [ip: 208. 43.234.227] is alive (101.98 ms)
      montreal.voip.ms [ip:  67.205. 74.184] is alive ( 80.16 ms)
     montreal2.voip.ms [ip:  67.205. 74.187] is alive ( 87.16 ms)
     montreal3.voip.ms [ip:  72. 55.168. 18] is alive ( 76.54 ms)
     montreal4.voip.ms [ip:  67.205. 74.179] is alive ( 97.51 ms)
      toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.18 ms)
      toronto3.voip.ms [ip: 184. 75.215.146] is alive (142.81 ms)
      toronto4.voip.ms [ip: 184. 75.213.210] is alive (138.95 ms)
       toronto.voip.ms [ip: 184. 75.215.106] is alive (103.78 ms)
        london.voip.ms [ip:   5. 77. 36.136] is alive (153.14 ms)
   
   Round 4
       atlanta.voip.ms [ip: 174. 34.146.162] is alive ( 89.19 ms)
      atlanta2.voip.ms [ip:  72.  9.246.170] is alive ( 92.98 ms)
       chicago.voip.ms [ip: 208.100. 39. 52] is alive ( 49.21 ms)
      chicago2.voip.ms [ip: 208.100. 39. 53] is alive ( 60.50 ms)
      chicago3.voip.ms [ip: 208.100. 39. 54] is alive ( 59.68 ms)
      chicago4.voip.ms [ip: 208.100. 39. 55] is alive ( 50.18 ms)
        dallas.voip.ms [ip:  74. 54. 54.178] is alive ( 93.93 ms)
        denver.voip.ms [ip: 173.248.161. 90] is alive ( 94.22 ms)
       denver2.voip.ms [ip: 173.248.159.210] is alive ( 85.10 ms)
       houston.voip.ms [ip: 209. 62.  1.  2] is alive (103.67 ms)
    losangeles.voip.ms [ip:  96. 44.149.186] is alive ( 65.58 ms)
   losangeles2.voip.ms [ip:  96. 44.149.202] is alive ( 63.60 ms)
       newyork.voip.ms [ip:  74. 63. 41.218] is alive (114.76 ms)
      newyork2.voip.ms [ip: 107.  6. 67.236] is alive (120.44 ms)
      newyork3.voip.ms [ip: 107.  6. 67.237] is alive (121.05 ms)
      newyork4.voip.ms [ip: 107.  6. 67.238] is alive (110.51 ms)
       seattle.voip.ms [ip:  50. 23.160. 50] is alive ( 94.04 ms)
      seattle2.voip.ms [ip:  50. 23.160. 51] is alive ( 96.92 ms)
      seattle3.voip.ms [ip:  50. 23.160. 52] is alive ( 91.23 ms)
         tampa.voip.ms [ip:  68.233.226. 97] is alive (123.28 ms)
    washington.voip.ms [ip: 208. 43.234.226] is alive ( 98.45 ms)
   washington2.voip.ms [ip: 208. 43.234.227] is alive (100.94 ms)
      montreal.voip.ms [ip:  67.205. 74.184] is alive ( 82.33 ms)
     montreal2.voip.ms [ip:  67.205. 74.187] is alive ( 85.02 ms)
     montreal3.voip.ms [ip:  72. 55.168. 18] is alive ( 76.85 ms)
     montreal4.voip.ms [ip:  67.205. 74.179] is alive ( 96.32 ms)
      toronto2.voip.ms [ip: 184. 75.215.114] is alive (104.22 ms)
      toronto3.voip.ms [ip: 184. 75.215.146] is alive (148.33 ms)
      toronto4.voip.ms [ip: 184. 75.213.210] is alive (141.61 ms)
       toronto.voip.ms [ip: 184. 75.215.106] is alive (105.91 ms)
        london.voip.ms [ip:   5. 77. 36.136] is alive (152.85 ms)
   
   Server              Average (ms)
   atlanta.voip.ms       88.7630
   atlanta2.voip.ms      92.9233
   chicago.voip.ms       49.6477
   chicago2.voip.ms      59.9305
   chicago3.voip.ms      59.3972
   chicago4.voip.ms      49.9152
   dallas.voip.ms        95.0790
   denver.voip.ms        94.8077
   denver2.voip.ms       85.2797
   houston.voip.ms      103.1562
   losangeles.voip.ms    65.4693
   losangeles2.voip.ms   63.8347
   newyork.voip.ms      118.0643
   newyork2.voip.ms     120.9265
   newyork3.voip.ms     121.2778
   newyork4.voip.ms     110.8275
   seattle.voip.ms       93.9993
   seattle2.voip.ms      95.8267
   seattle3.voip.ms      91.1035
   tampa.voip.ms        123.6570
   washington.voip.ms    98.4065
   washington2.voip.ms  101.3774
   montreal.voip.ms      81.5525
   montreal2.voip.ms     85.9863
   montreal3.voip.ms     76.4058
   montreal4.voip.ms     96.7013
   toronto2.voip.ms     103.7986
   toronto3.voip.ms     143.3156
   toronto4.voip.ms     136.0254
   toronto.voip.ms      104.1012
   london.voip.ms       157.3885

Powershell

Diciembre 2017 - Un problema en el codigo  del dominio washington2.voip.ms lo mostraba como el mejor servidor, esto fue corregido.
# Usage: Copy and paste the following code into a powershell window
# To run it from a command prompt, save this file with extension ps1. 
# Then run Powershell.exe -file "pathtothisscript.ps1"
Clear-Variable best* -Scope Global #Clear the best* variables in case you run it more than once...
#Get the list of servers into an array
$Servers =      
@("amsterdam.voip.ms","atlanta.voip.ms","atlanta2.voip.ms","chicago.voip.ms","chicago2.voip.ms","chicago3.voip.ms",
"chicago4.voip.ms","dallas.voip.ms","dallas2.voip.ms","denver.voip.ms","denver2.voip.ms","houston.voip.ms",
"houston2.voip.ms","london.voip.ms","losangeles.voip.ms","losangeles2.voip.ms","melbourne.voip.ms","montreal.voip.ms",
"montreal2.voip.ms","montreal3.voip.ms","montreal4.voip.ms","montreal5.voip.ms","montreal6.voip.ms","montreal7.voip.ms",
"montreal8.voip.ms","newyork.voip.ms","newyork2.voip.ms","newyork3.voip.ms","newyork4.voip.ms","newyork5.voip.ms",
"newyork6.voip.ms","newyork7.voip.ms","newyork8.voip.ms","paris.voip.ms","sanjose.voip.ms","sanjose2.voip.ms",
"seattle.voip.ms","seattle2.voip.ms","seattle3.voip.ms","tampa.voip.ms","tampa2.voip.ms","toronto.voip.ms",
"toronto2.voip.ms","toronto3.voip.ms","toronto4.voip.ms","toronto5.voip.ms","toronto6.voip.ms","toronto7.voip.ms",
"toronto8.voip.ms","vancouver.voip.ms","vancouver2.voip.ms","washington.voip.ms","washington2.voip.ms")
$k = 0 #Counting variable so we know what server number we are testing
#num of servers to test
$servercount = $servers.length 
#Do the following code for each server in our array
ForEach($server in $servers)
{  
  #Add one to the counting variable....we are on server #1...then server 2, then server 3 etc...
  $k++
  #Update the progress bar                    
  Write-Progress -Activity "Testing Server: ${server}" -status "Testing Server $k out of $servercount" -percentComplete ($k / $servercount*100) 
  #Counting variable for number of times we tried to ping a given server
  $i = 0
  Do{
     #assume a failure
     $pingsuccess = $false 
     $i++ #Add one to the counting variable.....1st try....2nd try....3rd try etc...
     Try{
         #Try to ping
         $currentping = (test-connection $server -count 1 -ErrorAction Stop).responsetime 
         #If success full, set success variable
         $pingsuccess = $true
     }
     #Catch the failure and set the success variable to false
     Catch {
      $pingsuccess = $false 
      }     
  }
  #Try everything between Do and While up to 5 times, or while $pingsuccess is not true
  While($pingsuccess -eq $false -and $i -le 5) 
  #Compare the last ping test with the best known ping test....if there is no known best ping test, assume this one is the best $bestping = $currentping 
  If($pingsuccess -and ($currentping -lt $bestping -or (!($bestping)))){ 
  #If this is the best ping...save it
        $bestserver = $server    #Save the best server
        $bestping = $currentping #Save the best ping results
  }
  write-host "tested: $server at $currentping ms after $i attempts" #write the results of the test for this server
}
write-host "`r`n The server with the best ping is: $bestserver at $bestping ms`r`n" #write the end result
Pause

Linux Shell Script

Hace ping a varios servidores voip.ms

  #!/bin/sh
  # Ping several servers and display Latency, Jitter and Packet Loss 
  #
  # First, create a text file with all servers you want to ping - one host name per line. 
  # The list of voip.ms servers is available at http://wiki.voip.ms/article/Choosing_Server
  myHF="voip_ping_hosts.txt"
  # Sample file:
  #    toronto.voip.ms
  #    montreal.voip.ms
  #    seattle.voip.ms
  #    chicago.voip.ms
  #    newyork.voip.ms
  #
  echo "============================================"
  printf "%-20s %7s %8s %6s\n" "VoIP Server" "Latency" "Jitter" "Loss"
  echo "============================================"
  cat ${myHF} |\
  while read myLn
  do
     ping -c 3 -i 5 -q $myLn |\
     awk '/^PING / {myH=$2}
          /packet loss/ {myPL=$6}
          /min\/avg\/max/ {
             split($4,myS,"/")
             printf( "%-20s    %3.1f    %1.3f   %4s\n", myH, myS[2], myS[4], myPL)
         }'
  done
  echo "============================================"

Salidas:

  ============================================
  VoIP Server          Latency   Jitter   Loss
  ============================================
  toronto.voip.ms         68.3    0.439     0%
  montreal.voip.ms        89.6    0.197     0%
  seattle.voip.ms         71.2    0.387     0%
  chicago.voip.ms         71.6    0.084     0%
  newyork.voip.ms         79.1    0.411     0%
  ============================================

La Latencia y su importancia

La latencia es muy importante para Voip, esto determinará el tiempo que tardará la transmisión del paquete de datos en llegar al destino. Una latencia alta provocará un retraso y ecos en la comunicación.

La latencia se mide en milisegundos (ms) Por ejemplo: una latencia de 150 ms es apenas perceptible, por lo que es aceptable. Más alto que eso, la calidad comienza a sufrir. Cuando supera los 300 ms, se vuelve inaceptable.

Personal tools
Namespaces
Variants
Actions
VoIP.ms Wiki
VoIP.ms Blog
Configuration
Guides (English)
Guides (Français)
Guías (Español)
Toolbox