1993-05-12 - Re: CALLER ID?

Header Data

From: George A. Gleason <gg@well.sf.ca.us>
To: jet@nas.nasa.gov
Message Hash: fdba9638141471f28510f1aeb3e0419e3c34a44639d1645709f0ea19ca13da50
Message ID: <199305120921.AA05565@well.sf.ca.us>
Reply To: N/A
UTC Datetime: 1993-05-12 09:21:41 UTC
Raw Date: Wed, 12 May 93 02:21:41 PDT

Raw message

From: George A. Gleason <gg@well.sf.ca.us>
Date: Wed, 12 May 93 02:21:41 PDT
To: jet@nas.nasa.gov
Subject: Re:  CALLER ID?
Message-ID: <199305120921.AA05565@well.sf.ca.us>
MIME-Version: 1.0
Content-Type: text/plain



Getting the wrong number: That can happen if you're in a PBX with a separate
outgoing and incoming trunk group.  Particularly if your incoming number is
a Direct Inward Dialing (DID) number, which means that people in the Outside
World can call right to your desk by dialing (area code +) 7-digits.  There
is no facility on most PBXs to have DID numbers or other station directory
numbers follow outgoing calls, though you might have a call accounting
system hooked up to provide information to your company about which
extensions are making which outside calls; but again, that's entirely within
your own system.  

If you do have an outgoing trunk group, I would advise setting it up so that
incoming calls on that group at least ring to the receptionist's console,
and then give out those numbers to company folks who might have reason to
need a way to get through in a pinch if everything else is down.  Also the
outgoing group will be regular loop- or ground-start trunks, and as a
last-ditch backup you can terminate them on single-line jacks for use with
emergency phones in case of a system crash or an extended power failure.  

You can also use the outgoing group to provide night service, where calls to
various lines in that group would ring to specified extensions in the areas
where people may be working after hours.   

-gg





Thread