HPC Call Profile - CLI

High Probability of Completion (HPC) features comprise a set of functionalities that provide an enhanced probability of call completion to authorized Government Emergency Telecommunications Service (GETS) and Wireless Priority Service (WPS) users during network stress and/or congestion.

 The SBC supports the following HPC capabilities:

• Identification of an HPC call based on the presence of either a GETS-Access Number (AN), or GETS-Number Translation (NT) string.
• Rejection of a call based on the presence of GET-Feature Code (FC) string.
• Identification of an HPC call based on the code point in the Calling Party Category (CPC) parameter of the ISUP MIME.
• Prioritization or rejection of a call based on Resource-Priority Header (RPH) r-values in an initial INVITE. The SBC also processes mid-call RPH.
• Generation of an RPH for inclusion in egress SIP messages.
• Support for early or late HPC call classification.
• Detection and logging of error conditions.
• HPC Call Admission Controls - ingress CAC for early HPC classified calls, and egress CAC treatment for early and late HPC classified calls.
• Call Queuing, if an HPC call request fails to get a resource it is queued; when the required resource is available, the processing resumes.
• Exemption of HPC messages from congestion control.
• DSCP marking and priority treatment for HPC packets - SIP, Diameter and Media packets.
• High Priority Media Port Range (HPMPR) - packets received on ports in (HPMPR) are prioritized.
• Statistics and alarms for monitoring HPC traffic.

There are two methods in HPC call classification:

• Early HPC classification—An HPC call is recognized based on the received SIP RPH content in the incoming INVITE or the code point in Calling Party's Category (CPC) parameter of the ISUP-MIME. For ANSI, the CPC parameter is National Security/Emergency Preparedness (NS/EP) and for ITU, the CPC parameter isInternationalEmergency Preference Scheme (IEPS).

• Late HPC classification—An HPC call can also be recognized by the PSX during analysis of the Called Party Number.

 The SBC supports the use of different Differentiated Services Code Point (DSCP) marking for signaling traffic that is associated with HPC and non-HPC calls. To support different DSCP marking for HPC and non-HPC calls in a SIP trunk group, the dscpValue parameter in the HPC profile configuration marks HPC calls and the DSCP configuration in the SIP signaling port marks non-HPC calls. The DSCP value configured in the HPC profile takes precedence over the DSCP value configured in the SIP signaling port and applies to all outbound traffic (IPv4 and IPv6) associated with HPC calls.

The outbound SIP signaling messages associated with HPC and non-HPC calls are marked with the DSCP value configured in the SIP signaling port when the hpcCallProfile is not configured in a SIP trunk group.

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

Command Syntax

% set profiles services hpcCallProfile <hpcCallProfile name>
	rph 
		etsCpcPrecedence <cpc | ets | hpc>
		etsDefaultValue <0-4>
		includeAcceptIn417 <disabled | enabled>
		includeRequire <disabled | enabled> 
		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:

Command Examples

set profiles services hpcCallProfile testHpcProfile state enabled 
set profiles services hpcCallProfile testHpcProfile rph tsCpcPrecedence hpc etsDefaultValue 1 
set profiles services hpcCallProfile testHpcProfile includeAcceptIn417 enabled includeRequire enabled rejectNotEtsDn enabled useIncomingEts enabled usePrecedence enabled useWpsPrecedence enabled wpsMlppPrecedence wps

show profiles services hpcCallProfile
hpcCallProfile HPCP {
    state enabled;
    rph {
        etsDefaultValue    1;
        useWpsPrecedence   enabled;
        useIncomingEts     enabled;
        usePrecedence      enabled;
        etsCpcPrecedence   hpc;
        wpsMlppPrecedence  wps;
        includeRequire     enabled;
        rejectNotEtsDn     enabled;
        includeAcceptIn417 enabled;
    }
}