sr-users

sr-users@lists.kamailio.org

48 participants
37555 discussions

RE: [Serusers] Working ser.cfg with mySQL authentication
by m36828253-1＠imap.1and1.com 27 Apr '05

27 Apr '05

According to error log, you should have syntax error in here: fifo_db_url="mysql://ser:heslo@localhost/ser" loadmodule "/usr/local/lib/ser/modules/mysql.so" but these two lines looks good to me. Are you sure, ser -E is using this configuration file? why dont you try with -f switch, like ser -E -f /etc/ser/ser.cfg, assuming your ser configuration file located at /et/ser/ser.cfg. Thanks, Mohammad Here is the start of the ser.cfg that shows errors: dns=no rev_dns=no fifo="/tmp/ser_fifo" fifo_db_url="mysql://ser:heslo@localhost/ser" 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" modparam("auth_db|usrloc", "db_url", "mysql://ser:heslo@localhost/ser") modparam("auth_db", "calculate_ha1", 1) modparam("auth_db", "password_column", "password") modparam("usrloc", "db_mode", 2) modparam("rr", "enable_full_lr", 1) route { # ----------------------------------------------------------------- # Sanity Check Section # ----------------------------------------------------------------- # ser -E 0(50633) parse error (5,1-12): syntax error 0(50633) parse error (5,12-13): unknown config variable 0(50633) parse error (7,1-11): ERROR: bad config file (3 errors) -----Original Message----- From: m36828253-1(a)imap.1and1.com [mailto:m36828253-1@imap.1and1.com] Sent: 27 April 2005 17:36 To: Graham Lewis; serusers(a)iptel.org Subject: RE: [Serusers] Working ser.cfg with mySQL authentication HI Graham, This log says, there have syntax error in your configuration file. Why don't you post first 10/15 lines of you configuration file. Thanks, Mohammad Original Message: ----------------- From: Graham Lewis graham.lewis(a)spitfire.co.uk Date: Wed, 27 Apr 2005 17:20:15 +0100 To: serusers(a)iptel.org Subject: [Serusers] Working ser.cfg with mySQL authentication Does anyone have a working example of ser.cfg with mySQL authentication they can share please. I have version 03a of the Onsip "SER Getting Started" documentation but the example given results is errors: # ser 0(49443) parse error (8,1-12): syntax error 0(49443) parse error (8,12-13): unknown config variable 0(49443) parse error (10,1-11): ERROR: bad config file (3 errors) # I think the Onsip doc. authors acknowledge this but have not updated the doc. yet. Graham Lewis _______________________________________________ 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/ . _______________________________________________ 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/ .

3 2

[Serusers] Web Front End to SER
by Dave 27 Apr '05

27 Apr '05

I am thinking of implementing a web frontend to ser (similar to serweb) for internal use and would appreciate some feedback regarding: 1) Is using the FIFO the best or the only way to manage SER? 2) From what I see, I'd need to access the database directly for me to be able to add users, assign groups or even being able to insert AVP's. But this would imply modifying my code each time the database schema were to change in the future. Is there any better way to handle this? Thanks in advance. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

[Serusers] Registering issues
by Mr Greg Plater 27 Apr '05

27 Apr '05

Hi I have Ser Express router on a Public ip address with no firewall between it and the internet. I have two hardware phones and two software clients connecting to the SER box. All 4 clients are on a private network with Nat connecting to a gateway on a public ip address in the same range as the Ser Unit. They register and I can make calls between these 4 clients. When I go to a remote location on a different ISP. I check the computer is on a public IP and no firewall is enabled. I place my SER details for registration into the client and it fails to register. I tried xlite with its debug screen and I see the send but note no response. When I use ethereal I capture the send but note no response packet received. I have tried a couple of port scans from the internet and I confirm port 5060 is open and listening. I have an Asterisk box on a public ip address also in the same range as the SER unit. It registers to SER and ser routes calls to it and bridges SIP - H323 out to a Gatekeeper and calls work within normal limits. What am I doing wrong? SERWEB is working and the website etc. all work from the internet no issue.

2 2

[Serusers] AS 5350 Default Dial-peer
by Razvan Nemesiu 27 Apr '05

27 Apr '05

Hi all, I know that all Cisco's have a default dial-peer that matches all calls.I believe that this is dial-peer 0.My main problem is that I want to close this dial-peer in order to stop matching all calls on my Cisco.Or I want to do something else: to create a dial-peer that has incoming called number a regexp string that matches all calls and to have on that dial-peer a call block rule.The problem is that I didn't succeed this thing.Do you have any ideas ? Thank you. -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

1 0

[Serusers] Working ser.cfg with mySQL authentication
by Graham Lewis 27 Apr '05

27 Apr '05

Does anyone have a working example of ser.cfg with mySQL authentication they can share please. I have version 03a of the Onsip "SER Getting Started" documentation but the example given results is errors: # ser 0(49443) parse error (8,1-12): syntax error 0(49443) parse error (8,12-13): unknown config variable 0(49443) parse error (10,1-11): ERROR: bad config file (3 errors) # I think the Onsip doc. authors acknowledge this but have not updated the doc. yet. Graham Lewis

2 1

RE: [Serusers] ACC into mysql
by Edgardo O. Gonzales II 27 Apr '05

27 Apr '05

Hi! Need for immediate assistance .. Im receiving this error message.. 0(17899) find_export: found <db_delete> in module mysql [/usr/local/ser/lib/ser/modules/mysql.so] 0(17899) find_export: found <db_update> in module mysql [/usr/local/ser/lib/ser/modules/mysql.so] 0(17899) connect_db(): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) 0(17899) db_init(): Error while trying to connect database 0(17899) mod_init(): Error while connecting database 0(17899) init_mod(): Error while initializing module usrloc what parameter should I use to to fix this problem. My db is up and running. chrome:/usr/local/ser/sbin# netstat -vatn Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN thanks, ed At 09:13 PM 4/26/2005, Matt Schulte wrote: >This particular config (I don't think?) won't log to a DB, additionally >you need to setflag(1); somewhere in your config. We tried to set on >"outbound" only originally and didn't have much luck so I set it near the >top. To log to (my)sql you will additionally need to set another flag and >setup similar mod params: > > >modparam("acc", "db_url", "mysql://ser:serro@blah.mysql.haha/dbname") ># Note flag 2, you will need to setflag(1); AND setflag(2); >modparam("acc", "db_flag", 2) >#Note this one logs all failed calls from the invite response, I find it >useful >modparam("acc", "failed_transactions", 1) ># In your route config use something like the following > ># This is pretty much near the top, while ACC won't log reg's or INFO >anyway, I just thought it'd be a little cleaner to have >... >if (!method == "REGISTER" || !method == "INFO" ) { > setflag(1); > setflag(2); >} >... > ># Doing the above ensure everything gets tagged including BYE's. A good >reason why your BYE's may not get ># tagged is possibly because record-route could be relaying the call >before the flag gets set, just a thought.. >-----Original Message----- >From: Edgardo O. Gonzales II [mailto:edgardo.g@pacific.net.ph] >Sent: Tuesday, April 26, 2005 1:29 AM >To: Kofi Obiri-Yeboah >Cc: serusers(a)lists.iptel.org >Subject: RE: [Serusers] ACC into mysql >Importance: High > > >Thanks again for your help .. Here's my running ser.cfg >Hope you can help me make my accounting work.. > >thanks, >ed > >================================================================ ># ----------- global configuration parameters ------------------------ > >#debug=3 >#fork=yes >#log_stderror=no > >#debug=7 >#fork=no >#log_stderror=yes > >check_via=no >dns=no >rev_dns=no >#port=5060 >#children=4 >fifo="/tmp/ser_fifo" > ># ------------------ module loading ---------------------------------- > >loadmodule "/usr/local/ser/lib/ser/modules/mysql.so" >loadmodule "/usr/local/ser/lib/ser/modules/sl.so" >loadmodule "/usr/local/ser/lib/ser/modules/tm.so" >loadmodule "/usr/local/ser/lib/ser/modules/rr.so" >loadmodule "/usr/local/ser/lib/ser/modules/maxfwd.so" >loadmodule "/usr/local/ser/lib/ser/modules/usrloc.so" >loadmodule "/usr/local/ser/lib/ser/modules/registrar.so" >loadmodule "/usr/local/ser/lib/ser/modules/auth.so" >loadmodule "/usr/local/ser/lib/ser/modules/auth_db.so" >loadmodule "/usr/local/ser/lib/ser/modules/acc.so" > ># ----------------- setting module-specific parameters --------------- > ># -- usrloc params -- > >modparam("usrloc", "db_mode", 1) >modparam("usrloc", "db_url","mysql://ser:heslo@localhost/ser") > ># -- auth params -- > >modparam("auth_db", "calculate_ha1", yes) >modparam("auth_db", "password_column", "password") > ># -- rr params -- > >modparam("rr", "enable_full_lr", 1) > ># -- acc params -- > >modparam("acc", "log_level", 1) >modparam("acc", "log_flag", 1) >modparam("acc", "log_missed_flag", 3) > ># ------------------------- request routing logic ------------------- > >alias=abc.com.ph > ># main routing logic > >route{ > if (!mf_process_maxfwd_header("10")) { > sl_send_reply("483","Too Many Hops"); > break; > }; > if ( msg:len > max_len ) { > sl_send_reply("513", "Message too big"); > break; > }; > > record_route(); > if (loose_route()) { > t_relay(); > break; > }; > > if (uri=~"abc.com.ph") { > if (method=="REGISTER") { > if (!www_authorize("abc.com.ph", "subscriber")) { > www_challenge("abc.com.ph", "0"); > break; > }; > > save("location"); > break; > }; > > lookup("aliases"); > > if (!lookup("location")) { > sl_send_reply("404", "Not Found"); > break; > }; > }; > if (!t_relay()) { > sl_reply_error(); > }; > >} > > > > >================================================================ >At 10:55 AM 4/26/2005, Kofi Obiri-Yeboah wrote: >>I am assuming your question is if the record_route() function is a >>parameter for accounting? If that was your question then the answer is >>no. Generally you invoke record_route() to ensure acl acceptance on a >>gateway (i.e. all calls through that gateway) >>-----Original Message----- >>From: Edgardo O. Gonzales II [ mailto:edgardo.g@pacific.net.ph] >>Sent: Monday, April 25, 2005 6:22 PM >>To: Kofi Obiri-Yeboah >>Cc: serusers(a)lists.iptel.org >>Subject: RE: [Serusers] ACC into mysql >> >>Hi Kofi! >>got it.. thanks for immediate feedback .. however my accounting is not >>working. >>any parameters to be added to make it work.. >>I have the following info already on my ser.cfg >>modparam("acc", "log_level", 1) >>modparam("acc", "log_flag", 1) >>modparam("acc", "log_missed_flag", 3) >> >>record_route(); -> its this a parameter for accounting >>thanks, >>ed >> >>At 08:32 AM 4/26/2005, Kofi Obiri-Yeboah wrote: >>>I think the correct modparam statement should read as follows: >>>modparam("acc", "db_url", "mysql://ser:heslo@localhost/ser") >>> >>>please note that "my" is required in front of sql >>> >>>and not: >>>modparam("acc", "db_url", "sql://ser:heslo@localhost/ser") >>> >>>-----Original Message----- >>>From: serusers-bounces(a)iptel.org [ mailto:serusers-bounces@lists.iptel.org]On >>>Behalf Of Edgardo O. Gonzales II >>>Sent: Monday, April 25, 2005 5:20 PM >>>To: serusers(a)lists.iptel.org >>>Subject: Re: [Serusers] ACC into mysql >>> >>>Hi all! >>>Im also receiving this error message. >>>Can somebody help us on how to make accounting work using mysql. >>>thanks, >>>ed >>>At 06:01 AM 4/26/2005, Leon Sun wrote: >>>>Hi, >>>>I am using 0.8.12 in Fedora 3. I tried to log account info into Mysql >>>>followed instruction from manual. I found, first, modparam("acc", >>>>"db_url", "sql://ser:heslo@localhost/ser") coudnlt work at all in >>>>ser.cfg. If I enabled in cfg file, it showed Starting ser: ERROR: bad >>>>config file (1 errors) >>>>If I disabled it, SER worked fine but I couldnt see any record in acc >>>>table. >>>>Would anyone suggest how to put call records into Mysql? >>>>Thank you. >>>> >>>># ----------- 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" >>>># ------------------ module loading ---------------------------------- >>>># Uncomment this if you want to use SQL database >>>>loadmodule "/usr/lib/ser/modules/mysql.so" >>>>loadmodule "/usr/lib/ser/modules/acc.so" >>>>loadmodule "/usr/lib/ser/modules/sl.so" >>>>loadmodule "/usr/lib/ser/modules/tm.so" >>>>loadmodule "/usr/lib/ser/modules/rr.so" >>>>loadmodule "/usr/lib/ser/modules/maxfwd.so" >>>>loadmodule "/usr/lib/ser/modules/usrloc.so" >>>>loadmodule "/usr/lib/ser/modules/registrar.so" >>>># Uncomment this if you want digest authentication >>>># mysql.so must be loaded ! >>>>loadmodule "/usr/lib/ser/modules/auth.so" >>>>loadmodule "/usr/lib/ser/modules/auth_db.so" >>>># ----------------- setting module-specific parameters --------------- >>>>#modparam("acc", "db_url", "sql://ser:heslo@localhost/ser") >>>># -- usrloc params -- >>>>#modparam("usrloc", "db_mode", 0) >>>># 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("acc","log_level",1) >>>>modparam("acc","log_flag",1) >>>># ------------------------- request routing logic ------------------- >>>># main routing logic >>>>route{ >>>> # initial sanity checks -- messages with >>>> # max_forwards==0, or excessively long requests >>>> if (!mf_process_maxfwd_header("10")) { >>>> sl_send_reply("483","Too Many Hops"); >>>> break; >>>> }; >>>> if ( msg:len > max_len ) { >>>> sl_send_reply("513", "Message too big"); >>>> break; >>>> }; >>>> # we record-route all messages -- to make sure that >>>> # subsequent messages will go through our proxy; that's >>>> # particularly good if upstream and downstream entities >>>> # use different transport protocol >>>> record_route(); >>>> # loose-route processing >>>> if (loose_route()) { >>>> if (method=="BYE") { >>>> setflag(1); >>>> setflag(2); >>>> } >>>> t_relay(); >>>> break; >>>> }; >>>> #labeled all transaction for accounting >>>> setflag(1); >>>> setflag(2); >>>> if (method=="CANCEL"){ >>>> t_relay(); >>>> }; >>>> # (in case, it does not work, use the following command >>>> # with proper names and addresses in it) >>>> if (uri==myself) { >>>> # This for PSTN destination >>>> if (uri=~"^sip:1") >>>> { rewritehost("10.10.10.10"); >>>> forward(10.10.10.10,5060); >>>> break; >>>> } >>>> if (method=="REGISTER") { >>>> # Uncomment this if you want to use digest authentication >>>> if (!www_authorize("sip.mycommunications.com", >>>> "subscriber")) { >>>> >>>>www_challenge("sip.mycommunications.com", "0"); >>>> break; >>>> }; >>>> save("location"); >>>> break; >>>> }; >>>> # native SIP destinations are handled using our USRLOC DB >>>> if (!lookup("location")) { >>>> sl_send_reply("404", "Not Found"); >>>> break; >>>> }; >>>> }; >>>> # 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(); >>>> }; >>>>} >>>>_______________________________________________ >>>>Serusers mailing list >>>>serusers(a)lists.iptel.org >>>>http://lists.iptel.org/mailman/listinfo/serusers

1 0

RE: [Serusers] Working ser.cfg with mySQL authentication
by Graham Lewis 27 Apr '05

27 Apr '05

Here is the start of the ser.cfg that shows errors: dns=no rev_dns=no fifo="/tmp/ser_fifo" fifo_db_url="mysql://ser:heslo@localhost/ser" 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" modparam("auth_db|usrloc", "db_url", "mysql://ser:heslo@localhost/ser") modparam("auth_db", "calculate_ha1", 1) modparam("auth_db", "password_column", "password") modparam("usrloc", "db_mode", 2) modparam("rr", "enable_full_lr", 1) route { # ----------------------------------------------------------------- # Sanity Check Section # ----------------------------------------------------------------- # ser -E 0(50633) parse error (5,1-12): syntax error 0(50633) parse error (5,12-13): unknown config variable 0(50633) parse error (7,1-11): ERROR: bad config file (3 errors) -----Original Message----- From: m36828253-1(a)imap.1and1.com [mailto:m36828253-1@imap.1and1.com] Sent: 27 April 2005 17:36 To: Graham Lewis; serusers(a)lists.iptel.org Subject: RE: [Serusers] Working ser.cfg with mySQL authentication HI Graham, This log says, there have syntax error in your configuration file. Why don't you post first 10/15 lines of you configuration file. Thanks, Mohammad Original Message: ----------------- From: Graham Lewis graham.lewis(a)spitfire.co.uk Date: Wed, 27 Apr 2005 17:20:15 +0100 To: serusers(a)lists.iptel.org Subject: [Serusers] Working ser.cfg with mySQL authentication Does anyone have a working example of ser.cfg with mySQL authentication they can share please. I have version 03a of the Onsip "SER Getting Started" documentation but the example given results is errors: # ser 0(49443) parse error (8,1-12): syntax error 0(49443) parse error (8,12-13): unknown config variable 0(49443) parse error (10,1-11): ERROR: bad config file (3 errors) # I think the Onsip doc. authors acknowledge this but have not updated the doc. yet. Graham Lewis _______________________________________________ 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/ .

1 0

RE: [Serusers] Working ser.cfg with mySQL authentication
by m36828253-1＠imap.1and1.com 27 Apr '05

27 Apr '05

HI Graham, This log says, there have syntax error in your configuration file. Why don't you post first 10/15 lines of you configuration file. Thanks, Mohammad Original Message: ----------------- From: Graham Lewis graham.lewis(a)spitfire.co.uk Date: Wed, 27 Apr 2005 17:20:15 +0100 To: serusers(a)iptel.org Subject: [Serusers] Working ser.cfg with mySQL authentication Does anyone have a working example of ser.cfg with mySQL authentication they can share please. I have version 03a of the Onsip "SER Getting Started" documentation but the example given results is errors: # ser 0(49443) parse error (8,1-12): syntax error 0(49443) parse error (8,12-13): unknown config variable 0(49443) parse error (10,1-11): ERROR: bad config file (3 errors) # I think the Onsip doc. authors acknowledge this but have not updated the doc. yet. Graham Lewis _______________________________________________ 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/ .

1 0

[Serusers] what is the best way of using asterisk as B2BUA
by Kamran Ahmad 27 Apr '05

27 Apr '05

hi list any person using ser and Asterisk as B2bUA. what is the best way of using asterisk as B2BUA. i can route calls to through asterisk its working but some time one UA tries to hangup the call and the other side is not able to receive Bye what could be the best way of using asterisk for monitering voice Thanks Kamran __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

[Serusers] gateways routing, based on prefix and blocking calls
by Iqbal 27 Apr '05

27 Apr '05

Hi I am trying to find an easy way to route calls, based on prefix, and also to block others. I have prefixes for my calls routes bound to gateways using lcr Now using the grp table I have 3 types of user Type A = can call Uk (landline)... setflag(50) Type B = can call UK landline AND mobile... setflag(51) Type C = does what he wants... setflag(52) Obviously over time this will get even more complicated, hence the reason for finding a simple way :-) in ser.cfg if the user is of Type A, he should only be able to call 00441X and 00442X if type B he should be able to call 0044X So in ser I am testing something like this if (uri=~"^sip:00.*@*") { if (uri=~"^sip:0044[1-2].*@*") { if isflagset(50) { call route } } if (uri=~"^sip:0044.*@*") { if isflagset(51) { call route } } } Now this is fine for a few different type of customer, and prefixes, but when I have say Type 4 who can call 0091, 0092, 0094, 00880 for example, then its starts to add up in tersm of pain :-) Is there a way of linking customer to package (I guess via grp) and then grp to prefix ---lcr ) Iqbal

1 0

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