vicidial.org

Updated ssl now required by browsers section has been added to the install walk through on GitHub.

Preface:
---------------------------------------------------------------------------------------------------------------------------------------------------
Needed and Wanted html 5 webphone / WebRTC, not java, not active x, not flash based phone.
Wanted to keep 1.8.29.0-vici asterisk unchanged for performance and stability.
The main purpose for us was to get to a web phone app where agents could nail up voice on login, and not necessarily to use the web phone for general outbound calling, again to use it for the purpose of nailed up voice on agent login.

(since this is a javascript implementation and html 5 this should work theoretically on any device and browser that supports html5 and WebRTC)


Summary of findings and some narrative:
---------------------------------------------------------------------------------------------------------------------------------------------------
Webrtc2sip will act as a gateway to asterisk converting websocket connections and handing off SDP instruction to any version of asterisk.
Asterisk does not need to be modified patched or otherwise changed from a source code perspective. Some adjustments to .conf are helpful.
Upon testing, have not seen an increase in load on the server, no voice degradation.
The key here is don't trans-code. No trans-coding = low load / no load. Use ulaw or you can compile the gateway with g729 if you need to and have g729 compiled and loaded our your vici asterisk flavor.

With the advent of DTLS and SRTP (Forced in the new versions of Chrome and Firefox) - the gateway handshakes these secure protocols with the WEBRTC request, and hands off the SDP to asterisk for a connection and voice delivery.

The settings for the webphone are instructions to let the gateway know where to hand off the SDP.
Again the gateway doesn't need to be installed with any codecs if you are using ulaw, just ssl and srtp

**********************************************************************************************************************************
Version installed and tested with:
ViciBox Redux v.5.0.2-130821 (zypper up && zypper refresh to grab the latest svn during vicibox-install)
1.8.29.0-vici asterisk
(Standard Install)
Install and testing was done to an external ip vicibox with 1 to 1 natting and appropriate iptables firewalling
Tested with latest version of chrome on WinXP
Tested with a Chromebook (fantastic)
***********************************************************************************************************************************

******************************************************************************Ok Enough let's get to the install part******************************
Instructions to setup gateway:

https://github.com/noahseis/webrtc2sip.git

readme_install_walkthrough.txt

In our experience, webRTC is getting better, but ZoiperWeb is still easier and more reliable to adopt across our current client base. I'm sure that within a few years WebRTC phones will be the better option across the board.

Thank you very much for posting your experience in setting this up!

Just a quick update on the progress with this project.

Here's a TOP with Webrtc2sip gateway with 1 agent connected
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
17814 root 20 0 2575m 26m 5652 S 2.7 0.3 23:18.43 webrtc2sip

With 4 agents connected
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
17814 root 20 0 2575m 26m 5652 S 2.3 0.3 23:21.50 webrtc2sip

With 8 agents
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
17814 root 20 0 3015m 28m 5652 S 3.0 0.4 23:58.37 webrtc2sip

Thank you!

So I have done some testing with this as Chrome is going to stop supporting the Zoiper Webphone. I am not sure if this is just my configuration, but I can get it work in Chrome, but there seems to be about a five second delay between when I click answer and when the call connects in Asterisk. The audio passes nicely though. In Firefox the reverse is true. The call seems to answer immediately but there is no audio. IE just doesn't seem to work at all and after trying it in IE i cannot get it to work in any other browser without rebooting.

@Noah. Have you run into these issues? Also is there a way to get the webrtc2sip service to actually log its output somewhere?

Okay found the log. God I hate systemd

Anybody mind if I move this to Support where it appears to belong now?

I'm still unable to make it works. I've tried a few times. I'm able to do the outbound call but no audio.
Have anyone else installed webrtc successfully?
@William, I don't mind if you move this to support.

We got it to the point where it worked most of the time in Chrome, but it was not very reliable and often required reloading Chrome or even rebooting the workstation to get it to work again.

Thank you @mflorell

Happy to report that we have a full live implementation of this working, and extremely reliably--currently supporting close to 100 agents across multiple ViciDial systems without any known issues or problems to report.

Little copypasta:

We now have it implemented where there is a single central web phone for several dialer clients and is currently supporting over 100 concurrent users at any given time
and still maintains great call quality and minimal issues with it being laggy and/or registration. Requires significant tinkering and in 3 or 4 separate implementations we've run into issues and the final stages of setting up are always spent reconfiguring the final pieces.
Our webphone is implemented vertically across the vicidial (screenshot below) where the agent is able to show/hide it. The agent does need to click the "answer" button on the webphone in order to complete registration, but otherwise it can then be hidden (forcefully, if you wish). We notice a lot of agents hide it on their own anyway.

So currently we have the below webphone installed on a single virtual machine (8 vCores, 4GB RAM) and about 4 or 5 different ViciDial installations that point to it to register their extensions & pass the calls.



Let us know if you have any questions! More than happy to help out.
Shameless plug: We provide many Vici implementation and hosting solutions to several clients. Feel free to reach out.

nandotech, hello!
How it works?
Share this solution! This is very curious, really! =)

I tried several times with not luck. I'm waiting for someone else to share, or maybe an add on in the new svn

Anyone try direct connect from sipml5 to the new version of Asterisk 11.22.0-vici?

We've been working on our own WebRTC phone that works natively with Asterisk 11. It's pretty much done at this point, we are just setting up the SSL infrastructure so it can be used publicly(WebRTC has to have SSL on it's web server, SSL on the dialers and SSL on any associated web resources within the same browser page).

Here's a screenshot,

OK: That's cool.

WOW that's awesome ... when it's gonna be available to use ??

We don't have a date yet for public beta users, but we are preparing one of our larger VICIhost clients to try it out later this week.

i bought an ssl certificate for my server but can't find any help on how to install it ... can provide me some help to install my ssl certificate ??

iboam wrote:i bought an ssl certificate for my server but can't find any help on how to install it ... can provide me some help to install my ssl certificate ??

Please do not hijack posts for your own nefarious purposes. This post is about "WebRTC for Vicidial" which is categorically NOT "ssl certificate installation". Besides, that's a simple apache question, unrelated to Vicidial. But at least create a new post for it after checking to see if one already exists.

Later, someone else may require this information. It's doubtful that they would find it in "WebRTC for Vicidial". Make a new post. Put in a suitable subject line. Someone else may benefit from whatever information you get.

Update: Changed project name

I've developed webrtc based webfone and successfully integrated it with latest vicidial.
Code is placed on github https://github.com/chornyitaras/PBXWebPhone
This is ui-less webphone. Phone is based on SIPjs and works in Chrome, Firefox.
Installation steps will be uploaded within next few days.

chornyi_taras wrote:I've developed webrtc based webfone and successfully integrated it with latest vicidial. Code is placed on github https://github.com/chornyitaras/viciphone
This is ui-less webphone. Phone is based on SIPjs and works in Chrome, Firefox. Installation steps will be uploaded within next few days.

Probably a good idea to change the readme.md file to show the full version of Vicibox and Vicidial with which you tested it. Stating "latest" is poor form. LOL
Wouldn't the instructions basically be "copy this to a web folder"? (Probably plus "include phone_login&phone_pass&server_ip in the URL when calling the index.php page)

I'm going to describe full setup including Apache and asterisk SSL config as well as Vicidial system/phones config

I just Installed ... but it does not work ... i already have ssl williamconley helped me, but how may i enable ws ???

Thank you for posting chornyi_taras. But we would request that you change the name of your project to not be confused with the WebRTC phone that we will be releasing shortly. We also have already registered the domains for "viciphone".

Probably best to change it to "DialerWebPhone" which is more generic and avoids the "Vicidial" confusion for "viciphone". Especially since you're not selling it. And I'm pretty sure you'll be able to link it to other dialer systems. You may even want "PBXWebPhone" which is actually available if you want to purchase it.

Ok I'll rename it.

iboam wrote:I just Installed ... but it does not work ... i already have ssl williamconley helped me, but how may i enable ws ???

Check this example https://github.com/chornyitaras/PBXWebPhone/wiki/Asterisk-configuration

Thanks chornyi_taras for your help

chornyi_taras wrote:

iboam wrote:I just Installed ... but it does not work ... i already have ssl williamconley helped me, but how may i enable ws ???

Check this example https://github.com/chornyitaras/PBXWebPhone/wiki/Asterisk-configuration

It's working now but when webphone ring i have no option to take the call ...

i will suggest to add in your tutorial:

If your system requires the certificate and RSA Private key files in .pem format, you can do the following:

1) Download the certificate files (.crt and CA bundle) in your SSL provider account and rename them from .crt and .ca-bundle to .pem ones.

2) As for RSA Private key, it is generated in pair with a CSR. Nor Certificate Authorities have access to your private key. It is generated locally on your server and is never transmitted to anyone.

You can locate it on your server and also rename it from .key to .pem

phone should answer automatically
did you hear standard welcome message(you are the only person ...)?

No, just the ring

I'll just toss a guess in here: He could not answer the phone, no method to do so. Thus there was no sound on the unanswered phone.

Can you please provide asterisk logs ?

Or you can try to check your asterisk configuration using https://www.doubango.org/sipml5/call.htm or https://tryit.jssip.net/

you need to configure your phone
see https://github.com/chornyitaras/PBXWebP ... figuration

i did it before test ...

chornyi_taras wrote:you need to configure your phone
see https://github.com/chornyitaras/PBXWebP ... figuration

by the way i'm getting this error

SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.

can you please provide browser log(press F12 ans select console)?
As I can see from logs you were trying to use sipml5. Did you configure correct WebSocket Server URL in expert mode.? It should look like wss://<your domain>:8089/ws

iboam wrote:SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.

you see this error because you are connecting to ws but not wss.
check your sipml5 configuration in exper mode

This appears to be Chrome
SIPml-api.js?svn=250:1 SIPML5 API version = 2.0.3
call.htm:161 location=https://www.doubango.org/sipml5/call.htm
SIPml-api.js?svn=250:1 'webkitURL' is deprecated. Please use 'URL' instead.


Disable Video: Checked
Enable RTCWeb Breaker: Checked
WebSocket Server URL: wss://domain:8089/ws
Disable 3GPP Early IMS: Checked
Disable debug messages: Checked
Cache the media stream: Checked

uncheck Disable debug messages