IETF Logo Mail Archive

Re: [dispatch] SIP and GSM/UMTS with OpenBTS

Gullik Webjörn <gullik.webjorn@corevalue.se> Fri, 07 February 2014 14:11 UTC

Return-Path: <gullik.webjorn@corevalue.se>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3111D1A1F3D for <dispatch@ietfa.amsl.com>; Fri, 7 Feb 2014 06:11:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Level:
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kevx3c0C1B7R for <dispatch@ietfa.amsl.com>; Fri, 7 Feb 2014 06:11:53 -0800 (PST)
Received: from mailgw8.surf-town.net (mail4.surf-town.net [212.97.132.44]) by ietfa.amsl.com (Postfix) with ESMTP id 93BE11A1F4A for <dispatch@ietf.org>; Fri, 7 Feb 2014 06:11:53 -0800 (PST)
Received: by mailgw8.surf-town.net (Postfix, from userid 65534) id AC906AFC99; Fri, 7 Feb 2014 15:11:52 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by mailgw8.surf-town.net (Postfix) with ESMTP id 9CC5CAFDB1 for <dispatch@ietf.org>; Fri, 7 Feb 2014 15:11:52 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mailgw8.surf-town.net
Received: from mailgw8.surf-town.net ([127.0.0.1]) by localhost (mailgw8.surf-town.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id FIZAQ5QC5tzS for <dispatch@ietf.org>; Fri, 7 Feb 2014 15:11:50 +0100 (CET)
Received: from [192.168.1.102] (78-72-48-131-no186.tbcn.telia.com [78.72.48.131]) (Authenticated sender: gullik.webjorn@corevalue.se) by mailgw8.surf-town.net (Postfix) with ESMTPSA id 20EC7AFC99 for <dispatch@ietf.org>; Fri, 7 Feb 2014 15:11:49 +0100 (CET)
Message-ID: <52F4E9A4.5000203@corevalue.se>
Date: Fri, 07 Feb 2014 15:11:48 +0100
From: Gullik Webjörn <gullik.webjorn@corevalue.se>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: dispatch@ietf.org
References: <040E1A40-BC55-4CFC-834A-FC958DEFDE25@rangenetworks.com> <949EF20990823C4C85C18D59AA11AD8B12A6DE@FR712WXCHMBA11.zeu.alcatel-lucent.com> <60884D2D-1CC8-4A21-97BE-2ACCB49C351D@rangenetworks.com> <7723B448-642F-4138-89DD-379ACC7FA593@rangenetworks.com> <E1FE4C082A89A246A11D7F32A95A17826DFCD495@US70UWXCHMBA02.zam.alcatel-lucent.com> <F5DA260C-32C9-4D92-9169-2026983BFC47@gmail.com> <E1FE4C082A89A246A11D7F32A95A17826DFCD852@US70UWXCHMBA02.zam.alcatel-lucent.com> <77E6DEC0-BCE1-4607-B52C-A4B6761A4B17@gmail.com> <00C069FD01E0324C9FFCADF539701DB3BBF23E22@sc9-ex2k10mb1.corp.yaanatech.com> <CAHBDyN5-O3pNury3RUNzstGHO8NCq6pV3ewHt_Yrxjd1k-if5Q@mail.gmail.com> <948FB37B-F2D4-4462-8B29-D03FDF65215F@rangenetworks.com> <00C069FD01E0324C9FFCADF539701DB3BBF241C5@sc9-ex2k10mb1.corp.yaanatech.com> <AD3958C3-CAA4-44DD-BEEF-0B0F6895F447@westhawk.co.uk>
In-Reply-To: <AD3958C3-CAA4-44DD-BEEF-0B0F6895F447@westhawk.co.uk>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [dispatch] SIP and GSM/UMTS with OpenBTS
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 14:11:56 -0000

On 02/07/2014 01:45 PM, Tim Panton new wrote:
> On 6 Feb 2014, at 02:39, Michael Hammer <michael.hammer@yaanatech.com> wrote:
>
>> Interesting.  But, the 4G/LTE network is an IP internet of sorts.
>> The SIP/IMS components do not need to be in the radio network,
>> and thus not at the locations where the power is constrained.
> One of the nice properties of an openBTS install in a remote location is that it
> can still function as a local 'pbx' at times when the internet link is down. This turns out to
> be fabulously useful in a crisis. If you delegate all the logic out to a cloud service that stops being true.
>
> Tim.
I agree violently, the challenge here is to design the distributed 
protocol(s) add-ons that would enable
building a sip/GSM network out of hundreds or more autonomous BTS's.

Gullik
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

v2.23.0 | Report a Bug | By Email