A gateway is the specific endpoint calls are sent to or accepted from. Managing gateways as first-class configuration - created, listed and removed independently of the trunk - means changing where traffic goes is an edit rather than a re-provisioning exercise. That is what makes it practical to keep a secondary path configured before you need it.
Bring your own PBX
Standard SIP
API included
Define the gateways your calls traverse, and keep several configured so a route is a configuration change rather than a rebuild.
Gateways are independent objects
Add or remove a gateway without disturbing the trunk or the carrier it belongs to.
Keep an alternate path configured
A second gateway can exist before you need it, rather than being built under pressure.
Separate inbound and outbound paths
Different gateways for different directions or destinations where your setup calls for it.
Listed and auditable
See every configured gateway rather than discovering one nobody documented.
End to end, in the order it actually happens.
Create a gateway with its connection details.
Associate it with the relevant carrier.
Send test traffic through it.
Keep or remove it as your routing changes.
Worth knowing before you build a process around it.
Multi-carrier routing
Regional call routing
Preparing a secondary path
Migrating between providers
Bring Your Own Carrier (BYOC)
Connect the SIP trunk you already have from Twilio, Telnyx, Vonage, Plivo or your own PBX, and run its numbers through Edesy call logic.
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 moreA gateway is the specific endpoint calls are sent to or accepted from. Managing gateways as first-class configuration - created, listed and removed independently of the trunk - means changing where traffic goes is an edit rather than a re-provisioning exercise. That is what makes it practical to keep a secondary path configured before you need it.
1. Create a gateway with its connection details. 2. Associate it with the relevant carrier. 3. Send test traffic through it. 4. Keep or remove it as your routing changes.
Configuring a gateway does not by itself provide automatic failover. Treat failover behaviour as something to design and test, not assume. The gateway must be reachable and accept your traffic - configuration on this side does not fix a refusal on the other.
BPO, Enterprise IT, Telecom Resellers, Hospitality. Typical uses are multi-carrier routing, regional call routing, preparing a secondary path, migrating between providers.
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.