Windstream SIP - 911 issues

[Class2666]

We are running Aura ver 6.3 and recently switched from ATT pri's to Winstream SIP + pri's (for analog service)

We also use RedSky e911

The issue we are experiencing is with 911. Via the SIP circuit, we are able to make the calls. But the PSAP only reports the Billing phone number and not our specific caller id. We were unable to find a resolution and after discussing with Windstream tech were told we should simply use the PRI's as they do not have the same screening issues as the SIP.

Unfortunately, it doesn't work that way either. With our normal setup the calls fails due to unassigned number. (Which the tech attributed to an e164 protocol??...) I changed the trunk to a pub-unk and adjusted the route as well but now they say they are not receiving the caller ID info from us. (We do seem to be out-pulsing it but they said they see something along the lines of user screened...)

Has anyone dealt with these types of issues before?

Windstream keeps asking us to change it from natl number to a subscriber number but that doesn't correlate with options I see in the trunk or route.

Any help would be appreciated.

 

[iggy1952]

Class2666,

To clarify your issues:

1. Is the trunk handoff PRI (RJ-45) from the Windstream router? I assume your PRI circuit is up and has the correct protocol in the signaling group.
2. If the trunk is a true PRI handoff you can control numbers sent out from the CM public numbering tables.
3. Your route pattern for 911 calls allows you to set the numbering format as "natl-pub". If this change fails then Windstream is overriding something on their side of the network.

iggy1952

 

[kyle555]

AFAIK, PRI 911 forces BTN from telco to the PSAP unless you make alternate arrangements to send a specific DID if you have the carrier setup the 911 database to have a DID for "your address - first floor" and "2nd floor" etc.

So, that shouldn't be an issue normally...

 

[Class2666]

Iggy,
1. Yes on all counts. Normal analog based calls are in/outgoing without any issues. Showing correct caller id information as well.
2. Everything seems to be coming out of our switch correctly. When calling out over the pri I see (xxx) xxx-xxxx with no 1 or + or anything special to my cell.
3. I have the format blank currently on the route but the trunk is set to natl-pub and I did try with format set to that as well on route.

Kyle,
That was set up, and thats what we are trying to get to work properly. Windstream called it Enterprise 911 I believe and our RedSky is sending the bldg. floor and room info but since Windstream doesnt seem to pass along the caller id (they only pass the BTN) the PSAP doesnt get the info needed to match to database.

 

[iggy1952]

Class2666,

Have you performed a call trace on your 911 test calls?

iggy1952

 

[kyle555]

I'm not terribly familiar with e911 in the US, but I don't think you'll pass anything other than a number to the PSAP. Those numbers may be more than 1 per site, and RedSky can peel out which to send based on various parameters, but that number must be in the PSAPs database to correlate that information.

Now, on prem, RedSky can show the security guard a lot more information and if you set all your descriptions in your interfaces on your data switches and know which cube they go to, you might know that it's Sally in cube 5 and she's allergic to penicillin, but I don't think that'll get to the PSAP.

As far as I know, RedSky can't do anything more than the Emergency Location Extension entry in the IP network map as far as what you send to 911. When you say they saw "user screened", that's telling me that odds are your carrier isn't allowing it to pass.

 

[Wanebo]

If these calls are going out SIP you will need to get a packet capture of the call and verify what you are sending to your carrier as the P-Asserted Identity. Redsky is very specific in that is where they want to see the ELIN. If you are sending the correct information as the PAI then the next likely culprit is that your carrier is stripping and stuffing the information for some reason (usually because the number sent doesn't ride the trunking they provide i.e. they have no control of the number so they remove it and stuff the BTN in it's place). There is also the chance that your SBC is using some signal manipulation causing the issue.

 

[Wanebo]

If you are attempting to send DID numbers that you have on the Windstream SIP circuit out as caller ID on a PRI or other trunking that is NOT Windstream is almost a given that the PRI or other trunking provider will not allow those DID's to pass and that they will do the strip and stuff since they have no control over the PSALI database for the DID's. Plus, almost invariably, 911 calls will only go to the PSAP in the locality that the trunking terminates in (your city, county, parish, or metro unit) with only the address that the trunk terminates at or even no address information at all showing at the PSAP for the call.

Trying to use local trunking, instead of the SIP trunking, defeats many of the advantages that SIP trunking can offer such as getting diverse DID numbers from different geographical areas with local toll charges for outbound calls to that locality, and the ability to route 911 calls in geographically diverse locations to the proper PSAP with correct PS ALI information.