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
[CRASH] v0.10 when on call and CGRateS Engine restarts #2764
Comments
Trial97
pushed a commit
to Trial97/cgrates
that referenced
this issue
Mar 23, 2021
Trial97
pushed a commit
to Trial97/cgrates
that referenced
this issue
Mar 23, 2021
Trial97
pushed a commit
to Trial97/cgrates
that referenced
this issue
Mar 23, 2021
Trial97
pushed a commit
to Trial97/cgrates
that referenced
this issue
Mar 23, 2021
Trial97
pushed a commit
to Trial97/cgrates
that referenced
this issue
Mar 23, 2021
danbogos
pushed a commit
that referenced
this issue
Mar 23, 2021
Any chance to get this into a released v0.10 version? |
We have pushed a new development package on v0.10. Hope that will do. DanB |
@danbogos I have just tested that. Its working great!!! thanks !!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear Team,
CGRateS v0.10
Crashes with
[signal SIGSEGV: segmentation violation code=0x1 addr=0x90 pc=0x1051177]
when there is an on going call and I manually restart CGRateS Engine and then I hangup the call.
This happens 3-4 seconds after the call hangup.
Logs:
cgrates.json --> here
Let me know if you need any further information on this case
Thank you in advance for your support
Vasilios Tzanoudakis
The text was updated successfully, but these errors were encountered: