Cisco Cisco Packet Data Gateway (PDG)
P-GW Changes in Release 17
▀ P-GW Enhancements for 17.0
▄ Release Change Reference, StarOS Release 17
402
csfb-recv-resumedenied
mobility-recv-retransctxrsp
mobility-sent-retransidtrsp
mobility-sent-retransalertmmeack
mobility-sent-retransueactivityack
The following counters have been removed:
tun-recv-retransbearrescmd-fail
tun-recv-retransmodbearfail
tun-recv-retransdelbearfail
tun-sent-noRspPgwRstnotfreq
mobility-recv-retransctxack
mobility-recv-retransidtrsp
mobility-recv-retransfwdrelrsp
mobility-recv-retransfwdaccack
mobility-recv-retransfwdrelcmpack
mobility-recv-retransrelcancelrsp
mobility-recv-retransalertmmeack
mobility-recv-retransueactivityack
CSCup60931 - [17.0] PGW should not send UBR after PCSCF recovery MBR on
emergency APN
Feature Changes
P-GW Should Not Sent a UBR After P-CSCF Recovery MBR on an Emergency APN
Previous Behavior: When P-CSCF recovery gets initiated on an Active call, the P-CSCF Discovery gets re-initiated
for that call. In addition, P-CSCF discovery gets initiated during Call Bring-up (PDN Establishment). P-CSCF
Discovery upon PDN establishment was in place in StarOS Release 16.0.
for that call. In addition, P-CSCF discovery gets initiated during Call Bring-up (PDN Establishment). P-CSCF
Discovery upon PDN establishment was in place in StarOS Release 16.0.
New Behavior: For an Emergency Call, P-CSCF Discovery upon PDN establishment is applicable but P-CSCF
recovery is not applicable. Even if a trigger is received for P-CSCF Recovery for Emergency PDN for the Access side
(mostly for a multi-pdn scenario), then the P-GW will not perform P-CSCF Recovery processing for that trigger.
recovery is not applicable. Even if a trigger is received for P-CSCF Recovery for Emergency PDN for the Access side
(mostly for a multi-pdn scenario), then the P-GW will not perform P-CSCF Recovery processing for that trigger.
Important:
See CSCum17462 for additional information.