-
Notifications
You must be signed in to change notification settings - Fork 581
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
1.11.3 crashes when using request context from the onreply_route #388
Comments
Hi @gergelypeli , please post the exact xlog line you have in the script . Additionally, in gdb frame 0, print "trans" . |
I just noticed that the context specification was stripped from my original report (because of the angle brackets? I'll try with HTML entities then). The xlog call was simply:
The print you requested:
|
do you do the xlog from the default onreply route (the one without name) ? |
Yes. I figured out that AVPs are only visible in "t_onreply_route"-armed "onreply_route"-s (which does not seem to be documented at tm's "onreply_avp_mode" param), but I expected PVs to work without any transactions set up. |
Indeed, we need a fix to prevent the crash, but that PV (with request context) will not work in the default reply route - that route has no transaction context, so no way to reach the SIP requests and get the RURI. |
I just tried using $(ru) in an xlog from the onreply_route (should work according to the Core Variables doc page), but got a crash:
Reproducible always. The version is:
The text was updated successfully, but these errors were encountered: