SAFR WebRTC implementation supports making a call from SCAN to SAFR Mobile Android App or calling the device from SAFR Mobile Android application to SAFR SCAN. An AWS account is required in order to broker connections between the SCAN device and SAFR Android Mobile client. SAFR support 1-way video (SCAN->Phone) and 2-way audio. When Intercom is enabled, you will see a call button on SAFR SCAN screen. If Intercom is offline, the call button will appear with a line through it. When active, the button can be pressed to initiate a call.
This section describes how to set up SAFR for WebRTC Intercom.
SAFR Recognition App for Android must be connected to SAFR Server to initiate intercom session with SAFR SCAN.
SAFR Intercom requires that both SAFR SCAN and the Android phone running the SAFR Operator App can establish a connection out to AWS and require an AWS Account set up by the administrator. This document provides some guidance on setting up SAFR Intercom.
Kinesis video streaming is required to enable SAFR SCAN WebRTC Intercom. SMS Notifications enable you to send a notification to an operator to initiate the intercom call.
See Article Create AWS Account at http://docs.real.com or http://support.real.com for information on setting up AWS Account.
You can configure Intercom settings on SCAN either in SAFR SCAN Web Console (if running SCAN in standalone mode) or Video Feeds window of SAFR Desktop (If SAFR SCAN is connected to SAFR Server).
On SAFR SCAN Web Console or SAFR Desktop
To enable the operator to receive a notification when the call button is pressed, a notification must be set up. See Notifications below for details.
Below table describes the settings.
Setting name |
Default value |
Description |
AWS Region Code |
None (req’d) |
AWS hosting region where connections are made. Pick a region close to your location. In desktop app click “i’ to select a region near you. In Web Console see Amazon Kinesis Data Streams endpoints and quotas <https://docs.aws.amazon.com/general/latest/gr/ak.html> for a list of regions. |
AWS Account |
Req’d |
The AWS Account Access Key and AWS Account Secret Key for the IAM User you gave permissions for above. Be careful to avoid pasting spaces onto the beginning or end of the strings. |
AWS Channel Name |
Req’d |
A unique string associated with the SCAN device. SCAN will create a channel in AWS using this name. It must be unique within the AWS Account SCAN is connected to.
|
Video |
Enabled |
Option to disable video. Video takes about 1 Mbps from SCAN to operator. With WebRTC, video is routed directly between SCAN and the SAFR Mobile app on Android if possible. Otherwise, the AWS Kinesis account will be used to proxy the video. AWS Vide data transfer and video charges may apply – see AWS Costs above. |
Call button action |
Disabled |
Options: Disabled, Call Operator, Call Mobile Phone.
|
Required fields:
Signaling Channel field is only required to test Intercom. Enter the AWS Channel Name from the SAFR SCAN device you wish to test with. Under normal operation, Android client will get the signaling channel during session initiation and thus can operate with any SCAN device.
Press back button to save settings.
SAFR SCAN WebRTC Intercom requires SAFR Mobile App for Android be connected to SAFR Server to make or receive calls.
See SAFR Documentation for how to connect SAFR Mobile App for Android to SAFR Server. A quick summary is:
Use Event Sources page to see if Intercom is enabled and working. Each SCAN device is listed as an event source. SCAN devices that have Intercom enabled appear with a phone icon. The status of the phone icon will indicate the state of the device (active, in-call, ringing or error state).
Following shows view from Event sources on Android and iOS. iOS Intercom sources are view only – intercom sessions cannot be established from SAFR Mobile for iOS at this time.
Android |
iOS |
|
|
Following shows a single Event source for Android and iOS. iOS only allows viewing of the video – 2-way audio is not supported.
Android |
iOS |
|
|
You can initiate a SAFR WebRTC Intercom session in 2 ways:
Both options require SAFR Mobile App for Android be connected to SAFR Server. See instructions below.
You can make calls from the Android phone to SAFR SCAN. This is done through SAFR Mobile App Event Sources. This requires that SAFR Mobile App for Android be connected to SAFR Server and configured with the AWS Kinesis account as described above.
When in the call, you can take the following actions:
SMS messages are used to notify one or more operators of an inbound call from SAFR SCAN. The process works as. Follows:
Following steps describe how to set up SMS Notifications in SAFR to notify one or more operators to initiate a SAFR WebRTC Intercom session.
To initiate intercom via SMS you will first need to enable SMS for SAFR Server. With SAFR Cloud accounts, you can do this by simply choosing “SARF Cloud” as the SMS provider. To set up SMS on SAFR On-premises server, you must setup an AWS Account and enable SMS as described above in “Setup AWS Account”. Once the AWS Account is created, use the IAM User credentials to configure SMS for SAFR Server as follows:
Once SMS is enabled, you can create one or more SMS Alarms in SAFR as follows:
You can send the SMS to up to 10 phones which all may connect to the intercom session in parallel.
Once set up, clicking on the Call Button on SAFR SCAN will initiate an SMS message to the configured phones. The SMS will include a link. That link will launch the SAFR Android App and display the Intercom event that triggered the alarm. User can launch the intercom session from that event by launching the SAFR Android App. The SAFR App must be installed to initiate the Intercom call.