TelecomCustomAccountsId
Update Custom SIP account configuration. If server/country/transport/auth changed and trunks were already provisioned, they are reprovisioned automatically. Otherwise only allowed_addresses is pushed to the trunk.
Authorization
Bearer AuthorizationBearer <token>
JWT Authorization header using Bearer scheme
In: header
Path Parameters
id*string
Format
uuidRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
curl -X PATCH "https://api.speaknode.com/api/Telecom/custom/accounts/497f6eca-6276-4993-bfeb-53cbbbba6f08" \ -H "Content-Type: application/json" \ -d '{}'{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"provider": "string",
"account_identifier": "string",
"created_at": "2019-08-24T14:15:22Z",
"updated_at": "2019-08-24T14:15:22Z",
"sip_gateway": {
"addresses": [
"string"
]
},
"custom_sip": {
"sip_server_address": "string",
"sip_transport": "Auto",
"sip_destination_country": "string",
"sip_allowed_addresses": [
"string"
],
"sip_outbound_auth_username": "string",
"has_sip_outbound_auth_password": true,
"sip_inbound_auth_username": "string",
"has_sip_inbound_auth_password": true,
"port": 0,
"live_kit_inbound_trunk_id": "string",
"live_kit_outbound_trunk_id": "string",
"live_kit_dispatch_rule_id": "string",
"updated_at": "2019-08-24T14:15:22Z"
}
}Create a new Custom SIP account. LiveKit trunks are NOT created here — they spin up on first phone-number bind (CustomTelephonyProvider). POST
Previous Page
Reprovision LiveKit SIP trunks for a Custom TelecomAccount: deletes existing trunks (best-effort) and recreates them from current DB state. Useful when LiveKit was redeployed with empty DB or trunks were removed manually. POST
Next Page