Is there a way to force or assert PAI in the customer_auth or origin_gateway for a call originated without a caller id?
You could trying matching customer auth src rewrite rule in the number translation section with empty regex
^$ and put the full callerid in the the Src Rewrite Result as a replacement.
I have tried that already that would reveal the caller’s caller ID. The aim here is to allow calls with Blocked Caller ID while asserting PAI in the SIP header for the purpose of accounting by upstream carriers
@dmitry.s Can we use this option for Privacy in SDP?
As per the documentation, could we use Orig append header req to assert
Privacy: id and
Orig append headers req Additional SIP headers that Yeti should add to request to the Gateway (in case of using Gateway as Originator of calls). Additional header fields are lines composed of a field name, followed by a colon (:), followed by a field body, and terminated by followin set of characters (‘rn’). A field name must be composed of printable US-ASCII characters (i.e., characters that have values between 33 and 126, inclusive), except colon. A field body may be composed of any US-ASCII characters, except for carriage return character (‘r’) and line feed character (‘n’). Format of headers: field-name1: field-value1**rn**field-name1: field-value2…, where *field-name1 and field-name2* - names of the custom fields, *field-value1 and field-value2* - values of the custom fields, **rn** - the carriage-return/line-feed pair.