| Method | update.sip_lines |
|---|---|
| Description | Editing a SIP line |
| Available to | Partner, Client |
Request parameters
| Title | Type | Required | Accepted values | Description |
|---|---|---|---|---|
access_token |
string | yes | Authentication session key | |
id |
number | yes | Unique SIP line identifier | |
user_id |
number | no | Unique user identifier of the client agent on behalf of which the request is made Is required for the agentTo obtain a list of client users, you must use the method "get.customer_users" |
|
employee_id |
number | yes | Unique employee identifier, see method "get.employees" | |
virtual_phone_number |
string | yes | E164 format. Starts with 7 | Virtual number displayed on outgoing calls. If the virtual number is not transmitted, then the SIP line type will be only “incoming connection”; if transmitted, then it will be “incoming and outgoing” |
billing_state |
enum | no |
|
SIP line status in billing.
|
channels_count |
number | no | The number of available lines on a SIP line Determined by the limitations of the tariff plan. |
JSON request structure```json
{ "jsonrpc": "2.0", "id": "number", "method": "update.sip_lines", "params": { "access_token": "string", "user_id": "number", "id": "number", "employee_id": "number", "virtual_phone_number": "string", "billing_state": "enum", "channels_count": "number" } }
### JSON response structure```json
{
"jsonrpc":"2.0",
"id":"number",
"result":{
}
}
List of returned errors
See the section "List of errors for methods with the update verb"