для Cisco Cisco Packet Data Gateway (PDG)
ePDG Changes in Release 17
▀ ePDG Enhancements for 17.2
▄ Release Change Reference, StarOS Release 17
160
ePDG Enhancements for 17.2
This section identifies all of the ePDG enhancements included in this release:
Feature Changes - new or modified features or behavior changes. For details, refer to the ePDG Administration Guide
for this release.
for this release.
Command Changes - changes to any of the CLI command syntax. For details, refer to the Command Line Interface
Reference for this release.
Reference for this release.
Performance Indicator Changes - new, modified, and deprecated bulk statistics, disconnect reasons, counters and/or
fields in new or modified schema and/or show command output. For details, refer to the Statistics and Counters
Reference for this release.
fields in new or modified schema and/or show command output. For details, refer to the Statistics and Counters
Reference for this release.
Important:
This release includes enhancements that are applicable to multiple products. The following lists the
various multi-product enhancements sections, some of which might include content applicable to your ePDG.
AAA Enhancements
CF Enhancements
ECS Enhancements
Firewall Enhancements
GTPP Enhancements
Lawful Intercept Enhancements
MVG Enhancements
NAT Enhancements
SNMP MIB Enhancements
System and Platform Enhancements
CSCus30276, CSCus30296 - Support for tunnel endpt ip in SWm interface
Feature Changes
Passing on UE tunnel Endpoint Address over SWm
With this release ePDG to supports passing on UE tunnel Endpoint Address over SWm or S2b.
The provisioning of UE Tunnel Endpoint-IP (IKEv2 tunnel endpoint incase of NAT) to AAA server will help the
operator to identifying the UE's location at AAA server. The operator uses this information to control the access or to
decide the UE connections. Operator can lookup the GeoIP database (GeoDB) against the UE tunnel endpoint IP to
identify the country from where the UE is connecting from. Based on this information operator can allow the call or
reject it(using auth-failure) according to the policy configured. Lets say the policy dictates that the VoWiFi calls are
allowed only for UEs connecting from home country but not allowed while roaming outside the country, they can save
the revenue leakage using this information.
operator to identifying the UE's location at AAA server. The operator uses this information to control the access or to
decide the UE connections. Operator can lookup the GeoIP database (GeoDB) against the UE tunnel endpoint IP to
identify the country from where the UE is connecting from. Based on this information operator can allow the call or
reject it(using auth-failure) according to the policy configured. Lets say the policy dictates that the VoWiFi calls are
allowed only for UEs connecting from home country but not allowed while roaming outside the country, they can save
the revenue leakage using this information.