Troubleshooting
Purpose
Section titled “Purpose”A first-stop guide for diagnosing common Get2Dial issues.
Overview
Section titled “Overview”Start from the symptom, check health and logs, then work down the call path: web → control → NATS → edge call engine → FreeSWITCH/OpenSIPS → carrier. The trace ID ties a single call’s logs together across services.
Configuration
Section titled “Configuration”Ensure LOG_LEVEL=info (or debug while diagnosing) and that /healthz is
reachable for each service.
Examples
Section titled “Examples”| Symptom | First checks |
|---|---|
| New image not running | Did you run up -d --force-recreate after pull? |
| CDRs under wrong tenant | Edge TENANT_ID / g2d_tenant_id stamping |
| No outbound calls | NATS connectivity; one call engine per originate subject |
| Caller ID wrong at carrier | caller-id-in-from; gateway re-create after param change |
| Media one-way / drops | rtpengine re-anchor on re-INVITE (hold/transfer) |
| Asset won’t play on edge | EDGE_MEDIA_ROOT mismatch; media sync manifest |
- After a deploy, treat a migration-version mismatch as the prime suspect.
- A
sofiarescan won’t refresh an existing gateway’s params — recreate it.