Authentication is working fine now, ngrep is spitting out way too much, to the point where it is useless. All I really want to do at this point is have a call going to 9742146 to be forwarded to the 5350. This is not happening, i am doing debug all on the 5350 and nothing is coming accross from the Ser server. AJ Grinnell Network Operations Technician CRT/ Arialink Broadband 1223 Turner Street, Suite A Lansing, MI 48906 517.346.5041 517.492.1321 direct -----Original Message----- From: Vitaly Nikolaev [mailto:vitaly@switchgate.com] Sent: Tuesday, June 15, 2004 1:53 PM To: AJ Grinnell; serusers(a)lists.iptel.org Subject: RE: [Serusers] No outgoing calls Hello forward(uri:host, uri:port); - you do not need it... also commenting auth stuff could help for start. Later u can enable it. And use ngrep to see what is going on in the network -----Original Message----- From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of AJ Grinnell Sent: Tuesday, June 15, 2004 1:39 PM To: serusers(a)lists.iptel.org Subject: RE: [Serusers] No outgoing calls Before i get too far ahead of my self here, will someone just tell me if this config will work or not. # ----------- global configuration parameters ------------------------ debug=4 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=yes # (cmd line: -E) listen=216.157.192.117 listen=127.0.0.1 alias=216.157.192.117 alias=x.x.x.x check_via=yes # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=4 fifo="/tmp/ser_fifo" sip_warning=yes syn_branch=no server_signature=yes reply_to_via=no # ------------------ module loading ---------------------------------- # Uncomment this if you want to use SQL database loadmodule "/usr/lib/ser/modules/mysql.so" loadmodule "/etc/lib/ser/modules/sl.so" loadmodule "/etc/lib/ser/modules/tm.so" loadmodule "/etc/lib/ser/modules/rr.so" loadmodule "/etc/lib/ser/modules/maxfwd.so" loadmodule "/etc/lib/ser/modules/usrloc.so" loadmodule "/etc/lib/ser/modules/registrar.so" loadmodule "/etc/lib/ser/modules/auth.so" loadmodule "/etc/lib/ser/modules/auth_db.so" # ----------------- setting module-specific parameters --------------- # -- usrloc params -- #modparam("usrloc", "db_mode", 0) modparam("usrloc", "db_mode", 2) modparam("auth_db", "db_url", "sql://ser:heslo@localhost/ser") # -- auth params -- modparam("auth_db", "db_url", "sql://ser:heslo@localhost/ser") modparam("auth_db", "calculate_ha1", yes) 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") { # Uncomment this if you want to use digest authentication if (!www_authorize("asterisk.crt.net", "subscriber")) { www_challenge("asterisk.crt.net", "0"); break; }; save("location"); break; }; if (uri=~"^sip:9742146@.*") { # attempt handoff to PSTN. log( "Forwarding to PSTN\n" ); rewritehost("216.157.199.1:5060"); forward(uri:host, uri:port); }; }; # 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(); }; } AJ Grinnell Network Operations Technician CRT/ Arialink Broadband 1223 Turner Street, Suite A Lansing, MI 48906 517.346.5041 517.492.1321 direct -----Original Message----- From: Vitaly Nikolaev [mailto:vitaly@switchgate.com] Sent: Tuesday, June 15, 2004 1:17 PM To: AJ Grinnell Cc: serusers(a)lists.iptel.org Subject: RE: [Serusers] No outgoing calls Yea... Find program called ngrep (should go with SER... find it there) Compile it and execute "ngrep -q SIP" Then call and watch... :) That is tool number one for me -----Original Message----- From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of AJ Grinnell Sent: Tuesday, June 15, 2004 1:12 PM To: serusers(a)lists.iptel.org Subject: RE: [Serusers] No outgoing calls I am beginning to think that maybe Ser is working, but not getting the calls to the Cisco 5350. Is there anything else I need to do to get this working? AJ Grinnell Network Operations Technician CRT/ Arialink Broadband 1223 Turner Street, Suite A Lansing, MI 48906 517.346.5041 517.492.1321 direct -----Original Message----- From: Steve Blair [mailto:blairs@isc.upenn.edu] Sent: Tuesday, June 15, 2004 12:47 PM To: AJ Grinnell Subject: Re: [Serusers] No outgoing calls Oh, ok. I assumed that was the case but it wasn't clear from the configuration data. _Steve AJ Grinnell wrote: also piecing now. being Asterisk by up going able of ------------------------ ---------------------------------- --------------- ------------------- "subscriber")) DB support(a)arialink.com -- ISC Network Engineering The University of Pennsylvania 3401 Walnut Street, Suite 221A Philadelphia, PA 19104 voice: 215-573-8396 215-746-7903 fax: 215-898-9348 sip:blairs@upenn.edu -- This message has been scanned by Arialink for dangerous content and is believed to be clean. For more information please email support(a)arialink.com _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers -- This message has been scanned by Arialink for dangerous content and is believed to be clean. For more information please email support(a)arialink.com _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers -- This message has been scanned by Arialink for dangerous content and is believed to be clean. For more information please email support(a)arialink.com