BYOC Terms
These BYOC Terms form part of the Terms of Service and apply when you connect a carrier of your choice to the Services through a bring-your-own-carrier (“BYOC”) trunk. If these BYOC Terms conflict with another Policy on a BYOC matter, these BYOC Terms prevail.
1. What BYOC is
1.1 BYOC lets you route calls between the Services and a carrier with which you have your own contract (“Your Carrier”), while using sip.io for call control, programmable voice, recording, analytics and other platform features.
1.2 A BYOC trunk authenticates to Your Carrier using SIP digest credentials, IP-based authentication, or both, as you configure. Inbound calls from Your Carrier to the Services are authenticated by source IP or credentials you configure.
2. Your carrier relationship
2.1 You are solely responsible for selecting Your Carrier and for your contract with it. sip.io is not a party to that contract, is not Your Carrier’s agent, and has no obligations to Your Carrier.
2.2 You are responsible for all charges billed by Your Carrier, including termination, origination, number, port, regulatory and minimum-commitment charges, and for paying Your Carrier directly. We do not collect, pass through or dispute those charges for you.
2.3 You confirm that your contract with Your Carrier permits you to connect it to the Services and to send the traffic you send through it.
3. Platform fee
3.1 BYOC traffic incurs a per-minute platform fee of USD 0.005 per minute, or the rate shown on our pricing page or your order form if different. The fee applies to every minute of a call carried over a BYOC trunk, inbound or outbound, as recorded in the CDR, in the billing increment stated on the pricing page.
3.2 Other platform features you use with BYOC calls, such as recording, transcription, AI features, IVR and queues, are charged at their standard rates.
3.3 The platform fee is charged whether or not Your Carrier completes, bills or later disputes the call.
4. Compliance through your carrier
4.1 You are responsible for complying with all laws, regulations and carrier rules applicable to traffic you send through Your Carrier, including the Acceptable Use Policy and the Voice Services Policy, which apply to BYOC traffic in full.
4.2 Caller ID. You may present only caller IDs that you are authorised to use and that Your Carrier allows. STIR/SHAKEN signing for BYOC outbound calls is performed by Your Carrier, not by us, unless we state otherwise in writing. You are responsible for the attestation Your Carrier applies and for any registration obligations, such as the FCC Robocall Mitigation Database, that apply to you or Your Carrier.
4.3 Emergency calling. Emergency calls over a BYOC trunk are routed through Your Carrier. We do not provide emergency calling over BYOC. You are responsible for confirming that Your Carrier supports emergency calling, for registering addresses with it, and for configuring emergency routing correctly, as described in the Emergency Services Policy.
4.4 Numbers. Numbers provided by Your Carrier remain subject to Your Carrier’s terms. Porting them is between you and Your Carrier.
4.5 Lawful intercept and records. Where Your Carrier is subject to lawful intercept or data retention obligations, those are between you, Your Carrier and the relevant authority. We will respond to requests directed to us as described in the Law Enforcement Guidelines.
5. Credential security
5.1 You are responsible for the security of the digest credentials, IP addresses and other authentication details used for each BYOC trunk. Credentials you store in the Services for authenticating to Your Carrier are encrypted at rest and used only to place calls you route to that trunk.
5.2 You must use strong credentials, restrict Your Carrier account to the IP addresses of our SBCs where Your Carrier allows, and set spending and destination limits with Your Carrier.
5.3 You are liable for all traffic over your BYOC trunks, including unauthorised traffic, under the Fraud and Toll-Fraud Policy. That includes both our platform fees and Your Carrier’s charges.
6. Channel and CPS limits
6.1 Each BYOC trunk has configurable limits on concurrent channels and calls per second (CPS). Account-level limits also apply. You must set limits that do not exceed what Your Carrier allows.
6.2 Calls that exceed a limit may be rejected. We may lower limits where needed to protect our platform or other customers.
7. Service levels and support
7.1 Our Service Level Agreement covers only our platform. It does not cover Your Carrier’s network, availability, call completion, quality, routing, number provisioning or configuration, or the internet path between us and Your Carrier.
7.2 We provide trunk health information (such as up/down status and related webhooks) to help you monitor Your Carrier. This information is based on our observations and may not reflect the full state of Your Carrier’s network.
7.3 We will help diagnose BYOC issues on our side and will share SIP traces where available. Problems on Your Carrier’s side must be raised by you with Your Carrier.
8. Our right to disable a BYOC trunk
We may suspend or disable a BYOC trunk, immediately and without prior notice where necessary, if:
- it sends or receives traffic that breaches the Acceptable Use Policy or shows signs of fraud;
- it causes, or risks causing, harm to our network, other customers or upstream carriers, including through signalling floods or malformed SIP;
- Your Carrier, a regulator or a court requests it, or we are required to by law; or
- you fail to pay the platform fees.
9. Liability
In addition to the limitations in the Terms of Service, we are not liable for any act or omission of Your Carrier, for Your Carrier’s charges, or for any loss caused by Your Carrier’s network, policies, suspension of your service, or failure to complete emergency calls. You will indemnify us against claims by Your Carrier relating to your use of BYOC.