Menu

#95 Call does not failover in REQUEST_ROUTE for empty IP

ver devel
closed-invalid
core (125)
5
2006-08-10
2006-08-03
Di-Shi Sun
No

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.

Discussion

  • Di-Shi Sun

    Di-Shi Sun - 2006-08-03

    Test configuration and log

     
  • Daniel-Constantin Mierla

    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
    }

     
  • Daniel-Constantin Mierla

    • milestone: --> ver devel
    • assigned_to: nobody --> miconda
    • status: open --> closed-invalid
     

Log in to post a comment.