For people who reported problems calling Chrome Canary: This was an
issue in Chrome (
https://groups.google.com/group/discuss-webrtc/
browse_frm/thread/706126a5b1019387) and has been fixed:
http://code.google.com/p/webrtc/issues/detail?id=717
The fix will be part of the next Canary release.
For testing, I recommend using Chrome 21.0.1180.60 m (https://
www.google.com/intl/en/chrome/browser/)
On Aug 2, 5:26 pm, James Mortensen <
james.morten...@a-cti.com> wrote:
> Hi Varun,
>
> I think you missed the point of the problem that the WebRtc4All plugin is
> trying to solve. This merely implements the PeerConnection API inside
> Safari, Firefox, Opera, and Internet Explorer so that you can begin
> building applications that run on this platform *today* and be ready to go
> into production once the browsers catch up.
>
> I don't think this plugin is actually intended for production but merely
> for testing as-if the browsers actually implemented the official
> PeerConnection API.
>
> Marmadou, with that said, the last thing you're missing is the OSX and Unix
> support, but you knew that already. I'm on Ubuntu 11.04 64 bit, so a Unix
> version of this would be awesome ;) Thank you for your work on this!
>
> James
>
>
>
>
>
>
>
> On Wednesday, August 1, 2012 8:06:14 PM UTC-7, Varun wrote:
>
> > HI
>
> > It lacks two things for the feedback what I think:
>
> > 1) Documentation where to start and how to do?
> > 2) The WenRTC4all is 8.8 MB installer. I think when end user wants to use
> > our websoftphone for calling then first he have to install this 8.8 MB on
> > that system. That loses some web experience as it is better to install the
> > PC Softphone like Xlite then to install the 8.8 MB.
>
> > Regards
> > Varun
>