Cisco Cisco Packet Data Gateway (PDG)
P-GW Changes in Release 17
▀ P-GW Enhancements for 17.1
▄ Release Change Reference, StarOS Release 17
374
configure
context context_name
apn apn_name
ipv6 access-group group_name [ in | out ] [ fallback-enabled ]
end
Notes:
fallback-enabled
: When invalid ACL is received from RADIUS during Context Activation, ACL in this
APN will be applied so there is no loss of CDR or missing charging information.
By default, ACL fallback is disabled.
Run command without
fallback-enabled
option to disable ACL fallback for a previously configured ACL
applied to a particular APN.
Performance Indicator Changes
show apn name apn_name
The following fields have been added to show whether the ACL fallback option is enabled or disabled:
Ipv4 Input ACL Fallback
Ipv4 Output ACL Fallback
Ipv6 Input ACL Fallback
Ipv6 Output ACL Fallback
CSCuo92945 - 110 cause when temp fail not configured is treating as success
Feature Changes
Call Flow and Bearer Creation
Previous Behavior: In pgw-service, if
egtp cause-code temp-fail timeout
was not enabled and a 110 cause
code EGTP_CAUSE_TEMP_REJECTED_DUE_TO_HANDOVER_IN_PROGRESS was received in the create bearer
response message, then the P-GW created a new dedicated bearer.
response message, then the P-GW created a new dedicated bearer.
New Behavior: In pgw-service, if
egtp cause-code temp-fail timeout
is not enabled and a 110 cause code
EGTP_CAUSE_TEMP_REJECTED_DUE_TO_HANDOVER_IN_PROGRESS is received in the create bearer
response message, then the P-GW does not create a new bearer. Instead, it sends a
RESOURCE_ALLOCATION_FAILURE message to the PCRF.
response message, then the P-GW does not create a new bearer. Instead, it sends a
RESOURCE_ALLOCATION_FAILURE message to the PCRF.