-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webphone Browser-Phone does not work with letsencrypt certificates #557
Comments
También probé poniendo la central con IP Publica, tampoco funcionó. |
I'm sure that Let's Encrypt certificates work. Here is an example: https://www.innovateasterisk.com/phone/ There must be a config issue. When you say that it does not register, what does it show in the Developer Console? Also, since you say it's not registering, that sounds like the Phone code/UI is loading right? |
Greetings thanks for answering, as I mentioned before with a self-signed certificate for a private IP 192.168.2.60 it worked for me, here is evidence that in the local network (LAN) it worked for me with a self-signed certificate. But now with a real domain it does not work for me, you can look here: https://app.iscotel.com.ve/ En Español: Saludos gracias por contestar, como mencione anteriormente con un certificado autofirmado para una IP privada 192.168.2.60 me funcionó, aqui se evidencia que en la red local (LAN) me funcionó con un certificado autofirmado. Pero ahora con un dominio real no me funciona, puede mirar aquí: https://app.iscotel.com.ve/ |
Here is evidence that in the LAN it worked for me Communication error between Browser-Phone and Linphone. #552 |
Creating User Agent... phone.js:1928:13 |
Your web page works fine, and im able to register my own extension to my own server without a problem. There are two connections to consider, the page that hosts the HTML and javascript that makes up the phone - and then the WebSocket that connects back to Asterisk. Right now your problem is with the WebSocket connection.
You can test the SSL of your connection by using HTTPS and seeing if it can respond with the request to upgrade. The error you want to get off this: Make sure you have correctly referenced the Let's Encrypt PEM file in your Asterisk http.conf file (if you are hosting the WebSocket directly in Asterisk). |
Please can you explain me a little better, I don't understand much what you are telling me: The IP PBX is here ang.iscotel.com.ve This is in the same equipment. Everything is configured with VirtualHost of apache. It is a test equipment, to tune it, to make it work. How should be the expression: wss://domain.com:port/ws Follow my domain and subdomains. |
In the example of the log above, it says:
This means the Browser Phone is attempting to connect to your Asterisk at I can reach https://app.iscotel.com.ve, and I get the browser phone. This page is be served by So far so good, this is correct. Now to solve the WebSocket Connection issue. The URL Are you using Reverse Proxy with Apache for WebSocket forwarding? I would recommend this. Otherwise use port forwarding on port 8089 directly to Asterisk (on whatever port is defined for http TLS) In the end you will either have |
Good afternoon Mr. Conrad, thank you for your great explanation. Following your instructions in the Video Tutorial, I was able to configure the apache VirtualHost with reverse proxy. Already the Browser Phone registers. I can establish a call between the webphone and linphone, but the audio is heard, the voice is not heard. Maybe it is a NAT thing, since the pbx are in the LAN and the webphone being registered from the LAN with public domain goes out and in, goes out to the public area and then enters the private network segment. So it is a codec problem, I will do some other tests. I opened the rtp ports from 10000 to 60000 to test, but I can't hear the audio. Another thing, the call is established for 30 seconds, then hangs, I don't know if this Browser-Phone webphone has any time limitation. EN ESPAÑOL Buenas tardes Señor Conrad, gracias por su magnifica explicación. Siguiendo sus indicaciones del Video Tutorial, pude configurar el VirtualHost de apache con proxy en reversa. Ya el Browser Phone se registra. Puedo establecer una llamada entre el webphone y linphone, pero se se escucha el audio, no se escucha la voz. Puede que sea cosa de NAT, ya que la pbx estan en la LAN y los webphone estando registrados desde la LAN con dominio publico sale y entra, sale al ambito publico y luego entra al segmento de red privado. O sea un problema de codecs, haré algunas otras pruebas. Los puertos rtp los abri desde 10000 hasta 60000 para probar, pero nada que se escucha el audio. |
Webphone Browser-Phone does not work with letsencrypt certificates, please, I appreciate your guidance.
On LAN with self signed certificate it worked, but with letsencrypt certificates it does not work, it does not register.
The asterisk PBX is on the LAN and I am forwarding.
The IP PBX with asterisk has apache server, I installed a wordpress template and also the DNS server.
On the LAN it works, but with Letsencrypt it does not work.
The Asterisk IP PBX has FreePBX installed to manage it, I am using only PJSIP.
I am using VirtualHost in apache and several subdomains in the domain certificate creation and all those subdomains are configured in the DNS server.
En español
Webphone Browser-Phone no funciona con certificados letsencrypt, por favor, agradezco una orientación.
En la LAN con certificado autofirmado funcionó, pero con certificados letsencrypt no funciona, no se registra.
La central asterisk esta en la LAN y estoy haciendo forwarding.
La central IP con asterisk tiene server apache, instale una plantilla de wordpress y también esta el servidor DNS.
En la LAN funciona, pero con Letsencrypt no funciona.
La central IP Asterisk tiene instalado FreePBX para gestionar la misma, estoy usando solo PJSIP.
Estoy usando VirtualHost en apache y varios subdominios en la creacion del certificado del dominio y todos esos subdominios estan configurados en el servidor DNS.
Por favor alguna orientación.
The text was updated successfully, but these errors were encountered: