IETF Logo Mail Archive

[rtcweb] SIP on the Web: presentation and video

José Luis Millán <jmillan@aliax.net> Tue, 11 October 2011 06:28 UTC

Return-Path: <jmillan@aliax.net>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6D121F86EE for <rtcweb@ietfa.amsl.com>; Mon, 10 Oct 2011 23:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level:
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YLG+TqOSOEZC for <rtcweb@ietfa.amsl.com>; Mon, 10 Oct 2011 23:28:49 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5410A21F8753 for <rtcweb@ietf.org>; Mon, 10 Oct 2011 23:28:49 -0700 (PDT)
Received: by iaby26 with SMTP id y26so10137180iab.31 for <rtcweb@ietf.org>; Mon, 10 Oct 2011 23:28:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.5.73 with SMTP id 9mr7794832ibu.60.1318314528714; Mon, 10 Oct 2011 23:28:48 -0700 (PDT)
Received: by 10.231.36.201 with HTTP; Mon, 10 Oct 2011 23:28:48 -0700 (PDT)
Date: Tue, 11 Oct 2011 08:28:48 +0200
Message-ID: <CABw3bnMESQO=SUvgQFJPxipBNV3tv9gof7JswjEJ919LyoskHw@mail.gmail.com>
From: José Luis Millán <jmillan@aliax.net>
To: rtcweb@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: [rtcweb] SIP on the Web: presentation and video
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Oct 2011 06:28:50 -0000

Hi,

Some weeks ago we made a concrete proposal for signalling between Web
browser and server in RTCweb. Such a definition was described in
"draft-ibc-rtcweb-sip-websocket-00".

We don't advocate for a default signaling protocol in RTCweb (not at all).
Current proposal is just an example of a working signaling for RTCweb based
on SIP and carried over WebSocket.

We have just uploaded a video demo in which there can be seen a real
implementation of the mentioned draft.

The components of the signalling architecture are a WebSocket capable
SIP proxy and a SIP stack written in JavaScript. These are needed to
make the browser became a real SIP node, capable to interact with real
SIP World.

We would like to emphasize that the aim of this video is nothing but
showing an implementation of the proposed signalling.


We wish you enjoy.

http://sip-on-the-web.aliax.net.

Regards.



Iñaki Baz <ibc@aliax.net>
José Luis Millán <jmillan@aliax.net>

v2.23.0 | Report a Bug | By Email