We’ve been unable to correctly block outbound CLID through our voip service provider (VSP), voicenetwork.ca. They do not process (nor accept) the DTMF tones, and therefore *67 (or (*81), in the dial string in SIP trunk call setup. They do, however, correctly honor the SIP protocol P-Asserted-Identity with the “Privacy: id” option.
If the “Privacy: id” is present the called party correctly sees “Private Number” in their display.
How (and where) in the asterisk, freepbx (trixbox) technology stack can one set the “Privacy: id” field of an outbound call by one of its extensions on a selective basis (e.g. user prefixing *67)?
We presently have two SIP trunks to the VSP. We have a two outbound route dial plans
mapping to trunk OUT-BLOCKED
mapping to trunk OUT-SHOW
Where the OUTBOUND PEER DETIALS for trunk OUT-BLOCKED includes,
Where the OUTBOUND PEER DETIALS for trunk OUT-SHOW does not,
OMITTED: privacy=on&full omitted
This results in a close approximation of a blocked caller id, as seen by the called party, where “0000000000” is what the called party receives. Nevertheless, it’s not a true “Private Number.”
Any help setting the “Privacy: id” field in the scenario described or other use-case scenario would be greatly appreciated.