WebRTC Voice SDKs Commonalities
Authentication
The following means of authentications are offered
Consult the linked guides on to the specific how-to guides.
Dialing Registered Clients
| Method of Authentication | Dialing registered clients with | Examples |
| Basic credential based SIP connection | SIP user name on the connection object | john1234@sip.telnyx.com |
| Basic credential based SIP connection | Phone number on the connection | +13128889999 |
| Telephony credential | SIP user name on the telephony credential object | gencredXXXYYY@sip.telnyx.com |
| JWT | SIP user name on the parent telephony credential object | gencredxXxYyY@sip.telnyx.com |
Multi-client Registration Behavior
It’s recommended that the user sticks to one method of authentication and not mix and match unless there is a compelling use case for it.
Here is an example to illustrate —
Credential based SIP connection with SIP username john1234. Attached to this connections are:
- Telephony credential,
gencred1- JWT,
token1_1
- JWT,
- Telephony credential,
gencred2- JWT,
token2_1 - JWT,
token2_2
- JWT,
Respective registrations are:
client_ais registered withjohn1234client_bis registered withgencred1client_cis registered withtoken1_1client_dis registered withgencred2client_eis registered withtoken2_1client_fis registered withtoken2_2
| Dialing… | Which client gets rung… |
john1234@sip.telnyx.com | client_a |
gencred1@sip.telnyx.com | Indeterminate; the last client to register between client_b and client_c. |
gencred2@sip.telnyx.com | Indeterminate; the last client to register between client_d, client_e and client_f. |
Costs
WebRTC call legs are billed at $0.002/minute.
Other voice legs and add on features are charged separately and independently according to the user’s price plan.