| 01:17.03 | *** join/#asterisk-dev kpfleming (~kpfleming@unaffiliated/kpfleming) |
| 01:17.03 | *** mode/#asterisk-dev [+o kpfleming] by ChanServ |
| 01:27.49 | *** join/#asterisk-dev luckman212_ (~irc@2001:470:8abb:0:4cb5:ce24:38d4:da24) |
| 01:28.09 | *** join/#asterisk-dev luckman212__ (~irc@2001:470:8abb:0:dc71:d10e:5b7e:4865) |
| 01:59.26 | *** join/#asterisk-dev zerohalo (~zerohalo@74.61.196.236) |
| 09:45.04 | *** join/#asterisk-dev sezuan (bouncer@irc.scheff32.de) |
| 11:32.16 | *** join/#asterisk-dev kpfleming (~kpfleming@unaffiliated/kpfleming) |
| 11:32.16 | *** mode/#asterisk-dev [+o kpfleming] by ChanServ |
| 11:50.02 | *** join/#asterisk-dev hehol (~Adium@2a01:198:71d:0:21f:d0ff:fea1:568e) |
| 13:42.30 | *** join/#asterisk-dev hehol (~Adium@ip-178-202-243-147.unitymediagroup.de) |
| 14:17.44 | *** join/#asterisk-dev rethus (~suther@p54BBC95D.dip.t-dialin.net) |
| 14:19.29 | rethus | hi @ all. |
| 14:20.36 | rethus | i've read, asteris11 hae webrtc support?! |
| 14:21.03 | rethus | does this means, i need no additional websocket-server on my server where asterisk runs, to fire ami to * |
| 14:45.34 | kpfleming | WebRTC and AMI are completely unrelated |
| 14:46.08 | kpfleming | Asterisk 11 has a WebSocket server, and supports SIP over WebSocket |
| 14:46.54 | kpfleming | so if you use a SIP over WebSocket client (like sipml5 or js-sip), then yes, it can talk directly to asterisk, there is no need for any additional websocket server |
| 15:08.13 | rethus | <PROTECTED> |
| 15:08.28 | rethus | how far are the development on webrtc? is it usable in beta? |
| 15:08.49 | rethus | .....can talk directly to asterisk, there is no need for any additional websocket server |
| 15:08.54 | rethus | thats sounds realy realy great |
| 15:09.11 | rethus | before i had used AsterClick, but at the and, it realy sucks |
| 15:10.03 | rethus | kpfleming: are there some tiny howto outside, how to configure asterisk11 for first webrtc-testrun? |
| 15:12.56 | kpfleming | not yet |
| 15:14.40 | kpfleming | yes it is usable in the beta although the available browsers still have some problems |
| 15:15.16 | rethus | could you recommend me a browser to run some beta-tests for it |
| 15:15.40 | rethus | means: which one has less problems with rtc? |
| 15:15.50 | kpfleming | chrome is the only one but it does not completely work yet |
| 15:15.58 | rethus | k. |
| 15:16.11 | rethus | now i have install asterisk11 and srtc-utils on my debian-system. |
| 15:16.19 | rethus | have you some hints, what are the next steps? |
| 15:16.22 | kpfleming | ni |
| 15:16.24 | kpfleming | no |
| 15:17.03 | kpfleming | ask on the asterisk-dev mailing list |
| 15:17.16 | rethus | k, thanks a lot. |
| 15:17.40 | rethus | does there a roadmap, when webrtc comes to stablee |
| 15:18.17 | kpfleming | you'd have to check the IETF and W3C RTC working groups, there is a lot of work still going on |
| 15:18.46 | rethus | k, thanks |
| 15:20.19 | *** part/#asterisk-dev rethus (~suther@p54BBC95D.dip.t-dialin.net) |
| 17:24.14 | *** join/#asterisk-dev sruffell (~sruffell@asterisk/the-kernel-guy/sruffell) |
| 17:24.15 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |