Ok, so if I have asterisk register with ser using the register = > command that would be giving asterisk an extension. This is where I dont understand - if I want to reach the asterisk box then from a phone connected to ser I would have to dial that extension I setup with the register command...
here is my current ser.cfg / Please point out anything I should fix. what I'm basically trying to do is have around 1,000 users connected to ser but have phone queues voicemail ect done by asterisk - sort of a call center situation.
START ser.cfg
# # $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=3 # 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) port=5060 #children=4 fifo="/tmp/ser_fifo" listen=my sip domain name # ------------------ module loading ----------------------------------
# Uncomment this if you want to use SQL database loadmodule "/usr/local/lib/ser/modules/mysql.so"
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"
# 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", 0)
# Uncomment this if you want to use SQL database # for persistent storage and comment the previous line modparam("usrloc", "db_mode", 2) modparam("usrloc", "db_url", "mysql://user:pass@localhost/ser")
# -- 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") modparam("auth_db", "db_url", "mysql://user:pass@localhost/ser")
# -- 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") {
# Uncomment this if you want to use digest authentication if (!www_authorize("digicen.com", "subscriber")) { www_challenge("digicen.com", "0"); break; };
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(); };
#supposed asterisk forwarding?? if (uri=~"^sip:0[0-9]*@*") { forward( 10.0.18.3, 5060 ); break; };
}
On Sat, 12 Feb 2005 01:09:31 +0100, Jan Janak jan@iptel.org wrote:
You can tell ser to use domain using modparam("usrloc", "use_domain", 1) modparam("registrar", "use_domain", 1)
but that will probably not fix your problem. The fact that you get 404 means that the user the caller is trying to call is not registered. See what username does the INVITE have in the Request-URI and then see if such a username is in the location table.
Jan.
On 11-02 18:48, Patrick Baker wrote:
can anyone take a look at this config file and maybe tell me whats wrong with it or point me in the right direction http://pastebin.ca/5664 / ser is putting the location data into the db but its not putting in the domain - when I try to dial i get a 404
Thanks,
Patrick
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers