sr-users August 2005

sr-users@lists.kamailio.org

220 participants
558 discussions

by Ozan Blotter

Dear List, Assume that there are two different service providers and one SER in middle of them. A client needs to use/connect SER but also he/she has accounts in both providers and both supplied him/her DDIs (landline phone). Now again assume that client registers both of phones into SER. But still he/she wants to receive calls from both providers, is it possible to receive calls from different providers to that client and/or how to i setup ? In current SER.CFG below, i only setup one prefix which is "0", but i can change it to any and/or add many prefixes, ex: 0049 (germany), 001 (usa), 0044 (uk), 0090 (turkey) to Provider 1 and 0033 (france), 0038 (italy) to Provider 2 and so on. debug=3 fork=yes log_stderror=no listen=212.XXX.104.XXX # This is SER's Public IP port=5060 children=4 alias=212.XXX.104.XXX # This is SER's Public IP dns=no rev_dns=no fifo="/tmp/openser_fifo" fifo_db_url="mysql://openser:openserrw@localhost/openser" loadmodule "/usr/local/lib/openser/modules/mysql.so" loadmodule "/usr/local/lib/openser/modules/sl.so" loadmodule "/usr/local/lib/openser/modules/tm.so" loadmodule "/usr/local/lib/openser/modules/rr.so" loadmodule "/usr/local/lib/openser/modules/maxfwd.so" loadmodule "/usr/local/lib/openser/modules/usrloc.so" loadmodule "/usr/local/lib/openser/modules/registrar.so" loadmodule "/usr/local/lib/openser/modules/auth.so" loadmodule "/usr/local/lib/openser/modules/auth_db.so" loadmodule "/usr/local/lib/openser/modules/uri.so" loadmodule "/usr/local/lib/openser/modules/uri_db.so" loadmodule "/usr/local/lib/openser/modules/mediaproxy.so" loadmodule "/usr/local/lib/openser/modules/nathelper.so" loadmodule "/usr/local/lib/openser/modules/textops.so" loadmodule "/usr/local/lib/openser/modules/domain.so" loadmodule "/usr/local/lib/openser/modules/acc.so" modparam("auth_db", "calculate_ha1", 1) modparam("auth_db", "password_column", "password") modparam("auth_db", "use_domain", 1) modparam("domain", "db_mode", 1) modparam("nathelper", "rtpproxy_disable", 1) modparam("nathelper", "natping_interval", 180) modparam("mediaproxy","natping_interval", 30) modparam("mediaproxy","mediaproxy_socket", "/var/run/mediaproxy.sock") modparam("mediaproxy","sip_asymmetrics","/usr/local/etc/openser/sip-asymmetric-clients") modparam("mediaproxy","rtp_asymmetrics","/usr/local/etc/openser/rtp-asymmetric-clients") modparam("usrloc", "db_mode", 2) modparam("usrloc", "use_domain", 1) modparam("registrar", "default_expires", 60) modparam("registrar", "min_expires", 30) modparam("registrar", "nat_flag", 6) modparam("registrar", "use_domain", 1) modparam("rr", "enable_full_lr", 1) modparam("acc", "db_url", "mysql://openser:openserrw@localhost/openser") modparam("acc", "failed_transactions", 1) modparam("acc", "log_level", 1) modparam("acc", "log_flag", 1) modparam("acc", "db_flag", 1) route { # ----------------------------------------------------------------- # Sanity Check Section # ----------------------------------------------------------------- if (!mf_process_maxfwd_header("10")) { sl_send_reply("483", "Too Many Hops"); break; }; if (msg:len > max_len) { sl_send_reply("513", "Message Overflow"); break; }; # ----------------------------------------------------------------- # Record Route Section and Acc section # ----------------------------------------------------------------- if (method=="INVITE" && client_nat_test("3")) { record_route_preset("212.XXX.104.XXX:5060;nat=yes"); # This is SER's Public IP } else if (method!="REGISTER") { if!(uri=~"^sip:833[0-9]*@") { # I do not want to make accounting if clients' prefix is beginning with 833 record_route(); setflag(1); } }; # ----------------------------------------------------------------- # Call Tear Down Section # ----------------------------------------------------------------- if (method=="BYE" || method=="CANCEL") { end_media_session(); }; # ----------------------------------------------------------------- # Loose Route Section # ----------------------------------------------------------------- if (loose_route()) { if (has_totag() && (method=="INVITE" || method=="ACK")) { if (client_nat_test("3") || search("^Route:.*;nat=yes")) { setflag(6); use_media_proxy(); }; }; route(1); break; }; # ----------------------------------------------------------------- # Call Type Processing Section # ----------------------------------------------------------------- if (uri!=myself) { route(1); break; }; if (uri==myself) { if (method=="CANCEL") { route(3); break; } else if (method=="INVITE") { route(3); break; } else if (method=="REGISTER") { route(2); break; }; lookup("aliases"); if (uri!=myself) { route(1); break; }; if (!lookup("location")) { sl_send_reply("404", "User Not Found"); break; }; }; route(1); } route[1] { # ----------------------------------------------------------------- # Default Message Handler # ----------------------------------------------------------------- t_on_reply("1"); if (!t_relay()) { if (method=="INVITE" || method=="ACK") { end_media_session(); }; sl_reply_error(); }; } route[2] { # ----------------------------------------------------------------- # REGISTER Message Handler # ---------------------------------------------------------------- if (!search("^Contact:\ +\*") && client_nat_test("7")) { setflag(6); fix_nated_register(); force_rport(); }; sl_send_reply("100", "Trying"); if (!www_authorize("","subscriber")) { www_challenge("","0"); break; }; if (!check_to()) { sl_send_reply("401", "Unauthorized"); break; }; consume_credentials(); if (!save("location")) { sl_reply_error(); }; } route[3] { # ----------------------------------------------------------------- # CANCEL and INVITE Message Handler # ----------------------------------------------------------------- if (client_nat_test("3")) { setflag(7); force_rport(); fix_nated_contact(); }; lookup("aliases"); if (uri!=myself) { route(1); break; }; if (uri=~"^sip:0[0-9]*@*") { # If calling number is beginning with prefix 0, route it to PSTN rewritehost("195.XXX.122.XXX"); # This is PSTN Gateway's Public IP route(1); break; }; if (!lookup("location")) { sl_send_reply("404", "User Not Found"); break; }; if (method=="CANCEL") { route(1); break; }; if (!proxy_authorize("","subscriber")) { proxy_challenge("","0"); break; } else if (!check_from()) { sl_send_reply("403", "Use From=ID"); break; }; consume_credentials(); if (isflagset(6) || isflagset(7)) { use_media_proxy(); }; route(1); } onreply_route[1] { if ((isflagset(6) || isflagset(7)) && (status=~"(180)|(183)|2[0-9][0-9]")) { if (!search("^Content-Length:\ +0")) { use_media_proxy(); }; }; if (client_nat_test("1")) { fix_nated_contact(); }; }

18 years, 8 months

[Serusers] clarification about authentication

by Iqbal

Hi www_authorize , will this always fail, ? because it seems to and then a www.challenge is sent. In www.challenge, is it okay to leave the realm blank, as I have done, or is it better practice to have the same realm as that in www_authorise("", "1"); check_to should only be run if auth is correct above , is that correct? Why run check_to at all, ? and then u have proxy_auth and proxy_challenge, and is_from_local and is_uri_local, surely all these dont need to be used as checks in INVITE or do they. Iqbal

18 years, 8 months

[Serusers] Bye messages not logged

by Marc Khayat

Hi all, I upgraded my system from ser-0.8.14 to ser-0.9.3, and updated my ser.cfg. However, with the new thing, I'm getting INVITE and ACK messages, but no the BYE nor the REGISTER messages. I made no changes to the config file, only added the accounting requirements. But is the below stateful? Here's my ser.cfg: loadmodule "/usr/local/lib/ser/modules/acc.so" modparam("acc", "log_flag", 1 ) modparam("acc", "log_fmt", "miocfst") modparam("acc", "failed_transactions", 1) modparam("acc", "log_missed_flag", 2) modparam("acc", "report_cancels", 1) modparam("acc", "db_url", "mysql://ser:heslo@localhost/ser") modparam("acc", "db_flag", 5) modparam("acc", "db_missed_flag", 6) # 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 >= 2048 ) { 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 if (!method=="REGISTER") record_route(); # subsequent messages within a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); break; }; setflag(5); setflag(6); if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); route(1); 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=="INVITE") { if (uri=~"^sip:9") { t_relay_to_udp("50.65.11.23", "5060"); break; }; }; if (method=="REGISTER") { # Uncomment this if you want to use digest authentication # if (!www_authorize("mydomain.net", "subscriber")) { # www_challenge("mydomain.net", "0"); # break; # }; save("location"); break; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); break; }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; append_hf("P-hint: usrloc applied\r\n"); route(1); } route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; }

18 years, 8 months

Re: [Serusers] NAT example

by Kamran Ahmad

Thanks for reply [root@SIP ~]# ps -A | grep ser 131 ? 00:00:00 kseriod when i try to use asterisk on same port it is working. means port is free. it tried to change port from5060 to 5066. i have used killall ser before starting ser i tried to put in log into route2 but request is not reaching route2 route[2] { xlog("L_ERR","inside route2"); --- Samuel Osorio Calvo <samuel.osorio(a)nl.thalesgroup.com> wrote: > Don't worry, > These messages comes from the startup process, when > SER tries to get the PTR DNS records of the IP > addresses present in the config file. These pointers > map IP addresses to domain names, instead of the > "standard" domain->IP mapping provided by the A|AAA > DNS records. > > Probably your SER instance is running, have you > tried ps?? > > Enjoy! > > Samuel. > > > Unclassified. > >>> Kamran Ahmad <p_kami(a)yahoo.com> 08/30/05 10:35AM > >>> > i tried this > > ftp://siprouter.onsip.org/pub/gettingstarted/configs/nat-rtpproxy.3.05.cfg > > > but it is not working > > /var/log/messages > Aug 30 11:12:42 SIP ser: WARNING: fix_socket_list: > could not rev. resolve ip > Aug 30 11:12:42 SIP ser: WARNING: fix_socket_list: > could not rev. resolve ip > > > --- "Greger V. Teigre" <greger(a)teigre.com> wrote: > > > Try to Getting Started document from > > http://onsip.org/ You will find both a > > working config, as well as detailed explanation of > > the theory and actual > > commands. > > g-) > > > > Kamran Ahmad wrote: > > > Hello > > > > > > i am following this link for ser-0.9.3 but Nated > > > Clients > > > are not working. Can any one please tell > > me > > > what is the problem in my configuration. > > > > > > > > > http://www.voip-info.org/tiki-index.php?page=SER+nat+support > > > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

18 years, 8 months

[Serusers] Different Path for Request and Reply

by Andreas Granig

Hi, Let's say there are two SER servers A and B, a UAC and a UAS. If a request from UAC to UAS is routed via A and right after that A fails and B takes over, which impacts does it have if 1xx/200 replies from UAS to UAC are routed via B? The replies could theoretically be routed correctly because the next hop is available in the Via header. But since there is no transaction stored in SER for this, does this work? And what about accounting? What other functionality would be affected? Andy

18 years, 8 months

[Serusers] Radius Server sending reply to another machine!!!

by Ashutosh Kumar

Hi, I am facing a strange bewildering problem out here. Earlier I was running ser -0.9 on machine a.b.c.116. Now we shifted it to a.b.c.113 for testing for radius testing purposes. But in the radius packet dump, it is showing as the radius packet still originating from a.b.c.116 machine, despite the fact, my new revised ser.cfg doesn't contain any listen address or alias for .116 box. Also, the /etc/hosts doesn't mention .116 address. Also, it is not the case that .116 and .113 are IPs homes on same machine. My ser.cfg code for radius authorization is as follows. ... ..... if (!radius_www_authorize("")) { # if (!www_authorize("","subscriber")) { www_challenge("","0"); break; }; ... ..... In the DB also, there is no table . The Domains table has no records. But still SER is usng .116 address to send radius packets from. Here is the radius packet dump. [root@sip radiusclient]# tcpdump -i eth1 -s 1500 -w - udp | raddump -vvvvvvvvvvvvvvvvvvvvvsn tcpdump: listening on eth1 Looks like a(n) libpcap/tcpdump packet trace 17:45:13.051205 radius a.b.c.113:50912 > p.q.r.s:1812 Access-Request 180 User-Name = test(a)a.b.c.112 Ascend-PW-Warntime = 168195173 Ascend-PW-Warntime = 17774137 Ascend-PW-Warntime = 36320307 Ascend-PW-Warntime = 68383593 Ascend-PW-Warntime = 51008069 Ascend-Menu-Item = 75dd216d3efa9bfb9c2d7e013d54f7bb Service-Type = 15 (unknown) Ascend-PW-Lifetime = 1952805748 NAS-IP-Address = a.b.c.116 NAS-Port = 5060 (Is there any table /file in ser other than ser.cfg or mysql://ser that contains the domain information that might have been lying there unchanged since machine migration?) Also, why is SER using incorrect SER dictionary NAS client (Ascend)( shouldn't it have been Cisco or sometinhg like that). I have included the dictionary.ser included in ser-0.9 source in the radiusclient conf file. Help me, its driving me crazy. Regards, Ashutosh Kumar

18 years, 8 months

[Serusers] "Makefile.rules:80: action.d: No such file or directory" Errors

by Jaroslaw Gawron

Hello, I try to install ser-0.9.3 from source file on Mandriva 2005 limited edition and I get the following errors : Makefile.rules:80: action.d: No such file or directory Makefile.rules:80: crc.d: No such file or directory Makefile.rules:80: daemonize.d: No such file or directory Makefile.rules:80: data_lump.d: No such file or directory Makefile.rules:80: data_lump_rpl.d: No such file or directory Makefile.rules:80: dprint.d: No such file or directory Makefile.rules:80: dset.d: No such file or directory Makefile.rules:80: error.d: No such file or directory Makefile.rules:80: fifo_server.d: No such file or directory Makefile.rules:80: flags.d: No such file or directory Makefile.rules:80: forward.d: No such file or directory Makefile.rules:80: hash_func.d: No such file or directory Makefile.rules:80: ip_addr.d: No such file or directory Makefile.rules:80: main.d: No such file or directory Makefile.rules:80: md5.d: No such file or directory Makefile.rules:80: md5utils.d: No such file or directory Makefile.rules:80: modparam.d: No such file or directory Makefile.rules:80: msg_translator.d: No such file or directory Makefile.rules:80: pass_fd.d: No such file or directory Makefile.rules:80: proxy.d: No such file or directory Makefile.rules:80: qvalue.d: No such file or directory Makefile.rules:80: re.d: No such file or directory Makefile.rules:80: receive.d: No such file or directory Makefile.rules:80: resolve.d: No such file or directory Makefile.rules:80: route.d: No such file or directory Makefile.rules:80: route_struct.d: No such file or directory Makefile.rules:80: script_cb.d: No such file or directory Makefile.rules:80: socket_info.d: No such file or directory Makefile.rules:80: sr_module.d: No such file or directory Makefile.rules:80: stats.d: No such file or directory Makefile.rules:80: tcp_main.d: No such file or directory Makefile.rules:80: tcp_read.d: No such file or directory Makefile.rules:80: timer.d: No such file or directory Makefile.rules:80: tsend.d: No such file or directory Makefile.rules:80: udp_server.d: No such file or directory Makefile.rules:80: unixsock_server.d: No such file or directory Makefile.rules:80: usr_avp.d: No such file or directory Makefile.rules:80: mem/f_malloc.d: No such file or directory Makefile.rules:80: mem/mem.d: No such file or directory Makefile.rules:80: mem/memtest.d: No such file or directory Makefile.rules:80: mem/q_malloc.d: No such file or directory Makefile.rules:80: mem/shm_mem.d: No such file or directory Makefile.rules:80: mem/vq_malloc.d: No such file or directory Makefile.rules:80: parser/hf.d: No such file or directory Makefile.rules:80: parser/msg_parser.d: No such file or directory Makefile.rules:80: parser/parse_allow.d: No such file or directory Makefile.rules:80: parser/parse_content.d: No such file or directory Makefile.rules:80: parser/parse_cseq.d: No such file or directory Makefile.rules:80: parser/parse_disposition.d: No such file or directory Makefile.rules:80: parser/parse_diversion.d: No such file or directory Makefile.rules:80: parser/parse_event.d: No such file or directory Makefile.rules:80: parser/parse_expires.d: No such file or directory Makefile.rules:80: parser/parse_fline.d: No such file or directory Makefile.rules:80: parser/parse_from.d: No such file or directory Makefile.rules:80: parser/parse_hname2.d: No such file or directory Makefile.rules:80: parser/parse_hostport.d: No such file or directory Makefile.rules:80: parser/parse_methods.d: No such file or directory Makefile.rules:80: parser/parse_nameaddr.d: No such file or directory Makefile.rules:80: parser/parse_param.d: No such file or directory Makefile.rules:80: parser/parser_f.d: No such file or directory Makefile.rules:80: parser/parse_rpid.d: No such file or directory Makefile.rules:80: parser/parse_rr.d: No such file or directory Makefile.rules:80: parser/parse_sipifmatch.d: No such file or directory Makefile.rules:80: parser/parse_to.d: No such file or directory Makefile.rules:80: parser/parse_uri.d: No such file or directory Makefile.rules:80: parser/parse_via.d: No such file or directory Makefile.rules:80: parser/digest/digest.d: No such file or directory Makefile.rules:80: parser/digest/digest_parser.d: No such file or directory Makefile.rules:80: parser/digest/param_parser.d: No such file or directory Makefile.rules:80: parser/contact/contact.d: No such file or directory Makefile.rules:80: parser/contact/parse_contact.d: No such file or directory Makefile.rules:80: db/db.d: No such file or directory Makefile.rules:80: db/db_fifo.d: No such file or directory Makefile.rules:80: lex.yy.d: No such file or directory Does anyone know how to fix this problem ? Any help will be great ! Best regards, Jarosław Gawron

18 years, 8 months

Re: [Serusers] NAT example

by Samuel Osorio Calvo

Don't worry, These messages comes from the startup process, when SER tries to get the PTR DNS records of the IP addresses present in the config file. These pointers map IP addresses to domain names, instead of the "standard" domain->IP mapping provided by the A|AAA DNS records. Probably your SER instance is running, have you tried ps?? Enjoy! Samuel. Unclassified. >>> Kamran Ahmad <p_kami(a)yahoo.com> 08/30/05 10:35AM >>> i tried this ftp://siprouter.onsip.org/pub/gettingstarted/configs/nat-rtpproxy.3.05.cfg but it is not working /var/log/messages Aug 30 11:12:42 SIP ser: WARNING: fix_socket_list: could not rev. resolve ip Aug 30 11:12:42 SIP ser: WARNING: fix_socket_list: could not rev. resolve ip --- "Greger V. Teigre" <greger(a)teigre.com> wrote: > Try to Getting Started document from > http://onsip.org/ You will find both a > working config, as well as detailed explanation of > the theory and actual > commands. > g-) > > Kamran Ahmad wrote: > > Hello > > > > i am following this link for ser-0.9.3 but Nated > > Clients are not working. Can any one please tell > me > > what is the problem in my configuration. > > > > > http://www.voip-info.org/tiki-index.php?page=SER+nat+support > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

18 years, 8 months

Re: [Serusers] "Makefile.rules:80: action.d: No such file or directory"Errors

by Samuel Osorio Calvo

Don't worry, this files are created after the first compilation. Probably SER is already properly compiled in your host. Enjoy! Samuel. Unclassified. >>> "Jaroslaw Gawron" <j.gawron(a)wasko.pl> 08/30/05 10:20AM >>> Hello, I try to install ser-0.9.3 from source file on Mandriva 2005 limited edition and I get the following errors : Makefile.rules:80: action.d: No such file or directory Makefile.rules:80: crc.d: No such file or directory Makefile.rules:80: daemonize.d: No such file or directory Makefile.rules:80: data_lump.d: No such file or directory Makefile.rules:80: data_lump_rpl.d: No such file or directory Makefile.rules:80: dprint.d: No such file or directory Makefile.rules:80: dset.d: No such file or directory Makefile.rules:80: error.d: No such file or directory Makefile.rules:80: fifo_server.d: No such file or directory Makefile.rules:80: flags.d: No such file or directory Makefile.rules:80: forward.d: No such file or directory Makefile.rules:80: hash_func.d: No such file or directory Makefile.rules:80: ip_addr.d: No such file or directory Makefile.rules:80: main.d: No such file or directory Makefile.rules:80: md5.d: No such file or directory Makefile.rules:80: md5utils.d: No such file or directory Makefile.rules:80: modparam.d: No such file or directory Makefile.rules:80: msg_translator.d: No such file or directory Makefile.rules:80: pass_fd.d: No such file or directory Makefile.rules:80: proxy.d: No such file or directory Makefile.rules:80: qvalue.d: No such file or directory Makefile.rules:80: re.d: No such file or directory Makefile.rules:80: receive.d: No such file or directory Makefile.rules:80: resolve.d: No such file or directory Makefile.rules:80: route.d: No such file or directory Makefile.rules:80: route_struct.d: No such file or directory Makefile.rules:80: script_cb.d: No such file or directory Makefile.rules:80: socket_info.d: No such file or directory Makefile.rules:80: sr_module.d: No such file or directory Makefile.rules:80: stats.d: No such file or directory Makefile.rules:80: tcp_main.d: No such file or directory Makefile.rules:80: tcp_read.d: No such file or directory Makefile.rules:80: timer.d: No such file or directory Makefile.rules:80: tsend.d: No such file or directory Makefile.rules:80: udp_server.d: No such file or directory Makefile.rules:80: unixsock_server.d: No such file or directory Makefile.rules:80: usr_avp.d: No such file or directory Makefile.rules:80: mem/f_malloc.d: No such file or directory Makefile.rules:80: mem/mem.d: No such file or directory Makefile.rules:80: mem/memtest.d: No such file or directory Makefile.rules:80: mem/q_malloc.d: No such file or directory Makefile.rules:80: mem/shm_mem.d: No such file or directory Makefile.rules:80: mem/vq_malloc.d: No such file or directory Makefile.rules:80: parser/hf.d: No such file or directory Makefile.rules:80: parser/msg_parser.d: No such file or directory Makefile.rules:80: parser/parse_allow.d: No such file or directory Makefile.rules:80: parser/parse_content.d: No such file or directory Makefile.rules:80: parser/parse_cseq.d: No such file or directory Makefile.rules:80: parser/parse_disposition.d: No such file or directory Makefile.rules:80: parser/parse_diversion.d: No such file or directory Makefile.rules:80: parser/parse_event.d: No such file or directory Makefile.rules:80: parser/parse_expires.d: No such file or directory Makefile.rules:80: parser/parse_fline.d: No such file or directory Makefile.rules:80: parser/parse_from.d: No such file or directory Makefile.rules:80: parser/parse_hname2.d: No such file or directory Makefile.rules:80: parser/parse_hostport.d: No such file or directory Makefile.rules:80: parser/parse_methods.d: No such file or directory Makefile.rules:80: parser/parse_nameaddr.d: No such file or directory Makefile.rules:80: parser/parse_param.d: No such file or directory Makefile.rules:80: parser/parser_f.d: No such file or directory Makefile.rules:80: parser/parse_rpid.d: No such file or directory Makefile.rules:80: parser/parse_rr.d: No such file or directory Makefile.rules:80: parser/parse_sipifmatch.d: No such file or directory Makefile.rules:80: parser/parse_to.d: No such file or directory Makefile.rules:80: parser/parse_uri.d: No such file or directory Makefile.rules:80: parser/parse_via.d: No such file or directory Makefile.rules:80: parser/digest/digest.d: No such file or directory Makefile.rules:80: parser/digest/digest_parser.d: No such file or directory Makefile.rules:80: parser/digest/param_parser.d: No such file or directory Makefile.rules:80: parser/contact/contact.d: No such file or directory Makefile.rules:80: parser/contact/parse_contact.d: No such file or directory Makefile.rules:80: db/db.d: No such file or directory Makefile.rules:80: db/db_fifo.d: No such file or directory Makefile.rules:80: lex.yy.d: No such file or directory Does anyone know how to fix this problem ? Any help will be great ! Best regards, Jaroslaw Gawron

18 years, 8 months

[Serusers] NAT example

by Kamran Ahmad

Hello i am following this link for ser-0.9.3 but Nated Clients are not working. Can any one please tell me what is the problem in my configuration. http://www.voip-info.org/tiki-index.php?page=SER+nat+support ---------------------------------------------------------------- #ser.cfg # $Id: ser.cfg,v 1.21 2003/06/04 13:47:36 jiri 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" alias=mydomain.dyndns.org # ------------------ module loading ---------------------------------- loadmodule "/usr/local/lib/ser/modules/nathelper.so" loadmodule "/usr/local/lib/ser/modules/textops.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" # ----------------- setting module-specific parameters --------------- # -- 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{ # 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 (len_gt( 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; }; }; #inserted by klaus if (method=="INVITE") { record_route(); force_rtp_proxy(); /* set up reply processing */ t_on_reply("1"); }; # 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(); }; } #inserted by klaus # all incoming replies for t_onrepli-ed transactions enter here onreply_route[1] { if (status=~"[12][0-9][0-9]") force_rtp_proxy(); } __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

18 years, 8 months

← Newer
1
...
4
5
6
7
8
9
10
...
56
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users August 2005