VoIP provider portal and setup

The VoIP Provider Portal  lets a VoIP provider publish its name, logo and shared softphone configuration. Customers select the provider in the app and enter their own SIP username and password.

The portal is live. Mobile provider-directory support is being prepared for testing in SessionTalk Free and Paid on iOS and Android. Older app builds do not show the provider list. SessionCloud, whitelabel and desktop apps continue to use their existing provisioning flows.

For an overview, see VoIP providers on the SessionTalk website .

Create your listing

1. Open the provider portal  and create an account, or sign in with your existing SessionTalk account.
2. Verify your email address before publishing. The portal offers a resend link if needed.
3. Download the JSON configuration template. Set your provider name, SIP domain, transport and the supported defaults your customers need.
4. Upload the JSON configuration and a PNG, JPEG or WebP logo. The configuration file must be no larger than 64 KB and the logo no larger than 2 MB.
5. Check the preview and save the draft. Saving a draft does not change the published listing.
6. Select Publish when the configuration and logo are ready. Published listings are returned by the mobile provider directory.

The portal manages a provider listing separately from SessionCloud customer projects. A provider configuration contains shared connection settings; do not include subscriber passwords, tokens or other customer credentials.

Configuration example

Localphone is the single published test provider. Its configuration uses localphone.com with automatic SIP DNS discovery and private-IP push registration:

{
  "schemaVersion": 1,
  "name": "Localphone",
  "domain": "localphone.com",
  "transport": "UDP",
  "sipPort": 0,
  "proxy": "",
  "login": {
    "authUsername": false,
    "subdomain": false
  },
  "sipSettings": {
    "privateip": true
  }
}

Upload the logo separately from this JSON. sipPort: 0 leaves the port automatic, so the app can discover the SIP endpoint through DNS SRV records. Set a nonzero port only when your service requires an explicit port. privateip controls the push server’s SIP registration address; it does not change the customer’s SIP domain or enable a purchase.

The portal validates the supported configuration fields and rejects unknown settings. Use the downloadable template as the starting point. Enable login.authUsername if customers need a separate authentication username, or login.subdomain if they must enter a subdomain for your service.

How customers add an account

In a compatible standalone mobile build, open Settings → Accounts → Add account → SIP. Choose your provider, then enter the customer’s SIP credentials and save. The provider’s logo appears in the list and account setup screen.

Generic SIP account remains available for manual setup, including when the provider service cannot be reached. Customers can search the provider list by name. Reopen account setup to load the current published directory.

If Add Account opens the old login form, confirm the installed app supports the provider directory. A published server listing does not add the screen to an older app build.

Free app purchases

In SessionTalk Free, Push and Business must be purchased or restored before its features are available. Associated premium settings, including push registration mode, push server private IP, messaging and video settings, are hidden until ownership is verified. Provider defaults cannot unlock these features. SessionTalk Paid includes Business access.

A customer can still configure basic SIP calling without Business. Disabling an account allows editing of the settings their edition and purchase permit; it does not grant premium access.

Update or withdraw a listing

Upload revised settings or a new logo, save the draft, then publish the revision. Published settings supply defaults for new accounts; they do not overwrite accounts that customers have already configured. Use Unpublish to remove one provider listing from the public directory without deleting its saved draft.

Test before rollout

Use an app build with provider-directory support to check the logo, credentials form and applied settings. Test foreground calling and background push calls separately, with the applicable purchase active in the Free app. A successful configuration upload does not by itself verify registration or two-way audio.

For assistance, contact SessionTalk support.