IETF Logo Mail Archive

Re: [rtcweb] Media forking solution for SIP interoperability (without a media gateway)

Iñaki Baz Castillo <ibc@aliax.net> Sun, 30 October 2011 19:41 UTC

Return-Path: <ibc@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 BB37D21F8B16 for <rtcweb@ietfa.amsl.com>; Sun, 30 Oct 2011 12:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.645
X-Spam-Level:
X-Spam-Status: No, score=-2.645 tagged_above=-999 required=5 tests=[AWL=0.032, 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 LoFxX95WELPD for <rtcweb@ietfa.amsl.com>; Sun, 30 Oct 2011 12:41:32 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id DB13221F8B09 for <rtcweb@ietf.org>; Sun, 30 Oct 2011 12:41:31 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so5264921vcb.31 for <rtcweb@ietf.org>; Sun, 30 Oct 2011 12:41:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.1.196 with SMTP id 4mr1633580vcg.268.1320003691258; Sun, 30 Oct 2011 12:41:31 -0700 (PDT)
Received: by 10.220.184.6 with HTTP; Sun, 30 Oct 2011 12:41:31 -0700 (PDT)
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A058522357895FA@ESESSCMS0356.eemea.ericsson.se>
References: <CALiegfkikmpi55ePUo=AQCQvorv4_6v2ByTCdL=V_=umcCEpUA@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05852235717390@ESESSCMS0356.eemea.ericsson.se> <CALiegf=t=9YSbZ1fmCQs0BrV79TPAkXB5XEsONRA4KP_um4DtA@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A058522357895FA@ESESSCMS0356.eemea.ericsson.se>
Date: Sun, 30 Oct 2011 20:41:31 +0100
Message-ID: <CALiegfnDsP8Y19tUKifdG8vJ552ivY+1f6+e8JEQCyrFoZF9KQ@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Media forking solution for SIP interoperability (without a media gateway)
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: Sun, 30 Oct 2011 19:41:32 -0000

2011/10/30 Christer Holmberg <christer.holmberg@ericsson.com>:
>> I don't agree. If the UAC receives a 180 it means that the 180 has been received (regardless it was
>> unreliable), so UPDATE is possible.
>
> Ok, small correction: you are not allowed to send a new offer before you have received the previous answer in a reliably sent response :)

Ok, PRACK (RFC 3262) dates from 2002, so just add "Require: 100rel" in
the INVITE and you are done. Of course, if the remote SIP peer does
not implement PRACK I am sure it won't implement ICE and SRTP, so
interoperability with a WebRTC client is not possible anyway.

Anyhow, let's remember that the purpose of WebRTC is not the
interoperability with old SIP phones which implement nothing but plain
SIP and plain RTP. So I don't expect that WebRTC will allow reusing
the same local candidates in a new PeerConnection just to allow SIP
media forking.

Regards.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email