Skip to main content

Prerequisites

  • A valid V2 API key

Creating a Credential Based SIP Connection

The following API request will create a basic credential based SIP connection.
For call flows that make use of Pattern 1 (See Common Usage Patterns), the following additional configuration is required.
For call flows that make use of Pattern 2 (See Common Usage Patterns), the following configuration is required.

Using This Connection with Telephony Credentials

For WebRTC SDK authentication, this connection is typically the parent resource for one or more telephony credentials. Best practices:
  • For multi-user applications, create a separate telephony credential per device
  • If you create telephony credentials on demand, wait about 5 seconds before the first login. The same applies to a JWT minted from that credential
  • If you use JWT authentication, mint the JWT from that device’s telephony credential
  • Use the telephony credential’s sip_username (gencred...) with the SIP Registration Status endpoint to check whether the SDK is currently registered

SDK Authentication

SDKs are authenticated with
  • user_name
  • password

Limits

Sum of the following may not exceed 10,000 for an account.
  • Count of credential connection
  • Count of IP connection
  • Count of FQDN connection
  • Count of external connection
  • Count of TeXML application
  • Count of Call Control Application

Additional Resources