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 applies disconnect treatment to the ingress party specified by the Signaling Sequence Profile (SSP). This SSP is derived from the SCP disconnect treatment profile (DTP) and disconnect treatment indicator provided by the policy server in a trigger response. The DTP must be explicitly configured on the SBC. The existing disconnect reason is still forwarded to the ingress party immediately after the disconnect treatment (if applicable) is applied. The disconnect reason can be SCP or egress party initiated.
% set profiles services disconnectTreatmentProfile <profile name> reason <1-255> disconnectSSP <DSSP profile name>
The Disconnect Treatment Profile Parameters are as shown:
The following example creates a Disconnect Treatment Profile named "DTP-1" with a reason code of "16" (normal call clearing), and assigns disconnect SSP "DSSP-1" to this profile so that when this profile runs it will execute "DSSP-1".
% set profiles services disconnectTreatmentProfile DTP-1 reason 16 disconnectSSP DSSP-1 % show profiles services disconnectTreatmentProfile disconnectTreatmentProfile DTP-1 { reason 16 { disconnectSSP DSSP-1; } }