Cisco Cisco ASR 5000
Subscriber Overcharging Protection
Overcharging Protection - SGSN Configuration ▀
SGSN Administration Guide, StarOS Release 18 ▄
Note:
<apn_profile_name>
is the name of a previously configured APN profile. For more information, refer to the
Operator Policy chapter, also in this book.
RANAP Cause Trigger Configuration
This section provides the configuration example to enable the RANAP cause trigger and define the trigger message
value:
value:
configure
context <context_name>
iups-service <iups_service_name>
loss-of-radio-coverage ranap-cause <cause> end
Note:
<context_name>
is the name of the previously configured context in which the IuPS service has been
configured.
<cause>
is an integer from 1 to 512 (the range of reasons is a part of the set defined by 3GPP TS 25.413) that
allows configuration of the RANAP Iu release cause code to be included in messages. Default is 46 (MS/UE
radio connection lost).
radio connection lost).
Verifying the Feature Configuration
This section explains how to display the configurations after saving them in a .cfg file as described in the Verifying and
Saving Your Configuration chapter elsewhere in this guide.
Saving Your Configuration chapter elsewhere in this guide.
Important:
All commands listed here are under Exec mode. Not all commands are available on all platforms.
These instructions are used to verify the overcharging protection support configuration.
Step 1
Verify that your overcharging support is configured properly by entering the following command in Exec Mode:
show apn-profile full name apn_profile_name
The output of this command displays the entire configuration for the APN profile configuration. Only the
portion related to overcharging protection configuration in the SGSN is displayed below. Note that the profile
name is an example:
portion related to overcharging protection configuration in the SGSN is displayed below. Note that the profile
name is an example:
APN Profile name: : apnprofile1
Resolution Priority: : dns-fallback
...
...