You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Motivation
In the network during draining, when setting the erGW not to accept new requests (reject with "no resources available"), the many SGWs/SGSNs from different networks could not correlate the session creation requests and the responses. The analysis was that the root cause of the issue is that erGW returns the GTP rejections with the TEID GTP header value set to 0. While the specs (e.g. 3GPP 129.274) leave some space for interpretation.
Proposal
Implement in the returning of the SGW TEID in the session error handling code.
Current behavior
The SGW TEID is not returning in the session error handling code.
Expected behavior
The SGW TEID is returning in the session error handling code.
The text was updated successfully, but these errors were encountered:
erGW
version2.8.6
Description
In the network during draining, when setting the
erGW
not to accept new requests (reject with"no resources available"
), the manySGWs/SGSNs
from different networks could not correlate the session creation requests and the responses. The analysis was that the root cause of the issue is thaterGW
returns theGTP
rejections with theTEID GTP
header value set to0
. While the specs (e.g.3GPP 129.274
) leave some space for interpretation.Implement in the returning of the
SGW TEID
in the session error handling code.Current behavior
The
SGW TEID
is not returning in the session error handling code.Expected behavior
The
SGW TEID
is returning in the session error handling code.The text was updated successfully, but these errors were encountered: