Thanks — I’m responding to your question about sending extra parameters in the SIP URL (e.g., sip:dnis@IP;param1=ABCD;param2=1234) and why the agent doesn’t receive them. Short answer: SIP URL parameters like ;param1=... are not forwarded to agents. The system expects SIP headers, not URL parameters. What you can do: • Have the caller/peering system add custom SIP headers (for example

X-Param1: ABCD

,

X-Param2: 1234

) on the INVITE. • On your inbound SIP trunk configuration, map those headers to participant attributes using

headers_to_attributes

(for example map

X-Param1

→

customer.param1

). • The agent can then read those values from the participant’s attributes. If you’d like, tell me: • the names of the header keys you can send (or the calling platform you’re using), and • the trunk configuration you currently have (you can paste the

headers_to_attributes

section), and I’ll suggest the exact mapping you should add. Sources: Layered Caller Verification for LiveKit SIP Calls | LiveKit | Agents telephony integration | LiveKit Documentation, with interactive elements