Programmatic access to SIP PCAP / SIPCallInfo.pcap_file_link — is there a supported API?

Telephony
,
1

Hi team :waving_hand: — 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! :folded_hands:

2

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.

3

Thank you Darryn.

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

4

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.

5

No worries, thank you for checking.