DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
The SBC is enhanced to pass the "jcard" and the "call-reason" parameters received in the "Call-Info" header of the SIP INVITE to the PSX when STIR/SHAKEN is enabled. To support this functionality, the flexVariable
type is added to the SIP Adaptor Profile configuration to store up to 16 flex variables received from the PSX as input to the SBC SMM to modify SIP messages on the Egress leg.
SBC Behavior | PSX Behavior |
---|---|
The SBC sends the "jcard" information only if the size is less than 1024 bytes to the PSX.
| The PSX includes an option to support "rcd" PASSporT extension in the lines of other "ppt" types that are supported by the PSX. By default, this flag is disabled.
|
The SBC processes the Identity header of type "rcd" and sends it to the PSX (It is assumed that only one Identity header of type "rcd" exists. If multiple such Identity headers exist, then the SBC chooses the first Identity header among them) The SBC processes the "ppt" extensions when multiple Identity headers are present according to the following priority:
| The PSX processes the RCD claims only when the "ppt" with the type "shaken" or "rcd". If the RCD claims are present in other "ppt" types such as "div" and "rph", the PSX ignores such RCD claims.
|
Upon receiving RCD claims (jcl/jcd, logo), the SBC:
| The PSX indicates to the SBC upon RCD verification failure.
|
The SBC sends/adds the Call-Info" header with "purpose=jcard,icon" based on the indication received, under the following conditions:
| The PSX provides the following options on RCD Verification Success, RCD Verification Failure, and No RCD Verification and indicates the same to the SBC.
|