No salen llamadas con SPA-3102

[anonymous]

Hola!
Se que este tema ha sido tratado muchas veces en este foro, pero no he encontrado solución al problema que tengo yo.
Tengo una central configurada con varias extensiones y un gateway SPA-3102 que recibe la linea PSTN de mi empresa. Desde la que se recibem sin ningún problema las lamadas entrantes las cuales son direccionadas a una recepcionista digital y luego segun elija la persona que llama al interno que corresponda. Hasta aqui no hay problema.

El problema aparece a la hora de realizar llamadas. He creado una regla de salida indicando que las llamadas que empiecen con el prefijo 9 salgan por la ruta linea1 y remueva el primer digito.

En fin la llamada no logra salir a la red pública y el error del sistema es el siguiente...


17:00:16.764 [CM503008]: Call(26): Call is terminated

17:00:16.764 [CM503015]: Call(26): Attempt to reach failed. Reason: No Answer

17:00:16.764 [CM503003]: Call(26): Call to sip:[email protected]:5060 has failed; Cause: 408 Request Timeout; internal

16:59:44.592 [CM503024]: Call(26): Calling PSTNline:52913097@(Ln.10001@linea1)@[Dev:sip:[email protected]:5062]

16:59:44.592 [CM503004]: Call(26): Route 1: PSTNline:52913097@(Ln.10001@linea1)@[Dev:sip:[email protected]:5062]

16:59:44.577 [CM503010]: Making route(s) to

16:59:44.561 [CM505001]: Ext.100: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/PAP2-3.1.8(LS)] Transport: [sip:192.168.0.102:5060]


Agradecería su ayuda a resolver el problema! ya no se que probar!

Saludos!

 

[aesteve]

Si le dices a la centralita que te quite el primer dígito, te está quitando el 9 con lo que al número que estás marcando le falta ése dígito.

Dile que no elimine ningún dígito si es que el fijo empieza por 9.

 

[anonymous]

Pero el numero que deseo que marque es sin el 9, el 9 solo lo coloco para que la central diferencie las llamadas a la red externa de las internas... sino como es que lo sabe si no se coloca ningún dígito adelante?
De todas maneras intenté lo que me sugieres y tuve el mismo resultado!

muchas gracias de todas formas.

 

[aesteve]

Entonces debes crear una regla de salida que diga que los números que comiencen por el número que tú quieres, salgan por la SPA.

 

[anonymous]

He creado la regla de salida de esta forma pero tampoco funciona, puede ser posible que sea una mala configuración del SPA... aunque recibo las llamadas bien.

Saluodos!

 

[aesteve]

Vamos a ver.

¿ Por qué número empiezan los números a los que quieres llamar ?

 

[anonymous]

hola! nuevamente.

supongamos que yo quiero llamar al 4348 8000 y al 5291 5291 o al 0800 122 4652... (tal cual como se los debe discar)
todos esos numeros empiezan distinto... por lo que yo habia pensado agregar al llamar un 9

marcaría entonces en los telefonos 943488000 o 952915291 o 908001224652
y le pido que elimine el numero 9 de adelante... eso es lo que yo creí haber hecho con la regla de llamadas que cree.

no se si voy bien encaminado hasta aqui! (?)

 

[aesteve]

Hola,

hasta ahí vas bien. Ahora has de crear otra regla para cada el primer dígito de cada uno de los números que quieres que salgan.

Por ejemplo para llamar al 4348 8000, debe haber una regla que indique, que todos los número que comiencen por 4 salgan por "el sitio que elijas" y así con el resto de números.
Sino la centralita no sabe hacia donde encaminar esos números.

Un saludo.

 

[anonymous]

Hola Alejandro,

Para evitar tener que crear una regla de salida por cada uno de los numeros pense que sería mas util agregarle un digito al azar, el cual determiné como 9. para poder identificar las llamadas externas, entonces antes de marcar debo pensar en argregar el numero nueve luego la central lo elimina y marca solo los numeros que le siguen...

Esto me lleva a pensar luego de leer todo lo que me dices, que no se debe a un problema con la regla de salida. Sino quizas un problema de configuracion del SPA, puede ser quizas del "tono de llamada" o "dial tone"... ???

Saludos!

 

[aesteve]

Hola, ok, no te entendí bien. Ahora ya lo tengo claro. Me lié con el 9 ya que los núermos en España empiezan por 9. Yo tengo puesto un 0 y cuando marco 0 salgo por VoIP. Ahora ya lo entiendo.

La SPA la has configurado siguiendo esto ?

http: //www.3cx.com/voip-gateways/linksys-spa3102/

Un saludo.

 

[anonymous]

Hola Alejandro,

si, he configurado el SPA con esa guia...
pero... lo único que he desobedecido fue el paso 13.

"13.Click on the "Line 1" node and set the "Line Enable" to "No". "

ese campo esta en Yes puesto que utilizo el SPA como el interno 105.

Tambien leo que dice...

Note: The Linksys SPA3102 can either be set as a gateway OR as an ATA device. 3CX does not support the device when configured in both modes simultaneously.

Por lo que entiendo, no puedo utilizar el spa3102 para recibir una linea pstn y como interno al mismo tiempo.

esto es así?

Saludos!

 

[anonymous]

Bueno, he intentado deshabilitando la opción Line 1. Pero de todas maneras sigue sin permitirme las salidas externas...

 

[aesteve]

La SPA3102, funciona como pasarela para hacer y recibir llamadas a través de cualquier extensión, pero también le puedes conectar un teléfono convencional y que éste forme parte del grupo de extensiones. Ambas cosas se pueden hacer a la vez.

 

[anonymous]

Bueno, pues recibir llamadas y hacer llamadas internas funciona bien, pero hacer llamadas externas no! Esta creciéndome pelo verde por la ira.
Me pregunto si será algo relacionado con el tono de marcado de mi compañia telefónica? Leí en algún foro que la SPA no envia el numero a marcar hasta que no oye el tono de marcado. Quizas no este correctamente configurado.

 

[aesteve]

En qué país estás ? O desde que país quiere que sea el código de marcación ?

 

[anonymous]

Yo estoy en Argentina. Pero no es tono habitual de Argentina puesto que uso Telmex y tienen un tono de marcado distinto al que figura para el de este pais. El mismo se escucha exactamente igual que el tono de la central o el de la SPA.

 

[hanllenicolas]

La regla de salida parece estar aplicandola bien segun los Logs asi queda descartado sea por una mala regla, sin embargo envianos unos actuales, segun entiendo posees un linea analoga conectada a un SPA pero no logras sacar llamadas, tambien veo un timeout, desde donde estas intentando hacerlo ?..softphone, ?, me inclino a el SPA, si lo estas usando como router por favor deshabilita las funcionalidades de router, dejalo trabajando solo como pasarela a la PSTN.

Envianos screenshots, Logs, de tu configuracion tanto SPA como central.


Saludos.

 

[anonymous]

Hola!

Este seríael log de la central despues de un intento de realizar una llamada externa desde el interno 105 que es un telefono analógico inálambrico conectado al mismo SPA que recibe la linea entrante analógica.

Tambien hay otro intento de llamado que hice desde la extencion 101 que utiliza el softphone de 3cx, pero parecería que el resultado es el mismo.

He cambiado la regla de salida para que llame con el numero "0" adelante puesto que vi en la consola Opciones avanzado solapa "custom parameters" que en en el campo PEC "prefix for external call" dice "0" y me parecio que logicamente debería coincidir...


12:55:22.925 [CM503008]: Call(252): Call is terminated

12:55:22.909 [CM503015]: Call(252): Attempt to reach failed. Reason: Not Found

12:55:22.909 [CM503003]: Call(252): Call to sip:[email protected]:5060 has failed; Cause: 404 Not Found; from IP:192.168.0.101:5060

12:55:22.831 [CM503016]: Call(252): Target is not registered: PSTNline:52913097 dialed on (AnyLine@Linea 1)

12:55:22.831 [CM303003]: There are no available outbound lines on gateway Linea 1 at this time.

12:55:22.831 [CM503016]: Call(252): Target is not registered: PSTNline:52913097 dialed on (AnyLine@Linea 1)

12:55:22.831 [CM303003]: There are no available outbound lines on gateway Linea 1 at this time.

12:55:22.831 [CM503024]: Call(252): Calling PSTNline:52913097@(Ln.10001@Linea 1)@[Dev:sip:[email protected]:5062]

12:55:22.831 [CM503004]: Call(252): Route 1: PSTNline:52913097@(Ln.10001@Linea 1)@[Dev:sip:[email protected]:5062]

12:55:22.816 [CM503010]: Making route(s) to

12:55:22.816 [CM505001]: Ext.101: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CXVoipPhone;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 3.1.8571.0] Transport: [sip:192.168.0.102:5060]

12:55:22.800 [CM503001]: Call(252): Incoming call from Ext.101 to

12:49:00.507 [CM503008]: Call(251): Call is terminated

12:49:00.507 [CM503015]: Call(251): Attempt to reach failed. Reason: Not Found

12:49:00.491 [CM503003]: Call(251): Call to sip:[email protected]:5060 has failed; Cause: 404 Not Found; from IP:192.168.0.101:5060

12:49:00.429 [CM503016]: Call(251): Target is not registered: PSTNline:52913097 dialed on (AnyLine@Linea 1)

12:49:00.429 [CM303003]: There are no available outbound lines on gateway Linea 1 at this time.

12:49:00.429 [CM503016]: Call(251): Target is not registered: PSTNline:52913097 dialed on (AnyLine@Linea 1)

12:49:00.429 [CM303003]: There are no available outbound lines on gateway Linea 1 at this time.

12:49:00.429 [CM503024]: Call(251): Calling PSTNline:52913097@(Ln.10001@Linea 1)@[Dev:sip:[email protected]:5062]

12:49:00.413 [CM503004]: Call(251): Route 1: PSTNline:52913097@(Ln.10001@Linea 1)@[Dev:sip:[email protected]:5062]

12:49:00.413 [CM503010]: Making route(s) to

12:49:00.413 [CM505001]: Ext.105: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA3102-3.3.6(GW)] Transport: [sip:192.168.0.102:5060]

12:49:00.398 [CM503001]: Call(251): Incoming call from Ext.105 to

12:45:39.136 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

12:41:03.326 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

12:21:01.973 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

12:17:56.610 IP(s) added:[192.168.0.102]

12:17:46.548 IP(s) removed:[192.168.0.102]

12:16:13.985 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

12:01:14.923 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

11:46:29.766 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

11:41:13.079 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

11:21:09.626 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

11:16:45.532 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

11:01:06.032 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

10:55:34.798 [CM504002]: Ext.101: a contact is unregistered. Contact(s): [sip:[email protected]:53606;rinstance=b0d0ed224c2f2c11/101]

10:47:01.313 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

10:41:03.079 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

10:35:35.095 [CM504001]: Ext.101: new contact is registered. Contact(s): [sip:[email protected]:53606;rinstance=b0d0ed224c2f2c11/101, sip:[email protected]:57830;rinstance=235107e86cddfe63/101]

10:25:22.845 [CM504001]: Ext.101: new contact is registered. Contact(s): [sip:[email protected]:57830;rinstance=235107e86cddfe63/101]

10:21:01.032 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

10:17:17.095 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

10:00:57.923 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

09:47:32.860 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

09:40:55.938 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

09:20:54.735 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

09:17:48.626 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

09:00:51.704 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

08:48:04.376 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

08:40:48.923 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

08:20:46.704 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

08:18:20.141 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

08:00:44.266 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

07:48:35.907 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

07:40:42.220 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

07:20:40.329 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

07:18:51.673 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

07:00:40.126 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

06:49:07.438 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

06:40:39.923 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

06:20:39.704 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

06:19:23.204 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

06:00:39.454 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

05:49:39.016 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

05:40:39.345 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

05:20:36.751 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

05:19:54.516 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

05:00:36.407 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

04:50:10.266 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

04:40:36.095 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

04:20:35.970 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

04:20:26.032 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

04:00:34.860 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

03:50:41.813 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

03:40:34.735 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

03:20:57.579 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

03:20:33.157 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

03:00:31.954 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

02:51:13.345 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

02:40:31.798 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

02:21:29.126 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

02:20:31.657 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

02:00:30.454 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

01:51:44.891 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

01:40:28.298 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

01:22:00.673 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

01:20:27.095 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

01:00:24.970 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

00:52:16.438 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

00:40:22.282 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

00:22:32.220 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

00:20:20.360 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

00:00:18.220 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

23:52:48.001 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

23:40:16.204 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

23:23:03.766 [CM504001]: Ext.105: new contact is registered. Contact(s): [sip:[email protected]:5060/105]

23:20:13.345 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

23:00:10.220 [CM506001]: STUN request to resolve SIP external IPort mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.102:5060

 

[anonymous]

Lets see

 

[aesteve]

Hola,

puede parecerte una tontería, pero los cables como los tienes ?.

En Ethernet no hay que pinchar nada, y en WAN ha de ir al router o al switch.

Si lo tienes así ¿ tienes los 4 leds encendidos ?

Un saludo.