Update SIP Line voximplant.sip.update

Scope: telephony

Who can execute the method: user with the Manage Numbers — Edit access permission

The method voximplant.sip.update updates an existing SIP line created by the current application.

Method Parameters

Required parameters are marked with *

Name `type`	Description
CONFIG_ID* `integer`	Identifier of the SIP line configuration. You can obtain the identifier using the voximplant.sip.get method.
TITLE `string`	New name for the connection.
SERVER `string`	New SIP registration server address.
LOGIN `string`	New login for connecting to the server.
PASSWORD `string`	New password for connecting to the server. Maximum length is 100 characters.

To make changes, at least one of the following fields must be provided: TITLE, SERVER, LOGIN, PASSWORD.

Code Examples

How to Use Examples in Documentation

cURL (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"CONFIG_ID":5,"TITLE":"SIP line 1 (updated)"}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/voximplant.sip.update

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"CONFIG_ID":5,"TITLE":"SIP line 1 (updated)","auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/voximplant.sip.update

try
        {
            const response = await $b24.callMethod(
                'voximplant.sip.update',
                {
                    CONFIG_ID: 5,
                    TITLE: 'SIP line 1 (updated)'
                }
            );
        
            const result = response.getData().result;
            console.log('Data:', result);
        }
        catch (error)
        {
            console.error('Error:', error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'voximplant.sip.update',
                    [
                        'CONFIG_ID' => 5,
                        'TITLE' => 'SIP line 1 (updated)',
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error: ' . $e->getMessage();
        }

BX24.callMethod(
            'voximplant.sip.update',
            {
                CONFIG_ID: 5,
                TITLE: 'SIP line 1 (updated)'
            },
            function(result)
            {
                if (result.error())
                {
                    console.error(result.error(), result.error_description());
                }
                else
                {
                    console.log(result.data());
                }
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'voximplant.sip.update',
            [
                'CONFIG_ID' => 5,
                'TITLE' => 'SIP line 1 (updated)',
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';

Response Handling

HTTP Status: 200

{
            "result": 1,
            "time": {
                "start": 1773657589,
                "finish": 1773657589.659046,
                "duration": 0.659045934677124,
                "processing": 0,
                "date_start": "2026-03-16T13:39:49+01:00",
                "date_finish": "2026-03-16T13:39:49+01:00",
                "operating_reset_at": 1773658189,
                "operating": 0
            }
        }

Returned Data

Name
type

Description

result
integer

Result of the update.

1 — update was successful.

time
time

Information about the request execution time.

Error Handling

HTTP Status: 400, 403, 404

{
            "error": "ERROR_NOT_FOUND",
            "error_description": "Specified CONFIG_ID is not found"
        }

Name `type`	Description
error `string`	String error code. It may consist of digits, Latin letters, and underscores
error_description `error_description`	Textual description of the error. The description is not intended to be shown to the end user in its raw form

Possible Error Codes

Code	Description	Value
`ERROR_NOT_FOUND`	`Specified CONFIG_ID is not found`	SIP line with the specified `CONFIG_ID` was not found among the lines of the current application.
`CHECK_FIELDS_ERROR`	`Server address not specified`	An empty or incorrect value was provided for the `SERVER` parameter.
`CHECK_FIELDS_ERROR`	`Login for connecting to the server not specified`	An empty or incorrect value was provided for the `LOGIN` parameter.
`CHECK_FIELDS_ERROR`	`Password for connecting to the server cannot exceed 100 characters`	The limit for the `PASSWORD` parameter has been exceeded.
`TITLE_EXISTS`	`The specified connection name is already registered in the system`	A line with that name already exists.
`ACCESS_DENIED`	`Access denied!`	Insufficient permissions to update the SIP line.

Statuses and System Error Codes

HTTP Status: 20x, 40x, 50x

The errors described below may occur when calling any method.

Status	Code Error Message	Description
`500`	`INTERNAL_SERVER_ERROR` Internal server error	An internal server error has occurred, please contact the server administrator or Bitrix24 technical support
`500`	`ERROR_UNEXPECTED_ANSWER` Server returned an unexpected response	An internal server error has occurred, please contact the server administrator or Bitrix24 technical support
`503`	`QUERY_LIMIT_EXCEEDED` Too many requests	The request intensity limit has been exceeded
`405`	`ERROR_BATCH_METHOD_NOT_ALLOWED` Method is not allowed for batch usage	The current method is not allowed to be called using batch
`400`	`ERROR_BATCH_LENGTH_EXCEEDED` Max batch length exceeded	The maximum length of parameters passed to the batch method has been exceeded
`401`	`NO_AUTH_FOUND` Wrong authorization data	Invalid access token or webhook code
`400`	`INVALID_REQUEST` Https required	The methods must be called using the HTTPS protocol
`503`	`OVERLOAD_LIMIT` REST API is blocked due to overload	The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support
`403`	`ACCESS_DENIED` REST API is available only on commercial plans	The REST API is available only on commercial plans
`403`	`INVALID_CREDENTIALS` Invalid request credentials	The user whose access token or webhook was used to call the method lacks permissions
`404`	`ERROR_MANIFEST_IS_NOT_AVAILABLE` Manifest is not available	The manifest is not available
`403`	`insufficient_scope` The request requires higher privileges than provided by the webhook token	The request requires higher privileges than those provided by the webhook token
`401`	`expired_token` The access token provided has expired	The provided access token has expired
`403`	`user_access_error` The user does not have access to the application	The user does not have access to the application. This means that the application is installed, but the account administrator has allowed access to this application only for specific users
`500`	`PORTAL_DELETED` Portal was deleted	The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site

Continue Learning

Get List of SIP Connections

Get SIP Connection Status

Update SIP Line voximplant.sip.update

Method ParametersMethod Parameters

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning