Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca7f046c, userName='null'}
JIRAIDAUTHSBX-88903
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c8c30172, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c8c30172, userName='null'}


Panel

In this section:

Table of Contents



Info
iconfalse

Related articles:

Children Display


Resource Priority Header (RPH) configuration options to specify how the RPH or ISUP-MIME affects call handling and building of the RPH for HPC calls.

To View and Edit Rph

  1. On the SBC Main screen, navigate using any of the following EMA paths:
    • All > Profiles > Services > Hpc Call Profile > Rph
    • Configuration > Profile Management > Category: Service Profiles > Hpc Call Profile > Rph
  2. The Rph window displays.

    Caption
    0Figure
    1Rph

    Image Modified


  3. Using the drop-down list, select the Hpc Call Profile for which you want to edit the Rph flags.
  4. The Edit Rph window displays.

    Caption
    0Figure
    1Edit Rph

    Image Modified


    Caption
    0Table
    1Hpc Call Profile - Rph


    Parameter

    Description

    Ets Default ValueSpecifies the default value used for the ETS namespace. The value ranges from 0 to 4 and the default value is 0.
    Use Wps Precedence

    Specifies whether SBC must use ingress precedence, if available as ETS value when adding RPH header. The options are:

    • Disabled (default)
    • Enabled
    Use Incoming Ets

    Specifies whether SBC uses the received ETS value if available, when adding RPH and it has the highest precedence in deciding ETS value when adding RPH. The options are:

    • Disabled (default)
    • Enabled
    Use Precedence

    Specifies whether to use precedence Multilevel Precedence and Preemption or Wireless Priority Service (MLPP/WPS) from ingress side to be sent on egress side. The options are:

    • Disabled (default)
    • Enabled
    Ets CPC Precedence

    Controls the SBC behavior when it receives conflicting Emergency Telecommunications Services (ETS) (RPH and CPC (ISUP-MIME)) values. The options are:

    • Hpc (default)
    • Cpc
    • Ets
    Wps MIpp Precedence

    Specifies the SBC behavior when there is a conflict between precedence derived from RPH WPS namespace and ISUP-MIME (SIP-I) MLPP values. The options are:

    • Wps
    • MIpp (default)
    Include Require

    Specifies whether a Require: Resource-Priority header is included in an egress INVITE or not. The options are:

    • Disabled (default)
    • Enabled
    Reject Not Ets DnIf SBC classifies a call as HPC based on received RPH and rejectNotEtsDn is enabled and if PSX determines that the dialed digits do not match the PSX's configuration for Government Emergency Number Prefix, the call will be rejected. The options are:
    • Disabled (default)
    • Enabled
    Include Accept In417Specifies whether SBC includes the Accept-Resource-Priority header or not when sending a 417 response. The options are:
    • Disabled (default)
    • Enabled



  5. Make the required changes and click Save.

 


For more information on RPH handling, refer to SIP Resource Priority Header Support for HPC-GETS.pagebreak