sr-users June 2005

sr-users@lists.kamailio.org

241 participants
595 discussions

by Daniel-Constantin Mierla

Hello, there is a Wiki page where users can contribute to OpenSER documentation. It is open for everybody and we hope that everybody will have a fair attitude. http://openser.org/dokuwiki/ I have started a new document "OpenSER Core CookBook", we hope there will be many contributions. Best regards, Daniel

19 years

[Serusers] uri matching for dial plans

by Iqbal

Hi I have a nice table of prefixes and gateways, which works great using lcr, however I am now working on dial plans, i.e user can call 001, not 0044 etc etc, based on what I have in my grp table. Problem here is with codes like 001 since this would allow 001234 also, which for instance could be puerto rico (which it aint) but if it was I wouldnt want the call to go there. so I am doing something like if (uri=001 && !uri=001234) make the call...BUT this is a pain, especially for 001, I have had to block out 30 odd routes manually, which is making my ser config look really ugly. add into that other routes and suddenly we have a painful config file. So what I wanted to know is it possible to pull info from a DB, using exec, and store the value in a variable which can be used later. the grp table only really allows u to bind a "name" and then see if the from user is in that group, but it dont let you to the break that down into finer options, especially dial plans Iqbal

19 years

[serusers] PA module

by michael p

hi i tried to load the module pa but it doesn't work. how can i check for the presentity? i tried with the softphone eyebeam to add a contact to my contact list but the little man is like off line. i added in ser.cfg : loadmodule "/usr/lib/ser/modules/pa.so" and modparam("pa", "default_expires", 3600) and " handle_subscription("registrar"); " in : if (method=="REGISTER") { # Uncomment this if you want to use digest authentication if (!www_authorize("dev.annatel.net", "subscriber")) { www_challenge("dev.annatel.net", "0"); break; }; save("location"); handle_subscription("registrar"); break; }; i don't use jabber so i want when the user registrar that do the suscribe and transmit to the others... is that correct what i did? why there are so little doc about all the modules of SER? thanks for the help... M.

19 years

[Serusers] ask about using SER 0.9 with Cisco PSTN Gateway

by gunawan

i hav problem using ser 0.9 with Cisco PSTN gateway... i use Cisco Router 2620XM with voice module VIC2FXO as the RJ-11 connection and IOS Cisco 12.2(13)T4... does anyone in forum ever use cisco 2620XM as a PSTN gateway???? I need help in Cisco Configuration and Ser.cfg scripts.... it's work when i use Cisco Call Manager which use H323 Protocol as my server , and right now i want to try use SIP as my protocol and SER as my server.... thanks in advance..... __________________________________ Discover Yahoo! Stay in touch with email, IM, photo sharing and more. Check it out! http://discover.yahoo.com/stayintouch.html

19 years

[serusers] PA module

by michael p

hi where can i got informations about pa module? Is that true it doesn't work with sip messages and only work with jabber? where can i find a step by step for jabber and pa? thanks M.

19 years

[Serusers] Onsip.org ser.cfg + pstn + uac - can't authenticate on gateway

by Cameron Beattie

I am trying the get the uac module working with the onsip.org ser.cfg (the pstn + mediaproxy version). I think the problem is related to the authentication on the gateway device. It doesn't seem to be challenging SER. Below is the SIP traffic and then the ser.cfg file. Any suggestions would be appreciated. For information, the gateway (198.22.67.70) is provided by Nufone.net and is an Asterisk server, I believe. Thanks in advance for any advice. Regards Cameron U 147.202.xx.xxx:5060 -> 60.234.xxx.xxx:5060 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 192.168.0.11:5060;branch=z9hG4bK-fff17e3f;rport=5060;received=60.234 .xxx.xxx..From: <sip:user1@mydomain.com>;tag=f9493da2f8a6d10ao0..To: <sip:00442070800000@mydomain.com>..Call-ID: ce674b 82-e2fd1caa@192.168.0.11..CSeq: 102 INVITE..Server: Sip EXpress router (0.9.2 (i386/linux))..Content-Length: 0..Warning: 392 147.202.xx.xxx:5060 "Noisy feedback tells: pid=6752 req_src_ip=60.234.xxx.xxx req_src_port=5060 in_uri=sip:00442070800000@mydomain.com out_uri =sip:00442070800000@198.22.67.70 via_cnt==1".... ## U 147.202.xx.xxx:5060 -> 198.22.67.70:5060 INVITE sip:00442070800000@198.22.67.70 SIP/2.0..Record-Route: <sip:00442070800000@147.202.xx.xxx:5060;nat=yes;ftag=f9493da2f8a6d10ao0;lr=on>. .Via: SIP/2.0/UDP 147.202.xx.xxx;branch=z9hG4bK8b0a.2871d5c2.0..Via: SIP/2.0/UDP 192.168.0.11:5060;rport=5060;received=60.234.xxx.xxx;bran ch=z9hG4bK-fff17e3f..From: <sip:user1@mydomain.com>;tag=f9493da2f8a6d10ao0..To: <sip:00442070800000@mydomain.com>..Cal l-ID: ce674b82-e2fd1caa@192.168.0.11..CSeq: 102 INVITE..Max-Forwards: 16..Contact: <sip:user1@60.234.xxx.xxx:5060>..Expires: 240..User- Agent: Sipura/SPA3000-3.1.3(GWa)..Content-Length: 424..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: x-sipura ..Content-Type: application/sdp....v=0..o=- 757701 757701 IN IP4 192.168.0.11..s=-..c=IN IP4 147.202.xx.xxx..t=0 0..m=audio 35026 RTP/AVP 0 2 4 8 18 96 97 98 100 101..a=rtpmap:0 PCMU/8000..a=rtpmap:2 G726-32/8000..a=rtpmap:4 G723/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:18 G729 a/8000..a=rtpmap:96 G726-40/8000..a=rtpmap:97 G726-24/8000..a=rtpmap:98 G726-16/8000..a=rtpmap:100 NSE/8000..a=rtpmap:101 telephone-event /8000..a=fmtp:101 0-15..a=ptime:30..a=sendrecv.. # U 147.202.xx.xxx:5060 -> 60.234.xxx.xxx:5060 SIP/2.0 500 I'm terribly sorry, server error occurred (1/SL)..Via: SIP/2.0/UDP 192.168.0.11:5060;branch=z9hG4bK-fff17e3f;rport=5060;recei ved=60.234.xxx.xxx..From: <sip:user1@mydomain.com>;tag=f9493da2f8a6d10ao0..To: <sip:00442070800000@mydomain.com>;tag=66 9cac32ae43cfbf664b867e0fb4dd5a.572f..Call-ID: ce674b82-e2fd1caa@192.168.0.11..CSeq: 102 INVITE..Server: Sip EXpress router (0.9.2 (i386/l inux))..Content-Length: 0..Warning: 392 147.202.xx.xxx:5060 "Noisy feedback tells: pid=6752 req_src_ip=60.234.xxx.xxx req_src_port=5060 i n_uri=sip:00442070800000@mydomain.com out_uri=sip:00442070800000@198.22.67.70 via_cnt==1".... ## U 198.22.67.70:5060 -> 147.202.xx.xxx:5060 SIP/2.0 404 Not Found..Via: SIP/2.0/UDP 147.202.xx.xxx;branch=z9hG4bK8b0a.2871d5c2.0..Via: SIP/2.0/UDP 192.168.0.11:5060;received=60.234. xxx.xxx;branch=z9hG4bK-fff17e3f..From: <sip:user1@mydomain.com>;tag=f9493da2f8a6d10ao0..To: <sip:00442070800000@mydomain.com>;tag=as40c6caec..Call-ID: ce674b82-e2fd1caa@192.168.0.11..CSeq: 102 INVITE..User-Agent: Asterisk PBX..Allow: INVITE, ACK, CANCEL, O PTIONS, BYE, REFER, NOTIFY..Contact: <sip:00442070800000@198.22.67.70>..Content-Length: 0.... # U 147.202.xx.xxx:5060 -> 198.22.67.70:5060 ACK sip:00442070800000@198.22.67.70 SIP/2.0..Via: SIP/2.0/UDP 147.202.xx.xxx;branch=z9hG4bK8b0a.2871d5c2.0..From: <sip:user1@mydomain.com>;tag=f9493da2f8a6d10ao0..Call-ID: ce674b82-e2fd1caa@192.168.0.11..To: <sip:00442070800000@mydomain.com>;tag=as40c6caec. .CSeq: 102 ACK..User-Agent: Sip EXpress router(0.9.2 (i386/linux))..Content-Length: 0.... My ser.cfg is below: debug=3 fork=yes #fork=no log_stderror=yes check_via=no dns=no rev_dns=no fifo="/tmp/ser_fifo" fifo_db_url="mysql://user:password@localhost/ser" sock_mode=0666 #fifo_mode=0666 #fifo_user=root listen=147.202.xx.xxx port=5060 children=4 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" loadmodule "/usr/local/lib/ser/modules/auth.so" loadmodule "/usr/local/lib/ser/modules/auth_db.so" loadmodule "/usr/local/lib/ser/modules/uri.so" loadmodule "/usr/local/lib/ser/modules/uri_db.so" loadmodule "/usr/local/lib/ser/modules/avpops.so" loadmodule "/usr/local/lib/ser/modules/mediaproxy.so" loadmodule "/usr/local/lib/ser/modules/nathelper.so" loadmodule "/usr/local/lib/ser/modules/textops.so" loadmodule "/usr/local/lib/ser/modules/domain.so" loadmodule "/usr/local/lib/ser/modules/permissions.so" loadmodule "/usr/local/lib/ser/modules/acc.so" loadmodule "/usr/local/lib/ser/modules/uac.so" modparam("auth_db|permissions|uri_db|usrloc|acc", "db_url", "mysql:// user:password @localhost/ser") modparam("auth_db", "calculate_ha1", 1) modparam("auth_db", "password_column", "password") modparam("nathelper", "rtpproxy_disable", 1) modparam("nathelper", "natping_interval", 0) modparam("mediaproxy","natping_interval", 30) modparam("mediaproxy","mediaproxy_socket", "/var/run/mediaproxy.sock") modparam("mediaproxy","sip_asymmetrics","/usr/local/etc/ser/sip-clients") modparam("mediaproxy","rtp_asymmetrics","/usr/local/etc/ser/rtp-clients") modparam("usrloc", "db_mode", 2) modparam("registrar", "nat_flag", 6) modparam("rr", "enable_full_lr", 1) modparam("tm", "fr_inv_timer", 27) modparam("tm", "fr_inv_timer_avp", "inv_timeout") modparam("permissions", "db_mode", 1) modparam("permissions", "trusted_table", "trusted") modparam("acc", "db_flag", 1) modparam("acc", "db_missed_flag", 3) modparam("uac","credential","user:asterisk:password") 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 # ----------------------------------------------------------------- if (method=="INVITE" && client_nat_test("3")) { record_route_preset("147.202.xx.xxx:5060;nat=yes"); # insert IP address } else if (method!="REGISTER") { record_route(); }; # ----------------------------------------------------------------- # Call Tear Down Section # ----------------------------------------------------------------- if (method=="BYE" || method=="CANCEL") { setflag(1); 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(5); route(1); break; }; if (uri==myself) { if (method=="ACK") { route(6); break; } else 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(5); route(1); break; }; if (!lookup("location")) { sl_send_reply("404", "User Not Found"); break; }; }; route(1); } route[1] { # ----------------------------------------------------------------- # Default Message Handler # ----------------------------------------------------------------- if (!t_relay()) { if (method=="INVITE" || method=="ACK") { end_media_session(); }; sl_reply_error(); }; } route[2] { # ----------------------------------------------------------------- # REGISTER Message Handler # ---------------------------------------------------------------- sl_send_reply("100", "Trying"); if (!search("^Contact: \*") && client_nat_test("7")) { setflag(6); fix_nated_register(); force_rport(); }; 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(); }; if (method=="INVITE" && !allow_trusted()) { if (!proxy_authorize("","subscriber")) { proxy_challenge("","0"); break; } else if (!check_from()) { sl_send_reply("403", "Use From=ID"); break; }; consume_credentials(); }; lookup("aliases"); if (uri!=myself) { route(5); route(1); break; }; if (uri=~"^sip:[+|00][0-9]*@") { # International PSTN route(4); break; }; if (!lookup("location")) { if (uri=~"^sip:[0-9]{8}@") { # Domestic PSTN route(4); break; }; sl_send_reply("404", "User Not Found"); break; }; if (method=="CANCEL") { route(1); break; }; setflag(1); setflag(3); route(5); route(1); } route[4] { # ----------------------------------------------------------------- # PSTN Handler # ----------------------------------------------------------------- avp_write("i:45", "inv_timeout"); route(5); t_on_failure("4"); resetflag(8); t_relay_to_udp("198.22.67.70","5060"); route(1); } route[5] { # ----------------------------------------------------------------- # RTP Proxy Enabler # ----------------------------------------------------------------- if (isflagset(6) || isflagset(7)) { use_media_proxy(); }; } route[6] { # ------------------------------------------------------------------------ # ACK Handler # ------------------------------------------------------------------------ # ------------------------------------------------------------------------ # Aliases Section # ------------------------------------------------------------------------ lookup("aliases"); if (uri!=myself) { route(1); break; }; lookup("location"); 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(); }; } failure_route[5] { if (t_check_status("401|407")) { if (isflagset(8)) { t_reply("503","Auth failed"); break; } if (uac_auth()) { setflag(8); t_on_failure("5"); append_branch(); t_relay(); } } }

19 years

[Serusers] ultra monkey & ser

by Jack Wei

hi, I'm trying to set up a cluster of ser boxes using ultramonkey. i want ldirectord to detect if any of the ser boxes is down, but am not able to set it up properly. Here's my ldirector.cf: checktimeout=10 checkinterval=2 autoreload=no logfile="local0" quiescent=yes virtual=10.1.201.189:5060 real=10.1.201.191:5060 gate real=10.1.201.193:5060 gate scheduler=wlc protocol=udp # checktype=connect persistent=600 Using the above configuration, ipvsadm reports the real servers are up even if they aren't. If i enable "checktype=connect", ipvsadm reports the real servers are always down. if anyone know of solutions, please let me know. thanks. Jack Wei __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

19 years

Re: [Serusers] OpenSER release

by info＠beeplove.com

Are you guys planning to have a feature request page as well? Mohammad Original Message: ----------------- From: Greger V. Teigre greger(a)teigre.com Date: Wed, 15 Jun 2005 21:03:21 +0200 To: Salvatore.Giudice(a)FMR.COM, serdev(a)iptel.org, serusers(a)iptel.org Subject: Re: [Serusers] OpenSER release I completely agree with you. I have been told that there was an attempt at introducing a bug-tracking system earlier, but that it has been difficult. Anyhow, in setting up policies and procedures around the experimental directory, we have decided that usage of http://bugs.sip-router.org will be mandatory. Hopefully recent, better integration between the bug tracking system and the CVS will make it more convenient to use also for other CVS modules (however, I don't have a say there). g-) Giudice, Salvatore wrote: > I am not an advocate for either ser or openser, but I would like to > comment. > > Is openser going to be equipped with a forum/ticket system where > people can document bugs, feature requests, etc (non-configuration > issues)? > > This is just my observation and you may not agree, but I believe this > project could be much better maintained if it used a more structured > ticketing style system to manage development issues instead of the > current mailing lists. In my experience, mailing lists like this > foster a terrible user experience where many development issues can > go on without response. > > Ideally, if there was a mailing list to address user issues and > ticketing system like the one Digium uses to manage Asterisk, I think > everyone would benefit by being better informed and ser would > ultimately be a better product for it. How many people out there feel > that their issues have fallen through the cracks in the past couple > years? > > -----Original Message----- > From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] > Sent: Wednesday, June 15, 2005 4:28 AM > To: Andrei Pelinescu-Onciul > Cc: SER developer mailing list; serusers; users(a)openser.org; > devel(a)openser.org > Subject: Re: [Serusers] OpenSER release > > On 06/14/05 23:21, Andrei Pelinescu-Onciul wrote: > >> On Jun 14, 2005 at 22:48, Daniel-Constantin Mierla > <daniel(a)voice-system.ro> wrote: >> >> [...] >> >> >>> It is your opinion, but I repeat myself, that the SER code >>> maintained by us will go further -- I don't think that someone can >>> claim that we didn't do the job for our code (the only discrepancy >>> is some last-minute adds in xlog (to print avps) - will be >>> committed on unstable very soon > >>> with the new color patch). The cvs was created just to ease the >>> maintainance. The patches would be a nightmare. >>> >>> >> >> Maybe I've misunderstood you: is this only a parallel "stabilized" >> version + some features or is it a full fork (do you intend to fork >> unstable also)? >> >> > It is fork for the code that we changed (acc module, usrloc module > ...), > > in the future may be other that they do not find the path in SER. We > will maintain and upgrade our part of code from SER continuously. > >> I have no problem with another stable version, what worries me is >> fragmenting the development for unstable (which is the place where >> major changes are made). >> >> > I see no fragmenting there -- the situation is the same for SER as it > was before. For example, there is no fragment for acc module, it will > be > > maintained by who did it till now, adding what he considers necessary > there. But we came to meet a lot of requests of why the acc patch is > not > > included in the CVS (it was fully backward compatible and had new > features requested by many SER users) and we want to promote _more > open_ > > approach to contributions to all parts of code. The acc patch was sent > on November 1, 2004. No real response (neither negative, nor positive) > from maintainer to the submission since then ... are you aware of a > good > > reason?!?! ... should we wait just about (or more) half an year for > each > > contribution?!? I will not do that anymore!!! > > Daniel > >> >> Andrei >> >> >> > > _______________________________________________ > Serusers mailing list > Serusers(a)iptel.org > http://mail.iptel.org/mailman/listinfo/serusers > > _______________________________________________ > Serusers mailing list > Serusers(a)iptel.org > http://mail.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list Serusers(a)iptel.org http://mail.iptel.org/mailman/listinfo/serusers -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .

19 years

RE: [Serusers] OpenSER release

by Giudice, Salvatore

Is anyone using this bug tracking system? Is this system sponsored by iptel.org? -----Original Message----- From: m36828253-1(a)imap.1and1.com [mailto:m36828253-1@pop.1and1.com] Sent: Wednesday, June 15, 2005 3:16 PM To: greger(a)teigre.com; Giudice, Salvatore; serdev(a)lists.iptel.org; serusers(a)lists.iptel.org Subject: Re: [Serusers] OpenSER release Why the bug tracking page in a different website. Why not under iptel.org ? Mohammad Original Message: ----------------- From: Greger V. Teigre greger(a)teigre.com Date: Wed, 15 Jun 2005 21:03:21 +0200 To: Salvatore.Giudice(a)FMR.COM, serdev(a)lists.iptel.org, serusers(a)lists.iptel.org Subject: Re: [Serusers] OpenSER release I completely agree with you. I have been told that there was an attempt at introducing a bug-tracking system earlier, but that it has been difficult. Anyhow, in setting up policies and procedures around the experimental directory, we have decided that usage of http://bugs.sip-router.org will be mandatory. Hopefully recent, better integration between the bug tracking system and the CVS will make it more convenient to use also for other CVS modules (however, I don't have a say there). g-) Giudice, Salvatore wrote: > I am not an advocate for either ser or openser, but I would like to > comment. > > Is openser going to be equipped with a forum/ticket system where > people can document bugs, feature requests, etc (non-configuration > issues)? > > This is just my observation and you may not agree, but I believe this > project could be much better maintained if it used a more structured > ticketing style system to manage development issues instead of the > current mailing lists. In my experience, mailing lists like this > foster a terrible user experience where many development issues can > go on without response. > > Ideally, if there was a mailing list to address user issues and > ticketing system like the one Digium uses to manage Asterisk, I think > everyone would benefit by being better informed and ser would > ultimately be a better product for it. How many people out there feel > that their issues have fallen through the cracks in the past couple > years? > > -----Original Message----- > From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] > Sent: Wednesday, June 15, 2005 4:28 AM > To: Andrei Pelinescu-Onciul > Cc: SER developer mailing list; serusers; users(a)openser.org; > devel(a)openser.org > Subject: Re: [Serusers] OpenSER release > > On 06/14/05 23:21, Andrei Pelinescu-Onciul wrote: > >> On Jun 14, 2005 at 22:48, Daniel-Constantin Mierla > <daniel(a)voice-system.ro> wrote: >> >> [...] >> >> >>> It is your opinion, but I repeat myself, that the SER code >>> maintained by us will go further -- I don't think that someone can >>> claim that we didn't do the job for our code (the only discrepancy >>> is some last-minute adds in xlog (to print avps) - will be >>> committed on unstable very soon > >>> with the new color patch). The cvs was created just to ease the >>> maintainance. The patches would be a nightmare. >>> >>> >> >> Maybe I've misunderstood you: is this only a parallel "stabilized" >> version + some features or is it a full fork (do you intend to fork >> unstable also)? >> >> > It is fork for the code that we changed (acc module, usrloc module > ...), > > in the future may be other that they do not find the path in SER. We > will maintain and upgrade our part of code from SER continuously. > >> I have no problem with another stable version, what worries me is >> fragmenting the development for unstable (which is the place where >> major changes are made). >> >> > I see no fragmenting there -- the situation is the same for SER as it > was before. For example, there is no fragment for acc module, it will > be > > maintained by who did it till now, adding what he considers necessary > there. But we came to meet a lot of requests of why the acc patch is > not > > included in the CVS (it was fully backward compatible and had new > features requested by many SER users) and we want to promote _more > open_ > > approach to contributions to all parts of code. The acc patch was sent > on November 1, 2004. No real response (neither negative, nor positive) > from maintainer to the submission since then ... are you aware of a > good > > reason?!?! ... should we wait just about (or more) half an year for > each > > contribution?!? I will not do that anymore!!! > > Daniel > >> >> Andrei >> >> >> > > _______________________________________________ > 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 _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .

19 years

Re: [Serusers] OpenSER release

by m36828253-1＠imap.1and1.com

Why the bug tracking page in a different website. Why not under iptel.org ? Mohammad Original Message: ----------------- From: Greger V. Teigre greger(a)teigre.com Date: Wed, 15 Jun 2005 21:03:21 +0200 To: Salvatore.Giudice(a)FMR.COM, serdev(a)iptel.org, serusers(a)iptel.org Subject: Re: [Serusers] OpenSER release I completely agree with you. I have been told that there was an attempt at introducing a bug-tracking system earlier, but that it has been difficult. Anyhow, in setting up policies and procedures around the experimental directory, we have decided that usage of http://bugs.sip-router.org will be mandatory. Hopefully recent, better integration between the bug tracking system and the CVS will make it more convenient to use also for other CVS modules (however, I don't have a say there). g-) Giudice, Salvatore wrote: > I am not an advocate for either ser or openser, but I would like to > comment. > > Is openser going to be equipped with a forum/ticket system where > people can document bugs, feature requests, etc (non-configuration > issues)? > > This is just my observation and you may not agree, but I believe this > project could be much better maintained if it used a more structured > ticketing style system to manage development issues instead of the > current mailing lists. In my experience, mailing lists like this > foster a terrible user experience where many development issues can > go on without response. > > Ideally, if there was a mailing list to address user issues and > ticketing system like the one Digium uses to manage Asterisk, I think > everyone would benefit by being better informed and ser would > ultimately be a better product for it. How many people out there feel > that their issues have fallen through the cracks in the past couple > years? > > -----Original Message----- > From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] > Sent: Wednesday, June 15, 2005 4:28 AM > To: Andrei Pelinescu-Onciul > Cc: SER developer mailing list; serusers; users(a)openser.org; > devel(a)openser.org > Subject: Re: [Serusers] OpenSER release > > On 06/14/05 23:21, Andrei Pelinescu-Onciul wrote: > >> On Jun 14, 2005 at 22:48, Daniel-Constantin Mierla > <daniel(a)voice-system.ro> wrote: >> >> [...] >> >> >>> It is your opinion, but I repeat myself, that the SER code >>> maintained by us will go further -- I don't think that someone can >>> claim that we didn't do the job for our code (the only discrepancy >>> is some last-minute adds in xlog (to print avps) - will be >>> committed on unstable very soon > >>> with the new color patch). The cvs was created just to ease the >>> maintainance. The patches would be a nightmare. >>> >>> >> >> Maybe I've misunderstood you: is this only a parallel "stabilized" >> version + some features or is it a full fork (do you intend to fork >> unstable also)? >> >> > It is fork for the code that we changed (acc module, usrloc module > ...), > > in the future may be other that they do not find the path in SER. We > will maintain and upgrade our part of code from SER continuously. > >> I have no problem with another stable version, what worries me is >> fragmenting the development for unstable (which is the place where >> major changes are made). >> >> > I see no fragmenting there -- the situation is the same for SER as it > was before. For example, there is no fragment for acc module, it will > be > > maintained by who did it till now, adding what he considers necessary > there. But we came to meet a lot of requests of why the acc patch is > not > > included in the CVS (it was fully backward compatible and had new > features requested by many SER users) and we want to promote _more > open_ > > approach to contributions to all parts of code. The acc patch was sent > on November 1, 2004. No real response (neither negative, nor positive) > from maintainer to the submission since then ... are you aware of a > good > > reason?!?! ... should we wait just about (or more) half an year for > each > > contribution?!? I will not do that anymore!!! > > Daniel > >> >> Andrei >> >> >> > > _______________________________________________ > Serusers mailing list > Serusers(a)iptel.org > http://mail.iptel.org/mailman/listinfo/serusers > > _______________________________________________ > Serusers mailing list > Serusers(a)iptel.org > http://mail.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list Serusers(a)iptel.org http://mail.iptel.org/mailman/listinfo/serusers -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .

19 years

← Newer
1
...
30
31
32
33
34
35
36
...
60
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 June 2005