Cisco Cisco Packet Data Gateway (PDG)
ddn [ arp-watermark | cause | lapi ]
The ddn keyword configures the action to be taken for all DDN requests. The operator can reject DDN requests
based on ARP or LAPI values or both. Also, there is an option provided to reject all DDN requests without
using ARP/LAPI values.
based on ARP or LAPI values or both. Also, there is an option provided to reject all DDN requests without
using ARP/LAPI values.
The arp-watermark keyword specifies that DDN reject is applicable for ARP values greater than or equal
to the ARP specified. The ARP value ranges from 1 through 15.
to the ARP specified. The ARP value ranges from 1 through 15.
The cause keyword rejects DDN with the specified cause value. The valid cause value ranges from 1 through
255. The default value is 90 with the display message "Unable to page ue".
255. The default value is 90 with the display message "Unable to page ue".
The lapi keyword for DDN specifies that DDN rejection is applicable for UEs with LAPI.
This keyword option will be available only if a valid license is installed.
none
Disables DDN configuration.
handovers
Rejects handover attempts.
ps-attaches
Rejects packet switched Attach requests.
s1-setups time-to-wait { 1 | 10 | 2 | 20 | 50 | 60 }
Rejects S1 setup attempts with an eNodeB after 1, 2, 10, 20, 50 or 60 seconds.
This keyword option will be available only if a valid license is installed.
service-request
Rejects all service requests.
This keyword option will be available only if a valid license is installed.
tau-request
Rejects all Tracking Area Update requests.
[ lapi ] [ apn-based ]
These keyword options are available only if a valid license is installed.
When a congestion action profile is configured with the reject <call-event> lapi option, only requests with
Low Access Priority Indication (LAPI) will be rejected for those call-events during congestion. However, if
the call-event is configured without the lapi option, all LAPI and non-LAPI requests will be rejected.
Low Access Priority Indication (LAPI) will be rejected for those call-events during congestion. However, if
the call-event is configured without the lapi option, all LAPI and non-LAPI requests will be rejected.
If the congestion action profile is configured with the reject <call-event> apn-based option, only the requests
for those APNs configured for congestion control in the Operator Policy will be rejected for those call-events
during congestion. However, if the call-event is configured without the apn-based option, all requests will
be rejected. Refer to the apn network-identifier command in the Operator Policy Configuration Mode chapter
to enable congestion control for a specific APN.
for those APNs configured for congestion control in the Operator Policy will be rejected for those call-events
during congestion. However, if the call-event is configured without the apn-based option, all requests will
be rejected. Refer to the apn network-identifier command in the Operator Policy Configuration Mode chapter
to enable congestion control for a specific APN.
Command Line Interface Reference, Modes C - D, StarOS Release 19
421
Congestion Action Profile Configuration Mode Commands
reject