wx44wx/pipecat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Linking to the docs instead of full explanation.

Browse Source
This commit is contained in:
filipi87
2026-04-23 17:46:54 -03:00
parent 44756de15a
commit ce1506792e
1 changed files with 2 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
env.example
View File

@@ -216,24 +216,8 @@ WHATSAPP_APP_SECRET=...
# xAI / Grok # xAI / Grok
XAI_API_KEY=... XAI_API_KEY=...
# SmallWebRTC / aiortc
#
# PIPECAT_SCTP_MAX_CHUNK_SIZE controls the maximum SCTP DATA-chunk payload # PIPECAT_SCTP_MAX_CHUNK_SIZE controls the maximum SCTP DATA-chunk payload
# size (bytes) used by aiortc's data channel. The default is 1100. # size (bytes) used by aiortc's data channel. The default is 1100.
# # All the details here:
# When to change this: # https://docs.pipecat.ai/api-reference/server/services/transport/small-webrtc#pipecat_sctp_max_chunk_size
# Lower it if the data channel silently stalls on your network. This happens
# when aiortc's default (1200) produces UDP datagrams larger than your path
# MTU: each chunk adds ~105 bytes of SCTP + DTLS + UDP + IP headers, so
# 1200 → ~1305-byte datagrams, which exceeds the 1280-byte MTU common on
# IPv6 paths, Tailscale overlays, and many consumer VPNs. The kernel drops
# the packet with EMSGSIZE; aiortc retransmits at the same size and the
# channel stalls indefinitely. A value of 1100 (~1205-byte datagrams) fits
# any path with MTU ≥ 1210.
# Raise it only if you are on a controlled LAN (MTU 1500) and are sending
# large data-channel messages where extra fragmentation matters. Values
# above 1200 are unsafe on most internet paths.
#
# Note: this is a process-global setting (aiortc limitation) — all
# SmallWebRTC connections in the same process share the same value.
#PIPECAT_SCTP_MAX_CHUNK_SIZE=1100 #PIPECAT_SCTP_MAX_CHUNK_SIZE=1100