Actions290
- Task Actions
- Direct API Actions
- CRM Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Get Entity
- Add Entity
- Update Entity
- Delete Entity
- Get Entity Rights
- Get Entity Sections
- Add Entity Section
- Update Entity Section
- Delete Entity Section
- Get Entity Item
- Add Entity Item
- Update Entity Item
- Delete Entity Item
- Get Entity Item Properties
- Add Entity Item Property
- Update Entity Item Property
- Delete Entity Item Property
- Chat Actions
- User Field Actions
- File Actions
- User Field Config Actions
- Duplicate Actions
- Timeline Actions
- Disk Actions
- Upload File
- Download File
- Delete File
- Get File Info
- List Files
- Create Folder
- Delete Folder
- Get Storage Info
- Get Storages
- Get Storage
- Get Folders
- Get Folder
- Add Folder
- Update Folder
- Copy Folder
- Move Folder
- Rename Folder
- Get Files
- Get File
- Copy File
- Move File
- Rename File
- Share Item
- Get Shared Items
- Get Sharing Rights
- Update Sharing Rights
- Workflow Actions
- Status Actions
- Calendar Actions
- Chatbot Actions
- Events Actions
- Lists Actions
- Product Actions
- Open Lines Actions
- Telephony Actions
- Register External Call
- Finish External Call
- Hide External Call
- Show External Call
- Search CRM Entities
- Attach Call Record
- Get External Line
- Add External Line
- Update External Line
- Delete External Line
- Get Voximplant Statistics
- Get Voximplant Line
- Get Voximplant SIP Connector
- Get Voximplant SIP Line
- Add Voximplant SIP Line
- Update Voximplant SIP Line
- Delete Voximplant SIP Line
- Message Service Actions
- Notify Actions
Overview
This node integrates with the Bitrix24 platform, specifically enabling operations on telephony resources such as Voximplant SIP lines. The "Update Voximplant SIP Line" operation allows users to modify the configuration of an existing SIP line within Bitrix24's telephony system. This is useful for updating connection details like SIP server address, login credentials, or line metadata without recreating the line.
Practical scenarios include:
- Changing SIP server settings after infrastructure updates.
- Rotating SIP credentials for security compliance.
- Renaming or reassigning phone numbers associated with a SIP line.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate API requests: OAuth2 (recommended), Webhook (simpler), or API Key. |
| Line ID | The unique identifier of the SIP line to update (required). |
| Line Name | The new name to assign to the SIP line (required). |
| Line Number | The phone number associated with the SIP line (required). |
| SIP Server | The address of the SIP server to connect to (required). |
| SIP Login | The username/login credential for the SIP account (required). |
| SIP Password | The password for the SIP account (required, stored securely). |
Output
The node outputs JSON data representing the result of the update operation. Typically, this will include confirmation of the updated SIP line details or error information if the update failed.
If the node encounters an error and "Continue On Fail" is enabled, it outputs an object containing:
error: The error message.resource: The resource name ("telephony").timestamp: The time when the error occurred.
No binary data output is indicated in the source code.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2 token, webhook URL, or API key).
- Depends on Bitrix24 API endpoints for telephony and Voximplant SIP line management.
- No additional external libraries beyond those bundled are required.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials.
- Invalid Line ID: The specified Line ID must exist; otherwise, the API will return an error.
- Missing required fields: All required properties (Line ID, Line Name, Line Number, SIP Server, SIP Login, SIP Password) must be provided.
- API rate limits or connectivity issues: Network problems or Bitrix24 API limits may cause failures; retry or check network status.
- If the node throws an error, enabling "Continue On Fail" can help capture error details in the output for debugging.