[Devel] [ openser-Bugs-1534036 ] Call does not failover in
REQUEST_ROUTE for empty IP
SourceForge.net
noreply at sourceforge.net
Thu Aug 10 11:22:45 CEST 2006
Bugs item #1534036, was opened at 2006-08-03 21:22
Message generated for change (Comment added) made by miconda
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1534036&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 devel
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Di-Shi Sun (di-shi)
>Assigned to: Daniel-Constantin Mierla (miconda)
Summary: Call does not failover in REQUEST_ROUTE for empty IP
Initial Comment:
An empty IP on the same network segment as the OpenSER
is configured as the first destination in the "route"
function. The call does not failover to the second
destination configured in the "failure_route[1]"
function. It sends 477 to the source device.
But if the empty IP is configured as the second
destination in the "failure_route[1]" (the first
destination configured in the "route" functon rejects
the call), the call will failover to the third
destination defined in "failure_route[2]" and
completes the call.
I attached my test configuration and log.
----------------------------------------------------------------------
>Comment By: Daniel-Constantin Mierla (miconda)
Date: 2006-08-10 12:22
Message:
Logged In: YES
user_id=1246013
This is not a bug, it is about the meaning of the
failure_route[]. This type of route is executed when a
negative reply is received from downstream. If the t_relay()
fails, then no failure_route[] will be executed, because not
request was sent, therefore no reply will be received.
You can handle errors of t_relay() with 'if' conditions:
if(t_relay()) {
... success
} else {
... failure
}
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1534036&group_id=139143
More information about the Devel
mailing list