Article View: alt.cellular.attws
Article #705Re: ATT MicroCell
From: Todd Allcock
Date: Tue, 25 May 2010 18:43
Date: Tue, 25 May 2010 18:43
38 lines
2766 bytes
2766 bytes
"Boris" <nospam@nospam.com> wrote in message news:Xns9D83708E8D9E6blahblahcom@188.40.43.245... > Dane Jasper <dane@sonic.net> wrote in > news:4bfc0d13$0$1643$742ec2ed@news.sonic.net: >>> 5) I assume that when anyone calls from outside (1 mile away or 2000 >>> miles away, and from ANY? carrier), to any registered Microcell user >>> that it senses is within range of the Microcell, the ATTWS knows to >>> route that incoming call to the internet, so that it can reach the >>> Microcell. Is this correct? >> >> Well, only for AT&T 3G phones that are registered with the device. >> > > Dane, you're not saying that outside callers have to be authorized > microcell users? > > If a Verison user calls, will the call be routed through the internet to > the microcell, to an authorized ATTWS (3G phone) microcell user? > > If yes, does the Verizon caller have to be 3G, or is the 3G requirement > only on the authorized users end? > > Thanks, Dane From the end-user's perspective, the Microcell is just like any other cell tower- calls get routed to your handset when connected to the Microcell just as they would if you were connected to a "real" cell tower. Dane just meant _you_ (the AT&T user receiving the call) had to be using a 3G phone, since Microcells are 3G-only- they don't fall back to 2G like AT&T's real network does. The whole point of the Microcell is that the use of it, once properly set up, is transparent to the user- it's just another cell site you don't have to think about, like all of the other cell sites your phone uses.
Technical Details
Message-ID:
<sTUKn.37556$304.17356@newsfe12.iad>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post01.iad.highwinds-media.com!newsfe12.iad.POSTED!f09e3bc5!not-for-mailReferences:
<Xns9D82742D7AE09blahblahcom@81.169.183.62> <4bfc0d13$0$1643$742ec2ed@news.sonic.net> <Xns9D83708E8D9E6blahblahcom@188.40.43.245>Show Full Headers
Complete Article Headers
X-Google-Thread: aa617e85ca,29bea3e9c8441fc7 X-Google-Attributes: gidaa617e85ca,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post01.iad.highwinds-media.com!newsfe12.iad.POSTED!f09e3bc5!not-for-mail From: "Todd Allcock" <elecconnec@AnoOspamL.com> Newsgroups: alt.cellular.attws,ba.internet References: <Xns9D82742D7AE09blahblahcom@81.169.183.62> <4bfc0d13$0$1643$742ec2ed@news.sonic.net> <Xns9D83708E8D9E6blahblahcom@188.40.43.245> In-Reply-To: <Xns9D83708E8D9E6blahblahcom@188.40.43.245> Subject: Re: ATT MicroCell Lines: 40 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Windows Mail 6.0.6001.18416 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18416 Message-ID: <sTUKn.37556$304.17356@newsfe12.iad> X-Complaints-To: abuse@WWWSpace.NET NNTP-Posting-Date: Tue, 25 May 2010 18:43:36 UTC Date: Tue, 25 May 2010 12:43:24 -0600