{"id":3153,"date":"2026-04-21T02:43:23","date_gmt":"2026-04-21T02:43:23","guid":{"rendered":"https:\/\/multahost.com\/blog\/?p=3153"},"modified":"2026-04-21T02:50:55","modified_gmt":"2026-04-21T02:50:55","slug":"vos3000-sip-privacy-header","status":"publish","type":"post","link":"https:\/\/multahost.com\/blog\/vos3000-sip-privacy-header\/","title":{"rendered":"VOS3000 SIP Privacy Header: Essential Caller ID Protection Guide"},"content":{"rendered":"\n<h1 class=\"wp-block-heading\" id=\"vos-3000-sip-privacy-header-essential-caller-id-protection-guide\">VOS3000 SIP Privacy Header: Essential Caller ID Protection Guide<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd10 Have you ever needed to protect caller identity on your VOS3000 softswitch \u2014 but found yourself confused by the three different privacy modes and how they interact with per-gateway settings? The <strong>VOS3000 SIP privacy header<\/strong> is the key to controlling exactly how caller ID information is exposed or hidden in your SIP signaling. Configured via <strong>SS_SIP_USER_AGENT_PRIVACY<\/strong>, this parameter determines whether VOS3000 includes a Privacy header in outbound SIP messages and what value that header carries. \ud83d\udee1\ufe0f<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udcde Whether you are managing wholesale VoIP routes that require caller ID hiding, enterprise PBX trunks with privacy requirements, or regulatory compliance for caller identification, understanding the VOS3000 SIP privacy header is essential. The global parameter controls the default behavior, while per-gateway settings on Routing Gateways and Mapping Gateways give you granular control over each interconnect. This guide covers every aspect \u2014 from the three global modes (Ignore\/Id\/None) to per-gateway Privacy, P-Asserted-Identity, and P-Preferred-Identity configuration. \ud83c\udfaf<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd27 We will reference only official VOS3000 2.1.9.07 manual data \u2014 no guesses, no fabricated values. Let&#8217;s dive in! \ud83d\udca1<\/p>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Table of Contents<\/h2><nav><ul><li><a href=\"#vos-3000-sip-privacy-header-essential-caller-id-protection-guide\">VOS3000 SIP Privacy Header: Essential Caller ID Protection Guide<\/a><ul><li><a href=\"#\ud83d\udd10-what-is-vos-3000-sip-privacy-header\">\ud83d\udd10 What Is VOS3000 SIP Privacy Header?<\/a><ul><li><a href=\"#\ud83c\udfaf-why-vos-3000-sip-privacy-header-matters\">\ud83c\udfaf Why VOS3000 SIP Privacy Header Matters<\/a><\/li><\/ul><\/li><li><a href=\"#\u2699\ufe0f-vos-3000-sip-privacy-header-modes-explained\">\u2699\ufe0f VOS3000 SIP Privacy Header Modes Explained<\/a><ul><li><a href=\"#\ud83d\udce1-sip-message-examples-per-mode\">\ud83d\udce1 SIP Message Examples Per Mode<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udda5\ufe0f-per-gateway-vos-3000-sip-privacy-settings-routing-gateway\">\ud83d\udda5\ufe0f Per-Gateway VOS3000 SIP Privacy Settings (Routing Gateway)<\/a><ul><li><a href=\"#\ud83d\udee1\ufe0f-routing-gateway-privacy-options-in-detail\">\ud83d\udee1\ufe0f Routing Gateway Privacy Options in Detail<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udccb-p-asserted-identity-and-p-preferred-identity-headers\">\ud83d\udccb P-Asserted-Identity and P-Preferred-Identity Headers<\/a><ul><li><a href=\"#\ud83d\udcde-caller-dial-plan-for-p-asserted-identity\">\ud83d\udcde Caller Dial Plan for P-Asserted-Identity<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udd04-per-gateway-vos-3000-sip-privacy-mapping-gateway\">\ud83d\udd04 Per-Gateway VOS3000 SIP Privacy Header (Mapping Gateway)<\/a><\/li><li><a href=\"#\ud83d\udd17-related-parameter-ss-sip-e-164-display-from\">\ud83d\udd17 Related Parameter: SS_SIP_E164_DISPLAY_FROM<\/a><\/li><li><a href=\"#\ud83d\udd27-step-by-step-vos-3000-sip-privacy-header-configuration\">\ud83d\udd27 Step-by-Step VOS3000 SIP Privacy Header Configuration<\/a><ul><li><a href=\"#step-1-configure-global-ss-sip-user-agent-privacy-\ud83d\udccb\">Step 1: Configure Global SS_SIP_USER_AGENT_PRIVACY \ud83d\udccb<\/a><\/li><li><a href=\"#step-2-configure-per-gateway-privacy-on-routing-gateways-\ud83d\udda5\ufe0f\">Step 2: Configure Per-Gateway Privacy on Routing Gateways \ud83d\udda5\ufe0f<\/a><\/li><li><a href=\"#step-3-configure-mapping-gateway-privacy-if-applicable-\ud83d\udd04\">Step 3: Configure Mapping Gateway Privacy (If Applicable) \ud83d\udd04<\/a><\/li><li><a href=\"#step-4-verify-with-sip-debug-\ud83d\udd0d\">Step 4: Verify with SIP Debug \ud83d\udd0d<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udcca-vos-3000-sip-privacy-header-best-practices-by-deployment\">\ud83d\udcca VOS3000 SIP Privacy Header Best Practices by Deployment<\/a><\/li><li><a href=\"#\ud83d\udee1\ufe0f-common-vos-3000-sip-privacy-header-problems-and-solutions\">\ud83d\udee1\ufe0f Common VOS3000 SIP Privacy Header Problems and Solutions<\/a><ul><li><a href=\"#\u274c-problem-1-caller-id-not-hidden-despite-privacy-id\">\u274c Problem 1: Caller ID Not Hidden Despite Privacy: id<\/a><\/li><li><a href=\"#\u274c-problem-2-privacy-header-not-preserved-across-mapping-gateways\">\u274c Problem 2: Privacy Header Not Preserved Across Mapping Gateways<\/a><\/li><li><a href=\"#\u274c-problem-3-termination-provider-rejects-calls-without-pai\">\u274c Problem 3: Termination Provider Rejects Calls Without PAI<\/a><\/li><li><a href=\"#\u274c-problem-4-confusion-between-global-and-per-gateway-privacy-settings\">\u274c Problem 4: Confusion Between Global and Per-Gateway Privacy Settings<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udccb-complete-vos-3000-sip-privacy-parameter-quick-reference\">\ud83d\udccb Complete VOS3000 SIP Privacy Header Parameter Quick Reference<\/a><\/li><li><a href=\"#\ud83d\udca1-vos-3000-sip-privacy-header-configuration-checklist\">\ud83d\udca1 VOS3000 SIP Privacy Header Configuration Checklist<\/a><\/li><li><a href=\"#\u2753-frequently-asked-questions\">\u2753 Frequently Asked Questions<\/a><ul><li><a href=\"#\u2753-what-is-the-default-vos-3000-sip-privacy-header-setting\">\u2753 What is the default VOS3000 SIP privacy header setting?<\/a><\/li><li><a href=\"#\u2753-what-is-the-difference-between-privacy-id-and-privacy-none\">\u2753 What is the difference between Privacy: id and Privacy: none?<\/a><\/li><li><a href=\"#\u2753-how-do-per-gateway-privacy-settings-interact-with-ss-sip-user-agent-privacy\">\u2753 How do per-gateway Privacy settings interact with SS_SIP_USER_AGENT_PRIVACY?<\/a><\/li><li><a href=\"#\u2753-when-should-i-use-the-passthrough-option-for-privacy\">\u2753 When should I use the Passthrough option for Privacy?<\/a><\/li><li><a href=\"#\u2753-do-i-need-p-asserted-identity-when-using-privacy-id\">\u2753 Do I need P-Asserted-Identity when using Privacy: id?<\/a><\/li><li><a href=\"#\u2753-what-does-support-privacy-on-mapping-gateway-do\">\u2753 What does Support Privacy on Mapping Gateway do?<\/a><\/li><li><a href=\"#\u2753-how-do-i-troubleshoot-vos-3000-sip-privacy-header-issues\">\u2753 How do I troubleshoot VOS3000 SIP privacy header issues?<\/a><\/li><\/ul><\/li><li><a href=\"#\ud83d\udcde-need-expert-help-with-vos-3000-sip-privacy-header\">\ud83d\udcde Need Expert Help with VOS3000 SIP Privacy Header?<\/a><\/li><li><a href=\"#\ud83d\udcda-related-resources\">\ud83d\udcda Related Resources &#8211; VOS3000 SIP Privacy Header<\/a><\/li><li><a href=\"#\ud83d\udcde-need-call-center-setup-support\">\ud83d\udcde Need Professional VOS3000 Setup Support?<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udd10-what-is-vos-3000-sip-privacy-header\">\ud83d\udd10 What Is VOS3000 SIP Privacy Header?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udee1\ufe0f The <strong>VOS3000 SIP privacy header<\/strong> controls whether VOS3000 includes a <strong>Privacy<\/strong> header in SIP messages sent by registered user agents. The Privacy header, defined in <strong>RFC 3323<\/strong>, signals to downstream entities how the caller&#8217;s identity should be handled \u2014 specifically whether the caller ID should be hidden from the called party or displayed normally. \ud83d\udcde<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udccb This parameter is governed by <strong>SS_SIP_USER_AGENT_PRIVACY<\/strong> with a default value of <strong>Ignore<\/strong>. Here is the official reference from the VOS3000 2.1.9.07 manual:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Attribute<\/th><th class=\"has-text-align-left\" data-align=\"left\">Value<\/th><\/tr><tr><td>\ud83d\udccc Parameter Name<\/td><td>SS_SIP_USER_AGENT_PRIVACY<\/td><\/tr><tr><td>\ud83d\udd22 Default Value<\/td><td>Ignore<\/td><\/tr><tr><td>\ud83d\udcdd Description<\/td><td>Privacy Setting for Register User<\/td><\/tr><tr><td>\u2699\ufe0f Options<\/td><td>Ignore \/ Id \/ None<\/td><\/tr><tr><td>\ud83d\udccd Navigation<\/td><td>Operation management \u2192 Softswitch management \u2192 Additional settings \u2192 SIP parameter<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udca1 <strong>Key insight:<\/strong> The default of &#8220;Ignore&#8221; means VOS3000 does NOT include any Privacy header in outbound SIP messages. This is the most common setting for standard VoIP deployments where caller ID presentation is the default behavior. Only when you change this to &#8220;Id&#8221; or &#8220;None&#8221; will VOS3000 actively insert a Privacy header.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83c\udfaf-why-vos-3000-sip-privacy-header-matters\">\ud83c\udfaf Why VOS3000 SIP Privacy Header Matters<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\u26a0\ufe0f Without proper privacy header configuration, several problems can occur:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\ud83d\udd13 <strong>Unintended caller ID exposure:<\/strong> Sensitive caller numbers may be visible to downstream providers or called parties when they should be hidden<\/li>\n\n\n\n<li>\ud83d\udccb <strong>Regulatory non-compliance:<\/strong> Many jurisdictions require caller ID blocking capability; without Privacy headers, you cannot honor user privacy requests<\/li>\n\n\n\n<li>\ud83d\udeab <strong>Call rejection by carriers:<\/strong> Some carriers reject calls without proper privacy indicators when the calling party has requested anonymity<\/li>\n\n\n\n<li>\ud83d\udd04 <strong>Inconsistent privacy behavior:<\/strong> Without per-gateway control, privacy settings are &#8220;all or nothing&#8221; across all interconnects<\/li>\n\n\n\n<li>\ud83d\udce1 <strong>Identity header mismatch:<\/strong> Privacy header must be coordinated with P-Asserted-Identity and P-Preferred-Identity headers for consistent caller identification<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\u2699\ufe0f-vos-3000-sip-privacy-header-modes-explained\">\u2699\ufe0f VOS3000 SIP Privacy Header Modes Explained<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udcca The <strong>SS_SIP_USER_AGENT_PRIVACY<\/strong> parameter offers three distinct modes, each producing a different SIP signaling behavior. Understanding exactly what each mode does is critical for proper configuration. \ud83d\udd11<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Mode<\/th><th class=\"has-text-align-left\" data-align=\"left\">SIP Header Output<\/th><th class=\"has-text-align-left\" data-align=\"left\">Meaning<\/th><th class=\"has-text-align-left\" data-align=\"left\">Use Case<\/th><\/tr><tr><td>\ud83d\udeab Ignore (Default)<\/td><td>No Privacy field<\/td><td>VOS3000 does not add any Privacy header \u2014 caller ID is presented normally<\/td><td>Standard VoIP \u2014 caller ID shown to called party<\/td><\/tr><tr><td>\ud83d\udd10 Id<\/td><td>Privacy: id<\/td><td>Requests identity privacy \u2014 the caller ID should be hidden from the called party but available to trusted network entities<\/td><td>Caller ID blocking \u2014 caller requested privacy<\/td><\/tr><tr><td>\ud83d\udd13 None<\/td><td>Privacy: none<\/td><td>Explicitly states no privacy is requested \u2014 caller ID may be displayed<\/td><td>Explicit caller ID presentation \u2014 overrides network defaults<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd11 <strong>Critical distinction:<\/strong> &#8220;Privacy: id&#8221; and &#8220;Privacy: none&#8221; are NOT the same as omitting the header entirely. According to RFC 3323, the absence of a Privacy header means no privacy preference is expressed (the network decides), while &#8220;Privacy: none&#8221; explicitly declares that no privacy is requested. &#8220;Privacy: id&#8221; requests that the calling user&#8217;s identity be kept private from the called party. \ud83d\udce1<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udce1-sip-message-examples-per-mode\">\ud83d\udce1 SIP Message Examples Per Mode<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">\ud83d\udcde VOS3000 SIP Privacy Header \u2014 Message Examples:\n\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n\ud83d\udeab Mode: Ignore (Default) \u2014 No Privacy header\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\nINVITE sip:bob@example.com SIP\/2.0\nVia: SIP\/2.0\/UDP 192.168.1.1:5060\nFrom: \"Alice\" &lt;sip:alice@example.com&gt;;tag=1234\nTo: &lt;sip:bob@example.com&gt;\nCall-ID: abc123@example.com\nCSeq: 1 INVITE\nContent-Type: application\/sdp\nContent-Length: ...\n  \u2190 No Privacy header present\n\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n\ud83d\udd10 Mode: Id \u2014 Privacy: id header added\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\nINVITE sip:bob@example.com SIP\/2.0\nVia: SIP\/2.0\/UDP 192.168.1.1:5060\nFrom: \"Anonymous\" &lt;sip:anonymous@example.com&gt;;tag=1234\nTo: &lt;sip:bob@example.com&gt;\nPrivacy: id\nCall-ID: abc123@example.com\nCSeq: 1 INVITE\nContent-Type: application\/sdp\nContent-Length: ...\n  \u2190 Privacy: id \u2014 caller identity hidden\n\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n\ud83d\udd13 Mode: None \u2014 Privacy: none header added\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\nINVITE sip:bob@example.com SIP\/2.0\nVia: SIP\/2.0\/UDP 192.168.1.1:5060\nFrom: \"Alice\" &lt;sip:alice@example.com&gt;;tag=1234\nTo: &lt;sip:bob@example.com&gt;\nPrivacy: none\nCall-ID: abc123@example.com\nCSeq: 1 INVITE\nContent-Type: application\/sdp\nContent-Length: ...\n  \u2190 Privacy: none \u2014 no privacy requested\n<\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udda5\ufe0f-per-gateway-vos-3000-sip-privacy-settings-routing-gateway\">\ud83d\udda5\ufe0f Per-Gateway VOS3000 SIP Privacy Settings (Routing Gateway)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd27 While <strong>SS_SIP_USER_AGENT_PRIVACY<\/strong> controls the global default, VOS3000 provides powerful per-gateway privacy controls on Routing Gateways. These settings are found in <strong>Routing Gateway &gt; Additional settings &gt; Protocol &gt; SIP<\/strong> and offer far more granularity than the global parameter alone. \ud83c\udfaf<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udca1 The per-gateway settings include not just the Privacy header, but also the <strong>P-Preferred-Identity<\/strong> and <strong>P-Asserted-Identity<\/strong> headers \u2014 both defined in <strong>RFC 3325<\/strong>. These identity headers work together with the Privacy header to provide a complete caller identification and privacy framework. \ud83d\udccb<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Setting<\/th><th class=\"has-text-align-left\" data-align=\"left\">Options<\/th><th class=\"has-text-align-left\" data-align=\"left\">Description<\/th><\/tr><tr><td>\ud83d\udee1\ufe0f Privacy<\/td><td>None \/ Passthrough \/ Id<\/td><td>SIP Privacy header \u2014 controls caller ID privacy for this gateway<\/td><\/tr><tr><td>\ud83d\udc64 P-Preferred-Identity<\/td><td>None \/ Passthrough \/ Caller<\/td><td>SIP P-Preferred-Identity header \u2014 preferred identity for the caller<\/td><\/tr><tr><td>\ud83d\udccb P-Asserted-Identity<\/td><td>None \/ Passthrough \/ Caller<\/td><td>SIP P-Asserted-Identity header \u2014 asserted identity for the caller<\/td><\/tr><tr><td>\ud83d\udcde Caller dial plan<\/td><td>Dial plan selection<\/td><td>Dial plans for the caller number in &#8220;P-Asserted-Identity&#8221; field<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udee1\ufe0f-routing-gateway-privacy-options-in-detail\">\ud83d\udee1\ufe0f Routing Gateway Privacy Options in Detail<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udcca The per-gateway <strong>Privacy<\/strong> setting on Routing Gateways provides three options that differ from the global SS_SIP_USER_AGENT_PRIVACY modes. Here is what each option does: \ud83d\udd0d<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Option<\/th><th class=\"has-text-align-left\" data-align=\"left\">SIP Header Effect<\/th><th class=\"has-text-align-left\" data-align=\"left\">Behavior<\/th><th class=\"has-text-align-left\" data-align=\"left\">When to Use<\/th><\/tr><tr><td>\ud83d\udeab None<\/td><td>No Privacy field added<\/td><td>VOS3000 does not add any Privacy header to outbound INVITE messages via this gateway<\/td><td>Standard termination \u2014 caller ID presented normally<\/td><\/tr><tr><td>\ud83d\udd04 Passthrough<\/td><td>Pass through privacy field<\/td><td>VOS3000 forwards any existing Privacy header from the incoming call leg to the outbound leg via this gateway<\/td><td>Transparent proxy \u2014 honor upstream privacy requests<\/td><\/tr><tr><td>\ud83d\udd10 Id<\/td><td>Add Privacy: id header<\/td><td>VOS3000 actively adds &#8220;Privacy: id&#8221; to outbound INVITE messages via this gateway<\/td><td>Force caller ID hiding on this gateway<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udca1 <strong>Important:<\/strong> The Passthrough option is particularly powerful for wholesale VoIP providers. When a downstream carrier sends a call with &#8220;Privacy: id&#8221; and you need to forward that call to a termination provider, Passthrough ensures the privacy request is honored end-to-end. Without Passthrough, the Privacy header would be dropped and the caller ID could be exposed. For more on SIP call flow, see our <a href=\"https:\/\/multahost.com\/blog\/vos3000-sip-call-flow\/\">SIP call flow guide<\/a>. \ud83d\udce1<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udccb-p-asserted-identity-and-p-preferred-identity-headers\">\ud83d\udccb P-Asserted-Identity and P-Preferred-Identity Headers<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udc64 The <strong>P-Asserted-Identity (PAI)<\/strong> and <strong>P-Preferred-Identity (PPI)<\/strong> headers work hand-in-hand with the VOS3000 SIP privacy header. While the Privacy header controls whether the caller ID should be hidden, the PAI and PPI headers carry the actual caller identity information within the trusted network. \ud83d\udd10<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83c\udfaf For a deep dive into PAI configuration, see our dedicated <a href=\"https:\/\/multahost.com\/blog\/vos3000-p-asserted-identity-caller-id\/\">VOS3000 P-Asserted-Identity caller ID guide<\/a>. Below is the per-gateway reference for both headers:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Header<\/th><th class=\"has-text-align-left\" data-align=\"left\">Option<\/th><th class=\"has-text-align-left\" data-align=\"left\">SIP Effect<\/th><th class=\"has-text-align-left\" data-align=\"left\">Use Case<\/th><\/tr><tr><td>\ud83d\udccb P-Asserted-Identity<\/td><td>None<\/td><td>No PAI header added<\/td><td>Provider does not require PAI<\/td><\/tr><tr><td>\ud83d\udccb P-Asserted-Identity<\/td><td>Passthrough<\/td><td>Forward existing PAI header from upstream<\/td><td>Transparent \u2014 forward caller identity<\/td><\/tr><tr><td>\ud83d\udccb P-Asserted-Identity<\/td><td>Caller<\/td><td>Add PAI header with caller number<\/td><td>Provider requires PAI for caller identification<\/td><\/tr><tr><td>\ud83d\udc64 P-Preferred-Identity<\/td><td>None<\/td><td>No PPI header added<\/td><td>Standard \u2014 no PPI needed<\/td><\/tr><tr><td>\ud83d\udc64 P-Preferred-Identity<\/td><td>Passthrough<\/td><td>Forward existing PPI header from upstream<\/td><td>Transparent \u2014 forward preferred identity<\/td><\/tr><tr><td>\ud83d\udc64 P-Preferred-Identity<\/td><td>Caller<\/td><td>Add PPI header with caller number<\/td><td>UAC-originated calls with preferred identity<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd10 <strong>Key relationship:<\/strong> When <strong>Privacy: id<\/strong> is set and <strong>P-Asserted-Identity<\/strong> is also configured, the PAI header carries the real caller identity within the trusted network while the Privacy header instructs the network to hide this identity from the called party. The From header is typically set to &#8220;Anonymous&#8221; while the PAI contains the actual number. This is the standard pattern for caller ID blocking in SIP networks per RFC 3325. \ud83d\udce1<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\ud83d\udcde-caller-dial-plan-for-p-asserted-identity\">\ud83d\udcde Caller Dial Plan for P-Asserted-Identity<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd27 The <strong>Caller dial plan<\/strong> setting in the Routing Gateway SIP configuration determines how the caller number is formatted in the P-Asserted-Identity field. This is essential when the termination provider requires a specific number format (e.g., E.164 with country code, or local format without country code). The dial plan transforms the caller number before it is placed in the PAI header. \ud83d\udccb<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udca1 For comprehensive caller ID management including dial plans and number formatting, refer to our <a href=\"https:\/\/multahost.com\/blog\/vos3000-caller-id-management-complete\/\">VOS3000 caller ID management guide<\/a>. \ud83c\udfaf<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udd04-per-gateway-vos-3000-sip-privacy-mapping-gateway\">\ud83d\udd04 Per-Gateway VOS3000 SIP Privacy Header (Mapping Gateway)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udda5\ufe0f In addition to Routing Gateway settings, VOS3000 also provides privacy control on the <strong>Mapping Gateway<\/strong> side. This is configured in <strong>Mapping Gateway &gt; Additional settings &gt; Protocol &gt; SIP<\/strong>. \ud83d\udd27<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Setting<\/th><th class=\"has-text-align-left\" data-align=\"left\">Description<\/th><\/tr><tr><td>\ud83d\udee1\ufe0f Support Privacy<\/td><td>Pass through mapping gateway private domain \u2014 forwards Privacy header through the mapping gateway<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udca1 <strong>What this does:<\/strong> When <strong>Support Privacy<\/strong> is enabled on a Mapping Gateway, VOS3000 passes through the Privacy header from the originating side to the routing side through the mapping gateway&#8217;s private domain. This ensures that privacy requests are preserved across the mapping gateway boundary. If disabled, the Privacy header may be stripped when the call traverses the mapping gateway. \ud83d\udce1<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83c\udfaf <strong>When to enable:<\/strong> Enable Support Privacy on Mapping Gateways when you need end-to-end privacy header preservation across multiple network domains. This is critical for wholesale VoIP providers who need to honor upstream privacy requests when routing calls through mapping gateways. For more about gateway configuration, see our <a href=\"https:\/\/multahost.com\/blog\/vos3000-gateway-configuration-routing-mapping\/\">gateway configuration guide<\/a>. \ud83d\udd17<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udd17-related-parameter-ss-sip-e-164-display-from\">\ud83d\udd17 Related Parameter: SS_SIP_E164_DISPLAY_FROM<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udcca The <strong>SS_SIP_E164_DISPLAY_FROM<\/strong> parameter is closely related to the VOS3000 SIP privacy header. While the Privacy header controls whether the caller ID is hidden, SS_SIP_E164_DISPLAY_FROM controls how the caller&#8217;s display information appears in the SIP From header. \ud83d\udccb<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Attribute<\/th><th class=\"has-text-align-left\" data-align=\"left\">Value<\/th><\/tr><tr><td>\ud83d\udccc Parameter Name<\/td><td>SS_SIP_E164_DISPLAY_FROM<\/td><\/tr><tr><td>\ud83d\udd22 Default Value<\/td><td>Ignore<\/td><\/tr><tr><td>\ud83d\udcdd Description<\/td><td>Mode of SIP display information<\/td><\/tr><tr><td>\ud83d\udccd Navigation<\/td><td>Operation management \u2192 Softswitch management \u2192 Additional settings \u2192 SIP parameter<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udca1 <strong>Why it matters:<\/strong> When SS_SIP_USER_AGENT_PRIVACY is set to &#8220;Id&#8221; (Privacy: id), the From header display name is typically changed to &#8220;Anonymous.&#8221; The SS_SIP_E164_DISPLAY_FROM parameter controls the display information format in the From header independently \u2014 it determines whether the display portion uses E.164 format, the original format, or is ignored. Both parameters work together to control how caller identity is presented in SIP signaling. For the complete parameter reference, see our <a href=\"https:\/\/multahost.com\/blog\/vos3000-parameter-description\/\">VOS3000 parameter description<\/a> and <a href=\"https:\/\/multahost.com\/blog\/vos3000-system-parameters\/\">system parameters<\/a> guide. \ud83d\udd27<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udd27-step-by-step-vos-3000-sip-privacy-header-configuration\">\ud83d\udd27 Step-by-Step VOS3000 SIP Privacy Header Configuration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u2699\ufe0f Follow these steps to configure the VOS3000 SIP privacy header on your system:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"step-1-configure-global-ss-sip-user-agent-privacy-\ud83d\udccb\">Step 1: Configure Global SS_SIP_USER_AGENT_PRIVACY \ud83d\udccb<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\ud83d\udd10 Log in to VOS3000 Client<\/li>\n\n\n\n<li>\ud83d\udccc Navigate: <strong>Operation management \u2192 Softswitch management \u2192 Additional settings \u2192 SIP parameter<\/strong><\/li>\n\n\n\n<li>\ud83d\udd0d Locate <strong>SS_SIP_USER_AGENT_PRIVACY<\/strong> in the parameter list<\/li>\n\n\n\n<li>\u270f\ufe0f Select the desired mode: <strong>Ignore<\/strong> \/ <strong>Id<\/strong> \/ <strong>None<\/strong><\/li>\n\n\n\n<li>\ud83d\udcbe Save and apply the changes<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"step-2-configure-per-gateway-privacy-on-routing-gateways-\ud83d\udda5\ufe0f\">Step 2: Configure Per-Gateway Privacy on Routing Gateways \ud83d\udda5\ufe0f<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\ud83d\udccc Navigate: <strong>Routing Gateway \u2192 [Select Gateway] \u2192 Additional settings \u2192 Protocol \u2192 SIP<\/strong><\/li>\n\n\n\n<li>\ud83d\udee1\ufe0f Set <strong>Privacy<\/strong>: None \/ Passthrough \/ Id<\/li>\n\n\n\n<li>\ud83d\udc64 Set <strong>P-Preferred-Identity<\/strong>: None \/ Passthrough \/ Caller<\/li>\n\n\n\n<li>\ud83d\udccb Set <strong>P-Asserted-Identity<\/strong>: None \/ Passthrough \/ Caller<\/li>\n\n\n\n<li>\ud83d\udcde Select <strong>Caller dial plan<\/strong> for PAI number formatting (if P-Asserted-Identity is set to Caller)<\/li>\n\n\n\n<li>\ud83d\udcbe Save gateway settings<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"step-3-configure-mapping-gateway-privacy-if-applicable-\ud83d\udd04\">Step 3: Configure Mapping Gateway Privacy (If Applicable) \ud83d\udd04<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\ud83d\udccc Navigate: <strong>Mapping Gateway \u2192 [Select Gateway] \u2192 Additional settings \u2192 Protocol \u2192 SIP<\/strong><\/li>\n\n\n\n<li>\ud83d\udee1\ufe0f Enable <strong>Support Privacy<\/strong> to pass through privacy fields<\/li>\n\n\n\n<li>\ud83d\udcbe Save mapping gateway settings<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"step-4-verify-with-sip-debug-\ud83d\udd0d\">Step 4: Verify with SIP Debug \ud83d\udd0d<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udcdd After configuration, verify the privacy headers are working correctly using SIP debug tools. For comprehensive debugging instructions, see our <a href=\"https:\/\/multahost.com\/blog\/vos3000-troubleshooting-guide-2026\/\">VOS3000 troubleshooting guide<\/a>.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">\ud83d\udcde VOS3000 SIP Privacy Header \u2014 Verification Flow:\n\nCaller \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500 VOS3000 \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500 Termination Gateway\n  \u2502                      \u2502                          \u2502\n  \u2502\u2500\u2500 INVITE \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u25ba\u2502                          \u2502\n  \u2502   From: sip:1234@... \u2502                          \u2502\n  \u2502   Privacy: id        \u2502                          \u2502\n  \u2502                      \u2502                          \u2502\n  \u2502                      \u2502\u2500\u2500 INVITE \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u25ba\u2502\n  \u2502                      \u2502   From: Anonymous@...    \u2502\n  \u2502                      \u2502   Privacy: id            \u2502  \u2190 Per-gateway Privacy=Id\n  \u2502                      \u2502   P-Asserted-Identity:   \u2502  \u2190 Per-gateway PAI=Caller\n  \u2502                      \u2502     &lt;sip:1234@domain&gt;   \u2502\n  \u2502                      \u2502                          \u2502\n  \u2502                      \u2502  \u2705 Called party sees:   \u2502\n  \u2502                      \u2502  \"Anonymous\" (From)      \u2502\n  \u2502                      \u2502  Trusted network sees:   \u2502\n  \u2502                      \u2502  1234 (PAI header)       \u2502\n<\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcca-vos-3000-sip-privacy-header-best-practices-by-deployment\">\ud83d\udcca VOS3000 SIP Privacy Header Best Practices by Deployment<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83c\udfaf Different VoIP deployment types require different privacy header configurations. Here are our recommended settings based on real-world experience: \ud83d\udca1<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Deployment Type<\/th><th class=\"has-text-align-left\" data-align=\"left\">Global Privacy<\/th><th class=\"has-text-align-left\" data-align=\"left\">Routing GW Privacy<\/th><th class=\"has-text-align-left\" data-align=\"left\">PAI Setting<\/th><th class=\"has-text-align-left\" data-align=\"left\">Rationale<\/th><\/tr><tr><td>\ud83d\udcde Wholesale VoIP<\/td><td>Ignore<\/td><td>Passthrough<\/td><td>Caller<\/td><td>Honor upstream privacy; provide PAI for caller ID delivery<\/td><\/tr><tr><td>\ud83c\udfe2 Enterprise PBX<\/td><td>Ignore<\/td><td>None or Passthrough<\/td><td>Caller<\/td><td>Present caller ID normally; PAI for carrier requirements<\/td><\/tr><tr><td>\ud83d\udd10 Privacy-required routes<\/td><td>Id<\/td><td>Id<\/td><td>Caller<\/td><td>Force Privacy: id on all calls; PAI carries real number in trusted network<\/td><\/tr><tr><td>\ud83d\udce1 SIP trunking<\/td><td>Ignore<\/td><td>Passthrough<\/td><td>Passthrough or Caller<\/td><td>Transparent privacy handling; follow upstream provider requirements<\/td><\/tr><tr><td>\ud83c\udf0d Multi-carrier routing<\/td><td>Ignore<\/td><td>Per-carrier settings<\/td><td>Per-carrier settings<\/td><td>Different carriers have different PAI and privacy requirements<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udca1 <strong>Pro tip:<\/strong> The most flexible approach is to set the global <strong>SS_SIP_USER_AGENT_PRIVACY<\/strong> to <strong>Ignore<\/strong> and then use per-gateway settings on Routing Gateways for specific privacy requirements. This way, each termination provider can have its own Privacy, PAI, and PPI settings without affecting other gateways. For call routing configuration, see our <a href=\"https:\/\/multahost.com\/blog\/vos3000-call-routing\/\">call routing guide<\/a>. \ud83d\udcca<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udee1\ufe0f-common-vos-3000-sip-privacy-header-problems-and-solutions\">\ud83d\udee1\ufe0f Common VOS3000 SIP Privacy Header Problems and Solutions<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u26a0\ufe0f Misconfigured privacy headers can cause a range of issues. Here are the most common problems and their solutions:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u274c-problem-1-caller-id-not-hidden-despite-privacy-id\">\u274c Problem 1: Caller ID Not Hidden Despite Privacy: id<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd0d <strong>Symptom:<\/strong> SS_SIP_USER_AGENT_PRIVACY is set to &#8220;Id&#8221; but the called party still sees the caller number.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udca1 <strong>Cause:<\/strong> The per-gateway Privacy setting on the Routing Gateway may be set to &#8220;None,&#8221; which overrides the global parameter. Or the termination provider is ignoring the Privacy header and reading the number from the PAI header without honoring the privacy indicator.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u2705 <strong>Solutions:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\ud83d\udd27 Verify the per-gateway Privacy setting is set to &#8220;Id&#8221; or &#8220;Passthrough&#8221; on the relevant Routing Gateway<\/li>\n\n\n\n<li>\ud83d\udccb Check that the P-Asserted-Identity header is not being sent to untrusted networks<\/li>\n\n\n\n<li>\ud83d\udce1 Capture a SIP trace to confirm the Privacy: id header is actually present in the outbound INVITE<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u274c-problem-2-privacy-header-not-preserved-across-mapping-gateways\">\u274c Problem 2: Privacy Header Not Preserved Across Mapping Gateways<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd0d <strong>Symptom:<\/strong> Privacy header is present on the originating side but missing on the termination side after the call passes through a Mapping Gateway.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udca1 <strong>Cause:<\/strong> The Mapping Gateway&#8217;s <strong>Support Privacy<\/strong> setting is not enabled, so the Privacy header is stripped during the mapping gateway traversal.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u2705 <strong>Solutions:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\ud83d\udee1\ufe0f Enable <strong>Support Privacy<\/strong> on the Mapping Gateway: Mapping Gateway > Additional settings > Protocol > SIP<\/li>\n\n\n\n<li>\ud83d\udd04 Verify the privacy field is passing through by checking SIP traces on both sides of the mapping gateway<\/li>\n\n\n\n<li>\ud83d\udccb If using multiple mapping gateways, ensure Support Privacy is enabled on all of them<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u274c-problem-3-termination-provider-rejects-calls-without-pai\">\u274c Problem 3: Termination Provider Rejects Calls Without PAI<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd0d <strong>Symptom:<\/strong> Calls to a specific termination provider are rejected with SIP 403 or 403 errors. The provider requires a P-Asserted-Identity header.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udca1 <strong>Cause:<\/strong> The P-Asserted-Identity setting on the Routing Gateway for this provider is set to &#8220;None,&#8221; so no PAI header is included in the outbound INVITE.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u2705 <strong>Solutions:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\ud83d\udccb Set P-Asserted-Identity to <strong>Caller<\/strong> on the Routing Gateway for this provider<\/li>\n\n\n\n<li>\ud83d\udcde Configure the <strong>Caller dial plan<\/strong> to format the number as required by the provider (e.g., E.164 with + prefix)<\/li>\n\n\n\n<li>\ud83d\udd10 If privacy is also required, keep Privacy set to &#8220;Id&#8221; \u2014 the PAI header will carry the number in the trusted network while the From header shows &#8220;Anonymous&#8221;<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u274c-problem-4-confusion-between-global-and-per-gateway-privacy-settings\">\u274c Problem 4: Confusion Between Global and Per-Gateway Privacy Settings<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd0d <strong>Symptom:<\/strong> Privacy behavior is inconsistent \u2014 some gateways hide caller ID and others do not, and you are unsure which setting is in control.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udca1 <strong>Cause:<\/strong> Both the global SS_SIP_USER_AGENT_PRIVACY and per-gateway Privacy settings exist, and they can conflict or produce unexpected results when not coordinated.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u2705 <strong>Solutions:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u2699\ufe0f Set the global SS_SIP_USER_AGENT_PRIVACY to <strong>Ignore<\/strong> as a baseline<\/li>\n\n\n\n<li>\ud83d\udda5\ufe0f Use per-gateway Privacy settings on Routing Gateways to control privacy for each interconnect independently<\/li>\n\n\n\n<li>\ud83d\udcdd Document which gateways have which privacy settings for easy troubleshooting<\/li>\n\n\n\n<li>\ud83d\udd0d For security best practices, see our <a href=\"https:\/\/multahost.com\/blog\/vos3000-security\/\">VOS3000 security guide<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udccb-complete-vos-3000-sip-privacy-parameter-quick-reference\">\ud83d\udccb Complete VOS3000 SIP Privacy Header Parameter Quick Reference<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udcca Here is the complete reference table for all privacy-related parameters and settings in VOS3000:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Parameter \/ Setting<\/th><th class=\"has-text-align-left\" data-align=\"left\">Default<\/th><th class=\"has-text-align-left\" data-align=\"left\">Location<\/th><th class=\"has-text-align-left\" data-align=\"left\">Scope<\/th><\/tr><tr><td><strong>SS_SIP_USER_AGENT_PRIVACY<\/strong><\/td><td>Ignore<\/td><td>SIP parameter (global)<\/td><td>All registered users<\/td><\/tr><tr><td>SS_SIP_E164_DISPLAY_FROM<\/td><td>Ignore<\/td><td>SIP parameter (global)<\/td><td>All SIP display information<\/td><\/tr><tr><td>Privacy (Routing GW)<\/td><td>\u2014<\/td><td>Routing GW &gt; SIP<\/td><td>Per-routing-gateway<\/td><\/tr><tr><td>P-Asserted-Identity (Routing GW)<\/td><td>\u2014<\/td><td>Routing GW &gt; SIP<\/td><td>Per-routing-gateway<\/td><\/tr><tr><td>P-Preferred-Identity (Routing GW)<\/td><td>\u2014<\/td><td>Routing GW &gt; SIP<\/td><td>Per-routing-gateway<\/td><\/tr><tr><td>Caller dial plan (Routing GW)<\/td><td>\u2014<\/td><td>Routing GW &gt; SIP<\/td><td>Per-routing-gateway (PAI format)<\/td><\/tr><tr><td>Support Privacy (Mapping GW)<\/td><td>\u2014<\/td><td>Mapping GW &gt; SIP<\/td><td>Per-mapping-gateway<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udccd Global SIP parameters are located at: <strong>Navigation \u2192 Operation management \u2192 Softswitch management \u2192 Additional settings \u2192 SIP parameter<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udca1-vos-3000-sip-privacy-header-configuration-checklist\">\ud83d\udca1 VOS3000 SIP Privacy Header Configuration Checklist<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u2705 Use this checklist when deploying or tuning your VOS3000 SIP privacy header settings:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Check<\/th><th class=\"has-text-align-left\" data-align=\"left\">Action<\/th><th class=\"has-text-align-left\" data-align=\"left\">Status<\/th><\/tr><tr><td>\ud83d\udccc 1<\/td><td>Set SS_SIP_USER_AGENT_PRIVACY to appropriate mode (Ignore\/Id\/None) for your deployment<\/td><td>\u2610<\/td><\/tr><tr><td>\ud83d\udccc 2<\/td><td>Configure per-gateway Privacy on each Routing Gateway (None\/Passthrough\/Id)<\/td><td>\u2610<\/td><\/tr><tr><td>\ud83d\udccc 3<\/td><td>Set P-Asserted-Identity on each Routing Gateway per provider requirements<\/td><td>\u2610<\/td><\/tr><tr><td>\ud83d\udccc 4<\/td><td>Configure P-Preferred-Identity where needed (typically for UAC-originated calls)<\/td><td>\u2610<\/td><\/tr><tr><td>\ud83d\udccc 5<\/td><td>Select Caller dial plan for PAI number formatting on each Routing Gateway<\/td><td>\u2610<\/td><\/tr><tr><td>\ud83d\udccc 6<\/td><td>Enable Support Privacy on Mapping Gateways that need to preserve privacy headers<\/td><td>\u2610<\/td><\/tr><tr><td>\ud83d\udccc 7<\/td><td>Verify with SIP trace that Privacy and identity headers appear correctly in outbound INVITE<\/td><td>\u2610<\/td><\/tr><tr><td>\ud83d\udccc 8<\/td><td>Review SS_SIP_E164_DISPLAY_FROM for consistent From header display behavior<\/td><td>\u2610<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\u2753-frequently-asked-questions\">\u2753 Frequently Asked Questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-what-is-the-default-vos-3000-sip-privacy-header-setting\">\u2753 What is the default VOS3000 SIP privacy header setting?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udee1\ufe0f The default VOS3000 SIP privacy header setting is <strong>Ignore<\/strong>, configured via the <strong>SS_SIP_USER_AGENT_PRIVACY<\/strong> parameter. When set to Ignore, VOS3000 does not include any Privacy header in SIP messages \u2014 caller ID is presented normally. The other options are &#8220;Id&#8221; (adds Privacy: id to hide caller identity) and &#8220;None&#8221; (adds Privacy: none to explicitly indicate no privacy requested). \ud83d\udd14<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-what-is-the-difference-between-privacy-id-and-privacy-none\">\u2753 What is the difference between Privacy: id and Privacy: none?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udcca <strong>Privacy: id<\/strong> requests that the calling user&#8217;s identity be kept private from the called party \u2014 the From header typically shows &#8220;Anonymous&#8221; while the real number is carried in the P-Asserted-Identity header within the trusted network. <strong>Privacy: none<\/strong> explicitly states that no privacy is requested and the caller ID may be displayed. The key difference from having no Privacy header at all is that &#8220;Privacy: none&#8221; is an explicit declaration, while the absence of a header means no privacy preference is expressed. Per RFC 3323, these are semantically different. \ud83d\udce1<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-how-do-per-gateway-privacy-settings-interact-with-ss-sip-user-agent-privacy\">\u2753 How do per-gateway Privacy settings interact with SS_SIP_USER_AGENT_PRIVACY?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd27 The global <strong>SS_SIP_USER_AGENT_PRIVACY<\/strong> controls the default privacy behavior for all registered user agents. The per-gateway Privacy settings on Routing Gateways provide more granular control for each termination interconnect. The recommended approach is to set the global parameter to <strong>Ignore<\/strong> and use per-gateway settings for specific requirements \u2014 this gives you the most flexibility. Per-gateway settings take precedence over the global default for calls routed through that specific gateway. \ud83d\udda5\ufe0f<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-when-should-i-use-the-passthrough-option-for-privacy\">\u2753 When should I use the Passthrough option for Privacy?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd04 Use <strong>Passthrough<\/strong> when you need to preserve an existing Privacy header from an upstream provider. For example, if a wholesale customer sends a call with &#8220;Privacy: id&#8221; and you need to forward that call to a termination provider while honoring the privacy request, set the Routing Gateway&#8217;s Privacy to Passthrough. This is the most common setting for wholesale VoIP providers who act as a transit between originating and terminating networks. Without Passthrough, the Privacy header would be dropped and the caller ID could be exposed unintentionally. \ud83d\udcde<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-do-i-need-p-asserted-identity-when-using-privacy-id\">\u2753 Do I need P-Asserted-Identity when using Privacy: id?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd10 Yes, in most cases. When <strong>Privacy: id<\/strong> is set, the From header displays &#8220;Anonymous&#8221; to the called party. However, the real caller identity still needs to be communicated within the trusted network for billing, routing, and regulatory purposes. The <strong>P-Asserted-Identity (PAI)<\/strong> header carries this information \u2014 it is visible to trusted network entities but should not be forwarded to untrusted endpoints. Setting PAI to &#8220;Caller&#8221; on the Routing Gateway ensures the real number is included in the PAI header while the Privacy header keeps it hidden from the called party. For detailed PAI configuration, see our <a href=\"https:\/\/multahost.com\/blog\/vos3000-p-asserted-identity-caller-id\/\">P-Asserted-Identity guide<\/a>. \ud83d\udccb<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-what-does-support-privacy-on-mapping-gateway-do\">\u2753 What does Support Privacy on Mapping Gateway do?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udda5\ufe0f The <strong>Support Privacy<\/strong> setting on Mapping Gateways enables the pass-through of the Privacy header across the mapping gateway&#8217;s private domain. When enabled, any Privacy header present in the incoming call leg is preserved and forwarded to the outbound routing side. When disabled, the Privacy header may be stripped when the call traverses the mapping gateway boundary. Enable this setting when you need end-to-end privacy header preservation in multi-domain deployments \u2014 especially critical for wholesale VoIP providers. \ud83d\udd04<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"\u2753-how-do-i-troubleshoot-vos-3000-sip-privacy-header-issues\">\u2753 How do I troubleshoot VOS3000 SIP privacy header issues?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd0d Start by capturing a SIP trace on both the incoming and outgoing sides of VOS3000. Verify that the Privacy header appears (or does not appear) as expected in the outbound INVITE. Check that per-gateway Privacy settings match your expectations for each Routing Gateway. If privacy headers are missing after a Mapping Gateway, verify that <strong>Support Privacy<\/strong> is enabled. For PAI-related issues, confirm the P-Asserted-Identity setting is configured to &#8220;Caller&#8221; and the Caller dial plan is correct. For detailed troubleshooting, see our <a href=\"https:\/\/multahost.com\/blog\/vos3000-troubleshooting-guide-2026\/\">VOS3000 troubleshooting guide<\/a>. For expert support, contact us on WhatsApp at <strong>+8801911119966<\/strong>. \ud83d\udcde<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcde-need-expert-help-with-vos-3000-sip-privacy-header\">\ud83d\udcde Need Expert Help with VOS3000 SIP Privacy Header?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udd27 Configuring the VOS3000 SIP privacy header correctly is essential for protecting caller identity, meeting regulatory requirements, and maintaining compatibility with termination providers. Whether you need help with global parameter tuning, per-gateway Privacy and PAI configuration, or troubleshooting caller ID exposure issues, our team is ready to assist. \ud83d\udee1\ufe0f<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udcac <strong>WhatsApp:<\/strong> <a href=\"https:\/\/wa.me\/8801911119966\" target=\"_blank\" rel=\"noopener\">+8801911119966<\/a> \u2014 Get instant support for VOS3000 SIP privacy header configuration, caller ID protection, and identity header setup. \ud83c\udf10<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcda-related-resources\">\ud83d\udcda Related Resources &#8211; VOS3000 SIP Privacy Header<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\ud83d\udd17 <a href=\"https:\/\/multahost.com\/blog\/vos3000-caller-id-management-complete\/\">VOS3000 Caller ID Management Complete Guide<\/a><\/li>\n\n\n\n<li>\ud83d\udd17 <a href=\"https:\/\/multahost.com\/blog\/vos3000-p-asserted-identity-caller-id\/\">VOS3000 P-Asserted-Identity Caller ID Guide<\/a><\/li>\n\n\n\n<li>\ud83d\udd17 <a href=\"https:\/\/multahost.com\/blog\/vos3000-sip-authentication\/\">VOS3000 SIP Authentication Guide<\/a><\/li>\n\n\n\n<li>\ud83d\udd17 <a href=\"https:\/\/multahost.com\/blog\/vos3000-sip-registration\/\">VOS3000 SIP Registration Guide<\/a><\/li>\n\n\n\n<li>\ud83d\udd17 <a href=\"https:\/\/multahost.com\/blog\/vos3000-sip-call-flow\/\">VOS3000 SIP Call Flow Guide<\/a><\/li>\n\n\n\n<li>\ud83d\udd17 <a href=\"https:\/\/multahost.com\/blog\/vos3000-parameter-description\/\">VOS3000 Parameter Description Guide<\/a><\/li>\n\n\n\n<li>\ud83d\udd17 <a href=\"https:\/\/multahost.com\/blog\/vos3000-system-parameters\/\">VOS3000 System Parameters Overview<\/a><\/li>\n\n\n\n<li>\ud83d\udd17 <a href=\"https:\/\/multahost.com\/blog\/vos3000-call-routing\/\">VOS3000 Call Routing Guide<\/a><\/li>\n\n\n\n<li>\ud83d\udd17 <a href=\"https:\/\/multahost.com\/blog\/vos3000-security\/\">VOS3000 Security Guide<\/a><\/li>\n\n\n\n<li>\ud83d\udd17 <a href=\"https:\/\/multahost.com\/blog\/vos3000-security-anti-fraud\/\">VOS3000 Security Anti-Fraud Guide<\/a><\/li>\n\n\n\n<li>\ud83d\udd17 <a href=\"https:\/\/multahost.com\/blog\/vos3000-troubleshooting-guide-2026\/\">VOS3000 Troubleshooting Guide 2026<\/a><\/li>\n\n\n\n<li>\ud83d\udd17 <a href=\"https:\/\/multahost.com\/blog\/vos3000-installation\/\">VOS3000 Installation Guide<\/a><\/li>\n\n\n\n<li>\ud83d\udd17 <a href=\"https:\/\/multahost.com\/blog\/vos3000-billing-system\/\">VOS3000 Billing System Guide<\/a><\/li>\n\n\n\n<li>\ud83c\udf10 <a href=\"https:\/\/www.vos3000.com\/downloads.php\" target=\"_blank\" rel=\"noopener\">Official VOS3000 Downloads<\/a><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udcde Still have questions about the VOS3000 SIP privacy header? Reach out on WhatsApp at <strong>+8801911119966<\/strong> \u2014 we provide professional VOS3000 installation, configuration, and support services worldwide. For official VOS3000 software downloads, visit <a href=\"https:\/\/www.vos3000.com\/downloads.php\" target=\"_blank\" rel=\"noopener\">vos3000.com<\/a>. \ud83c\udf10<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcde-need-call-center-setup-support\">\ud83d\udcde Need Professional VOS3000 Setup Support?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udcf1 <strong>WhatsApp:<\/strong> <a href=\"https:\/\/wa.me\/8801911119966\" target=\"_blank\" rel=\"noopener\">+8801911119966<\/a><br>\ud83c\udf10 <strong>Website:<\/strong> <a href=\"https:\/\/www.vos3000.com\" target=\"_blank\" rel=\"noopener\">www.vos3000.com<\/a><br>\ud83c\udf10 <strong>Blog:<\/strong> <a href=\"https:\/\/multahost.com\/blog\">multahost.com\/blog<\/a><br>\ud83d\udce5 <strong>Downloads:<\/strong> <a href=\"https:\/\/www.vos3000.com\/downloads.php\" target=\"_blank\" rel=\"noopener\">VOS3000 Downloads<\/a><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><img data-recalc-dims=\"1\" height=\"540\" width=\"809\" decoding=\"async\" src=\"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-SIP-Authentication-Retry-VOS3000-SIP-Early-Hangup-VOS3000-SIP-Session-Timer-Refresh-VOS3000-Non-Timer-Endpoint-Safety-VOS3000-SIP-NAT-Keepalive-2.png?resize=809%2C540\" alt=\"VOS3000 SIP Authentication Retry, VOS3000 SIP Early Hangup, VOS3000 SIP Session Timer Refresh, VOS3000 Non-Timer Endpoint Safety, VOS3000 SIP NAT Keepalive, VOS3000 SIP Resend Interval, VOS3000 SIP INVITE Timeout, VOS3000 SIP Call Progress Timeout, VOS3000 SIP Outbound Registration Parameters, VOS3000 SIP Privacy Header, VOS3000 SIP Routing Gateway Contact, VOS3000 SIP Publish Expire, VOS3000 SIP Display From, VOS3000 SIP Send Unregister\" title=\"\"><\/td><td><img data-recalc-dims=\"1\" height=\"540\" width=\"809\" decoding=\"async\" src=\"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-SIP-Authentication-Retry-VOS3000-SIP-Early-Hangup-VOS3000-SIP-Session-Timer-Refresh-VOS3000-Non-Timer-Endpoint-Safety-VOS3000-SIP-NAT-Keepalive-2.png?resize=809%2C540\" alt=\"VOS3000 SIP Authentication Retry, VOS3000 SIP Early Hangup, VOS3000 SIP Session Timer Refresh, VOS3000 Non-Timer Endpoint Safety, VOS3000 SIP NAT Keepalive, VOS3000 SIP Resend Interval, VOS3000 SIP INVITE Timeout, VOS3000 SIP Call Progress Timeout, VOS3000 SIP Outbound Registration Parameters, VOS3000 SIP Privacy Header, VOS3000 SIP Routing Gateway Contact, VOS3000 SIP Publish Expire, VOS3000 SIP Display From, VOS3000 SIP Send Unregister\" title=\"\"><\/td><td><img data-recalc-dims=\"1\" height=\"540\" width=\"809\" decoding=\"async\" src=\"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-SIP-Authentication-Retry-VOS3000-SIP-Early-Hangup-VOS3000-SIP-Session-Timer-Refresh-VOS3000-Non-Timer-Endpoint-Safety-VOS3000-SIP-NAT-Keepalive-2.png?resize=809%2C540\" alt=\"VOS3000 SIP Authentication Retry, VOS3000 SIP Early Hangup, VOS3000 SIP Session Timer Refresh, VOS3000 Non-Timer Endpoint Safety, VOS3000 SIP NAT Keepalive, VOS3000 SIP Resend Interval, VOS3000 SIP INVITE Timeout, VOS3000 SIP Call Progress Timeout, VOS3000 SIP Outbound Registration Parameters, VOS3000 SIP Privacy Header, VOS3000 SIP Routing Gateway Contact, VOS3000 SIP Publish Expire, VOS3000 SIP Display From, VOS3000 SIP Send Unregister\" title=\"\"><\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>Master VOS3000 SIP privacy header with SS_SIP_USER_AGENT_PRIVACY. Configure Ignore\/Id\/None modes, per-gateway Privacy, P-Asserted-Identity, and caller ID protection.<\/p>\n","protected":false},"author":1,"featured_media":3146,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[684,2,685,774,795],"tags":[8442,8366,8466,8458,8489,6085,8444,8494,8482,8452,8476,8488,8478,8456,8464,6098,8473,6888,8474,8450,6887,8470,8492,8480,6916,8446,8486,8465,8462,8479,8469,8475,8483,8454,8460,8481,8490,8448,8440,8485,8385,8471,8472,8487,8467,8477,8484,8468],"class_list":["post-3153","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vos3000-sip","category-vos3000","category-vos3000-sip-accounts","category-vos3000-sip-codec-support","category-vos3000-sip-message-settings","tag-ss_sip_user_agent_privacy","tag-vos3000-additional-settings-sip","tag-vos3000-caller-dial-plan","tag-vos3000-caller-id-blocking","tag-vos3000-caller-id-header","tag-vos3000-caller-id-management","tag-vos3000-caller-id-protection","tag-vos3000-caller-identity-protection","tag-vos3000-caller-number-privacy","tag-vos3000-caller-privacy","tag-vos3000-e164-display-from","tag-vos3000-gateway-additional-settings","tag-vos3000-gateway-privacy-settings","tag-vos3000-hide-caller-id","tag-vos3000-mapping-gateway-privacy","tag-vos3000-p-asserted-identity","tag-vos3000-p-asserted-identity-header","tag-vos3000-p-preferred-identity","tag-vos3000-p-preferred-identity-header","tag-vos3000-per-gateway-privacy","tag-vos3000-privacy-header","tag-vos3000-privacy-header-modes","tag-vos3000-privacy-header-setup","tag-vos3000-privacy-header-troubleshooting","tag-vos3000-privacy-id","tag-vos3000-privacy-none","tag-vos3000-privacy-none-vs-id","tag-vos3000-privacy-passthrough","tag-vos3000-routing-gateway-privacy","tag-vos3000-sip-call-privacy","tag-vos3000-sip-caller-identification","tag-vos3000-sip-display-from","tag-vos3000-sip-header-configuration","tag-vos3000-sip-header-privacy","tag-vos3000-sip-identity-headers","tag-vos3000-sip-identity-privacy","tag-vos3000-sip-parameter-tuning","tag-vos3000-sip-privacy-configuration","tag-vos3000-sip-privacy-header","tag-vos3000-sip-privacy-modes","tag-vos3000-sip-protocol-parameters","tag-vos3000-sip-rfc-3323","tag-vos3000-sip-rfc-3325","tag-vos3000-sip-signaling-privacy","tag-vos3000-softswitch-privacy","tag-vos3000-ss_sip_e164_display_from","tag-vos3000-voip-caller-protection","tag-vos3000-voip-privacy"],"acf":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-SIP-Call-Progress-Timeout-VOS3000-SIP-Outbound-Registration-Parameters-VOS3000-SIP-Privacy-Header-VOS3000-SIP-Routing-Gateway-Contact-VOS3000-SIP-Publish-Expire-VOS3000-SIP-Display-From.png?fit=1536%2C1024&ssl=1?v=1776736554","jetpack-related-posts":[{"id":2891,"url":"https:\/\/multahost.com\/blog\/vos3000-p-asserted-identity-caller-id\/","url_meta":{"origin":3153,"position":0},"title":"VOS3000 P-Asserted-Identity: Caller ID Manipulation Important Guide for VoIP","author":"king","date":"April 13, 2026","format":false,"excerpt":"VOS3000 P-Asserted-Identity caller ID manipulation guide. Configure PAI, Privacy, P-Preferred-Identity headers for trusted caller ID presentation and compliance.","rel":"","context":"In &quot;VOS3000&quot;","block_context":{"text":"VOS3000","link":"https:\/\/multahost.com\/blog\/category\/vos3000\/"},"img":{"alt_text":"VOS3000 P-Asserted-Identity, VOS3000 Web Manager, VOS3000 DTMF Configuration, VOS3000 Agent Account, VOS3000 Transcoding","src":"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding.png?fit=1200%2C800&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding.png?fit=1200%2C800&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding.png?fit=1200%2C800&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding.png?fit=1200%2C800&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-P-Asserted-Identity-VOS3000-Web-Manager-VOS3000-DTMF-Configuration-VOS3000-Agent-Account-VOS3000-Transcoding.png?fit=1200%2C800&ssl=1&resize=1050%2C600 3x"},"classes":[]},{"id":3163,"url":"https:\/\/multahost.com\/blog\/vos3000-sip-display\/","url_meta":{"origin":3153,"position":1},"title":"VOS3000 SIP Display From: Important E164 Caller Configuration","author":"king","date":"April 21, 2026","format":false,"excerpt":"Master VOS3000 SIP display from with SS_SIP_E164_DISPLAY_FROM. Configure E164 caller format in From header, per-gateway display modes, caller presentation, and mapping gateway number extraction.","rel":"","context":"In &quot;VOS3000&quot;","block_context":{"text":"VOS3000","link":"https:\/\/multahost.com\/blog\/category\/vos3000\/"},"img":{"alt_text":"VOS3000 SIP Authentication Retry, VOS3000 SIP Early Hangup, VOS3000 SIP Session Timer Refresh, VOS3000 Non-Timer Endpoint Safety, VOS3000 SIP NAT Keepalive, VOS3000 SIP Resend Interval, VOS3000 SIP INVITE Timeout, VOS3000 SIP Call Progress Timeout, VOS3000 SIP Outbound Registration Parameters, VOS3000 SIP Privacy Header, VOS3000 SIP Routing Gateway Contact, VOS3000 SIP Publish Expire, VOS3000 SIP Display From, VOS3000 SIP Send Unregister","src":"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-SIP-Routing-Gateway-Contact-VOS3000-SIP-Publish-Expire-VOS3000-SIP-Display-From-VOS3000-SIP-Send-Unregister.png?fit=1200%2C800&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-SIP-Routing-Gateway-Contact-VOS3000-SIP-Publish-Expire-VOS3000-SIP-Display-From-VOS3000-SIP-Send-Unregister.png?fit=1200%2C800&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-SIP-Routing-Gateway-Contact-VOS3000-SIP-Publish-Expire-VOS3000-SIP-Display-From-VOS3000-SIP-Send-Unregister.png?fit=1200%2C800&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-SIP-Routing-Gateway-Contact-VOS3000-SIP-Publish-Expire-VOS3000-SIP-Display-From-VOS3000-SIP-Send-Unregister.png?fit=1200%2C800&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-SIP-Routing-Gateway-Contact-VOS3000-SIP-Publish-Expire-VOS3000-SIP-Display-From-VOS3000-SIP-Send-Unregister.png?fit=1200%2C800&ssl=1&resize=1050%2C600 3x"},"classes":[]},{"id":3208,"url":"https:\/\/multahost.com\/blog\/vos3000-caller-source-header-selection\/","url_meta":{"origin":3153,"position":2},"title":"VOS3000 Caller Source Header Selection Complete From Remote-Party-ID Display Important","author":"king","date":"April 21, 2026","format":false,"excerpt":"VOS3000 caller source header selection configures CLI extraction from From, Remote-Party-ID, or Display headers. Accurate caller ID for mapping gateway routing.","rel":"","context":"In &quot;VOS3000&quot;","block_context":{"text":"VOS3000","link":"https:\/\/multahost.com\/blog\/category\/vos3000\/"},"img":{"alt_text":"VOS3000 Caller Source Header, VOS3000 Callee Source Header, VOS3000 Remote Ring Back Mode, VOS3000 Call Forward Signal Recognition, VOS3000 Replace Failed Reason","src":"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-Caller-Source-Header-VOS3000-Callee-Source-Header-VOS3000-Remote-Ring-Back-Mode-VOS3000-Call-Forward-Signal-Recognition-VOS3000-Replace-Failed-Reason.png?fit=1200%2C800&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-Caller-Source-Header-VOS3000-Callee-Source-Header-VOS3000-Remote-Ring-Back-Mode-VOS3000-Call-Forward-Signal-Recognition-VOS3000-Replace-Failed-Reason.png?fit=1200%2C800&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-Caller-Source-Header-VOS3000-Callee-Source-Header-VOS3000-Remote-Ring-Back-Mode-VOS3000-Call-Forward-Signal-Recognition-VOS3000-Replace-Failed-Reason.png?fit=1200%2C800&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-Caller-Source-Header-VOS3000-Callee-Source-Header-VOS3000-Remote-Ring-Back-Mode-VOS3000-Call-Forward-Signal-Recognition-VOS3000-Replace-Failed-Reason.png?fit=1200%2C800&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-Caller-Source-Header-VOS3000-Callee-Source-Header-VOS3000-Remote-Ring-Back-Mode-VOS3000-Call-Forward-Signal-Recognition-VOS3000-Replace-Failed-Reason.png?fit=1200%2C800&ssl=1&resize=1050%2C600 3x"},"classes":[]},{"id":3162,"url":"https:\/\/multahost.com\/blog\/vos3000-sip-routing-gateway-contact\/","url_meta":{"origin":3153,"position":3},"title":"VOS3000 SIP Routing Gateway Contact: Essential INVITE Header Guide","author":"king","date":"April 21, 2026","format":false,"excerpt":"Master VOS3000 SIP routing gateway contact with SS_SIP_ROUTING_GATEWAY_INVITE_USE_CONTACT. Configure Contact header routing, request-line callee handling, and To field preservation for VoIP softswitch.","rel":"","context":"In &quot;VOS3000&quot;","block_context":{"text":"VOS3000","link":"https:\/\/multahost.com\/blog\/category\/vos3000\/"},"img":{"alt_text":"VOS3000 SIP Authentication Retry, VOS3000 SIP Early Hangup, VOS3000 SIP Session Timer Refresh, VOS3000 Non-Timer Endpoint Safety, VOS3000 SIP NAT Keepalive, VOS3000 SIP Resend Interval, VOS3000 SIP INVITE Timeout, VOS3000 SIP Call Progress Timeout, VOS3000 SIP Outbound Registration Parameters, VOS3000 SIP Privacy Header, VOS3000 SIP Routing Gateway Contact, VOS3000 SIP Publish Expire, VOS3000 SIP Display From, VOS3000 SIP Send Unregister","src":"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-SIP-Call-Progress-Timeout-VOS3000-SIP-Outbound-Registration-Parameters-VOS3000-SIP-Privacy-Header-VOS3000-SIP-Routing-Gateway-Contact-VOS3000-SIP-Publish-Expire-VOS3000-SIP-Display-From.png?fit=1200%2C800&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-SIP-Call-Progress-Timeout-VOS3000-SIP-Outbound-Registration-Parameters-VOS3000-SIP-Privacy-Header-VOS3000-SIP-Routing-Gateway-Contact-VOS3000-SIP-Publish-Expire-VOS3000-SIP-Display-From.png?fit=1200%2C800&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-SIP-Call-Progress-Timeout-VOS3000-SIP-Outbound-Registration-Parameters-VOS3000-SIP-Privacy-Header-VOS3000-SIP-Routing-Gateway-Contact-VOS3000-SIP-Publish-Expire-VOS3000-SIP-Display-From.png?fit=1200%2C800&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-SIP-Call-Progress-Timeout-VOS3000-SIP-Outbound-Registration-Parameters-VOS3000-SIP-Privacy-Header-VOS3000-SIP-Routing-Gateway-Contact-VOS3000-SIP-Publish-Expire-VOS3000-SIP-Display-From.png?fit=1200%2C800&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-SIP-Call-Progress-Timeout-VOS3000-SIP-Outbound-Registration-Parameters-VOS3000-SIP-Privacy-Header-VOS3000-SIP-Routing-Gateway-Contact-VOS3000-SIP-Publish-Expire-VOS3000-SIP-Display-From.png?fit=1200%2C800&ssl=1&resize=1050%2C600 3x"},"classes":[]},{"id":3587,"url":"https:\/\/multahost.com\/blog\/sistema-vos3000-registro-sip\/","url_meta":{"origin":3153,"position":4},"title":"Sistema VOS3000 Registro SIP Potente: Encabezados, Privacidad y Dominio Local Important","author":"king","date":"May 2, 2026","format":false,"excerpt":"Sistema VOS3000 Registro SIP Potente: encabezados privacidad, registro outbound, PRACK, modos direccion SIP, transparencia headers y dominio local.","rel":"","context":"In &quot;VOS3000&quot;","block_context":{"text":"VOS3000","link":"https:\/\/multahost.com\/blog\/category\/vos3000\/"},"img":{"alt_text":"Sistema VOS3000 Facturacion, Sistema VOS3000 Registros CDR, Sistema VOS3000 Gestion CDR, Sistema VOS3000 Seguridad Autenticacion, Sistema VOS3000 Protocolo SIP, Sistema VOS3000 Registro SIP, Sistema VOS3000 Failover Pasarelas, Sistema VOS3000 Gestion Llamadas, Sistema VOS3000 Lista Negra, Sistema VOS3000 Configuracion Pasarelas","src":"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/05\/Sistema-VOS3000-Failover-Pasarelas-Sistema-VOS3000-Gestion-Llamadas-Sistema-VOS3000-Lista-Negra-Sistema-VOS3000-Configuracion-Pasarelas-1.png?fit=1200%2C628&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/05\/Sistema-VOS3000-Failover-Pasarelas-Sistema-VOS3000-Gestion-Llamadas-Sistema-VOS3000-Lista-Negra-Sistema-VOS3000-Configuracion-Pasarelas-1.png?fit=1200%2C628&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/05\/Sistema-VOS3000-Failover-Pasarelas-Sistema-VOS3000-Gestion-Llamadas-Sistema-VOS3000-Lista-Negra-Sistema-VOS3000-Configuracion-Pasarelas-1.png?fit=1200%2C628&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/05\/Sistema-VOS3000-Failover-Pasarelas-Sistema-VOS3000-Gestion-Llamadas-Sistema-VOS3000-Lista-Negra-Sistema-VOS3000-Configuracion-Pasarelas-1.png?fit=1200%2C628&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/05\/Sistema-VOS3000-Failover-Pasarelas-Sistema-VOS3000-Gestion-Llamadas-Sistema-VOS3000-Lista-Negra-Sistema-VOS3000-Configuracion-Pasarelas-1.png?fit=1200%2C628&ssl=1&resize=1050%2C600 3x"},"classes":[]},{"id":3209,"url":"https:\/\/multahost.com\/blog\/vos3000-callee-source-header\/","url_meta":{"origin":3153,"position":5},"title":"VOS3000 Callee Source Header Flexible To Request-Line Selection Important","author":"king","date":"April 21, 2026","format":false,"excerpt":"VOS3000 callee source header selects destination number from To header or Request-Line. Configure dialed number extraction for accurate routing and billing.","rel":"","context":"In &quot;VOS3000&quot;","block_context":{"text":"VOS3000","link":"https:\/\/multahost.com\/blog\/category\/vos3000\/"},"img":{"alt_text":"VOS3000 Caller Source Header, VOS3000 Callee Source Header, VOS3000 Remote Ring Back Mode, VOS3000 Call Forward Signal Recognition, VOS3000 Replace Failed Reason","src":"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-Caller-Source-Header-VOS3000-Callee-Source-Header-VOS3000-Remote-Ring-Back-Mode-VOS3000-Call-Forward-Signal-Recognition-VOS3000-Replace-Failed-Reason-1.png?fit=1200%2C800&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-Caller-Source-Header-VOS3000-Callee-Source-Header-VOS3000-Remote-Ring-Back-Mode-VOS3000-Call-Forward-Signal-Recognition-VOS3000-Replace-Failed-Reason-1.png?fit=1200%2C800&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-Caller-Source-Header-VOS3000-Callee-Source-Header-VOS3000-Remote-Ring-Back-Mode-VOS3000-Call-Forward-Signal-Recognition-VOS3000-Replace-Failed-Reason-1.png?fit=1200%2C800&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-Caller-Source-Header-VOS3000-Callee-Source-Header-VOS3000-Remote-Ring-Back-Mode-VOS3000-Call-Forward-Signal-Recognition-VOS3000-Replace-Failed-Reason-1.png?fit=1200%2C800&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/multahost.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-Caller-Source-Header-VOS3000-Callee-Source-Header-VOS3000-Remote-Ring-Back-Mode-VOS3000-Call-Forward-Signal-Recognition-VOS3000-Replace-Failed-Reason-1.png?fit=1200%2C800&ssl=1&resize=1050%2C600 3x"},"classes":[]}],"jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/multahost.com\/blog\/wp-json\/wp\/v2\/posts\/3153","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/multahost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/multahost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/multahost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/multahost.com\/blog\/wp-json\/wp\/v2\/comments?post=3153"}],"version-history":[{"count":0,"href":"https:\/\/multahost.com\/blog\/wp-json\/wp\/v2\/posts\/3153\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/multahost.com\/blog\/wp-json\/wp\/v2\/media\/3146"}],"wp:attachment":[{"href":"https:\/\/multahost.com\/blog\/wp-json\/wp\/v2\/media?parent=3153"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/multahost.com\/blog\/wp-json\/wp\/v2\/categories?post=3153"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/multahost.com\/blog\/wp-json\/wp\/v2\/tags?post=3153"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}