Target Platform

Authenticates CCaaS to a NetSapiens platform and configures the connection settings so SIP extensions can be registered and calls routed through the system.

An API user and an OAuth client, both created in the NetSapiens Admin Portal, authorize CCaaS to communicate with the platform. This authentication is completed once per CCaaS tenant and must be in place before any SIP extensions can be registered — see SIP Extensions.


Accessing Target Platform

Target Platform is accessible to accounts with Admin permissions.

  1. Navigate to Admin (System) > Target Platform Configuration
  2. A "Netsapiens Platform Settings" window opens for entering the platform's connection details

Requirements

Setting up Target Platform touches three separate systems, each requiring its own access:

InterfaceNeeded For
NetSapiens Admin (NMS) PortalGenerating the Client ID and Client Secret, and verifying the API user's call limit
CCaaS instanceRegistering the new contact center with NetSapiens
NetSapiens Manager PortalCreating the API connection information, via an Office Manager–level user

Creating an API User

The API user serves both as the credential CCaaS uses to reach the NetSapiens API and as the extension used to receive calls from the Contact Center.

  1. Log in to the NetSapiens Admin Portal, typically at https://<FQDN>/SiPbx/adminlogin.php

  2. Select the assigned Domain

  3. Navigate to Users > Configuration and select Add User

  4. Complete the user fields

📘

Naming and Scope

Naming the user Xima LB or Xima CCaaS helps prevent it from being mistaken for a live agent and accidentally deleted. Scope must be set to "Office Manager" or higher — anything lower prevents the API connection from working correctly.

  1. Select Create, then Create User Device

Verifying Unlimited Call Capacity

Call Limit defaults to Unlimited, which is the recommended setting for this user, though it can be lowered if needed.

  1. In the NetSapiens Admin Portal, navigate to Users > Domains

  2. Locate the API user created above and select it

  3. Confirm Call Limit reads Unlimited


Creating OAuth Credentials

Each application accessing the NetSapiens API — including CCaaS — authenticates with its own OAuth client.

  1. Navigate to System > Settings > Advanced > OAuth Clients

  2. Select Add

  3. Enter a Client ID name and select Create

  4. Select the newly created Client ID to reveal the associated Client Secret

  5. Record the Client ID and Client Secret for use in CCaaS

📘

Revoking Access

A Client ID and Secret can be revoked or deleted at any time from the OAuth Clients page, which immediately disconnects the associated application.


Choosing a Connection Method: SRV Record vs. SIP Outbound Proxy

An SRV record is the default and best-practice way to connect CCaaS to NetSapiens, since it follows the platform's own failover process across data centers.

📘

Requesting the SRV Record

If the SRV record is not known, the NetSapiens partner responsible for the deployment can provide it.

If the SRV record is unavailable, a SIP Outbound Proxy can be entered instead:

  1. In the NetSapiens Manager Portal, under the assigned domain, select the API user created above

  2. Navigate to that user's Phone menu and edit the phone

  3. Within the Settings menu, copy the Outbound Proxy value

  4. Paste this into the SIP Outbound Proxy field in the Target Platform Configuration window

⚠️

No Automatic Failover with Outbound Proxy

A connection made using a SIP Outbound Proxy instead of an SRV record will not automatically fail over between data centers.


Required Platform Information

The following fields make up the Netsapiens Platform Settings window in CCaaS, in the order they appear. Domain, SRV Record (or SIP Outbound Proxy), API URL, Client ID, Client Secret, Admin Username, and Admin Password are required; the remaining fields are optional and can be left at their defaults.

FieldDescription
DomainThe domain assigned within the NetSapiens environment, found under Domain, Inventory, or the phone provisioning section
SRV RecordThe default and best-practice connection method — see Choosing a Connection Method above
SIP Outbound ProxyUsed only if the SRV Record is not known — the Outbound Proxy value from the API user's phone configuration, entered without the port
SIP Transport ProtocolThe transport protocol used to register with the NetSapiens platform — see Connection Resiliency Settings
API URLThe base URL of the NetSapiens Manager Portal, up to and including the domain
API Backup URLsOptional additional API URLs CCaaS falls back to if the primary API URL is unreachable
API Preferred ServerOptional — see Connection Resiliency Settings
Client IDThe OAuth credential created above
Client SecretThe OAuth credential created above
Admin UsernameThe API user's credential created above
Admin PasswordThe API user's credential created above; the account must show "Secure password set"
Drop Delay in MillisecondsOptional — see Connection Resiliency Settings
Presence Check Interval in SecondsOptional — see Connection Resiliency Settings
Stuck Calls Check Interval in SecondsOptional — see Connection Resiliency Settings

Entering Platform Settings in CCaaS

  1. In the NetSapiens Manager Portal, navigate to Domains > {Assigned Domain} > Users, locate the API user's extension, and select its edit icon, then Phones
  2. Note the Domain/Proxy and Outbound Proxy shown in the Edit Phone window
  3. In the "Netsapiens Platform Settings" window in CCaaS, enter each field listed in Required Platform Information above
  4. Select Save

Verifying API Access

  1. Navigate to User Management > UC Phone Licensing in CCaaS
  2. If no users are listed, the connection to that domain has not finished completing
  3. From the User Management menu, select Sync UC Users to send a new request
  4. If UC Phone Licensing now populates with the list of UC users, the domain has connected successfully

If users still cannot be pulled from NetSapiens into CCaaS, the following should be checked:

  1. The spelling and formatting of the API URL, Client ID, Client Secret, Admin Username, and Admin Password
  2. The API username and password are correct, and the account shows "Secure password set"
  3. The API user has sufficient permissions
📘

Testing Credentials Directly

The Admin Username and Password can be tested independently of CCaaS by logging into the API URL directly with those credentials.

OAuth clients can be reviewed under System > Settings > Advanced > OAuth Clients in the NetSapiens Admin Portal; user permissions under Users > Configuration > {User} > Scope. If issues persist, Xima Support can assist further.