InnovateAsterisk / Browser-Phone

A fully featured browser based WebRTC SIP phone for Asterisk
https://www.innovateasterisk.com
GNU Affero General Public License v3.0
499 stars 245 forks source link

WebPhone index.php not open #466

Open ali-matrix22 opened 1 year ago

ali-matrix22 commented 1 year ago

Hello and thank you for your good software. I installed the Webphone software according to your installation procedure on two Isabel servers and it was installed without any problems. But when I open the website address (https://192.168.1.100/webphone), I get the following message:

Thank you for choosing ViciPhone. In order to use ViciPhone you must use "https://phone1.viciphone.com/viciphone.php" as your Webphone URL. If you are using ViciPhone in conjunction with Vicidial you will need to change this setting in ADMIN → System Settings.

please guide me.

InnovateAsterisk commented 1 year ago

This is not ViciPhone though.

The default configuration is /phone/

ali-matrix22 commented 1 year ago

I install with this command:

yum install git -y git clone https://github.com/innovateAsterisk/Browser-Phone.git cp Browser-Phone/Phone /var/www/html/webphone

InnovateAsterisk commented 1 year ago

Try https://192.168.1.100/webphone/Phone/

ali-matrix22 commented 1 year ago

not work...

ali-matrix22 commented 1 year ago

I install new issabel with asterisk 18 and pjsip. This time, the web page of Webphone opened easily and without any problems. But after defining the webrtc number and entering the account configuration, my webphone is not registered and gives the following error message: Connecting to Web Socket... I have attached the error image. Untitled

Also, there is no firewall in the system and the web socket is active. TLS is also set correctly. Untitled2

InnovateAsterisk commented 1 year ago

I see you are connecting with an ip address. The problem is that modern browsers don’t allow you to connect to a websocket over TLS without the server responding with a valid SSL certificate, and since a certificate can only be made from a fully qualified url, you will have to make a certificate and install this on the server.

Because you appear to be working over a local lan, it would be easier use the .local system. Most Linux system can advertise a .local host name to make the certificate from.

InnovateAsterisk commented 1 year ago

Also you could trace the websocket handshake with something like wire shark to confirm this.

ali-matrix22 commented 1 year ago

Thanks for the explanation. Yes, I use this server in a local network, so I have to set a domain and then test.