PROBLEMAS AL LLAMAR

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

PROBLEMAS AL LLAMAR

Postby apcomt » Sat Nov 27, 2010 7:29 pm

Buenas tardes a todos, primero que nada, hasta hace unas dias no sabia como Montar una centralita de estas, (me parece cool), Instale aSTERISKw32 y funciono bien, (bastante bien para ser mi primera prueba) investigue y descubir 3CX instale (version de evaluacion) y al configurar mi XLITE marca como Phone Ready, en la 3CX me carca "Registrado(No Ocupado)" pero cuando intento llamar entre usuarios XLITE marca Failed to stablish call, Mi maquina tiene Firewall Desactivado, y En Modo DMZ desde el Router. de hecho el usuario si se registra. Es mi primera Prueba, estoy pensando seriamente Iniciar en Este Negocio.
apcomt
New User
 
Posts: 11
Joined: Sat Nov 27, 2010 7:24 pm

Re: PROBLEMAS AL LLAMAR

Postby hg » Mon Nov 29, 2010 1:57 pm

los usuarios estan en distintos equipos? o tenes todo en el mismo?. la llamada que intentas realizar es entre extensiones? o estas tratando de llamar por una linea (IP, PSNT, Skype)??
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

Re: PROBLEMAS AL LLAMAR

Postby apcomt » Mon Nov 29, 2010 4:27 pm

Estoy intentando hablar entre extensiones en 2 equipos diferentes. las dos maquinas estan en mi red LOCAL, el servidor tambien esta en la RED local. aun no he podido establecer la llamada, cuando marca inmediatamente marca que fallo la llamada,
apcomt
New User
 
Posts: 11
Joined: Sat Nov 27, 2010 7:24 pm

Re: PROBLEMAS AL LLAMAR

Postby hg » Thu Dec 02, 2010 4:05 pm

Que equipos estas utilizando???? softphones??? ip Phones???... nos puedes mostrar un log?, estan registrados en la pbx?
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

Re: PROBLEMAS AL LLAMAR

Postby apcomt » Fri Dec 03, 2010 10:03 pm

Estoy usando SOFTPOHONE (XLITE)

este es el log

14:58:19.203

Requests rate from IP 192.168.1.68 is too high! Blacklisted for 334 seconds

14:58:19.203

[CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:



INVITE sip:1000@sportmaster.sytes.net SIP/2.0



Via: SIP/2.0/UDP 192.168.1.68:30938;branch=z9hG4bK-d8754z-84d4cda545b5bcc1-1---d8754z-;rport=30938



Max-Forwards: 70



Contact: <sip:1000@192.168.1.68:30938>



To: <sip:1000@sportmaster.sytes.net>



From: "Adrian"<sip:1000@sportmaster.sytes.net>;tag=d66a1d81



Call-ID: Yzg4OGUwZDBlOTcxN2JiN2E5NTM4NzBkYjhlMDYxYzY.



CSeq: 1 INVITE



Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO



Supported: replaces



User-Agent: X-Lite 4 release 4.0 stamp 58832



Content-Length: 0





14:58:19.203

[CM302001]: Authorization system can not identify source of: SipReq: INVITE 1000@sportmaster.sytes.net tid=84d4cda545b5bcc1 cseq=INVITE contact=1000@192.168.1.68:30938 / 1 from(wire)

14:58:15.796

[CM302001]: Authorization system can not identify source of: SipReq: SUBSCRIBE *47@mty13.axtel.net tid=1bafcf71a7f7dc40 cseq=SUBSCRIBE contact=1000@192.168.1.68:30938 / 1 from(wire)

14:58:15.796

[CM302001]: Authorization system can not identify source of: SipReq: SUBSCRIBE 1000@sportmaster.sytes.net tid=96a62e8ba0156dd0 cseq=SUBSCRIBE contact=1000@192.168.1.68:30938 / 1 from(wire)

14:58:15.656

[CM504001]: Ext.1000: new contact is registered. Contact(s): [sip:1000@192.168.1.68:30938;rinstance=d5c34aae6156fea3/1000]

14:57:51.937

[CM102001]: Authentication failed for SipReq: REGISTER sportmaster.sytes.net tid=99610e97df899a08 cseq=REGISTER contact=1000@192.168.1.68:52844 / 2 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

14:56:02.125

[CM504001]: Ext.MakeCall: new contact is registered. Contact(s): [sip:MakeCall@127.0.0.1:40600;rinstance=04dd1f476022a54f/MakeCall]

14:56:02.125

[CM504001]: Ext.IVRForward: new contact is registered. Contact(s): [sip:IVRForward@127.0.0.1:40600;rinstance=fbbe2640595be993/IVRForward]

14:56:02.125

[CM504001]: Ext.EndCall: new contact is registered. Contact(s): [sip:EndCall@127.0.0.1:40600;rinstance=9f106431eaa4bc78/EndCall]

14:56:02.015

[CM504001]: Ext.9999: new contact is registered. Contact(s): [sip:9999@127.0.0.1:40600;rinstance=c086eec2fb69c1d3/9999]

14:56:01.359

[CM504001]: Ext.7004: new contact is registered. Contact(s): [sip:7004@127.0.0.1:40300;rinstance=ca8fe8da3478ac24/7004]

14:56:01.359

[CM504001]: Ext.7003: new contact is registered. Contact(s): [sip:7003@127.0.0.1:40300;rinstance=f24394da15db3b6e/7003]

14:56:01.265

[CM504001]: Ext.7002: new contact is registered. Contact(s): [sip:7002@127.0.0.1:40300;rinstance=83245538af0518ef/7002]

14:56:01.265

[CM504001]: Ext.7001: new contact is registered. Contact(s): [sip:7001@127.0.0.1:40300;rinstance=9b6e0e791ffe63f3/7001]

14:56:01.265

[CM504001]: Ext.7000: new contact is registered. Contact(s): [sip:7000@127.0.0.1:40300;rinstance=174cbc1465046362/7000]

14:56:00.890

[CM504001]: Ext.SP9: new contact is registered. Contact(s): [sip:SP9@127.0.0.1:40000;rinstance=875cc82a2ca226a3/SP9]

14:56:00.890

[CM504001]: Ext.SP8: new contact is registered. Contact(s): [sip:SP8@127.0.0.1:40000;rinstance=b03e97e0d870143f/SP8]

14:56:00.890

[CM504001]: Ext.SP7: new contact is registered. Contact(s): [sip:SP7@127.0.0.1:40000;rinstance=cdc5e086595f1daf/SP7]

14:56:00.890

[CM504001]: Ext.SP6: new contact is registered. Contact(s): [sip:SP6@127.0.0.1:40000;rinstance=09deb652b4ed9eae/SP6]

14:56:00.875

[CM504001]: Ext.SP5: new contact is registered. Contact(s): [sip:SP5@127.0.0.1:40000;rinstance=b44428cf5b12e7f9/SP5]

14:56:00.859

[CM504001]: Ext.SP4: new contact is registered. Contact(s): [sip:SP4@127.0.0.1:40000;rinstance=49f46d2990d9e895/SP4]

14:56:00.859

[CM504001]: Ext.SP3: new contact is registered. Contact(s): [sip:SP3@127.0.0.1:40000;rinstance=0dab720e2c9d8afc/SP3]

14:56:00.812

[CM504001]: Ext.SP2: new contact is registered. Contact(s): [sip:SP2@127.0.0.1:40000;rinstance=7d2455523f1d7de6/SP2]

14:56:00.812

[CM504001]: Ext.SP1: new contact is registered. Contact(s): [sip:SP1@127.0.0.1:40000;rinstance=bf596458e595ec78/SP1]

14:56:00.812

[CM504001]: Ext.SP0: new contact is registered. Contact(s): [sip:SP0@127.0.0.1:40000;rinstance=a64117278b173c3d/SP0]

14:56:00.812

[CM504001]: Ext.*1: new contact is registered. Contact(s): [sip:*1@127.0.0.1:40000;rinstance=967a5e906188924a/*1]

14:56:00.781

[CM504001]: Ext.*0: new contact is registered. Contact(s): [sip:*0@127.0.0.1:40000;rinstance=ac5aa81dccde774f/*0]

14:56:00.750

[CM504001]: Ext.*777: new contact is registered. Contact(s): [sip:*777@127.0.0.1:40000;rinstance=6594c414e46592de/*777]

14:55:53.843

[EC200002]: Media server is connected: application:ServerDedicado:0/MediaServer local:127.0.0.1:5482 remote:127.0.0.1:1407

14:55:52.250

[EC200006]: Conference server is connected: application:ServerDedicado:0/3CXConferenceRoom local:127.0.0.1:5482 remote:127.0.0.1:1406

14:55:52.062

IP(s) added:[189.158.13.137]

14:55:50.875

[EC200005]: Parking Orbit server is connected: application:ServerDedicado:0/3CXParkOrbit local:127.0.0.1:5482 remote:127.0.0.1:1405

14:55:50.125

[CM504008]: Fax Service: registered as sip:8888@189.158.13.137:5060 with contact sip:8888@189.158.13.137:5100;user=phone

14:55:47.921

[EC200004]: IVR server is connected: application:ServerDedicado:0/IVRServer local:127.0.0.1:5482 remote:127.0.0.1:1401

14:55:43.546

[CM506002]: Resolved SIP external IP:port (189.158.13.137:5060) on Transport 189.158.13.137:5060

14:55:43.312

[CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 189.158.13.137:5060

14:55:42.031

Failed to obtain short path name for [C:\Documents and Settings\All Users\Datos de programa\3CX\Bin\Cert]

14:55:42.031

[CM501006]: Default Local IP address: [189.158.13.137]

14:55:42.031

[CM501002]: Version: 9.0.14474.0

14:55:42.031

[CM501007]: *** Started Calls Controller thread ***

14:55:42.031

[CM501001]: Start 3CX PhoneSystem Call Manager

14:55:41.906

[EC200001]: Configuration server is connected: application:ServerDedicado:5485/DBProvider local:127.0.0.1:1399 remote:127.0.0.1:5485

14:55:41.906

[CM501009]: License Info: Loaded Succeede


lo reinstale 3 veces y es igual
apcomt
New User
 
Posts: 11
Joined: Sat Nov 27, 2010 7:24 pm

Re: PROBLEMAS AL LLAMAR

Postby hg » Mon Dec 06, 2010 6:11 pm

ntes quenada, te recomiendo que uses el 3cx phone, no el xlite, por lo menos hasta q tengas todo funcionando, por otro lado te pido q me des mas detalles como por ej: ip de la central telefonica, y los datos que tenes configurados en el xlite, como por ej. proxy, usuario, pass etc, pq estaria todo bien.
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

Re: PROBLEMAS AL LLAMAR

Postby apcomt » Wed Dec 08, 2010 4:52 pm

Antes que nada, gracias por ayudarme,

Te comento, no tengo una direccion IP Fija pero tengo un Dominio Redirigido a mi IP

sportmaster.sytes.net

Ya instale el 3CXPHONE y cuando intento llamar entre 3CXPHONE marca "Forbidden" estando los 2 registrados en la Centralita.

extension: 1000
id: 1000
password: 3004 (lo pongo para que puedas hacer pruebas)

en el XLITE pongo domain sportmaster.sytes.net

en xlite tecleo que use direccion local (local ip)
apcomt
New User
 
Posts: 11
Joined: Sat Nov 27, 2010 7:24 pm

Re: PROBLEMAS AL LLAMAR

Postby apcomt » Thu Dec 09, 2010 12:27 am

EL SERVIDOR ESTA "on" DE LAS 8:30AM A LAS 6:00PM TIEMPO DE LA CIUDAD DE MEXICO, MEXICO
apcomt
New User
 
Posts: 11
Joined: Sat Nov 27, 2010 7:24 pm

Re: PROBLEMAS AL LLAMAR

Postby aesteve » Thu Dec 09, 2010 2:11 am

Hola,

tu problema es de Firewall. Desactiva el Firewall de Windows. ( O mira si tu Antivirus lleva Firewall )

Un saludo.
Alejandro Esteve
3CX Certified Partner - 3CX Premium Parter España
Microsoft Certified Profesional
VoIP Provider MASQUEVOZ
http://www.masquevoz.es
aesteve
3CX Valued Professional
3CX Valued Professional
 
Posts: 601
Joined: Sat Sep 20, 2008 10:30 am
Location: Spain

Re: PROBLEMAS AL LLAMAR

Postby apcomt » Fri Dec 10, 2010 6:54 pm

Dudo mucho que sea Firewall, ya que el firewall de windows esta desactivado, y el del Antivirus tambien. de hecho hasta descativo el Antivirus totalmente, y aun asi no ,

Si fuera de firewall el programa ni se conectaria y este si se conecta, pero no realiza llamadas. aun asi aunque instale el 3CX Phone, este no puede realizar llamadas.
apcomt
New User
 
Posts: 11
Joined: Sat Nov 27, 2010 7:24 pm

Re: PROBLEMAS AL LLAMAR

Postby apcomt » Fri Dec 10, 2010 6:54 pm

hg wrote:Que equipos estas utilizando???? softphones??? ip Phones???... nos puedes mostrar un log?, estan registrados en la pbx?

les muestro 2 usuarios que tengo registrados en la pbx ,Solo para hacer pruebas: les pongo mis datos de la pbx.

en el navegador tecleen http://adminpack.sytes.net:5481

usuario: 'admin'
password: 'telpro'

Por favor, si hacen que funcione digando que ajustes hicieron.

Por motivos de seguridad: el servidor PBX estara disponible hasta el 11 - DICIEMBRE - 2010

señores, no hagan cambio de password de la PBX si no, esto no valdra. gracias
apcomt
New User
 
Posts: 11
Joined: Sat Nov 27, 2010 7:24 pm

Re: PROBLEMAS AL LLAMAR

Postby hg » Fri Dec 10, 2010 7:53 pm

Cuando hagas estas cosas hacelas, por mensaje privado por tu seguridad....
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

Re: PROBLEMAS AL LLAMAR

Postby aesteve » Sat Dec 11, 2010 12:12 pm

El test de firewall de 3CX lo pasa con normailidad ?
Alejandro Esteve
3CX Certified Partner - 3CX Premium Parter España
Microsoft Certified Profesional
VoIP Provider MASQUEVOZ
http://www.masquevoz.es
aesteve
3CX Valued Professional
3CX Valued Professional
 
Posts: 601
Joined: Sat Sep 20, 2008 10:30 am
Location: Spain

Re: PROBLEMAS AL LLAMAR

Postby apcomt » Sat Dec 11, 2010 4:00 pm

AQUI ESTA LA PRUEBA DE FIREWALL, Y SIGO SIN PODER LLAMAR. EH VISTO MANUALES, Y AL PARECER TODO SALE BIEN.
EL 3CX MARCA ON HOOK Y AL INTENTAR LLAMAR, SE DESCONECTA O ALGO PASA, Y EL XLITE, INFORMA "PHONE READY" Y AL INTENTAR LLAMAR INFORMA "FAILED".

[size=50]3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.
<08:55:29>: Phase 1, checking servers connection, please wait...
<08:55:29>: Stun Checker service is reachable. Phase 1 check passed. <08:55:29>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
<08:55:30>: UDP SIP Port is set to 5060. Response received correctly with no translation. Phase 2a check passed.
<08:55:30>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
<08:55:30>: TCP SIP Port is set to 5060. Response received correctly with no translation. Phase 2b check passed. <08:55:30>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
<08:55:30>: TCP TUNNEL Port is set to 5090. Response received correctly with no translation. Phase 3 check passed. <08:55:30>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
<08:55:37>: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
<08:55:37>: UDP RTP Port 9001. Response received correctly with no translation. Phase 4-02 check passed.
<08:55:37>: UDP RTP Port 9002. Response received correctly with no translation. Phase 4-03 check passed.
<08:55:37>: UDP RTP Port 9003. Response received correctly with no translation. Phase 4-04 check passed.
<08:55:37>: UDP RTP Port 9004. Response received correctly with no translation. Phase 4-05 check passed.
<08:55:37>: UDP RTP Port 9005. Response received correctly with no translation. Phase 4-06 check passed.
<08:55:37>: UDP RTP Port 9006. Response received correctly with no translation. Phase 4-07 check passed.
<08:55:37>: UDP RTP Port 9007. Response received correctly with no translation. Phase 4-08 check passed.
<08:55:37>: UDP RTP Port 9008. Response received correctly with no translation. Phase 4-09 check passed.
<08:55:37>: UDP RTP Port 9009. Response received correctly with no translation. Phase 4-10 check passed.
<08:55:37>: UDP RTP Port 9010. Response received correctly with no translation. Phase 4-11 check passed.
<08:55:37>: UDP RTP Port 9011. Response received correctly with no translation. Phase 4-12 check passed.
<08:55:37>: UDP RTP Port 9012. Response received correctly with no translation. Phase 4-13 check passed.
<08:55:37>: UDP RTP Port 9013. Response received correctly with no translation. Phase 4-14 check passed.
<08:55:37>: UDP RTP Port 9014. Response received correctly with no translation. Phase 4-15 check passed.
<08:55:37>: UDP RTP Port 9015. Response received correctly with no translation. Phase 4-16 check passed.
<08:55:37>: UDP RTP Port 9016. Response received correctly with no translation. Phase 4-17 check passed.
<08:55:37>: UDP RTP Port 9017. Response received correctly with no translation. Phase 4-18 check passed.
<08:55:37>: UDP RTP Port 9018. Response received correctly with no translation. Phase 4-19 check passed.
<08:55:37>: UDP RTP Port 9019. Response received correctly with no translation. Phase 4-20 check passed.
<08:55:37>: UDP RTP Port 9020. Response received correctly with no translation. Phase 4-21 check passed.
<08:55:37>: UDP RTP Port 9021. Response received correctly with no translation. Phase 4-22 check passed.
<08:55:37>: UDP RTP Port 9022. Response received correctly with no translation. Phase 4-23 check passed.
<08:55:37>: UDP RTP Port 9023. Response received correctly with no translation. Phase 4-24 check passed.
<08:55:37>: UDP RTP Port 9024. Response received correctly with no translation. Phase 4-25 check passed.
<08:55:37>: UDP RTP Port 9025. Response received correctly with no translation. Phase 4-26 check passed.
<08:55:37>: UDP RTP Port 9026. Response received correctly with no translation. Phase 4-27 check passed.
<08:55:37>: UDP RTP Port 9027. Response received correctly with no translation. Phase 4-28 check passed.
<08:55:37>: UDP RTP Port 9028. Response received correctly with no translation. Phase 4-29 check passed.
<08:55:37>: UDP RTP Port 9029. Response received correctly with no translation. Phase 4-30 check passed.
<08:55:37>: UDP RTP Port 9030. Response received correctly with no translation. Phase 4-31 check passed.
<08:55:37>: UDP RTP Port 9031. Response received correctly with no translation. Phase 4-32 check passed.
<08:55:37>: UDP RTP Port 9032. Response received correctly with no translation. Phase 4-33 check passed.
<08:55:37>: UDP RTP Port 9033. Response received correctly with no translation. Phase 4-34 check passed.
<08:55:37>: UDP RTP Port 9034. Response received correctly with no translation. Phase 4-35 check passed.
<08:55:37>: UDP RTP Port 9035. Response received correctly with no translation. Phase 4-36 check passed.
<08:55:37>: UDP RTP Port 9036. Response received correctly with no translation. Phase 4-37 check passed.
<08:55:37>: UDP RTP Port 9037. Response received correctly with no translation. Phase 4-38 check passed.
<08:55:37>: UDP RTP Port 9038. Response received correctly with no translation. Phase 4-39 check passed.
<08:55:37>: UDP RTP Port 9039. Response received correctly with no translation. Phase 4-40 check passed.
<08:55:37>: UDP RTP Port 9040. Response received correctly with no translation. Phase 4-41 check passed.
<08:55:37>: UDP RTP Port 9041. Response received correctly with no translation. Phase 4-42 check passed.
<08:55:37>: UDP RTP Port 9042. Response received correctly with no translation. Phase 4-43 check passed.
<08:55:37>: UDP RTP Port 9043. Response received correctly with no translation. Phase 4-44 check passed.
<08:55:37>: UDP RTP Port 9044. Response received correctly with no translation. Phase 4-45 check passed.
<08:55:37>: UDP RTP Port 9045. Response received correctly with no translation. Phase 4-46 check passed.
<08:55:37>: UDP RTP Port 9046. Response received correctly with no translation. Phase 4-47 check passed.
<08:55:37>: UDP RTP Port 9047. Response received correctly with no translation. Phase 4-48 check passed.
<08:55:37>: UDP RTP Port 9048. Response received correctly with no translation. Phase 4-49 check passed.
<08:55:37>: UDP RTP Port 9049. Response received correctly with no translation. Phase 4-50 check passed.
Application exit code is 0
[/size]
apcomt
New User
 
Posts: 11
Joined: Sat Nov 27, 2010 7:24 pm

Re: PROBLEMAS AL LLAMAR

Postby hg » Mon Dec 13, 2010 7:05 pm

Que tipo de conexion a internet tenes en ambos puntos?
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

Next

Return to Español


Who is online

Users browsing this forum: No registered users and 0 guests

Announcements: