Accepting Non-Standard verstat
By default, the SBC treats some non-standard verstat responses as failed. This is true even if verification is ultimately successful. This happens because the SBC cannot parse these verstat values. The SBC also increments the “STI-VS Failed Verification” statistics when it receives these non-standard verstat responses. An example non-standard verstat is shown below.
verstat=TN-Validation-Passed;attest=A;origid=1cab14fd-7c29-4c95-9177-a8317bb0bbbb@172.22.247.57
When you configure the verstat-delimiter option under sti-server, the SBC can parse customized verstat value on the basis of configured delimiter and fetch the valid verstat value. An example for configuring verstat-delimiter is shown below.
ORACLE(sti-server)# options + verstat-delimiter=;
Here, the delimiter is a semi-colon (;).
Oracle recommends that you consider configuring the verstat-delimiter option with the applicable character, such as a semi-colon, as a tool for parsing the entire verstat.