Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

911 over ISDN PRI

Status
Not open for further replies.
Aug 27, 2001
502
US
Last year we installed an ISDN PRI to our G3Si PBX (r11).

We have two buildings on our campus. The buildings have different addresses and separate "inbound" phone numbers. Both numbers come in through the ISDN and are routed to the appropriate building by the PBX.

Unfortunately, all "outbound" calls appear to come from the demarc location (Building A). So when someone from Building B calls 911, it looks like they're calling from Building A. This has caused a problem with 911 on at least one occasion.

I've spoken with our phone company and gotten information on Locator ID service.

Here is my question:

I have "Building" information completed for each station. How can I force the PBX to use different outbound numbers based on the "building" information?

For instance:
Building A - 555-0001
Building B - 555-0002

All outbound calls (no matter which building they come from) appear to come from 555-0001. I'd like the PBX to look at the station information and use the appropriate outbound number for that building.

Is this possible?

Thanks!
Ron

“If you are irritated by every rub, how will you be polished?” ~ Mevlana Rumi


Do you live in Michigan? Join us in the Tek-Tips in Michigan forum.
 
On your "A" PBX do a: change isdn public-unknown-numbering

Code:
                          Page   2 of   8
                    ISDN NUMBERING - PUBLIC/UNKNOWN FORMAT
                                   Total                                   Total
Ext Ext    Trk       CPN            CPN Ext Ext    Trk       CPN            CPN
Len Code   Grp(s)    Prefix         Len Len Code   Grp(s)    Prefix         Len

 4 24                5550001         7
 4 25                5550002         7

If you have certian ranges plug them into the table. For instance in the example above, all extensions with a length of 4 that start with 24xx will appear as 5550001 to the outside world...

and

all extensions with a length of 4 that start with 25xx will appear as 5550002 to the outside world.

If you have the extensions scattered, you'll have to make an entry for each.
 
Well, nice try. But it didn't work. I added this configuration. This information is presented correctly to the caller id of called numbers (I called my cell phone to make sure). But I called 911 from one of the "changed" numbers and it's still listed on their screen as coming from "Building A". [sad]

Any other suggestions?

Ron

“If you are irritated by every rub, how will you be polished?” ~ Mevlana Rumi


Do you live in Michigan? Join us in the Tek-Tips in Michigan forum.
 
manfmmd: Yes, Building B is connected to Building A via copper pairs which run directly to the stations. All of the phone "equipment" is located at the demarc in Building A.

rgtrgt: I'm not sure I follow what you mean. When I programmed the PBX (using "ch isdn pub") to send a specific phone number, it seemed to work (as mentioned above). It just didn't work for 911. If that isn't what you mean, could please explain?

Thanks,
Ron

“If you are irritated by every rub, how will you be polished?” ~ Mevlana Rumi


Do you live in Michigan? Join us in the Tek-Tips in Michigan forum.
 
Just add a single analog line to building B (TN747). You can use ARS partitioning to direct 911 calls to that TG.

Kevin
 
on page 2 of the trunk group, send number should be a yes
 
Address information is provided by the LEC based on billing information. The PBX does not control the address.
 
rgtrgt: There looks to be a couple "send number" fields on that page. But they're both set to "y".

4merAvaya: I may have to do that, or pay for & maintain the locator service with AT&T. [thumbsdown]

I'm still a little confused about how the locator service works though. They said that they can add another entry to the 911 table. That much I (kinda) understand. What I don't get is, how do they know when to use which entry? The PBX must be sending them SOME information about where, exactly, the call is originating. How do I control THAT information?

Ron

“If you are irritated by every rub, how will you be polished?” ~ Mevlana Rumi


Do you live in Michigan? Join us in the Tek-Tips in Michigan forum.
 
I use the AT&T/SBC/Ameritech E911 service (Intrado). For initial setup, I sent them a spreadsheet of all of my D.I.D. numbers, including address and location code. Anytime we move a station, we have to update our database (through the internet). You can have multiple addresses in the database (such as in a campus environment). Then when you move a station, you go online adn change that station in your on-line database. Once it's setup, it's easy to maintain. There can be a delay of up to 12 hours between making your update and the change getting uploaded into whatever system the 911 database actually uses, but that hasn't been an issue for us yet. I don't pay the bills, so I have no idea what it costs on a monthly/annual basis.

Hope this helps.

- Duaneness
 
After speaking with a couple product specialists at AT&T, it looks like the "Locator ID Service Lite" is the way for us. We only have two buildings and two DID numbers to worry about. I'm still not 100% sure on how to assign a specific DID number to an outbound call on our ISDN PRI. Is that done using change isdn public-unknown-numbering?

I'll post the results here when it's all done.

Thanks for all the suggestions!

Ron

“If you are irritated by every rub, how will you be polished?” ~ Mevlana Rumi


Do you live in Michigan? Join us in the Tek-Tips in Michigan forum.
 
You said you were able to get the different numbers from each building on your cell phone.
What you need to do is talk to the 911 center and ask them if they can update their records to indicate the "other" building when the ID comes through with that number.
They should be able to as Billing info as provided by the lec can be totally useless.
 
Just for fun, check your trunking. Make sure that the calls to 911 are going out on the same trunk as test calls to your cell phone.

- Duaneness
 
All the replies here sound accurate, and there is more than one way to solve this problem. Sending a different CLID is usually a good way to accomplish your task, and hopefuly your E911 center will be able to adjust their system to key in on CLID rather than (what is probably) the PRI BTN.

One of the easiest alternatives was mentioned by Kevin, who said:

"Just add a single analog line to building B (TN747). You can use ARS partitioning to direct 911 calls to that TG.

Kevin"

So if your work with the PSAP (E911 center) does not result in a solution, consider the ARS partitioning before spending $$$ on a canned solution.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top