Zum Hauptinhalt springen

BulkSMS

Navigate to SMS Management

Add an SMS provider

  • Log into your Vodia Tenant portal.

  • Click Trunks on the left menu then SMS Management

  • Under the Providers tab click the [+ | Add] button

  • Complete the information.

  • Name: Provide a name (for your purposes)

  • Provider: Select BulkSMS

  • Username: Enter your BulkSMS API token ID (username).

  • Password / Application Secret: Enter your BulkSMS API token secret (password).

    note

    BulkSMS uses HTTP Basic authentication built from the username and password you enter here. You can create a token ID / secret pair in the BulkSMS account portal — consult the BulkSMS documentation for the exact location.

  • Click [Save].

Add your SMS numbers

Now you need to add your DIDs into the Numbers tab.

  • Under the section SMS Management (Trunks on the left menu then SMS Management)
  • Click the Numbers tab and click the [+ | Add] button.
  • Provide a name (for your purposes)
  • Enter your phone number in E.164 format (e.g., +12025551234). Numbers are passed to BulkSMS exactly as entered.
  • Policy: If you have any policy in place, choose it. (optional)
  • Provider: Choose the provider name you have created.
  • URL prefix for receiving messages: Enter something you will use for your SMS callback URL. Eg: bulksmsinbound
  • Source: It could be your extension number.
  • Destination: It could be your extension number.
  • Click [Save].

Configure the BulkSMS inbound webhook

To receive messages, configure BulkSMS to deliver inbound messages to your PBX. In the BulkSMS portal, locate the inbound message / webhook settings (consult the BulkSMS documentation for the exact location) and set:

  • Webhook / callback URL: Your PBX URL with the prefix you specified above, for example: https://your-pbx-domain.com/bulksmsinbound
  • Format: JSON

Vodia expects the inbound payload as JSON containing from, to, and a body (or text) field.

Outbound messages are sent to https://api.bulksms.com/v1/messages.

Your BulkSMS integration is now configured and ready to use.