llamas remotas

Soporte general de la Central Telefónica 3CX para Windows, SIP y VoIP (por parte de la Comunidad) Apoyo de usuario a usuario - Las respuestas son proporcionadas por la comunidad. 3CX no aporta ningún tipo de soporte técnico por medio de este foro.

Moderators: kevin, 3CX staff

llamas remotas

Postby juanniram » Wed Jan 07, 2009 3:46 pm

Hola miren he intentado artas cosas pero no me resulta, les explico

tengo instalado el sistema 3cx en un pc que esta en mi casa, seria el servidor, cree 4 extenciones a otros pcs dentro de la red de mi casa, pero
he tratado de conectar otro pc que esta en otra region, y no me deja. no funciona

el servidor tiene instalado el no-ip para fijar la ip, me podrian ayudar a solucionar esto porfa, que quiero enlazar el pc de mi madre y el de unos familiares, asi hablamos gratis entre la familia usando las conecciones, no quiero usar el msn , o skype por eso pregunto como hacerlo por este medio sera posible??? me falta configurar el remoto, si es que no hay que modificar algo en el server , bueno espero me ayuden gracias
juanniram
New User
 
Posts: 5
Joined: Mon Dec 29, 2008 7:25 pm

Re: llamas remotas

Postby edossantos » Wed Jan 07, 2009 4:42 pm

¿Estás intentando configurar las extensiones remotas usando el tunel o en forma directa?
¿El teléfono se registra? ¿O los problemas son en el audio? ¿Qué estás usando como extensión remota?
¿Podés postear los logs del estado del servidor?
Ernesto Dos Santos Afonso
BORTECH
http://www.bor-tech.com
edossantos
3CX Valued Professional
3CX Valued Professional
 
Posts: 666
Joined: Wed Jun 27, 2007 6:54 pm
Location: Buenos Aires, Argentina

Re: llamas remotas

Postby juanniram » Wed Jan 07, 2009 5:02 pm

lo he intentado en forma directa y en local (el pc remoto)
en ninguna logra conectarse
el tunel no lo he usado porque dice que en la vercion gratis no esta disponible

cual seria la forma correcta de configurar el server y el cliente remoto para realizar una coneccion directa??

el log del server es el siguiente

Code: Select all
12:58:58.165  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:56.962  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:56.852  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:55.977  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:55.102  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:53.899  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:53.790  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:52.915  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:52.040  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:50.837  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:50.727  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:49.852  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:49.040  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:47.837  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:47.727  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:46.852  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:45.977  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:44.774  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:44.665  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:43.790  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:42.915  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:41.712  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:41.602  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:40.727  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:39.852  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:38.649  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:38.540  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:37.665  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:36.805  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:35.587  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:35.477  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:34.602  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:33.774  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:32.571  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:32.462  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:31.587  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:30.712  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:29.508  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:29.399  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:28.524  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:27.649  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:26.415  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:26.305  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:25.524  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:24.649  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:23.415  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:23.305  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:22.430  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:21.555  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:21.399  [CM504008]: Fax Service: registered as sip:888@192.168.1.143:5060 with contact sip:888@192.168.1.143:5100;user=phone

12:58:20.321  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:20.212  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:19.337  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:18.524  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:17.321  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:17.212  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:16.337  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:15.462  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:14.258  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:14.149  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:13.274  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:12.399  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:11.196  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:11.087  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:10.212  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:09.337  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:08.133  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:08.024  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:07.149  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:06.274  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:05.071  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:04.962  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:04.087  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:03.243  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:02.040  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:01.930  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:01.055  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:58:00.180  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:58.993  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:58.883  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:58.008  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:57.133  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:55.993  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:55.868  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:54.993  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:54.118  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:52.977  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:52.868  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:51.993  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:51.118  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:49.915  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:49.805  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:48.930  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:48.055  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:46.852  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:46.743  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:45.868  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:44.993  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060

12:57:43.790  [CM506004]: STUN request to STUN server 190.82.38.193:3478 has timed out; used Transport: 192.168.1.143:5060
juanniram
New User
 
Posts: 5
Joined: Mon Dec 29, 2008 7:25 pm

Re: llamas remotas

Postby edossantos » Wed Jan 07, 2009 5:08 pm

En la versión gratuita el tunel para extensiones está disponible. Lo que no está disponible es el tunel entre centrales 3CX. Es decir, podés configurar una extensión remota utilizando el tunel, pero no conectar dos centrales 3CX instaladas en sitios remotos.
¿Cuál es el escenario exacto donde querés utilizar esto?
Ernesto Dos Santos Afonso
BORTECH
http://www.bor-tech.com
edossantos
3CX Valued Professional
3CX Valued Professional
 
Posts: 666
Joined: Wed Jun 27, 2007 6:54 pm
Location: Buenos Aires, Argentina

Re: llamas remotas

Postby juanniram » Wed Jan 07, 2009 5:23 pm

ah.. ok mira tengo la central en mi casa, como veras en el log le asigne la ip 192.168.1.143 en local al server, a este server le estoy dando salida usando el no-ip para fijar la ip, al otro lado en casa de mi madre esta en otra region pero tiene internet aya instale el cliente de la centralita, lo administro con radadmin para hacer cambios, entonces para hacer uso del tunel entre central y y cliente remoto como lo tendria que hacer???
juanniram
New User
 
Posts: 5
Joined: Mon Dec 29, 2008 7:25 pm

Re: llamas remotas

Postby edossantos » Wed Jan 07, 2009 5:34 pm

La central siempre está preparada para recibir llamadas a través del tunel. Tenés que abrir el puerto correspondiente en el firewall del sitio donde está la 3CX y apuntarlo a ese servidor. Este puerto por defecto es el 5090 TCP. Te recomiendo que leas la sección "Firewall configuration" del manual para información más detallada.

En el extremo de la extensión remota necesitás configurar el 3CX VoIP Client para que utilice el tunel. En el manual del 3CX VoIP Client tenés el instructivo paso por paso, en la sección "Configuring a remote connection using the 3CX Tunnel".

Si tenés problemas con el inglés, la versión 6 tiene los manuales traducidos al español en http://www.3cx.com/ip-pbx/downloadlinks.html. En estos puntos la configuración es muy similar y debería servirte como guía...

Si llegás a tener alguna duda adicional, estamos a tu disposición.
Ernesto Dos Santos Afonso
BORTECH
http://www.bor-tech.com
edossantos
3CX Valued Professional
3CX Valued Professional
 
Posts: 666
Joined: Wed Jun 27, 2007 6:54 pm
Location: Buenos Aires, Argentina

Re: llamas remotas

Postby juanniram » Wed Jan 07, 2009 5:38 pm

ya, ahora modifico el post ya que solucione el problema, era super simple de solucionar, como uds me decian la central esta lista para recibir, pero como estaba en la red local yo instale usando la ip local, lo que hice fue desintalar todo, y reinstale, cuando me pide la ip de la central le doy el dominio que cree con no ip y sigo los pasos normales, y a los clientes le doy coneccion directa y en la ip le doy el dominio no-ip que tiene el servidor y solucionado, ahora me funciona en laocal y en remoto :P muchas gracias por la atencion se pasaron
juanniram
New User
 
Posts: 5
Joined: Mon Dec 29, 2008 7:25 pm

Re: llamas remotas

Postby emily » Fri Sep 09, 2011 8:06 pm

También estoy usando la versión gratuita, me funciona perfecto dentro de mi LAN. Pero no se que debo descargar ni de dónde o cómo configurar mis extensiones remotas, me interesa poder contestar en mi casa las llamadas que entren a la oficina. Muchas gracias

¿Puedo también crear una extensión remota y contestar en un teléfono celular (iphone o un android), con servicio de datos del proveedor de telefonía móvil de mi país? Entendiendose que no se encuentran dentro de mi LAN, sino con servicio de datos y 3G en cualquier punto de la ciudad.
emily
New User
 
Posts: 1
Joined: Fri Sep 09, 2011 3:32 pm

Re: llamas remotas

Postby hg » Thu Sep 15, 2011 8:44 am

si pero debes configurar todo el entorno de acuerdo a lo que stas necesitando hacer, con esto quiero decir, que si necesitas acceder a 3cx desde fuera para conectarte con una extension remota, debes abrir los puertos en el router necesarios (se explican en el manual de 3CX) o poner la 3CX en la dmz y asi acceder desde cualquier telefono
Hugo Guindani
HGcomp.com - 3CX Partner - Sangoma Partner
Soluciones Tecnologicas de valor agregado en Telecomunicaciones
http://blog.hgcomp.com - http://www.hgcomp.com
hg
3CX Valued Professional
3CX Valued Professional
 
Posts: 920
Joined: Mon Aug 11, 2008 8:15 am


Return to Español


Who is online

Users browsing this forum: No registered users and 2 guests

Announcements: