Cisco Cisco ASR 5000 Technical Manual

Page of 25
Apn−based: This indicates that requests for the Access Point Names (APNs) that are configured for
the congestion control in the operator policy will be dropped. Here is the CLI syntax:
drop <call−event> lapi
Note: The apn network−identifier command in the operator policy is used in order to configure the
congestion control for an APN.
• 
Note: If the congestion action profile is configured with both the LAPI and APN−based options, then call
events will be dropped only if both conditions are matched.
Exclude Emergency Events
This allows the emergency requests to be processed even when the threshold has been exceeded. Here is the
CLI syntax:
exclude−emergency−events
When this is configured, the congestion action rejects and drops are not applied for these messages in
emergency−attached UEs:
TAU requests
• 
Service requests
• 
Handovers
• 
ADDN−PDN requests
• 
Exclude Voice Events
This allows voice calls to be processed even when the threshold has been exceeded. Here is the CLI syntax:
exclude−voice−events
None
This specifies that no congestion control action should be taken for inbound requests when the congestion
control threshold has been reached. Here is the CLI syntax:
none { addn−brr−requests | addn−pdn−connects | combined−attaches | handovers |
 psattaches | s1−setups | service−request | tau−request }
Here are the details of the call events that can be configured for this action (none is the default action for all of
these call events):
Addn−brr−request: This causes no congestion control action to be completed for packets that contain
UE−initiated bearer resource requests.
• 
Addn−pdn−connect: This causes no congestion control action to be completed for additional Packet
Data Network (PDN) context connections.
• 
Brr−ctxt−mod−requests: This causes no congestion control action to be completed for packets that
contain bearer context modification requests.
•