In this section:
Overview
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 use of the GETS SOFTWARE is restricted in the U.S. and U.S. TERRITORIES to NS/EP users authorized by the Office of the Manager, National Communications System (OMNCS). The SBC supports the following HPC capabilities: There are two methods in HPC call classification: For more information, refer to: The SBC must be configured to use the external PSX for this feature. For more information on using the PSX for GETS / WPS, refer to the PSX document Government Emergency Telecommunications Service. Preferential servicing of HPC calls is conditional on the installation of NW-HPC license on the EMS/RAMP. For more information, refer to: 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 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 Setting the DSCP on the UDP or TCP network socket is a system call, which impacts the system performance if the DSCP frequently switches between HPC and non-HPC calls. This feature only applies to HPC calls over UDP transport. This feature does not apply to TCP transport since TCP is byte stream oriented and does not preserve message boundaries.
Note
Note
Note
Caution
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.hpcCallProfile is not configured in a SIP trunk group.
Caution
Note
This section describes the CLI syntax and parameter descriptions of the HPC Call Profile.
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
% set profiles services hpcCallProfile <hpcCallProfile name> dscp <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:
HPC 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.
|
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.
|
queue | Use this parameter to configure HPC call queuing for trunk groups.
|
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.
|
state | Administrative state of HPC Call Profile.
|
Command Examples
Assuming all other parameters and flags have their default values, the following command example shows a minimal configuration for hpcCallProfile:
% set profiles services hpcCallProfile testHpcProfile % commit
To enable the hpcCallProfile created in the previous example, with an allowed dscpValue:
% set profiles services hpcCallProfile testHpcProfile dscpValue 50 stated enabled % commit
To enable useRecvdValue for dscp egress:
% set profiles services hpcCallProfile testHpcProfile dscp egress useRecvdValue enabled % commit
To enable useRecvdValue for dscp ingress:
% set profiles services hpcCallProfile testHpcProfile dscp ingress useRecvdValue enabled % commit
To configure a GETS-AN string:
% set profiles services hpcCallProfile testHpcProfile getsStrings accessNumber an 7106274387 % commit
To configure a GETS-FC string:
% set profiles services hpcCallProfile testHpcProfile getsStrings featureCode fc *272
To configure a GETS-NT string:
% set profiles services hpcCallProfile testHpcProfile getsStrings numberTranslation nt 7102001234 % commit
To configure a HPC call queue:
% set profiles services hpcCallProfile testHpcProfile queue length 50 state enabled timeout 60 % commit
Caution
Do not enable HPC call queuing for ingress and egress trunk groups simultaneously.
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
To configure RPH for the egress of a HPC Call Profile:
% set profiles services hpcCallProfile testHpcProfile rph egress nonEtsWps include validEtsWps dontInclude
To configure RPH for the ingress of a HPC Call Profile:
% set profiles services hpcCallProfile testHpcProfile rph ingress invalidEtsWps reject nonEtsWps ignore validEtsWps accept
To display a configured HPC call profile:
% show profiles services hpcCallProfile testHpcProfile
state enabled;
rph {
ingress {
invalidEtsWps reject;
validEtsWps accept;
nonEtsWps ignore;
}
egress {
validEtsWps dontInclude;
nonEtsWps include;
}
}
getsStrings {
featureCode {
fc *272;
}
accessNumber {
an 7106274387;
}
numberTranslation {
nt 7102001234;
}
}
queue {
state enabled;
length 50;
timeout 60;
}
dscp {
egress {
useRecvdValue enabled;
}
}
dscpValue 50;
To delete a configured HPC call profile:
% delete profiles services hpcCallProfile testHpcProfile % commit
Overview
Content Tools