Re: [rtcweb] Future requirement: RTC-Web apps must work through interface switching

"Olle E. Johansson" <> Mon, 03 October 2011 12:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2307521F8B24 for <>; Mon, 3 Oct 2011 05:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.786
X-Spam-Status: No, score=-1.786 tagged_above=-999 required=5 tests=[AWL=-0.437, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_24=0.6, MIME_8BIT_HEADER=0.3]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id aLZqpDiLBq+d for <>; Mon, 3 Oct 2011 05:30:26 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 2BC0121F8B27 for <>; Mon, 3 Oct 2011 05:30:26 -0700 (PDT)
Received: from [] ( []) by (Postfix) with ESMTPA id E4ACF754BD0D; Mon, 3 Oct 2011 12:33:22 +0000 (UTC)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=iso-8859-1
From: "Olle E. Johansson" <>
In-Reply-To: <>
Date: Mon, 3 Oct 2011 14:33:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <>
X-Mailer: Apple Mail (2.1244.3)
Subject: Re: [rtcweb] Future requirement: RTC-Web apps must work through interface switching
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 03 Oct 2011 12:30:27 -0000

3 okt 2011 kl. 14:29 skrev Iñaki Baz Castillo:

> 2011/10/3 Olle E. Johansson <>et>:
>> THe SIP outbound extension has handling of IP address change during a registration/connection. But that doesn't imply IP address change during a call.
> When a SIP client implementing the outbound extension (RFC 5626)
> detects that the TCP (or TLS or WebSocket) connection is
> terminated/down, it should re-register and should send a re-INVITE for
> established dialogs telling the peer about its new location and SDP
> address. In fact, the using RFC 5626 the client does not need to know
> its exact local IP:port, as the edge proxy would route back incoming
> in-dialog request using the new client connection.
Over UDP the client recognizes a new binding using STUN and determines that the connection has failed
and re-initializes.

>> Software like Asterisk has added protection on the RTP ports so after initial packets (handling symmetric RTP) Asterisk will not accept packets from an unknown IP.
> It should allow a change in the source IP:port of the RTP packets in
> case a re-INVITE has been sent by the peer.
Always. Of course. But previously we always accepted it...
>> I would assume that if we had ICE support, ICE could re-initialize the session and the server could open new connections.
> I expect this to be the same: the client would send a re-INVITE after
> detecting local address change and Asterisk should accept it and
> update the session information.