Many SIP parsers and middleboxes assume 1024 bytes is a reasonable maximum for a header line and may reject or truncate longer headers if not explicitly configured to allow more.
For inbound calls, the custom SIP headers (headers that starts with X-
or x-
) are automatically received, extracted and available in the call.custom_sip_headers
, it’s also automatically added to your collection of dynamic variables, and you can access it within your agent by stripping the X-
or x-
prefix. There’s no configuration needed for this feature.
For example, if this is the SIP header received for an inbound call:
Then here’s your call.custom_sip_headers
field, and they will be added to your dynamic variables.
If you have already specific dynamic variables with the same name for this inbound call, it will override the value received from the SIP header.
For outbound calls, you can add custom SIP headers as needed. It must starts with X-
.
For call transfers, you can also add custom SIP headers as needed. It must starts with X-
.
You can use dynamic variable for your custom SIP header value, so you can pass information extracted from the call to the receiving party.
If you are using: