# Programmatic access to SIP PCAP / SIPCallInfo.pcap\_file\_link — is there a supported API?

**URL:** <https://community.livekit.io/t/programmatic-access-to-sip-pcap-sipcallinfo-pcap-file-link-is-there-a-supported-api/2026>\
**Category:** Telephony\
**Tags:** sip-trunking, livekit-cloud\
**Created:** [September 10, 2026, 4:18am UTC](https://community.livekit.io/t/programmatic-access-to-sip-pcap-sipcallinfo-pcap-file-link-is-there-a-supported-api/2026 "2026-09-10T04:18:10Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![samson](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@samson](https://community.livekit.io/u/samson)\
**Post date:** [September 10, 2026, 4:18am UTC](https://community.livekit.io/t/programmatic-access-to-sip-pcap-sipcallinfo-pcap-file-link-is-there-a-supported-api/2026/1 "2026-09-10T04:18:10Z")

</div>

Hi team 👋 — LiveKit Cloud customer running voice agents over SIP (outbound telephony at meaningful volume). Looking for a supported way to pull the per-call **PCAP** (or the metadata inside it) programmatically.

**Why we want it**

We grade carrier/route quality per call. From our own dial events we already track ASR / ACD / PDD / MOS / SHAKEN / hangup-cause. The one thing we can’t get from attributes, CDR, or the participant API is the **far-end (carrier) RTP media IP** and per-packet stats — which are exactly what you need to spot bad routes: hang-up boxes, anchored/relayed media, one-way audio, and abnormal loss/jitter clustered to a media endpoint.

The **PCAP has all of this.** We downloaded one from the dashboard (Telephony → Calls → Download) and parsed it offline — from a single call we cleanly extracted the far-end media IP:port, negotiated codec, RTP packet counts + directionality, sequence-loss %, and the media-vs-signaling IP split (anchoring signal). Great data. We only need the **packet metadata** , not the audio.

**The gap — we can’t automate it**

- The dashboard **Download** button calls `cloud_protocol.AnalyticsService/GetSipPcapFile`, which authenticates with a **browser session token** , not a project API key/secret — and it isn’t in the open-source server SDKs or the `lk` CLI.
- The server SDK (`livekit-api`) has **no `ListSIPCallInfo` / `GetSIPCallInfo`** method, so we can’t fetch `SIPCallInfo` (which is where `pcap_file_link` lives).
- The webhook event set doesn’t appear to include a SIP call-info / PCAP event.

So today the PCAP looks like a **dashboard-only, manual** capability.

**The ask**

1. Is there a **supported, API-key-authenticated** way to (a) list/get `SIPCallInfo` per call and (b) fetch the PCAP (or a presigned `pcap_file_link`)?
2. If not today — could `pcap_file_link` (plus `to_uri`/`from_uri`, `audio_codec`) be delivered via a **SIP webhook event** , or exposed through a **server RPC**? Either would let us build a small “CDR-style” enrichment job.
3. Any guidance on **PCAP retention window** , and whether PCAP capture is on by default for Cloud SIP (or needs enabling)?

We’d **sample/target** (suspect carriers/DIDs, rolling sample) — not firehose every call — and store only derived metadata. Happy to share more about the use case if helpful. Thanks! 🙏

---

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [September 10, 2026, 9:43am UTC](https://community.livekit.io/t/programmatic-access-to-sip-pcap-sipcallinfo-pcap-file-link-is-there-a-supported-api/2026/2 "2026-09-10T09:43:58Z")

</div>

Hi Samson, unfortunately we do not have an automated way of obtaining pcap files today, or the data within them.  
We are working on a wider initiative for API access to data more generally, which would be the correct solution here, but that would not be a solution for you in the short term.

Sorry I don’t have a better solution for you.

---

<div class="post-metadata">

**Author:** ![samson](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@samson](https://community.livekit.io/u/samson)\
**Post date:** [September 10, 2026, 2:08pm UTC](https://community.livekit.io/t/programmatic-access-to-sip-pcap-sipcallinfo-pcap-file-link-is-there-a-supported-api/2026/3 "2026-09-10T14:08:57Z")

</div>

Thank you Darryn.

Is there a release date you have in mind for the initiative you mentioned above?

---

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [September 11, 2026, 8:34am UTC](https://community.livekit.io/t/programmatic-access-to-sip-pcap-sipcallinfo-pcap-file-link-is-there-a-supported-api/2026/4 "2026-09-11T08:34:07Z")

</div>

Sorry but I wouldn’t even like to speculate publicly. I notice you are on scale so I did check internally if there was some kind of early beta you could have joined but that’s also not available I’m afraid.

---

<div class="post-metadata">

**Author:** ![samson](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@samson](https://community.livekit.io/u/samson)\
**Post date:** [September 11, 2026, 1:59pm UTC](https://community.livekit.io/t/programmatic-access-to-sip-pcap-sipcallinfo-pcap-file-link-is-there-a-supported-api/2026/5 "2026-09-11T13:59:37Z")

</div>

No worries, thank you for checking.

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/system/32/26_2.png) [@system](https://community.livekit.io/u/system)\
**Post date:** [September 26, 2026, 2:00pm UTC](https://community.livekit.io/t/programmatic-access-to-sip-pcap-sipcallinfo-pcap-file-link-is-there-a-supported-api/2026/6 "2026-09-26T14:00:25Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
