PingOne

Use Case: Configuring Telesign as a provider with PingOne

About this task

Add Telesign as your organization’s provider account.

Steps

  1. Go to Settings > Sender.

  2. Select SMS/Voice.

  3. Select Custom Provider.

    Selecting Custom Provider deletes any existing custom server configuration.

  4. Provider Name: Enter a meaningful name for your Telesign provider account.

  5. Authorization: Select Basic and then enter the following:

    1. User Name: Enter the Client ID for your Telesign provider account.

    2. Password: Enter the API key for your Telesign provider account.

      When editing an existing configuration, you can click Change Account to enter a new password for the custom provider account.

  6. SMS:

    To use Telesign to send SMS messages, configure this section.

    1. Type: Select the POST operation to issue SMS notification requests to the associated vendor URL endpoint.

    2. URL: Enter the following URL https://rest-api.telesign.com/v1/messaging

    3. Body: The request body format style for configuration maintenance. In the list select Form and then add the following key and value pairs. Click Add Key, Value for each additional entry.

      Key Value

      message_type

      ARN

      message

      ${message}

      phone_number

      ${to}

      Changing the the request body’s format style from Form deletes the request body’s key and value pairs, and changing the format style from Raw deletes the request body’s free-form JSON text.

    4. Headers: The Telesign header for the SMS notification requests is added by default.

    5. Plus sign: Select Enabled to enable the standard number format for the sender and recipient numbers, including a leading plus sign.

  7. Voice:

    To use Telesign to send voice messages, configure this section.

    1. Type: Select the POST operation to issue voice notification requests to the associated vendor URL endpoint.

    2. URL: Enter the following URL https://rest-api.telesign.com/v1/voice

    3. Body: The request body format style for configuration maintenance. In the list select Form and then add the following key and value pairs: Click Add Key, Value for each additional entry.

      Key Value

      message_type

      ARN

      message

      ${message}

      phone_number

      ${to}

      Changing the the request body’s format style from Form deletes the request body’s key and value pairs, and changing the format style from Raw deletes the request body’s free-form JSON text.

    4. Preceding padding: Set a custom pause or padding before an OTP character, to leverage Telesign vendor capabilities when sending voice notifications. For example:

      "beforeTag":"<Say>",

    5. Succeeding padding: Set a custom pause or padding after an OTP character, to Telesign vendor capabilities when sending voice notifications. For example:

      "afterTag":"</Say> <Pause length=\"1\"/>"

    6. Headers: The Telesign header for the SMS notification requests is added by default.

    7. Plus sign: Select Disabled to ensure a leading plus sign is not added to the sender and recipient numbers.

      Telesign does not support the use of a leading "+" in phone numbers for voice notifications.

  8. Click Save.

  9. Check your configuration:

    1. To check SMS configuration, in the SMS area, click Send Test SMS and in the popup window enter a destination phone number to test receiving an SMS notification from Telesign, and then click Send. A test SMS notification should be received on the destination phone.

    2. To check Voice configuration, in the Voice area, click Send Test Voice and in the popup window enter a destination phone number to send a Voice notification from Telesign, and then click Send. A test voice notification should be received on the destination phone.