Cisco Cisco ASR 5000
Call Control Profile Configuration Mode
▀ apn-restriction
▄ Command Line Interface Reference, StarOS Release 18
1916
apn-restriction
Enables the APN restriction feature and configures the instruction for the SGSN on the action to take when an APN
restriction value is received from the GGSN during an Update PDP Context procedure.
restriction value is received from the GGSN during an Update PDP Context procedure.
Product
SGSN
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > Call Control Profile Configuration
configure > call-control-profile profile_name
Entering the above command sequence results in the following prompt:
[local]host_name(config-call-control-profile-profile_name)#
Syntax
apn-restriction update-policy deactivate restriction
default apn-restriction
default
Creates a default APN restriction configuration.
update-policy deactivate
restriction
Specifies one of the two restriction types to define the appropriate action if the APN restriction value received
conflicts with the stored value:
conflicts with the stored value:
least-restrictive
set the least restrictive value applicable when there are no already active PDP
context(s).
most-restrictive
sets the most stringent restriction required by any already active PDP context(s).
Usage
When this feature is enabled, the SGSN will send the maximum APN restriction value in every CPC Request
message sent to the GGSN. The SGSN expects to receive an APN restriction value in each PDP Context
received from the GGSN. The SGSN stores and compares received APN restriction values to check for
conflicts. In the case of a conflict, the SGSN rejects the PDP Context with appropriate messages and error
codes to the MS.
If an APN restriction value is not assigned by the GGSN, the SGSN assumes the value of “1” (least
restrictive) to allow APN restriction rules will be possible when valid values are assigned for new PDP
Context(s) from the same MS.
The least or most restrictive values of the APN restriction are applicable only for the Gn SGSN, as the APN
restriction can be present in UPCQ/UPCR for Gn SGSN and this configuration is required to determine the
PDN to be de-activated when an APN restriction violation occurs during modification procedures in the Gn
SGSN. In the case of S4-SGSN, the APN restriction arrives at the S4-SGSN only in Create Session Response
during activation. During activation in S4-SGSN, a PDN connection that violates the current Maximum APN
message sent to the GGSN. The SGSN expects to receive an APN restriction value in each PDP Context
received from the GGSN. The SGSN stores and compares received APN restriction values to check for
conflicts. In the case of a conflict, the SGSN rejects the PDP Context with appropriate messages and error
codes to the MS.
If an APN restriction value is not assigned by the GGSN, the SGSN assumes the value of “1” (least
restrictive) to allow APN restriction rules will be possible when valid values are assigned for new PDP
Context(s) from the same MS.
The least or most restrictive values of the APN restriction are applicable only for the Gn SGSN, as the APN
restriction can be present in UPCQ/UPCR for Gn SGSN and this configuration is required to determine the
PDN to be de-activated when an APN restriction violation occurs during modification procedures in the Gn
SGSN. In the case of S4-SGSN, the APN restriction arrives at the S4-SGSN only in Create Session Response
during activation. During activation in S4-SGSN, a PDN connection that violates the current Maximum APN