3 Nov
2020
3 Nov
'20
4:33 a.m.
kamailio 5.5.0-dev3
I'm unsure if this is expected behavior, so thought I would ask...
When using http_async_query("URI", "ROUTENAME")
request_route {
route(AUTH);
# this does not get executed below route(AUTH)
xinfo("[$ci][$rm] we hit this line");
}
route[AUTH] {
t_newtran();
http_async_query("URI", "ROUTENAME");
}
route[ROUTENAME] {
# do stuff here to check authentication and return
if(auth + registration) {
append_hf("Path....");
msg_apply_changes(); # this fails and errors out about incorrect
route
# ^ invalid usage - not in request route or a reply
save("location");
}
if(auth + invite) {
# route to pstn
}
}
Expected behavior: to be able to obtain some processing / information
gathering about authentication with the call and additional information
possibly and return to normal routing. As-is now I've to move the actions
all into ROUTENAME for kamailio to continue processing, it does not go back
to request_route { }.
# this does not get executed below route(AUTH)
Is this expected behavior, or am I missing something?
If I do catch route(AUTH) with a hash table and prevent its execution after
first run, the avp's from the transaction created are not available in
request_route that were set in ROUTENAME.