PingOne

Configuring a Syniverse account for PingOne

Use the information in this section to configure PingOne to use your Syniverse account.

Before you begin

Ensure that you have:

  • Your Syniverse account Access Token from the Syniverse dashboard.

  • One or more Syniverse phone numbers that support SMS or Voice.

About this task

By enabling your Syniverse account, you’re taking responsibility for dispatching SMS and voice messages.

Steps

  1. Go to Settings > Senders.

  2. Click +, enter the following options, and then click Next:

    1. In the Sender Type list, select SMS/Voice.

    2. In the Provider Type list, select Syniverse.

    3. In the Syniverse Account Type list, select Syniverse.

  3. In the Provider Configuration window, enter the following information to configure your Syniverse account to work with PingOne:

    A Syniverse account applies across all PingOne applications of the environment.

    • Provider Name: Enter a meaningful name for the Syniverse account.

    • Access Token: Enter the Syniverse Access Token.

    The system uses your access token to connect to your Syniverse account.

    Recommended: In your account in the Syniverse portal, define an application that is dedicated to PingOne traffic. Use this application for analyzing PingOne traffic throughput, and troubleshooting SMS or voice message dispatch cases.

  4. Click Verify. This validates the account to PingOne and populates the Organization Numbers list from your Syniverse account.

    • If the Access Token is incorrect, an error message displays.

    • If your Syniverse account isn’t fully configured, a warning displays next to the Access Token field.

    • If there are no organization numbers in the Syniverse account, it won’t be validated to PingOne.

    Once the account is successfully verified, Organization Numbers displays.

  5. Select one or more phone numbers available to this Syniverse account.

    1. For Toll-free and Short code numbers, you can configure supported Countries for notification recipients:

      • Click in the Countries field. The Configure countries modal opens.

      • Click in the Select countries field to display the list of countries. Select a country from the list.

        • Toll-free: You can add multiple countries in the Select countries list. If no country is specified, the specified toll-free number can only be used to dispatch notifications to United States recipient numbers.

        • Short code: You can select only one country in the Select countries list. If no country is specified, the specified short code can only be used to dispatch notifications to United States recipient numbers.

    2. Click the Show only selected or Show all toggle to show only the marked phone numbers and hide the numbers that aren’t selected, or to show selected and unselected numbers.

    3. Click Select all or Unselect all to select or deselect all the numbers for this account.

      • If you intend to use both SMS and voice, all your selected numbers must support both SMS and voice.

      • Syniverse allows the use of sender IDs (in place of telephone numbers) for commercial use or to comply with regulations requiring SMSs to be sent as transactional and not promotional.

      • Sender IDs are displayed according to the Sender IDs sent in the API requests.

  6. Click Save. A Third-party Service Consent message shows. Click I Consent to proceed and save your changes.

    After configuring this sender, add it to a notification policy to control when PingOne uses it for SMS or voice notifications. Learn more in Notification Policies.

Fallback

If PingOne receives an error during the message dispatch process that the used number is invalid, it retries using another configured Syniverse number. After attempting to dispatch the message and receiving an error for all configured numbers, the fallback flow is triggered.

  • If there is no way of originating the SMS or voice event with the tenant’s own Syniverse account and you defined a fallback, the event will be originated from the configured fallback account.

  • The following errors will cause fallback:

    • All API errors (but not SMS delivery errors).

    • No organization number was found on the Syniverse account.

  • If a transaction was charged to a specific account, it doesn’t imply that subsequent transactions will be charged to the same account. The account charged for each transaction is determined on an individual basis. Preference is always given to the custom account.

Adding Syniverse notification tracking to PingOne audit logs

To help troubleshoot any potential issues, include Syniverse notification events in the PingOne audit logs. To include Syniverse notification events in the PingOne audit logs:

  1. In the list of configured senders, locate your sendert.

  2. Click the sender name. The summary of the sender configuration is displayed on the right side of the screen.

  3. Copy the URL from the Address field.

  4. In your Syniverse account:

    1. In the Delivery Configuration, paste the URL that you copied from the PingOne Address field.

    2. Create two subscriptions: SCG-Message and SCG-Voice-Calls.

      Learn more in the Syniverse article How to setup a Webhook for Receiving Messages and Notifications.

    These Syniverse configurations are required in order that Ping Identity’s dashboards and reports will reflect complete and accurate data. Ping Identity won’t be able to troubleshoot SMS or voice events related to Syniverse if these configurations are incomplete.