sr-users

sr-users@lists.kamailio.org

48 participants
37555 discussions

[Users] Prefix in ENUM
by Andrew And 31 May '06

31 May '06

I have prefix e.164 that I need to change by domainame, but I have problem with DNS. When I have prefix "19991" I need to change URI by "@domainname.br". Is the regexp "!^.*$sip:.+$!@domainname.br" correct? $ORIGIN 1.9.9.9.1.e164.arpa. IN NAPTR 1 10 "E2U+sip" "!^.*$sip:.+$!@domainname.br".

2 1

[Users] Call not approved
by raviprakash sunkara 31 May '06

31 May '06

Hi Everybody, I had arrived a small problem , when i making the call from softphones.... It logined and when dialing to some other softphone , its show me as " CALL NOT aPPROVED " what this means, please solve problem.... and my openser.cfg file -------------------------- # # $Id: openser.cfg,v 1.5 2005/10/28 19:45:33 bogdan_iancu Exp $ # # simple quick-start config script # # ----------- global configuration parameters ------------------------ debug=4 # debug level (cmd line: -dddddddddd) fork=no log_stderror=yes # (cmd line: -E) /* Uncomment these lines to enter debugging mode fork=no log_stderror=yes */ server_signature=yes unix_sock="/tmp/openser.sock" #user="openser" #group="openser" listen=192.168.2.55 check_via=0 # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=3 alias=192.168.2.55 fifo="/tmp/openser_fifo" fifo_db_url="mysql://openser:openserrw@localhost/openser" fifo_mode=0666 #fifo_dir="/tmp/" #fifo_modesock_modefile_mode=0660 # # uncomment the following lines for TLS support #disable_tls = 0 #listen = tls:your_IP:5061 #tls_verify = 1 #tls_require_certificate = 0 #tls_method = TLSv1 #tls_certificate = "/usr/local/etc/openser/tls/user/user-cert.pem" #tls_private_key = "/usr/local/etc/openser/tls/user/user-privkey.pem" #tls_ca_list = "/usr/local/etc/openser/tls/user/user-calist.pem" # ------------------ module loading ---------------------------------- # Uncomment this if you want to use SQL database 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/textops.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! loadmodule "/usr/local/lib/openser/modules/auth.so" loadmodule "/usr/local/lib/openser/modules/auth_db.so" loadmodule "/usr/local/lib/openser/modules/acc.so" # ----------------- setting module-specific parameters --------------- # -- usrloc params -- #modparam("usrloc", "db_mode", 1) # Uncomment this if you want to use SQL database # for persistent storage and comment the previous line modparam("usrloc", "db_mode", 2) # -- auth params -- # Uncomment if you are using auth module # modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # modparam("auth_db", "password_column", "password") # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) modparam("usrloc","db_url","mysql://openser:openserrw@localhost/openser") #modparam("auth","db_url","mysql://openser:openserrw@localhost/openser") modparam("auth_db","db_url","mysql://openser:openserrw@localhost/openser") modparam("auth","secret","") modparam("acc","log_flag",1) modparam("acc","log_level",1) modparam("acc","radius_config","/usr/local/etc/radiusclient-ng/radiusclient.conf") # ------------------------- 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"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; # 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 withing 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); }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); # if you have some interdomain connections via TLS #if(uri=~"@tls_domain1.net") { # t_relay_to_tls("IP_domain1","port_domain1"); # exit; #} else if(uri=~"@tls_domain2.net") { # t_relay_to_tls("IP_domain2","port_domain2"); # exit; #} route(1); }; # 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("192.168.2.55", "subscriber")) { www_challenge("192.168.2.55", "0"); exit; }; save("location"); setflag(1); if(method=="INVITE") { record_route(); }; exit; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); exit; }; 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(); }; exit; } Bye -- Thanks and Regards with cheers Sunkara Ravi Prakash (Voip Developer) Hyperion Technology www.hyperion-tech.com <b>

2 1

[Serusers] RE: Authorizing IM requests
by İlker Aktuna (Koç.net) 31 May '06

31 May '06

Hi Vaclav, On which file does Ser look for when authorizing messages ? According to that maybe I can link privacy-lists file to im-rules file (which Ser looks for) Would that work ? Usrloc problem is very important for me. Please tell me anything I can do to find out the problem (if there is anything that I can do) Thanks, ilker -----Original Message----- From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] Sent: Wednesday, May 31, 2006 9:29 AM To: İlker Aktuna (Koç.net) Cc: samuel; serusers(a)iptel.org Subject: Re: Authorizing IM requests Hi, yes I did, but I had forgotten... You can NOT use EyeBeam to work with message authorization - it will NEVER set the rules which are needed by SER. You can do this only manually on XCAP server. I try to look on the userloc problem, but don't know when. Vaclav On Tue, May 30, 2006 at 05:29:27PM +0300, ?lker Aktuna (Koç.net) wrote: > Hi Vaclav, > > Did you receive my following email ? > > Btw, I still couldn't find the neccessary db structure for using > usrloc with db support. Can you point me to the right person who knows > the required db structure ? > > Thanks, > ilker > > ________________________________ > > From: ?lker Aktuna (Koç.net) > Sent: Monday, May 29, 2006 12:52 PM > To: 'Vaclav Kubart' > Cc: samuel; serusers(a)iptel.org > Subject: RE: Authorizing IM requests > > > > > Well, then what can I use in the following line to authorize IM messages ? > > if (authorize_message("https://sip.koc.net/xcap")) { > > Eyebeam updates file /xcap/privacy-lists/user/privacy-lists.xml when I change the "privacy" configuration on Eyebeam client. > > Thanks, > ilker > > -----Original Message----- > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] > Sent: Friday, May 26, 2006 4:48 PM > To: ?lker Aktuna (Koç.net) > Cc: samuel; serusers(a)iptel.org > Subject: Re: Authorizing IM requests > > Yes, I meant, that this will not work together. > > I don't know. Privacy-lists are something eyeBeam's internal or something standardized? > > Im-rules are SER internal. > > Vaclav > > On Fri, May 26, 2006 at 04:43:35PM +0300, ?lker Aktuna (Koç.net) wrote: > > Do you mean it won't work with privacy-lists ? > > What can I try ? > > > > Thanks, > > ilker > > > > -----Original Message----- > > From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] > > Sent: Friday, May 26, 2006 4:40 PM > > To: ?lker Aktuna (Koç.net) > > Cc: samuel; serusers(a)iptel.org > > Subject: Re: Authorizing IM requests > > > > EyeBeam won't use im-rules and SER won't use with privacy-lists. It something else. > > > > Vaclav > > > > On Fri, May 26, 2006 at 02:24:42PM +0300, ?lker Aktuna (Koç.net) wrote: > > > Hi Samuel, > > > > > > Now that presence is working I'm checking xcap possibilities. > > > I see that IM xcap authorization is not working. > > > > > > I don't know what to use in: > > > >if (authorize_message("im-rules.xml")){ > > > > > > My client (Eyebeam) does not use im-rules.xml , but it uses > > > privacy-lists.xml and that file is in privacy-lists folder. How > > > should I change the configuration line to use this file ? > > > > > > Regards, > > > ilker > > > > > > -----Original Message----- > > > From: samuel [mailto:samu60@gmail.com] > > > Sent: Tuesday, May 16, 2006 5:26 PM > > > To: Vaclav Kubart > > > Cc: ?lker Aktuna (Koç.net); serusers(a)iptel.org > > > Subject: Re: [Serusers] PA error sending notifies > > > > > > 2006/5/16, Vaclav Kubart <vaclav.kubart(a)iptel.org>: > > > > reply inline... > > > > > If you are using XCAP authentication for MESSAGEs, there's a > > > > > function called authorize_message that needs to have as > > > > > parameter the file name of the IM ruleset. > > > > > For user sam, in xcap-root/im-rules/users/sam/im-rules.xml > > > > > there are the rules for this function. The XML file is similar > > > > > to the presence-rules but has important differences (correct > > > > > me if I'm wrong, > > > > > Vaclav!!!): > > > > > *it only has a blacklist parameter (no whitelist!!) > > > > > > > > It doesn't depend on name of the rule (blacklist/whitelist/...) > > > > it depends on the action (block, ...). You can have as many > > > > rules as you want, but to explicitly enable something > > > > (whitelist) is needless because MESSSAGEs are allowed by default > > > > (at the end of the presence handbook I tried to describe > > > > im-rules the same way as presence-rules are described in their draft). > > > > > > > > > *the namespace is different (so be carefull in copy&paste from > > > > > the > > > > > presence-rules!!!) and, as Vaclav poitned out "proprietary" > > > > > from iptel. > > > > > > > > And the action element name differs: <im-handling> is used > > > > instead of <sub-handling>. > > > > > > > > > > Uops...I haven't noticed :P thanks! > > > > > > > Vaclav > > > > > > > > > > > > > > About the structure I have: x86 debian testing. Libraries > > > > > versions I don't know exactly but the ones in the testing > > > > > repository EXCEPT a library which I had to get for serweb from > > > > > the stable version...but it's not affecting SER part. > > > > > > > > > > Samuel. > > > > > 2006/5/16, ?lker Aktuna (Koç. net ) <ilkera(a)koc.net>: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >Hi, > > > > > > > > > > > >What did you mean by following: > > > > > > > > > > > >>Instead of > > > > > >>> > > > > > >>> if (authorize_message("http://localhost/xcap")) { > > > > > >> > > > > > >>there should be > > > > > >> > > > > > >>if (authorize_message("im-rules.xml")){ > > > > > > > > > > > >Btw, did you receive my email with following questions : > > > > > > > > > > > >>> I have the same problem with notification and other > > > > > >>> presence messages > > > > > >with you. > > > > > >>> Can you tell me which Linux distribution you are using Ser on ? > > > > > >>> Also please include version numbers for libraries that are > > > > > >>> required by > > > > > >Ser. > > > > > >>> > > > > > >>> I am trying to find similarities between yours and my ser server. > > > > > > > > > > > >Regards, > > > > > >ilker > > > > > > <http://387555.sigclick.mailinfo.com/sigclick/06090304/030C4A09/02014803/151…> _____________________________________________________________________________________________________________________________________________ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence. _____________________________________________________________________________________________________________________________________________

2 1

[Users] Dialog Module & MySQL
by Martin Klisch 31 May '06

31 May '06

Hi, is it planned to insert a MySQL-functionality in MySQL? Would be a nice feature. Bye, Martin

2 1

[Users] Can this work?: re. uac_auth cseq problem
by G.Jacobsen 31 May '06

31 May '06

I am still digging in this cseq uac problem which I need desperately to solve. The problem is that the uac_auth function can create credentials for the downstream proxy after being challenged with a 401 or 407 message - but the downstream proxy (UAS) refuses this proxy_auth message since openser does not increase the cseq number. Increasing the cseq number only downstream wouldnt solve the problem since any replies of the downstream proxy back to the originating UAC would have cseq numbers which are out of sync. I propose: In order to keep the cseq numbers in sync upstream and downstream one must generate challenges and proxy-auth responses on both legs of the route - and not only respond downstream as currently. So whenever openser receives from the downstream proxy a challenge it must forward this challenge the originating UAC (if necessary modify the message in such a way that the UAC is guaranteed to respond). This upstream challenge causes the originating UAC to increase the cseq. Naturally openser must also increase the cseq number downstream when generating its own proxy_auth repsonse to the downstream proxy. Whatever credentials UAC produces are discarted by openser. The scheme: 1. UAC issues invite which is routed by OS to the downstream proxy (UAS) - as usual. 2. UAS issues challenge 401 or 407 - as usual 3. OS captures challenge on_failure route - as envisaged by UAC module 4. this is new: a) OS relays the challenge upstream to UAC (would it be necessary to modify it before doing so ?) b) OS constructs with uac_auth function correct proxy_auth credentials for UAS, increases the cseq with some text manipulation function and replies to UAS. 5. UAC responds with (wrong) proxy_auth credentials via OS to UAS 6. OS discards the credential message it received from the UAC - to avoid that the message reaches UAS. 7. Invite successful or failure : UAS responds with further messages which are routed to UAC. Can this scheme work - or am I overlooking something here ? TIA Gerry

2 1

[Users] Re: Users Digest, Vol 12, Issue 83
by Padmaja RV 31 May '06

31 May '06

Hi all! can any one tell me what is the best method to run openser out of all the methods mentioned in the link below? http://openser.org/install.php Thank you, Regards, Padmaja ----- Original Message ----- From: <users-request(a)openser.org> To: <users(a)openser.org> Sent: Wednesday, May 31, 2006 12:09 PM Subject: Users Digest, Vol 12, Issue 83 > Send Users mailing list submissions to > users(a)openser.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://openser.org/cgi-bin/mailman/listinfo/users > or, via email, send a message with subject or body 'help' to > users-request(a)openser.org > > You can reach the person managing the list at > users-owner(a)openser.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Users digest..." > > > Today's Topics: > > 1. Can this work?: re. uac_auth cseq problem (G.Jacobsen) > 2. Call Hunting: use Avpop or LCR module ? (Rafael J. Risco G.V.) > 3. Re: Call Hunting: use Avpop or LCR module ? > (Daniel-Constantin Mierla) > 4. multiple domain best practices? (Mark Kent) > 5. Re: dispatcher module and rewritehost vs forward (Script Head) > 6. Dialog Module & MySQL (Martin Klisch) > 7. OpenSER and Redundancy (Martin Klisch) > 8. Re: how to run openser through monit daemon? (Jayesh Nambiar) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 30 May 2006 17:19:05 +0300 > From: "G.Jacobsen" <g_jacobsen(a)yahoo.co.uk> > Subject: [Users] Can this work?: re. uac_auth cseq problem > To: <users(a)openser.org> > Message-ID: <06ef01c683f8$3d8da960$6501a8c0@winmach1> > Content-Type: text/plain; charset="iso-8859-1" > > I am still digging in this cseq uac problem which I need desperately to > solve. > > The problem is that the uac_auth function can create credentials for the > downstream proxy after being challenged with a 401 or 407 message - but > the downstream proxy (UAS) refuses this proxy_auth message since openser > does not increase the cseq number. Increasing the cseq number only > downstream wouldnt solve the problem since any replies of the downstream > proxy back to the originating UAC would have cseq numbers which are out of > sync. > > I propose: In order to keep the cseq numbers in sync upstream and > downstream one must generate challenges and proxy-auth responses on both > legs of the route - and not only respond downstream as currently. > > So whenever openser receives from the downstream proxy a challenge it must > forward this challenge the originating UAC (if necessary modify the > message in such a way that the UAC is guaranteed to respond). This > upstream challenge causes the originating UAC to increase the cseq. > Naturally openser must also increase the cseq number downstream when > generating its own proxy_auth repsonse to the downstream proxy. Whatever > credentials UAC produces are discarted by openser. > > The scheme: > > 1. UAC issues invite which is routed by OS to the downstream proxy (UAS) - > as usual. > 2. UAS issues challenge 401 or 407 - as usual > 3. OS captures challenge on_failure route - as envisaged by UAC module > 4. this is new: > a) OS relays the challenge upstream to UAC (would it be necessary to > modify it before doing so ?) > b) OS constructs with uac_auth function correct proxy_auth credentials for > UAS, increases the cseq with some text manipulation function and replies > to UAS. > 5. UAC responds with (wrong) proxy_auth credentials via OS to UAS > 6. OS discards the credential message it received from the UAC - to avoid > that the message reaches UAS. > 7. Invite successful or failure : UAS responds with further messages which > are routed to UAC. > > Can this scheme work - or am I overlooking something here ? > > TIA > > Gerry >

1 0

[Users] OpenSER dimensioning. How many calls/sec can it set up?
by Script Head 31 May '06

31 May '06

Hello, I am deploying OpenSER to distribute calls for a number of Asterisk boxes. I believe there are some people on this list to have a similar setup. I'd like to know what kind of hardware do you guys run OpenSER on and how many calls per second can you set up with your specs. I am looking to set up about 30-40 calls per second so I was wondering what kind of hardware I'd need. ScriptHead

9 17

[Users] dispatcher module and rewritehost vs forward
by Script Head 31 May '06

31 May '06

I have the following in my config, which works... now if I comment forward and comment out rewritehost I get errors. Am I not using the correct syntax? route[5] { # ----------------------------------------------------------------- # PSTN Handler # ----------------------------------------------------------------- t_on_reply("1"); # do load balancing ds_select_dst("1","4"); sl_send_reply("100","Trying"); #rewritehost(uri:host); forward(uri:host,uri:port); route(4); route(1); }

2 3

Re: [Serusers] Two PSTN gateway providers needs different prefix
by Ryan Pagquil 31 May '06

31 May '06

Hi Andrey, I want SER the one to append the prefix on the Request URI. I think this fits when the user appends a prefix... Any suggestion? Thanks, Ryan At 05:22 PM 5/26/2006, Andrey Kouprianov wrote: >how about this... dont use # key. just append 3333 or 4444 to the number, i.e. > >GW1 ---> 3333<phone number> >GW2 ---> 4444<phone number> > > >if(uri=~"^sip:3333.*") { > strip(4); #if you need to get rid of first 4 >digits (i.e. "3333") > t_relay_to_udp("gw1.ip.address", "gw1-port") ; >} >else if(uri=~"^sip:4444.*") { > strip(4); #if you need to get rid of first 4 >digits (i.e. "4444") > t_relay_to_udp("GW2.ip.address", "GW2-port"); >}; > > >Hope that works out for you. > > >On 5/26/06, Ryan Pagquil <rpagquil(a)philonline.com> wrote: >>Hi, >> Anyone has any idea on how to do this? >> >>Please help.... >> >>Thanks, >>Ryan >> >> >> >>At 11:15 AM 5/25/2006, Ryan Pagquil wrote: >> >Hi SER users, >> > >> > I have a problem. We have two PSTN gateway providers and >> > both of them needs different prefixes when sending request to >> their gateway. >> > >> > For example: >> > GW1 ---> 3333#<phone number> >> > GW2 ---> 4444#<phone number> >> > >> >Now I'll be using these two provider with LCR, but I don't know how >> >will I accomplish their requirements on their prefixes. Could you >> >give me any idea about this scenario? Also how can I make LCR to >> >failover with these gateways? >> > >> >Please help.... >> > >> >Thanks in advance, >> >Ryan Pagquil >> > >> > >> > >> >_______________________________________________ >> >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

2 4

[Users] new MediaProxy release 1.7.2
by Adrian Georgescu 31 May '06

31 May '06

Hello, There is a new MediaProxy release available. The change log is available at http://mediaproxy.ag-projects.com/Changelog. Beside bug fixes a new accounting features has been introduced. To upgrade go to http://mediaproxy.ag-projects.com/ or download the software directly from: http://mediaproxy.ag-projects.com/mediaproxy-1.7.2.tar.gz Kind regards, Adrian Georgescu

3 3

Jump to page:

2025

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