Cisco Cisco Tunnel Terminating Gateway (TTG)
P-GW Changes in Release 17
P-GW Enhancements for 17.1 ▀
Release Change Reference, StarOS Release 17 ▄
375
CSCup44058 - Acct msg shows both v4 and v6 addr even if v4 is denied for
static alloc
Feature Changes
Correct IP Address and PDN Type sent in RADIUS Accounting.
Previous Behavior: If there was a UE request for dual PDP type and either IPv4 or IPv6 PDP type failed, then the
RADIUS account would have a failed IP address/PDP type.
RADIUS account would have a failed IP address/PDP type.
New Behavior: If there is a UE request for dual PDP type and either IPv4/IPv6 address allocation fails, a new PDP
type and correct IP address is sent in RADIUS accounting.”
type and correct IP address is sent in RADIUS accounting.”
CSCup44635 - SM support for CSCul22770, SFR - PSP algorithm modification
Feature Changes
Modification in Bandwidth Policy Selection During Call Setup
Previous Behavior: A single bandwidth policy was being sent from the session manager to ECS for validation. When
an invalid bandwidth policy was received from RADIUS, the call was being terminated.
an invalid bandwidth policy was received from RADIUS, the call was being terminated.
New Behavior: Primary and fallback policies are sent from SM to ECS. When an invalid bandwidth policy is received
from RADIUS, bandwidth policy from APN can be applied if it is valid and the call will remain active.
from RADIUS, bandwidth policy from APN can be applied if it is valid and the call will remain active.
Customer Impact: This will help prevent termination of calls when an incorrect bandwidth policy is sent through
RADIUS.
RADIUS.
CSCup59406 - sesstrc task in over state during longevity/aggravator run
Feature Changes
Configuring Session Trace File Type
To address the issues caused when the sesstrc task allocates memory over the allotted limit, under a random subscriber
session trace load tests on P-GW/S-GW, support for B-type XML files is introduced in addition to the A-type files
already supported.
session trace load tests on P-GW/S-GW, support for B-type XML files is introduced in addition to the A-type files
already supported.
Previous Behavior: The file type was A-type XML file and the type could not be changed.
New Behavior: The CLI has been modified (see Command Changes section) to allow the operator to select the file
type generated by session trace. When B-type XML files are used, multiple trace recording session elements will be
encoded in a single XML file. It should be noted that different trace recording sessions may be associated with different
TCEs, according to the TCE IP address specified during activation. As expected, each Type-B XML file will contain
traceRecSession elements that pertain only to the same target TCE. There will be different XML Type-B files created
for different TCEs and they will be placed in different tce_x directories for transmission to the target TCEs.
type generated by session trace. When B-type XML files are used, multiple trace recording session elements will be
encoded in a single XML file. It should be noted that different trace recording sessions may be associated with different
TCEs, according to the TCE IP address specified during activation. As expected, each Type-B XML file will contain
traceRecSession elements that pertain only to the same target TCE. There will be different XML Type-B files created
for different TCEs and they will be placed in different tce_x directories for transmission to the target TCEs.