RedSky Implementation 1

[cfickes]

Ran into a problem and I cannot figure out how to send a dedicated ELIN. The problem encountered was instead of the correct ELIN being sent to the RedSky call center, it is sending the wrong ANI/ELIN. I’ve got 34 sites and about 370 subscribers across 10 states, which we are going to connect to our core, no gateways. We are implementing SIP trunking on our core for local/LD calling for these 34 sites. I am sharing ELIN licenses among many stations (a cost constraint). Meaning that, for instance, a site of 25 stations would all share one ELIN, and each site would have its own unique ELIN. I have location-based ARS implemented to direct 911 calls out via the core LD trunks.
Current setup:
1. Created new location for each site
2. Defined Network-Region for each site
3. Defined Network Map for each site – input ELIN extension in “Emergency Location Ext”
4. Added Route Pattern
5. Defined ARS table for that location
Can anyone assist?

 

[kyle555]

I guess the location based routing wouldn't even matter if you're all going out the same trunks.

ELE in the network map + an ARS string defined as alrt = sending that ELE out to the PSAP

When you say RedSky, you don't mean having your own on site and integrating it, but just sending your 911 over a SIP trunk and passing the associated ELE, right?

What you could do is make your cell # in ARS be alrt and route out the SIP trunks and trace off your SBC inside and out and see what's being sent in the from and pai headers if you're in fact passing it to the provider.

What, if anything, does your SIP carrier say or know about that? They might be heading you off at the pass if they don't know you're intending to put 35 sites behind one SIP trunk if you don't have DIDs ordered in those rate centers and they might be overwriting that ELE you're passing for 911 calls. Have they confirmed you're good to go on their end for doing that?

 

[cfickes]

The 911 calls are going out an ISDN trunk group, there isn't any configuration with SIP for 911. The SIP trunking is just for the inbound DID's.

 

[kyle555]

OK, then is your PRI provider allowing you to override BTN when dialing 911? Try the example I said making your cell an alrt # - if you see the right number on CLID on your cell, you know the screening table is off to send what you want, but your provider still absolutely needs to let you send variable DIDs for 911 depending and you need release forms and stuff to accept responsibility if you mess up.

Also, I'm not too familiar with the US implementation of it... but can you guys send a DID for Boston 911 out a NY PRI to do what you're trying? I've never seen that!

 

[Msensabaugh]

we've been testing for E911 on our systems and found we had to add the ELIN to the public unknown number table in order to send the number out the correct clid digits for the 911 call.

As someone stated already, the emergency call number 911 needs to be configured as alrt or emergency in order for it to use ELE number, and if ELE/ELIN number needs to be in public inknown table in order to publish correct digits. The Pri provisioning needs to allow you to send clid over the BTN on the circuit.

I hope this helps.

 

[Saiyan656]

May need to spin up an open source e911 solution

https://www.kamailio.org/w/

(SIP connection to SMGR for ELIN).

https://downloads.avaya.com/css/P8/documents/100128344.

The document attached link is for Redsky but maybe the same config for Kamailio? Also not sure if it can work across different 911 exchanges, only seen this work out of the same exchange with multiple buildings.

 

[PhonesAllDay]

When I implemented RedSky they specifically said to NOT populate the network map as they were updating the emergency location number on the station based on the station IP Address.

We input IP Address Ranges per location into the RedSky database and associate them with an ELIN and describe the address and location there.

To route 911 we changed our ARS Digit Conversion for every location for 911 to have a replacement string for full phone number RedSky assigned us.
In the ARS Analysis table we enter in the number RedSky Assigned for 911 and set the call type to alrt.

Then the ARS for that replacement string has a route pattern per location to use our SIP trunk first and their local PRI second.

For the outbound caller ID in the Public/Private table for the SIP trunk we put the extension for the ELIN stations with their full caller ID (because it's the ELIN station that should display on the outbound).

They should have given you a test number you can dial where it will read back your caller ID. I setup 611 as the test number to get this going.
--------------------------------------------------------------------------------------------------
ARS DIGIT CONVERSION REPORT

Location: all

Matching Pattern Min Max Del Replacement String Net Conv ANI Req

911 3 3 3 17705551212 ars n n n
--------------------------------------------------------------------------------------------------
list ars analysis

ARS DIGIT ANALYSIS REPORT

Location: all

Dialed Total Route Call Node ANI
String Min Max Pattern Type Number Req

17705551212 11 11 10 alrt n

--------------------------------------------------------------------------------------------------

display route-pattern 10 Page 1 of 3
Pattern Number: 10 Pattern Name: RedSkey E911
SCCAN? n Secure SIP? n
Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC
No Mrk Lmt List Del Digits QSIG
Dgts Intw
1: 3 1 200 1 n user
2: 103 1 200 1 n user
3: n user
4: n user
5: n user
6: n user

BCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR
0 1 2 M 4 W Request Dgts Format
Subaddress
1: y y y y y n n rest lev1-pvt next
2: y y y y y n n rest lev1-pvt none
3: y y y y y n n rest none
4: y y y y y n n rest none
5: y y y y y n n rest none
6: y y y y y n n rest none
--------------------------------------------------------------------------------------------------
display system-parameters crisis-alert
CRISIS ALERT SYSTEM PARAMETERS

ALERT STATION
Every User Responds? y

ALERT PAGER
Alert Pager? y
Originating Extension: 77777
Crisis Alert Code: 911
--------------------------------------------------------------------------------------------------

CRISIS ALERT IP SOFT PHONE
display station 70000 Page 1 of 5
STATION

Extension: 70000 Lock Messages? n BCC: 0
Type: 9630 Security Code: * TN: 1
Port: S05637 Coverage Path 1: COR: 7
Name: ;REDSKY CRISIS ALERT IPFONE Coverage Path 2: COS: 6
Hunt-to Station: Tests? y
STATION OPTIONS
Location: Time of Day Lock Table:
Loss Group: 19 Personalized Ringing Pattern: 1
Message Lamp Ext: 74778
Speakerphone: 2-way Mute Button Enabled? y
Display Language: english Button Modules: 0
Survivable GK Node Name:
Survivable COR: internal Media Complex Ext:
Survivable Trunk Dest? y IP SoftPhone? y ------------------SOFT PHONE Y
--------------------------------------------------------------------------------------------------
BUTTON ASSIGNMENTS
1: call-appr 5:
2: call-appr 6:
3: call-appr 7:
4: crss-alert 8:--------------------------------------------CRSS-ALERT
--------------------------------------------------------------------------------------------------
ELIN STATION

display station 30000 Page 1 of 5
STATION
Extension: 30000 Lock Messages? n BCC: 0
Type: 6408D+ Security Code: TN: 1
Port: X Coverage Path 1: COR: 1
Name: ;REDSKY ELIN 404-123-4567 Coverage Path 2: COS: 1
--------------------------------------------------------------------------------------------------
list private-numbering Page 1-------------------PUBLIC AND PRIVATE TABLE IDENTICAL

NUMBERING - PRIVATE FORMAT
Ext Ext Trk Private Total
Len Code Grp(s) Prefix Len

5 30000 3 4041234567 10---------------------------------------ELIN STATION AND ELIN DID will outpulse 404-123-4567
5 30000 103 4041234567 10


--------------------------------------------------------------------------------------------------
ALTERNATIVE FOR MULTIPLE ELIN EXTENSIONS:
--------------------------------------------------------------------------------------------------
ELIN STATION

display station 31234 Page 1 of 5
STATION
Extension: 31234 Lock Messages? n BCC: 0
Type: 6408D+ Security Code: TN: 1
Port: X Coverage Path 1: COR: 1
Name: ;REDSKY ELIN 404-123-8899 Coverage Path 2: COS: 1

list private-numbering Page 1-------------------PUBLIC AND PRIVATE TABLE IDENTICAL

NUMBERING - PRIVATE FORMAT
Ext Ext Trk Private Total
Len Code Grp(s) Prefix Len

5 3 3 40412 10---------------------------------------ELIN STATION AND ELIN DID will outpulse 404-12 + ELIN Station
5 3 103 40412 10 38899
--------------------------------------------------------------------------------------------------
display station 10000 Page 1 of 5
STATION

Extension: 10000 Lock Messages? n BCC: M
Type: 9620 Security Code: * TN: 15
Port: S05166 Coverage Path 1: 300 COR: 7
Name: Smith, Jo Coverage Path 2: COS: 9
PAGE 2 Hunt-to Station: Tests? y
Emergency Location Ext: 31967 Always Use? n IP Audio Hairpinning? y ------------------REDSKY AUTOMATICALLY ASSIGNED EMERGENCY LOCATION NUMBER
--------------------------------------------------------------------------------------------------
list history Page 1

HISTORY
Date of Loaded Translation: 10:00pm Sun Sep 6, 2015

Date Time Port Login Actn Object Qualifier
9/27 13:10 MAINT redskySMScha station 10000
--------------------------------------------------------------------------------------------------
status station 10000 Page 4 of 7
CALL CONTROL SIGNALING
Port: S05166 Switch-End IP Signaling Loc: PROCR H.245 Port:
IP Address Port Node Name Rgn
Switch-End: 10.185.140.20 1720 procr 1
Reg Set End:10.25.21.16 23587 220--------------------STATION IP ADDRESS 10.25.21.16
--------------------------------------------------------------------------------------------------
display ip-network-map
IP ADDRESS MAPPING

Subnet Network Emergency
IP Address Bits Region VLAN Location Ext
--------------------------------------------- ------ ------ ---- -------------
FROM: 10.25.21.0 /24 220 n -------------------NOTE: NO EMERGENCY LOCATION DEFINED
TO: 10.25.21.255
--------------------------------------------------------------------------------------------------
RED SKY E911 MANAGER

EMERGENCY RESPONSE LOCATIONS:
HOME OFFICE ATLANTA 1ST 4041238899
--------------------------------------------------------------------------------------------------
RED SKY E911 MANAGER

IP RANGES LOWER UPPER
HOME OFFICE ATLANTA 10.25.21.0 10.25.21.255
--------------------------------------------------------------------------------------------------

You can test all of the sites remotely by using the list trace station/Button number +6 if you set autodial on the station to 911

For example: autodial on button #5 command: list trace station 10000/11 {will remotely press button 5 on station 10000 set to autodial 911)
You can use another station with COR that allows monitor/speak on the test station to talk to the 911 operator to verify the address RedSky is displaying with them
Setup your monitoring/speaking for that station on another phone before you do the list trace JUST DONT USE A SOFTPHONE for this monitoring, it turned out badly for me.
Was able to test over 10 remote sites in different states in less than an hour using this method. Some operators will yell at you because all of them have different rules for testing so that was the most stressful part.

Good Luck
PhonesAllDay
(and all night)