HTTP OUT SMS trunks allow you to send outbound SMS messages from your DID numbers to a specified HTTP(s) endpoint. This enables direct integration with your own systems or third-party services.
Enter the general information required to set up your SMS to HTTP OUT trunk. Provide a descriptive friendly name, configure the callback URL for delivery notifications, specify allowed IP addresses, and define the sender ID settings for outbound SMS.
Fig. 2. SMS to HTTP OUT Trunk configuration window.#
The Source Address Settings section controls which DID numbers can be used as the sender ID for outbound SMS.
Use the Allow any DID(s) for SMS OUT toggle to choose how sender IDs are assigned:
Toggle on (default): All DIDs with Outbound P2P SMS enabled in your account can be used as the sender ID.
Toggle off: You can specify which DIDs are allowed. To do this, select numbers from the Available Source Addresses list and add them to the Allowed Source Addresses list. Only the numbers you add will be available as sender IDs.
Fig. 3. Source address selection for SMS to HTTP OUT Trunk.#
Note
When the Allow any DID(s) for SMS OUT toggle is turned off, the Available Sender IDs list shows only DIDs that support outbound P2P SMS.
The system automatically selects the message encoding:
GSM-7 is used for Latin-based characters. Each SMS fragment can contain up to 160 characters.
UCS-2 is used for non-Latin characters. Each SMS fragment can contain up to 70 characters.
Billing is based on SMS fragments, not on the message as submitted. If a
long SMS is split into multiple fragments, each fragment is billed
separately.