BYOC lets you keep the carrier you already pay for. You register your existing SIP trunk as a carrier, add the gateway it sends and receives calls on, and register the numbers (DIDs) you hold with that carrier. Edesy then matches inbound calls from that gateway to the right number and application, and sends outbound calls from those numbers back out through your carrier. Recipes cover Twilio Elastic SIP Trunking, Telnyx, Vonage, Plivo and a generic PBX on a static IP. One API call can create the carrier, its gateways, an application and the numbers together, and it rolls back if any step fails.
Bring your own PBX
Standard SIP
API included
Connect the SIP trunk you already have from Twilio, Telnyx, Vonage, Plivo or your own PBX, and run its numbers through Edesy call logic.
Keep your carrier and its rates
Your existing Twilio, Telnyx, Vonage or Plivo trunk keeps carrying the minutes. Commercial terms stay between you and that carrier.
Recipes for common carriers
Registration-based setups for Telnyx and Plivo, IP-authenticated setups for Twilio Elastic SIP Trunking and Vonage, and a static-IP recipe for a generic PBX.
One call to provision
Create the carrier, its gateways, an optional application and your DIDs in a single request. If any step fails, everything created earlier in that request is rolled back.
Primary and backup gateways
Add more than one gateway to a carrier, each marked for inbound, outbound or both.
Your numbers, Edesy call logic
Point BYOC numbers at an application, so inbound calls reach your webhook or AI voice agent and outbound calls from those numbers route through your carrier.
Scoped to your workspace
Carriers, gateways and numbers you register are visible only to your own account.
End to end, in the order it actually happens.
Register your existing trunk as a carrier: registration credentials and SIP realm, or IP authentication.
Add the carrier's SIP gateway, for example your Twilio termination URI, sip.telnyx.com, sip.nexmo.com, phone.plivo.com or your PBX's static IP.
Register the DIDs you hold with that carrier and link them to an application.
On the carrier's side, point the trunk at the Edesy SIP address and port shown in your dashboard, and allowlist the Edesy IP if the carrier uses IP authentication.
Place a test call each way. Inbound calls are matched by the gateway's source IP; outbound calls use the carrier linked to the from number.
Worth knowing before you build a process around it.
Moving AI voice agents onto numbers you already hold
Keeping a Twilio, Telnyx, Vonage or Plivo contract
Connecting an office PBX on a static IP
Running more than one carrier
Gateway Configuration
Define the gateways your calls traverse, and keep several configured so a route is a configuration change rather than a rebuild.
Learn moreTrunk Provisioning
Create, update and remove SIP trunks from the portal, and run more than one trunk on the same account.
Learn moreRouting Applications
Define what happens to a call once it arrives, and point different trunks or numbers at different behaviours.
Learn moreBYOC lets you keep the carrier you already pay for. You register your existing SIP trunk as a carrier, add the gateway it sends and receives calls on, and register the numbers (DIDs) you hold with that carrier. Edesy then matches inbound calls from that gateway to the right number and application, and sends outbound calls from those numbers back out through your carrier. Recipes cover Twilio Elastic SIP Trunking, Telnyx, Vonage, Plivo and a generic PBX on a static IP. One API call can create the carrier, its gateways, an application and the numbers together, and it rolls back if any step fails.
1. Register your existing trunk as a carrier: registration credentials and SIP realm, or IP authentication. 2. Add the carrier's SIP gateway, for example your Twilio termination URI, sip.telnyx.com, sip.nexmo.com, phone.plivo.com or your PBX's static IP. 3. Register the DIDs you hold with that carrier and link them to an application. 4. On the carrier's side, point the trunk at the Edesy SIP address and port shown in your dashboard, and allowlist the Edesy IP if the carrier uses IP authentication. 5. Place a test call each way. Inbound calls are matched by the gateway's source IP; outbound calls use the carrier linked to the from number.
There is no certified-carrier programme. The recipes are starting points; whether a specific carrier account works is confirmed by configuring and testing it. Call quality and number availability on your own carrier are that carrier's responsibility. Edesy routes to them; it does not change their route. Minutes carried on your own trunk are billed by your carrier under your agreement with them.
AI Startups, BPO, Enterprise IT, SaaS. Typical uses are moving ai voice agents onto numbers you already hold, keeping a twilio, telnyx, vonage or plivo contract, connecting an office pbx on a static ip, running more than one carrier.
SIP trunking is a method of delivering voice calls over the internet using the Session Initiation Protocol (SIP). It replaces traditional PRI/ISDN lines, connecting your PBX or contact center to the public telephone network (PSTN) via an internet connection.
SIP trunking uses an internet connection instead of a physical PRI line. You set the number of concurrent calls on the trunk instead of buying fixed 30-channel PRI circuits, and there is no telco hardware to install on site. Edesy SIP calls cost Rs 0.50/min with a 60-second pulse, and unanswered calls are free.
Rs 0.50/min with a 60-second pulse, unanswered calls free. Connect the PBX you already run.