sr-users November 2007

sr-users@lists.kamailio.org

138 participants
248 discussions

by Patrick Miccio

Hi everyone, I came across another problem when using a newly compiled OpenSER binary (from 1.1.1-notls source with no modifications). When starting OpenSER with -c -f configfile I would get the following errors: ----- 0(18837) parse error (354,1-2): invalid routing table number ----- Looking around with google I found out that this is because in the original config.h the following is set: ------ define RT_NO 40 /* routing tables number */ ------ In my openser.cfg there is already 44 routing tables ;) So my question is: can you somehow set RT_NO in openser.cfg, or is that only possible in config.h + recompiling? digital greetings, Patrick. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person: to do so could be a breach of confidence. Thank you for your cooperation. Information pursuant to paragraph 14 Austrian Companies Code: UPC Austria GmbH; Registered Office: Wolfganggasse 58-60, 1120 Vienna Company Register Number: FN 189858d at the Commercial Court of Vienna

16 years, 11 months

[Serusers] ser presence question

by Yufei Tao

Hi I want to be able to use PUBLISH/SUBSCRIBE/NOTIFY for presence information of users. So users can update their presence information by PUBLISH and watchers be informed by NOTIFY when there are changes in the presence status. I am using pa.so, mysql. Not using XCAP. My problems are 1. The OK from SER to PUBLISH has no SIP_ETag. Also SER prints out debug messages saying: publish_presentity: no tuple for 01(a)sertest.com I wonder if there's something wrong with my PUBLISH and PIDF so SER is not processing it? 2. The watcher subscribes to the presentity 01(a)sertest.com. But the NOTIFY message the watcher gets always has basic status being closed, despite that the presentity has PUBLISHed its status as open. I guess this may be due to problem 1 - SER never understood the PUBLISH? Currently my UA sends PUBLISH message: PUBLISH sip:01@sertest.com:5060 SIP/2.0 via: SIP/2.0/UDP 192.168.168.149:40070;branch=z9hG4bK314278337 max-forwards: 70 to: <sip:01@sertest.com:5060> from: <sip:01@sertest.com:5060>;tag=314279337 call-id: cd674de3-0-1196253409 cseq: 46046 PUBLISH contact: <sip:01@192.168.168.149:40070> expires: 3600 user-agent: Red v1.00 0.6.3.42 - von event: presence content-type: application/pidf+xml content-length: 274 <?xml version="1.0" encoding="UTF-8"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" entity="sip:01@sertest.com"> <tuple id="status"> <status> <basic>open</basic> </status> <contact priority="0.500000">sip:01@sertest.com</contact> </tuple> </presence> and SER replies with the following msg where there is no SIP-ETag field: SIP/2.0 200 OK via: SIP/2.0/UDP 192.168.168.149:40070;branch=z9hG4bK314278338 to: <sip:01@sertest.com:5060>;tag=482760500770a188d9ef565befb876b4-7979 from: <sip:01@sertest.com:5060>;tag=314279338 call-id: cd674de3-0-1196253409 cseq: 46047 PUBLISH Server: Sip EXpress router (0.9.6 (i386/linux)) Content-Length: 0 Warning: 392 192.168.168.241:5060 "Noisy feedback tells: pid=14095 req_src_ip=192.168.168.149 req_src_port=40070 in_uri=sip:01@sertest.com:5060 out_uri=sip:01@sertest.com:5060 via_cnt==1" The parts in my ser.cfg that are relevant to SUBSCRIBE and PUBLISH: modparam("usrloc", "db_mode", 2) modparam("usrloc", "timer_interval", 10) modparam("auth_db", "calculate_ha1", 1) modparam("auth_db", "password_column", "password") modparam("rr", "enable_full_lr", 1) # for SUBSCRIBE/NOTIFY modparam("pa", "default_expires", 3600) modparam("pa", "use_db", 1) modparam("pa", "db_url", "mysql://ser:heslo@localhost/ser") modparam("pa", "pa_domain", "sertest.com")# -- same as or different from registrar ... ... ... ... if (method=="SUBSCRIBE") { if (!t_newtran()) { sl_reply_error(); break; }; handle_subscription("registrar"); break; } if (method=="PUBLISH") { if (!t_newtran()) { log(1, "newtran error\n"); sl_reply_error(); }; handle_publish("registrar"); break; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); break; };

16 years, 11 months

[OpenSER-Users] OpenSer: Group Module Parameter "re_exp_column"

by Helmut Kuper

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, the example in OpenSER 1.3 and devel module doc for module group is wrong. It gives this line as example: modparam("group", "reg_exp_column", "re") but it should be: modparam("group", "reg_exp_column", "reg_exp") minor thing, but anoying, when u just copy and paste modparams into your config without reading the chapter titles .... Maybe there should be a block with all modparams and their default values in each module's doc... regards Helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHTDhm4tZeNddg3dwRAh/5AKC0r9jbisrrR+YZC0BKtk6hzGz8oQCdEtcv 2oHfwzkoe43hGB4YO4dv6mM= =ysim -----END PGP SIGNATURE-----

16 years, 11 months

[OpenSER-Users] multiple contact

by Daniel

Hi all, I have a user A registering with 2 differrent contact, one of each behind NAT. If I set "modparam("registrar", "append_branches", 1)", and if q-values are setted as 1, the proxy, aftel lookup (location) will call both of contacts in parallel mode. But how can I manage the Natted contact and set mediaproxy ? regards, daniel -- Daniel Grotti ________________________ e-mail : d.grotti(a)gmail.com

16 years, 11 months

[OpenSER-Users] editing the via header

by Othmar Pasteka

hello, I would like to know when the via header of the openser proxy is inserted (the new one). and/or if there is a practical way to manipulate it by me in a different module, like that some additional information is added after the branch tag. I browsed through the documentation and also googled but couldn't find valuable information how the via headers are treated in this respect. I found the reference in parser/msg_parser.h:struct sip_msg, that they reference via1/via2 but I assume via1 is not the current one which will be added by the local openser proxy. any additional information is greatly appreciated. thanks. regards, Othmar

16 years, 11 months

[OpenSER-Users] [CPL] Why aren't loaded bflags when <lookup source="registration"> ?

by Iñaki Baz Castillo

Hi, I set: modparam("cpl-c","proxy_route", 10) and in route[10] I set RtpProxy if flag(5) (NAT in the caller) or bflag(6) (NAT in the called) is present. But unfortunatelly the bflag(6) is never set when usingCPL. For example the following and very simple CPL: <cpl> <incoming> <lookup source="registration"> <success> <proxy /> </success> </lookup> </incoming> </cpl> I understand that the operation of CPL is "encapsulated" and so, but since we can spec some parameters as: modparam("cpl-c","lookup_domain","location") modparam("cpl-c","lookup_append_branches", 1) why then can't bflags be loaded? If it is not possible then I can't use <lookup source="registration"> and need to do, neccesarialy, a spiral with: <location url="sip:SAME_USER;cpl=no"> <proxy /> </location> and don't apply CPL in the spiral incoming message if URI has "cpl=no". Any explanation of this limitation could be really great. Thanks a lot. -- Iñaki Baz Castillo

16 years, 11 months

Re: [Serusers] nathelper doesn't ping registered users

by Jiri Kuthan

I'm kind of finding this conversation a bit confusing -- what is cl in this context actually good for? I mean the "boundary proxy" (what is it actually good for?) can have shadow usrloc (it is presumably in the path anyhow?) if natping shall be sent from there. sip-based natping can be run from the "inside proxy" as well, very much as any other SIP request. That causes heavier traffic but also increases the success chance (for example behind my firewall and with my SIP phone, non-SIP pings does not help because client doesn't send enough outbound traffic) Just wild guesses -- I'm not really understanding the specifics of this proxy chain. -jiri At 15:13 27/11/2007, Tomasz Zieleniewski wrote: >unfortunatelly it is not available >any chance to have it for ser 2.0?? > >regards >tomasz > >On Nov 27, 2007 2:51 PM, Greger V. Teigre <greger(a)teigre.com> wrote: >> >> usrloc-cl is a cacheless version of usrloc module, i.e. nothing is stored >> in memory. I believe Martin Hoffmann took over maintenance of it, but I'm >> not sure about the status on 2.0.0. If your edge proxy uses usrloc-cl >> instead of usrloc, it will pull locations to ping from the DB instead of >> from memory. >> >> >> g-) >> >> Tomasz Zieleniewski wrote: >> what is usrloc-cl?? >> What do you mean by that and how can I do that? >> >> -tomasz >> >> On Nov 27, 2007 8:58 AM, Greger V. Teigre <greger(a)teigre.com> wrote: >> >> >> You use usrloc-cl? >> If not, unless you replicate, the non-REGISTER handling server will not >> have the usrloc in memory. >> g-) >> >> >> >> Tomasz Zieleniewski wrote: >> Hi Jiri, >> >> On Nov 25, 2007 10:08 PM, Jiri Kuthan <jiri(a)iptel.org> wrote: >> >> >> At 10:56 25/11/2007, Tomasz Zieleniewski wrote: >> >> >> Hi, >> >> I don't have those lines because I have a registrar on seperate SIP Proxy. >> This proxy here is the boundary one, but they both use the same database >> and have access to location table common. >> >> Well, I'm not sure I'm getting the context of this configuration so I don't >> feel certain with providing some hints (in particular two proxy serveer >> in a series both using usrloc seems unusual to me). A hand-waving estimate >> is you need to configure the "boundary proxy" to change all natted clients >> to form "as seen by the network" and the "actual proxy" to send pings to >> all contacts. >> >> >> Boundary proxy uses usrloc only for the purpose of pinging the natted >> users. >> Nathelper module requires usrloc. Because all reuqest travels 'boundary >> proxy' >> before entering network the 'boundary proxy' must ping users to keep >> my nat bindings >> right. they are both on seperate machines. >> >> -tomek >> >> >> -jiri >> >> >> >> >> >> -tomasz >> >> On Nov 25, 2007 10:40 AM, Jiri Kuthan <jiri(a)iptel.org> wrote: >> >> >> Hi Tomasz, >> >> well it could be that reusing an existing config and commiting than your >> specific >> changes to it would save you quite some laborous exercises rather than >> writing >> it from scratch.... >> http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/etc/ser-oob.cfg?re… >> >> The lines in question are (out of which I think you are missing the >> registrar params) >> >> >> FLAG_NAT : 3, # the UAC is behind a NAT >> >> ... >> # identify natted contacts using a flag >> modparam("registrar", "load_nat_flag", "FLAG_NAT") >> modparam("registrar", "save_nat_flag", "FLAG_NAT") >> ... >> modparam("rr", "cookie_filter", "(account|uac_nat)") >> ... >> modparam("nathelper", "ping_nated_only", 1 ) >> # if this option is not set, simple 4-bytes ping is sent >> modparam("nathelper", "natping_method", "OPTIONS" ) >> #temporary statefull natping test (only in future versions) >> #modparam("nathelper", "natping_stateful", 1) >> ... >> >> setflag(FLAG_NAT); >> >> >> -jiri >> >> >> At 22:20 24/11/2007, Tomasz Zieleniewski wrote: >> >> >> I'm sorry for the CC >> here is my config: >> >> debug=3 # debug level (cmd line: -dddddddddd) >> memdbg=5 >> memlog=5 >> log_facility=LOG_LOCAL0 >> fork=yes >> log_stderror=no >> check_via=yes # (cmd. line: -v) >> dns=no # (cmd. line: -r) >> rev_dns=no # (cmd. line: -R) >> port=5060 >> tls_port_no=5061 >> children=4 >> user=ser >> group=ser >> mhomed=yes >> disable_tcp=no >> tcp_accept_aliases=yes >> enable_tls=no >> sip_warning=0 >> reply_to_via=no >> alias="voip.touk.pl" >> >> dns_retr_time=1 >> dns_retr_no=1 >> dns_servers_no=1 >> dns_use_search_list=no >> dns_try_ipv6=no >> # dns cache & failover >> use_dns_cache=on >> use_dns_failover=on >> # dns_cache_flags=0 >> dns_cache_negative_ttl=300 >> dns_cache_min_ttl=60 >> dns_cache_max_ttl=86400 # 1 day >> dns_cache_mem=2048 # 2 MB >> dns_cache_gc_interval=60 >> >> tcp_connection_lifetime=3600 >> tcp_max_connections=2048 >> tcp_connect_timeout=1 >> >> loadmodule ... >> .... >> >> # specify the path to you database here >> modparam("acc_db|auth_db|avp_db|domain|gflags|usrloc|uri_db|speeddial|msilo|lcr", >> "db_url", "mysql://ser:ser@localhost/ser") >> >> # -- usrloc params -- >> modparam("usrloc", "db_mode", 1) >> >> # -- registrar params -- >> modparam("registrar", "default_expires", 300) >> modparam("registrar", "min_expires", 60) >> modparam("registrar", "max_expires", 300) >> modparam("registrar", "append_branches", 1) >> modparam("registrar", "received_param", "rcv") >> modparam("registrar", "max_contacts", 2) >> >> # -- auth params -- >> modparam("auth_db", "calculate_ha1", yes) >> modparam("auth_db", "password_column", "password") >> >> # -- rr params -- >> modparam("rr", "enable_full_lr", 1) >> modparam("rr", "cookie_filter", "uac_nat") >> modparam("rr", "cookie_secret", "secret") >> modparam("rr", "user_part_avp", "route_user") >> modparam("rr", "next_route_avp", "route_next") >> >> # -- gflags params -- >> modparam("gflags", "load_global_attrs", 1) >> >> # -- domain params -- >> modparam("domain", "load_domain_attrs", 1) >> >> # -- ctl params -- >> modparam("ctl", "binrpc", "unixs:/tmp/ser-bsp_ctl") >> modparam("ctl", "fifo", "fifo:/tmp/ser-bsp_fifo") >> # modparam("ctl", "binrpc", "tcp:localhost:2046") >> modparam("ctl", "mode", 0777) >> >> # -- tm params -- >> modparam("tm", "restart_fr_on_each_reply", 1) >> >> # -- auth_radius params -- >> modparam("auth_radius", "radius_config", >> "/usr/local/etc/radiusclient-ng/radiusclient.conf") >> modparam("auth_radius", "service_type", 15) >> >> # -- options params -- >> modparam("options", "accept", "*/*") >> modparam("options", "accept_encoding", "") >> modparam("options", "accept_language", "en") >> >> # -- ratelimit params -- >> modparam("ratelimit","timer_interval", 10) >> modparam("ratelimit","invite_limit", 100) >> modparam("ratelimit","register_limit", 100) >> modparam("ratelimit","subscribe_limit", 100) >> >> # -- xmlrpc params -- >> modparam("xmlrpc", "route","RPC") >> >> # -- nathelper params -- >> modparam("nathelper", "natping_interval", 20) >> modparam("nathelper", "ping_nated_only", 0) >> modparam("nathelper", "rtpproxy_disable", 1) >> modparam("nathelper", "tcpping_crlf", 1) >> >> # -- tls params -- >> modparam("tls", "config", "/home/ser/ser/ca/tls-bsp.cfg") >> modparam("tls", "tls_force_run", 0) >> modparam("tls", "tls_log",3) >> modparam("tls", "handshake_timeout", 10) >> modparam("tls", "send_timeout", 10) >> modparam("tls", "tls_disable_compression", 0) >> #modparam("tls", "private_key", "/etc/certs/key.pem") >> #modparam("tls", "certificate", "/etc/certs/cert.pem") >> #modparam("tls", "ca_list", "/etc/certs/ca_list.pem") >> #modparam("tls", "require_certificate", 0) >> #modparam("tls", "verify_certificate", 1) >> #modparam("tls", "tls_method", "TLSv1") >> >> route{ >> ... >> } >> >> On Nov 24, 2007 9:35 PM, Atle Samuelsen <clona(a)cyberhouse.no> wrote: >> >> >> Hi, >> >> Always CC the list. >> >> then I dont know.. post your full config so people can see if they see >> something >> -A >> >> * Tomasz Zieleniewski <tzieleniewski(a)gmail.com> [071124 20:38]: >> >> >> >> Hi, >> >> I had that parameter set to 0, but still no udp packets... >> >> On Nov 24, 2007 6:43 PM, Atle Samuelsen <clona(a)cyberhouse.no> wrote: >> >> >> * Tomasz Zieleniewski <tzieleniewski(a)gmail.com> [071124 16:50]: >> >> >> >> HI, >> >> I have the following nathelper settings: >> modparam("nathelper", "natping_interval", 20) >> modparam("nathelper", "ping_nated_only", 1) >> modparam("nathelper", "rtpproxy_disable", 1) >> modparam("nathelper", "tcpping_crlf", 1) >> >> But i cant see any udp packets being sent to registered users. >> Please point me what did I miss. >> >> Hi, >> >> without seeing any more of your config, I'm guessing that you do not set >> the natflag, so if you change ping_nated_only to 0, I think you will see >> some udp packets. >> >> - Atle >> (shot in the whild world of sip) >> >> >> >> >> Best >> Tomasz >> _______________________________________________ >> Serusers mailing list >> Serusers(a)lists.iptel.org >> http://lists.iptel.org/mailman/listinfo/serusers >> >> _______________________________________________ >> Serusers mailing list >> Serusers(a)lists.iptel.org >> http://lists.iptel.org/mailman/listinfo/serusers >> >> >> -- >> Jiri Kuthan http://iptel.org/~jiri/ >> >> >> >> _______________________________________________ >> Serusers mailing list >> Serusers(a)lists.iptel.org >> http://lists.iptel.org/mailman/listinfo/serusers >> >> >> -- >> Jiri Kuthan http://iptel.org/~jiri/ >> >> >> >> _______________________________________________ >> Serusers mailing list >> Serusers(a)lists.iptel.org >> http://lists.iptel.org/mailman/listinfo/serusers >> >> >> >> >> >> _______________________________________________ >> Serusers mailing list >> Serusers(a)lists.iptel.org >> http://lists.iptel.org/mailman/listinfo/serusers >> >> >> >> -- Jiri Kuthan http://iptel.org/~jiri/

16 years, 11 months

Re: [Serusers] nathelper doesn't ping registered users

by Jiri Kuthan

At 10:56 25/11/2007, Tomasz Zieleniewski wrote: >Hi, > >I don't have those lines because I have a registrar on seperate SIP Proxy. >This proxy here is the boundary one, but they both use the same database >and have access to location table common. Well, I'm not sure I'm getting the context of this configuration so I don't feel certain with providing some hints (in particular two proxy serveer in a series both using usrloc seems unusual to me). A hand-waving estimate is you need to configure the "boundary proxy" to change all natted clients to form "as seen by the network" and the "actual proxy" to send pings to all contacts. -jiri >-tomasz > >On Nov 25, 2007 10:40 AM, Jiri Kuthan <jiri(a)iptel.org> wrote: >> Hi Tomasz, >> >> well it could be that reusing an existing config and commiting than your specific >> changes to it would save you quite some laborous exercises rather than writing >> it from scratch.... >> http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/etc/ser-oob.cfg?re… >> >> The lines in question are (out of which I think you are missing the registrar params) >> >> >> FLAG_NAT : 3, # the UAC is behind a NAT >> >> ... >> # identify natted contacts using a flag >> modparam("registrar", "load_nat_flag", "FLAG_NAT") >> modparam("registrar", "save_nat_flag", "FLAG_NAT") >> ... >> modparam("rr", "cookie_filter", "(account|uac_nat)") >> ... >> modparam("nathelper", "ping_nated_only", 1 ) >> # if this option is not set, simple 4-bytes ping is sent >> modparam("nathelper", "natping_method", "OPTIONS" ) >> #temporary statefull natping test (only in future versions) >> #modparam("nathelper", "natping_stateful", 1) >> ... >> >> setflag(FLAG_NAT); >> >> >> -jiri >> >> >> At 22:20 24/11/2007, Tomasz Zieleniewski wrote: >> >I'm sorry for the CC >> >here is my config: >> > >> >debug=3 # debug level (cmd line: -dddddddddd) >> >memdbg=5 >> >memlog=5 >> >log_facility=LOG_LOCAL0 >> >fork=yes >> >log_stderror=no >> >check_via=yes # (cmd. line: -v) >> >dns=no # (cmd. line: -r) >> >rev_dns=no # (cmd. line: -R) >> >port=5060 >> >tls_port_no=5061 >> >children=4 >> >user=ser >> >group=ser >> >mhomed=yes >> >disable_tcp=no >> >tcp_accept_aliases=yes >> >enable_tls=no >> >sip_warning=0 >> >reply_to_via=no >> >alias="voip.touk.pl" >> > >> >dns_retr_time=1 >> >dns_retr_no=1 >> >dns_servers_no=1 >> >dns_use_search_list=no >> >dns_try_ipv6=no >> ># dns cache & failover >> >use_dns_cache=on >> >use_dns_failover=on >> ># dns_cache_flags=0 >> >dns_cache_negative_ttl=300 >> >dns_cache_min_ttl=60 >> >dns_cache_max_ttl=86400 # 1 day >> >dns_cache_mem=2048 # 2 MB >> >dns_cache_gc_interval=60 >> > >> >tcp_connection_lifetime=3600 >> >tcp_max_connections=2048 >> >tcp_connect_timeout=1 >> > >> >loadmodule ... >> >.... >> > >> ># specify the path to you database here >> >modparam("acc_db|auth_db|avp_db|domain|gflags|usrloc|uri_db|speeddial|msilo|lcr", >> >"db_url", "mysql://ser:ser@localhost/ser") >> > >> ># -- usrloc params -- >> >modparam("usrloc", "db_mode", 1) >> > >> ># -- registrar params -- >> >modparam("registrar", "default_expires", 300) >> >modparam("registrar", "min_expires", 60) >> >modparam("registrar", "max_expires", 300) >> >modparam("registrar", "append_branches", 1) >> >modparam("registrar", "received_param", "rcv") >> >modparam("registrar", "max_contacts", 2) >> > >> ># -- auth params -- >> >modparam("auth_db", "calculate_ha1", yes) >> >modparam("auth_db", "password_column", "password") >> > >> ># -- rr params -- >> >modparam("rr", "enable_full_lr", 1) >> >modparam("rr", "cookie_filter", "uac_nat") >> >modparam("rr", "cookie_secret", "secret") >> >modparam("rr", "user_part_avp", "route_user") >> >modparam("rr", "next_route_avp", "route_next") >> > >> ># -- gflags params -- >> >modparam("gflags", "load_global_attrs", 1) >> > >> ># -- domain params -- >> >modparam("domain", "load_domain_attrs", 1) >> > >> ># -- ctl params -- >> >modparam("ctl", "binrpc", "unixs:/tmp/ser-bsp_ctl") >> >modparam("ctl", "fifo", "fifo:/tmp/ser-bsp_fifo") >> ># modparam("ctl", "binrpc", "tcp:localhost:2046") >> >modparam("ctl", "mode", 0777) >> > >> ># -- tm params -- >> >modparam("tm", "restart_fr_on_each_reply", 1) >> > >> ># -- auth_radius params -- >> >modparam("auth_radius", "radius_config", >> >"/usr/local/etc/radiusclient-ng/radiusclient.conf") >> >modparam("auth_radius", "service_type", 15) >> > >> ># -- options params -- >> >modparam("options", "accept", "*/*") >> >modparam("options", "accept_encoding", "") >> >modparam("options", "accept_language", "en") >> > >> ># -- ratelimit params -- >> >modparam("ratelimit","timer_interval", 10) >> >modparam("ratelimit","invite_limit", 100) >> >modparam("ratelimit","register_limit", 100) >> >modparam("ratelimit","subscribe_limit", 100) >> > >> ># -- xmlrpc params -- >> >modparam("xmlrpc", "route","RPC") >> > >> ># -- nathelper params -- >> >modparam("nathelper", "natping_interval", 20) >> >modparam("nathelper", "ping_nated_only", 0) >> >modparam("nathelper", "rtpproxy_disable", 1) >> >modparam("nathelper", "tcpping_crlf", 1) >> > >> ># -- tls params -- >> >modparam("tls", "config", "/home/ser/ser/ca/tls-bsp.cfg") >> >modparam("tls", "tls_force_run", 0) >> >modparam("tls", "tls_log",3) >> >modparam("tls", "handshake_timeout", 10) >> >modparam("tls", "send_timeout", 10) >> >modparam("tls", "tls_disable_compression", 0) >> >#modparam("tls", "private_key", "/etc/certs/key.pem") >> >#modparam("tls", "certificate", "/etc/certs/cert.pem") >> >#modparam("tls", "ca_list", "/etc/certs/ca_list.pem") >> >#modparam("tls", "require_certificate", 0) >> >#modparam("tls", "verify_certificate", 1) >> >#modparam("tls", "tls_method", "TLSv1") >> > >> >route{ >> >... >> >} >> > >> >On Nov 24, 2007 9:35 PM, Atle Samuelsen <clona(a)cyberhouse.no> wrote: >> >> Hi, >> >> >> >> Always CC the list. >> >> >> >> then I dont know.. post your full config so people can see if they see >> >> something >> >> -A >> >> >> >> * Tomasz Zieleniewski <tzieleniewski(a)gmail.com> [071124 20:38]: >> >> >> >> > Hi, >> >> > >> >> > I had that parameter set to 0, but still no udp packets... >> >> > >> >> > On Nov 24, 2007 6:43 PM, Atle Samuelsen <clona(a)cyberhouse.no> wrote: >> >> > > * Tomasz Zieleniewski <tzieleniewski(a)gmail.com> [071124 16:50]: >> >> > > >> >> > > > HI, >> >> > > > >> >> > > > I have the following nathelper settings: >> >> > > > modparam("nathelper", "natping_interval", 20) >> >> > > > modparam("nathelper", "ping_nated_only", 1) >> >> > > > modparam("nathelper", "rtpproxy_disable", 1) >> >> > > > modparam("nathelper", "tcpping_crlf", 1) >> >> > > > >> >> > > > But i cant see any udp packets being sent to registered users. >> >> > > > Please point me what did I miss. >> >> > > >> >> > > Hi, >> >> > > >> >> > > without seeing any more of your config, I'm guessing that you do not set >> >> > > the natflag, so if you change ping_nated_only to 0, I think you will see >> >> > > some udp packets. >> >> > > >> >> > > - Atle >> >> > > (shot in the whild world of sip) >> >> > > >> >> > > >> >> > > > >> >> > > > Best >> >> > > > Tomasz >> >> > > > _______________________________________________ >> >> > > > Serusers mailing list >> >> > > > Serusers(a)lists.iptel.org >> >> > > > http://lists.iptel.org/mailman/listinfo/serusers >> >> > > >> >> >> >_______________________________________________ >> >Serusers mailing list >> >Serusers(a)lists.iptel.org >> >http://lists.iptel.org/mailman/listinfo/serusers >> >> >> >> -- >> Jiri Kuthan http://iptel.org/~jiri/ >> >> >_______________________________________________ >Serusers mailing list >Serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

16 years, 11 months

[OpenSER-Users] OpenSER Core CookBook link on openser.org

by Ovidiu Sas

It would be really handy to have a link to the CoreBook page from the main doc page: http://www.openser.org/docs/ This page starts with a shortcut for the wiki (the first link), but after that it would be nice to have links to the CoreBook/version page just like we have for modules, PV and transformations. Regards, Ovidiu Sas

16 years, 11 months

[OpenSER-Users] OpensSer Release Name

by Walter Rodrigues Filho

Dear Bogdan - Since OpenSer has deep roots in Rumania, and considering the suggestions like: * blackcat (because of the 13 thing...) * Santa "Curz"(instead of Cruz it looks like a CURSE...) * deadly SINS (like luxuria, gula...) They are all drive you into either BAD or superstitious concepts.... heheh IN THIS LINE, I would suggest then people names related somehow to Rumanian history (eventough they may have not been Rumanians but after all OpenSer is OPEN to other nationalities to improve and contribute on it...) * DRACULA * IVAN * ATTILA * CORVINUS All of them have had something to do with Rumania in certain time like all members of this opensource community. IN CONCLUSION: All of them is good but "blackcat" is much to much similar to american missiles (tomcat and things..). We really should have here a LATIN BASED NAME or Rumanian history related name (eventhough the names could be of temporary CONQUERORS of Rumania...hehe). END OF LINE> Walter Rodrigues Filho Brazil

16 years, 11 months

← Newer
1
2
3
4
5
6
7
...
25
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 November 2007