Versions Compared

Key

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

Add_workflow_for_techpubs
AUTH1
JIRAIDAUTHSBX-

72081

88903
REV5
REV6
REV3
REV1

Panel

In this section:

Table of Contents
maxLevel3
minLevel2

 

Overview

Excerpt Include
SBC Support of GETS and WPS
SBC Support of GETS and WPS
nopaneltrue

This section describes the CLI syntax and parameter descriptions of the HPC Call Profile.

Info

The SBC must be configured to use the external PSX for this feature. The SBC supports configuring up to 256 HPC Call Profiles.

 

Command Syntax

Code Block
languagenone
% set profiles services hpcCallProfile <hpcCallProfile name>
	dscp value <egress | ingress>
		useRecvdValue <diabled | enabled>
	dscpValue <0-63>
	getsStrings    
		accessNumber an <3-10 digits>
		featureCode fc <3-10 characters>
		numberTranslation nt <3-10 digits>
	queue
		length <1-256>
		state <disabled | enabled>
		timeout <1-90>
	rph 
		egress
			nonEtsWps <dontInclude | include>
			validEtsWps <dontInclude | include>
		etsCpcPrecedence <cpc | ets | hpc>
		etsDefaultValue <0-4>
		includeAcceptIn417 <disabled | enabled>
		includeRequire <disabled | enabled> 
		ingress
			invalidEtsWps <ignore | reject>
			nonEtsWps <accept | ignore>
			validEtsWps <accept | ignore | reject>
		rejectNotEtsDn <disabled | enabled>
		useIncomingEts <disabled | enabled>
		usePrecedence <disabled | enabled>
		useWpsPrecedence <disabled | enabled>
		wpsMlppPrecedence <mlpp | wps>
	state <disabled | enabled>

The HPC Call Profile parameters are defined below:

 
Caption
0Table
1HPC Call Profile Parameters
3HPC Call Profile Parameters

Parameter

Description

hpcCallProfile<profile name, up to 23 characters> – HPC Call Profile name.
dscp

The SBC uses the DSCP value received in the initial INVITE for the DSCP marking of the SIP message.

 
  • egress - Use to relate dscp to the egress trunk group. Use the following flag for further configuration:
    • useRecvdValue - When the HPC call profile attaches to a trunk group acting as an egress trunk group, use this flag to control DSCP marking for SIP messages the SBC sends forward (for example, INVITE or ACK).
      • disabled (default)
      • enabled
  • ingress - Use to relate dscp to the ingress trunk group. Use the following flag for further configuration:
    • useRecvdValue - When the HPC call profile attaches to a trunk group acting as an ingress trunk group, use this flag to control DSCP marking for SIP messages the SBC sends backward (for example, 18x or 200 OK).
      • disabled (default)
      • enabled
dscpValue<0-63> The DSCP code for the HPC Call.
getsStrings

A set of Government Emergency Telecommunications Service (GETS) Access Number (AN), Number Translation (NT), and Feature Code (FC) strings that the SBC uses to determine whether a call is an HPC call or is rejected.

  • accessNumber an < 3-10 digits> - The SBC classifies HPC calls using digits in the Request-URI of an initial INVITE request that match GETS-AN. You can configure a maximum of 10 GETS-AN strings.
  • featureCode fc < 3-10 characters without visual separators> - The SBC rejects HPC calls using strings in the Request-URI of an initial INVITE request that match GETS-FC. You can configure a maximum of 4 GET-FC strings.
  • numberTranslation nt < 3-10 digits> - The SBC classifies HPC calls using digits in the Request-URI of an initial INVITE request that match GETS-NT. You can configure a maximum of 10 GETS-NT strings.
queue

Use this parameter to configure HPC call queuing for trunk groups.

  • length <1-256> - Specifies the maximum number of calls that can simultaneously queue at each trunk group. Default: 5.
  • state - Use this flag to enable or disable the queuing of HPC calls.
    • disabled (default)
    • enabled
      Note: Do not enable HPC call queuing for ingress and egress trunk groups simultaneously.
     
  • timeout<1-90> - Specifies the maximum time (in seconds) that an HPC call remains queued before the SBC stops the attempt to connect the call in the associated trunk group. Default: 30.
    Note: When call is queued on the egress trunk group and the queue timer expires, the SBC sends a 408 response towards the ingress side to release the queued call. For the same scenario in a GW-GW call, the ingress SBC sends a 503 response instead of 408. 


Note: By default, the SBC sends a response code 600 when the call queue is full. To configure the SBC to send the response code 503 when the call queue is full, execute  similar commands as described below:

    % set profiles signaling sipCauseCodeMapping cpcToSipCauseMapProfile TEST baseProfile defaultCpcSip causeMap 161 sipCause 503

    % set addressContext default zone ZONE1 sipTrunkGroup INGRESS_TG signaling causeCodeMapping cpcSipCauseMappingProfile TEST

    % commit

rph

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.

  • egress - Determines how the SBC handles the ets and wps namespaces in the RPH (built by the SBC).
    • nonEtsWps - Determines if the SBC includes or does not include namespaces other than ets and wps in the RPH (built by the SBC).
      • dontInclude (default)
      • include
    • validEtsWps - Determines if the SBC includes or does not include valid ets and wps namespaces in the RPH (built by the SBC).
      • dontInclude
      • include (default)

  • etsCpcPrecedence – This parameter is used for deriving a call's CPC during ingress processing when a conflict exists between the CPC based on RPH and the ISUP-MIME (SIP-I) calling party category parameter.
    • cpc – The call's CPC parameter is derived from the ISUP-MIME CPC parameter.

    • ets – The call’s CPC parameter is derived based on the SIP RPH ETS value.

    • hpc (default) – The call’s CPC parameter is derived based on SIP RPH ETS, or else it is derived from ISUP-MIME CPC parameter.


  • etsDefaultValue <value> – Default priority value used for the ETS namespace. (range: 0-4 / default = 0)

  • includeAcceptIn417 – Enable this flag to include the Accept-Resource-Priority header when sending a 417 response.
    • disabled (default)
    • enabled

  • includeRequire – Enable this flag for the SBC to include the Require header with the resource-priority option tag in an egress INVITE.
    • disabled (default)
    • enabled

  • ingress - Determines how the SBC handles namespaces in the received RPH.
    • invalidEtsWps - Determines if the SBC ignores or rejects invalid ets and wps namespaces in the RPH of an ingress SIP INVITE request.
      • ignore (default)
      • reject
    • nonEtsWps - Determines if the SBC accepts or ignores namespaces other than ets and wps in the RPH of an ingress SIP INVITE request.
      • accept (default)
      • ignore
    • validEtsWps - Determines if the SBC accepts, ignores, or rejects valid ets and wps namespaces in the received RPH.
      • accept (default)
      • ignore
      • reject

  • rejectNotEtsDn – Enable this flag for the SBC to reject a call when SBC classifies the call as HPC based on the received RPH and the PSX determines Directory Number (DN) to be a non-ETS DN.
    • disabled (default)
    • enabled

  • useIncomingEts – Enable this flag for the SBC to use the received ETS value. If set to disabled, the SBC uses the provisioned etsDefaultValue.
    • disabled (default)
    • enabled

  • usePrecedence – Specifies whether the ETS value in outgoing SIP messages for the call takes the priority/precedence value received in the ingress.
    • disabled (default) – The ETS priority value in outgoing SIP messages is derived from the etsDefaultValue, when either of the usePrecedence at the ingress trunk group’s HPC profile or useWpsPrecedence at the egress trunk group’s HPC profile fields are disabled, or when there is no incoming priority/precedence value.
    • enabled – When usePrecedence is enabled at the ingress trunk group’s HPC profile and useWpsPrecedence is enabled at the egress trunk group’s HPC profile, the ETS value in outgoing SIP messages is derived from the incoming Wireless Priority Service/Multilevel Precedence and Preemption (WPS/MLPP) priority/precedence value.
  • useWpsPrecedence – Enable this flag for the SBC to take the ETS priority value from WPS/ MLPP precedence, if available, when adding ETS. If set to disabled, the SBC uses the configured etsDefaultValue when adding ETS.
    • disabled (default)
    • enabled

  • wpsMlppPrecedence – Use this parameter to determine 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:
    • mlpp (default) – Handle the call as indicated by the ISUP-MIME MLPP parameter.
    • wps – Handle the call as indicated by the SIP RPH WPS value.
state

Administrative state of HPC Call Profile.

  • disabled (default)
  • enabled

 

Command Examples

Assuming all other parameters and flags have their default values, the following command example shows a minimal configuration for hpcCallProfile:

Code Block
languagenone
% set profiles services hpcCallProfile testHpcProfile state enabled 

% commit

 

To enable the hpcCallProfile created in the previous example, with an allowed dscpValue:

Code Block
% set profiles services hpcCallProfile testHpcProfile rphdscpValue tsCpcPrecedence50 hpcstated etsDefaultValue 1 
enabled
% commit

 

To enable useRecvdValue for dscp egress:

Code Block
% set profiles services hpcCallProfile testHpcProfile dscp egress includeAcceptIn417useRecvdValue enabled includeRequire enabled rejectNotEtsDn enabled useIncomingEts enabled usePrecedence enabled useWpsPrecedence enabled wpsMlppPrecedence wps

% commit

 

To enable useRecvdValue for dscp ingress:

Code Block
% set profiles services hpcCallProfile testHpcProfile dscp ingress useRecvdValue enabled
% commit

 

To configure a GETS-AN string:

Code Block
% set
show profiles services hpcCallProfile
hpcCallProfile HPCPtestHpcProfile {
getsStrings accessNumber an 7106274387
% commit

 

To configure a GETS-FC string:

Code Block
% set profiles services hpcCallProfile testHpcProfile getsStrings featureCode fc *272

 

To configure a GETS-NT string:

Code Block
% set profiles services hpcCallProfile testHpcProfile getsStrings numberTranslation nt 7102001234
% commit

 

To configure a HPC call queue:

Code Block
% set profiles services hpcCallProfile testHpcProfile queue length 50 state enabled timeout 60
% commit
Note
titleCaution

Do not enable HPC call queuing for ingress and egress trunk groups simultaneously.

Info
titleNote

When call is queued on the egress trunk group and the queue timer expires, the SBC sends a 408 response towards the ingress side to release the queued call. For the same scenario in a GW-GW call, the ingress SBC sends a 503 response instead of 408.

Info
titleNote

By default, the SBC sends a response code 600 when the call queue is full.

To configure the SBC to send the response code 503 when the call queue is full, execute similar commands as described below:

    % set profiles signaling sipCauseCodeMapping cpcToSipCauseMapProfile TEST baseProfile defaultCpcSip causeMap 161 sipCause 503

    % set addressContext default zone ZONE1 sipTrunkGroup INGRESS_TG signaling causeCodeMapping cpcSipCauseMappingProfile TEST

    % commit

 

To configure RPH for the egress of a HPC Call Profile:

Code Block
% set profiles services hpcCallProfile testHpcProfile rph egress nonEtsWps include validEtsWps dontInclude

 

To configure RPH for the ingress of a HPC Call Profile:

Code Block
% set profiles services hpcCallProfile testHpcProfile rph ingress invalidEtsWps reject nonEtsWps ignore validEtsWps accept

 

To display a configured HPC call profile:

Code Block
% show profiles services hpcCallProfile testHpcProfile

state     enabled;
rph {
    ingress { state enabled;
    rph {
        etsDefaultValue    1;
        useWpsPrecedence   enabled;
        useIncomingEts     enabled;
        usePrecedence      enabled;
        etsCpcPrecedence   hpc;
        wpsMlppPrecedenceinvalidEtsWps  wpsreject;
        includeRequirevalidEtsWps     enabledaccept;
        rejectNotEtsDnnonEtsWps     enabledignore;
    }
    includeAcceptIn417egress enabled;{
    }
} 
 
 
> show profiles services hpcCallProfile
hpcCallProfile HPCP {
    validEtsWps dontInclude;
     dscpValue 10
  nonEtsWps  state enabledinclude;
    rph}
}
getsStrings {
    featureCode {
    etsDefaultValue    1fc *272;
    }
    useWpsPrecedence   enabled;accessNumber {
        useIncomingEtsan 7106274387;
    enabled;}
    numberTranslation {
   usePrecedence     nt enabled7102001234;
    }
}
queue {
    etsCpcPrecedencestate   hpcenabled;
    length    wpsMlppPrecedence  wps50;
    timeout 60;
}
dscp {
  includeRequire  egress   enabled;{
        rejectNotEtsDnuseRecvdValue     enabled;
    }
}
dscpValue 50;

 

To delete a configured HPC call profile:

Code Block
% delete profiles services includeAcceptIn417hpcCallProfile enabled;testHpcProfile
    }
}% commit

 


Pagebreak