Cisco Cisco Packet Data Gateway (PDG)
P-GW Changes in Release 16
P-GW Enhancements for 16.0 ▀
Release Change Reference, StarOS Release 16 ▄
345
Num license exceeded
No Session Manager
Congestion Policy Applied
Input pacing queue exceeded
ims auth failed
aaa auth req exceeded/failed
static ip not present
ms req invalid ip
DHCP IP Address Not Present
mem_alloc_failed
CSCua97985 - Graceful Shutdown of PDN with inactive VoLTE calls
Feature Changes
Graceful Shutdown Support for VoLTE
There are likely to be cases where an Operator would need to shut down a P-GW/S-GW/SAEGW for
upgrade/maintenance purpose; during that time, there is a need for a means by which the VoLTE calls on such nodes are
cleaned up in a graceful manner, so that ongoing calls are not interrupted, thus improving user experience.
upgrade/maintenance purpose; during that time, there is a need for a means by which the VoLTE calls on such nodes are
cleaned up in a graceful manner, so that ongoing calls are not interrupted, thus improving user experience.
This could also be used in case there is a need to migrate a VoLTE APN from one P-GW to another. This feature will
help in doing this VoLTE APN migration in a graceful manner. A new qualifier,
help in doing this VoLTE APN migration in a graceful manner. A new qualifier,
non-volte-call
, has been added to
the
clear subscribers
CLI to clean up only those PDNs that have no Active Voice bearer. Identification of the
VoLTE PDN and bearer is done using the VoLTE call identification configuration discussed above.
Until the time the upgrade/maintenance is going on, the new calls will be rejected so that an alternate P-GW/S-
GW/SAEGW can handle it. This is done using the
GW/SAEGW can handle it. This is done using the
new-call policy
configuration.
Below are the set of steps that can be carried out to gracefully clean up VoLTE PDNs on a node:
1. Use call identification configuration to configure the VoLTE APN to do the VoLTE PDN and bearer
identification.
2. Using the new call-policy configuration, configure the node to reject any new calls coming on the node, so that
these new calls get directed to an alternate PDN.
3. Using the
clear subscribers
CLI with
non-volte-call
qualifier in it, initiate the clean up of PDNs that
don’t have any Active Voice bearer.
4. Wait for some time and execute the
clear subscribers
CLI again to clean up any non-active VoLTE PDNs.
Repeat this step until all of the VoLTE PDNs are cleaned up.
Further enhancements are planned for this feature in future releases.
Customer Impact: Several features added for VoLTE in 16.0 will provide a lot of value to Operators; they help
Operator in providing high quality VoLTE service to ensure better user experience for VoLTE service users.
Operator in providing high quality VoLTE service to ensure better user experience for VoLTE service users.