Home/Access/Guides/Features/Intercom

2 SIP Intercom

SAFR SIP implementation supports making a call from SCAN or calling the device from a SIP phone. A PBX or SIP server is required. Connections are brokered through the server. 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 SIP Intercom.

2.1 System requirements

  • SAFR SCAN SC100, SC200 or SC50 models
  • SAFR SCAN Firmware version 1.16 or later
  • SAFR Recognition App for Android version 3.16 or later (optional)
  • 3rd party SIP Server with 1 SIP account created for each SCAN device.
  • 3rd party SIP Client (software application or SIP enabled physical phone)

2.1.13 rd Party SIP Applications

You will need a SIP Server to broker the connection between SCAN and a SIP enabled soft or hard phone. If you don't have one you can use one of the following which have been tested and work well with SAFR:

You can then connect both SAFR SCAN and your SIP phone to the server and make calls between them.

You will also need a SIP enabled client. This can be a software-based SIP client running on PC or mobile or a physical SIP-enabled phone (hardphone). Following is a good free option that is tested and known to work with SAFR SCAN:

Linphone - https://www.linphone.org/

See also PortSIP Client above.

2.2 Configuring SAFR SCAN for SIP Intercom

Before configuring SAFR SCAN, install a SIP Server and add one account for each SAFR SCAN device. An account is typically made up of digits 0 through 9 (though SCAN supports any ASCII characters in username). You will need the password associated with the account unless your SIP server does not require a password for the account.

2.2.1 Enable SIP on SAFR SCAN

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

  1. Go to Operation Settings
    1. Web Console: Operation > Intercom
    2. SAFR Desktop: Video Feeds > “…” menu for desired SCAN > Operation Settings > Intercom
  2. Select SIP from the Protocol dropdown list. The dialog will show the following options.

A screenshot of a phone call Description automatically generated

  1. Set the following settings
    1. SIP Server Address (IP Address or hostname)
    2. SIP Server Realm (if required)
    3. SIP Device Username and Password
    4. Call button action (This is the SIP account that will be called when pressing call button on SCAN diplay)
    5. Door unlock dial key (When this key is sent by the remote device, scan will perform a temporary unlock)

Below table describes the settings.

Setting name

Default value

Description

SIP Server Address

None (req’d)

IP Address or host name of the SIP Server.

SIP Server Realm

*

Realm defined on SIP Server. Realms provide a unique namespace for usernames. Often a domain name is used. Use * to not limit to a Realm.

SIP Device Username

None (req’d)

Account username defined on SIP Server. Can be letters or numbers but most often are just numbers to facilitate easily dialing by keypad.

SIP Device Password

None

The password of above account if required by SIP Server. An account does not need to have a password but when completing this dialog, a value is required so enter any value if password not required by SIP Server.

Transport

TCP

The network transport to use. Either TCP, UDP or TLS. This should match what is allowed by your SIP Server. Often SIP Server will allow two or more. Use TCP or UDP if unsure.

Audio

Auto

Either Audio or one of the following codecs: Auto, Speex-8000, Speex-16000, Speex-32000, iLBC-8000, GSM-8000, PCMU-8000, PCMA-8000, G722-8000, Opus-48000-2

Leave auto unless issues observed (i.e. no audio or clipping). Audio codec must be supported on SIP Server and the remote SIP client. With some SIP Servers, you may need to set the audio codec specifically. Try different codecs until you are able to hear good quality audio or identify the audio codecs supported by your SIP Server and SIP Clients.

Video

Enabled

SCAN supports 1-way video from SCAN to the remote SIP device. Set to disable will to save bandwidth by not sending video from SCAN to remote SIP device. Video takes up about 1 Mbps of bandwidth.

Call button action

Call operator

The action triggered by pressing the phone icon on the SCAN touch screen display.

  • Disabled – No action. Calls cannot be intiated from SCAN device.
  • Call operator (ext-0) – Initiates a SIP call to extension 0 on PBX server. SIP server must be configured to accept this action.
  • Call extension – Initiates a sip call to the extension provided in the Extension setting. This will be another SIP account on the SIP Server.

SIP Server can be configured for various actions such as routing a call to a specific user, calling a group, route a call to available operator, etc.

Extension

None

The SIP client extension to call when pressing call button on SAFR SCAN screen.

Door unlock via dial key

Enabled

Enables or disables option to temporarily unlock SAFR SCAN from the remote SIP device. If set, the Door unlock dial key should be set. If set, the Temporary unlock signal to Control Panel in Access Control settings page will indicate the credentials to send to the access control panel when Door unlock dial key is pressed.

Door unlock dial key

0

Digit 0 through 9 used to issue a temporary unlock command. When pressed SCAN will display the Access Granted messaging and if configured will send the temporary unlock credential configured in Access Control settings (see below).

Accept Incoming calls

Enabled

Use disable to prevent calls from remote SIP devices from opening a SIP session to this SCAN device.

Limit incoming to extensions

None

If no extensions are entered, all calls from SIP Server are accepted. If any extensions are entered, only calls from entered extensions will be accepted.

2.3 Call Behavior

General call behavior is described in Section 1.6 above.

2.3.1 Pause/Resume Support

SAFR SCAN supports pausing the SIP Intercom session as shown below.

A screenshot of a video call Description automatically generated

During pause, audio and video are not transmitted/screen does not update. Resume will resume 2-way audio and 1-way video.

2.4 Temporary Unlock

Temporary unlock is performed by pressing a DTMF tone in the client (i.e. the keypad). Any single digit (0 thru 9) can be configured to unlock the door. See Section 1.6 for what it means to unlock the door.

2.4.1 SIP Notifications

Typically, the SIP client will notify operators of an incoming call. This may not always be supported on mobile operating systems such as iOS which may not allow an application to run in the background or behave like a typical incoming phone call.

If desired, SAFR can be configured to send SMS notifications to operators when the call button is pressed. See Intercom Notifications below for details on how to use SAFR to generate SMS notifications.

2.5 Troubleshooting SIP Intercom

  • Symptom: No Audio or popping sound
    • Cause: Possibly the audio codec is not supported on SIP server or client
    • Resolution: Test with different audio codecs in SAFR settings until sound is heard.
      • With Genetec Sipelia, following audio codecs do not work: Speex-8000, iLBC-800, Opus-48000-2
    • Cause: Audio device is not enabled
    • Resolution: If using Remote Desktop to server, make sure Microphone is enabled in Remote Desktop settings. Check if your SIP Client has preferences for which device to use as a Microphone.
  • Symptom: Not found error or similar errors upon connecting from SCAN or SIP Endpoints
    • Cause: Server address or port incorrect or possibly caused by invalid account credentials (either username or password)
    • Resolution: Ensure that SIP server address and port are correct. Test these from alternate SIP endpoint. Also confirm username and password and ensure SIP server is configured correctly.
  • Symptom: Unable to make calls from SCAN to a SIP Client but can make calls from SIP Client to SCAN
    • Cause: Possibly caused by mismatch of transport protocol.
    • Resolution: Ensure that the client is configured to the same transport protocol (TCP, UDP or TLS) as SAFR SCAN
  • Symptom: Inbound calls from scan are delayed or SAFR SCAN disconnects from PBX frequently.
    • Cause: Could be due to network configuration issues.
    • Resolution: Try configuring scan to use Static ip address.
  • Symptom: Outbound calls from scan are delayed.
    • Cause: Could be due to unreachable DNS Server.
    • Resolution: If using DHCP, ensure DNS Server returned by DHCP server is valid. If using Static IP address, ensure valid DNS server is configured in SAFR SCAN