Skip to main content
Use custom SIP headers to carry application metadata into your answer URL or through an outbound Dial flow.

Inbound SIP headers

For an inbound call from a SIP endpoint, configure the originating SIP phone or endpoint to send custom headers whose names start with X-VH-. Vobiz includes those values in the HTTP request that fetches XML from your application. For example, your SIP endpoint can send:
Read the corresponding X-VH-Reference and X-VH-Reason values from the inbound answer request. Validate header values before using them in application logic.

Outbound Dial metadata

Set sipHeaders on <Dial> to attach metadata to a Dial flow. Vobiz exposes each pair with an X-VH- prefix in related lifecycle callbacks.
The Dial callbacks include:
Parent-level metadata applies to the Dial flow and its webhooks. A pair such as CallerId=value is only custom metadata; it does not set the PSTN caller ID. Use the parent callerId attribute for caller-ID presentation.

User SIP-leg metadata

Set sipHeaders on <User> when metadata must be attached to the SIP B-leg:
Vobiz attaches these values to the SIP B-leg and includes the corresponding X-VH- fields in answer, connected, and hangup callbacks.

Render values in your application

Vobiz does not expand application placeholders in XML attributes. Render the final value before returning XML:
Do not return unresolved placeholders such as Reference={{order_id}} unless that literal value is what you intend to send.

Next steps