home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!news.miami.edu!wupost!cs.utexas.edu!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!telecom-request
- Date: 15 Nov 1992 00:05:06 GMT
- From: rees@pisa.citi.umich.edu (Jim Rees)
- Newsgroups: comp.dcom.telecom
- Subject: Re: Stupid Phone Systems Blocking N[01]X Prefixes
- Reply-To: Jim.Rees@umich.edu
- Message-ID: <telecom12.843.10@eecs.nwu.edu>
- Organization: University of Michigan CITI
- Sender: Telecom@eecs.nwu.edu
- Approved: Telecom@eecs.nwu.edu
- X-Submissions-To: telecom@eecs.nwu.edu
- X-Administrivia-To: telecom-request@eecs.nwu.edu
- X-Telecom-Digest: Volume 12, Issue 843, Message 10 of 11
- Lines: 28
-
- In article <telecom12.840.9@eecs.nwu.edu>, rees@pisa.citi.umich.edu
- (Jim Rees) writes:
-
- > You would think that cellular providers would be sensitive to the
- > problem of dialing numbers with a 0 or 1 as the second digit, since
- > many cellular prefixes are of this type. But our latest cell phone
- > number is in the 600 prefix, and we've found that we can't roam
- > anywhere, even where our provider has a mutual roaming agreement with
- > the remote provider.
-
- > [Moderator's Note: When you say they 'cannot deal with the 600 prefix'
- > do you mean other carriers refuse to accept it as a valid phone number
- > for purposes of billing roamers, or do you mean they refuse/cannot
- > accept it for the purpose of incoming calls passed along through the
- > local xxx-ROAM number?
-
- The former. We haven't tried to get incoming calls while roaming.
-
- > I'd say the best recourse here is to simply refuse to pay any
- > roaming charges under the circumstances.
-
- We would do that, but no charges show up on our bill. We are simply
- unable to make any outgoing calls while roaming, short of contacting
- every cell service provider in the US, I can't think of any good
- solution. Looks like we will have to ask our local provider for a
- different number in a more "normal" prefix.
-
-