VOS3000 caller ID settings
Carriers reject or mislabel calls when the caller ID is missing or in the wrong header. These settings decide what VOS3000 reads and sends.
Updated · By the VOS3000 Web team
Quick answer: VOS3000 reads the caller number from the From header by default, or from Remote-Party-ID or the display name, set on the mapping gateway. On the routing gateway you choose whether to send Privacy, P-Preferred-Identity and P-Asserted-Identity, and caller dial plans change the number itself.
- Read from
- From, Remote-Party-ID or Display
- Send
- P-Asserted-Identity: None, Pass through or Caller
- Change the number
- Caller Rewrite Rule/Dial plan
- Phones
- Display caller id
Where VOS3000 reads the numbers (mapping gateway)
On the customer's mapping gateway, Additional settings → Protocol → SIP:
- Caller: take the caller number from From, Remote-Party-ID or Display (the display name).
- Callee: take the called number from To or the Request-Line.
- Support Privacy: pass the customer's privacy request on.
If the customer puts the real number in a header VOS3000 is not reading, every CDR shows the wrong caller. Check the customer's INVITE in a debug trace.
What VOS3000 sends (routing gateway)
On the carrier's routing gateway, Additional settings → Protocol → SIP:
| Setting | Choices |
|---|---|
| Privacy | None (no header), Passthrough (send what the customer sent), Id (add Privacy: id). |
| P-Preferred-Identity | None, Passthrough, Caller (use the caller number). |
| P-Asserted-Identity | None, Pass through, Caller (use the caller number), with its own Caller dial plan. |
| user=phone | Adds user=phone to the INVITE, which some carriers require. |
| Allow all extra header fields | Passes other SIP headers from the customer through unchanged. |
Most carriers want the caller number in E.164 format (country code, no leading 00 or +) in both From and P-Asserted-Identity. Ask your carrier which header they read.
Changing the number itself
The Caller Rewrite Rule/Dial plan on the mapping or routing gateway changes the caller number, for example adding a country code; see rewrite rules. For caller ID pools and random digits, see dial plan patterns. A gateway with Caller transform on replaces caller numbers using the Number transform table; see number management.
Phones
- Each phone has a Display caller id: the number the called side sees. On the routing gateway, Enable phone display number uses it instead of the phone number.
- DID/DDI lists the other numbers a phone may use as caller ID.
- On forwarded calls, SS_CALL_FORWARD_USING_ORIGINAL_CALLER (On) shows the original caller rather than the forwarding phone.
Only send caller IDs you have the right to use. Carriers increasingly block calls with invalid or spoofed numbers.
Questions about this topic
How do I send P-Asserted-Identity from VOS3000?
On the routing gateway, Additional settings, Protocol, SIP, set P-Asserted-Identity to Caller (use the caller number) or Pass through (send what the customer sent).
Why does the carrier see the wrong caller ID?
Check which header the carrier reads, then match it: the From number is changed by caller dial plans, and P-Asserted-Identity has its own caller dial plan.
How do I hide the caller ID?
Set Privacy to Id on the routing gateway, or Passthrough to keep the customer's own privacy request. Many carriers still need a valid number in P-Asserted-Identity.
Try every step in the live demo
Each screen in this guide is in the VOS3000 Web demo, with made-up data. Sign in with demo / demo.
Keep reading
Dial plan patterns
Wildcards, number ranges, random digits, kept digits and length rules in VOS3000 dial plans.
Rewrite rules and dial plans
The initial:destination format, prefix allow and forbidden lists, number lengths.
Add a mapping gateway
Set up a customer gateway: types, IPs, line limits, prefixes and billing.
Add a routing gateway
Set up a vendor route: prefix, IP and port, priority and least-cost options.