Example of where there is a compliance issue:
School district with 800 phones, 4 buildings, 200 phones per building.
Most school districts only have a few main numbers and do not have a DID per phone.
The RedSky email notifications sent to the central location (building main office / security desk / front desk) do not contain the callback extension number in element (2). The notifications would actually contain the building's main number DID in the notification to the building main office, which doesn't make any sense.
Per Kari's Law below, there are 3 elements that must be included in the notification for on-site personnel. Section 2 states a “valid callback number” must be in the notification at the central location. This would be the extension number that the central location can use to call back the person that made the emergency call. Section 3 is only referring to the information that is sent to the PSAP, and states that this information must also be included in the notification. In this case, this would include the location main number since the PSAP wouldn’t be able to call an extension directly.
You can add the extension number in a workspace name so it shows in the RedSky notification "Display Name" field for Workspace devices, but not for user devices.
The native WxC emergency call alerts are not a workaround since they defeat the purpose of RedSky as they are tied to a Webex Calling Location, and: 1. The will show the wrong location information since the location is statically assigned. 2. Everyone in the WxC location will receive the alert regardless of where physically the phone is. 3. If the phone is physically in a different WxC location, the notification would potentially be sent to the wrong recipient.
I would think Cisco and RedSky would need to work together to:
Have Webex Calling send the extension number of the calling party in the SIP invite as a header field, whether it’s E911-User-ID, or another header, to RedSky.
RedSky needs to modify their notifications to support adding this field to the notifications / templates.
https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-9
MLTS notification. An MLTS feature that can send notice to a central location at the facility where the system is installed or to another person or organization regardless of location. Examples of notification include conspicuous on-screen messages with audible alarms for security desk computers using a client application, text messages for smartphones, and email for administrators. Notification shall include, at a minimum, the following information:
(1) The fact that a 911 call has been made;
(2) A valid callback number; and
(3) The information about the caller's location that the MLTS conveys to the public safety answering point (PSAP) with the call to 911; provided, however, that the notification does not have to include a callback number or location information if it is technically infeasible to provide this information.
