In this section:
Overview - How does Emergency Call Notification API Work?
United States law requires multi-line telephone systems (MLTS) systems to provide direct dial access to 911 to report emergencies. It prohibits having to dial a prefix to reach an outside line. In addition, when a 911 call is placed on an MLTS system, the system must be configured to notify a central location on-site or off-site where someone is likely to see or hear the notification. Examples of notification can include on-screen messages using a soft client phone application, text messages for smartphones, and email for administrators.
Ribbon’s Emergency Call Notification API provides a notification framework within the SBC Edge to recognize that an outbound 911 has been placed and to actuate an SMS notification sequence (send a text messages) to the configured directory numbers/recipients via a supported SMS Service Provider. For Release 9.0, the only provider supported is Kandy.
Step 1: Review Prerequisites
The following are required to provide SMS messaging:
Step 2: Install SBC Edge
These instructions assume the SBC Edge is installed and running. If the product is not installed, refer to the links below.
Step 3: Create account with Kandy Business Services (KBS)
SBC Edge uses Kandy Business Services (KBS) as the Service Provider for the SMS Notification feature. You must have an account subscription with KBS in order to send SMS notifications to end users.
- Ensure you have a valid subscription to KBS; this service is required to send text 911 notifications to the end user. Refer to: https://apimarket.att.com/pricing/self-service-apis/messaging.
- Create a project within Kandy that contains the following:
- Private Project Key (used as Client ID inSBC Edge)
- Private Project Secret (used as Secret inSBC Edge )
- Caller ID
- Register one number (Caller ID).
Step 4: Configure SMS Notification in SBC Edge
You must configure E911 service
- In the WebUI, click the Settings tab.
- In the left navigation page, access Emergency Services > Notification Manager.
Click the Create (
) icon.Configuration Notes- The maximum number of entries in the E911 Recipients List is 6.
- There is no limit on the number of Notification Manager profiles, but there can only be one active profile.
- To disable the notification table, select Disable from Admin State.
- Configure the options. For field definitions, refer to Creating and Modifying entries in Notification Manager. Return to this page after configuration.
- Click Apply.
Step 5: Configure E911 Emergency Call Route in SBC Edge
- In the WebUI, click the Settings tab.
- Access Settings > Transformation.
- Create a call Transformation Table to support E911 calls. Refer to Creating and Modifying Entries to Transformation Tables.
- Access Settings > Call Routing Table.
- Create a Call Route for E911 calls (i.e., Emergency Calls). For details, refer to Creating and Modifying Entries to Call Routing Tables.
- Select the Number/Name Transformation Table that includes E911 specifications (created above).
Step 6: Test SMS between SBC Edge and Service Provider (KBS)
The Test Event Message option enables you to send a test SMS to the configured directory number/recipients.
Test an SMS notification as follows:
- In the left navigation pane, go to Emergency Services > Notification Manager Table.
- Select the check box next to the profile you wish to test.
Click the Test Event Message at the top of the table. The test message is sent.
The following possible messages are displayed in the form of alerts on the WebUI:
Step 7: Send SMS when E911 is Dialed
Send an SMS as follows:
- Access PBX (or device connected to the Service Provider).
- Dial 911 to sent the notification message to configured recipients.
Access the Alarms Manager to verify the notification has been sent to the Service Provider. The outgoing message will include details of the caller, such as calling number, extension, Caller IP address.
Outgoing MessageAT&T API Marketplace Free Account - Emergency Number dialled calling number:sipp; Calling Extension:;callingIPAddress:10.54.81.86 AttemptTime:05-26-2020 12:50:49.245715