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

Compare with Current View Page History

Version 1 Current »

 

Use this flag to allow the 

Unable to show "metadata-from": No such page "_space_variables"
 to select the GIBA security mechanism when a REGISTER message is received without specific security headers. The 
Unable to show "metadata-from": No such page "_space_variables"
 validates Source IP Address against Via header IP Address and transparently passes UEs Via header in egress messages towards network entities. If REGISTER message is received with "sec-agree" in Proxy-Require header along with Auth headers, and no IP Sec profile is configured, the 
Unable to show "metadata-from": No such page "_space_variables"
 rejects the message with "4xx Bad Extension" error response irrespective of the accessClass flag setting.

When GIBA security mechanism is selected and Via header is configured to pass transparently to egress leg, 

Unable to show "metadata-from": No such page "_space_variables"
 inserts a “received” parameter with the source IP address of the PDU if the host portion of the UE’s Via header does not equate to the source IP address seen by the 
Unable to show "metadata-from": No such page "_space_variables"
.

Command Syntax

% set addressContext <name> zone <name> sipTrunkGroup <name> signaling accessClass <3GPP | none>

Command Parameters

Access Class Parameter

ParameterDescription
accessClass

Select 3GPP to select GIBA security mechanism when a REGISTER message is received without specific security headers. Otherwise, select none for the

Unable to show "metadata-from": No such page "_space_variables"
to use SIP Digest without TLS authentication.

  • 3GPP  
  • none (default)
 

  • No labels