For inbound SIP calls, artifact.pcapUrl exists but the stored object is only 24 bytes (pcap global header, no packets). Verified via HTTP HEAD: Content-Length=24 and Range GET returns only header. All four PCAP objects share the same ETag, suggesting a placeholder upload. Example calls (all endedReason=assistant-forwarded-call): - 019e06e4-66f1-799e-896d-b3ecdd7c0e92 - 019e06d4-d566-7003-9d1b-3dc28dfc9003 - 019e06d3-e4dc-7bbf-b8df-5a11e6179486 - 019e06d3-2f2d-7002-b58f-cea2d3f2b268 artifact.messages shows transfer tool go_to_frontend(destination: sip:6400@sip.vapi.ai) with tool result "Transfer initiated.", so calls are happening but PCAP capture/artifact generation for SIP seems broken (transport.provider: vapi.sip). Can someone confirm if this is a regression and ETA for fix/workaround? https://cdn.discordapp.com/attachments/1502266370958819378/1502266371151499414/VAPI_PCAP_Empty.png?ex=69ff1615&is=69fdc495&hm=fcfd7eb668154e26d8a7aeefa415d7de1f0bbce0ebfb756b6be0843ad6ab4b7e&