Configure SIP credentials to connect your organization to any VoIP provider. Credentials are shared across your organization — create them once, then link phone numbers to use them. What you’ll learn: How to configure SIP credentials, choose transport protocols, set up rate limiting, and troubleshoot connection issues.Documentation Index
Fetch the complete documentation index at: https://docs.blackbox.dasha.ai/llms.txt
Use this file to discover all available pages before exploring further.
SIP credentials overview
SIP credentials store the authentication details for your SIP trunk provider. Create credentials once at the organization level, then link multiple phone numbers to use them.Create SIP credentials
- Dashboard
- API
- Navigate to Phone Numbers → Credentials tab
- Click Add Credentials
- Fill in the configuration fields
- Click Save
Configuration fields
Required
| Field | Format | Description |
|---|---|---|
server | hostname:port | SIP server address. Include port if non-standard (default: 5060) |
Authentication
| Field | Description |
|---|---|
authUser | Username for SIP authentication (provided by your provider) |
authPassword | Password for SIP authentication |
domain | SIP domain/realm for authentication (often same as server hostname) |
Transport
| Field | Values | Description |
|---|---|---|
transport | udp, tcp, tls | Protocol for SIP signaling (default: udp) |
Rate limiting
| Field | Description |
|---|---|
cpsLimit | Maximum calls per second through this trunk |
cpsKey | Shared key to combine rate limits across multiple credentials |
Transport protocols
Choose the right transport based on your requirements:| Protocol | Port | Encryption | Use when |
|---|---|---|---|
| UDP | 5060 | No | Standard setup, lowest latency |
| TCP | 5060 | No | Behind restrictive firewalls |
| TLS | 5061 | Yes | Security/compliance requirements |
Example: TLS configuration
Example: TLS configuration
Rate limiting
Control call pacing to avoid exceeding your provider’s limits.Single trunk limit
Shared limit across trunks
When you have multiple trunks with a shared rate limit from your provider:Provider-managed credentials
When you connect a Twilio provider, SIP credentials are created automatically:- Source: Shows as
providerinstead ofmanual - Read-only: Cannot modify provider-managed credentials
- Lifecycle: Deleted when the provider is deleted
Check credential usage
Before modifying or deleting credentials, check which phone numbers and agents depend on them:Delete credentials
Troubleshooting
Authentication failures
| Error | Cause | Fix |
|---|---|---|
| 401 Unauthorized | Wrong username/password | Verify credentials in provider portal |
| 403 Forbidden | IP not whitelisted | Add Dasha IPs to provider allowlist |
| Domain mismatch | Wrong domain value | Check provider’s authentication realm |
Connection issues
| Error | Cause | Fix |
|---|---|---|
| Timeout | Wrong server/port | Verify server address and port |
| Connection refused | Wrong transport | Try tcp instead of udp (or vice versa) |
| TLS handshake failed | Certificate issue | Check provider supports TLS; verify port 5061 |
Rate limiting
| Error | Cause | Fix |
|---|---|---|
| 503 Service Unavailable | Exceeded provider CPS | Set cpsLimit below provider’s limit |
| Calls dropping | Shared limit exceeded | Use cpsKey to combine trunk limits |
Next steps
Phone Numbers
Add and link phone numbers
Caller ID
Configure display names
Inbound Calls
Handle incoming calls
Outbound Calls
Make outbound calls