similar to: WebRTC - Transport Issues.

hi, i'm fighting with webrtc for 14 days reporting my experience to minimize number of crazy asterisk users i have working webrtc with simpl5 + asterisk 13 + pjproject 2.4.5 + chan_pjsip + secure websockets + secure audio + audio in both ways problems first, i needed run chan_sip for old hard phones and wss with chan_pjsip only for webrtc. this is possible with patch from

Hello, I'm trying to have my first calls with WebRTC. My server has asterisk 13.7.0. I'm following the instructions from the wiki [1]. So I'm using [2] live demo from a Chrome navigator (v48) on Debian Jessie station. Whenever I type something like ws://123.123.123.123:8088/ws in Expert Mode form (see [1]), I'm getting this error : *2:SecurityError: Failed to construct

2016-02-18 14:57 GMT+01:00 Simon Hohberg <simon.hohberg at mcs-datalabs.com>: > > Is it implied here that both HTTPS and WSS must also come from the same >> server (Same Origin Policy) ? >> > No, the same origin policy does not apply to web sockets. > > Then, can I also install my own WebRTC demo page on my own private >> Asterisk server and access this demo

Thank you much for yor reply. 2016-02-18 13:30 GMT+01:00 Simon Hohberg <simon.hohberg at mcs-datalabs.com>: > Hi Oliver, > > On 02/18/2016 12:10 PM, Olivier wrote: > > Hello, > > I'm trying to have my first calls with WebRTC. > My server has asterisk 13.7.0. > > I'm following the instructions from the wiki [1]. > So I'm using [2] live demo from

2016-02-18 15:42 GMT+01:00 Marek ?ervenka <cervajs at fpf.slu.cz>: > my experience with pjsip for webrtc > http://lists.digium.com/pipermail/asterisk-users/2015-September/287562.html > > > Yes I saw this post earlier today. Having to fight 14 days scared me a bit ! Did you set sipml5 on your own server or did you use Live demo (

Is it possible to use serveral protocols for a single transport section in pjsip.con? In sip.conf you could use transport=udp,ws,wss so you cound use webrtc along with your phones but if I try: [transport-udp] type=transport protocol=udp,ws,wss bind=0.0.0.0 I get an error that transport-udp is not found. Do I need a dedicated interface for WebRTC? [Feb 15 12:42:10] ERROR[3308]:

Hello I am trying to set up webRTC video calls from my Chrome webbrowser (Fedora) to my Chrome webbrowser (Windows 10). There is local video input (I can see myself), but never video on the receiving side. This is the case in both directions (so it makes no difference which peer is calling which peer). Both webRTC SIP peers have opus and H264 codec in their peer definition :   Video

hello, i'm facing strange problem asterisk13.5 + chan_sip wss transport + SIPML5 1.5.230 person1 to person3 are behind different NATs audio devices double checked call from person1(chrome) to person2(chrome) works call from person1(chrome) to person 3(chrome) - no audio on both side (RTP flowing only in one direction) call from person2(chrome) to person 3(chrome) - no audio on both side

On 2/15/16 12:50 PM, Joshua Colp wrote: > Carlos Chavez wrote: >> Is it possible to use serveral protocols for a single transport section >> in pjsip.con? In sip.conf you could use transport=udp,ws,wss so you >> cound use webrtc along with your phones but if I try: >> >> [transport-udp] >> type=transport >> protocol=udp,ws,wss >> bind=0.0.0.0 >

I am having trouble getting Google Chrome to accept a WebRTC call coming from Asterisk, even though Firefox can (now) accept the same call without issue. My setup is as follows: Server: CentOS 7 x86_64 (Elastix 4 RC) with IP: 10.1.0.4 192.168.5.146 asterisk-11.21.0 patched to work around https://issues.asterisk.org/jira/browse/ASTERISK-25659 openssl-1.0.1e-51.el7_2.2.x86_64 [root at elx4 ~]#

Hello, I have a problem with a call between 2 webrtc clients. Asterisk removes the ice-related lines from the sdp when it sends the INVITE out, and the called webrtc client rejects the INVITE due to the missing ice lines. Both webrtc clients are defined exactly the same way, same values in all fields except the number of the peer. There's probably something I've changed that causes this

I am using Asterisk 11.3.0 and just updated Nightly to 24.0a1 (2013-06017) and get a SIP 488 Not Acceptable Here response. I have no problems using the same Asterisk configuration and the same page to make a call from Chrome. I have seen other people post a similar issue, but I have not seen a solution. If someone with good knowledge of this issue were to respond with "this is a known

hi, i have following topology PSTN - Asterisk ---- internet -----  router - jssip client (wss) Asterisk 13.29.1 on public IP, chan_pjsip for wss, chan_sip/udp for SIP connection to PSTN router - public IP/private IP (NAT) jssip client - private IP - sip over websocket to Asterisk PJSIP ~30% of calls has problem with no audio. reason is that Asterisk is sending RTP to private IP of jssip

2016-02-19 12:01 GMT+01:00 Marek ?ervenka <cervajs at fpf.slu.cz>: > on my own server > Today, I'm back from holidays trip. First of all, thanks for replying ! I'll try to use jssip as you suggested. Anyway, I'm still failing to understand if wiki's page [1] is still valid with Asterisk 13, and if it's not valid anymore, which is the main change that prevent

Hi Alexey, This is what works for me: [http.conf]: tlsenable=yes ; enable tls - default no. tlsbindaddr=144.x.y.z:8089 ; address and port to bind to - default is bindaddr and port 8089. tlscertfile=/etc/asterisk/keys/mycert.pem ; path to the certificate file (*.pem) only. tlsprivatekey=/etc/asterisk/keys/mycert.pem ; path to private key file (*.pem) only. Date: Tue, 13 Jan

Hello Using Asterisk 12.8.2. I now have the "via ICE" messages in the RTP debug (see below). If you look in the SIP debug (see below), you also now see the "ice-ufrag" and "ice-pwd" in the 200 OK SIP-message from Asterisk to the webRTC client. But still no audio ! None at all ! In both directions. You can see in the SIP debug that the IP-address in de

My main reason not to upgrade to Ast 13 is because I'm afraid of losing functionality as there are certain functions deprecated/replaced. This can also cause headache :-) I will do so if there is no other option. But still, I don't see why Ast 13 would differ so much in this case ? If ICE and NAT is working (not causing problems) why should Ast 13 bring me audio and Ast 12 don't

A while back (last year maybe?), there was a Digium blog post on setting up WebRTC. I was never able to get that working. I was working with Asterisk 15 on a RHEL derived distro and had no idea of where to go to shoot the failure. Has anyone got a tutorial with trouble shooting?

On 04/24/2018 09:08 AM, Matt Fredrickson wrote: > On Tue, Apr 24, 2018 at 10:54 AM, Bruce Ferrell <bferrell at baywinds.org> wrote: >> A while back (last year maybe?), there was a Digium blog post on setting up >> WebRTC. >> >> I was never able to get that working. >> >> I was working with Asterisk 15 on a RHEL derived distro and had no idea of >>

hi, is there someone with working asterisk13+chan_sip+SIP.js/sipml5 ? or is chan_pjsip better supported? or the recommended way for asterisk is use respoke.io? my problem with asterisk13+chan_sip+sipml5(the same problem is with SIP.js) chan_sip.c:10496 process_sdp: Can't provide secure audio requested in SDP offer " sip.conf (important parts) [vr1a882] ... nat=force_rport,comedia