As we continue developing ASTPP, I’ve been curious about what tools our community actually relies on for SIP traffic monitoring and call tracing in production environments.
We’ve come across two commonly mentioned options:
VoIPMonitor - captures SIP and RTP, has a visual web GUI, supports call quality scoring and CDR correlation. We’ve already documented setup steps in our knowledge base.
SIPcapture / Homer - purpose-built for large-scale SIP capture, protocol-level analysis, HEP-based, and scales well in multi-server environments.
A few things I’m genuinely curious about:
Which tool do you use alongside ASTPP?
Why did you pick it over the alternatives?
How do you handle high-traffic environments where capturing everything becomes expensive?
Is there something else entirely that works better for you?
If the community leans toward a particular tool, we’d consider adding proper integration documentation for it. So your input here can directly influence what we build next.
Thanks for jumping in @jcattan and @cogs66. sngrep comes up a lot in our own support interactions too, especially for quick on-the-spot SIP tracing directly on the server without needing any separate setup.
For those unfamiliar, sngrep is a terminal-based SIP packet viewer that reads live traffic or pcap files and displays SIP dialogs in a clean visual flow. Very handy for quick debugging.
A few follow-up questions for anyone who wants to share more:
Do you use sngrep for real-time tracing only, or also for post-call analysis from saved pcap files?
For those running multi-server setups (OpenSIPS + FreeSWITCH on separate nodes), do you run sngrep on both servers separately or do you centralize capture somewhere?
Has anyone combined sngrep with Homer/SIPcapture to get the best of both worlds: quick local inspection plus centralized long-term storage?
Also curious whether anyone has hit issues with sngrep on high-traffic servers where packet loss starts affecting visibility.