[Devel] [ openser-Bugs-1534126 ] Strange behaviour regarding sl_send_reply and failure_route

[SourceForge.net]

Bugs item #1534126, was opened at 2006-08-03 13:50
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1534126&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: ver 1.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: unspin (unspin)
Assigned to: Nobody/Anonymous (nobody)
Summary: Strange behaviour regarding sl_send_reply and failure_route

Initial Comment:
I'm encountering an issue using sl_send_reply in a
route referenced from route

failure_route snippet
---
    if ( t_check_status("486") )
    {
        route(15);
        drop();
    }
---

Inside which i call another route() block
---
route[15]
{
    sl_send_reply("404", "Well i tried, but they're
nowhere to be found");
}
---

After returning to the failure_route drop() is executed

What i'm seeing is that both the message i'm generating
with
sl_send_reply and the "486 Busy" are being sent on to
the client.  I was expecting the message created by
sl_send_reply to be sent and the original message to be
dropped


I've attached a really simple configuration that will
reproduce this issue.

This config is designed to handle incoming
registrations (so that you
can register a phone and then leave it off hook so that
it will respond
"486" to any incoming INVITE) and store the location
information in
memory. 
It will the handle incoming INVITE and execute a
lookup("location"); so
that the call may be routed to a registered user. 
A failure route is defined that looks for a status of
486, upon finding
this it will execute route(15) which simply calls
sl_send_reply and then
returns, at this point a drop() will be executed and
you will see both
the result of the sl_send_reply sent to the client AND
the "486 Busy".

This was found on an OpenSER 1.0 cvs checkout about 2
weeks ago

tavis

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1534126&group_id=139143