sinch-elastic-sip-trunking

Provision and manage SIP trunks, endpoints, ACLs, and phone numbers.

9|4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/sinch/skills --skill sinch-elastic-sip-trunking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sinch-elastic-sip-trunking
Source: https://github.com/sinch/skills/tree/main/skills/sinch-elastic-sip-trunking
Command: npx skills add https://github.com/sinch/skills --skill sinch-elastic-sip-trunking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Rapidly provision and configure SIP trunks, endpoints, access control lists, credential lists, and phone numbers so teams can connect customer infrastructure to the PSTN without manual console work or misordered API calls.

Core Features & Use Cases

  • Trunk provisioning: Create and configure trunks with hostname-based SIP domains for outbound and inbound routing.
  • Auth & access control: Configure ACL-based or credential-based authentication for outbound calls and registered endpoints.
  • Endpoint and number management: Create static or registered SIP endpoints and assign E.164 phone numbers to trunks for inbound call routing.
  • Use case: Integrate a PBX with Sinch for both inbound PSTN call delivery and outbound PSTN termination, including failover endpoints and rate-limit considerations.

Quick Start

Create an outbound SIP trunk using ACL-based auth for IP 203.0.113.10 and provide curl and Node.js SDK examples for each step.

Frequently Asked Questions about sinch-elastic-sip-trunking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I provision a SIP trunk for PBX integration with the PSTN?

Configuring a SIP trunk for PSTN connectivity involves creating the trunk with a hostname-based SIP domain, setting up CIDR ACLs or credential lists for authentication, and assigning E.164 phone numbers for inbound routing. This enables both inbound PSTN delivery and outbound termination for your PBX.

What is the difference between ACL-based and credential-based authentication for SIP endpoints?

ACL-based authentication uses CIDR IP address ranges to authorize static outbound calls, whereas credential-based authentication relies on digest credentials for registered SIP endpoints. Both mechanisms secure your SIP trunk against unauthorized access.

Can I use E.164 phone numbers for inbound call routing on a static SIP endpoint?

Yes, E.164 phone numbers can be assigned to trunks to route inbound PSTN calls to static or registered SIP endpoints. This configuration supports failover endpoints to ensure reliable inbound call delivery.

Why do my SIP trunk configuration changes not work immediately after API creation?

SIP trunk configuration changes are subject to mandatory propagation delays across the network before taking effect. You must wait for these propagation delays to complete after resource creation before testing inbound or outbound PSTN routing.

Do I need OAuth2 or Basic authentication to manage SIP trunking API calls?

You need either OAuth2 or Basic authentication to authorize API requests for managing SIP trunks, endpoints, and ACLs. These authentication methods secure the programmatic provisioning of your PSTN routing infrastructure.

What is the best way to automate SIP trunk provisioning without manual console work?

The best way to automate SIP trunk provisioning without manual console work is using API calls that follow ordered resource creation for trunks, endpoints, and credential lists. This approach ensures correct configuration dependencies for reliable PSTN connectivity.