Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Add_workflow_for_techpubsAUTH1JIRAIDAUTHSBX-72081REV5REV6REV3REV1

Command Syntax

Code Block
> show table profiles services hpcCallProfile <profile name>

 

Command Parameters

Caption
0Table
1HPC Call Profile Parameters
3HPC Call Profile Parameters
ParameterDescription
nameThe name of the High Probability of Completion (HPC) Profile.
dscpValue<0-63> The DSCP code for the HPC call.
etsCpcPrecedence 

Identifies how a call's CPC is derived during ingress processing when a conflict exists between the CPC based on RPH and the ISUP-MIME (SIP-I) calling party category parameter.

etsDefaultValueDefault priority value used for the ETS namespace.
includeAcceptIn417

If enabled, the

Spacevars
0product
includes the Accept-Resource-Priority header when sending a 417 response.

includeRequire 

If enabled, the

Spacevars
0product
includes the Require header with the resource-priority option tag in an egress INVITE.

rejectNotEtsDn 

If enabled, the

Spacevars
0product
rejects a call when
Spacevars
0product
classifies the call as HPC based on the received RPH and the PSX determines Directory Number (DN) to be a non-ETS DN.

state Administrative state of this HPC Call Profile.
useIncomingEts 

If enabled, the

Spacevars
0product
uses the received ETS value. If disabled, the the provisioned etsDefaultValue is used.

usePrecedence 

Specifies whether the ETS value in outgoing SIP messages for the call takes the priority/precedence value received in the ingress.

useWpsPrecedence 

If enabled, the

Spacevars
0product
takes the ETS priority value from WPS/ MLPP precedence, if available, when adding ETS. If disabled, the
Spacevars
0product
uses the configured etsDefaultValue when adding ETS.

wpsMlppPrecedence 

Specifies how to handle the call when the WPS value in the SIP RPH and a MLPP parameter in the associated ISUP-MIME indicate different handling

Pagebreak