-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
switch session state to stopped after receiving a DIAMETER error #200
Conversation
ee27004
to
286a333
Compare
286a333
to
576492f
Compare
src/ergw_aaa_rf.erl
Outdated
@@ -292,7 +292,7 @@ handle_aca(['ACA' | #{'Result-Code' := ?'DIAMETER_BASE_RESULT-CODE_SUCCESS'} = A | |||
{ok, Session, Events, State}; | |||
handle_aca([Answer | #{'Result-Code' := Code}], Session, Events, _Opts, State) | |||
when Answer =:= 'ACA'; Answer =:= 'answer-message' -> | |||
{{fail, Code}, Session, Events, State}; | |||
{{fail, Code}, Session, Events, State#state{state = stopped}}; | |||
handle_aca({error, _} = Result, Session, Events, _Opts, State) -> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is different for Rf?
Nasraq set state to stopped for handle_aca({error, _}
Rf does not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
valid point. I'll rework the change to apply the stop logic only on Requests/Responses that are authorisation related.
Error in Accounting requests (Rf and NASREQ ACR/ACA should IMHO no lead to stop of the session).
This ensures that session do not send termination requests after the session was stopped by a previous error.
576492f
to
2679944
Compare
No CCR-T is sent on Gy dialogues failing upon init. |
This ensures that session do not send termination requests after the session
was stopped by a previous error.