[Serusers] fix_nated_sdp bug or ser.cfg error?? - sr-users

7 May 2004


      Hi all
I am trying ser+nathelper+rtpproxy
ser is downloaded form CVS on 2004/04/22
my environment is just like
nec-----------------Internet---------------ser+nathelper+rtpproxy---------------NAT-------------------jimmy
61.61.61.3                                        61.61.61.1               192.168.5.1          61.61.61.2           192.168.5.2
both client use kphone4.02 , Symmetric Signaling ,Symmetric Media
when jimmy call nec ,and after nec answer the call , kphone will crash...
I think it may be something wrong..
so i check the package...
the 200 OK with SDP after ser to jimmy is correct ,
Connection Information (c): IN IP4 61.61.61.1
but  the SDP of INVITE request after ser to nec 
the part of rtp will occur some incorrcet information
Connection Information (c): IN IP4 61.61.61.261.61.61.1
                                                        ^^^^^^^^^^^^^^^^^^  this is not correct
I don't know if this is a bug , or some thing wrong in my ser.cfg
can anyone tell me where is wrong in my ser.cfg ???
thanks
jimmy
ser.cfg==========================================================================
# ----------- global configuration parameters ------------------------
#debug=3         # debug level (cmd line: -dddddddddd)
#fork=yes
#log_stderror=no # (cmd line: -E)
#/* Uncomment these lines to enter debugging mode 
debug=4
#fork=no
log_stderror=yes
#*/
check_via=no # (cmd. line: -v)
dns=no           # (cmd. line: -r)
rev_dns=no      # (cmd. line: -R)
#port=5060
#children=4
fifo="/tmp/ser_fifo"
# ------------------ module loading ----------------------------------
loadmodule "/usr/local/lib/ser/modules/sl.so"
loadmodule "/usr/local/lib/ser/modules/tm.so"
loadmodule "/usr/local/lib/ser/modules/rr.so"
loadmodule "/usr/local/lib/ser/modules/maxfwd.so"
loadmodule "/usr/local/lib/ser/modules/usrloc.so"
loadmodule "/usr/local/lib/ser/modules/registrar.so"
#++++++++++    jimmy added      ++++++++++++++++++
loadmodule "/usr/local/lib/ser/modules/textops.so"
loadmodule "/usr/local/lib/ser/modules/nathelper.so"
#----------------------------------------------------
# ----------------- setting module-specific parameters ---------------
#++++++++++    jimmy added      ++++++++++++++++++
#we will you flag 6 to mark NATed contacts
modparam("registrar","nat_flag",6)
#Enable NAT pinging
modparam("nathelper","natping_interval",3)
#ping only contacts that are known to be behind NAT
modparam("nathelper","ping_nated_only",1)
#----------------------------------------------------
# -- usrloc params --
modparam("usrloc", "db_mode",   0)
# -- 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{
#++++++++++    jimmy added      ++++++++++++++++++
 if(nat_uac_test("3"))
 {
  if((method == "REGISTER") || !(search("^Record-Route:")))
  {
   log("LOG:Someone trying to register from private IP, rewriting\n");
fix_nated_contact();
   if(method == "INVITE")
   {
    fix_nated_sdp("3");
    force_rtp_proxy();
    t_on_reply("1");
   };
   force_rport();
   setflag(6);
  };
 };
#----------------------------------------------------
# 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;
  };
# native SIP destinations are handled using our USRLOC DB
  if (!lookup("location")) {
   sl_send_reply("404", "Not Found");
   break;
  };
 };
 # 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();
 };
}
route[1]
{
 if(uri=~"[@:](192.168.|10.|172.16)" && !search("^Route:"))
 {
  sl_send_reply("479","we don't forward to private IP address");
  break;
 };
 if(isflagset(6))
 {
  force_rtp_proxy();
  t_on_reply("1");
  append_hf("P-Behind-NAT: Yes\r\n");
 }
if(!t_relay())
 {
  sl_reply_error();
  break;
 }
}
onreply_route[1]
{
 if(status =~ "(183)|2[0-9][0-9]")
 {
  fix_nated_contact();
  force_rtp_proxy();
 };
}