Add_workflow_for_techpubs | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Panel | |
---|---|
In this Section:
|
Info | ||
---|---|---|
| ||
Related articles: |
Excerpt | |||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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:
There are two methods in HPC call classification:
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
|
The SBC provides HPC calls with priority treatment over non-HPC calls during the initial SIP INVITE request processing.
The SBC determines whether a call is an HPC call based on the following:
The SBC accepts the ets and wps namespaces as valid with only the following resource values:
Info | ||
---|---|---|
| ||
The SBC uses the multiple value format from RFC 4412 to format an RPH. |
Info | ||
---|---|---|
| ||
This feature does not impact other namespaces that the SBC supports. |
The SBC identifies GETS-AN, GETS-NT or GETS-Feature Code (FC) string in the received user string of the Request-URI of an initial SIP INVITE. The received user string refers to the user portion of a SIP:URI with user=phone or the ‘telephone-subscriber’ portion of a TEL:URI (ignoring any visual separators). The SBC allows up to ten GETS-AN, ten GETS-NT, and four GETS-FC strings to be associated with an IP trunk group (TG). For more information on GETS Strings, refer to HPC Call Profile - CLI.
To identify a GETS-FC string in the Request-URI, the SBC performs string matches against provisioned GETS-FC strings (of length [n]). The SBC detects a successful match for a GETS provisioned TG when:
If a GETS-FC string is identified in the initial SIP INVITE Request-URI, the SBC rejects the call with a SIP 403 (Forbidden) response with no RPH.
Info | ||
---|---|---|
| ||
Processing of the GETS-FC string takes precedence over the GETS-AN and GETS-NT strings. |
To identify a GETS-AN or GETS-NT in the Request-URI, the SBC performs string matches against provisioned GETS-AN or GETS-NT strings (of length [m]) respectively. The SBC detects a successful match for a GETS provisioned TG when:
Info | ||
---|---|---|
| ||
For more information, refer to SIP Resource Priority Header Support for HPC-GETS. |
When the dscpValue
parameter is modified, the new value applies only to new HPC calls while the existing HPC calls use the previously configured value.
The following call flow illustrates the DSCP marking for HPC calls.
Pagebreak |
---|
Figure 1: DSCP Marking for HPC Call
Info | ||
---|---|---|
| ||
The SIP 100 Trying provisional response is handled as an exception. The SBC sends this provisional response with a DSCP value that is configured in the SIP signaling port because the provisional response is sent before an incoming call is determined as an HPC or non-HPC call (see the preceding call flow). |
Pagebreak |
---|
The following call flow illustrates the DSCP marking for non-HPC calls.
Figure 2: DSCP Marking for Non-HPC Call
In previous releases, the SBC supported Differentiated Services Code Point (DSCP) marking for non-audio streams (video and T.140 text) for both High Priority Calls (HPC) and non-HPC calls. The SBC Core is enhanced to support alternative DSCP marking for T.140 text media stream types from what is used for video and audio media stream types irrespective if the request has an RPH header.
For Government Emergency Telecommunications Service (GETS) / Wireless Priority Service (WPS) calls ( high priority calls), DSCP markings are associated with the provisioned ETS value and in the outgoing message includes an RPH containing the provisioned ETS.x. When the message is destined for the internal network, there is a single DSCP associated with that ETS value and assigned to all associated signaling and media packets. When it is destined for an external network, there is a single DSCP associated for every peer. In other words, there is a set of DSCP values rather than a single DSCP value in each case, one each for signaling, audio, video and text.
A new parameter "T140 DSCP" is added to QosValues for DSCP marking of T.140 text. The DSCP value for T.140 packets is configured on Packet Service Profile (PSP) basis.
Info | ||
---|---|---|
| ||
When the parameter "DSCP Passthrough" is enabled, DSCP Pass-through takes precedence over the "T.140 DSCP" setting. |
The following figure depicts a T.140 media call.
Figure 3: T.140 Media Call Flow
Pagebreak |
---|