- Shipped
- August 27, 2026 at 10:28 AM UTC
- Author
- Kamo
- Commit
- d521217
A TCP connect to 5060 proves almost nothing — it succeeds against anything listening, and on UDP it cannot fail at all. That ambiguity is exactly what led me to report the router as blocked when the real fault was a crashlooping pod. sip-probe.py sends a real OPTIONS and requires 200 OK, which is the only evidence the whole path works: NAT, profile, advertised address and all. It also fails if the response leaks 'freeswitch', 'kazoo' or '2600hz' — the white-label is part of the contract, not decoration. Currently passing from outside the network: 47.181.8.87:5060 -> SIP/2.0 200 OK (User-Agent: KamoPBX)