Bring Your Own Carrier (BYOC)
Bring Your Own Carrier (BYOC)
Dasha platform enables seamless integration with existing VoIP infrastructure through SIP (Session Initiation Protocol) connectivity. This allows both platform users and their end customers to maintain their current telephony setups while leveraging Dasha's conversational AI capabilities.
Overview
BYOC support enables organizations to:
- Keep existing carrier relationships and phone numbers
- Maintain current PBX systems and call routing
- Preserve quality of service agreements
- Control costs through preferred carriers
- Enable end-users to keep their telephony setup
Supported Platforms
Dasha works with major VoIP providers and platforms including:
Commercial Platforms
- Twilio
- Avaya
- Five9
- Genesys
- RingCentral
- 8x8
- Any SIP-compliant carrier or platform
Open Source PBX Systems
- Asterisk
- FreeSWITCH
- OpenSIPS
- Kamailio
Integration Methods
Integration Options
You can set up VoIP integrations through multiple approaches:
No-Code Setup (Dasha Playground)
Programmatic Integration
Inbound Calls
For incoming calls, Dasha provides a unique SIP URI that can be configured in your carrier's system. See our inbound calls tutorial for detailed setup instructions. The URI format is:
sip:<unique-id>@sip.us.dasha.ai
Outbound Calls
For outgoing calls, Dasha connects through your SIP trunk using provided credentials. See our outbound calls tutorial for setup details.
Security Features
Dasha's BYOC implementation includes:
- TLS encryption for all connections
- IP-based access control lists
- SIP authentication
- Secure real-time protocol (SRTP) support
SIP Headers and Call Routing
Dasha provides comprehensive access to SIP headers, including Diversion headers, which are crucial for advanced call routing and tracking call history. The Diversion header is particularly important as it:
- Preserves the original called number when calls are forwarded
- Enables tracking of call forwarding chain
- Helps implement accurate billing and call analytics
- Supports complex call routing scenarios based on original destination
Accessing SIP Headers
You can access SIP headers in your DashaScript using the getConnectOptions() method, which returns an object containing:
- SIP domain of the current connection
- From header information (user part and display name)
- Diversion headers (user parts and domains for multiple forwarding hops)
- Custom X-headers (automatically converted from X-Header-Name format to sip_x_header_name)
Common use cases for Diversion headers include:
- Call center routing based on original dialed number
- Multi-tenant setups with number preservation
- Tracking call forwarding chains
- Implementing fallback routing logic
Reference configuration:
| Property | Type | Description |
|---|---|---|
| account | string | Account username (see user parameter). |
| password | string | Account password (see password parameter). |
| ipAcl | string[] | List of IP addresses or IP masks (e. g. 10.0.1.0/24) you can work with. |
| priority | number | An integer from 0 to 7. The job with a higher priority will be processed earlier. |
Multi-tenant Support
Organizations can:
- Configure multiple carrier connections
- Support different end-user carrier preferences
- Maintain separate routing rules per tenant
- Set priorities for different connections
Technical Requirements
- SIP-compliant carrier or PBX system
- Network access to Dasha's SIP endpoints
- Proper firewall configuration for SIP traffic
Through BYOC support, Dasha enables organizations to add conversational AI capabilities while preserving their telecommunications infrastructure investments and relationships at every level of deployment.