E911 over PRI

[TivoNut]

I know the traditional implementation for E911 requires the use of CAMA trunks from local telco and a CAMA trunk card in the Definity. However, SBC (PacBell) here in Orange County, CA, will do it over PRI.

I have a single PRI trunk group (23 channels) for our local service. I know how to use ISDN PUB/Unk numbering to construct individual 10 digit numbers for outbound caller ID (ANI). However, we currenly send only our main office number as the ANI for all outbound calls. I want this to remain the same, but when a user dials 911, I want the individual, unique ANI constructed and sent.

I can't seem to to have it both ways, I've been tinkering with ISDN numbering, trunk groups and route patterns, but can't get it. Anyone have any ideas?

 

[bwilch]

If I understand you correctly, you want your outbound caller ID to be your main office, but if someone dials 911, you want it to show the ext the call is orginating from?

 

[TivoNut]

Yes, that is correct. So for example, I normally send 714-555-1000 for all calls. But my extension is 1234, so if I dial 911, I want to send 714-555-1234. I can't seem to find a way to do this.

With CAMA trunks, there is the CAMA-Numbering form "change cama" which would solve the problem, but I assume that only works with CAMA trunks.

 

[NX01]

How many trunks do you have?

In the future everything will work...

 

[TivoNut]

I have one PRI trunk group from the LEC which contains 23 B channels, or one PRI T1. I know if I had multiple trunk groups, I could specify 911 calls out over only that one trunk, and then define that one trunk separately in ISDN-Public numbering. But I don't have two trunks. I've thought of splitting the trunk into two smaller trunks, but I'm not sure that will work. One D channel would have to control two separate trunk groups in my switch, even though everything is on the same physical T1. I may try that if there are no other clever solutions.

 

[NX01]

Crisis Alert to your security, admins or HR would be a work around.

Also you can specify a route pattern just for 911 calls. Then insert the " Per Call CPN Unblocking Code Access Code:" into the route pattern.

In the future everything will work...

 

[TivoNut]

We already have crisis alert going, but we're 24 hour so they're not always around, plus we're two buildings with different street addresses.

That second solution is the type of clever thing that just might work, I'll give it a try.

 

[TivoNut]

That was clever, but not clever enough. It worked when I manually dialed all the digits, but the digit insertion on the route pattern inserts the digits on the actual trunk when making the call, so I actually reach a wrong number.

 

[TivoNut]

I spoke with Avaya support today and the only solution they had was splitting the trunk group as I suggested previously. I've tested and it appears this will work fine, so I'll probably go that route.