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
Dialog: Core dump when using dlg_set_timeout #1011
Comments
The values in the variables have to be numbers, not strings. Try to convert first with {s.int}, like:
|
I did later - but we should not segfault for a bad config, right? |
Sure, that needs to be caught. I tried to suggest a solution for now. |
Thank you! I still can't find the proper dialog, but that's another problem. |
miconda
added a commit
that referenced
this issue
Mar 13, 2017
I pushed some commits with safety checks back to 4.4. If the issue is still there, reopen. |
lbalaceanu
pushed a commit
to lbalaceanu/kamailio
that referenced
this issue
Mar 16, 2017
lbalaceanu
pushed a commit
to lbalaceanu/kamailio
that referenced
this issue
Mar 16, 2017
- related to GH kamailio#1011
miconda
added a commit
that referenced
this issue
Jun 13, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
dlg_set_timeout("2419200", $var(entry), $var(id));
The both $var's contains strings. If I enclose them with "" there's no segfault, but the var's doesn't seem to be parsed by dlg_set_timeout either.
Doing this causes a seg fault when kamailio starts. Version 4.4.2
Will try to get a core dump, but not sure since this is a production system...
The text was updated successfully, but these errors were encountered: