Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request From: jcp@cgch.uucp (Joseph C. Pistritto) Newsgroups: comp.dcom.telecom Subject: Cellular and Caller*ID Message-ID: <4315@accuvax.nwu.edu> Date: 23 Feb 90 15:04:18 GMT Sender: news@accuvax.nwu.edu Organization: TELECOM Digest Lines: 28 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 125, Message 8 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. All the interesting stuff happens between that switch and the user. Each cellular customer has the virtual equivalent of a local loop, (in the early systems, I think there was actually a physical local loop), which has an assigned phone number. So the switch generates Caller*ID information when placing the outbound call into the network. Further, I'm sure the cellular switch RECEIVES the Caller*ID info just fine as well. The problem is getting it onto the display in the cellular mobile. I don't think there's any provision in the cellular standard for text information to be passed to the remote during call setup. (I could be wrong here, it's been a couple years since I saw the relevant documents). In any event, as far as I know, older phones couldn't support any change to implement this. -jcp- ====================================================================== Joseph C. Pistritto HB9NBB N3CKF 'Think of it as Evolution in Action' (J.Pournelle) Ciba Geigy AG, R1241.1.01, Postfach CH4002 Basel, Switzerland Internet: bpistr@cgch.uucp Phone: (+41) 61 697 6155 Bitnet: bpistr%cgch.uucp@cernvax.bitnet Fax: (+41) 61 697 2435 From US: cgch!bpistr@mcsun.eu.net