3CX STUN Problems

[vaecom]

Buenas tardes,

Venimos experimentando problemas con una instancia de 3CX instalada en local.

Tenemos la instancia instalada en un Datacenter, y los teléfonos tras una conexión FTTH en otro lugar.

El problema viene en realizar ciertas acciones como transferir llamadas entrantes a otras extensiones de 3CX, así como ciertas ocasiones en las que no se escucha al interlocutor y demás problemas.

Hemos revisado el registro de eventos de la PBX y no hemos encontrado ningún problema / nada extraño. También hemos revisado las conexiones en ambos routers y no vemos que se quede nada colgado, ni que haya ningún problema en la red. En el firewall checker de 3CX aparece todo correctamente.

¿Alguna sugerencia sobre el posible error? Pensamos que podría ser fallo de comunicación.

Saludos y muchas gracias.

 

[NicholasP_3CX]

Translation.

Good afternoon,

We have been experiencing problems with a locally installed 3CX instance. We have the instance installed in a Datacenter, and the phones behind an FTTH connection in another place.

The problem comes in performing certain actions such as transferring incoming calls to other 3CX extensions, as well as certain occasions in which the caller is not heard and other problems.

We have checked the PBX event log and have not found any problems/nothing strange. We have also checked the connections on both routers and we do not see anything hanging or any network problems. In the 3CX firewall checker everything appears correctly.

Any suggestions on the possible error? We think it could be communication failure.

Greetings and thank you very much.

 

[NicholasP_3CX]

Please provide the following information when asking for assistance. Please also note that assistance in this forum should be in English. We also provide a Spanish forum for your convenience.

https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[vaecom]

Good afternoon,

Here is the information,

• 3CX Version, Standard Annual 18.0 (Build 461)
• Server OS, Debian 9
• Is the 3CX Server Hosted and where? On-premises
• IP Phone Make/Model/Firmware version, GrandStream GRP2613 version 1.0.5.93 / GXP2170 1.0.11.35
• Provisioning Method: STUN
• Trunk Provider or VoIP Gateway Make/Model, AireNetworks
• Has the Firewall Checker passed: Yes
• Are custom Phone Templates being used: No

I hope this is what you were asking for. If not, tell me please.

Best Regards,

 

[NicholasP_3CX]

• Provisioning Method: STUN

This is most probably where your problem is.

Please ensure the following:

For every phone at this site, you will need to have DIFFERENT ports for EACH phone.

Phone 1:



Phone 2:



These ports will need to be forwarded on your remote firewall where all the phones are to each individual telephone. If you have 20 phones at this site, you will need to forward 20 sets of ports to each device!

To enable proper communication, either configure the ports properly on the PBX for each device at the location, and then port forward on the remote firewall.

OR the alternative is to use the 3CX SBC and have 0 firewall configuration necessary.

 

[vaecom]

Hi Nicholas,

Thak you for your answer, but after reviewing it, ans changing the ports in the phones with the same RTP Audio Ports, it is still happening the same.

When the call needs to be transfered, in the 3CX PBX it is showing correctly the call being transfered, but the person in the receiving phone cannot answer.

The error that appears in the register:



Thank you in advance.

 

[NicholasP_3CX]

Have you forwarded the ports on your remote firewall to the IP Phones? Just changing the ports in the PBX is not enough.

Also, each IP Phone should have its own range of audio ports, and individual SIP Port.

 

[Saqqara]

If the phones are at the same location, and support SBC server, install a SBC it will make your life so much easier

 

[vaecom]

Hi,

Yes, the ports are also forwarded on the remote firewall to the private IP Address of each IP Phone.

As I told in the previous message, each IP Phone has its own SIP and RTP unique ports.

Could it be another type of problems?