Docs Sales Partners Adding Your Own Vendors (SIP & SMPP)

Adding Your Own Vendors (SIP & SMPP)

A field-by-field walkthrough of connecting your own voice and SMS carriers to your Softswitch account, including the SMPP settings that most often trip people up.


Open My Vendors →

Adding Your Own Vendors

Your My Vendors page is where you connect your own carrier relationships to your Softswitch account. A vendor can carry voice, SMS, or both - each direction is configured and priced separately.

Voice (SIP)

A voice vendor needs a host (their IP or hostname), and either IP-based authentication (nothing further to enter, they authorize by your dedicated IP) or a username/password if they require registration-style auth. A tech prefix is only needed if your vendor requires one prepended to the dialed number.

SMS (SMPP)

An SMS vendor connects over SMPP - the standard protocol carriers use for bulk messaging. You will need these from your vendor:

  • SMPP Host & Port - where their SMPP server listens (port 2775 is the common default, but confirm with your vendor).
  • SMPP Username & Password - your account credentials with them.
  • SMPP System Type - only needed if your vendor specifically requires one; leave blank otherwise.
  • SMPP Bind Type - almost always Transceiver (send and receive on one connection), the default. Only change this to Transmitter or Receiver if your vendor's own documentation specifically requires a split send/receive connection - most do not.
  • SMPP Source Address - leave blank unless your vendor tells you otherwise. This is the one field that varies most between vendors.
⚠️ If your vendor rejects the connection with "Invalid Source Address": this means their SMPP server requires the Source Address field to be set to a specific value they assign you - often the same as your SMPP username, but not always. This is genuinely vendor-specific: reply to whoever gave you your SMPP credentials and ask what Source Address to use, then enter it on the vendor's edit page. Most vendors never require this at all, so leave it blank first and only chase it down if you hit this exact error.

Confirming It Actually Connected

After saving, your vendor syncs automatically - this can take a few seconds. Use Check Connector on your Route Test page to confirm: it reports whether the connector is genuinely bound and authenticated with the carrier right now, not just whether the connection attempt is configured. A vendor stuck retrying a failed bind will show as not bound - if that happens, double check host/port/username/password first, then ask your vendor about the Source Address requirement above.

Rates

Voice and SMS rates are entered separately for each vendor - a vendor's SMS pricing is its own table, independent of its voice rates. Both support CSV bulk import/export so a large rate sheet does not need to be typed in one destination at a time.

Routing Groups

New vendors land in your primary routing group by default. If you have split your customers into pools (see Routing Groups), assign the vendor to the right group(s) from the vendor list.

Was this article helpful?