You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

 

The 

Unable to show "metadata-from": No such page "_space_variables"
platform supports processing the Resource-Priority Header (RPH) to classify a call as an emergency call. If the namespace and r-priority of a received r-value in the initial INVITE RPH exactly matches with the namespace and r-priority respectively of a configured value, then the call is considered an emergency call. The comparison is case-insensitive, and multiple r-values can be processed in incoming INVITE.

The SBC can use the IPSP transparency flag 'resourcePriorityOptionTag' to transparently pass the 'resource-priority' option tag received in Require or Supported header of various SIP messages, such as INVITE, REGISTER, SUBSCRIBE (but not in-dialog SUBSCRIBE), PUBLISH, REFER, NOTIFY, UPDATE, MESSAGE, OPTIONS, CANCEL, and GW-GW transparency. This flag is available to both the ERE and external PSX. Refer to Common IP Attributes - SIP - CLI for CLI details.

IMPORTANT

The Transparency Profile is the recommended method of configuring transparency on the SBC Core for new deployments as well as when applying additional transparency configurations to existing deployments. Do not use IP Signaling Profile flags in these scenarios because the flags will be retired in upcoming releases.

Refer to the SBC SIP Transparency Implementation Guide for additional information.

Command Syntax

The CLI syntax to configure the SIP RPH Profile is shown below:

% set profiles services sipResourcePriorityHeaderProfile <RPHprofile name> 
	rphEmergencyMatchingConfig <RPH namespace> <RPH priority>
	sendEgressRphForEmergency <RPH namespace> <RPH priority>
	
% show table profiles services sipResourcePriorityHeaderProfile <RPHprofile name> 

% delete profiles services sipResourcePriorityHeaderProfile <RPHprofile name>

Command Parameters

SIP Resource Priority Header Profile Parameters

Parameter

Length/Range

Description

sipResourcePriorityHeaderProfile

1-23Use this parameter specify the name of the Resource Priority Header Profile configured on the node. A maximum of 32 RPH Profiles can be created.
rphEmergencyMatchingConfig
1-31

Use this parameter to specify the r-value configuration consisting of the following:

  • <RPH namespace> – The namespace associated with the r-value (alphanumeric string with a maximum size of 31 characters).

  • <RPH priority> – Specifies the priority associated with the r-value. (alphanumeric string with a maximum size of 31 characters).

A maximum of 24 r-values can be configured. The r-values are unique case-insensitive.

sendEgressRphForEmergency1-31

Use this parameter to specify RPH value to send from egress, if configured.

  • <RPH namespace> – The namespace associated with the r-value (alphanumeric string with a maximum size of 31 characters).

  • <RPH priority> – Specifies the priority associated with the r-value. (alphanumeric string with a maximum size of 31 characters).

Command Examples

To create an RPH profile:

% set profiles services sipResourcePriorityHeaderProfile RPHProfile
% set profiles services sipResourcePriorityHeaderProfile RPHProfile rphEmergencyMatchingConfig RValue1 1
% set profiles services sipResourcePriorityHeaderProfile RPHProfile sendEgressRphForEmergency Rvalue1 2
% commit

% show profiles services sipResourcePriorityHeaderProfile
sipResourcePriorityHeaderProfile RPHProfile {
    rphEmergencyMatchingConfig RValue1 1;
    sendEgressRphForEmergency Rvalue1 2;
}


To attach an RPH profile to an emergency profile:

% set profiles services emergencyCallProfile ECProfile resPriorityHeaderProfile RPHProfile


To associate the emergency profile to a SIP Trunk Group:

% set addressContext ac1 zone zoneTest sipTrunkGroup TG-1 services emergencyCallProfile ECProfile



  • No labels