Cisco Cisco ASR 5000
MTC Congestion Control
Configuring MTC Congestion Control ▀
SGSN Administration Guide, StarOS Release 18 ▄
Important:
For SM congestion to work, the apn-based option must be configured with the
sm-messages reject command .
rau | service-req
: Defines congestion response for Routing Area Update messages or Service Request
messages.
drop | reject
: Defines the congestion response action, drop or reject, to be taken when RAU or Service
Request messages are received during an active call.
low-priority-ind-ue
: Instructs the SGSN to only take defined action if messages include LAPI.
apn-based
: Instructs the SGSN to reject a new call based on the subscribed APN if congestion control is
configured for that APN under an applicable Operator Policy.
If both the LAPI and APN-based options are included in the action-profile, then the call event will only be
rejected if both conditions are matched.
Verifying the SGSN Congestion Control Configuration
Use the command illustrated below to verify the configuration created with the commands in the Configuring SGSN
Congestion Control section above.
Congestion Control section above.
The following command is entered from the Exec mode. NOTE that the entire command must be typed, tabbing does
not function for this command.
not function for this command.
[local]SGSN1-NH# show sgsn-mode
The following provides a sample of the display generated by the command illustrated above:
[local]R16sgsn-Sim# show sgsn-mode
Congestion Action Profile
-------------------------
Congestion Action Profile Name:profile1
New Call Policy :Reject only LAPI devices
Active Call Policy :
Routing Area Update :Not configured
Service Request :Reject
APN Based Congestion Control :
MM messages :Not configured
SM messages :Reject