[Serusers] Re-routing to same device in failure_route

[Gustavo García]

Hi,

 

It’s possible that the Xten softphone detects that the second INVITE is part
of a cleared session (the first INVITE rejected with 400 error), and
discards it
.

 

G.

 

  _____  

De: serusers-bounces at iptel.org [mailto:serusers-bounces at lists.iptel.org] En nombre
de Karun Chemudugunta
Enviado el: martes, 07 de junio de 2005 18:43
Para: serusers at lists.iptel.org
CC: serdev at lists.iptel.org
Asunto: [Serusers] Re-routing to same device in failure_route

 

Hi Group, 

     Cisco 5300 -----> SER ----> Xten softphone-A ----> Failed call with
error code >400 -------> try to route to Xten softphone A(same as previous)

           I am trying to route calls to softphones in such way that, if
call failed by some reason (>400), trying to route second time to the same
soft phone using append_brach() and t_relay() like below. But, soft phone is
unable process INVITE message for some reason.  But, if I forward failed
call different soft phone,  call was successful.

 

Am I doing any thing wrong in config ??? 

Thanks for your help in advance. 

Regards, 
Karun 

############################################################################
############## 
# 
# $Id: ser.cfg,v 1.21.4.1 2003/11/10 15:35:15 andrei Exp $ 
# 
# simple quick-start config script 
# 

# ----------- global configuration parameters ------------------------ 

#debug=9         # debug level (cmd line: -dddddddddd) 
#fork=yes 
#log_stderror=no        # (cmd line: -E) 

/* Uncomment these lines to enter debugging mode 
debug=7 
fork=no 
log_stderror=yes 
*/ 

check_via=no    # (cmd. line: -v) 
#dns=no           # (cmd. line: -r) 
#rev_dns=no      # (cmd. line: -R) 

dns=no           # (cmd. line: -r) 
rev_dns=no      # (cmd. line: -R) 
#port=5060 
#children=4 
fifo="/tmp/ser_fifo" 

#alias=voip.cafe.bevocal.com 
#alias=66.77.14.238 
alias=209.233.189.177 
alias=voice.engca.bevocal.com 

 

# ------------------ module loading ---------------------------------- 

# Uncomment this if you want to use SQL database 
#loadmodule "/usr/lib/ser/modules/mysql.so" 

loadmodule "/usr/lib/ser/modules/sl.so" 
loadmodule "/usr/lib/ser/modules/tm.so" 
loadmodule "/usr/lib/ser/modules/rr.so" 
loadmodule "/usr/lib/ser/modules/maxfwd.so" 
loadmodule "/usr/lib/ser/modules/usrloc.so" 
loadmodule "/usr/lib/ser/modules/registrar.so" 
loadmodule "/usr/lib/ser/modules/exec.so" 
loadmodule "/usr/lib/ser/modules/textops.so" 
#loadmodule "/usr/lib/ser/modules/acc.so" 

#modparam("acc", "log_level", 2) 
#modparam("acc", "log_flag", 1) 
#modparam("acc", "report_cancels", 1) 
#modparam("acc", "failed_transactions", 1) 

 

# Uncomment this if you want digest authentication 
# mysql.so must be loaded ! 
#loadmodule "/usr/lib/ser/modules/auth.so" 
#loadmodule "/usr/lib/ser/modules/auth_db.so" 

# ----------------- setting module-specific parameters --------------- 

# -- usrloc params -- 

modparam("usrloc", "db_mode",   0) 

# Uncomment this if you want to use SQL database 
# for persistent storage and comment the previous line 
#modparam("usrloc", "db_mode", 2) 

# -- auth params -- 
# Uncomment if you are using auth module 
# 
#modparam("auth_db", "calculate_ha1", yes) 
# 
# If you set "calculate_ha1" parameter to yes (which true in this config), 
# uncomment also the following parameter) 
# 
#modparam("auth_db", "password_column", "password") 
# -- rr params -- 
# add value to ;lr param to make some broken UAs happy 
modparam("rr", "enable_full_lr", 1) 

# -------------------------  request routing logic ------------------- 

# main routing logic 
route{ 

        # initial sanity checks -- messages with 
        # max_forwards==0, or excessively long requests 
        if (!mf_process_maxfwd_header("10")) 
        { 
                sl_send_reply("483","Too Many Hops"); 
                break; 
        }; 
        if ( msg:len > max_len ) { 
                sl_send_reply("513", "Message too big"); 
                break; 
        }; 

        # we record-route all messages -- to make sure that 
        # subsequent messages will go through our proxy; that's 
        # particularly good if upstream and downstream entities 
        # use different transport protocol 
 #       record_route(); 
        # loose-route processing 
        if (loose_route()) { 
                t_relay(); 
                break; 
        }; 
        # if the request is for other domain use UsrLoc 
        # (in case, it does not work, use the following command 
        # with proper names and addresses in it) 
        if (uri==myself) 
        { 
                if (method=="REGISTER") 
                { 
                        save("location"); 
                        break; 
                }; 

                if(method=="INVITE") 
                { 
                     log(1,"about lookup in route zero"); 
                     if (!lookup("location")) { 
                         log(1,"lookup failed :SIP request from config"); 
                 sl_send_reply("404", "Not Found"); 
                       break; 
                     }; 
                    t_on_failure("5"); 
                 }; 
        }; 

       # forward to current uri now; use stateful forwarding; that 
        # works reliably even if we forward from TCP to UDP 
        if (!t_relay()) { 
                sl_reply_error(); 
        }; 

} 

failure_route[5] { 
    log(1,"Inside failure_route five"); 
    revert_uri(); 
     append_branch(); 
     if (!lookup("location")) { 
               log(1,"lookup failed :SIP request from config"); 
               t_reply("404", "Not Found"); 
                break; 
           }; 
       if (!t_relay()) { 
               sl_reply_error(); 
      }; 

} 

############################################################################
########## 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20050608/49a661e7/attachment.htm>