Cisco Cisco Packet Data Gateway (PDG) Nota Di Rilascio
P-GW Changes in Release 15.0
▀ P-GW Enhancements for October 31, 2014
▄ Cisco ASR 5x00 Release Change Reference
384
CSCuo06912 - PGW call fails if Framed-Pool enforced from radius
Feature Changes
P-GW Call Fails if Frame-Pool Enforced from Radius
In P-GW, if radius returned ip pool in access accept, then this scenario was not handled correctly.
Previous Behavior: For P-GW, if radius returned ip pool for ip address alloc method as no-dynamic, then ip address
allocation was not successful.
allocation was not successful.
New Behavior: For P-GW, if radius returns ip pool for ip address alloc method as no-dynamic, then ip address
allocation will be successful.
allocation will be successful.
Customer Impact: The customer will be able to use no-dynamic ip alloc method for radius returned ip pool.
CSCuo95038 - PGW forces lower AMBR values than received
Feature Changes
P-GW forces lower AMBR values than received
Previous Behavior: In absence of PCRF, the APN AMBR that was received in the MOB BEARER REQUEST during
GnGp HO was not applied.
GnGp HO was not applied.
New Behavior: In absence of PCRF, the APN AMBR received in MOB BEARER REQUEST during GnGp HO will
now be applied.
now be applied.
CSCuq39165 - [OCS FOA] Create Session Response is not sent out from PGW
Feature Changes
Create Session Response is Not Sent Out From P-GW
Previous Behavior: In an LTE new call, the call failed with a CS Response ‘NO_RESOURCE_AVAILABLE’ if the
PAP/CHAP parameters were absent in the CS Request message and the PAP/CHAP auth was configured as mandatory
in the boxer config.
PAP/CHAP parameters were absent in the CS Request message and the PAP/CHAP auth was configured as mandatory
in the boxer config.
New Behavior: A call now fails with the CS Response ‘USER_AUTHENTICATION_FAILED’.