3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

The "Update Microsoft 365 Teams Integration" operation allows users to modify the configuration settings of an existing Microsoft 365 Teams telephony integration within their system. This node is useful for administrators who need to update parameters such as SIP domain, TLS ports, certificates, and other telephony-related settings to ensure seamless communication between Microsoft Teams and their telephony infrastructure.

Practical examples include:

  • Changing the SIP domain or TLS port numbers to match updated network configurations.
  • Updating security certificates and private keys used for secure SIP communication.
  • Enabling or disabling features like Secure SIP or dynamic IP handling.

Properties

Name Meaning
Area Code The area code associated with the telephony integration.
Dial Plan Code The dial plan code used for routing calls.
Enabled Boolean flag to enable or disable the integration.
Id Numeric identifier of the Microsoft 365 Teams integration instance to update.
Is Dynamic IP Boolean indicating if the integration uses a dynamic IP address.
Is Native FQDN Boolean indicating if the Fully Qualified Domain Name (FQDN) is native.
Sbc Certificate JSON object representing the Session Border Controller (SBC) certificate details.
Sbc Certificate Expiration Date Expiration date string of the SBC certificate.
Sbc FQDN The Fully Qualified Domain Name of the SBC.
Sbc Private Key JSON object containing the private key information for the SBC.
Secure Sip Enabled Boolean flag to enable or disable Secure SIP communication.
Sip Domain The SIP domain used in the integration.
Tls Port For Native FQDN Numeric TLS port number used when the FQDN is native.
Tls Port For Non Native FQDN Numeric TLS port number used when the FQDN is not native.

Output

The node outputs JSON data representing the updated state or confirmation of the Microsoft 365 Teams integration after applying the changes. The exact structure depends on the API response but typically includes fields confirming the updated properties and status.

If binary data were involved (e.g., certificates), it would be handled accordingly, but here certificates are passed as JSON objects, so no binary output is expected.

Dependencies

  • Requires an active connection to the Microsoft 365 Teams telephony integration API.
  • Needs appropriate API authentication credentials configured in n8n (such as an API key or OAuth token).
  • Network access to the Microsoft 365 Teams service endpoint.

Troubleshooting

  • Common Issues:
    • Invalid or expired certificates may cause update failures.
    • Incorrect numeric IDs or missing required fields can result in errors.
    • Network connectivity issues to Microsoft 365 services.
  • Error Messages:
    • Authentication errors indicate invalid or missing API credentials; verify and update credentials.
    • Validation errors suggest missing or malformed input properties; check property values carefully.
    • Timeout or connection errors require checking network access and service availability.

Links and References

  • Microsoft official documentation on Teams Direct Routing and SBC configuration.
  • Microsoft Graph API reference for Teams telephony integration (if applicable).
  • n8n documentation on creating and configuring HTTP request nodes and credential management.

Discussion