IETF Logo Mail Archive

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

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Mon, 10 February 2014 17:56 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
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 3A48B1A07EB for <dispatch@ietfa.amsl.com>; Mon, 10 Feb 2014 09:56:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
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 atVf4SejpdDB for <dispatch@ietfa.amsl.com>; Mon, 10 Feb 2014 09:56:44 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id 77BA61A0500 for <dispatch@ietf.org>; Mon, 10 Feb 2014 09:56:43 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s1AHufIb025437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 10 Feb 2014 11:56:42 -0600 (CST)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s1AHufSN024746 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 10 Feb 2014 18:56:41 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Mon, 10 Feb 2014 18:56:41 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Jim Forster <jim.forster@rangenetworks.com>, Mary Barnes <mary.ietf.barnes@gmail.com>
Thread-Topic: [dispatch] SIP and GSM/UMTS with OpenBTS
Thread-Index: AQHPIj0OkF9riHfhQ0Se4gDBfVRQX5qmz3RggAAosQCAAAyAAIAAASOQgAA3AICAAALFAIAAAFCAgAAAZICAAAdQgIAALnKAgAZ4SwCAAJlyIA==
Date: Mon, 10 Feb 2014 17:56:40 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B12F6C3@FR712WXCHMBA11.zeu.alcatel-lucent.com>
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> <93B4EA30-0734-439E-A129-B3B91B077720@rangenetworks.com>
In-Reply-To: <93B4EA30-0734-439E-A129-B3B91B077720@rangenetworks.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
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: Mon, 10 Feb 2014 17:56:47 -0000

If I follow this diagram correctly, you claim to have collapsed the HLR into your BTS. Your BTS apparently have no communication shown with each other. This means you each subscriber is limited to a single BTS with no roaming between them.

To sumamrise, this diagram tells us nothing about what you want to do with your architecture, unless you really want no service capabilities at all.

Can you please start answering some of the questions I asked earlier.

Keith Drage
 

> -----Original Message-----
> From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf 
> Of Jim Forster
> Sent: 10 February 2014 04:35
> To: Mary Barnes
> Cc: dispatch@ietf.org
> Subject: Re: [dispatch] SIP and GSM/UMTS with OpenBTS
> 
> On Feb 6, 2014, at 8:46 AM, Jim Forster 
> <jim.forster@rangenetworks.com> wrote:
> 
> >> 
> >> I think it would really help if there were some diagrams 
> showing what IMS protocols are being used.
> > 
> > Well, I can certainly provide some diagrams that show how 
> the system works.
> 
> Much delayed; apologies.  It's a bit simplified, and where it 
> calls out Asterix, one should read "any SIP switching module".
> 
> For those of you that are inclined to read code, it's all 
> available, as well as web site, mailing list, and wiki.  
> OpenBTS.org, openbts-discuss@lists.sourceforge.net, 
> https://wush.net/trac/rangepublic.  We plan on bringing a Dev 
> Kit and can demo somewhere.
> 
> 
>   -- Jim
> 
>

v2.23.0 | Report a Bug | By Email