Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request
From: covert@covert.enet.dec.com (John R. Covert  24-Feb-1990 0754)
Newsgroups: comp.dcom.telecom
Subject: The Facts about Cellular and Caller ID
Message-ID: <4329@accuvax.nwu.edu>
Date: 24 Feb 90 13:04:58 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 30
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 126, Message 9 of 11


>There's no reason (none at all), why cellular phones shouldn't
>generate Caller*ID (eg. the person being called FROM a cellular phone
>would get correct Caller*ID displayed on his box), as the 'switch'
>part of a cellular system is pretty much a standard model.

Dead wrong.

Every cellular switch in the U.S. is connected to the local network
just like a PBX.  No phone company is currently offering SS7 (the
prerequisite for Caller ID) as a method of connection for PBXs.  This
means that where there is Caller ID, the number which will appear is
_not_ the cellular number, but rather the number assigned to one of
the DoD trunks.  In fact, when I call the New England Telephone
operator in Boston from a NYNEX or Southwestern Bell cellular phone,
the operator doesn't have the cellular number.

>Further, I'm sure the cellular switch RECEIVES the Caller*ID
>info just fine as well.

Nope.  Sorry.  Again, cellular switches are connected without the
benefit of SS7, and have no way to receive Caller ID info, which can
_only_ be passed on lines (not trunks).

>I don't think there's any provision in the cellular standard for text
>information to be passed to the remote during call setup.

Correct, and it probably won't be added to the standard.

/john