Cisco Cisco Packet Data Gateway (PDG) Notas De La Versión
SGSN Changes in Release 15.0
▀ SGSN Enhancements for October 31, 2014
▄ Cisco ASR 5x00 Release Change Reference
468
The output of the
show call-control-profile full name profile_name
no longer displays the following
fields or any related values:
Authentication Activate ANY (UMTS/GPRS)
Authentication Activate UMTS
Authentication Activate GPRS
Authentication Activate First/Primary ANY (UMTS/GPRS)
Authentication Activate First/Primary UMTS
Authentication Activate First/Primary GPRS
CSCuo86321 - issue with show subscriber and clear subscriber
Feature Changes
Evaluation of Idle-Time
The
show subscribers
and
clear subscribers
commands were not performing as expected when the
idle-
time
keyword was included with the commands.
Previous Behavior: Evaluation of idle-time was based on MM signaling.
New Behavior: Evaluation of idle-time is now based on the data session idle time of the subscriber. The changes will
result in:
result in:
Both of the following commands will display the same number of subscribers based on the idle time calculation:
show sub summary idle-time greater-than 1 | grep T
show sub idle-time greater-than 1
The following command functions are in sync so that clearing does not occur if the show command indicates no
subscribers are found:
show subscribers pan <panama> idle-time greater-than <number>
clear subscribers pan <panama> idle-time greater-than <number>
Yes/No confirmation has been added to the
clear subscribers apn <apn_name> idle-time greater-
than <number>
to ensure subscribers are not accidentally cleared.
CSCuo93431 - PDP failure due to subscribers stuck in disconnecting state
Feature Changes
Changes to Deactivation Procedures for Duplicate PDP Context
Previous Behavior: When the SGSN received a duplicate PDP (primary or secondary) Context Activation Request
against a PDP (primary or secondary) context currently under deactivation, then the SGSN does not honor the duplicate
Activate Request (primary or secondary) and replies with by sending an SM-STATUS (with cause message ‘not
compatible with protocol state’).
against a PDP (primary or secondary) context currently under deactivation, then the SGSN does not honor the duplicate
Activate Request (primary or secondary) and replies with by sending an SM-STATUS (with cause message ‘not
compatible with protocol state’).