IETF Logo Mail Archive

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

Tim Panton new <thp@westhawk.co.uk> Mon, 10 February 2014 18:28 UTC

Return-Path: <thp@westhawk.co.uk>
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 513F11A00EE for <dispatch@ietfa.amsl.com>; Mon, 10 Feb 2014 10:28:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 6o5NkxqSl9cv for <dispatch@ietfa.amsl.com>; Mon, 10 Feb 2014 10:28:19 -0800 (PST)
Received: from smtp001.apm-internet.net (smtp001-out.apm-internet.net [85.119.248.222]) by ietfa.amsl.com (Postfix) with ESMTP id 7F89A1A01F1 for <dispatch@ietf.org>; Mon, 10 Feb 2014 10:28:18 -0800 (PST)
Received: (qmail 66311 invoked from network); 10 Feb 2014 18:28:17 -0000
X-AV-Scan: clean
X-APM-Authkey: 83769 18679
Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp001.apm-internet.net with SMTP; 10 Feb 2014 18:28:17 -0000
Received: from zimbra003.verygoodemail.com (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id 4A4A018A03C9; Mon, 10 Feb 2014 18:28:17 +0000 (GMT)
Received: from limit.westhawk.co.uk (limit.westhawk.co.uk [192.67.4.33]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id DBF8C18A0153; Mon, 10 Feb 2014 18:28:16 +0000 (GMT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Tim Panton new <thp@westhawk.co.uk>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B12F6C3@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Date: Mon, 10 Feb 2014 18:28:00 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <2B05935E-EB65-4B36-ABD3-09DE9921F8A7@westhawk.co.uk>
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> <949EF20990823C4C85C18D59AA11AD8B12F6C3@FR712WXCHMBA11.zeu.alcatel-lucent.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1827)
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 18:28:21 -0000

On 10 Feb 2014, at 17:56, DRAGE, Keith (Keith) <keith.drage@alcatel-lucent.com> wrote:

> 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.

I think you are assuming a specific solution to a specific problem. 
Many ITSPs allow SIP  registrations to a DID/account to come from dynamic IPs. So the necessary 'communication' can be 
implemented via the ITSP's normal functions. So when a user moves from the BTS in village A to the BTS  in village B 
their DID travels with them.

Sure you wouldn't get the ability for an arbitrary GSM SIM to roam into the network
and be billed to their home network. 

But realistically that sort of roaming isn't really a technical problem, it is predominantly a legal/commercial one.

Tim.

v2.23.0 | Report a Bug | By Email