[Serusers] Multiple domains via a DB

Jan Janak jan at iptel.org
Mon Feb 20 17:58:03 CET 2006


Take a look at the domain module README. There is the function called
is_uri_host_local which will check the request-uri domain against a list of
domain names which is stored in database in domain table.

  Jan.

Nick Hoffman wrote:
> How do you setup a multi-domain SER using a database? I've seen examples 
> where you hard code into ser.cfg a regular expression for each domain. Is 
> there a call that can do something similar as in compare the URI with 
> returned values from the database?
> 
> I tried this:
>     if(is_from_local()) {
>         sl_send_reply("600", "is local");
>         break;
>         };
> but it didn't fire for existing or non-existing domains. Does anyone have 
> suggestions as to what should be done instead, or what needs to be fixed? 
> I've attached my ser.cfg in case it's of any help.
> 
> Thanks for your help,
> -- Nick
> e: nick.hoffman at altcall.com
> p: +61 7 5591 3588
> f: +61 7 5591 6588
> 
> If you receive this email by mistake, please notify us and do not make any 
> use of the email.  We do not waive any privilege, confidentiality or 
> copyright associated with it.
> 
> 
> ------------------------------------------------------------------------
> 
> #
> # simple quick-start config script
> #
> 
> # ----------- global configuration parameters ------------------------
> 
> #debug=3         # debug level (cmd line: -dddddddddd)
> #fork=yes
> #log_stderror=no# (cmd line: -E)
> 
> listen=10.0.100.12
> 
> /* Uncomment these lines to enter debugging mode 
> 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 ----------------------------------
> 
> # Uncomment this if you want to use SQL database
> #loadmodule "/usr/local/lib/ser/modules/mysql.so"
> loadmodule "/usr/lib/ser/modules/mysql.so"
> loadmodule "/usr/lib/ser/modules/domain.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/textops.so"
> loadmodule "/usr/lib/ser/modules/acc.so"
> 
> # Uncomment this if you want digest authentication
> # mysql.so must be loaded !
> #loadmodule "/usr/local/lib/ser/modules/auth.so"
> #loadmodule "/usr/local/lib/ser/modules/auth_db.so"
> 
> # ----------------- setting module-specific parameters ---------------
> 
> # -- usrloc params --
> modparam("usrloc", "db_mode", 2)
> modparam("usrloc", "db_url", "mysql://ser:hello@localhost/ser")
> modparam("usrloc", "use_domain", 1)
> 
> 
> # 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)
> 
> # -- domain params --
> modparam("domain", "db_url", "mysql://ser:hello@localhost/ser")
> modparam("domain", "db_mode", 1)
> modparam("domain", "domain_table", "domain")
> modparam("domain", "domain_col", "domain")
> 
> 
> # -- registrar params --
> modparam("registrar", "use_domain", 1)
> 
> # -- acc params --
> # set the reporting log level
> modparam("acc", "log_level", 1)
> # number of flag, which will be used for accounting; if a message is
> # labeled with this flag, its completion status will be reported
> modparam("acc", "log_flag", 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(uri==is_from_local()) {
> 		sl_send_reply("600", "is local");
> 		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 (is_from_local()) {
>    	    if (method=="REGISTER") { 
>   
>    	    # Uncomment this if you want to use digest authentication 
> 	    #if (!www_authorize("proxy.example.org", "subscriber")) { 
> 	    #    www_challenge("proxy.example.org", "0"); 
> 	    #    break; 
> 	    #    }; 
> 	    #
> 	    #save("location"); 
> 	        break; 
> 	        }; 
>   
> 	    lookup("aliases"); 
>   
>    	    # 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(); 
>          }; 
>   
>  }
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers




More information about the sr-users mailing list