Calling Line ID - PBX Info :: Your Free PBX, PABX and Telephone Information Resource

markj39k · 06-10-2003, 01:28 PM

We help administer an Opt 11 that serves a High School and
2 Middle schools. A while back I recieved much help and advice
from jack and others in reference to passing location information
to 911 more specific than the Billing # for the PRI's. The Demarc
for the campus is in one of the middle schools. Im a Norstar/Merlin
guy, untrained in the intricacies of the big wide world of more than
200 sets. Anyway, at the time I was informed by you fine folks that
indeed there was a service, rather expensive, that would ID a phone
call down to the room number through some sort of shared data base
or somesuch. After much discussion with our local friends at SBC, we
were told that service (Another employee, who has left, made all the
phone calls) was not available over PRI and the issue just sorta died.
Well surprise, surprise , it's baaaaaack and it's my problem. I have
a few questions.
What is this service called (Generic, Specific, whatever ya got) ?
There was some other "flavor" of lines that this worked over,wasn't there?
Will these lines require a different card that the DTI one currently in
the switch ?
Will this service also provide a more specific "Caller ID" or is it only
for 911 calls.
Anybody else worked/ordered this service in Southern Michigan ?
As I recall getting SBC people on the phone who even knew what
this was, was like pulling teeth.

Merci, Danke, Thanks.

[Edited on 10/6/2003 by markj39k]

**Chas2002** · 06-10-2003, 03:55 PM

Markj39K

I think what you're looking for is ESA..

Emergency Services Access
Emergency Services Access (ESA)
In accordance with FCC regulations, Emergency Services Access allows any Meridian 1 telephone to dial 911 (overriding their station class of service), provides outgoing ANI number translation for non-DID calls, provides onsite notification to TTYs and a specifically designated OSN teleset, and supports both CAMA and ISDN trunks to public network emergency services.

IF So - Then check this out...................

A note on packaging
ESA is comprised of three different packages, which must be implemented
separately depending on the functionality that a customer desires.
The ESA package 329 provides ESA Call Recognition and ESA Call
Routing. It also provides basic number translation, such as the addition of
NXX and NPA (area and office) codes, but not non-DID to DID translation
(this is provided by the ESA_CLMP package.) The ESA_SUPP package
provides supplementary capabilities, such as networking capabilities (for
example, incoming ISDN to CAMA number conversions), and On Site
Notification. The ESA_CLMP package provides translation of non-DID to
DID numbers.

AND this..............

Emergency Services Access Product description and administration

ESA Call Recognition....................................... ................................

The ESA Call Recognition function allows the Meridian 1 system
administrator to configure an Emergency Services Directory Number
(ESDN) in Overlay 24 (also used for Direct Inward System Access
administration), on a customer basis. When a Meridian 1 user dials the
ESDN, the Meridian 1 recognizes the call as a public emergency services
request, and immediately routes it to the public emergency services over
trunks designated to handle ESA calls.
The ESDN can be up to four digits long, and can be the same number that a
caller would use to request emergency services from home (in North
America, this number is 911), unless the number conflicts with any other
number in the Meridian 1 dialing plan.
The configuration of a customer’s ESDN is independent of the customer’s
ESN database, so that ESA calls can be routed to the PSAP as soon as the
ESDN is dialed. There is no need to dial a BARS/NARS Access Code prior
to dialing the ESDN. ESA calls also override any access restrictions placed
on sets or trunks. Refer to “Access Restrictions” on page 73 of the feature
interactions section for more details.

Guidelines for configuring the ESDN.............................................. ..........

The Meridian 1 does not check for conflicts between the digits used for the
ESDN and digits used for internal DNs, Coordinated Dialing Plan steering
codes, or a BARS/NARS dialing plan. Therefore, the following guidelines
should be followed when configuring the ESDN on the Meridian 1:
— Do not configure internal DNs and CDP steering codes, that are the same
length or longer than the ESDN, to have the same leading digits as the
ESDN.
If there is any internal DN or steering code that is equal to or longer than
the ESDN, and all the leading digits of that internal DN match the ESDN
digits, then calls will not terminate on that internal DN or steering code,
since ESA calls receive priority. For example, if the ESDN is 911, and
there is a station DN or a steering code of 9112, then whenever someone
dials the 9112 extension, or steering code, they are automatically routed
to the PSAP as an ESA call.

— Do not configure internal DNs or CDP steering codes, that are shorter
than the ESDN, to have the same leading digits as the ESDN.
If there is any internal DN or steering code that is shorter than the ESDN,
and all the leading digits of the ESDN match those of that internal DN or
steering, the callers may be prevented from making an ESA call. For
example, if the ESDN is 911, and there is a station DN or steering code
of 91, then whenever someone attempts to dial the 911 ESDN, they are
presented as a call to that station, or routed out as a CDP steering code,
rather than being routed to the PSAP as an ESA call.
— Do not configure a BARS/NARS dialing plan, i.e., Access Code (AC) +
Location Code (LOC)/North American Planning Area Code
(NPA)/Central Office Code (NXX)/Special Number (SPN), that is the
same length or longer than the ESDN, to have the same leading digits as
the ESDN.

Note: If there is BARS/NARS dialing plan, equal to or longer than the ESDN,
and all the leading digits of that internal DN match the ESDN digits, then
calls will not terminate on that dialing plan, since ESA calls receive
priority. For example, if the ESDN is 911, and there is a BARS/NARS
dialing plan having an access Code of 9 and a Special Number of 114,
then whenever someone tries to dial 9114, they are automatically routed
to the PSAP as an ESA call.
— Do not configure a BARS/NARS dialing plan, i.e., Access Code (AC) +
Location Code (LOC)/North American Planning Area Code
(NPA)/Central Office Code (NXX)/Special Number (SPN), that is
shorter than the ESDN, to have the same leading digits as the ESDN.
If there is BARS/NARS dialing plan, shorter in length than the ESDN,
and all the leading digits of that internal DN match the ESDN digits, then
callers may be prevented from making ESA calls. For example, if the
ESDN is 911, and there is a BARS/NARS dialing plan having an access
Code of 9 and a Special Number of 1, then whenever someone tries to
dial 911, they are automatically routed out as a BARS/NARS Special
Number.

— For customers using a BARS/NARS dialing plan, it is possible to
configure their database such that the PSAP may be reached by either
dialing only the ESDN, or an Access Code and then the ESDN. In order
for the latter to be recognized as an ESA call by the Meridian 1, the
ESDN must be configured as a BARS/NARS Special Number in Overlay
87 (by entering the ESDN in response to the SPN prompt), and the
Special Number be configured to use a local terminating route list index
(by responding to the LTER prompt with YES in Overlay 86).

Originating an ESA call from a set

An ESA call may be made from an analog (500/2500 type) set by simply
going off-hook, waiting for dial tone, and dialing the ESDN. If there is
another call already established on the set, the caller may do a consultation,
or invoke standard conference or call transfer by performing an off-hook
flash, waiting for special dial tone, and then dialing the ESDN.
An ESA call may be made from a Meridian 1 proprietary set by simply going
off-hook, waiting for dial tone after pressing either the Single Call Ringing,
Single Call Non-ringing, Multiple Call Ringing, Multiple Call Non-ringing,
or Hotline (HOT) key, and then dialing the ESDN. If there is another call
already established on the set, the caller may do a consultation, or invoke
standard conference or call transfer by pressing either the Transfer,
Conference, No-hold Conference, or No-hold Conference Hotline key,
waiting for dial tone, and then dialing the ESDN.

Originating an ESA call from an attendant console

An ESA call may be made from an attendant console by pressing an idle
LOOP key, waiting for dial tone, and dialing the ESDN. If the attendant
already has an established call on the source (SRC) side of an active LOOP
key, an ESA call may be initiated on the destination (DEST) side of the active
LOOP key.

Take a look at all that and let me know if that's what you're looking for. This information can be found in: NTP 553-3001-313

dixiedogger · 06-10-2003, 10:54 PM

esa is the packages in the pbx that allow 911 calls to send a different caller id than the normal caller id. for instance the boss wants the front desk number to show when he calls out to everybody but if he calls 911 then his actual extension will be passed as caller id (I think thats pretty much what it mainly does anyway). But all those gyrations do no good if both the bosses number and the front desk reflect the exact same address. If you want to reflect more exact locations on a per DID basis you need what we call in BellSouth's area Pin Point. Which basically lets you manage your own database. For example ext 4000 is address plus room 1409 and 4001 is a different address. You have controll over the description that is seen by the 911 operators when a call is answered. What actually happens is your data is sent to the master database of 911 in colorado and when a call is made to 911 is is crossreferenced by this database and given the proper description. In BellSouth's area this service is avalible on PRI. You could always relocate to a real phone companies area :laugh:

**Chas2002** · 06-12-2003, 05:12 AM

markj39k

Can you provide an Example of a database/software that is compatiable with Bell South "Pin Point"?

Thanks,
Chas

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
help! All T1's are disabled	epsilon6	Meridian Systems	11	11-26-2007 08:00 PM
Caller ID on second line	vdc2222	Siemens / Rolm	2	11-14-2006 06:32 AM
10XX calls will not go through	612moto	Meridian Systems	74	08-08-2006 09:48 AM
Pulse / Tone Problem	telecombo	Technology Chat	4	09-01-2004 08:14 AM
Brooktrout/ HICOM 300	bobmay	Hicom/HiPath	4	06-29-2004 08:04 PM

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)