Hello,
I am getting the folowing error on communication with one of our application servers:
tm:t_should_relay_response: pick_branch failed (lowest==-1) for code 404
This is in situation where I have two triggerings to the AS (orig and term) and term subscriber is not registered to OpenSER. OpenSER thus returns 404 not found which is then sent back to OpenSER to be forwarded to orig leg of the AS. I had the very same behavior with other AS in our lab and found out that it was because of tag added to To header in AS for the 404 response. So i removed the tag and the call worked fine. However with this AS it doesn't seem to work. Is there a way to hack pick_branch so that I see what are the existing branches and why it does not match any? Or is there any easier way to find out the reason?
Thanks a lot, Fero
--- reklama ----------------------------------------------------- Hľadáš DOM – BYT – POZEMOK – KANCELÁRIU ? http://www.reality.sk
On Thursday 24 July 2008, Fero Vlkolinsky wrote:
I am getting the folowing error on communication with one of our application servers:
tm:t_should_relay_response: pick_branch failed (lowest==-1) for code 404
This is in situation where I have two triggerings to the AS (orig and term) and term subscriber is not registered to OpenSER. OpenSER thus returns 404 not found which is then sent back to OpenSER to be forwarded to orig leg of the AS. I had the very same behavior with other AS in our lab and found out that it was because of tag added to To header in AS for the 404 response. So i removed the tag and the call worked fine. However with this AS it doesn't seem to work. Is there a way to hack pick_branch so that I see what are the existing branches and why it does not match any? Or is there any easier way to find out the reason?
Hi Fero,
you could activate the debugging, then you will get more informations from within t_should_relay_response and t_pick_branch. And you could also add off course more debugging to the code by yourself.
Cheers,
Henning