Cisco Cisco Packet Data Gateway (PDG)
SAEGW Changes in Release 16
▀ SAEGW Enhancements for 16.0
▄ Release Change Reference, StarOS Release 16
418
Notes:
no
disables private extension overcharge protection. If this option is not enabled in the egtp-service, then by
default the EGTPC layer will encode/decode overcharge-protection related data in the Indication information
element. The default setting is disabled.
element. The default setting is disabled.
If this command is enabled in the egtp-service then EGTPC will encode/decode overcharge-protection related
data in/from the private extension instead of the Indication information element.
Important:
An Overcharge-protection license is required to use this feature. In addition, the overcharge-
protection command must be configured in APN Profile Configuration Mode for this feature to work properly.
Performance Indicator Changes
show egtp-service name
This command has been enhanced to list the private-extension overcharge-protection setting on the S-GW, if
configured.
configured.
GTPC Private Extension
Overcharging Protection (Seconds): Enabled or Disabled
CSCui42572 - Error response handling at SGW
Feature Changes
Improved Error Response Handling at the S-GW
The software has been enhanced to improve error response handling at the S-GW when an erroneous message is
received by EGTPC from a peer. On receiving a bad response from the peer, instead of dropping the message while
doing validation, EGTPC informs the S-GW about the bad response received. The S-GW uses this notification from
EGTPC that a bad response is received to send a proper response to the other peer. This will reduce load on the S-GW
due to retransmissions. This also helps in capturing statistics based on the correct cause code.
received by EGTPC from a peer. On receiving a bad response from the peer, instead of dropping the message while
doing validation, EGTPC informs the S-GW about the bad response received. The S-GW uses this notification from
EGTPC that a bad response is received to send a proper response to the other peer. This will reduce load on the S-GW
due to retransmissions. This also helps in capturing statistics based on the correct cause code.
Previous Behavior: When an erroneous response message is received by the S-GW EGTPC service from a peer, it is
dropped while performing validation. After all retries of the request message, the EGTPC service then informs the other
peer that there was no response from the peer.
dropped while performing validation. After all retries of the request message, the EGTPC service then informs the other
peer that there was no response from the peer.
New Behavior: If error-response-handling is enabled, and EGTPC receives the first error response, it now sends back
Invalid reply from remote peer in the response message to the other peer.
Invalid reply from remote peer in the response message to the other peer.
Customer Impact: There will be no request message retries if the error response is received.
Command Changes
gtpc error-response-handling
The new command
gtpc error-response-handling
has been added to EGTP Service Configuration Mode. This
command controls error response handling at the S-GW when an erroneous message is received by EGTPC from a peer.