Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mailrus!accuvax.nwu.edu!nucsrl!telecom-request
From: doug@letni.lonestar.org (Doug Davis)
Newsgroups: comp.dcom.telecom
Subject: Re: My Trip to Kansas
Message-ID: <9537@accuvax.nwu.edu>
Date: 9 Jul 90 18:37:00 GMT
Sender: news@accuvax.nwu.edu
Organization: Logic Process, Dallas Tx
Lines: 25
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 470, Message 9 of 10


In article <9507@accuvax.nwu.edu> TELECOM Moderator writes:

>On the way back everything worked fine, except
>that on a few occasions when between carrier areas, the roaming light
>(as opposed to 'no service' light) would come on, leading me to
>believe there was service at that point when there was not.

This is usually due to a phone being programmed to scan the b and a
carriers, sometimes they mistakenly lock on a (insert opposing
carrier)'s signal and roam to it.  The solution is to program your
phone to only scan the correct ( b [wireline] or a [non-wireline] )
carrier for whomever you have a roaming agreement with.

Also sometimes on the CT-301 (and all the other phones made by Mobira)
a close proximity tower of the other carrier will cause your phone to
roam on it, if that tower overpowers the correct carrier for your
phone.

On most phones this is a user option and can be changed "on the fly"
without going into program mode.


Doug Davis/4409 Sarazen/Mesquite Texas, 75150/214-270-9226
{texsun|lawnet|texbell}!letni!doug or doug@letni.lonestar.org