返回资讯中心
外部精选
软件工程
#开发者实时流

Pcap-Diagnose – SIP/VoIP trace analysis that masks PII locally first

What the result looks like — no sign-up, on a real case.

Hacker News 最新ankaios762026/11/5 · 今天2 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

What the result looks like — no sign-up, on a real case.

The analyzed capture is a busy call (SIP 486 Busy Here). For your own captures, the first analysis per email address is free. (The app's UI is German-first.)

The capture contains exactly one call. After the INVITE and a 100 Trying, the called side responds directly with 486 Busy Here. There is no 180 Ringing and no RTP stream — the call never connects and never even rings.

486 Busy Here is sent by the called side and means "busy". Because it arrives immediately, without ringing, the B-party is either genuinely busy (with no call waiting), deliberately rejecting (DND / "busy on busy"), or a channel/line limit on the trunk or SBC has been reached.

The evidence points clearly to the B-side — no action is needed in the network.

0.000s

INVITE 0.040s

100 Trying

0.120s

486 Busy Here 0.125s

ACK

Want to analyze your own capture? Phone numbers and IPs are masked locally first. First analysis free.

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →