Inbound calls can now turn supported `X-` SIP headers into call tags automatically, making source-provided data available for routing and reporting without adding the same SIP mapping to individual Targets.

Header names are normalized by removing the `X-` prefix and replacing hyphens with underscores. For example, `X-Custom-Route-Tag` maps to `Custom_Route_Tag`.

Source-provided ZIP and state values now remain authoritative through caller-location enrichment and can be used by ZIP/state filters and configured outbound RTB fields. A later explicit tag update still takes precedence.

Custom header names are accepted only when the corresponding Custom Tag already exists for the organization. Writable ZIP/state system tags are supported; unknown custom tags and protected system tags are ignored.

For a custom value, open Custom Tags and create the tag name that the inbound header will produce. For example, configure `Custom_Route_Tag` for an incoming `X-Custom-Route-Tag` header.

Configure the inbound SIP source to send string-valued `X-` headers. Use a supported ZIP header such as `X-ZIP` or `X-CALLER-ZIP`, and a supported state header such as `X-STATE` or `X-CALLER-STATE`, when routing should use source-provided location.

Open Targets/RTBs, then create or edit the destination whose eligibility should use the value. In Advanced Filtering, add the applicable ZIP, state, or tag condition and save.

If an outbound RTB request needs the value, use the existing ZIP, state, or matching tag field in that RTB configuration. Moja applies the normalized inbound value during call routing.

Publishers using an external voice or SIP workflow can pass ZIP, state, vertical, and other approved call context into Moja once at call entry instead of maintaining duplicate mappings across Targets.

ZIP-sensitive routing can follow the caller location supplied by the source rather than falling back to the phone number’s NPA-NXX location, reducing out-of-area routing when the caller’s number and actual location differ.

Organization-level allowlisting and protected system tags prevent arbitrary inbound headers from changing unsupported or read-only call data.