LogoLogo
Provectus Technologies GmbH
  • Introduction
    • Secure Contacts App (SCA) - Safe & GDPR Compliant
    • Technical / Security Overview
    • Editions
    • Requirements
  • Quickstart Guide
    • iOS (MAM) - Steps to activate SCA in your Entra Tenant
      • Step 1 -MAM- Register Enterprise App
      • Step 2 -MAM- Add App Protection Policy
      • Step 3 -MAM- Add Conditional Access Policy
      • Step 4 -MAM- Add App Configuration Policy
    • iOS (Intune Managed Device) - Steps to activate SCA in your Entra Tenant
      • Step 1 -MDM- Register Enterprise App
      • Step 2 -MDM- Add App Protection Policy
      • Step 3 -MDM- Add Conditional Access Policy
      • Step 4 -MDM- Add App Configuration Policy
    • Android (Android Enterprise) - Steps to activate SCA in your Entra Tenant
      • Step 1 -AE- Register Enterprise App
      • Step 2 -AE- Add App Configuration Policy
    • Android (aMAM) - Steps to activate SCA in your Entra Tenant
      • Step 1 -aMAM- Register Enterprise App
      • Step 2 -aMAM- Add App Configuration Policy
      • Step 3 -aMAM- Add App Protection Policy
      • Step 4 -aMAM- Add Conditional Access Policy
    • Additional Datasource for SCA
    • Best-Practice Guide for SCA
  • Enduser guide
    • iOS - Onboarding SCA
    • iOS - activate Caller Identification
    • iOS - Userguide
    • iOS - App Manual
      • Contacts page
      • Contacts Sync
      • Contact information
      • Contact settings menu
      • Side menu
      • Logviewer
      • Help menu
      • vCard
    • Android Enterprise - Userguide
  • Documentation
    • Authentication
      • Enterprise Application
      • Conditional Access
        • CA with SCA - Require Complaint Device
        • SCA with CA - Require App Protection Policy
    • Deployment SCA
      • iOS - App Installation
      • Android - App Installation
      • App Configuration
        • iOS - MobileDeviceManagement (MDM) protocol
        • Android - App Restrictions
        • AppConfigurationPolicies
          • iOS - App Configuration Policies - MAM Integration in Microsoft Intune
          • Android - App Configuration Policies - MDM Integration in Microsoft Intune
      • App Protection Policy - Integration in Microsoft Intune
        • APP - unmanaged Devices
        • APP - managed Devices
        • Requirement - Open phone-settings
        • Requirement - Open Maps app
        • Requirement - Open GoogleMaps app
        • Requirement - Open WebExTeams
        • Requirement - Open WhatsApp
        • Requirement - Open Facetime
        • Requirement - Open email-link from SCA in Outlook
      • Deployment for your Devices in Intune
        • Deployment iOS - MAM-WE - APP only
        • Deployment iOS MDM - Managed & Complaint Device
        • Deployment iOS MDM - Managed Device & APP
        • Deployment Android MDM - Managed Device
    • App Configuration Policy -Name/Values for SCA
      • SCA Configuration - SecContacts.Defaults
      • SCA Configuration - SecContacts.Licenses
      • SCA Configuration - AAD filters
      • SCA Configuration - AAD groups
      • SCA Configuration - Connect additional Datasource
      • SCA Configuration - Custom Datasource Names
      • SCA Configuration - CI Customization
    • Data Sources
      • AAD - Azure Active Directory
      • GAL - Global Address List
      • APC - Personal Outlook Contacts
      • D365 - Dynamics 365
      • DVRS - Dataverse
      • ABS - Azure Blob Storage
      • SMC - Shared Mailbox Contacts
    • Valid phone numbers for SCA
    • iOS and Android version of SCA in comparison
  • Additional Information
    • Troubleshooting
    • Frequently Asked Questions (FAQ)
    • Phone number handling defaults changed in release v2.0.19
    • Links
    • Product Page - Secure Contacts App
Powered by GitBook
On this page

Was this helpful?

  1. Documentation

Valid phone numbers for SCA

Last updated 8 months ago

Was this helpful?

SCA works best with phone numbers in a international format for incoming caller identification.

Phone numbers without a international format are invalid for identifying incoming callers.

Use the Configuration Parameter to specify a 2-letter country code, e.g. DE or US. Phone numbers that do not have the full international format will be completed with the regional format of the country code defined. The default value for this parameter is false.

If a phone number cannot be completed automatically, it is marked as invalid in SCA. In this case, depending on the current location, it can be used for an outgoing call, but not for identifying incoming callers.

SCA can filter out invalid phone numbers with the Configuration Parameter set to true. The default value for this parameter is false.

A phone number in full international format includes a plus sign (+) followed by the country code, city code, and local phone number. Make sure that the phone numbers in all data sources are in this format.

Examples of valid international phone numbers:

phone numbers in data source
SCA parsed & formated
is valid

+49 69 3531247

+49 69 3531247

yes

+49 (0)89 56164193

+49 89 56164193

yes

004930124711372

+49 30 124711372

yes

+1 (415) 555-2332

+1 415-555-2332

yes

001 646 940 8602

+1 646-940-8602

yes

001-410-555-1331

+1 410-555-1331

yes

+34 91 426-0693

+34 914 26 06 93

yes

+34608246176

+34 608 24 61 76

yes

14045551337

+1 404-555-1337

yes

491734532510

+49 173 4532510

yes

Examples of invalid phone numbers:

phone numbers in data source
SCA parsed & formated
is valid

(415) 555-2332

(415) 555-2332

no

410 555-1331

410 555-1331

no

914260693

914260693

no

(0)89 56164193

(0)89 56164193

no

01725570802

01725570802

no

313-433-723

313-433-723

no

7321-334

7321-334

no

2001

2001

no

PhoneNumberParseCountryCode_Option
PhoneNumberIngoreInvalid_Option