Home/Access/Guides/Features/Intercom

1 SAFR Intercom Overview

SAFR SCAN offers an intercom capability that provides a mechanism for the person at a SAFR SCAN device to communicate with an operator using 2-way audio and one-way video (video from SCAN to the Operator). SAFR SCAN offers this capability through either WebRTC or SIP protocols. At any time, the operator can remotely issue an Access Granted action which either activates the local door relay or issues a pre-configured credential to the panel to unlock the door.

1.1 Known issues

  • SIP Intercom UDP does not work with a number of SIP Servers. This issue will be resolved in a future release.

1.2 SAFR Intercom Protocols

1.2.1 SIP or WebRTC

SAFR offers the choice of either SIP or WebRTC protocols. Following summarizes the functionality of each and which protocol may fit best for you.

Protocol

Dependencies

Applications

SIP

  • SIP Server (may be supported through your access control manufacturer or a stand alone SIP Server can be used.)
  • SIP-enabled client (either softphone or hardphone)
    • Hardphones are devices that look like a traditional phone but connect via Wireless or Ethernet and support the SIP protocol.
    • Softphones are software applications that run on a mobile device or PC.
  • Use with SAFR On-Premises or SAFR Cloud where SIP is preferred.
  • Applications where device may need to route to one or more extensions.
    • SIP Server can handle routing to multiple extensions either in parallel or sequence.
    • Future release of SCAN will support using keypad to identify extension for multi-unit residential applications.

WebRTC

  • Amazon AWS Account with Kinesis Video Streams enabled.
  • SAFR Cloud account (SAFR On-Premises is possible not, but for most applications not practical for WebRTC due to requirement that mobile clients sign into SAFR Server)
  • WebRTC calls are only supported from SAFR Mobile for Android currently (future releases may include SAFR Desktop for Windows and SAFR iOS clients)
  • SAFR SCAN and WebRTC Clients must have connection to AWS
  • If new connection notifications are required, SAFR Mobile clients must have connection to SAFR Cloud account
  • Deployments using with SAFR Cloud.
  • Deployment where tight integration to SAFR Mobile client for Android is desired.

1.3 SIP Overview

SIP offers the following capabilities:

  • Enable interoperable intercom over SIP functionality on SCAN device.
  • Allow user to call Operator (attendant) from SCAN.
  • At later time, allow user to call contact from directory displayed on SCAN.
  • Allow Operator or Contact to grant access (unlock door temporarily) via SCAN device connected by intercom session.
  • Allow Operator to at any time initiate call to SCAN device.

1.3.1 SIP Architecture

Below is a diagram demonstrating SAFR SIP Architecture.

A diagram of a software system

Description automatically generated

SAFR Mobile app will list out all connected readers if connected to SAFR Server. Status of each reader is provided and calls to the selected reader can be initiated from the SAFR Mobile App. Operators can also use a SIP softfone or hardphone to initiate calls to the readers by entering the SIP extension.

All calls are routed through a SIP Server (dark blue lines). Each SCAN device signs into the SIP server with its own SIP account. Soft or hard phones that will interact with SAFR SCAN must also be signed into the same account or otherwise accessible vis SIP Proxy from that SIP Server. The SIP Server maintains an extension for each SCAN device as well as the operators and is about to route calls as needed. Media is also routed through the SIP Server.

Operators can issue an unlock command by pressing a pre-configured number and sending a DTMF tone. The SCAN device will trigger an Access Granted action and if configured send a pre-defined credential through Wiegand or OSDP to the Panel (green wiring).

1.4 WebRTC Overview

1.4.1 WebRTC Architecture

Below is a diagram demonstrating SAFR WebRTC Architecture.

A diagram of a computer network

Description automatically generated

SAFR Mobile app will list out all connected readers if connected to SAFR Server. Status of each reader is provided and calls to the selected reader can be initiated from the SAFR Mobile App.

All calls are initiated using an AWS account configured with Kinesis Service (dark blue dotted lines). Each SCAN device signs into the AWS account with an AWS IAM account. Mobile Android phones that will interact with SAFR SCAN must also be signed into the same AWS account using SAFR Mobile App for Android (Only Android is supported at this time). AWS Kinesis initiates the session and allows the clients to negotiate an optimal path for media. If SCAN and the mobile phone are on the same network, media is transmitted across the local network. If SCAN and mobile phone are not on the same network, then media is transmitted through the AWS Kinesis account.

Operators can issue an unlock command by pressing the unlock button while in a call. The SCAN device will trigger an Access Granted action and if configured send a pre-defined credential through Wiegand or OSDP to the Panel (green wiring).

1.5 Intercom Display States

SAFR SCAN uses the display to indicate when the device is intercom enabled and what state it is in. Following are the three states the device may be in for the full size SAFR SCAN readers with 3.5 inch displays (SC100 and SC200).

Waiting

Ringing

In Call

When there is no activity, the device will display a white phone icon indicating that it is an intercom enabled device. If a person at the device clicks the call button, the “Ringing” state is shown with animated arrows. The device will stay in this state until the SIP Server disconnects. Once an intercom connection is established, the icon changes to green with a solid green horizontal light indicating that the deice is in a call.

If SCAN is unable to communicate with the Intercom Server (SIP or AWS) or other issues prevent intercom from functioning, the waiting state will indicate such using following graphic:

A face of a person

Description automatically generated

Following are the display states for the mullion SAFR SCAN readers with the 1.5 inch display.

Waiting

Ringing

In Call

A black rectangular object with white text

Description automatically generated

A black rectangular object with white text

Description automatically generated

A black rectangular object with white text

Description automatically generated

1.6 Call Behavior

1.6.1 Outbound Calls

Outbound calls are initiated by pressing the call button on the SAFR SCAN display screen. When pressed, SCAN will initiate a call to the number configured in SCAN Intercom settings. This number can be different for each SCAN device. The SIP Server may implement customized call routing such as sequential or simultaneous calling routing.

When a call is initiated, SCAN will begin to display the Ringing state as shown above. SCAN will remain in this state while awaiting a connection. This cannot be cancelled from the SCAN device. Ringing will continue until timed out by the SIP Server or an operator picks up the call.

Once connected, SCAN display will change to the In Call state as shown above. If configured, SCAN will send 2-way audio and 1-way video (from SCAN’s camera to the operator) for the duration of the call.

Calls cannot be ended from the SCAN device. Only the operator can end the call.

1.6.2 Inbound Calls

Calls can be initiated from a remote client if enabled in SAFR SCAN settings (Accept Incoming Calls). When an operator initiates a call to SCAN, there is no indication of an inbound call (i.e. no ringing). SCAN will go from Waiting state shown above directly to In Call state shown above. Immediately audio and video are transmitted from the device to the operator and operator may begin speaking.

Calls cannot be ended from the SCAN device. Only the operator can end the call.

1.7 Temporary Unlock

SCAN Intercom allows the operator to issue a temporary unlock command to unlock the door. This is performed slightly differently for SIP or WebRTC Intercom and described in the respective sections below.

Regardless of the Intercom Protocol, the unlock action is the same. When a Temporary Unlock command is issued, the following occurs:

  • SAFR SCAN triggers the Door Relay action if enabled.
  • SAFR SCAN sends a fixed credential via Wiegand or OSDP if enabled.
  • SAFR SCAN shows Access Granted Message
    • If Feedback From Panel is configured, then SAFR SCAN will delay the Access Granted message until panel has responded.

1.7.1 Temporary Unlock Credentials

SAFR SCAN can send a temporary unlock command to the access control panel. To do this, a pre-configured credential must be added to the panel and that credential added to SAFR SCAN as follows:

  1. Open SAFR SCAN Operation Settings
  2. Go to Access Control page
  3. Enable “Temporary unlock signal to Control Panel” and supply a facility id and card id.
    • The Card Format that is configured in the “Card Reader” tab will be used (excluding the UID-32-Mapped and UID-56-Mapped formats)

A screenshot of a computer

Description automatically generated