- sr-users - kamailio.org

[Serusers] CDRz?
by Parminder.Nayyar＠relianceada.com 23 Jul '07

23 Jul '07

Hi Can anyone tell me which module to explore , if i want to check about CDRz and billing?? Please help..... Parminder Nayyar

2 1

[OpenSER-Users] bug ? remote mysql server in openser-devel
by Julien REVERET 23 Jul '07

23 Jul '07

Hi, I'm currently using openser-devel release 2497 and I'm facing what I think is a bug. I'm using a remote mysql server. My openser.cfg file contains the following lines : loadmodule "/usr/local/lib/openser/modules/mysql.so" loadmodule "/usr/local/lib/openser/modules/usrloc.so" loadmodule "/usr/local/lib/openser/modules/auth.so" loadmodule "/usr/local/lib/openser/modules/auth_db.so" loadmodule "/usr/local/lib/openser/modules/uri_db.so" modparam("usrloc", "db_mode", 2) modparam("auth_db", "calculate_ha1", 1) modparam("auth_db", "password_column", "password") modparam("auth_db", "user_column", "username") modparam("auth_db", "domain_column", "domain") modparam("usrloc|auth_db","db_url","mysql://foo:bar@192.168.1.62:3306/openser") When starting openser, I get these lines in the logs : openser[30331]: INFO: statistics manager successfully initialized openser[30331]: StateLess module - initializing openser[30331]: TM - initializing... openser[30331]: maxfwd:initializing openser[30331]: INFO:ul_init_locks: locks array size 512 openser[30331]: TextOPS - initializing openser[30331]: new_connection: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) openser[30331]: ERROR: uridb_db_ver: unable to open database connection openser[30331]: ERROR: uri_db:mod_init(): Error while querying table version openser[30331]: init_mod(): Error while initializing module uri_db openser[30331]: INFO:mi_fifo:mi_destroy: process hasn't been created -> nothing to kill I tried to launch a local mysql and as far as I can see, openser only connects to the local server, it doesn't do any requests. So is there a bug or am I missing something ? -- Julien REVERET OSIATIS - LIFO https://www.lifo-osiatis.com

2 1

[Users] 473 Filtered destination?
by Tobias Lindgren 23 Jul '07

23 Jul '07

Hi, recently moved from SER > OpenSER 1.2.0, but after some time when the server is running OpenSER starts to respond with: "SIP/2.0 473 Filtered destination (473/TM)." to my INVITEs. I don't have any blacklists/accesslist configured (the config is from SER which doesn't support that), why am I seeing this problem? Br, /Tobias

7 11

[Serusers] SER 0.9.6 and xlog + syslog
by Cesc Santa 23 Jul '07

23 Jul '07

Hi, I just came across a strange "feature" in xlog for ser 0.9.6. When I send output to stderr, no problem ... but using the same config and sending to syslog, some xlog output gets trunkated :O I have these lines in my config: xlog( "L_NOTICE", "============================================================\n"); xlog( "L_NOTICE", "==[%Tf]\n" ); xlog( "L_NOTICE", "==[%is ## %pp]\n==\n" ); #Print the whole received SIP message buffer ... xlog( "L_NOTICE", "\n%mb\n\n"); And this is what I get in /var/log/messages: Jul 23 01:45:09 FC3lara /usr/local/sbin/cafesRouter[21957]: ===================================== Jul 23 01:45:09 ser[21957]: ==[Mon Jul 23 01:45:09 2007] Jul 23 01:45:09 ser[21957]: ==[192.168.200.141 ## 21957] == ntent-Length: 0ne/1.65.377a (SJ Labs)000000;rport2.0 As you can see, the part of xlog which prints the sip message gets truncated ... it only prints the last part (ntent-Length .... ). Ideas? Cesc

1 1

[OpenSER-Users] Dispatcher Module
by NicklasZ 23 Jul '07

23 Jul '07

Hi, ok now i have openser and asterisk running (at the moment i can only connect to the database with asterisk if it is on the local client but hope i can fix it soon, if someone had a suggestion i will be glad [ res_odbc.c:559 odbc_obj_connect: res_odbc: Error SQLConnect=-1 errno=1044 [unixODBC][MySQL][ODBC 3.51 Driver]Access denied for user 'asterisk'@'%' to database 'asterisk' ] ) What i want to do is to use openSER as Loadbalancer http://wow.real94.de/openSER.jpg As soon as i try load the dispatcher module im not able to start openser. How do i have to use the dispachter module?

2 1

[OpenSER-Users] Possible Problem in code mysql/dbase.c, MySQL issue
by Schumann Sebastian 23 Jul '07

23 Jul '07

Hi all, I got problems after compiling OpenSER Rev. 2492. Including Module mysql, after compiling and executing openser, there occurs an error message about an undefined mysql method. In modules/mysql/dbase.c, there are the methods line 682 db_mysql_print_values() and on line 692 db_mysql_print_set. I think they have been replaces to db/db_ut.c as db_print_values() and db_print_set respectively. Also, these new methods have a parameter val2str as last parameter. Can this be something that has been forgotten to change in Rev. 2353? If I change the functions according db_ut.h, openser runs! Regards from hot Bratislava Sebastian Sebastian Schumann Diploma Student Architecture and Design Department Slovak Telekom, a. s. T-Com, Operations Unit Production and Service Division Innovations and Enterprise Solution Subunit Address: Namestie Slobody 6, 817 62 Bratislava, Slovakia Office: Room 449, Jarabinkova 1, 821 09 Bratislava, Slovakia +421 2 588 13332 (tel) +421 910 643010 (mobile) +49 175 1925928 (mobile) sebastian.schumann(a)t-com.sk http://www.t-com.sk <http://www.t-com.sk/>

2 3

[Serusers] SER as PRESENCE SERVER
by Cyprian Clement 23 Jul '07

23 Jul '07

Hi everyone, Just a quick question, can SER be used as PRESENCE SERVER ?. If so, does anyone have an example script of how SER can be configured as Presence Server?. Many thanks in advance. Regards, Cyp. ------ ___________________________________________________________ Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for your free account today http://uk.rd.yahoo.com/evt=44106/*http://uk.docs.yahoo.com/mail/winter07.ht…

2 1

Re: [Serusers] ser and asterisk
by Cyprian Clement 23 Jul '07

23 Jul '07

Hello Ram, I see the link showing an integration between OPENSER and ASTERISKS. Does this apply to SER and ASTERISKS or it's only with OPENSER? Your clarification will be much appreciated. Regards, Cyp. --------- ----- Original Message ---- From: ram <talk2ram(a)gmail.com> To: Kirk McCalla <kirk.mccalla(a)gmail.com> Cc: serusers(a)lists.iptel.org Sent: Monday, 23 July, 2007 6:00:20 AM Subject: Re: [Serusers] ser and asterisk On 7/23/07, Kirk McCalla <kirk.mccalla(a)gmail.com> wrote: Does any one have any documentation to be able to integrate ser and asterisk. http://www.openser.org/dokuwiki/doku.php/asterisk:realtime-integration ram ___________________________________________________________ For email that puts you in control, choose Yahoo! Mail. http://uk.docs.yahoo.com/mail/addressguard2.html

1 0

[Serusers] ser and asterisk
by Kirk McCalla 23 Jul '07

23 Jul '07

Does any one have any documentation to be able to integrate ser and asterisk.

2 1

[OpenSER-Users] OpenSer and Asterisk-b2bua
by Ha Noi Telecommunications 23 Jul '07

23 Jul '07

Hi! I am using OpenSer with two Asterisk-b2bua Sip client<--------->OpenSer<--------------------->Asterisk-b2bua<------->PSTN | | <----------------------------->Asterisk-b2bua<----------->PSTN In OpenSer configure file I am using ds_select_dst("2", "4"); to perform load sharing the calls to PSTN. But when Sip client hang up first, I don't konw how to make OpenSer forward the Bye message from Sip client to correct Asterisk-b2bua to hang up the call at PSTN side. Can any body can help me. Thanks and best regards

2 2

[Serusers] replace username depend on r-uri
by Meidiana Ten 21 Jul '07

21 Jul '07

Hi there, I'd like to know how to replace username depend on r-uri. I want to use it to change my mailbox url dynamically. Thanx Regards, Meidiana ____________________________________________________________________________________ Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. http://mobile.yahoo.com/go?refer=1GNXIC

1 0

[OpenSER-Users] OpenSer as Loadbalancer for Asterisk
by NicklasZ 21 Jul '07

21 Jul '07

Hi, is there a howto out there how to use OpenSer as a Loadbalancer for Asterisk. It's part of an exercise of an university course. It should be a LAN SIP envirenment only. 1 Asterisk got a fictitious CPU load of 75% by SIP calls and it should be balanced on 2. How does it work? I think the SIP clients has to register at the openSER. Am i right? What i've found is http://www.voip-info.org/wiki/view/Realtime+Integration+Of+Asterisk+With+Op… http://www.openser.org/dokuwiki/doku.php/asterisk:load-balancing-and-ha But which one did i need and what else do i have to do? Thanks

2 2

[OpenSER-Users] Presence Module no response for SUBSCRIBE request
by KevinKinnan 20 Jul '07

20 Jul '07

Thanks, Anca.If I change requestURI as "sip:alice@148.88.232.101", the PUBLISH request wont be sent to the Presence server. What should I do? _________________________________________________________________ 使用下一代的 MSN Messenger。 http://imagine-msn.com/messenger/launch80/default.aspx?locale=zh-cn&source=…

1 0

[OpenSER-Users] Presence Module no response for SUBSCRIBE request
by KevinKinnan 20 Jul '07

20 Jul '07

My Presence module works fine with PUBLISH request, but not with SUBSCRIBE request. The trace shows as follows, the requestURI is the IP address of Presence module, and the request directly sends to presence server, I think there must be something wrong with the structure of SUBSCRIBE request. any one can point what is wrong will be helpful , Thank you!---------------Sending Request---------------PUBLISH sip:148.88.233.209:5065 SIP/2.0Call-ID: ef68e3acb55c2a4c791b1e31f7362b6f(a)148.88.232.101CSeq: 849 PUBLISHFrom: <sip:alice@148.88.232.101:5061>To: <sip:alice@148.88.232.101:5061>Via: SIP/2.0/UDP 148.88.232.101:5061;branch=z9hG4bK19953Max-Forwards: 70Expires: 3600Event: presenceContact: <sip:alice@148.88.232.101:5061>Content-Type: application/cpim-pidf+xmlContent-Length: 220<?xml version="1.0" encoding="UTF-8" standalone="no"?><presence xmlns="urn:ietf:params:xml:ns:pidf" entity="pres:alice@open-ims.test"><tuple id="sip-client(java)"><status><basic>online</basic></status></tuple></presence>---------------Received Response---------------SIP/2.0 200 OKCall-ID: ef68e3acb55c2a4c791b1e31f7362b6f(a)148.88.232.101CSeq: 849 PUBLISHFrom: <sip:alice@148.88.232.101:5061>To: <sip:alice@148.88.232.101:5061>;tag=762c87025812f63000552d0e54932ab8.31c6Via: SIP/2.0/UDP 148.88.232.101:5061;branch=z9hg4bk19953Expires: 3590SIP-ETag: a.1184861600.3810.10Server: OpenSER (1.2.0-notls (i386/linux))Content-Length: 0---------------Sending Request---------------SUBSCRIBE sip:148.88.233.209:5065 SIP/2.0Call-ID: 5c280b2299c2834b7705dece8497ec2f(a)148.88.232.101CSeq: 20 SUBSCRIBEFrom: <sip:alice@148.88.232.101>To: <sip:bob@148.88.232.101>Via: SIP/2.0/UDP 148.88.232.101:5061;branch=z9hG4bK97556Max-Forwards: 70Expires: 3600Event: presenceContact: <sip:alice@148.88.232.101:5061>Content-Length: 0...... _________________________________________________________________ 探索 Windows Vista 的世界 http://search.live.com/results.aspx?q=windows+vista&mkt=zh-cn&FORM=LIVSOP

2 2

[OpenSER-Users] Redirect to Trunk IP SIP/PSTN gateway + billing
by Marc LEURENT 20 Jul '07

20 Jul '07

Does anyone succeed in redirecting SIP calls like [0-9]*(a)sip.test.com to a SIP/PSTN gateway provider without using asterisk? Thanks

4 4

[OpenSER-Users] Bug or bad config?
by Antonio Reale 20 Jul '07

20 Jul '07

Hi all, Im trying to set up conditional call forwarding using an openser.cfg created with sip:wizard on sipwise.com. On ring-timeout before response 408 I receive a "500 I'm terribly sorry..." message. ngrep output: ---------------------------------------------------------------------- U proxyip:5060 -> clientip:1025 SIP/2.0 500 I'm terribly sorry, server error occurred (1/SL). Via: SIP/2.0/UDP clientip;branch=z9hG4bK0a0a2d5600000054469e38f600007d4800000065;rport=1025. From: "unknown" <sip:9991@proxyip>;tag=6c5264b687a. To: <sip:8888@proxyip>;tag=89c3d91cf34558b4440b4dea7bd37a3b.9860. Call-ID: EDC29EF258D44A69818BF2960CF191360x0a0a2d56. CSeq: 2 INVITE. Server: OpenSer (1.1.1-notls (i386/linux)). Content-Length: 0. . # U proxyip:5060 -> clientip:1025 SIP/2.0 408 Request Timeout. Via: SIP/2.0/UDP clientip;branch=z9hG4bK0a0a2d5600000054469e38f600007d4800000065;rport=1025. From: "unknown" <sip:9991@proxyip>;tag=6c5264b687a. To: <sip:8888@proxyip>;tag=1da87856efbb12e9687f30fa08f307cb-9860. Call-ID: EDC29EF258D44A69818BF2960CF191360x0a0a2d56. CSeq: 2 INVITE. Server: OpenSer (1.1.1-notls (i386/linux)). Content-Length: 0. ------------------------------------------------------------------------- With tail -f /var/log/message I see (output lines are cutted): ------------------------------------------------------------------------- Jul 18 18:55:22 proxy /usr/sbin/openser[5615]: NAT-Reply - S=180 D=Ringing F=sip.... Jul 18 18:55:26 proxy /usr/sbin/openser[5620]: Redirect from UAC intercepted - M=INVITE RURI=sip:.... Jul 18 18:55:26 proxy /usr/sbin/openser[5620]: Clear callee preferences - M=INVITE RURI=sip:.... Jul 18 18:55:26 proxy /usr/sbin/openser[5620]: is_uri_host_local(): Branch is missing, error in script Jul 18 18:55:26 proxy /usr/sbin/openser[5620]: Call to foreign domain - M=INVITE RURI=sip:.... Jul 18 18:55:26 proxy /usr/sbin/openser[5620]: Request leaving server, D-URI='' - M=INVITE RURI=sip:.... Jul 18 18:55:26 proxy /usr/sbin/openser[5620]: ERROR:tm:t_forward_nonack: no branch for forwarding Jul 18 18:55:26 proxy /usr/sbin/openser[5620]: ERROR:tm:w_t_relay: t_forward_nonack failed -------------------------------------------------------------------------- How can I solve this problem? Attached the routing section of openser.cfg (full file was too big for mailing list). Thanks in advance. Best regards. -- Antonio

2 2

[Serusers] client register
by raid＠gmx.net 20 Jul '07

20 Jul '07

hi my scenario. (ser_0.8.14) client with dynamic ip register to ser, the client change the dynamic ip end register to ser. ser has now two entries for this client and no call comes through. if I delete the first register(old) the call comes through. is there a possibility the older entry to delete if the same client new register thx raid -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail

1 0

[OpenSER-Users] a problem with IPV6 and NAT
by Lee Jacky 20 Jul '07

20 Jul '07

Hi,everyone. Now I am using mediaproxy to solve NAT,and rtpproxy to solve IPV6. When they are configured separately, each can work correctly. However, if I configure them together in one openser.cfg, they will conflict with each other. Have anyone solve IPV6 and NAT together? Any advice will be appreciated! ___________________________________________________________ 抢注雅虎免费邮箱3.5G容量，20M附件！ http://cn.mail.yahoo.com

2 1

[OpenSER-Users] SipSpy Usage
by Jon Steer 20 Jul '07

20 Jul '07

I have gotten sipSpy setup on two systems, but I am not seeing any traffic. I know that traffic is happening and that if I use ngrep I can see traffic correctly. The only thing I can think of is that my regexp expression isn't right. My password file is auser:badpass:admin:.*@foo.local This should get me all messages with sip:baz@foo.local, but I'm not seeing anything. Should I just see INVITE sequences? Should I see registrations? Should I see presence? What am I missing? thanks, jon

4 5

[Serusers] choosing gateway for each country code
by Nhadie Ramos 20 Jul '07

20 Jul '07

Hi All, Is there a way to choose which gateway i send the traffic to depending on the dialed number? e.g if 001XXXXXXXXX route to 10.10.10.1 and if 0065XXXXXXXXXX route it to 10.10.10.2 is that possible? thank you regards, nhadie

2 1

[OpenSER-Users] Presence without registration
by Serhat Demir 19 Jul '07

19 Jul '07

Dear OpenSER users, I want to use OpenSER as a Presence Server. Let me first describe my network; I am responsible from the network of a Internet Telephony Service Company, and our customers generally use SIP devices, sometimes softphones. What I want to do is also let my customers IM each other. I have a SIP Proxy as SCB and all my customers are registered there. What I am trying to do is to redirect incoming SUBSCRIBE and PUBLISH packets coming to my SIP Proxy to OpenSER and when OpenSER sends the NOTIFY packet back to SIP Proxy, redirect it to the customer. I still could not manage to get the NOTIFY packet from OpenSER but its not the main point here. Main point is, will presence work with this scenario? Does OpenSER needs the clients to be registered to itself to handle SUBSCRIBE packets? Or its just enough for OpenSER to recieve SUBSCRIBE packets and response with NOTIFY packets? I will appreciate your ideas, thoughts and advices. Thanks in advance. -S

1 0

[OpenSER-Users] Can Presence module work alone?
by KevinKinnan 19 Jul '07

19 Jul '07

I build Openser Presence module and it works well. The cfg file is the same content as shown on this website "http://uctimsclient.berlios.de/openser.cfg". I change the listen IP address, module path, and comment `loadmodule "registrar.so"`(coz I just want it work as a Presence AS). The problem is, I want to implement Presence by using a sip client(designed by Jain-1.2-NIST) to talk with Presence Module. As I said, the Presence AS doesn't have registrar module. It just works as Presence server with a open port 5065. If the sip client directly sends PUBLISH or SUBSCRIBE request(I'll deal with the structure of request) to the Presence AS, does the server response to the sip client with NOTIFY?Any hint would be helpful!!!CheersKevin, _________________________________________________________________ 中国十大热门旅游景点 http://search.msn.com/results.aspx?q=%E4%B8%AD%E5%9B%BD%E5%8D%81%E5%A4%A7%E…

1 0

[Serusers] conjunction from ser to a sip provider
by julia heller 19 Jul '07

19 Jul '07

Hi at all, i'll hope anybody can tell me, how i can make a conjunction from ser to a sip provider? What changes must be made in the ser.cfg? Kind regards, Julia -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail

1 0

[Serusers] Blocking the caller ID
by Jai Rangi 19 Jul '07

19 Jul '07

Hello All, Does any one know what module can be used to block calls from some particular phone numbers. I want to store those numbers in the database. I am looking for these possibilities, 1. We want to block all the calls from some phone number 666 777 8888 2. One of the user agent wants to block the call from some phone number 444 444 4444. Thank you, -Jai

3 2

[Serusers] ser noanswer call forward
by Arun Kumar 19 Jul '07

19 Jul '07

HI I've configured my ser to call forward on no answer(30 sec.) to PSTN. SIP User A -> SER -> SIP User B if User B don't answer within 30 sec. ser will goto failure_route and in that Im setting flag 27 and calling my pstn route to place call to PSTN by getting his pstn number from avp database. it works fine no problem. but instead of SIP User if any user calls my incoming number and then dial other users SIP ID call is coming but no-answer feature is not working for this user. any idea. if you need any other info please let me know. thanks arun

2 1

[OpenSER-Users] class 4 softswitch with openser
by Ashish Barot 19 Jul '07

19 Jul '07

Respected All, i am newbie to join this group. i want to know about the class 4 soft switch functionality with openser. can anybody guide me that, can openser [ with combination of some other tools] work as softswitch. which has all basic function of class 4. As for internet sources i come to know that, open ser had capacity of handling more than 1000 concurrent calls per second. having doubt on it. but now want to implement so my doubt get clear. pl any small help or suggestion will be thankful to me. Best Regards, Ashi.

2 1

[OpenSER-Users] replace domain of RURI with result of DNS lookup
by Tim 19 Jul '07

19 Jul '07

Hello, Does anyone know how to replace the domain portion of the Request-URI with the result of a DNS lookup provided the domain comes into openser as a FQDN? The default behaviour has the FQDN resolved in DNS and the Reqest relayed to the resolved destination however the domain portion of the R-URI remains as a FQDN. Thanks, Tim

2 1

[OpenSER-Users] NEW FEATURE: dialog enhancements
by Bogdan-Andrei Iancu 19 Jul '07

19 Jul '07

Hi everybody, For people not following the SVN commit logs, here is a brief update related to the latest enhancements of the dialog module: 1) DB persistence Thanks to Ancuta (ancuta(a)voice-system.ro), the dialog module saves the dialog related information into DB (in realtime or delayed), so the dialog processing will perfectly survive across server restart. Also allows an easy integration (via DB) with other apps that need the dialog information. 2) Complete dialog information Again, thanks to Ancuta, the dialog module store not only the information required to match the dialog, but all the additional information required to build a within the dialog requests. The following fields were added (for both caller and callee side): contact, cseq number, route set, local socket. No all the information is in place if you want to generate a sequential request for the dialog 3) Speed-ups Thanks to Tavis Paquette <tavis(a)galaxytelecom.net> and Peter Baer <pbaer(a)galaxytelecom.net> a faster dialog matching was implemented for the case where no dialog ID was used. Also, the dependency of the ftag RR parameter eas removed, so you do not have to force this RR parameter for the dialog module to work. 4) TODO: generating BYEs This is still on the TODO list, but it's about having the possibility to terminate a dialog (sending BYEs in both directions) via the dialog module. As there were a lot of new and massive changes, any help in testing will be welcome ;) Regards, Bogdan

2 2

[OpenSER-Users] Openser Process performance
by Sergio Gutierrez 19 Jul '07

19 Jul '07

Hi everybody. I would like to know what is the adjustment you recommend for the number of process and Shared memory segment of Openser. Thanks in advance for your attention. Kind Regards. Sergio Gutiérrez EPM Telecomunicaciones.

2 1

[OpenSER-Users] Table Version Error
by Gerson A. Matiolli 19 Jul '07

19 Jul '07

Hi, I am with the following problem, when start openser happens the following error: Jul 18 16:58:48 localhost openser: init_tcp: using epoll_lt as the io watch method (auto detected) Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: INFO: statistics manager successfully initialized Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: StateLess module - initializing Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: TM - initializing... Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: Maxfwd module- initializing Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: INFO:ul_init_locks: locks array size 512 Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: TextOPS - initializing Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: AUTH module - initializing Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: AUTH_DB module - initializing Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: ACC - initializing Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: EXEC - initializing Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: MSILO:mod_init: Wrong version v4 for table <silo>, need v5 Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: init_mod(): Error while initializing module msilo Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: INFO:mi_fifo:mi_destroy:memory for the child's mi_fifo_pid was not allocated -> nothing to destroyJul 18 16:58:48 localhost openser: init_tcp: using epoll_lt as the io watch method (auto detected) Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: INFO: statistics manager successfully initialized Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: StateLess module - initializing Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: TM - initializing... Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: Maxfwd module- initializing Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: INFO:ul_init_locks: locks array size 512 Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: TextOPS - initializing Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: AUTH module - initializing Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: AUTH_DB module - initializing Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: ACC - initializing Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: EXEC - initializing Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: MSILO:mod_init: Wrong version v4 for table <silo>, need v5 Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: init_mod(): Error while initializing module msilo Jul 18 16:58:48 localhost /usr/local/sbin/openser[25741]: INFO:mi_fifo:mi_destroy:memory for the child's mi_fifo_pid was not allocated -> nothing to destroy Somebody can help? Thanks

2 3

[Serusers] Openser+freeradius+mysql
by zze-WU Yin RD-MAPS-LAN 18 Jul '07

18 Jul '07

Hi, I have installed openser-1.2.1-notls, freeradius-1.1.6, mysql-0.5.41, radiusclient-ng-0.5.2 successfully. Openser works well with no modification of the 'openser.cfg' and I can register a SIP telephone. The Openser reponses always 200 ok! And freeradius works well with the databases of mysql. When I make a 'radtest', I can received a 'access-request'. But when I need to use openser+freeradius+mysql. It seems that the authentification doesn't work. I think that may be the problem to register a user in the mysql tables. I just want a authentification with username and password. But I can not find a clear sample about that. Can you help me? Thank you very much!!! And this is information I received: [root@localhost openser-1.2.1-notls]# rad_recv: Access-Request packet from host 127.0.0.1:33097, id=136, length=225 User-Name = "1000(a)opensersip.test.machine" Digest-Attributes = 0x0a0631303030 Digest-Attributes = 0x01196f70656e7365727369702e746573742e6d616368696e65 Digest-Attributes = 0x022a343639653234323065313462316439323164623762393938343536346361666665 37396332663633 Digest-Attributes = 0x04187369703a3137322e32302e31342e3231343a35303630 Digest-Attributes = 0x030a5245474953544552 Digest-Response = "49c0b2b33010b2681d8b610a763387e7" Service-Type = Sip-Session Sip-Uri-User = "1000" NAS-Port = 5060 NAS-IP-Address = 127.0.0.1 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 3 modcall[authorize]: module "preprocess" returns ok for request 3 modcall[authorize]: module "chap" returns noop for request 3 modcall[authorize]: module "mschap" returns noop for request 3 rlm_digest: Adding Auth-Type = DIGEST modcall[authorize]: module "digest" returns ok for request 3 rlm_realm: Looking up realm "opensersip.test.machine" for User-Name = "1000(a)opensersip.test.machine" rlm_realm: No such realm "opensersip.test.machine" modcall[authorize]: module "suffix" returns noop for request 3 rlm_eap: No EAP-Message, not doing EAP modcall[authorize]: module "eap" returns noop for request 3 radius_xlat: '1000(a)opensersip.test.machine' rlm_sql (sql): sql_set_user escaped user --> '1000(a)opensersip.test.machine' radius_xlat: 'SELECT id, UserName, Attribute, Value, op FROM radcheck WHERE Username = '1000(a)opensersip.test.machine' ORDER BY id' rlm_sql (sql): Reserving sql socket id: 1 rlm_sql (sql): User 1000(a)opensersip.test.machine not found in radcheck radius_xlat: 'SELECT radgroupcheck.id,radgroupcheck.GroupName,radgroupcheck.Attribute,radgrou pcheck.Value,radgroupcheck.op FROM radgroupcheck,usergroup WHERE usergroup.Username = '1000(a)opensersip.test.machine' AND usergroup.GroupName = radgroupcheck.GroupName ORDER BY radgroupcheck.id' radius_xlat: 'SELECT radgroupreply.id,radgroupreply.GroupName,radgroupreply.Attribute,radgrou preply.Value,radgroupreply.op FROM radgroupreply,usergroup WHERE usergroup.Username = '1000(a)opensersip.test.machine' AND usergroup.GroupName = radgroupreply.GroupName ORDER BY radgroupreply.id' rlm_sql (sql): User 1000(a)opensersip.test.machine not found in radgroupcheck rlm_sql (sql): Released sql socket id: 1 rlm_sql (sql): User not found modcall[authorize]: module "sql" returns notfound for request 3 rlm_pap: WARNING! No "known good" password found for the user. Authentication may fail because of this. modcall[authorize]: module "pap" returns noop for request 3 modcall: leaving group authorize (returns ok) for request 3 rad_check_password: Found Auth-Type DIGEST auth: type "digest" Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 3 rlm_digest: Configuration item "User-Password" or Digest-HA1 is required for authentication. modcall[authenticate]: module "digest" returns invalid for request 3 modcall: leaving group authenticate (returns invalid) for request 3 auth: Failed to validate the user. Delaying request 3 for 1 seconds Finished request 3 Going to the next request --- Walking the entire request list --- Waking up in 1 seconds... .... Waking up in 1 seconds... .... Finished request 5 Going to the next request --- Walking the entire request list --- Sending Access-Reject of id 136 to 127.0.0.1 port 33097 Waking up in 1 seconds... --- Walking the entire request list --- Sending Access-Reject of id 137 to 127.0.0.1 port 33098 Waking up in 1 seconds... --- Walking the entire request list --- Sending Access-Reject of id 138 to 127.0.0.1 port 33099 Waking up in 2 seconds... --- Walking the entire request list --- Cleaning up request 3 ID 136 with timestamp 469e22f4 Waking up in 1 seconds... --- Walking the entire request list --- Cleaning up request 4 ID 137 with timestamp 469e22f5 Waking up in 1 seconds... --- Walking the entire request list --- Cleaning up request 5 ID 138 with timestamp 469e22f6 Nothing to do. Sleeping until we see a request. rad_recv: Access-Request packet from host 127.0.0.1:33100, id=139, length=225 User-Name = "1000(a)opensersip.test.machine" Digest-Attributes = 0x0a0631303030 Digest-Attributes = 0x01196f70656e7365727369702e746573742e6d616368696e65 Digest-Attributes = 0x022a343639653238643463376637366632393962623164383531383637323739623034 36656462363061 Digest-Attributes = 0x04187369703a3137322e32302e31342e3231343a35303630 Digest-Attributes = 0x030a5245474953544552 Digest-Response = "9423cfb4f5e1472a432daf62417ea82e" Service-Type = Sip-Session Sip-Uri-User = "1000" NAS-Port = 5060 NAS-IP-Address = 127.0.0.1 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 6 modcall[authorize]: module "preprocess" returns ok for request 6 modcall[authorize]: module "chap" returns noop for request 6 modcall[authorize]: module "mschap" returns noop for request 6 rlm_digest: Adding Auth-Type = DIGEST modcall[authorize]: module "digest" returns ok for request 6 rlm_realm: Looking up realm "opensersip.test.machine" for User-Name = "1000(a)opensersip.test.machine" rlm_realm: No such realm "opensersip.test.machine" modcall[authorize]: module "suffix" returns noop for request 6 rlm_eap: No EAP-Message, not doing EAP modcall[authorize]: module "eap" returns noop for request 6 radius_xlat: '1000(a)opensersip.test.machine' rlm_sql (sql): sql_set_user escaped user --> '1000(a)opensersip.test.machine' radius_xlat: 'SELECT id, UserName, Attribute, Value, op FROM radcheck WHERE Username = '1000(a)opensersip.test.machine' ORDER BY id' rlm_sql (sql): Reserving sql socket id: 3 rlm_sql (sql): User 1000(a)opensersip.test.machine not found in radcheck radius_xlat: 'SELECT radgroupcheck.id,radgroupcheck.GroupName,radgroupcheck.Attribute,radgrou pcheck.Value,radgroupcheck.op FROM radgroupcheck,usergroup WHERE usergroup.Username = '1000(a)opensersip.test.machine' AND usergroup.GroupName = radgroupcheck.GroupName ORDER BY radgroupcheck.id' radius_xlat: 'SELECT radgroupreply.id,radgroupreply.GroupName,radgroupreply.Attribute,radgrou preply.Value,radgroupreply.op FROM radgroupreply,usergroup WHERE usergroup.Username = '1000(a)opensersip.test.machine' AND usergroup.GroupName = radgroupreply.GroupName ORDER BY radgroupreply.id' rlm_sql (sql): User 1000(a)opensersip.test.machine not found in radgroupcheck rlm_sql (sql): Released sql socket id: 3 rlm_sql (sql): User not found modcall[authorize]: module "sql" returns notfound for request 6 rlm_pap: WARNING! No "known good" password found for the user. Authentication may fail because of this. modcall[authorize]: module "pap" returns noop for request 6 modcall: leaving group authorize (returns ok) for request 6 rad_check_password: Found Auth-Type DIGEST auth: type "digest" Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 6 rlm_digest: Configuration item "User-Password" or Digest-HA1 is required for authentication. modcall[authenticate]: module "digest" returns invalid for request 6 modcall: leaving group authenticate (returns invalid) for request 6 auth: Failed to validate the user. Delaying request 6 for 1 seconds Finished request 6 Going to the next request --- Walking the entire request list --- Waking up in 1 seconds... Waking up in 1 seconds... ....... --- Walking the entire request list --- Sending Access-Reject of id 139 to 127.0.0.1 port 33100 Sending Access-Reject of id 140 to 127.0.0.1 port 33101 Waking up in 1 seconds... --- Walking the entire request list --- Sending Access-Reject of id 141 to 127.0.0.1 port 33102 Waking up in 3 seconds... --- Walking the entire request list --- Cleaning up request 6 ID 139 with timestamp 469e27a8 Cleaning up request 7 ID 140 with timestamp 469e27a8 Waking up in 1 seconds... --- Walking the entire request list --- Cleaning up request 8 ID 141 with timestamp 469e27a9 Nothing to do. Sleeping until we see a request.

1 0

[OpenSER-Users] Good how-to openser + radius authentification
by zze-WU Yin RD-MAPS-LAN 18 Jul '07

18 Jul '07

Hi, is it possible for you to send me your freeradius and your openser configuration files too? Thank u very much! Yin

2 1

[OpenSER-Users] Openser + Radiator
by Sergio Gutierrez 18 Jul '07

18 Jul '07

Hello all. Does somebody have any experience running Openser + Radiator for authentication and accounting? If it does, what is, more or less the maximum performance can be achieved? And finally, Is the experience running Openser + Radiator better compared to using for example free radius? Thanks in advance for your opinions. Sergio Gutiérrez EPM Telecomunicaciones Medellín - Colombia

2 1

[OpenSER-Users] release dates, updated roadmap
by Henning Westerholt 18 Jul '07

18 Jul '07

Hello all, just a short pointer to some informations from the yesterday IRC meeting: We have actual dates for the next releases: http://www.openser.org/dokuwiki/doku.php/development:release-policy The updated roadmap shows the features that will be probably in 1.3: http://www.openser.org/dokuwiki/doku.php/roadmap:1.3.x The complete minutes of the meeting are available in the wiki too. Best regards, Henning -- Henning Westerholt - Unix system development 1&1 Internet AG, Brauerstraße 48, 76135 Karlsruhe

1 0

Re: [OpenSER-Users] Good how-to openser + radius authentification
by Marc LEURENT 18 Jul '07

18 Jul '07

I've followed a french tutorial: http://www.pervasive-network.org/SPIP/Installation-de-Freeradius-sur-une Please find enclosed my config files Good luck ram a écrit : > Hi > > thats good news > > do you mind share the config files > of Radius and Openser > > iam really stuck with FreeRadius config files > > ram > > > On 7/16/07, *Marc LEURENT* <lftsy(a)free.fr <mailto:lftsy@free.fr>> wrote: > > It's working for me for OpenSER authentification/acc through > freeradius! > I've installed a debian to replace my ubuntu server, and compiled > OpenSER with radius acc support > > I'v made a .deb from source: > wget > http://ftp.debian.org/debian/pool/main/o/openser/openser_1.2.1.orig.tar.gz > <http://ftp.debian.org/debian/pool/main/o/openser/openser_1.2.1.orig.tar.gz> > wget > http://ftp.debian.org/debian/pool/main/o/openser/openser_1.2.1-1.diff.gz > tar xvzf openser_1.2.1.orig.tar.gz > cd openser-1.2.1-tls / > vim Makefile # to delete *_radius and mysql module from excluded > module > vim modules/acc/Makefile to enable radius acc and disable mysql acc > dpkg-buildpkg -rfakeroot # to create .deb > > For the rest, I've followed the tutorial, and it's working > Good luck > > Best regards, > Marc > > > ram a écrit : > > Hi > > > > thanks for the quick reply > > > > even iam trying my best to work > > > > if i see some success i will share > > > > may be with our co-ordination we can come out new setup > > working > > > > lets hope for the best > > > > ram > > > > > > On 7/16/07, *Marc LEURENT* < lftsy(a)free.fr > <mailto:lftsy@free.fr> <mailto:lftsy@free.fr > <mailto:lftsy@free.fr>>> wrote: > > > > I have got troubles too > > I'm still trying to understand how does it work > > I'll keep you informed > > Have a noce day > > > > ram a écrit : > > > Hi > > > > > > are u able to make this setup working > > > > > > iam still the same status > > > > > > let me know if you have any update we can share each other > > > > > > ram > > > > > > > > > On 7/13/07, *Marc LEURENT* < lftsy(a)free.fr > <mailto:lftsy@free.fr> <mailto:lftsy@free.fr <mailto:lftsy@free.fr>> > > <mailto:lftsy@free.fr <mailto:lftsy@free.fr> > <mailto:lftsy@free.fr <mailto:lftsy@free.fr>>>> wrote: > > > > > > I'm looking forward to seeing your update! > > > In the meantime, is it possible for you to send me your > > freeradius > > > and > > > your openser configuration files... > > > I am compiling openser with radius enabled in the acc > module... > > > > > > Best Regards, > > > > > > Marc LEURENT > > > > > > Neeraj Gupta a écrit : > > > > Hello Ram, > > > > > > > > I have successfully configured OpenSer with FreeRadius. > > However > > > I used > > > > all latest software versions. > > > > The link you mentioned is quite old now. I am > planning to > > post a new > > > > how to very soon. > > > > > > > > Thanks, > > > > Neeraj Gupta > > > > > > > > ram wrote: > > > >> > > > >> > > > >> On 7/12/07, *Bogdan-Andrei Iancu* < > bogdan(a)voice-system.ro <mailto:bogdan@voice-system.ro> > > <mailto:bogdan@voice-system.ro <mailto:bogdan@voice-system.ro>> > > > <mailto:bogdan@voice-system.ro > <mailto:bogdan@voice-system.ro> <mailto: bogdan(a)voice-system.ro > <mailto:bogdan@voice-system.ro>>> > > > >> <mailto:bogdan@voice-system.ro > <mailto:bogdan@voice-system.ro> > > <mailto: bogdan(a)voice-system.ro <mailto:bogdan@voice-system.ro>> > > > <mailto: bogdan(a)voice-system.ro > <mailto:bogdan@voice-system.ro> > > <mailto:bogdan@voice-system.ro > <mailto:bogdan@voice-system.ro>>>>> wrote: > > > >> > > > >> Hi Marc, > > > >> > > > >> have you tried this: > > > >> > http://www.openser.org/docs/openser-radius-1.0.x.html > > > <http://www.openser.org/docs/openser-radius-1.0.x.html > > < http://www.openser.org/docs/openser-radius-1.0.x.html>> > > > >> > > > >> regards, > > > >> bogdan > > > >> > > > >> > > > >> Hi > > > >> > > > >> with the above URL, can any one able to make success > > > >> integration with Freeradius > > > >> > > > >> i get lot of errors on freeradius side > > > >> some time hint, some time groups, some time Auth-Type > > > >> > > > >> i followed the same instrusction > > > >> i get this following errors > > > >> > > > >> any help ? > > > >> > > > >> Module: Loaded files > > > >> files: usersfile = "/usr/local/etc/raddb/users" > > > >> files: acctusersfile = > "/usr/local/etc/raddb/acct_users" > > > >> files: preproxy_usersfile = > > "/usr/local/etc/raddb/preproxy_users" > > > >> files: compat = "no" > > > >> /usr/local/etc/raddb/users[1]: Parse error (check) for > > entry test: > > > >> Unknown attribute "Auth-Type" > > > >> Errors reading /usr/local/etc/raddb/users > > > >> radiusd.conf[863]: files: Module instantiation failed. > > > >> radiusd.conf[1204] Unknown module "files". > > > >> radiusd.conf[1201] Failed to parse preacct section. > > > >> > > > >> > > > >> ram > > > >> > > > >> > > > > > > ------------------------------------------------------------------------ > > > >> > > > >> _______________________________________________ > > > >> Users mailing list > > > >> Users(a)openser.org <mailto:Users@openser.org> > <mailto:Users@openser.org <mailto:Users@openser.org>> > > <mailto:Users@openser.org <mailto:Users@openser.org> > <mailto:Users@openser.org <mailto:Users@openser.org>>> > > > >> http://openser.org/cgi-bin/mailman/listinfo/users > > > >> > > > > > > > > -- > > > > > ------------------------------------------------------------- > > > > o Neeraj Gupta email: > neeraj.gupta(a)sun.com <mailto:neeraj.gupta@sun.com> > > <mailto:neeraj.gupta@sun.com <mailto:neeraj.gupta@sun.com>> > > > <mailto: neeraj.gupta(a)sun.com > <mailto:neeraj.gupta@sun.com> <mailto:neeraj.gupta@sun.com > <mailto:neeraj.gupta@sun.com>>> > > > > o Netra Systems & Networking phone: +1(408) > 276-7214 x71214 > > > > o Sun Microsystems, Inc. fax : +1(408) 276-4552 > > > > o 4120 Network Circle, USCA12-216, Santa Clara, CA > 95054, USA > > > > > ------------------------------------------------------------- > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > > > > > > _______________________________________________ > > > > Users mailing list > > > > Users(a)openser.org <mailto:Users@openser.org> > <mailto:Users@openser.org <mailto:Users@openser.org>> > > <mailto: Users(a)openser.org <mailto:Users@openser.org> > <mailto:Users@openser.org <mailto:Users@openser.org>>> > > > > http://openser.org/cgi-bin/mailman/listinfo/users > <http://openser.org/cgi-bin/mailman/listinfo/users> > > > > > > > > > > > > > > > > # # $Id: openser.cfg 1827 2007-03-12 15:22:53Z bogdan_iancu $ # # simple quick-start config script # Please refer to the Core CookBook at http://www.openser.org/dokuwiki/doku.php # for a explanation of possible statements, functions and parameters. # # ----------- global configuration parameters ------------------------ debug=7 # debug level (cmd line: -dddddddddd) fork=no log_stderror=yes # (cmd line: -E) children=4 # Uncomment these lines to enter debugging mode #fork=no #log_stderror=yes # listen=sip.test.fr port=5060 # uncomment the following lines for TLS support #disable_tls = 0 #listen = tls:your_IP:5061 #tls_verify_server = 1 #tls_verify_client = 1 #tls_require_client_certificate = 0 #tls_method = TLSv1 #tls_certificate = "/etc/openser/tls/user/user-cert.pem" #tls_private_key = "/etc/openser/tls/user/user-privkey.pem" #tls_ca_list = "/etc/openser/tls/user/user-calist.pem" # ------------------ module loading ---------------------------------- #set module path mpath="/usr/lib/openser/modules/" # Uncomment this if you want to use SQL database loadmodule "mysql.so" loadmodule "sl.so" loadmodule "tm.so" loadmodule "rr.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "mi_fifo.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! loadmodule "auth.so" loadmodule "acc.so" loadmodule "avpops.so" loadmodule "uri.so" #loadmodule "auth_db.so" loadmodule "auth_radius.so" loadmodule "group_radius.so" loadmodule "avp_radius.so" #loadmodule "presence.so" loadmodule "options.so" # ----------------- setting module-specific parameters --------------- # -- mi_fifo params -- modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo") # -- 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", "radius_flag", 1) modparam("acc", "radius_missed_flag", 2) modparam("acc", "log_flag", 1) modparam("acc", "log_missed_flag", 1) modparam("acc", "service_type", 15) modparam("acc", "radius_extra", "Sip-Src-IP=$si;Sip-Src-Port=$sp") modparam("acc|auth_radius|group_radius|avp_radius", "radius_config", "/etc/radiusclient-ng/radiusclient.conf") # -- group_radius params -- modparam("group_radius", "use_domain", 1) # -- avpops params -- #modparam("avpops", "avp_aliases", "day=i:101;time=i:102") # -- presence params -- modparam("usrloc", "db_url", "mysql://openser:openserrw@192.168.95.248/openser") #modparam("presence|usrloc", "db_url", "mysql://openser:openserrw@192.168.95.248/openser") #modparam("presence", "max_expires", 3600) #modparam("presence", "force_active", 1) #modparam("presence", "server_address", "sip:sip.test.fr:5060" ) # -- options params -- #modparam("options", "accept", "*/*") #modparam("options", "accept_encoding", "") # gzip non supporte #modparam("options", "accept_language", "en") # ------------------------- 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("tls:domain1.net"); # exit; #} else if(uri=~"@tls_domain2.net") { # t_relay("tls:domain2.net"); # 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("sip.test.fr", "subscriber")) { # www_challenge("sip.test.fr", "0"); # exit; #}; if (!radius_www_authorize("sip.test.fr")) { www_challenge("sip.test.fr", "0"); exit; }; save("location"); 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"); }; if (uri==myself) { if ((method==OPTIONS) && (! uri=~"sip:.*[@]+.*")) { options_reply(); }; }; 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; } ## ## radiusd.conf -- FreeRADIUS server configuration file. ## ## http://www.freeradius.org/ ## $Id: radiusd.conf.in,v 1.188.2.4.2.12 2006/07/29 19:43:30 nbk Exp $ ## # The location of other config files and # logfiles are declared in this file # # Also general configuration for modules can be done # in this file, it is exported through the API to # modules that ask for it. # # The configuration variables defined here are of the form ${foo} # They are local to this file, and do not change from request to # request. # # The per-request variables are of the form %{Attribute-Name}, and # are taken from the values of the attribute in the incoming # request. See 'doc/variables.txt' for more information. prefix = /usr exec_prefix = /usr sysconfdir = /etc localstatedir = /var sbindir = ${exec_prefix}/sbin logdir = /var/log/freeradius raddbdir = /etc/freeradius radacctdir = ${logdir}/radacct # Location of config and logfiles. confdir = ${raddbdir} run_dir = ${localstatedir}/run/freeradius # # The logging messages for the server are appended to the # tail of this file. # log_file = ${logdir}/radius.log # # libdir: Where to find the rlm_* modules. # # This should be automatically set at configuration time. # # If the server builds and installs, but fails at execution time # with an 'undefined symbol' error, then you can use the libdir # directive to work around the problem. # # The cause is usually that a library has been installed on your # system in a place where the dynamic linker CANNOT find it. When # executing as root (or another user), your personal environment MAY # be set up to allow the dynamic linker to find the library. When # executing as a daemon, FreeRADIUS MAY NOT have the same # personalized configuration. # # To work around the problem, find out which library contains that symbol, # and add the directory containing that library to the end of 'libdir', # with a colon separating the directory names. NO spaces are allowed. # # e.g. libdir = /usr/local/lib:/opt/package/lib # # You can also try setting the LD_LIBRARY_PATH environment variable # in a script which starts the server. # # If that does not work, then you can re-configure and re-build the # server to NOT use shared libraries, via: # # ./configure --disable-shared # make # make install # libdir = /usr/lib/freeradius # pidfile: Where to place the PID of the RADIUS server. # # The server may be signalled while it's running by using this # file. # # This file is written when ONLY running in daemon mode. # # e.g.: kill -HUP `cat /var/run/freeradius/freeradius.pid` # pidfile = ${run_dir}/freeradius.pid # user/group: The name (or #number) of the user/group to run radiusd as. # # If these are commented out, the server will run as the user/group # that started it. In order to change to a different user/group, you # MUST be root ( or have root privleges ) to start the server. # # We STRONGLY recommend that you run the server with as few permissions # as possible. That is, if you're not using shadow passwords, the # user and group items below should be set to 'nobody'. # # On SCO (ODT 3) use "user = nouser" and "group = nogroup". # # NOTE that some kernels refuse to setgid(group) when the value of # (unsigned)group is above 60000; don't use group nobody on these systems! # # On systems with shadow passwords, you might have to set 'group = shadow' # for the server to be able to read the shadow password file. If you can # authenticate users while in debug mode, but not in daemon mode, it may be # that the debugging mode server is running as a user that can read the # shadow info, and the user listed below can not. # user = freerad group = freerad # max_request_time: The maximum time (in seconds) to handle a request. # # Requests which take more time than this to process may be killed, and # a REJECT message is returned. # # WARNING: If you notice that requests take a long time to be handled, # then this MAY INDICATE a bug in the server, in one of the modules # used to handle a request, OR in your local configuration. # # This problem is most often seen when using an SQL database. If it takes # more than a second or two to receive an answer from the SQL database, # then it probably means that you haven't indexed the database. See your # SQL server documentation for more information. # # Useful range of values: 5 to 120 # max_request_time = 30 # delete_blocked_requests: If the request takes MORE THAN 'max_request_time' # to be handled, then maybe the server should delete it. # # If you're running in threaded, or thread pool mode, this setting # should probably be 'no'. Setting it to 'yes' when using a threaded # server MAY cause the server to crash! # delete_blocked_requests = no # cleanup_delay: The time to wait (in seconds) before cleaning up # a reply which was sent to the NAS. # # The RADIUS request is normally cached internally for a short period # of time, after the reply is sent to the NAS. The reply packet may be # lost in the network, and the NAS will not see it. The NAS will then # re-send the request, and the server will respond quickly with the # cached reply. # # If this value is set too low, then duplicate requests from the NAS # MAY NOT be detected, and will instead be handled as seperate requests. # # If this value is set too high, then the server will cache too many # requests, and some new requests may get blocked. (See 'max_requests'.) # # Useful range of values: 2 to 10 # cleanup_delay = 5 # max_requests: The maximum number of requests which the server keeps # track of. This should be 256 multiplied by the number of clients. # e.g. With 4 clients, this number should be 1024. # # If this number is too low, then when the server becomes busy, # it will not respond to any new requests, until the 'cleanup_delay' # time has passed, and it has removed the old requests. # # If this number is set too high, then the server will use a bit more # memory for no real benefit. # # If you aren't sure what it should be set to, it's better to set it # too high than too low. Setting it to 1000 per client is probably # the highest it should be. # # Useful range of values: 256 to infinity # max_requests = 1024 # bind_address: Make the server listen on a particular IP address, and # send replies out from that address. This directive is most useful # for machines with multiple IP addresses on one interface. # # It can either contain "*", or an IP address, or a fully qualified # Internet domain name. The default is "*" # # As of 1.0, you can also use the "listen" directive. See below for # more information. # bind_address = * # port: Allows you to bind FreeRADIUS to a specific port. # # The default port that most NAS boxes use is 1645, which is historical. # RFC 2138 defines 1812 to be the new port. Many new servers and # NAS boxes use 1812, which can create interoperability problems. # # The port is defined here to be 0 so that the server will pick up # the machine's local configuration for the radius port, as defined # in /etc/services. # # If you want to use the default RADIUS port as defined on your server, # (usually through 'grep radius /etc/services') set this to 0 (zero). # # A port given on the command-line via '-p' over-rides this one. # # As of 1.0, you can also use the "listen" directive. See below for # more information. # port = 0 # # By default, the server uses "bind_address" to listen to all IP's # on a machine, or just one IP. The "port" configuration is used # to select the authentication port used when listening on those # addresses. # # If you want the server to listen on additional addresses, you can # use the "listen" section. A sample section (commented out) is included # below. This "listen" section duplicates the functionality of the # "bind_address" and "port" configuration entries, but it only listens # for authentication packets. # # If you comment out the "bind_address" and "port" configuration entries, # then it becomes possible to make the server accept only accounting, # or authentication packets. Previously, it always listened for both # types of packets, and it was impossible to make it listen for only # one type of packet. # #listen { # IP address on which to listen. # Allowed values are: # dotted quad (1.2.3.4) # hostname (radius.example.com) # wildcard (*) # ipaddr = * # Port on which to listen. # Allowed values are: # integer port number (1812) # 0 means "use /etc/services for the proper port" # port = 0 # Type of packets to listen for. # Allowed values are: # auth listen for authentication packets # acct listen for accounting packets # # type = auth #} # hostname_lookups: Log the names of clients or just their IP addresses # e.g., www.freeradius.org (on) or 206.47.27.232 (off). # # The default is 'off' because it would be overall better for the net # if people had to knowingly turn this feature on, since enabling it # means that each client request will result in AT LEAST one lookup # request to the nameserver. Enabling hostname_lookups will also # mean that your server may stop randomly for 30 seconds from time # to time, if the DNS requests take too long. # # Turning hostname lookups off also means that the server won't block # for 30 seconds, if it sees an IP address which has no name associated # with it. # # allowed values: {no, yes} # hostname_lookups = no # Core dumps are a bad thing. This should only be set to 'yes' # if you're debugging a problem with the server. # # allowed values: {no, yes} # allow_core_dumps = no # Regular expressions # # These items are set at configure time. If they're set to "yes", # then setting them to "no" turns off regular expression support. # # If they're set to "no" at configure time, then setting them to "yes" # WILL NOT WORK. It will give you an error. # regular_expressions = yes extended_expressions = yes # Log the full User-Name attribute, as it was found in the request. # # allowed values: {no, yes} # log_stripped_names = yes # Log authentication requests to the log file. # # allowed values: {no, yes} # log_auth = yes # Log passwords with the authentication requests. # log_auth_badpass - logs password if it's rejected # log_auth_goodpass - logs password if it's correct # # allowed values: {no, yes} # log_auth_badpass = yes log_auth_goodpass = yes # usercollide: Turn "username collision" code on and off. See the # "doc/duplicate-users" file # # WARNING # !!!!!!! Setting this to "yes" may result in the server behaving # !!!!!!! strangely. The "username collision" code will ONLY work # !!!!!!! with clear-text passwords. Even then, it may not do what # !!!!!!! you want, or what you expect. # !!!!!!! # !!!!!!! We STRONGLY RECOMMEND that you do not use this feature, # !!!!!!! and that you find another way of acheiving the same goal. # !!!!!!! # !!!!!!! e,g. module fail-over. See 'doc/configurable_failover' # WARNING # usercollide = no # lower_user / lower_pass: # Lower case the username/password "before" or "after" # attempting to authenticate. # # If "before", the server will first modify the request and then try # to auth the user. If "after", the server will first auth using the # values provided by the user. If that fails it will reprocess the # request after modifying it as you specify below. # # This is as close as we can get to case insensitivity. It is the # admin's job to ensure that the username on the auth db side is # *also* lowercase to make this work # # Default is 'no' (don't lowercase values) # Valid values = "before" / "after" / "no" # lower_user = no lower_pass = no # nospace_user / nospace_pass: # # Some users like to enter spaces in their username or password # incorrectly. To save yourself the tech support call, you can # eliminate those spaces here: # # Default is 'no' (don't remove spaces) # Valid values = "before" / "after" / "no" (explanation above) # nospace_user = no nospace_pass = no # The program to execute to do concurrency checks. checkrad = ${sbindir}/checkrad # SECURITY CONFIGURATION # # There may be multiple methods of attacking on the server. This # section holds the configuration items which minimize the impact # of those attacks # security { # # max_attributes: The maximum number of attributes # permitted in a RADIUS packet. Packets which have MORE # than this number of attributes in them will be dropped. # # If this number is set too low, then no RADIUS packets # will be accepted. # # If this number is set too high, then an attacker may be # able to send a small number of packets which will cause # the server to use all available memory on the machine. # # Setting this number to 0 means "allow any number of attributes" max_attributes = 200 # # reject_delay: When sending an Access-Reject, it can be # delayed for a few seconds. This may help slow down a DoS # attack. It also helps to slow down people trying to brute-force # crack a users password. # # Setting this number to 0 means "send rejects immediately" # # If this number is set higher than 'cleanup_delay', then the # rejects will be sent at 'cleanup_delay' time, when the request # is deleted from the internal cache of requests. # # Useful ranges: 1 to 5 reject_delay = 1 # # status_server: Whether or not the server will respond # to Status-Server requests. # # Normally this should be set to "no", because they're useless. # See: http://www.freeradius.org/rfc/rfc2865.html#Keep-Alives # # However, certain NAS boxes may require them. # # When sent a Status-Server message, the server responds with # an Access-Accept packet, containing a Reply-Message attribute, # which is a string describing how long the server has been # running. # status_server = no } # PROXY CONFIGURATION # # proxy_requests: Turns proxying of RADIUS requests on or off. # # The server has proxying turned on by default. If your system is NOT # set up to proxy requests to another server, then you can turn proxying # off here. This will save a small amount of resources on the server. # # If you have proxying turned off, and your configuration files say # to proxy a request, then an error message will be logged. # # To disable proxying, change the "yes" to "no", and comment the # $INCLUDE line. # # allowed values: {no, yes} # proxy_requests = yes $INCLUDE ${confdir}/proxy.conf # CLIENTS CONFIGURATION # # Client configuration is defined in "clients.conf". # # The 'clients.conf' file contains all of the information from the old # 'clients' and 'naslist' configuration files. We recommend that you # do NOT use 'client's or 'naslist', although they are still # supported. # # Anything listed in 'clients.conf' will take precedence over the # information from the old-style configuration files. # $INCLUDE ${confdir}/clients.conf # SNMP CONFIGURATION # # Snmp configuration is only valid if SNMP support was enabled # at compile time. # # To enable SNMP querying of the server, set the value of the # 'snmp' attribute to 'yes' # snmp = no $INCLUDE ${confdir}/snmp.conf # THREAD POOL CONFIGURATION # # The thread pool is a long-lived group of threads which # take turns (round-robin) handling any incoming requests. # # You probably want to have a few spare threads around, # so that high-load situations can be handled immediately. If you # don't have any spare threads, then the request handling will # be delayed while a new thread is created, and added to the pool. # # You probably don't want too many spare threads around, # otherwise they'll be sitting there taking up resources, and # not doing anything productive. # # The numbers given below should be adequate for most situations. # thread pool { # Number of servers to start initially --- should be a reasonable # ballpark figure. start_servers = 5 # Limit on the total number of servers running. # # If this limit is ever reached, clients will be LOCKED OUT, so it # should NOT BE SET TOO LOW. It is intended mainly as a brake to # keep a runaway server from taking the system with it as it spirals # down... # # You may find that the server is regularly reaching the # 'max_servers' number of threads, and that increasing # 'max_servers' doesn't seem to make much difference. # # If this is the case, then the problem is MOST LIKELY that # your back-end databases are taking too long to respond, and # are preventing the server from responding in a timely manner. # # The solution is NOT do keep increasing the 'max_servers' # value, but instead to fix the underlying cause of the # problem: slow database, or 'hostname_lookups=yes'. # # For more information, see 'max_request_time', above. # max_servers = 32 # Server-pool size regulation. Rather than making you guess # how many servers you need, FreeRADIUS dynamically adapts to # the load it sees, that is, it tries to maintain enough # servers to handle the current load, plus a few spare # servers to handle transient load spikes. # # It does this by periodically checking how many servers are # waiting for a request. If there are fewer than # min_spare_servers, it creates a new spare. If there are # more than max_spare_servers, some of the spares die off. # The default values are probably OK for most sites. # min_spare_servers = 3 max_spare_servers = 10 # There may be memory leaks or resource allocation problems with # the server. If so, set this value to 300 or so, so that the # resources will be cleaned up periodically. # # This should only be necessary if there are serious bugs in the # server which have not yet been fixed. # # '0' is a special value meaning 'infinity', or 'the servers never # exit' max_requests_per_server = 0 } # MODULE CONFIGURATION # # The names and configuration of each module is located in this section. # # After the modules are defined here, they may be referred to by name, # in other sections of this configuration file. # modules { # # Each module has a configuration as follows: # # name [ instance ] { # config_item = value # ... # } # # The 'name' is used to load the 'rlm_name' library # which implements the functionality of the module. # # The 'instance' is optional. To have two different instances # of a module, it first must be referred to by 'name'. # The different copies of the module are then created by # inventing two 'instance' names, e.g. 'instance1' and 'instance2' # # The instance names can then be used in later configuration # INSTEAD of the original 'name'. See the 'radutmp' configuration # below for an example. # # PAP module to authenticate users based on their stored password # # Supports multiple encryption schemes # clear: Clear text # crypt: Unix crypt # md5: MD5 ecnryption # sha1: SHA1 encryption. # DEFAULT: crypt pap { encryption_scheme = crypt } # CHAP module # # To authenticate requests containing a CHAP-Password attribute. # chap { authtype = CHAP } # Pluggable Authentication Modules # # For Linux, see: # http://www.kernel.org/pub/linux/libs/pam/index.html # # WARNING: On many systems, the system PAM libraries have # memory leaks! We STRONGLY SUGGEST that you do not # use PAM for authentication, due to those memory leaks. # pam { # # The name to use for PAM authentication. # PAM looks in /etc/pam.d/${pam_auth_name} # for it's configuration. See 'redhat/radiusd-pam' # for a sample PAM configuration file. # # Note that any Pam-Auth attribute set in the 'authorize' # section will over-ride this one. # pam_auth = radiusd } # Unix /etc/passwd style authentication # unix { # # Cache /etc/passwd, /etc/shadow, and /etc/group # # The default is to NOT cache them. # # For FreeBSD and NetBSD, you do NOT want to enable # the cache, as it's password lookups are done via a # database, so set this value to 'no'. # # Some systems (e.g. RedHat Linux with pam_pwbd) can # take *seconds* to check a password, when th passwd # file containing 1000's of entries. For those systems, # you should set the cache value to 'yes', and set # the locations of the 'passwd', 'shadow', and 'group' # files, below. # # allowed values: {no, yes} cache = no # Reload the cache every 600 seconds (10mins). 0 to disable. cache_reload = 600 # # Define the locations of the normal passwd, shadow, and # group files. # # 'shadow' is commented out by default, because not all # systems have shadow passwords. # # To force the module to use the system password functions, # instead of reading the files, leave the following entries # commented out. # # This is required for some systems, like FreeBSD, # and Mac OSX. # # passwd = /etc/passwd shadow = /etc/shadow # group = /etc/group # # The location of the "wtmp" file. # This should be moved to it's own module soon. # # The only use for 'radlast'. If you don't use # 'radlast', then you can comment out this item. # radwtmp = ${logdir}/radwtmp } # Extensible Authentication Protocol # # For all EAP related authentications. # Now in another file, because it is very large. # $INCLUDE ${confdir}/eap.conf # Microsoft CHAP authentication # # This module supports MS-CHAP and MS-CHAPv2 authentication. # It also enforces the SMB-Account-Ctrl attribute. # mschap { # # As of 0.9, the mschap module does NOT support # reading from /etc/smbpasswd. # # If you are using /etc/smbpasswd, see the 'passwd' # module for an example of how to use /etc/smbpasswd # if use_mppe is not set to no mschap will # add MS-CHAP-MPPE-Keys for MS-CHAPv1 and # MS-MPPE-Recv-Key/MS-MPPE-Send-Key for MS-CHAPv2 # #use_mppe = no # if mppe is enabled require_encryption makes # encryption moderate # #require_encryption = yes # require_strong always requires 128 bit key # encryption # #require_strong = yes # Windows sends us a username in the form of # DOMAIN\user, but sends the challenge response # based on only the user portion. This hack # corrects for that incorrect behavior. # #with_ntdomain_hack = no # The module can perform authentication itself, OR # use a Windows Domain Controller. This configuration # directive tells the module to call the ntlm_auth # program, which will do the authentication, and return # the NT-Key. Note that you MUST have "winbindd" and # "nmbd" running on the local machine for ntlm_auth # to work. See the ntlm_auth program documentation # for details. # # Be VERY careful when editing the following line! # #ntlm_auth = "/path/to/ntlm_auth --request-nt-key --username=%{Stripped-User-Name:-%{User-Name:-None}} --challenge=%{mschap:Challenge:-00} --nt-response=%{mschap:NT-Response:-00}" } # Lightweight Directory Access Protocol (LDAP) # # This module definition allows you to use LDAP for # authorization and authentication. # # See doc/rlm_ldap for description of configuration options # and sample authorize{} and authenticate{} blocks # # However, LDAP can be used for authentication ONLY when the # Access-Request packet contains a clear-text User-Password # attribute. LDAP authentication will NOT work for any other # authentication method. # # This means that LDAP servers don't understand EAP. If you # force "Auth-Type = LDAP", and then send the server a # request containing EAP authentication, then authentication # WILL NOT WORK. # # The solution is to use the default configuration, which does # work. # # Setting "Auth-Type = LDAP" is ALMOST ALWAYS WRONG. We # really can't emphasize this enough. # ldap { server = "ldap.your.domain" # identity = "cn=admin,o=My Org,c=UA" # password = mypass basedn = "o=My Org,c=UA" filter = "(uid=%{Stripped-User-Name:-%{User-Name}})" # base_filter = "(objectclass=radiusprofile)" # set this to 'yes' to use TLS encrypted connections # to the LDAP database by using the StartTLS extended # operation. # The StartTLS operation is supposed to be used with normal # ldap connections instead of using ldaps (port 689) connections start_tls = no # tls_cacertfile = /path/to/cacert.pem # tls_cacertdir = /path/to/ca/dir/ # tls_certfile = /path/to/radius.crt # tls_keyfile = /path/to/radius.key # tls_randfile = /path/to/rnd # tls_require_cert = "demand" # default_profile = "cn=radprofile,ou=dialup,o=My Org,c=UA" # profile_attribute = "radiusProfileDn" access_attr = "dialupAccess" # Mapping of RADIUS dictionary attributes to LDAP # directory attributes. dictionary_mapping = ${raddbdir}/ldap.attrmap ldap_connections_number = 5 # # NOTICE: The password_header directive is NOT case insensitive # # password_header = "{clear}" # # Set: # password_attribute = nspmPassword # # to get the user's password from a Novell eDirectory # backend. This will work *only if* freeRADIUS is # configured to build with --with-edir option. # # # The server can usually figure this out on its own, and pull # the correct User-Password or NT-Password from the database. # # Note that NT-Passwords MUST be stored as a 32-digit hex # string, and MUST start off with "0x", such as: # # 0x000102030405060708090a0b0c0d0e0f # # Without the leading "0x", NT-Passwords will not work. # This goes for NT-Passwords stored in SQL, too. # # password_attribute = userPassword # # Un-comment the following to disable Novell eDirectory account # policy check and intruder detection. This will work *only if* # FreeRADIUS is configured to build with --with-edir option. # # edir_account_policy_check=no # # groupname_attribute = cn # groupmembership_filter = "(|(&(objectClass=GroupOfNames)(member=%{Ldap-UserDn}))(&(objectClass=GroupOfUniqueNames)(uniquemember=%{Ldap-UserDn})))" # groupmembership_attribute = radiusGroupName timeout = 4 timelimit = 3 net_timeout = 1 # compare_check_items = yes # do_xlat = yes # access_attr_used_for_allow = yes # # By default, if the packet contains a User-Password, # and no other module is configured to handle the # authentication, the LDAP module sets itself to do # LDAP bind for authentication. # # You can disable this behavior by setting the following # configuration entry to "no". # # allowed values: {no, yes} # set_auth_type = yes } # passwd module allows to do authorization via any passwd-like # file and to extract any attributes from these modules # # parameters are: # filename - path to filename # format - format for filename record. This parameters # correlates record in the passwd file and RADIUS # attributes. # # Field marked as '*' is key field. That is, the parameter # with this name from the request is used to search for # the record from passwd file # Attribute marked as '=' is added to reply_itmes instead # of default configure_itmes # Attribute marked as '~' is added to request_items # # Field marked as ',' may contain a comma separated list # of attributes. # authtype - if record found this Auth-Type is used to authenticate # user # hashsize - hashtable size. If 0 or not specified records are not # stored in memory and file is red on every request. # allowmultiplekeys - if few records for every key are allowed # ignorenislike - ignore NIS-related records # delimiter - symbol to use as a field separator in passwd file, # for format ':' symbol is always used. '\0', '\n' are # not allowed # # An example configuration for using /etc/smbpasswd. # #passwd etc_smbpasswd { # filename = /etc/smbpasswd # format = "*User-Name::LM-Password:NT-Password:SMB-Account-CTRL-TEXT::" # authtype = MS-CHAP # hashsize = 100 # ignorenislike = no # allowmultiplekeys = no #} # Similar configuration, for the /etc/group file. Adds a Group-Name # attribute for every group that the user is member of. # #passwd etc_group { # filename = /etc/group # format = "=Group-Name:::*,User-Name" # hashsize = 50 # ignorenislike = yes # allowmultiplekeys = yes # delimiter = ":" #} # Realm module, for proxying. # # You can have multiple instances of the realm module to # support multiple realm syntaxs at the same time. The # search order is defined by the order in the authorize and # preacct sections. # # Four config options: # format - must be 'prefix' or 'suffix' # delimiter - must be a single character # ignore_default - set to 'yes' or 'no' # ignore_null - set to 'yes' or 'no' # # ignore_default and ignore_null can be set to 'yes' to prevent # the module from matching against DEFAULT or NULL realms. This # may be useful if you have have multiple instances of the # realm module. # # They both default to 'no'. # # 'realm/username' # # Using this entry, IPASS users have their realm set to "IPASS". realm IPASS { format = prefix delimiter = "/" ignore_default = no ignore_null = no } # 'username@realm' # realm suffix { format = suffix delimiter = "@" ignore_default = no ignore_null = no } # 'username%realm' # realm realmpercent { format = suffix delimiter = "%" ignore_default = no ignore_null = no } # # 'domain\user' # realm ntdomain { format = prefix delimiter = "\\" ignore_default = no ignore_null = no } # A simple value checking module # # It can be used to check if an attribute value in the request # matches a (possibly multi valued) attribute in the check # items This can be used for example for caller-id # authentication. For the module to run, both the request # attribute and the check items attribute must exist # # i.e. # A user has an ldap entry with 2 radiusCallingStationId # attributes with values "12345678" and "12345679". If we # enable rlm_checkval, then any request which contains a # Calling-Station-Id with one of those two values will be # accepted. Requests with other values for # Calling-Station-Id will be rejected. # # Regular expressions in the check attribute value are allowed # as long as the operator is '=~' # checkval { # The attribute to look for in the request item-name = Calling-Station-Id # The attribute to look for in check items. Can be multi valued check-name = Calling-Station-Id # The data type. Can be # string,integer,ipaddr,date,abinary,octets data-type = string # If set to yes and we dont find the item-name attribute in the # request then we send back a reject # DEFAULT is no #notfound-reject = no } # rewrite arbitrary packets. Useful in accounting and authorization. # # # The module can also use the Rewrite-Rule attribute. If it # is set and matches the name of the module instance, then # that module instance will be the only one which runs. # # Also if new_attribute is set to yes then a new attribute # will be created containing the value replacewith and it # will be added to searchin (packet, reply, proxy, proxy_reply or config). # searchfor,ignore_case and max_matches will be ignored in that case. # # Backreferences are supported: %{0} will contain the string the whole match # and %{1} to %{8} will contain the contents of the 1st to the 8th parentheses # # If max_matches is greater than one the backreferences will correspond to the # first match # #attr_rewrite sanecallerid { # attribute = Called-Station-Id # may be "packet", "reply", "proxy", "proxy_reply" or "config" # searchin = packet # searchfor = "[+ ]" # replacewith = "" # ignore_case = no # new_attribute = no # max_matches = 10 # ## If set to yes then the replace string will be appended to the original string # append = no #} # Preprocess the incoming RADIUS request, before handing it off # to other modules. # # This module processes the 'huntgroups' and 'hints' files. # In addition, it re-writes some weird attributes created # by some NASes, and converts the attributes into a form which # is a little more standard. # preprocess { huntgroups = ${confdir}/huntgroups hints = ${confdir}/hints # This hack changes Ascend's wierd port numberings # to standard 0-??? port numbers so that the "+" works # for IP address assignments. with_ascend_hack = no ascend_channels_per_line = 23 # Windows NT machines often authenticate themselves as # NT_DOMAIN\username # # If this is set to 'yes', then the NT_DOMAIN portion # of the user-name is silently discarded. # # This configuration entry SHOULD NOT be used. # See the "realms" module for a better way to handle # NT domains. with_ntdomain_hack = no # Specialix Jetstream 8500 24 port access server. # # If the user name is 10 characters or longer, a "/" # and the excess characters after the 10th are # appended to the user name. # # If you're not running that NAS, you don't need # this hack. with_specialix_jetstream_hack = no # Cisco (and Quintum in Cisco mode) sends it's VSA attributes # with the attribute name *again* in the string, like: # # H323-Attribute = "h323-attribute=value". # # If this configuration item is set to 'yes', then # the redundant data in the the attribute text is stripped # out. The result is: # # H323-Attribute = "value" # # If you're not running a Cisco or Quintum NAS, you don't # need this hack. with_cisco_vsa_hack = no } # Livingston-style 'users' file # files { usersfile = ${confdir}/users acctusersfile = ${confdir}/acct_users preproxy_usersfile = ${confdir}/preproxy_users # If you want to use the old Cistron 'users' file # with FreeRADIUS, you should change the next line # to 'compat = cistron'. You can the copy your 'users' # file from Cistron. compat = no } # Write a detailed log of all accounting records received. # detail { # Note that we do NOT use NAS-IP-Address here, as # that attribute MAY BE from the originating NAS, and # NOT from the proxy which actually sent us the # request. The Client-IP-Address attribute is ALWAYS # the address of the client which sent us the # request. # # The following line creates a new detail file for # every radius client (by IP address or hostname). # In addition, a new detail file is created every # day, so that the detail file doesn't have to go # through a 'log rotation' # # If your detail files are large, you may also want # to add a ':%H' (see doc/variables.txt) to the end # of it, to create a new detail file every hour, e.g.: # # ..../detail-%Y%m%d:%H # # This will create a new detail file for every hour. # detailfile = ${radacctdir}/%{Client-IP-Address}/detail-%Y%m%d # # The Unix-style permissions on the 'detail' file. # # The detail file often contains secret or private # information about users. So by keeping the file # permissions restrictive, we can prevent unwanted # people from seeing that information. detailperm = 0600 # # Certain attributes such as User-Password may be # "sensitive", so they should not be printed in the # detail file. This section lists the attributes # that should be suppressed. # # The attributes should be listed one to a line. # #suppress { # User-Password #} } # # Many people want to log authentication requests. # Rather than modifying the server core to print out more # messages, we can use a different instance of the 'detail' # module, to log the authentication requests to a file. # # You will also need to un-comment the 'auth_log' line # in the 'authorize' section, below. # # detail auth_log { # detailfile = ${radacctdir}/%{Client-IP-Address}/auth-detail-%Y%m%d # # This MUST be 0600, otherwise anyone can read # the users passwords! # detailperm = 0600 # } # # This module logs authentication reply packets sent # to a NAS. Both Access-Accept and Access-Reject packets # are logged. # # You will also need to un-comment the 'reply_log' line # in the 'post-auth' section, below. # # detail reply_log { # detailfile = ${radacctdir}/%{Client-IP-Address}/reply-detail-%Y%m%d # # This MUST be 0600, otherwise anyone can read # the users passwords! # detailperm = 0600 # } # # This module logs packets proxied to a home server. # # You will also need to un-comment the 'pre_proxy_log' line # in the 'pre-proxy' section, below. # # detail pre_proxy_log { # detailfile = ${radacctdir}/%{Client-IP-Address}/pre-proxy-detail-%Y%m%d # # This MUST be 0600, otherwise anyone can read # the users passwords! # detailperm = 0600 # } # # This module logs response packets from a home server. # # You will also need to un-comment the 'post_proxy_log' line # in the 'post-proxy' section, below. # # detail post_proxy_log { # detailfile = ${radacctdir}/%{Client-IP-Address}/post-proxy-detail-%Y%m%d # # This MUST be 0600, otherwise anyone can read # the users passwords! # detailperm = 0600 # } # # The rlm_sql_log module appends the SQL queries in a log # file which is read later by the radsqlrelay program. # # This module only performs the dynamic expansion of the # variables found in the SQL statements. No operation is # executed on the database server. (this could be done # later by an external program) That means the module is # useful only with non-"SELECT" statements. # # See rlm_sql_log(5) manpage. # # sql_log { # path = ${radacctdir}/sql-relay # acct_table = "radacct" # postauth_table = "radpostauth" # # Start = "INSERT INTO ${acct_table} (AcctSessionId, UserName, \ # NASIPAddress, FramedIPAddress, AcctStartTime, AcctStopTime, \ # AcctSessionTime, AcctTerminateCause) VALUES \ # ('%{Acct-Session-Id}', '%{User-Name}', '%{NAS-IP-Address}', \ # '%{Framed-IP-Address}', '%S', '0', '0', '');" # Stop = "INSERT INTO ${acct_table} (AcctSessionId, UserName, \ # NASIPAddress, FramedIPAddress, AcctStartTime, AcctStopTime, \ # AcctSessionTime, AcctTerminateCause) VALUES \ # ('%{Acct-Session-Id}', '%{User-Name}', '%{NAS-IP-Address}', \ # '%{Framed-IP-Address}', '0', '%S', '%{Acct-Session-Time}', \ # '%{Acct-Terminate-Cause}');" # Alive = "INSERT INTO ${acct_table} (AcctSessionId, UserName, \ # NASIPAddress, FramedIPAddress, AcctStartTime, AcctStopTime, \ # AcctSessionTime, AcctTerminateCause) VALUES \ # ('%{Acct-Session-Id}', '%{User-Name}', '%{NAS-IP-Address}', \ # '%{Framed-IP-Address}', '0', '0', '%{Acct-Session-Time}','');" # # Post-Auth = "INSERT INTO ${postauth_table} \ # (user, pass, reply, date) VALUES \ # ('%{User-Name}', '%{User-Password:-Chap-Password}', \ # '%{reply:Packet-Type}', '%S');" # } # # Create a unique accounting session Id. Many NASes re-use # or repeat values for Acct-Session-Id, causing no end of # confusion. # # This module will add a (probably) unique session id # to an accounting packet based on the attributes listed # below found in the packet. See doc/rlm_acct_unique for # more information. # acct_unique { key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port" } # Include another file that has the SQL-related configuration. # This is another file only because it tends to be big. # # The following configuration file is for use with MySQL. # # For Postgresql, use: ${confdir}/postgresql.conf # For MS-SQL, use: ${confdir}/mssql.conf # For Oracle, use: ${confdir}/oraclesql.conf # $INCLUDE ${confdir}/sql.conf # For Cisco VoIP specific accounting with Postgresql, # use: ${confdir}/pgsql-voip.conf # # You will also need the sql schema from: # src/billing/cisco_h323_db_schema-postgres.sql # Note: This config can be use AS WELL AS the standard sql # config if you need SQL based Auth # Write a 'utmp' style file, of which users are currently # logged in, and where they've logged in from. # # This file is used mainly for Simultaneous-Use checking, # and also 'radwho', to see who's currently logged in. # radutmp { # Where the file is stored. It's not a log file, # so it doesn't need rotating. # filename = ${logdir}/radutmp # The field in the packet to key on for the # 'user' name, If you have other fields which you want # to use to key on to control Simultaneous-Use, # then you can use them here. # # Note, however, that the size of the field in the # 'utmp' data structure is small, around 32 # characters, so that will limit the possible choices # of keys. # # You may want instead: %{Stripped-User-Name:-%{User-Name}} username = %{User-Name} # Whether or not we want to treat "user" the same # as "USER", or "User". Some systems have problems # with case sensitivity, so this should be set to # 'no' to enable the comparisons of the key attribute # to be case insensitive. # case_sensitive = yes # Accounting information may be lost, so the user MAY # have logged off of the NAS, but we haven't noticed. # If so, we can verify this information with the NAS, # # If we want to believe the 'utmp' file, then this # configuration entry can be set to 'no'. # check_with_nas = yes # Set the file permissions, as the contents of this file # are usually private. perm = 0600 callerid = "yes" } # "Safe" radutmp - does not contain caller ID, so it can be # world-readable, and radwho can work for normal users, without # exposing any information that isn't already exposed by who(1). # # This is another 'instance' of the radutmp module, but it is given # then name "sradutmp" to identify it later in the "accounting" # section. radutmp sradutmp { filename = ${logdir}/sradutmp perm = 0644 callerid = "no" } # attr_filter - filters the attributes received in replies from # proxied servers, to make sure we send back to our RADIUS client # only allowed attributes. attr_filter { attrsfile = ${confdir}/attrs } # counter module: # This module takes an attribute (count-attribute). # It also takes a key, and creates a counter for each unique # key. The count is incremented when accounting packets are # received by the server. The value of the increment depends # on the attribute type. # If the attribute is Acct-Session-Time or of an integer type we add the # value of the attribute. If it is anything else we increase the # counter by one. # # The 'reset' parameter defines when the counters are all reset to # zero. It can be hourly, daily, weekly, monthly or never. # # hourly: Reset on 00:00 of every hour # daily: Reset on 00:00:00 every day # weekly: Reset on 00:00:00 on sunday # monthly: Reset on 00:00:00 of the first day of each month # # It can also be user defined. It should be of the form: # num[hdwm] where: # h: hours, d: days, w: weeks, m: months # If the letter is ommited days will be assumed. In example: # reset = 10h (reset every 10 hours) # reset = 12 (reset every 12 days) # # # The check-name attribute defines an attribute which will be # registered by the counter module and can be used to set the # maximum allowed value for the counter after which the user # is rejected. # Something like: # # DEFAULT Max-Daily-Session := 36000 # Fall-Through = 1 # # You should add the counter module in the instantiate # section so that it registers check-name before the files # module reads the users file. # # If check-name is set and the user is to be rejected then we # send back a Reply-Message and we log a Failure-Message in # the radius.log # If the count attribute is Acct-Session-Time then on each login # we send back the remaining online time as a Session-Timeout attribute # # The counter-name can also be used instead of using the check-name # like below: # # DEFAULT Daily-Session-Time > 3600, Auth-Type = Reject # Reply-Message = "You've used up more than one hour today" # # The allowed-servicetype attribute can be used to only take # into account specific sessions. For example if a user first # logs in through a login menu and then selects ppp there will # be two sessions. One for Login-User and one for Framed-User # service type. We only need to take into account the second one. # # The module should be added in the instantiate, authorize and # accounting sections. Make sure that in the authorize # section it comes after any module which sets the # 'check-name' attribute. # counter daily { filename = ${raddbdir}/db.daily key = User-Name count-attribute = Acct-Session-Time reset = daily counter-name = Daily-Session-Time check-name = Max-Daily-Session allowed-servicetype = Framed-User cache-size = 5000 } # # This module is an SQL enabled version of the counter module. # # Rather than maintaining seperate (GDBM) databases of # accounting info for each counter, this module uses the data # stored in the raddacct table by the sql modules. This # module NEVER does any database INSERTs or UPDATEs. It is # totally dependent on the SQL module to process Accounting # packets. # # The 'sqlmod_inst' parameter holds the instance of the sql # module to use when querying the SQL database. Normally it # is just "sql". If you define more and one SQL module # instance (usually for failover situations), you can # specify which module has access to the Accounting Data # (radacct table). # # The 'reset' parameter defines when the counters are all # reset to zero. It can be hourly, daily, weekly, monthly or # never. It can also be user defined. It should be of the # form: # num[hdwm] where: # h: hours, d: days, w: weeks, m: months # If the letter is ommited days will be assumed. In example: # reset = 10h (reset every 10 hours) # reset = 12 (reset every 12 days) # # The 'key' parameter specifies the unique identifier for the # counter records (usually 'User-Name'). # # The 'query' parameter specifies the SQL query used to get # the current Counter value from the database. There are 3 # parameters that can be used in the query: # %k 'key' parameter # %b unix time value of beginning of reset period # %e unix time value of end of reset period # # The 'check-name' parameter is the name of the 'check' # attribute to use to access the counter in the 'users' file # or SQL radcheck or radcheckgroup tables. # # DEFAULT Max-Daily-Session > 3600, Auth-Type = Reject # Reply-Message = "You've used up more than one hour today" # sqlcounter dailycounter { counter-name = Daily-Session-Time check-name = Max-Daily-Session sqlmod-inst = sql key = User-Name reset = daily # This query properly handles calls that span from the # previous reset period into the current period but # involves more work for the SQL server than those # below # For mysql: query = "SELECT SUM(AcctSessionTime - \ GREATEST((%b - UNIX_TIMESTAMP(AcctStartTime)), 0)) \ FROM radacct WHERE UserName='%{%k}' AND \ UNIX_TIMESTAMP(AcctStartTime) + AcctSessionTime > '%b'" # For postgresql: # query = "SELECT SUM(AcctSessionTime - \ # GREATER((%b - AcctStartTime::ABSTIME::INT4), 0)) \ # FROM radacct WHERE UserName='%{%k}' AND \ # AcctStartTime::ABSTIME::INT4 + AcctSessionTime > '%b'" # This query ignores calls that started in a previous # reset period and continue into into this one. But it # is a little easier on the SQL server # For mysql: # query = "SELECT SUM(AcctSessionTime) FROM radacct WHERE \ # UserName='%{%k}' AND AcctStartTime > FROM_UNIXTIME('%b')" # For postgresql: # query = "SELECT SUM(AcctSessionTime) FROM radacct WHERE \ # UserName='%{%k}' AND AND AcctStartTime::ABSTIME::INT4 > '%b'" # This query is the same as above, but demonstrates an # additional counter parameter '%e' which is the # timestamp for the end of the period # For mysql: # query = "SELECT SUM(AcctSessionTime) FROM radacct \ # WHERE UserName='%{%k}' AND AcctStartTime BETWEEN \ # FROM_UNIXTIME('%b') AND FROM_UNIXTIME('%e')" # For postgresql: # query = "SELECT SUM(AcctSessionTime) FROM radacct \ # WHERE UserName='%{%k}' AND AcctStartTime::ABSTIME::INT4 \ # BETWEEN '%b' AND '%e'" } sqlcounter monthlycounter { counter-name = Monthly-Session-Time check-name = Max-Monthly-Session sqlmod-inst = sql key = User-Name reset = monthly # This query properly handles calls that span from the # previous reset period into the current period but # involves more work for the SQL server than those # below # The same notes above about the differences between mysql # versus postgres queries apply here. query = "SELECT SUM(AcctSessionTime - \ GREATEST((%b - UNIX_TIMESTAMP(AcctStartTime)), 0)) \ FROM radacct WHERE UserName='%{%k}' AND \ UNIX_TIMESTAMP(AcctStartTime) + AcctSessionTime > '%b'" # This query ignores calls that started in a previous # reset period and continue into into this one. But it # is a little easier on the SQL server # query = "SELECT SUM(AcctSessionTime) FROM radacct WHERE \ # UserName='%{%k}' AND AcctStartTime > FROM_UNIXTIME('%b')" # This query is the same as above, but demonstrates an # additional counter parameter '%e' which is the # timestamp for the end of the period # query = "SELECT SUM(AcctSessionTime) FROM radacct \ # WHERE UserName='%{%k}' AND AcctStartTime BETWEEN \ # FROM_UNIXTIME('%b') AND FROM_UNIXTIME('%e')" } # # The "always" module is here for debugging purposes. Each # instance simply returns the same result, always, without # doing anything. always fail { rcode = fail } always reject { rcode = reject } always ok { rcode = ok simulcount = 0 mpp = no } # # The 'expression' module currently has no configuration. # # This module is useful only for 'xlat'. To use it, # put 'exec' into the 'instantiate' section. You can then # do dynamic translation of attributes like: # # Attribute-Name = `%{expr:2 + 3 + %{exec: uid -u}}` # # The value of the attribute will be replaced with the output # of the program which is executed. Due to RADIUS protocol # limitations, any output over 253 bytes will be ignored. expr { } # # The 'digest' module currently has no configuration. # # "Digest" authentication against a Cisco SIP server. # See 'doc/rfc/draft-sterman-aaa-sip-00.txt' for details # on performing digest authentication for Cisco SIP servers. # digest { } # # Execute external programs # # This module is useful only for 'xlat'. To use it, # put 'exec' into the 'instantiate' section. You can then # do dynamic translation of attributes like: # # Attribute-Name = `%{exec:/path/to/program args}` # # The value of the attribute will be replaced with the output # of the program which is executed. Due to RADIUS protocol # limitations, any output over 253 bytes will be ignored. # # The RADIUS attributes from the user request will be placed # into environment variables of the executed program, as # described in 'doc/variables.txt' # exec { wait = yes input_pairs = request } # # This is a more general example of the execute module. # # This one is called "echo". # # Attribute-Name = `%{echo:/path/to/program args}` # # If you wish to execute an external program in more than # one section (e.g. 'authorize', 'pre_proxy', etc), then it # is probably best to define a different instance of the # 'exec' module for every section. # exec echo { # # Wait for the program to finish. # # If we do NOT wait, then the program is "fire and # forget", and any output attributes from it are ignored. # # If we are looking for the program to output # attributes, and want to add those attributes to the # request, then we MUST wait for the program to # finish, and therefore set 'wait=yes' # # allowed values: {no, yes} wait = yes # # The name of the program to execute, and it's # arguments. Dynamic translation is done on this # field, so things like the following example will # work. # program = "/bin/echo %{User-Name}" # # The attributes which are placed into the # environment variables for the program. # # Allowed values are: # # request attributes from the request # config attributes from the configuration items list # reply attributes from the reply # proxy-request attributes from the proxy request # proxy-reply attributes from the proxy reply # # Note that some attributes may not exist at some # stages. e.g. There may be no proxy-reply # attributes if this module is used in the # 'authorize' section. # input_pairs = request # # Where to place the output attributes (if any) from # the executed program. The values allowed, and the # restrictions as to availability, are the same as # for the input_pairs. # output_pairs = reply # # When to execute the program. If the packet # type does NOT match what's listed here, then # the module does NOT execute the program. # # For a list of allowed packet types, see # the 'dictionary' file, and look for VALUEs # of the Packet-Type attribute. # # By default, the module executes on ANY packet. # Un-comment out the following line to tell the # module to execute only if an Access-Accept is # being sent to the NAS. # #packet_type = Access-Accept } # Do server side ip pool management. Should be added in post-auth and # accounting sections. # # The module also requires the existance of the Pool-Name # attribute. That way the administrator can add the Pool-Name # attribute in the user profiles and use different pools # for different users. The Pool-Name attribute is a *check* item not # a reply item. # # Example: # radiusd.conf: ippool students { [...] } # users file : DEFAULT Group == students, Pool-Name := "students" # # ********* IF YOU CHANGE THE RANGE PARAMETERS YOU MUST ********* # ********* THEN ERASE THE DB FILES ********* # ippool main_pool { # range-start,range-stop: The start and end ip # addresses for the ip pool range-start = 192.168.1.1 range-stop = 192.168.3.254 # netmask: The network mask used for the ip's netmask = 255.255.255.0 # cache-size: The gdbm cache size for the db # files. Should be equal to the number of ip's # available in the ip pool cache-size = 800 # session-db: The main db file used to allocate ip's to clients session-db = ${raddbdir}/db.ippool # ip-index: Helper db index file used in multilink ip-index = ${raddbdir}/db.ipindex # override: Will this ippool override a Framed-IP-Address already set override = no # maximum-timeout: If not zero specifies the maximum time in seconds an # entry may be active. Default: 0 maximum-timeout = 0 } # $INCLUDE ${confdir}/sqlippool.conf # OTP token support. Not included by default. # $INCLUDE ${confdir}/otp.conf } # Instantiation # # This section orders the loading of the modules. Modules # listed here will get loaded BEFORE the later sections like # authorize, authenticate, etc. get examined. # # This section is not strictly needed. When a section like # authorize refers to a module, it's automatically loaded and # initialized. However, some modules may not be listed in any # of the following sections, so they can be listed here. # # Also, listing modules here ensures that you have control over # the order in which they are initalized. If one module needs # something defined by another module, you can list them in order # here, and ensure that the configuration will be OK. # instantiate { # # Allows the execution of external scripts. # The entire command line (and output) must fit into 253 bytes. # # e.g. Framed-Pool = `%{exec:/bin/echo foo}` exec # # The expression module doesn't do authorization, # authentication, or accounting. It only does dynamic # translation, of the form: # # Session-Timeout = `%{expr:2 + 3}` # # So the module needs to be instantiated, but CANNOT be # listed in any other section. See 'doc/rlm_expr' for # more information. # expr # # We add the counter module here so that it registers # the check-name attribute before any module which sets # it # daily } # Authorization. First preprocess (hints and huntgroups files), # then realms, and finally look in the "users" file. # # The order of the realm modules will determine the order that # we try to find a matching realm. # # Make *sure* that 'preprocess' comes before any realm if you # need to setup hints for the remote radius server authorize { # # The preprocess module takes care of sanitizing some bizarre # attributes in the request, and turning them into attributes # which are more standard. # # It takes care of processing the 'raddb/hints' and the # 'raddb/huntgroups' files. # # It also adds the %{Client-IP-Address} attribute to the request. preprocess # # If you want to have a log of authentication requests, # un-comment the following line, and the 'detail auth_log' # section, above. # auth_log # attr_filter # # The chap module will set 'Auth-Type := CHAP' if we are # handling a CHAP request and Auth-Type has not already been set chap # # If the users are logging in with an MS-CHAP-Challenge # attribute for authentication, the mschap module will find # the MS-CHAP-Challenge attribute, and add 'Auth-Type := MS-CHAP' # to the request, which will cause the server to then use # the mschap module for authentication. mschap # # If you have a Cisco SIP server authenticating against # FreeRADIUS, uncomment the following line, and the 'digest' # line in the 'authenticate' section. digest # # Look for IPASS style 'realm/', and if not found, look for # '@realm', and decide whether or not to proxy, based on # that. # IPASS # # If you are using multiple kinds of realms, you probably # want to set "ignore_null = yes" for all of them. # Otherwise, when the first style of realm doesn't match, # the other styles won't be checked. # suffix # ntdomain # # This module takes care of EAP-MD5, EAP-TLS, and EAP-LEAP # authentication. # # It also sets the EAP-Type attribute in the request # attribute list to the EAP type from the packet. # eap # # Read the 'users' file # files # # Look in an SQL database. The schema of the database # is meant to mirror the "users" file. # # See "Authorization Queries" in sql.conf sql # # If you are using /etc/smbpasswd, and are also doing # mschap authentication, the un-comment this line, and # configure the 'etc_smbpasswd' module, above. # etc_smbpasswd # # The ldap module will set Auth-Type to LDAP if it has not # already been set # ldap # # Enforce daily limits on time spent logged in. # daily # # Use the checkval module # checkval } # Authentication. # # # This section lists which modules are available for authentication. # Note that it does NOT mean 'try each module in order'. It means # that a module from the 'authorize' section adds a configuration # attribute 'Auth-Type := FOO'. That authentication type is then # used to pick the apropriate module from the list below. # # In general, you SHOULD NOT set the Auth-Type attribute. The server # will figure it out on its own, and will do the right thing. The # most common side effect of erroneously setting the Auth-Type # attribute is that one authentication method will work, but the # others will not. # # The common reasons to set the Auth-Type attribute by hand # is to either forcibly reject the user, or forcibly accept him. # authenticate { # # PAP authentication, when a back-end database listed # in the 'authorize' section supplies a password. The # password can be clear-text, or encrypted. Auth-Type PAP { pap } # # Most people want CHAP authentication # A back-end database listed in the 'authorize' section # MUST supply a CLEAR TEXT password. Encrypted passwords # won't work. Auth-Type CHAP { chap } # # MSCHAP authentication. Auth-Type MS-CHAP { mschap } # # If you have a Cisco SIP server authenticating against # FreeRADIUS, uncomment the following line, and the 'digest' # line in the 'authorize' section. digest # # Pluggable Authentication Modules. # pam # # See 'man getpwent' for information on how the 'unix' # module checks the users password. Note that packets # containing CHAP-Password attributes CANNOT be authenticated # against /etc/passwd! See the FAQ for details. # # unix # Uncomment it if you want to use ldap for authentication # # Note that this means "check plain-text password against # the ldap database", which means that EAP won't work, # as it does not supply a plain-text password. # Auth-Type LDAP { # ldap # } # # Allow EAP authentication. # eap } # # Pre-accounting. Decide which accounting type to use. # preacct { preprocess # # Ensure that we have a semi-unique identifier for every # request, and many NAS boxes are broken. acct_unique # # Look for IPASS-style 'realm/', and if not found, look for # '@realm', and decide whether or not to proxy, based on # that. # # Accounting requests are generally proxied to the same # home server as authentication requests. # IPASS suffix # ntdomain # # Read the 'acct_users' file files } # # Accounting. Log the accounting data. # accounting { # # Create a 'detail'ed log of the packets. # Note that accounting requests which are proxied # are also logged in the detail file. detail # daily # Update the wtmp file # # If you don't use "radlast", you can delete this line. unix # # For Simultaneous-Use tracking. # # Due to packet losses in the network, the data here # may be incorrect. There is little we can do about it. radutmp # sradutmp # Return an address to the IP Pool when we see a stop record. # main_pool # # Log traffic to an SQL database. # # See "Accounting queries" in sql.conf sql # # Instead of sending the query to the SQL server, # write it into a log file. # # sql_log # Cisco VoIP specific bulk accounting # pgsql-voip } # Session database, used for checking Simultaneous-Use. Either the radutmp # or rlm_sql module can handle this. # The rlm_sql module is *much* faster session { radutmp # # See "Simultaneous Use Checking Querie" in sql.conf sql } # Post-Authentication # Once we KNOW that the user has been authenticated, there are # additional steps we can take. post-auth { # Get an address from the IP Pool. # main_pool # # If you want to have a log of authentication replies, # un-comment the following line, and the 'detail reply_log' # section, above. # reply_log # # After authenticating the user, do another SQL query. # # See "Authentication Logging Queries" in sql.conf sql # # Instead of sending the query to the SQL server, # write it into a log file. # # sql_log # # Un-comment the following if you have set # 'edir_account_policy_check = yes' in the ldap module sub-section of # the 'modules' section. # # ldap # # Access-Reject packets are sent through the REJECT sub-section of the # post-auth section. # Uncomment the following and set the module name to the ldap instance # name if you have set 'edir_account_policy_check = yes' in the ldap # module sub-section of the 'modules' section. # # Post-Auth-Type REJECT { # insert-module-name-here # } } # # When the server decides to proxy a request to a home server, # the proxied request is first passed through the pre-proxy # stage. This stage can re-write the request, or decide to # cancel the proxy. # # Only a few modules currently have this method. # pre-proxy { # attr_rewrite # Uncomment the following line if you want to change attributes # as defined in the preproxy_users file. # files # If you want to have a log of packets proxied to a home # server, un-comment the following line, and the # 'detail pre_proxy_log' section, above. # pre_proxy_log } # # When the server receives a reply to a request it proxied # to a home server, the request may be massaged here, in the # post-proxy stage. # post-proxy { # If you want to have a log of replies from a home server, # un-comment the following line, and the 'detail post_proxy_log' # section, above. # post_proxy_log # attr_rewrite # Uncomment the following line if you want to filter replies from # remote proxies based on the rules defined in the 'attrs' file. # attr_filter # # If you are proxying LEAP, you MUST configure the EAP # module, and you MUST list it here, in the post-proxy # stage. # # You MUST also use the 'nostrip' option in the 'realm' # configuration. Otherwise, the User-Name attribute # in the proxied request will not match the user name # hidden inside of the EAP packet, and the end server will # reject the EAP request. # eap }

1 0

[OpenSER-Users] The problem of authentication radius(mysql) with openser
by zze-WU Yin RD-MAPS-LAN 18 Jul '07

18 Jul '07

Hi, I have installed openser-1.2.1-notls, freeradius-1.1.6, mysql-0.5.41, radiusclient-ng-0.5.2 successfully. Openser works well with no modification of the 'openser.cfg' and I can register a SIP telephone. The Openser reponses always 200 ok! And freeradius works well with the databases of mysql. When I make a 'radtest', I can received a 'access-request'. But when I need to use openser+freeradius+mysql. It seems that the authentification doesn't work. I have load the module 'auth_radius' and modified some another parametres of 'openser.cfg'. I think that may be the problem to register a user in the mysql tables. I just want a authentification with username and password. But I can not find a clear sample about that. Can you help me? YIN

1 0

[OpenSER-Users] The problem of authentication radius(mysql) with openser
by zze-WU Yin RD-MAPS-LAN 18 Jul '07

18 Jul '07

Hi, I have installed openser-1.2.1-notls, freeradius-1.1.6, mysql-0.5.41, radiusclient-ng-0.5.2 successfully. Openser works well with no modification of the 'openser.cfg' and I can register a SIP telephone. The Openser reponses always 200 ok! And freeradius works well with the databases of mysql. When I make a 'radtest', I can received a 'access-request'. But when I need to use openser+freeradius+mysql. It seems that the authentification doesn't work. I have load the module 'auth_radius' and modified some another parametres of 'openser.cfg'. I think that may be the problem to register a user in the mysql tables. I just want a authentification with username and password. But I can not find a clear sample about that. Can you help me? YIN

1 0

Re: [OpenSER-Users] Radius integration issue
by OpenSER ML 18 Jul '07

18 Jul '07

Hi Dan, I am running in debug mode, here is the output of FreeRadius which seems fine to me: rad_recv: Access-Request packet from host 192.168.2.80:35223, id=250, length=232 User-Name = "101(a)openser.org" Digest-Attributes = 0x0a05313031 Digest-Attributes = 0x010d6f70656e7365722e6f7267 Digest-Attributes = 0x022a34363961626230616465333832613934646432333533636264663264666438336231353933663564 Digest-Attributes = 0x04127369703a3139322e3136382e322e3830 Digest-Attributes = 0x030a5245474953544552 Digest-Attributes = 0x050661757468 Digest-Attributes = 0x090a3030303030303930 Digest-Attributes = 0x081235343038316466316439623562383564 Digest-Response = "d3ff78d09d9b2cefdce0c975b3c6fd26" Service-Type = IAPP-Register X-Ascend-PW-Lifetime = 0x313031 NAS-Port = 5060 NAS-IP-Address = 192.168.2.80 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 1124 modcall[authorize]: module "preprocess" returns ok for request 1124 radius_xlat: '/usr/local/freeradius/var/log/radius/radacct/192.168.2.80/auth-detail-20070716' rlm_detail: /usr/local/freeradius/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /usr/local/freeradius/var/log/radius/radacct/192.168.2.80/auth-detail-20070716 modcall[authorize]: module "auth_log" returns ok for request 1124 rlm_digest: Adding Auth-Type = DIGEST modcall[authorize]: module "digest" returns ok for request 1124 users: Matched entry 101(a)openser.org at line 53 modcall[authorize]: module "files" returns ok for request 1124 modcall: leaving group authorize (returns ok) for request 1124 rad_check_password: Found Auth-Type DIGEST auth: type "digest" Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 1124 rlm_digest: Converting Digest-Attributes to something sane... Digest-User-Name = "101" Digest-Realm = "openser.org" Digest-Nonce = "469abb0ade382a94dd2353cbdf2dfd83b1593f5d" Digest-URI = "sip:192.168.2.80" Digest-Method = "REGISTER" Digest-QOP = "auth" Digest-Nonce-Count = "00000090" Digest-CNonce = "54081df1d9b5b85d" A1 = 101:openser.org:101 A2 = REGISTER:sip:192.168.2.80 H(A1) = f195c177997cee336c919be9279c5703 H(A2) = 046d0643f281affab19fe62ffc848ab5 KD = f195c177997cee336c919be9279c5703:469abb0ade382a94dd2353cbdf2dfd83b1593f5d:00000090:54081df1d9b5b85d:auth:046d0643f281affab19fe62ffc848ab5 EXPECTED d3ff78d09d9b2cefdce0c975b3c6fd26 RECEIVED d3ff78d09d9b2cefdce0c975b3c6fd26 modcall[authenticate]: module "digest" returns ok for request 1124 modcall: leaving group authenticate (returns ok) for request 1124 Login OK: [101(a)openser.org/<no User-Password attribute>] (from client 192.168.2.80 port 5060) Sending Access-Accept of id 250 to 192.168.2.80 port 35223 Finished request 1124 Going to the next request Waking up in 6 seconds... Z2L ----- Original Message ----- From: "Dan-Cristian Bogos" <dan.bogos(a)gmail.com> To: openser(a)zap2link.com Sent: Wednesday, July 18, 2007 1:53:14 PM (GMT+0200) Asia/Jerusalem Subject: Re: [OpenSER-Users] Radius integration issue Hi, try running FreeRADIUS in debug mode, this will tell u more info regarding the cause of failure. To run FreeRADIUS in debug start it with -X option. Let us know about the results. Cheers, DanB On 7/18/07, OpenSER ML <openser(a)zap2link.com> wrote: > Hi All, > > I'm trying to connect OpenSER with FreeRadius. I've managed to get the digest authentication > going correctly, having the Radius respond with LOGIN OK for the requests that are in the users file. However, although the authentication process appears to succeed, the IP phone doesn't register to the OpenSER server. > > The following can be seen in the debug: > > 0(17821) SIP Request: > 0(17821) method: <REGISTER> > 0(17821) uri: <sip:192.168.2.80> > 0(17821) version: <SIP/2.0> > 0(17821) parse_headers: flags=2 > 0(17821) Found param type 232, <branch> = <z9hG4bK4d7202f23b6595fc>; state=16 > 0(17821) end of header reached, state=5 > 0(17821) parse_headers: Via found, flags=2 > 0(17821) parse_headers: this is the first via > 0(17821) After parse_msg... > 0(17821) preparing to run routing scripts... > 0(17821) parse_headers: flags=100 > 0(17821) DEBUG:parse_to:end of header reached, state=10 > 0(17821) DBUG:parse_to: display={}, ruri={sip:101@192.168.2.80;user=phone} > 0(17821) DEBUG: get_hdr_field: <To> [35]; uri=[sip:101@192.168.2.80;user=phone] > 0(17821) DEBUG: to body [<sip:101@192.168.2.80;user=phone> > ] > 0(17821) get_hdr_field: cseq <CSeq>: <20048> <REGISTER> > 0(17821) DEBUG:maxfwd:is_maxfwd_present: value = 70 > 0(17821) parse_headers: flags=200 > 0(17821) DEBUG: get_hdr_body : content_length=0 > 0(17821) found end of header > 0(17821) find_first_route: No Route headers found > 0(17821) loose_route: There is no Route HF > 0(17821) grep_sock_info - checking if host==us: 12==12 && [192.168.2.80] == [192.168.2.80] > 0(17821) grep_sock_info - checking if port 5060 matches port 5060 > 0(17821) grep_sock_info - checking if host==us: 12==12 && [192.168.2.80] == [192.168.2.80] > 0(17821) grep_sock_info - checking if port 5060 matches port 5060 > 0(17821) check_nonce(): comparing [469aba5f4ff6b78f7b9588ad19fc0ab514e709da] and [469aba5f4ff6b78f7b9588ad19fc0ab514e709da] > 0(17821) ERROR:auth_radius:radius_authorize_sterman: rc_auth failed > 0(17821) build_auth_hf(): 'WWW-Authenticate: Digest realm="openser.org", nonce="469aba5f4ff6b78f7b9588ad19fc0ab514e709da", qop="auth" > ' > 0(17821) parse_headers: flags=ffffffffffffffff > 0(17821) check_via_address(192.168.2.101, 192.168.2.101, 0) > 0(17821) DEBUG:destroy_avp_list: destroying list (nil) > 0(17821) receive_msg: cleaning up > > As you can surely see, the ERROR is somewhere in the authorization status. Now, I've verified > the secret key between the machine, and all seems to be in place - any pointers will be highly appreciated. > > Z2L > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users >

2 2

[OpenSER-Users] Radius integration issue
by Dan-Cristian Bogos 18 Jul '07

18 Jul '07

Hi, try running FreeRADIUS in debug mode, this will tell u more info regarding the cause of failure. To run FreeRADIUS in debug start it with -X option. Let us know about the results. Cheers, DanB On 7/18/07, OpenSER ML <openser(a)zap2link.com> wrote: > Hi All, > > I'm trying to connect OpenSER with FreeRadius. I've managed to get the digest authentication > going correctly, having the Radius respond with LOGIN OK for the requests that are in the users file. However, although the authentication process appears to succeed, the IP phone doesn't register to the OpenSER server. > > The following can be seen in the debug: > > 0(17821) SIP Request: > 0(17821) method: <REGISTER> > 0(17821) uri: <sip:192.168.2.80> > 0(17821) version: <SIP/2.0> > 0(17821) parse_headers: flags=2 > 0(17821) Found param type 232, <branch> = <z9hG4bK4d7202f23b6595fc>; state=16 > 0(17821) end of header reached, state=5 > 0(17821) parse_headers: Via found, flags=2 > 0(17821) parse_headers: this is the first via > 0(17821) After parse_msg... > 0(17821) preparing to run routing scripts... > 0(17821) parse_headers: flags=100 > 0(17821) DEBUG:parse_to:end of header reached, state=10 > 0(17821) DBUG:parse_to: display={}, ruri={sip:101@192.168.2.80;user=phone} > 0(17821) DEBUG: get_hdr_field: <To> [35]; uri=[sip:101@192.168.2.80;user=phone] > 0(17821) DEBUG: to body [<sip:101@192.168.2.80;user=phone> > ] > 0(17821) get_hdr_field: cseq <CSeq>: <20048> <REGISTER> > 0(17821) DEBUG:maxfwd:is_maxfwd_present: value = 70 > 0(17821) parse_headers: flags=200 > 0(17821) DEBUG: get_hdr_body : content_length=0 > 0(17821) found end of header > 0(17821) find_first_route: No Route headers found > 0(17821) loose_route: There is no Route HF > 0(17821) grep_sock_info - checking if host==us: 12==12 && [192.168.2.80] == [192.168.2.80] > 0(17821) grep_sock_info - checking if port 5060 matches port 5060 > 0(17821) grep_sock_info - checking if host==us: 12==12 && [192.168.2.80] == [192.168.2.80] > 0(17821) grep_sock_info - checking if port 5060 matches port 5060 > 0(17821) check_nonce(): comparing [469aba5f4ff6b78f7b9588ad19fc0ab514e709da] and [469aba5f4ff6b78f7b9588ad19fc0ab514e709da] > 0(17821) ERROR:auth_radius:radius_authorize_sterman: rc_auth failed > 0(17821) build_auth_hf(): 'WWW-Authenticate: Digest realm="openser.org", nonce="469aba5f4ff6b78f7b9588ad19fc0ab514e709da", qop="auth" > ' > 0(17821) parse_headers: flags=ffffffffffffffff > 0(17821) check_via_address(192.168.2.101, 192.168.2.101, 0) > 0(17821) DEBUG:destroy_avp_list: destroying list (nil) > 0(17821) receive_msg: cleaning up > > As you can surely see, the ERROR is somewhere in the authorization status. Now, I've verified > the secret key between the machine, and all seems to be in place - any pointers will be highly appreciated. > > Z2L > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users >

1 0

[OpenSER-Users] Radius integration issue
by OpenSER ML 18 Jul '07

18 Jul '07

Hi All, I'm trying to connect OpenSER with FreeRadius. I've managed to get the digest authentication going correctly, having the Radius respond with LOGIN OK for the requests that are in the users file. However, although the authentication process appears to succeed, the IP phone doesn't register to the OpenSER server. The following can be seen in the debug: 0(17821) SIP Request: 0(17821) method: <REGISTER> 0(17821) uri: <sip:192.168.2.80> 0(17821) version: <SIP/2.0> 0(17821) parse_headers: flags=2 0(17821) Found param type 232, <branch> = <z9hG4bK4d7202f23b6595fc>; state=16 0(17821) end of header reached, state=5 0(17821) parse_headers: Via found, flags=2 0(17821) parse_headers: this is the first via 0(17821) After parse_msg... 0(17821) preparing to run routing scripts... 0(17821) parse_headers: flags=100 0(17821) DEBUG:parse_to:end of header reached, state=10 0(17821) DBUG:parse_to: display={}, ruri={sip:101@192.168.2.80;user=phone} 0(17821) DEBUG: get_hdr_field: <To> [35]; uri=[sip:101@192.168.2.80;user=phone] 0(17821) DEBUG: to body [<sip:101@192.168.2.80;user=phone> ] 0(17821) get_hdr_field: cseq <CSeq>: <20048> <REGISTER> 0(17821) DEBUG:maxfwd:is_maxfwd_present: value = 70 0(17821) parse_headers: flags=200 0(17821) DEBUG: get_hdr_body : content_length=0 0(17821) found end of header 0(17821) find_first_route: No Route headers found 0(17821) loose_route: There is no Route HF 0(17821) grep_sock_info - checking if host==us: 12==12 && [192.168.2.80] == [192.168.2.80] 0(17821) grep_sock_info - checking if port 5060 matches port 5060 0(17821) grep_sock_info - checking if host==us: 12==12 && [192.168.2.80] == [192.168.2.80] 0(17821) grep_sock_info - checking if port 5060 matches port 5060 0(17821) check_nonce(): comparing [469aba5f4ff6b78f7b9588ad19fc0ab514e709da] and [469aba5f4ff6b78f7b9588ad19fc0ab514e709da] 0(17821) ERROR:auth_radius:radius_authorize_sterman: rc_auth failed 0(17821) build_auth_hf(): 'WWW-Authenticate: Digest realm="openser.org", nonce="469aba5f4ff6b78f7b9588ad19fc0ab514e709da", qop="auth" ' 0(17821) parse_headers: flags=ffffffffffffffff 0(17821) check_via_address(192.168.2.101, 192.168.2.101, 0) 0(17821) DEBUG:destroy_avp_list: destroying list (nil) 0(17821) receive_msg: cleaning up As you can surely see, the ERROR is somewhere in the authorization status. Now, I've verified the secret key between the machine, and all seems to be in place - any pointers will be highly appreciated. Z2L

1 0

Re: [OpenSER-Users] OpenSER + OPTIONS module
by Iñaki Baz Castillo 18 Jul '07

18 Jul '07

El Monday 16 July 2007 18:30:20 Marc LEURENT escribió: > I'm using the following config but it's still not working with openwengo > and sjphone... Strange > Any idea??? > > if (uri==myself) { > if (method==OPTIONS){ > if (uri=~"sip:ping[@]+.*") { > rewriteuri("sip:sip.test.fr"); > xlog("URI after rewriteuri() = $ru \r\n"); > }; > if (! uri=~"sip:.*[@]+.*") { Add here: xlog("URI again = $ru \r\n"); > options_reply(); > }; > }; > }; -- Iñaki Baz Castillo ibc(a)in.ilimit.es

2 1

Re: [OpenSER-Users] OpenSer and FreeRadius implementation
by OpenSer ML 18 Jul '07

18 Jul '07

Please give me a bit more credit than that, I had been using Linux for the past 10 years ;-) Although, from my previous questions, one can easily assume I'm a linux newbie :-D Z2L ----- Original Message ----- From: "raviprakash sunkara" <sunkara.raviprakash.feb14(a)gmail.com> To: openser(a)zap2link.com Sent: Wednesday, July 18, 2007 10:59:06 AM (GMT+0200) Asia/Jerusalem Subject: Re: [OpenSER-Users] OpenSer and FreeRadius implementation hi oops this versio is working fine did u try ldconfig v , to load the library files On 7/18/07 , OpenSer ML < openser(a)zap2link.com > wrote: Hi Neeraj, Can you please specify the versions of OpenSER and FreeRadius you are using? I'm trying to use OpenSER 1.2.1 and FreeRadius 1.1.6 Regards, Z2L ----- Original Message ----- From: "Neeraj Gupta" < Neeraj.Gupta(a)Sun.COM > To: openser(a)zap2link.com Cc: "users" < users(a)openser.org > Sent: Wednesday, July 18, 2007 1:20:11 AM (GMT+0200) Asia/Jerusalem Subject: Re: [OpenSER-Users] OpenSer and FreeRadius implementation Ok, I will paste critical configs in email. You need to setup radius as usual and copy dictionary files as usual. /etc/openser.cfg: # # $Id$ # # radius config script # # ----------- global configuration parameters ------------------------ debug=0 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E) check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=4 listen=udp:yy.yy.yy.yy listen=udp:xx.xx.xx.xx alias= sfbay.sun.com avp_aliases="day=i:101;time=i:102" #fifo="/tmp/openser_fifo" # ------------------ module loading ---------------------------------- #mpath="/usr/local/openser-1.0.1/lib/openser/modules" mpath="/usr/local/lib64/openser/modules" #loadmodule "mysql.so" loadmodule "sl.so" loadmodule "tm.so" loadmodule "rr.so" loadmodule "maxfwd.so" loadmodule "avpops.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "xlog.so" loadmodule "uri.so" loadmodule " acc.so" loadmodule "auth.so" loadmodule "auth_radius.so" loadmodule "group_radius.so" loadmodule "avp_radius.so" # ----------------- setting module-specific parameters --------------- # -- usrloc params -- #modparam("usrloc","db_url","mysql://openser:openserrw@localhost/openser") # neeraj changed to 0 from 2 modparam("usrloc", "db_mode", 0) # -- acc params -- modparam("acc", "radius_flag", 1) modparam("acc", "radius_missed_flag", 2) modparam("acc", "log_flag", 1) modparam("acc", "log_missed_flag", 1) modparam("acc", "service_type", 15) modparam("acc", "radius_extra", "Sip-Src-IP=$si;Sip-Src-Port=$sp") modparam("acc|auth_radius|group_radius|avp_radius", "radius_config", "/etc/radiusclient-ng/radiusclient.conf") # -- group_radius params -- modparam("group_radius", "use_domain", 1) # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) # ------------------------- request routing logic ------------------- # main routing logic route{ # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); }; # check if user is suspended ###if(is_method("REGISTER|INVITE|MESSAGE|OPTIONS|SUBSCRIBE")) { ### if (radius_is_user_in("From", "suspended")) { ### sl_send_reply("403", "Forbidden - suspended"); ### 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"); if(is_method("BYE")) { # log it all the time acc_rad_request("200 ok"); acc_log_request("200 ok"); } route(1); }; if(is_method("INVITE") && !has_totag()) { # set the acc flags setflag(1); setflag(2); }; if (!uri==myself) { # check if user is allowed to do voip calls to other domains if(is_method("INVITE|MESSAGE")) { if (!radius_is_user_in("From", "voip")) { sl_send_reply("403", "Forbidden VoIP"); exit; }; }; # mark routing logic in request append_hf("P-hint: outbound\r\n"); 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) { # authenticate registers if (method=="REGISTER") { if (!radius_www_authorize("")) { www_challenge("", "1"); exit; }; # check the src ip address # no need to use this now. tested OK ###if(!avp_check("$avp(i:2)", "eq/$src_ip/ig")) { ### sl_send_reply("403", "Forbidden IP"); ### exit; ###}; save("location"); exit; }; # calls to pstn if(uri=~"sip:00[1-9][0-9]+@") { if(is_method("INVITE") && !has_totag()) { if (!radius_is_user_in("From", "pstn")) { sl_send_reply("403", "Forbidden PSTN"); exit; }; }; # set gateway address rewritehostport(" 10.10.10.10:5090 "); route(1); }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { # log to acc as missed call acc_rad_request("404 Not Found"); acc_log_request("404 Not Found"); sl_send_reply("404", "Not Found"); exit; }; append_hf("P-hint: usrloc applied\r\n"); }; route(1); } # generic forward route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; exit; } /etc/radiusclient-ng/servers: xx.xx.xx.xx test1234 yy.yy.yy.yy test1234 /etc/radiusclient-ng/radiusclient.conf: <snip> # neeraj authserver xx.xx.xx.xx:1812 # RADIUS server to use for accouting requests. All that I # said for authserver applies, too. # # neeraj #acctserver localhost acctserver xx.xx.xx.xx :1813 <snip> Neeraj Gupta wrote: Yes. I have this working.. all with latest pieces of software on Sun SPARC Solaris 10. What exactly do you need ? -Neeraj OpenSER ML wrote: Hi All, Ok, I'm a bit mixed up here, the documents are simply not cutting it. I'm wondering if any of you have a working OpenSER + FreeRadius configuration that I can look at and extrapulate my required settings? I've gone over all the material I could find, but all of it reverts back to the outdated how-to on the FreeRadius website. Assistance would be highly appreciated. Regards, Z2L _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users -- ------------------------------------------------------------- o Neeraj Gupta email: neeraj.gupta(a)sun.com o Netra Systems & Networking phone: +1(408) 276-7214 x71214 o Sun Microsystems, Inc. fax : +1(408) 276-4552 o 4120 Network Circle, USCA12-216, Santa Clara, CA 95054, USA ------------------------------------------------------------- _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users -- Thanks &Regards Ravi Prakash Sunkara

1 0

[OpenSER-Users] OpenSer and FreeRadius implementation
by OpenSER ML 18 Jul '07

18 Jul '07

Hi All, Ok, I'm a bit mixed up here, the documents are simply not cutting it. I'm wondering if any of you have a working OpenSER + FreeRadius configuration that I can look at and extrapulate my required settings? I've gone over all the material I could find, but all of it reverts back to the outdated how-to on the FreeRadius website. Assistance would be highly appreciated. Regards, Z2L

2 3

[OpenSER-Users] softswitch with openser
by Ashish Barot 18 Jul '07

18 Jul '07

Respected sir, can you pl. help me out. i need to know that, can we use open ser to build softswitch which had features like class 4. and yes, then is there any guideline for that. so i can move ahead in that direction./ pl. any little help will be appiciate. Thanks. Best Regards, Ashi.

2 1

[OpenSER-Users] RADIUS and Local database lookup on register
by liran tal 18 Jul '07

18 Jul '07

Hey everyone, I was wondering if it's possible to combine the two methods of lookup so that a user can authenticate to both radius and local database (on the one that he is defined). to authenticate via radius it is done in my register section like this: if (!radius_www_authorize("")) { www_challenge("","0"); exit; }; and so I was wondering if it's possible to do something like this: if ( (!www_authorize("","subscriber")) || (!radius_www_authorize("")) ) { www_challenge("","0"); exit; }; Thanks, Lir.

2 1

[OpenSER-Users] Slightly OT: Anyone used RLM_PERL on FreeRadius with OpenSER?
by openser＠zap2link.com 18 Jul '07

18 Jul '07

Hi All, I'm trying to get FreeRadius to work with rlm_radius, but it would appear that although my perl script is loaded - it won't authenticate with it. Anyone ever worked with this before? Regards, Zap2Link

2 1

[OpenSER-Users] OpenSER not sending User-Password to Radius Server
by OpenSer ML 17 Jul '07

17 Jul '07

Hi All, I seem to have run into a situation where OpenSER doesn't send the user-password to the Radius server, upon initiating the Register method. The following information is received at the radius end: rad_recv: Access-Request packet from host 192.168.2.80:48582, id=200, length=194 User-Name = "101(a)192.168.2.80" Digest-Attributes = 0x0a05313031 Digest-Attributes = 0x010e3139322e3136382e322e3830 Digest-Attributes = 0x022a34363961326338396334343963303038323664396265313331653431376334316333303763376134 Digest-Attributes = 0x04127369703a3139322e3136382e322e3830 Digest-Attributes = 0x030a5245474953544552 Digest-Response = "8a61cba1c0729fa70929a115c6ae7c31" Service-Type = Authenticate-Only X-Ascend-PW-Lifetime = 0x313031 NAS-Port = 5060 NAS-IP-Address = 192.168.2.80 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 75 perl_pool: item 0x98baa10 asigned new request. Handled so far: 3 found interpetator at address 0x98baa10 rlm_perl: RAD_REQUEST: X-Ascend-PW-Lifetime = 0x313031 rlm_perl: RAD_REQUEST: Digest-Response = 8a61cba1c0729fa70929a115c6ae7c31 rlm_perl: RAD_REQUEST: User-Name = 101(a)192.168.2.80 rlm_perl: RAD_REQUEST: Service-Type = Authenticate-Only rlm_perl: RAD_REQUEST: NAS-IP-Address = 192.168.2.80 rlm_perl: RAD_REQUEST: NAS-Port = 5060 rlm_perl: RAD_REQUEST: Digest-Attributes = ARRAY(0x99f368c) perl_pool total/active/spare [32/0/32] This clearly shows that the User-Password attribute is not sent. Anyone can point me at the direction to look? z2l

2 1

[OpenSER-Users] parameter <fr_inv_timer> not found in module <lcr>
by adrien plessis 17 Jul '07

17 Jul '07

Hi It's my first message and i am not accustomed. I have install OpenSER 1.2.1 last month but i have bug because i use a t_relay with a renegociation of codec. I have install OpenSER 1.3.1 but i have one error when i lunch openser, i have error: 0(24405) set_mod_param_regex: parameter <fr_inv_timer> not found in module <lcr> 0(24405) parse error (49,19-20): Can't set module parameter I have not modify my config file i dont understand. please if you have already see My openser.cfg: #### #### ----------- global configuration parameters ------------------------ debug=4 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=yes# (cmd line: -E) check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) listen=xx.xxx.xxx.xx port=5060 children=4 # fifo="/tmp/ser_fifo" ####----------------------------------------------------------------------- #### #### #### ------------------ module loading ---------------------------------- loadmodule "/usr/lib/openser/modules/mysql.so" loadmodule "/usr/lib/openser/modules/nathelper.so" loadmodule "/usr/lib/openser/modules/sl.so" loadmodule "/usr/lib/openser/modules/tm.so" loadmodule "/usr/lib/openser/modules/rr.so" loadmodule "/usr/lib/openser/modules/maxfwd.so" loadmodule "/usr/lib/openser/modules/lcr.so" loadmodule "/usr/lib/openser/modules/acc.so" loadmodule "/usr/lib/openser/modules/usrloc.so" loadmodule "/usr/lib/openser/modules/registrar.so" ####------------------------------------------------------------------------ #### #### #### ----------------- setting module-specific parameters --------------- #modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo") ########################### Least Cost routing ############################# modparam("lcr","db_url", "mysql://root:Gabriel0$@localhost/openser") modparam("lcr","gw_table","gw") modparam("lcr","gw_name_column","gw_name") modparam("lcr","ip_addr_column","ip_addr") modparam("lcr","port_column","port") #modparam("lcr","uri_scheme_column","uri_scheme") #modparam("lcr","transport_column","transport") modparam("lcr","grp_id_column","grp_id") modparam("lcr","lcr_table","lcr") modparam("lcr","prefix_column","prefix") modparam("lcr","from_uri_column","from_uri") modparam("lcr","priority_column","priority") #modparam("lcr","gw_uri_avp","1400") modparam("lcr","contact_avp","1401") modparam("lcr","fr_inv_timer_avp","fr_inv_timer_avp") #modparam("lcr","rpid_avp","rpid") modparam("lcr","fr_inv_timer",90) modparam("lcr","fr_inv_timer_next",30) ########################### RR shit ######################################### modparam("rr","enable_full_lr",1) ########################### ACC ############################################# modparam("acc","db_url", "mysql://root:Gabriel0$@localhost/openser") modparam("acc", "db_flag", 2) ############################ usrloc params ################################## modparam("usrloc", "db_url", "mysql://root:Gabriel0$@localhost/openser") modparam("usrloc", "db_mode", 3) ####------------------------------------------------------------------------- #### #### ####---------------------------- Routing ------------------------------------ route { ############################## Sanity checks ################################# if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); }; if (msg:len >= max_len ) { sl_send_reply("513", "Message too big"); }; ########################## Record route for NAT ################################ if(!method=="REGISTER") { record_route(); }; ########################## Register ########################################### if (method=="REGISTER") { if (uri==myself) { sl_send_reply("100", "Trying"); if(!save("location")) { sl_reply_error(); }; exit; } else { sl_send_reply("403", "Forbidden"); exit; }; }; ############################# if(loose_route()) { route(1); }; ############################ Least Cost Routing ################################### if(!load_gws()) { sl_send_reply("500", "Internal server error, unable to load gateways"); } if(!next_gw()) { sl_send_reply("503", "Service not available, no gateways found"); }; ################################################################################### route(1); } route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP setflag(2); if(method=="INVITE") { force_rtp_proxy(); t_on_reply("1"); }; if (!t_relay()) { sl_reply_error(); }; } onreply_route[1] { setflag(2); if (status=~"[12]0-90-9") { force_rtp_proxy(); }; } ####-------------------------------------------------------------------------------------------- #### I have this when i started openser : 0(24405) loading module /usr/local/lib/openser/modules/mysql.so 0(24405) loading module /usr/local/lib/openser/modules/nathelper.so 0(24405) loading module /usr/local/lib/openser/modules/sl.so 0(24405) loading module /usr/local/lib/openser/modules/tm.so 0(24405) DEBUG: register_pv: tm 0(24405) xl_add_extra_spec: extra items list is not initialized 0(24405) xl_add_extra_spec: inserting extra item [T_branch_idx] at [0] 0(24405) xl_add_extra_spec: inserting extra item [T_reply_code] at [1] 0(24405) loading module /usr/local/lib/openser/modules/rr.so 0(24405) loading module /usr/local/lib/openser/modules/maxfwd.so 0(24405) loading module /usr/local/lib/openser/modules/lcr.so 0(24405) loading module /usr/local/lib/openser/modules/acc.so 0(24405) loading module /usr/local/lib/openser/modules/usrloc.so 0(24405) loading module /usr/local/lib/openser/modules/registrar.so 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <db_url> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <gw_table> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <gw_name_column> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <ip_addr_column> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <port_column> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <uri_scheme_column> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <transport_column> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <grp_id_column> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <lcr_table> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <prefix_column> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <from_uri_column> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <priority_column> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <gw_uri_avp> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <contact_avp> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <fr_inv_timer_avp> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <rpid_avp> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: parameter <fr_inv_timer> not found in module <lcr> 0(24405) parse error (49,19-20): Can't set module parameter 0(24405) set_mod_param_regex: lcr matches module lcr 0(24405) set_mod_param_regex: found <fr_inv_timer_next> in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) set_mod_param_regex: rr matches module rr 0(24405) set_mod_param_regex: found <enable_full_lr> in module rr [/usr/local/lib/openser/modules/rr.so] 0(24405) set_mod_param_regex: acc matches module acc 0(24405) set_mod_param_regex: found <db_url> in module acc [/usr/local/lib/openser/modules/acc.so] 0(24405) set_mod_param_regex: acc matches module acc 0(24405) set_mod_param_regex: found <db_flag> in module acc [/usr/local/lib/openser/modules/acc.so] 0(24405) set_mod_param_regex: usrloc matches module usrloc 0(24405) set_mod_param_regex: found <db_url> in module usrloc [/usr/local/lib/openser/modules/usrloc.so] 0(24405) set_mod_param_regex: usrloc matches module usrloc 0(24405) set_mod_param_regex: found <db_mode> in module usrloc [/usr/local/lib/openser/modules/usrloc.so] 0(24405) find_cmd_export_t: found <mf_process_maxfwd_header>(1) in module maxfwd [/usr/local/lib/openser/modules/maxfwd.so] 0(24405) find_cmd_export_t: found <sl_send_reply>(2) in module sl [/usr/local/lib/openser/modules/sl.so] 0(24405) find_cmd_export_t: found <sl_send_reply>(2) in module sl [/usr/local/lib/openser/modules/sl.so] 0(24405) find_cmd_export_t: found <record_route>(0) in module rr [/usr/local/lib/openser/modules/rr.so] 0(24405) find_cmd_export_t: found <sl_send_reply>(2) in module sl [/usr/local/lib/openser/modules/sl.so] 0(24405) find_cmd_export_t: found <save>(1) in module registrar [/usr/local/lib/openser/modules/registrar.so] 0(24405) find_cmd_export_t: found <sl_reply_error>(0) in module sl [/usr/local/lib/openser/modules/sl.so] 0(24405) find_cmd_export_t: found <sl_send_reply>(2) in module sl [/usr/local/lib/openser/modules/sl.so] 0(24405) find_cmd_export_t: found <loose_route>(0) in module rr [/usr/local/lib/openser/modules/rr.so] 0(24405) find_cmd_export_t: found <load_gws>(0) in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) find_cmd_export_t: found <sl_send_reply>(2) in module sl [/usr/local/lib/openser/modules/sl.so] 0(24405) find_cmd_export_t: found <next_gw>(0) in module lcr [/usr/local/lib/openser/modules/lcr.so] 0(24405) find_cmd_export_t: found <sl_send_reply>(2) in module sl [/usr/local/lib/openser/modules/sl.so] 0(24405) find_cmd_export_t: found <force_rtp_proxy>(0) in module nathelper [/usr/local/lib/openser/modules/nathelper.so] 0(24405) find_cmd_export_t: found <t_on_reply>(1) in module tm [/usr/local/lib/openser/modules/tm.so] 0(24405) find_cmd_export_t: found <t_relay>(0) in module tm [/usr/local/lib/openser/modules/tm.so] 0(24405) find_cmd_export_t: found <sl_reply_error>(0) in module sl [/usr/local/lib/openser/modules/sl.so] 0(24405) find_cmd_export_t: found <force_rtp_proxy>(0) in module nathelper [/usr/local/lib/openser/modules/nathelper.so] ERROR: bad config file (1 errors) 0(24405) DEBUG: tm_shutdown : start 0(24405) DEBUG: tm_shutdown : emptying hash table 0(24405) DEBUG: tm_shutdown : releasing timers 0(24405) DEBUG: tm_shutdown : removing semaphores 0(24405) DEBUG: tm_shutdown : destroying tmcb lists 0(24405) DEBUG: tm_shutdown : done 0(24405) shm_mem_destroy

2 1

[OpenSER-Users] LCR
by Gerson Matiolli 17 Jul '07

17 Jul '07

I have 2500 lines in table LCR, but to openser recognizes only 255. How I can change this?

2 1

[Serusers] loose_route behaviour, detecting single Route with myself
by JF 17 Jul '07

17 Jul '07

Hi all, When SER receives an INVITE with a single Route header pointing to itself, it's supposed to delete it and process the message as if no Route header was there in the first place. This is what RFC3261 mandates, right? But currently the loose_route function returns true to the script in this case, just like when more Route headers are present. So I have some routing logic for when no Route headers are present, and if I want to apply the same routing logic to the case when there is a single Route header pointing to myself (naturally, as it's the same as if no Route header was present), I currently have to replicate the same routing logic inside the if (loose_route())... Or is there an other way? Do I have to develop my own module function or use some regexp search from the script to detect if there are more Routes besides myself before I call loose_route? The best would be to change loose_route to return false and just remove the Route header pointing to myself when there are no more Route headers in the message... what do you think? JF

12 59

[OpenSER-Users] media not accpetable with outgoing call on cisco
by laurent schweizer 17 Jul '07

17 Jul '07

Hello, I have a problem with a cisco GW, if i only set g711 ulaw or alow as codec in my ata the the GW return a media not acceptable error. but If i add the g729 codec the all is ok. I see in the config of the cisco where to define codec for imcoming call but not for outgoing *Jul 17 15:57:02.604: Received: INVITE sip:0041787518551@192.168.0.110 SIP/2.0 Via: SIP/2.0/UDP 192.168.0.107:5070;branch=z9hG4bK5f66.fc82e301.0 To: <sip:0041787518551@192.168.0.110> From: 021111111 <sip:021111111@peoplefone.ch >;tag=27B98752-469CEA8A0002F2E4-5F903B30 CSeq: 10 INVITE Call-ID: 1973211C-469CEA8A0002F2EA-5F903B30(a)212.203.123.82 Content-Length: 250 User-Agent: OpenSER (1.2.1-notls (i386/linux)) Contact: <sip:sems@192.168.0.107:5070> P-MsgFlags: 0 billingid: 106 accountid: 28928 Remote-Party-ID: <sip:0445532001@192.168.0.106 >;party=calling;id-type=subscriber;screen=yes Content-Type: application/sdp v=0 o=MxSIP 0 198 IN IP4 192.168.0.249 s=SIP Call c=IN IP4 200.200.100.106 t=0 0 m=audio 39318 RTP/AVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=direction:active a=nortpproxy:yes *Jul 17 15:57:02.608: 0x64C01D00 : State change from (STATE_NONE, SUBSTATE_NONE) to (STATE_IDLE, SUBSTATE_NONE) *Jul 17 15:57:02.608: sipSPIStreamTypeAndDtmfRelay: ERROR - no voice codec and no dtmf-relay match *Jul 17 15:57:02.608: sipSPIDoAudioNegotiation: Media negotiation failed for m-line 1 *Jul 17 15:57:02.608: sipSPIDoMediaNegotiation: ERROR - no valid fax or audio streams *Jul 17 15:57:02.608: sipSPIHandleInviteMedia: Media Negotiation failed for an incoming call - Sending 488 *Jul 17 15:57:02.608: 0x64C01D00 : State change from (STATE_IDLE, SUBSTATE_NONE) to (STATE_DISCONNECTING, SUBSTATE_NONE) *Jul 17 15:57:02.608: Sent: SIP/2.0 488 Not Acceptable Media Via: SIP/2.0/UDP 192.168.0.107:5070;branch=z9hG4bK5f66.fc82e301.0 From: 021111111 <sip:021111111@peoplefone.ch >;tag=27B98752-469CEA8A0002F2E4-5F903B30 To: <sip:0041787518551@192.168.0.110>;tag=C0E57710-2347 Date: Tue, 17 Jul 2007 15:57:02 GMT Call-ID: 1973211C-469CEA8A0002F2EA-5F903B30(a)212.203.123.82 Server: Cisco-SIPGateway/IOS-12.x CSeq: 10 INVITE Allow-Events: telephone-event Content-Length: 0

2 1

[OpenSER-Users] imc module, any help?
by Iñaki Baz Castillo 17 Jul '07

17 Jul '07

Hi, I'm trying to configure the imc module for IM chat rooms and I get nothing. My conf related to this is: ------------------------------ modparam("imc", "db_url", "mysql://openser:openserrw@localhost/openser") if(method=="MESSAGE") { if (uri=~ "sip:chat1@") { imc_manager(); } } ------------------------------ Of course "chat1" doesn't exist in subscription o location table. So I open Linphone and send a message to "chat1(a)domain.org": #create test_room and I get in Linphone: "[<sip:test_room@openser.ilimit.es>] :*** room was created" And in fifo I see: ~$ openserctl fifo imc_list_rooms database engine 'MYSQL' loaded Control engine 'FIFO' loaded entering fifo_cmd imc_list_rooms 200 OK ROOM:: URI=sip:chat1@domain.org MEMBERS=0 OWNER=sip:810@domain.org But if I send a message to "test_room(a)domain.org" I get a 404 in OpenSer. And now, what more? I've tryed with #join chat1 but no members are added anywhere. So I'd appreciate a help with this since I don't find enough information about this module. PD: Why the MySQL tables imc_rooms and imc_members are always empty when "openserctl fifo imc_list_rooms" shows me the created rooms? Thanks a lot. -- Iñaki Baz Castillo ibc(a)in.ilimit.es

2 2

Re: [Serusers] loose_route behaviour, detecting single Route with myself
by Jiri Kuthan 17 Jul '07

17 Jul '07

Not sure it is worth patching the code which is IMO working. If I understand it right, you are having tel URI in Route? However this might have happened, that seems little sensible to me. The point is that tel URI is used to decouple a PSTN destination from a possible path via IP netowrk, whereas Route is intended to lay down such a path. Putting these two things together appears of limited use value to me. Anyhow, would you mind sending a dump of the SIP request in question -- I'm a bit confused what situation we are actually solving. -jiri At 19:46 10/07/2007, JF wrote: >no comments? > >On 6/28/07, JF <jfkavaka(a)gmail.com> wrote: >> I would propose to simply apply this patch to modules/rr/loose.c: >> >> @@ -1069,8 +1069,8 @@ >> return -1; >> } >> >> - if (is_myself(&_m->parsed_uri.host, _m->parsed_uri.port_no) >> - || _m->parsed_uri.type==TEL_URI_T || >> _m->parsed_uri.type==TELS_URI_T) { >> + if (_m->parsed_uri.type==TEL_URI_T || _m->parsed_uri.type==TELS_URI_T || >> + is_myself(&_m->parsed_uri.host, >> _m->parsed_uri.port_no)) { >> DBG("loose_route: RURI is myself (or tel URI)\n"); >> if ((ret = is_myself(&puri.host, puri.port_no)) == 1 && >> !(enable_double_rr && is_2rr(&puri.params))) { >> >> >> JF >> >> On 6/22/07, Greger Viken Teigre <greger(a)teigre.com> wrote: >> > This seems like a corner case where the tel uri with no domain results in maybe a bit unfortunate return code from loose_route. >> > Comments anyone? >> > g-) >> > >> > >> > ------- Original message ------- >> > From: JF <jfkavaka(a)gmail.com> >> > Cc: serusers(a)iptel.org, openimscore-cscf(a)lists.berlios.de >> > Sent: 22.6.'07, 11:11 >> > >> > > Thanks Greger, >> > > >> > > The problem is related to the fact that the Req-URI is a tel-URI. >> > > I had to work around it in the script by not letting loose_route get >> > > called when the URI is a tel URI. >> > > >> > > In loose.c, loose_route() says (by looking at the log): >> > > DBG("loose_route: RURI is NOT myself\n"); >> > > because Req-URI doesn't have a host part. >> > > >> > > Then after_loose(_m, &puri, 1, 0) is called because the single >> > > existing Route header has our SIP URI. >> > > And then: >> > > DBG("after_loose: Topmost route URI: '%.*s' is me\n", uri->len, ZSW(uri->s)); >> > > and >> > > DBG("after_loose: No next URI found\n"); >> > > An since _ruri_myself == 0, return RR_DRIVEN; >> > > >> > > IMO the fact that the Req-URI is a tel URI shouldn't make loose_route >> > > return true in this case... >> > > >> > > JF >> > > >> > > >> > > On 6/21/07, Greger V. Teigre <greger(a)teigre.com> wrote: >> > > > If there's a single Route header pointing to itself, then this is a good >> > > > indication that a UA added a Route to your proxy as an outbound proxy. >> > > > If SER correctly identities the uri as itself, it should AFAIK return false. >> > > > Could you please turn on debugging and then look for loose_route and >> > > > after_loose debug messages in the logs and post them? >> > > > g-) >> > > > >> > > > JF wrote: >> > > > > Hi all, >> > > > > >> > > > > When SER receives an INVITE with a single Route header pointing to >> > > > > itself, it's supposed to delete it and process the message as if no >> > > > > Route header was there in the first place. This is what RFC3261 >> > > > > mandates, right? >> > > > > >> > > > > But currently the loose_route function returns true to the script in >> > > > > this case, just like when more Route headers are present. >> > > > > >> > > > > So I have some routing logic for when no Route headers are present, >> > > > > and if I want to apply the same routing logic to the case when there >> > > > > is a single Route header pointing to myself (naturally, as it's the >> > > > > same as if no Route header was present), I currently have to replicate >> > > > > the same routing logic inside the if (loose_route())... >> > > > > >> > > > > Or is there an other way? Do I have to develop my own module function >> > > > > or use some regexp search from the script to detect if there are more >> > > > > Routes besides myself before I call loose_route? >> > > > > >> > > > > The best would be to change loose_route to return false and just >> > > > > remove the Route header pointing to myself when there are no more >> > > > > Route headers in the message... what do you think? >> > > > > >> > > > > JF >> > > > > _______________________________________________ >> > > > > 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 -- Jiri Kuthan http://iptel.org/~jiri/

2 1

[OpenSER-Users] short remainder: IRC OpenSER meeting today 13:00 GMT
by Henning Westerholt 17 Jul '07

17 Jul '07

Hello all, just a short remainder about the IRC OpenSER development meeting today at 13:00 GMT in the #openser channel on freenode.net. Information about this meeting: http://openser.org/dokuwiki/doku.php/development:irc-meeting-agenda-17-07-2… Please join us! -- Henning Westerholt - Unix system development 1&1 Internet AG, Brauerstraße 48, 76135 Karlsruhe, Germany

1 0

[OpenSER-Users] Request for comment : logging in OpenSER
by Bogdan-Andrei Iancu 17 Jul '07

17 Jul '07

Hi everybody, There is some undergoing work on the logging system in OpenSER and I feel that some issues should be publicly addressed before moving forward. What we have now in openser: 1) two logging systems - syslog and standard error 2) message format - totally chaos. What we want to fix: 1) a better way to make easy distinction between the logs from different levels (ERR, WARN, DBG, etc) 2) a standard message format that, independend of the logging support (syslog, stderr), will provide all the needed information (level and date at least). Here is my suggestion: 1) logging and message format: There will be different macros for each log level and the message should include the module_name and function for a better tracking of the messages: LOG_NOTICE("module_name:function: message") LOG_DBG("module_name:function: message") LOG_ERR("module_name:function: message") ...... 2) logging backends: a) syslog syslog automatically logs the date, process and from syslog.conf, you can redirect the log in different files based on the log level, so here there is nothing to be changed. b) stderr we need to extend dprint() (logger function for stderr) to prefix to the log message the date and log level (as text). This will provide similar possibilities as for syslog. (a patch is already available for this on the tracker) If there are some comments on the proposed solution or there is a better approach, please let me know as I want to move on with this topic. Regards, Bogdan

5 6

[Serusers] need help!
by Mukesh Prajapati 17 Jul '07

17 Jul '07

Hi I read the Ser Getting started pdf. can anybody tell me what would be the structure of My Sql database used in "Hello world scenario with my sql authentication" thnks mukesh --------------------------------- Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.

2 1

[OpenSER-Users] OpenSER + FreeRadius issue
by openser＠zap2link.com 16 Jul '07

16 Jul '07

Hi All, Well, after a bit of a struggle with the example document on the website, which is highly outdated, I've managed to have OpenSER send Radius requests to my FreeRadius Server. Now, I'm getting rejected by the radius server, with the following error messages: Sun Jul 15 05:02:02 2007 : Auth: rlm_digest: Configuration item "User-Password" or Digest-HA1 is required for authentication. Sun Jul 15 05:02:02 2007 : Auth: Login incorrect: [101(a)192.168.2.80/<no User-Password attribute>] (from client openser port 5060) Sun Jul 15 05:02:12 2007 : Auth: Login incorrect: [101(a)192.168.2.80/<no User-Password attribute>] (from client openser port 0) Sun Jul 15 05:02:22 2007 : Auth: rlm_digest: Configuration item "User-Password" or Digest-HA1 is required for authentication. Sun Jul 15 05:02:22 2007 : Auth: Login incorrect: [101(a)192.168.2.80/<no User-Password attribute>] (from client openser port 5060) Sun Jul 15 05:02:31 2007 : Auth: Login incorrect: [103(a)192.168.2.80/<no User-Password attribute>] (from client openser port 0) Assistance would be appreciated. Following below is my OpenSER and FreeRadius configurations: http://pastebin.com/f41e8204a Regards, openser(a)zap2link.com

1 0

[Serusers] [serusers] sip trunk between a cisco callmanager
by julia heller 16 Jul '07

16 Jul '07

Hi, does anybody know, how i can make a sip trunk between a cisco callmanager 5.0 and a sip express router (0.9.6)? kind regards julia -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

2 2

[OpenSER-Users] OpenSER + OPTIONS module
by Marc LEURENT 16 Jul '07

16 Jul '07

Hello Does anyone succeed in having openwengo SIP pings working with openser I've added the options module and the fonction below but openser isn't answering. loadmodule "options.so" ...... if (uri==myself) { if ((method==OPTIONS) || ( uri=~"sip:ping[@]+.*")) { options_reply(); }; }; Thanks Marc Session Initiation Protocol Status-Line: SIP/2.0 404 Not Found Status-Code: 404 [Resent Packet: False] Message Header Via: SIP/2.0/UDP 192.168.95.109:5060;rport=5060;branch=z9hG4bK1170921213 From: sip.wifirst.fr <sip:test@192.168.95.248>;tag=62904156 To: <sip:ping@192.168.95.248>;tag=e9b225e6b81dc6124ee6640a10a59bf1.f647 Call-ID: 668195568(a)192.168.95.109 CSeq: 20 OPTIONS Sequence Number: 20 Method: OPTIONS Server: OpenSER (1.2.1-notls (i386/linux)) Content-Length: 0

3 2

[OpenSER-Users] <db_url> not found in module <pua_usrloc>
by Iñaki Baz Castillo 16 Jul '07

16 Jul '07

Hi, I'm trying to enabe the module pua_usrloc in OpenSer 1.2.1 but I can't since I get an error: set_mod_param_regex: parameter <db_url> not found in module <pua_usrloc> Of course, I have loaded the modules: loadmodule "pua.so" loadmodule "pua_usrloc.so" I see no "db_url" parameter for pua_usrloc module in the doc: http://www.openser.org/docs/modules/1.2.x/pua_usrloc.html but I do see it in the pua module, so I set: modparam("pua", "db_url", "mysql://openser:openserrw@localhost/openser") but I get the same error: <db_url> not found in module <pua_usrloc> So I've tryed to add: modparam("pua_usrloc", "db_url", "mysql://openser:openserrw@localhost/openser") with exactly same problem. Any idea of what I'm doing wrong? anybody using pua_usrloc module succesfully? Regards. -- Iñaki Baz Castillo ibc(a)in.ilimit.es

2 2

[Serusers] How to use avps in subst
by Roger Lewau 16 Jul '07

16 Jul '07

Hello I am running version 0.9.6 and have a situation where I want to change the remote-party-id of a forwarded call so that when the call reach the destination the forwarding users number is avertised. It is necessary to change it becaus if I dont change this header the first number of the trunk is shown, which almost everytime is another customer than the forwarder. I have experimented with avpops and subst but can not get the avp part to translate into the value in the resulting string. This is the code I am using for unconditional forwarding if (avp_db_load("$ruri/username", "s:cfwd")) { setflag(22); revert_uri(); avp_write("$ruri/username","s:calledno"); subst('/^Remote-Party-ID:(.*)>(.*)$/Remote-Party-ID: "$avp(calledno)" <sip:$avp(calledno)>\2/i'); avp_delete("s:calledno"); avp_pushto("$ruri/username", "s:cfwd"); prefix("01"); #use interface 1 on Vegastream Gate route(5); route(4); break; }; The resulting header looks like this: Remote-Party-ID: "$avp(rpid)" <sip:$avp(rpid)>;party=calling;screen=no;privacy=off. Is it not possible to use avpops in subst? Any other idea on how to change the header in 0.9.6. Kind regards Roger Lewau

1 0

[Serusers] SER <> Asterisk in trunk context
by inge 16 Jul '07

16 Jul '07

Hi all, I find somes informations about using SER and Asterisk to do a SIP trunk. Indeed, the context is the follow : - One Asterisk with PABX functionnality wich provide some services - This Asterisk wants to make calls to PSTN without direct interco - Asterisk should be interconnect to a SER server In this context, what's the solutions to provide a trunk between Asterisk and SER for this context, and have accounting on SER ? Thanks for your indications and support. Sincerely, Adrien .L

1 1

[Serusers] endless authentication needed
by Benoit Pradelle 16 Jul '07

16 Jul '07

Hi all, I'm working on a SIP client, I'm implementing SIMPLE but during my tests I encounter a very strange behavior with the iptel.org server. When I send a SUBSCRIBE message with an Expires value of 0 I receive a 407 / Authentication needed, I handle the challenge correctly (I've checked, the response value is correct) but I receive a new 407 message with the same challenge ! It continues again and again and I'm never able to authenticate. What is the problem ? I can join a dump if needed. Cheers, Ben

5 6

Re: [OpenSER-Users] Good how-to openser + radius authentification
by Marc LEURENT 16 Jul '07

16 Jul '07

It's working for me for OpenSER authentification/acc through freeradius! I've installed a debian to replace my ubuntu server, and compiled OpenSER with radius acc support I'v made a .deb from source: wget http://ftp.debian.org/debian/pool/main/o/openser/openser_1.2.1.orig.tar.gz wget http://ftp.debian.org/debian/pool/main/o/openser/openser_1.2.1-1.diff.gz tar xvzf openser_1.2.1.orig.tar.gz cd openser-1.2.1-tls/ vim Makefile # to delete *_radius and mysql module from excluded module vim modules/acc/Makefile to enable radius acc and disable mysql acc dpkg-buildpkg -rfakeroot # to create .deb For the rest, I've followed the tutorial, and it's working Good luck Best regards, Marc ram a écrit : > Hi > > thanks for the quick reply > > even iam trying my best to work > > if i see some success i will share > > may be with our co-ordination we can come out new setup > working > > lets hope for the best > > ram > > > On 7/16/07, *Marc LEURENT* <lftsy(a)free.fr <mailto:lftsy@free.fr>> wrote: > > I have got troubles too > I'm still trying to understand how does it work > I'll keep you informed > Have a noce day > > ram a écrit : > > Hi > > > > are u able to make this setup working > > > > iam still the same status > > > > let me know if you have any update we can share each other > > > > ram > > > > > > On 7/13/07, *Marc LEURENT* <lftsy(a)free.fr <mailto:lftsy@free.fr> > <mailto:lftsy@free.fr <mailto:lftsy@free.fr>>> wrote: > > > > I'm looking forward to seeing your update! > > In the meantime, is it possible for you to send me your > freeradius > > and > > your openser configuration files... > > I am compiling openser with radius enabled in the acc module... > > > > Best Regards, > > > > Marc LEURENT > > > > Neeraj Gupta a écrit : > > > Hello Ram, > > > > > > I have successfully configured OpenSer with FreeRadius. > However > > I used > > > all latest software versions. > > > The link you mentioned is quite old now. I am planning to > post a new > > > how to very soon. > > > > > > Thanks, > > > Neeraj Gupta > > > > > > ram wrote: > > >> > > >> > > >> On 7/12/07, *Bogdan-Andrei Iancu* <bogdan(a)voice-system.ro > <mailto:bogdan@voice-system.ro> > > <mailto:bogdan@voice-system.ro <mailto:bogdan@voice-system.ro>> > > >> <mailto:bogdan@voice-system.ro > <mailto:bogdan@voice-system.ro> > > <mailto: bogdan(a)voice-system.ro > <mailto:bogdan@voice-system.ro>>>> wrote: > > >> > > >> Hi Marc, > > >> > > >> have you tried this: > > >> http://www.openser.org/docs/openser-radius-1.0.x.html > > <http://www.openser.org/docs/openser-radius-1.0.x.html > <http://www.openser.org/docs/openser-radius-1.0.x.html>> > > >> > > >> regards, > > >> bogdan > > >> > > >> > > >> Hi > > >> > > >> with the above URL, can any one able to make success > > >> integration with Freeradius > > >> > > >> i get lot of errors on freeradius side > > >> some time hint, some time groups, some time Auth-Type > > >> > > >> i followed the same instrusction > > >> i get this following errors > > >> > > >> any help ? > > >> > > >> Module: Loaded files > > >> files: usersfile = "/usr/local/etc/raddb/users" > > >> files: acctusersfile = "/usr/local/etc/raddb/acct_users" > > >> files: preproxy_usersfile = > "/usr/local/etc/raddb/preproxy_users" > > >> files: compat = "no" > > >> /usr/local/etc/raddb/users[1]: Parse error (check) for > entry test: > > >> Unknown attribute "Auth-Type" > > >> Errors reading /usr/local/etc/raddb/users > > >> radiusd.conf[863]: files: Module instantiation failed. > > >> radiusd.conf[1204] Unknown module "files". > > >> radiusd.conf[1201] Failed to parse preacct section. > > >> > > >> > > >> ram > > >> > > >> > > > ------------------------------------------------------------------------ > > >> > > >> _______________________________________________ > > >> Users mailing list > > >> Users(a)openser.org <mailto:Users@openser.org> > <mailto:Users@openser.org <mailto:Users@openser.org>> > > >> http://openser.org/cgi-bin/mailman/listinfo/users > > >> > > > > > > -- > > > ------------------------------------------------------------- > > > o Neeraj Gupta email: neeraj.gupta(a)sun.com > <mailto:neeraj.gupta@sun.com> > > <mailto:neeraj.gupta@sun.com <mailto:neeraj.gupta@sun.com>> > > > o Netra Systems & Networking phone: +1(408) 276-7214 x71214 > > > o Sun Microsystems, Inc. fax : +1(408) 276-4552 > > > o 4120 Network Circle, USCA12-216, Santa Clara, CA 95054, USA > > > ------------------------------------------------------------- > > > > > > > > > ------------------------------------------------------------------------ > > > > > > > > _______________________________________________ > > > Users mailing list > > > Users(a)openser.org <mailto:Users@openser.org> > <mailto:Users@openser.org <mailto:Users@openser.org>> > > > http://openser.org/cgi-bin/mailman/listinfo/users > > > > > > > > >

1 0

RE: [OpenSER-Users] lookup problem
by Kro Kamil 16 Jul '07

16 Jul '07

Hi, I will try to give more details, Actually everything was working fine till I the day I moved my dns server to the same machine with ser. I setup bind9 on the machine where ser is installed. I did the same dns configuration with the old one but after some time ser started to give that error. I then removed bind9 but nothing changed. Now here is my named.conf ********************** zone "intersan.com.tr" { type master; file "/var/cache/bind/intersan.com.tr.hosts"; };zone "sahratelekom.com.tr" { type master; file "/var/cache/bind/sahratelekom.com.tr.hosts"; }; ********************** this is "intersan.com.tr.hosts": ********************** $ttl 38400intersan.com.tr. IN SOA ns1.intersan.com.tr. alp.intersan.com.tr. ( 1152602393 10800 3600 604800 38400 )intersan.com.tr. IN NS ns1.intersan.com.tr.intersan.com.tr. IN NS ns2.intersan.com.tr.www.intersan.com.tr. IN CNAME intersan.com.tr.intersan.com.tr. IN MX 10 intersan.com.tr.intersan.com.tr. IN A 85.105.26.49ns1.intersan.com.tr. IN A 88.248.71.3ns2.intersan.com.tr. IN A 85.111.0.20249.26.105.85.intersan.com.tr. IN PTR intersan.com.tr. ********************** this is "sahratelekom.com.tr.hosts" ********************** $ttl 38400sahratelekom.com.tr. IN SOA ns1.intersan.com.tr. alp.intersan.com.tr. ( 1152602935 10800 3600 604800 38400 )sahratelekom.com.tr. IN NS ns1.intersan.com.tr.sahratelekom.com.tr. IN NS ns2.intersan.com.tr.www.sahratelekom.com.tr. IN CNAME sahratelekom.com.tr.sahratelekom.com.tr. IN MX 5 sahratelekom.com.tr.sahratelekom.com.tr. IN A 85.105.26.4949.26.105.85.sahratelekom.com.tr. IN PTR sahratelekom.com.tr. sip.sahratelekom.com.tr. IN A 85.111.0.205********************** I am also pasting the message traffic below. > Date: Mon, 16 Jul 2007 10:39:28 +0300> From: bogdan(a)voice-system.ro> To: kro_ser(a)hotmail.com> CC: users(a)openser.org> Subject: Re: [OpenSER-Users] lookup problem> > Hi Kro,> > OpenSER tries to preform NAPTR and SRV lookups on the name before A dns > lookup. As the debug shows, most probably you do not have NAPTR and SRV > records for the domain name and the A record is used. Can you confirm > that the request is forwarded? When I listen the main interface, here is the traffic 85.105.26.49:17030 -> 85.111.0.205:5060INVITE 85.111.0.205:5060 -> 85.105.26.49:17030 SIP/2.0 100 Giving a try 85.111.0.205:5060 -> 85.105.26.49:17030 SIP/2.0 513 Message too big 85.105.26.49:17030 -> 85.111.0.205:5060ACK > > The "message too big" is most probably a side-effect of a request that > loops on the server because improper configuring - try to lool on > loopback interface to see if so.> The loopback interface traffic is: 85.111.0.205:5060 -> 85.111.0.205:5060 INVITE 85.111.0.205:5060 -> 85.111.0.205:5060 SIP/2.0 100 Giving a try --INVITE and Giving a try repeated 5 times-- 85.111.0.205:5060 -> 85.111.0.205:5060 SIP/2.0 513 Message too big 85.111.0.205:5060 -> 85.111.0.205:5060 ACK --Message too big and ACK repeated 5 times-- thanks Kro > regards,> bogdan> > > > Kro Kamil wrote:> > Hello,> > > > Actually it does not look like a ser problem but I could not find a > > way out so I am asking your help.> > When I try to make a call, after calling lookup function I get the > > following error and then a "message too big" reply.> > > > *************************> > DEBUG:sip_resolvehost2: no port, no proto -> do NAPTR lookup!> > get_record: lookup(sip.sahratelekom.com.tr, 35) failed> > DEBUG:sip_resolvehost2: no valid NAPTR record found for > > sip.sahratelekom.com.tr, trying direct SRV lookup...> > get_record: lookup(_sip._udp.sip.sahratelekom.com.tr, 33) failed> > DEBUG:sip_resolvehost2: no valid SRV record found for > > _sip._udp.sip.sahratelekom.com.tr, trying A record lookup...> > *************************> > > > When I look at the code I saw that "res_search" function is called in > > "get_record" function and it returns -1 which says that it could not > > resolve hostname. My "resolv.conf" file is properly configured and I > > can ping and resolve any address from command line including > > "sip.sahratelekom.com".> > Do you have any idea about this problem?> > > > thanks> > > > Kro> >> > ------------------------------------------------------------------------> > Live.com'u deneyin - hýzlý ve kiþiselleþtirilmiþ giriþ sayfanýzla > > istediðiniz her þey tek bir yerde. tek bir yerde. > > <http://www.live.com/getstarted>> > ------------------------------------------------------------------------> >> > _______________________________________________> > Users mailing list> > Users(a)openser.org> > http://openser.org/cgi-bin/mailman/listinfo/users> > > _________________________________________________________________ Live.com'u deneyin - hýzlý ve kiþiselleþtirilmiþ giriþ sayfanýzla istediðiniz her þey tek bir yerde. http://www.live.com/getstarted

1 0

[OpenSER-Users] lookup problem
by Kro Kamil 16 Jul '07

16 Jul '07

Hello, Actually it does not look like a ser problem but I could not find a way out so I am asking your help. When I try to make a call, after calling lookup function I get the following error and then a "message too big" reply. ************************* DEBUG:sip_resolvehost2: no port, no proto -> do NAPTR lookup! get_record: lookup(sip.sahratelekom.com.tr, 35) failed DEBUG:sip_resolvehost2: no valid NAPTR record found for sip.sahratelekom.com.tr, trying direct SRV lookup... get_record: lookup(_sip._udp.sip.sahratelekom.com.tr, 33) failed DEBUG:sip_resolvehost2: no valid SRV record found for _sip._udp.sip.sahratelekom.com.tr, trying A record lookup... ************************* When I look at the code I saw that "res_search" function is called in "get_record" function and it returns -1 which says that it could not resolve hostname. My "resolv.conf" file is properly configured and I can ping and resolve any address from command line including "sip.sahratelekom.com". Do you have any idea about this problem? thanks Kro _________________________________________________________________ Live.com'u deneyin - hýzlý ve kiþiselleþtirilmiþ giriþ sayfanýzla istediðiniz her þey tek bir yerde. http://www.live.com/getstarted

3 2

RE: [OpenSER-Users] lookup problem
by Kro Kamil 16 Jul '07

16 Jul '07

> Date: Mon, 16 Jul 2007 08:34:19 +0200> From: klaus.mailinglists(a)pernau.at> To: kro_ser(a)hotmail.com> CC: users(a)openser.org> Subject: Re: [OpenSER-Users] lookup problem> > > > Kro Kamil wrote:> > Hello,> > > > Actually it does not look like a ser problem but I could not find a> > way out so I am asking your help. When I try to make a call, after> > calling lookup function I get the following error and then a "message> > too big" reply.> > > > ************************* DEBUG:sip_resolvehost2: no port, no proto> > -> do NAPTR lookup! get_record: lookup(sip.sahratelekom.com.tr, 35)> > failed DEBUG:sip_resolvehost2: no valid NAPTR record found for> > sip.sahratelekom.com.tr, trying direct SRV lookup... get_record:> > lookup(_sip._udp.sip.sahratelekom.com.tr, 33) failed> > DEBUG:sip_resolvehost2: no valid SRV record found for> > _sip._udp.sip.sahratelekom.com.tr, trying A record lookup...> > *************************> > > > When I look at the code I saw that "res_search" function is called in> > "get_record" function and it returns -1 which says that it could not> > resolve hostname. My "resolv.conf" file is properly configured and I> > can ping and resolve any address from command line including> > "sip.sahratelekom.com.tr". Do you have any idea about this problem?> > ^^(corrected) > > > openser is trying to resolve sip.sahratelekom.com.tr> ^^ Correct domain is "sip.sahratelekom.com.tr". I also can ping "sip.sahratelekom.com.tr" from command line. > > regards> klaus> > > > > thanks> > > > Kro _________________________________________________________________ _________________________________________________________________ Kendinizi ifade edin: giriþ sayfanýzý Live.com ile istediðiniz biçimde tasarlayýn. http://www.live.com/getstarted

1 0

Re: [OpenSER-Users] Strange ACK format gives OpenSER error?
by Tobias Lindgren 16 Jul '07

16 Jul '07

Hi Martin, thanks for quick answer. Exactly how does disabling full lr solve this? I mean, how does it change the way "<>" is handled? Br, /Tobias Martin Klisch said the following on 2007-07-06 12:59: >> Hi all, >> >> after a patch from one of our providers ACKs started to come with R-URI >> looking like: >> ACK <sip:192.168.0.1;lr=on;ftag=507454020> SIP/2.0 >> instead of: >> ACK sip:192.168.0.1;lr=on;ftag=507454020 SIP/2.0 >> like it did before the patch. >> >> The new ACK format gives an error in OpenSER: >> Jul 6 11:35:55 ser1 /sbin/openser[9634]: ERROR: parse_uri: bad uri, >> state 0 parsed: <<sip> (4) / <<sip:192.168.0.1;lr=on;ftag=507454020>> (38) >> Jul 6 11:35:55 ser1 /sbin/openser[9634]: ERROR: parse_sip_msg_uri: bad >> uri <<sip:192.168.0.1;lr=on;ftag=507454020>> >> Jul 6 11:35:55 ser1 /sbin/openser[9634]: loose_route: Error while >> parsing Request URI >> >> Are the new format of the ACKs valid? With the "<>"? If they are valid, >> the problem lies in OpenSER? > > It is not valid. it is a bug on cisco PGW after upgrading to another ios. > you have to disable full lr: modparam("rr", "enable_full_lr", 0). > > the cisco gateway takes the whole from-uri (with <>) for the r-uri. cisco > people said "the =on behind the lr is wrong. it is not in the rfc." - but > the rfc doesnt say, that there must only be a lr without params. but the > rfc shows a "must not" about <> in R-URI. > > > > > >

2 4

[OpenSER-Users] SER : Query Regarding User Authorisation.
by Parminder.Nayyar＠relianceada.com 15 Jul '07

15 Jul '07

Hi We are facing problem using the authentication module of SER. First we enabled the database to mysql and set the db_mode in userloc to 2. Then we added a user through the serctl add <username> <password> <emailid> Now, in the config file , we load the auth moduel and the auth_db module, and try to authorize the REGISTER attempts using www_authorize() procedure. But every time we are returned a message that Authorisation failed. However if we remove teh authorisation functionality from the config file, the subscriber is shown in the location table of ser database. CAN ANYONE HELP ME IN UNDERSTANDING WHAT IS HAPPENING, and How do i make the authorisation procedure work? 3(27177) SIP Request: 3(27177) method: <REGISTER> 3(27177) uri: <sip:10.128.16.254> 3(27177) version: <SIP/2.0> 3(27177) parse_headers: flags=1 3(27177) Found param type 235, <rport> = <n/a>; state=6 3(27177) Found param type 232, <branch> = <z9hG4bK2DD03B6ACD9544A89ACF7C48EF87CEFB>; state=16 3(27177) end of header reached, state=5 3(27177) parse_headers: Via found, flags=1 3(27177) parse_headers: this is the first via 3(27177) After parse_msg... 3(27177) preparing to run routing scripts... 3(27177) parse_headers: flags=128 3(27177) end of header reached, state=9 3(27177) DEBUG: get_hdr_field: <To> [35]; uri=[sip:rakesh@10.128.16.254] 3(27177) DEBUG: to body [rakesh <sip:rakesh@10.128.16.254> ] 3(27177) get_hdr_field: cseq <CSeq>: <34836> <REGISTER> 3(27177) DEBUG:maxfwd:is_maxfwd_present: value = 70 3(27177) DBG:maxfwd:process_maxfwd_header: value 70 decreased to 16 3(27177) parse_headers: flags=256 3(27177) DEBUG: get_hdr_body : content_length=0 3(27177) found end of header 3(27177) find_first_route: No Route headers found 3(27177) loose_route: There is no Route HF 3(27177) grep_sock_info - checking if host==us: 13==13 && [10.128.16.254] == [10.128.16.254] 3(27177) grep_sock_info - checking if port 5060 matches port 5060 3(27177) parse_headers: flags=-1 3(27177) check_via_address(10.128.16.149, 10.128.16.149, 0) 3(27177) check_nonce(): comparing [46973120b5e52ab0043489c086504ae54af9d299] and [46973120b5e52ab0043489c086504ae54af9d299] 3(27177) check_response(): Our result = 'a20c4795c00787c796addb4fff02bc15' 3(27177) check_response(): Authorization failed 3(27177) build_auth_hf(): 'WWW-Authenticate: Digest realm="10.128.16.254", nonce="46973120b5e52ab0043489c086504ae54af9d299" ' 3(27177) parse_headers: flags=-1 3(27177) check_via_address(10.128.16.149, 10.128.16.149, 0) 3(27177) DEBUG:destroy_avp_list: destroying list 0 3(27177) receive_msg: cleaning up the config file used is attached with the mail Wish I could get a solution asap... Thanks! Parminder Nayyar

2 1

[Serusers] FIFO Commands
by Christian Thomas 15 Jul '07

15 Jul '07

Hi, I would like to know how to obtain the complete FIFO command list. I'm running a SER 0.9.4 and thru serctl I would like to be able to quickly show or reload tables contents. Like serctl fifo trusted_dump or trusted_reload. Thanks Christian Thomas Diretor Executivo Canal West Fone : +55 (48) 2107 2728 Fax : +55 (48) 3333 3745 MSN / Email : cthomas(a)canalwest.com VoIP : cthomas(a)sip.canalwest.com

1 0

[OpenSER-Users] logging
by Pande, Piyush 13 Jul '07

13 Jul '07

Hi , Forgive me if this an obvious question but when OpenSER is running is there a log file I can look for to debug what OpenSER receives and sends back? Also how can we put debug statements in the openser.cfg and where will they be outputted to? Thanks Piyush

2 1

[Serusers] Checking Route
by Ron Shacham 13 Jul '07

13 Jul '07

Hi. I am new to SER. I am trying to update the Route header. In order to do this, I need to check the value of, for example, the first route entry, and push new routes. Can someone give me some pointers about how to do this? In general, how can I check the value of a header field. This is a basic question, but I haven't been able to find direction in the documentation. Thanks, Ron

2 1

[Serusers] getting failed permissions and this is affecting registrations of natted clients
by Kirk McCalla 13 Jul '07

13 Jul '07

I am using fedora core 4 I just did a yum install to install the ser as well as the ser-mysql and mysql packages. I am starting ser and I am getting this error 0(0) Default allow file (/etc/ser/permissions.allow) not found => empty rule set 0(0) Default deny file (/etc/ser/permissions.deny) not found => empty rule set I am able to start ser and do a monitor of the ser system. when I try to register a UA I get a 408 forbidden message. I started mysql and tried to look at the user table. This table does not exist Can any one help. the file

1 0

[Serusers] ser cvs compile error
by JF 13 Jul '07

13 Jul '07

Hi, I can't compile SER HEAD. I get the errors below. How can this be fixed? Thanks, JF bison -d -b cfg cfg.y cfg.y: conflicts: 1 shift/reduce flex cfg.lex In file included from parser/../mem/../lock_ops.h:85, from parser/../mem/shm_mem.h:76, from parser/parse_rr.c:39: parser/../mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from parser/../mem/../lock_ops.h:85, from parser/../mem/shm_mem.h:76, from parser/parse_param.c:42: parser/../mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from mem/shm_mem.c:43: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from mem/mem.c:50: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from usr_avp.c:48: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from tcp_conn.h:42, from tls_hooks.h:40, from tls_hooks.c:26: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from timer.c:59: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from tcp_conn.h:42, from tcp_read.c:59: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from tcp_conn.h:42, from tcp_main.c:111: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from select.c:49: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from pt.c:42: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from msg_translator.c:134: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from main.c:119: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from lock_ops.c:27: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from io_wait.h:93, from io_wait.c:54: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from dst_blacklist.c:40: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from dprint.c:34: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from dns_cache.c:48: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from core_cmd.c:32: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from parser/../mem/../lock_ops.h:85, from parser/../mem/shm_mem.h:76, from parser/parse_rr.c:39: parser/../mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from parser/../mem/../lock_ops.h:85, from parser/../mem/shm_mem.h:76, from parser/parse_param.c:42: parser/../mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from mem/shm_mem.c:43: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from mem/mem.c:50: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from usr_avp.c:48: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from tcp_conn.h:42, from tls_hooks.h:40, from tls_hooks.c:26: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from timer.c:59: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from tcp_conn.h:42, from tcp_read.c:59: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from tcp_conn.h:42, from tcp_main.c:111: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from select.c:49: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from pt.c:42: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from msg_translator.c:134: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from main.c:119: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from lock_ops.c:27: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from io_wait.h:93, from io_wait.c:54: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from dst_blacklist.c:40: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from dprint.c:34: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from dns_cache.c:48: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from core_cmd.c:32: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory gcc -g -O9 -funroll-loops -Wcast-align -minline-all-stringops -falign-loops -mtune=athlon -Wall -DNAME='"ser"' -DVERSION='"2.1.0-dev9-dns"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 3.4.3"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -c action.c -o action.o gcc -g -O9 -funroll-loops -Wcast-align -minline-all-stringops -falign-loops -mtune=athlon -Wall -DNAME='"ser"' -DVERSION='"2.1.0-dev9-dns"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 3.4.3"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -c atomic_ops.c -o atomic_ops.o gcc -g -O9 -funroll-loops -Wcast-align -minline-all-stringops -falign-loops -mtune=athlon -Wall -DNAME='"ser"' -DVERSION='"2.1.0-dev9-dns"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 3.4.3"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -c bit_scan.c -o bit_scan.o gcc -g -O9 -funroll-loops -Wcast-align -minline-all-stringops -falign-loops -mtune=athlon -Wall -DNAME='"ser"' -DVERSION='"2.1.0-dev9-dns"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 3.4.3"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -c core_cmd.c -o core_cmd.o In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from core_cmd.c:32: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from core_cmd.c:32: mem/../futexlock.h: In function `futex_get': mem/../futexlock.h:90: error: `FUTEX_WAIT' undeclared (first use in this function) mem/../futexlock.h:90: error: (Each undeclared identifier is reported only once mem/../futexlock.h:90: error: for each function it appears in.) mem/../futexlock.h: In function `futex_release': mem/../futexlock.h:118: error: `FUTEX_WAKE' undeclared (first use in this function) make: *** [core_cmd.o] Error 1

2 2

[OpenSER-Users] Re: [Serusers] enum_query from failure route
by Jiri Kuthan 13 Jul '07

13 Jul '07

Not sure. I think it is possible to turn it on but possibly ENUM's processing latency may conflict with the failure_route located in the middle of transaction processing and lead to some blocknig conditions, current TM maintainer, Andrei, will certainly know better. -jiri At 16:41 11/07/2007, JF wrote: >Hi, > >Is there any particular reason why enum_query cannot be called from >FAILURE_ROUTE? > >Thanks, > >JF >_______________________________________________ >Serusers mailing list >Serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

8 12

[OpenSER-Users] a c program behaves differently when called by openser than it does when called from the console.
by Bontron 13 Jul '07

13 Jul '07

Hello, I have this piece of code in my openser.cfg : exec_msg("/usr/local/etc/openser/uri-folder/record '$fu' $$SIP_USER '$ft' 'additionalinfo'"); The instruction 'record' is a c program. This is supposed to add a record in a mysql database - new incoming call, from caller , to called, date, and an additional info - and as the matter of fact it almost does except that 'record' is unable to append the date. It writes '0000-00-00'. The strange thing is that when the 'record' instruction is being called from the console, the set of instructions being manually written : record 'joe@....' etc ... it records everything including the right date and time. Did any one face a similar situation ? Thanks in advance. Olivier ________________________________________________ Message sent using UebiMiau 2.7.8

3 2

[OpenSER-Users] Restricting calls between users
by Gerardo Gonzalez 13 Jul '07

13 Jul '07

Regards, I have a debian (etch - kernel 2.6.18) server with openser 1.1.0-9-etch1installed and Asterisk 1.4.6. To admin openser, I'm using openseradmin 0.3 and Asterisk-GUI (Rev. 1203) to admin Asterisk. Openser service works fine to make calls between users (Linksys phones, ATA phones, Sipura phones, etc.) and I installed Asterisk to use VoiceMail, Call Queues, Conferencing, Voice Menus, Calls redirections and PSTN GW functions. NOTE: I can hear only Asterisk VoiceMail, but I'm still working to openser-asterisk integration. For me, who I am a new Linux user, It's hard but not impossible. I want to configure call restrictions between openser VoIP groups at the same domain. For example: I have an IP Network with clients who has remote offices. I'm using openser to connect their offices. Now, I want to use groups to resctric calls between clients. I want to know what's the best solution to do calls restrictions between groups. I must use AVPops, Groups, Asterisk modules, etc ?????? Can anybody help me? PD: I'm sorry for my spanglish. Thanks

2 1

Re: [OpenSER-Users] Performance metric
by Fredrik Lundmark 13 Jul '07

13 Jul '07

Have a look at these http://www.transnexus.com/White%20Papers/OpenSER-SER_Comparison.htm http://www.openser.org/mos/view/News/NewsItem/OpenSER-1.2.0---Perfomance-Te… Should relief any concerns reg. capacity... ///Fredrik ----- Original Message ----- From: Pande, Piyush To: users(a)openser.org Sent: Wednesday, July 11, 2007 10:44 PM Subject: [OpenSER-Users] Performance metric Hi, Does anybody know what is the benchmark for calls/sec and number of simultaneous SIP calls that OpenSER can support? -------------------------------------------------------------------------------- _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users

2 1

[OpenSER-Users] OpenSER development meeting 17-07-2007 13:00 GMT
by Henning Westerholt 13 Jul '07

13 Jul '07

Hello all, the next IRC OpenSER development meeting will take place at next tuesday, the 17-07-2007 at 13:00 UTC (15:00 CEST) at the #openser channel on irc.freenode.net. The purpose of this meeting is to discuss the latest developments in and around the OpenSER project. Topics so far: - release planning (minor, major, schedules) - roadmap trimming (priorization, distribution of tasks) - technical topics (async processing, db interface, script reloading..) - review/ resume of some topics from last meeting For information about the IRC meetings read: http://openser.org/dokuwiki/doku.php/development:irc-meetings For details about this meeting read: http://openser.org/dokuwiki/doku.php/development:irc-meeting-agenda-17-07-2… Please join us! -- Henning Westerholt - Unix system development 1&1 Internet AG, Brauerstraße 48, 76135 Karlsruhe, Germany

2 1

[OpenSER-Users] OpeSER Aministrator Training Course at VoN Itally, Rome
by Bogdan-Andrei Iancu 13 Jul '07

13 Jul '07

Hi everybody, Following the survey form the last 2 weeks regarding the interest in an OpeSER Aministrator Training Course, I'm very pleased to announce that first edition of this event will take place in Rome, during Von Fall Europe. I want to thanks to everybody who sent me or to the project feedback email regarding the event - they were very useful in taking the final decision. So, the event will take place in Rome, on 26 of September, at Marriott Park Hotel. It will a full day training, from 9:30 to 18:00, with lunch included. Once we settle all the details with pulvermedia, I will come back to you with information about the registration process and the detailed schedule of the course. Thanks and regards, Bogdan

1 0

[OpenSER-Users] Good how-to openser + radius authentification
by Marc LEURENT 13 Jul '07

13 Jul '07

Good morning everybody, I would be very grateful if you had a great tutorial for configuring openser with radius authentification! I had some trouble with the deb packages, some radius functions are not recognized so I'm compiling it. Thanks

4 4

[OpenSER-Users] Accessing openser mibs by name does not work.
by Sergio Gutierrez 13 Jul '07

13 Jul '07

Hello everybody. I am trying to access the mibs of openser by using its symbolic names, and I am having and error, but, if use the numerical oids, the values are returned well. # snmpget -v 2c -c public localhost openserSIPProtocolVersion.0 openserSIPProtocolVersion.0: Unknown Object Identifier (Sub-id not found: (top) -> openserSIPProtocolVersion) .1.1.1.1.1.0 # snmpget -v 2c -c public localhost .1.3.6.1.4.1.27483.1.1.1.1.1.0 SNMPv2-SMI::enterprises.27483.3.1.1.1.1.1.0 = STRING: "SIP/2.0" Besides, at sometimes, the subagent seems to disconnect, and I have this error: # snmpwalk -v 2c -c public localhost .1.3.6.1.4.1.27483 | more SNMPv2-SMI::enterprises.27483 = No Such Object available on this agent at this OID Is there something I can check? Thanks in advance for your attention. Sergio Gutiérrez EPM Telecomunicaciones Medellín, Colombia

2 3

[OpenSER-Users] Re: [Serusers] enum_query from failure route
by Jiri Kuthan 12 Jul '07

12 Jul '07

At 12:08 12/07/2007, JF wrote: >So, if I want to perform some less simple (e.g. enum_query) processing >on failed requests, I should loop the request through SER again and do >it in request route? > >Not a very nice way to solve it. Well sometimes a big-hammer approach features design simplicity which is good (simple to understand, audit, maintain, ....) and can be used to solve problems on serial basis. I personally find this quite a good solution. > One more Record-Route, bigger >message... parsing the whole thing again. parsing yes, you don't have to record-route each pass. -jiri >Andrei, what exactly is the problem regarding long processing in >failure route, and what could be done to fix it? > >Thanks, >JF > >On 7/11/07, Jiri Kuthan <jiri(a)iptel.org> wrote: >>At 21:22 11/07/2007, Martin Hoffmann wrote: >>>Jiri Kuthan wrote: >>>> At 16:41 11/07/2007, JF wrote: >>>> > >>>> >Is there any particular reason why enum_query cannot be called from >>>> >FAILURE_ROUTE? >>>> >>>> Not sure. I think it is possible to turn it on but possibly ENUM's processing >>>> latency may conflict with the failure_route located in the middle of >>>> transaction >>>> processing and lead to some blocknig conditions, current TM >>>> maintainer, Andrei, will >>>> certainly know better. >>> >>>In short: There may be dragons there. >>> >>>Anyways, I am not sure what you want to do, but you can usually skip the >>>problem by fixing the Request-URI and sprialing the call to yourself. >>> >>>For instance, if call forwarding is what you're after, instead of >>>re-setting the target and just running processing again, you can just >>>stuff the URI you want to forward to in the Request-URI and call >>>t_relay() (don't forget the append_branch() if in a failure_route). >>> >>>As a rule, keep failure and onreply routes simple. Actually, as a rule, >>>keep your config simple (Though simple does not necessarly mean short). >> >>Indeed: KISS applies to ser.cfg very well. >> >>-jiri >> >> >> >> >>-- >>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/

1 0

[OpenSER-Users] Question on force-active parameter of presence-xml module
by Michel de Boer 12 Jul '07

12 Jul '07

Hi, According to the documentation if the force-active parameter is set to 0, openser will consult the xcap_table when a SUBCRIBE for presence comes in. If there is no entry in the xcap_table, the watcher will receive NOTIFY messages with an empty body until the presentity authorizes the watcher. However, in my tests it doesn't seem to matter to what value I set force_active. The watcher always gets the presence state of the presentity. For my current tests this is fine as I don't have support for xcap, but it looks wrong to me. Can someone explain me how the force-active parameter works? I am using the devel version of openser. Regards, Michel -- Michel de Boer www.twinklephone.com

1 0

Re: [OpenSER-Users] BLA errors
by Jeremy George 12 Jul '07

12 Jul '07

Hi Anca, Thanks for the quick reply. I wondered a little about the phones, too. Alan sent me a note privately, very tactfully reminding me that I'd sent less phone information than I should have. The Polycom 650: bootrom.ld version: 3.2.3.0002 sip version: 2.1.2.0078 The Polycom 330: bootrom.lod verion: 3.2.3.0021 sip version: 2.1.2.0049 Both phone.cfgs are attached, as well ngrep traces from reboots. I did two traces, rebooting each phone separately. Again, I appreciate the help very much. Thanks. - Jeremy >-----Original Message----- >From: Anca-Maria Vamanu [mailto:anca@voice-system.ro] >Sent: Thursday, July 12, 2007 08:18 AM >To: 'Jeremy George' >Cc: users(a)openser.org >Subject: Re: [OpenSER-Users] BLA errors > >Hello, > >The implementation of the bla extension has been done according to the >specifications in draft-anil-sipping-bla-03.txt, and tested with >Polycom 430. > Since we received positive feedback from users impementing BLA, I am >thinking that the phones you use have a different behaviour and that >here is the cause of the errors. >To detect the exact cause I would need some more data. Could you send >me a part of the log , after starting openser and the first phones >registers, subscribes and is sent a Notify? > >regards, > >Anca Vamanu > >Jeremy George wrote: > >>Hello All, >> >> I have BLA implemented, with errors. An ngrep trace of relevant packets >>showing errors follows. The configurations of both main proxy and bla >>presence server are attached. >> >> I stripped the main proxy to the bone. No outside routing at all. The >>bla presence server is almost all from the sample. >> >> 75.56.10.115 is a Cisco 7960 with one line registered: jeremy/private >> 75.56.10.116 is a Polycom 650 with two lines registered: jessica/private >> and helen/shared >> 75.56.10.117 is a Polycom 330 with two lines registered: didama/private >> and helen/shared >> 128.91.3.19 is the main proxy running openser v1.2.1 . >> 128.91.2.215 is the bla presence server running openser svn 2413 . >> >> This error: "1(1184) PUA:subs_cback_func: no reply message found" is >>being produced repeatedly on the bla presence server. >> >> Finally, I'm getting these error messages on the bla presence server: >> >> 0(1284) PUA_BLA: handle_notify: ERROR Notify in a non existing dialog >> 0(1284) WARNING: script writer didn't release transaction >> >> From time-to-time pua entries eat all of available memory. Curiously, >>they were all for the Polycom 330 and none were for the Polycom 650. >> >> Any help is greatly appreciated. Thanks. >> >>- Jeremy >> >> >> > >

2 2

[Serusers] Meaning of and proper response for a 401
by SIP 12 Jul '07

12 Jul '07

There's a UA in our network that responds to a reinvite with a 401. U PROXY.IP.ADDRESS:5060 -> UA.IP.ADDRESS:63718 INVITE sip:1101XXXXXXX@UA.IP.ADDRESS:63718 SIP/2.0. Record-Route: <sip:PROXY.IP.ADDRESS;ftag=as7bbe322e;lr=on>. Via: SIP/2.0/UDP PROXY.IP.ADDRESS;branch=z9hG4bK9159.cd2a95b4.0. Via: SIP/2.0/UDP PSTN.GW.IP:5090;branch=z9hG4bK39c17f01;rport=5090. From: <sip:13154476314@our.domain.com>;tag=as7bbe322e. To: "User One" <sip:1101XXXXXXX@our.domain.com>;tag=202d9942. Contact: <sip:13154476314@PSTN.GW.IP:5090>. Call-ID: 6b3f44351f5fab945ac212a2141df93a(a)UA.IP.ADDRESS. CSeq: 102 INVITE. User-Agent: Asterisk PBX. Max-Forwards: 16. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. Content-Type: application/sdp. Content-Length: 314. P-hint: LR. . v=0. o=root 15241 15243 IN IP4 216.143.130.90. s=session. c=IN IP4 216.143.130.90. t=0 0. m=audio 17192 RTP/AVP 0 8 18 3 101. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:3 GSM/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=silenceSupp:off - - - -. # U UA.IP.ADDRESS:63718 -> PROXY.IP.ADDRESS:5060 SIP/2.0 410 Gone. Via: SIP/2.0/UDP PROXY.IP.ADDRESS:5060;branch=z9hG4bK9159.cd2a95b4.0. Via: SIP/2.0/UDP PSTN.GW.IP:5090;branch=z9hG4bK39c17f01;rport=5090. From: <sip:13154476314@our.domain.com>;tag=as7bbe322e. To: "User One" <sip:1101XXXXXXX@our.domain.com>;tag=202d9942. Contact: <sip:1101XXXXXXX@UA.IP.ADDRESS:63718>. Call-ID: 6b3f44351f5fab945ac212a2141df93a(a)UA.IP.ADDRESS. CSeq: 102 INVITE. Content-Length: 0. First off, I thought a 410 was supposed to be unauthorised (what is 'Gone' ?). Secondly... is the UA requesting our server to authorise its reinvite, or is something else going on here I clearly don't follow? N.

2 2

[OpenSER-Users] query: how to deal with crazy clients
by Klaus Darilion 12 Jul '07

12 Jul '07

Hi! I once again bother about a stupid SIP client which is misconfigured and sending REGISTER messages like crazy to my SIP proxy (~20 requests/second). How do you deal with that stupid clients. Manual blocking does not work as the client has dynamic IP addresses. I once also tried the pike module but had problems to find out a proper configuration (threshold value and sampling interval). Further, I think blocking at IP level (e.g. openser injects iptable rules) would be more useful. I would be happy to hear how you handle such situations.

2 3

[OpenSER-Users] SER query regarding mysql
by Parminder.Nayyar＠relianceada.com 12 Jul '07

12 Jul '07

hi, we are facing following problem while using SER with mysql data base. The problem statements are as follows: 0(0) find_mod_export: found <db_update> in module mysql [/export/home/mins/SER/lib/ser/modules/mysql.so] 0(0) get_connection(): Connection not found in the pool 0(0) release_connection(): Removing connection from the pool 0(0) get_connection(): Connection not found in the pool 0(0) release_connection(): Removing connection from the pool 0(0) fixing /export/home/mins/SER/lib/ser/modules/maxfwd.so mf_process_maxfwd_header 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_send_reply 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_send_reply 0(0) fixing /export/home/mins/SER/lib/ser/modules/rr.so record_route 0(0) fixing /export/home/mins/SER/lib/ser/modules/rr.so loose_route 0(0) fixing /export/home/mins/SER/lib/ser/modules/tm.so t_relay 0(0) fixing /export/home/mins/SER/lib/ser/modules/registrar.so lookup 0(0) fixing /export/home/mins/SER/lib/ser/modules/registrar.so lookup 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_send_reply 0(0) fixing /export/home/mins/SER/lib/ser/modules/tm.so t_relay 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_reply_error 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_send_reply 0(0) fixing /export/home/mins/SER/lib/ser/modules/auth_db.so www_authorize 0(0) get_connection(): Connection not found in the pool 0(0) release_connection(): Removing connection from the pool 0(0) fixing /export/home/mins/SER/lib/ser/modules/auth.so www_challenge 0(0) fixing /export/home/mins/SER/lib/ser/modules/uri_db.so check_to 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_send_reply 0(0) fixing /export/home/mins/SER/lib/ser/modules/auth.so consume_credentials 0(0) fixing /export/home/mins/SER/lib/ser/modules/registrar.so save 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_reply_error 0(0) fixing /export/home/mins/SER/lib/ser/modules/auth_db.so proxy_authorize 0(0) get_connection(): Connection not found in the pool 0(0) release_connection(): Removing connection from the pool 0(0) fixing /export/home/mins/SER/lib/ser/modules/auth.so proxy_challenge 0(0) fixing /export/home/mins/SER/lib/ser/modules/auth.so consume_credentials 0(0) fixing /export/home/mins/SER/lib/ser/modules/registrar.so lookup 0(0) fixing /export/home/mins/SER/lib/ser/modules/registrar.so lookup 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_send_reply 0(0) INFO: udp_init: SO_RCVBUF is initially 65536 0(0) DEBUG: udp_init: trying SO_RCVBUF: 131072 0(0) DEBUG: setting SO_RCVBUF; set=131072,verify=131072 0(0) DEBUG: udp_init: trying SO_RCVBUF: 262144 0(0) DEBUG: setting SO_RCVBUF; set=262144,verify=262144 0(0) INFO: udp_init: SO_RCVBUF is finally 262144 0(0) ERROR: tcp_init: bind(5, e83bc, 16) on 10.128.16.254: Address already in use 0(0) DEBUG: tm_shutdown : start 0(0) DEBUG: unlink_timer_lists : emptying DELETE list 0(0) DEBUG: tm_shutdown : emptying hash table 0(0) DEBUG: tm_shutdown : releasing timers 0(0) DEBUG: tm_shutdown : removing semaphores 0(0) DEBUG: tm_shutdown : destroying tmcb lists 0(0) DEBUG: tm_shutdown : done 0(20185) shm_mem_destroy 0(20185) destroying the shared memory lock The ser.cfg file used is attached with the mail. Plz sugest me some solution for mentioned problem... thanx 'n' regds, Parminder Nayyar

3 2

[OpenSER-Users] BLA errors
by Jeremy George 12 Jul '07

12 Jul '07

Hello All, I have BLA implemented, with errors. An ngrep trace of relevant packets showing errors follows. The configurations of both main proxy and bla presence server are attached. I stripped the main proxy to the bone. No outside routing at all. The bla presence server is almost all from the sample. 75.56.10.115 is a Cisco 7960 with one line registered: jeremy/private 75.56.10.116 is a Polycom 650 with two lines registered: jessica/private and helen/shared 75.56.10.117 is a Polycom 330 with two lines registered: didama/private and helen/shared 128.91.3.19 is the main proxy running openser v1.2.1 . 128.91.2.215 is the bla presence server running openser svn 2413 . This error: "1(1184) PUA:subs_cback_func: no reply message found" is being produced repeatedly on the bla presence server. Finally, I'm getting these error messages on the bla presence server: 0(1284) PUA_BLA: handle_notify: ERROR Notify in a non existing dialog 0(1284) WARNING: script writer didn't release transaction From time-to-time pua entries eat all of available memory. Curiously, they were all for the Polycom 330 and none were for the Polycom 650. Any help is greatly appreciated. Thanks. - Jeremy # U 128.91.2.215:5060 -> 75.56.10.117:5060 SUBSCRIBE sip:helen@75.56.10.117 SIP/2.0..Via: SIP/2.0/UDP 128.91.2.215;bra nch=z9hG4bKd187.ae440494.0..To: sip:helen@75.56.10.117;tag=9D362AB1-962A397 2..From: sip:helen@128.91.2.215;tag=45cdb744f974e73ed68392c080e87bb4-2684.. CSeq: 11 SUBSCRIBE..Call-ID: 7df1b9fa-810@128.91.2.215..Content-Length: 0.. User-Agent: OpenSER (1.3.0-dev7-tls (i386/linux))..Event: dialog;sla..Conta ct: <sip:helen@128.91.2.215>..Expires: 1810.... # U 75.56.10.117:5060 -> 128.91.2.215:5060 SIP/2.0 481 Call Leg/Transaction Does Not Exist..Via: SIP/2.0/UDP 128.91.2. 215;branch=z9hG4bKd187.9e440494.0..From: <sip:helen@128.91.2.215>;tag=45cdb 744f974e73ed68392c080e87bb4-2684..To: <sip:helen@75.56.10.117>;tag=9D362AB1 -962A3972..CSeq: 11 SUBSCRIBE..Call-ID: 7df1b9fa-810@128.91.2.215..Event: d ialog;sla..User-Agent: PolycomSoundPointIP-SPIP_330-UA/2.1.2.0049..Content- Length: 0.... # # U 128.91.2.215:5060 -> 75.56.10.117:5060 SUBSCRIBE sip:helen@75.56.10.117 SIP/2.0..Via: SIP/2.0/UDP 128.91.2.215;bra nch=z9hG4bK0de3.730cc385.0..To: sip:helen@75.56.10.117..From: sip:helen@128 .91.2.215;tag=45cdb744f974e73ed68392c080e87bb4-be09..CSeq: 10 SUBSCRIBE..Ca ll-ID: 7df1ba94-810@128.91.2.215..Content-Length: 0..User-Agent: OpenSER (1 .3.0-dev7-tls (i386/linux))..Event: dialog;sla..Contact: <sip:helen@128.91. 2.215>..Expires: 1820.... # U 75.56.10.117:5060 -> 128.91.2.215:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 128.91.2.215;branch=z9hG4bK0de3.730cc385.0 ..From: <sip:helen@128.91.2.215>;tag=45cdb744f974e73ed68392c080e87bb4-be09. .To: <sip:helen@75.56.10.117>;tag=8C7BE007-7BDCD3A4..CSeq: 10 SUBSCRIBE..Ca ll-ID: 7df1ba94-810@128.91.2.215..Contact: <sip:helen@75.56.10.117>..Event: dialog;sla..User-Agent: PolycomSoundPointIP-SPIP_330-UA/2.1.2.0049..Expire s: 1820..Content-Length: 0.... # # U 128.91.3.19:5060 -> 75.56.10.116:5060 SUBSCRIBE sip:helen@75.56.10.116 SIP/2.0..Record-Route: <sip:128.91.3.19;lr =on;ftag=36887A42-5425822F>..Via: SIP/2.0/UDP 128.91.3.19;branch=z9hG4bK27d 4.3e70f5b4.2..Via: SIP/2.0/UDP 75.56.10.117;branch=z9hG4bKa5b69571873BC26E. .From: "Helen" <sip:helen@128.91.3.19>;tag=36887A42-5425822F..To: <sip:hele n@128.91.3.19:5060>..CSeq: 1 SUBSCRIBE..Call-ID: aa7d279b-1806c1f8-b6acbe85 @75.56.10.117..Contact: <sip:helen@75.56.10.117>..Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER..Ev ent: call-info..User-Agent: PolycomSoundPointIP-SPIP_330-UA/2.1.2.0049..Max -Forwards: 70..Expires: 1800..Content-Length: 0.... # U 75.56.10.117:5060 -> 128.91.3.19:5060 SIP/2.0 482 Loop Detected..Via: SIP/2.0/UDP 128.91.3.19;branch=z9hG4bK27d4. 3e70f5b4.0..Via: SIP/2.0/UDP 75.56.10.117;branch=z9hG4bKa5b69571873BC26E..F rom: "Helen" <sip:helen@128.91.3.19>;tag=36887A42-5425822F..To: <sip:helen@ 128.91.3.19:5060>..CSeq: 1 SUBSCRIBE..Call-ID: aa7d279b-1806c1f8-b6acbe85@7 5.56.10.117..Contact: <sip:helen@75.56.10.117>..Record-Route: <sip:128.91.3 .19;lr=on;ftag=36887A42-5425822F>..Event: call-info..User-Agent: PolycomSou ndPointIP-SPIP_330-UA/2.1.2.0049..Content-Length: 0.... # U 75.56.10.116:5060 -> 128.91.3.19:5060 SIP/2.0 501 Not Implemented..Via: SIP/2.0/UDP 128.91.3.19;branch=z9hG4bK27d 4.3e70f5b4.1..Via: SIP/2.0/UDP 75.56.10.117;branch=z9hG4bKa5b69571873BC26E. .From: "Helen" <sip:helen@128.91.3.19>;tag=36887A42-5425822F..To: <sip:hele n@128.91.3.19:5060>;tag=BC1615E5-7F8E8B8C..CSeq: 1 SUBSCRIBE..Call-ID: aa7d 279b-1806c1f8-b6acbe85@75.56.10.117..Contact: <sip:helen@75.56.10.116>..Rec ord-Route: <sip:128.91.3.19;lr=on;ftag=36887A42-5425822F>..Event: call-info ..User-Agent: PolycomSoundPointIP-SPIP_650-UA/2.1.2.0078..Expires: 1800..Co ntent-Length: 0.... # # U 75.56.10.117:5060 -> 128.91.2.215:5060 NOTIFY sip:helen@128.91.2.215 SIP/2.0..Via: SIP/2.0/UDP 75.56.10.117;branch =z9hG4bK70de934cAD6A9A99..From: <sip:helen@75.56.10.117>;tag=8C7BE007-7BDCD 3A4..To: <sip:helen@128.91.2.215>;tag=45cdb744f974e73ed68392c080e87bb4-be09 ..CSeq: 1 NOTIFY..Call-ID: 7df1ba94-810@128.91.2.215..Contact: <sip:helen@7 5.56.10.117>..Event: dialog;sla..User-Agent: PolycomSoundPointIP-SPIP_330-U A/2.1.2.0049..Subscription-State: active;expires=1818..Max-Forwards: 70..Co ntent-Type: application/dialog-info+xml..Content-Length: 156....<?xml versi on="1.0"?>..<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version ="0" state="full" entity="sip:helen@128.91.3.19:5060">..</dialog-info> # U 128.91.2.215:5060 -> 75.56.10.117:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 75.56.10.117;branch=z9hG4bK70de934cAD6A9A9 9..From: <sip:helen@75.56.10.117>;tag=8C7BE007-7BDCD3A4..To: <sip:helen@128 .91.2.215>;tag=45cdb744f974e73ed68392c080e87bb4-be09..CSeq: 1 NOTIFY..Call- ID: 7df1ba94-810@128.91.2.215..Server: OpenSER (1.3.0-dev7-tls (i386/linux) )..Content-Length: 0.... # U 128.91.2.215:5060 -> 75.56.10.116:5060 NOTIFY sip:helen@75.56.10.116 SIP/2.0..Via: SIP/2.0/UDP 128.91.2.215;branch =z9hG4bK8d7b.ab428dd3.0..To: sip:helen@128.91.3.19;tag=FBC67234-A17D6FE3..F rom: sip:helen@128.91.2.215;tag=10.810.1184176700.14..CSeq: 3 NOTIFY..Call- ID: a023d5f7-3f2d49fe-76f2717d@75.56.10.116..Content-Length: 156..User-Agen t: OpenSER (1.3.0-dev7-tls (i386/linux))..Max-Forwards: 70..Event: dialog;s la..Contact: <sip:128.91.2.215:5060>..Subscription-State: active;expires=32 83..Content-Type: application/dialog-info+xml....<?xml version="1.0"?>.<dia log-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="15" state="ful l" entity="sip:helen@128.91.3.19:5060">.</dialog-info>. # U 75.56.10.116:5060 -> 128.91.2.215:5060 SIP/2.0 481 Call Leg/Transaction Does Not Exist..Via: SIP/2.0/UDP 128.91.2. 215;branch=z9hG4bK8d7b.ab428dd3.0..From: <sip:helen@128.91.2.215>;tag=10.81 0.1184176700.14..To: <sip:helen@128.91.3.19>;tag=FBC67234-A17D6FE3..CSeq: 3 NOTIFY..Call-ID: a023d5f7-3f2d49fe-76f2717d@75.56.10.116..Event: dialog;sl a..User-Agent: PolycomSoundPointIP-SPIP_650-UA/2.1.2.0078..Content-Length: 0.... # U 128.91.2.215:5060 -> 75.56.10.116:5060 NOTIFY sip:helen@75.56.10.116 SIP/2.0..Via: SIP/2.0/UDP 128.91.2.215;branch =z9hG4bK06ea.193b0e22.0..To: sip:helen@128.91.3.19;tag=D976CBBC-2176183F..F rom: sip:helen@128.91.2.215;tag=10.810.1184176890.21..CSeq: 2 NOTIFY..Call- ID: e11fdddb-9530f65a-3123a455@75.56.10.116..Content-Length: 156..User-Agen t: OpenSER (1.3.0-dev7-tls (i386/linux))..Max-Forwards: 70..Event: dialog;s la..Contact: <sip:128.91.2.215:5060>..Subscription-State: active;expires=34 73..Content-Type: application/dialog-info+xml....<?xml version="1.0"?>.<dia log-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="15" state="ful l" entity="sip:helen@128.91.3.19:5060">.</dialog-info>. # U 75.56.10.116:5060 -> 128.91.2.215:5060 SIP/2.0 481 Call Leg/Transaction Does Not Exist..Via: SIP/2.0/UDP 128.91.2. 215;branch=z9hG4bK06ea.193b0e22.0..From: <sip:helen@128.91.2.215>;tag=10.81 0.1184176890.21..To: <sip:helen@128.91.3.19>;tag=D976CBBC-2176183F..CSeq: 2 NOTIFY..Call-ID: e11fdddb-9530f65a-3123a455@75.56.10.116..Event: dialog;sl a..User-Agent: PolycomSoundPointIP-SPIP_650-UA/2.1.2.0078..Content-Length: 0.... # U 128.91.2.215:5060 -> 75.56.10.116:5060 NOTIFY sip:helen@75.56.10.116 SIP/2.0..Via: SIP/2.0/UDP 128.91.2.215;branch =z9hG4bKdcf1.0c60f511.0..To: sip:helen@128.91.3.19;tag=18F7DEB-D3FFDEAA..Fr om: sip:helen@128.91.2.215;tag=10.810.1184176985.23..CSeq: 2 NOTIFY..Call-I D: a7685c76-af0100e1-7b4a7078@75.56.10.116..Content-Length: 156..User-Agent : OpenSER (1.3.0-dev7-tls (i386/linux))..Max-Forwards: 70..Event: dialog;sl a..Contact: <sip:128.91.2.215:5060>..Subscription-State: active;expires=356 8..Content-Type: application/dialog-info+xml....<?xml version="1.0"?>.<dial og-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="15" state="full " entity="sip:helen@128.91.3.19:5060">.</dialog-info>. # U 75.56.10.116:5060 -> 128.91.2.215:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 128.91.2.215;branch=z9hG4bKdcf1.0c60f511.0 ..From: <sip:helen@128.91.2.215>;tag=10.810.1184176985.23..To: <sip:helen@1 28.91.3.19>;tag=18F7DEB-D3FFDEAA..CSeq: 2 NOTIFY..Call-ID: a7685c76-af0100e 1-7b4a7078@75.56.10.116..Contact: <sip:helen@75.56.10.116>..Event: dialog;s la..User-Agent: PolycomSoundPointIP-SPIP_650-UA/2.1.2.0078..Content-Length: 0....

2 1

[OpenSER-Users] OT: Asterisk mailing lists down
by Klaus Darilion 12 Jul '07

12 Jul '07

Hi! Am I the only one having problems with the Asterisk lists? thanks klaus

1 0

[Serusers] Help needed
by Azeem Mehmood 12 Jul '07

12 Jul '07

Dear Sir/Madam How are you? I hope you are fine. Can anybody help me installing SER from scratch. With Best Regards Azeem Mehmood ( President) Oskar-Tahir Sp z o.o ul. Regatowa 3A 03-639 Warsaw Poland Phone : +48604826332 WebSite:- www.voip-prof.com Email: voip-prof(a)voip-prof.com

1 0

[OpenSER-Users] OpenSER training course for admins
by Bogdan-Andrei Iancu 12 Jul '07

12 Jul '07

Hi, We have a good opportunity of organizing a one-day training course for OpenSER, specially for people looking for how to configure OpenSER. So, the targeted people are the OpenSER administrators that are looking to learn, via interactive sessions, based on script examples, how to configure different OpenSER features or services. We will try to mainly focus on the most complex and requested configuration cases, like: NAT traversal covering all cases Accounting - basic, extra accounting, multi-leg accounting General frame for routing (sequential request routing) Security (authentication, GW protection, blacklists) Integration to Asterisk (media services) Interdomain peering HA support (replication, GW redundancy) Now,about the course - as I said, it will be one day course and it will be hosted by the VoN Italy in Milan, on 26 September, from 9:30 to 18:00 hours. The package includes breakfast and lunch at the training location and the cost is estimated to be not more than 400 Euro per person. The event is organized in collaboration with Pulvermedia and right now we are looking to see how many people would be interested in this offer (technical side from openser.org and organization from Pulvermedia). Please feel free to contact me for any details/question. As I said, the first step is to see how many people are looking for such event, so let me know if you are interested in it. This survey will be ending Sunday 8th 24:00 CET. All this information will be posted on the openser project web page and forum. So, please give us the feedback regarding this opportunity to see if we go for it or not (also any suggestions are welcomed). Regards, Bogdan

8 10

[Serusers] 3-way conferences
by inge 12 Jul '07

12 Jul '07

Hi all, With two incoming calls, I'm able to initiate a 3-ways conference with my SPA-941 using the internal functionality. But, for ATAs which don't provide this function, is it possible to do that with SER ? Thanks for your support Adrien .L

2 2

[OpenSER-Users] Rewrite SDP for music of hold
by Iñaki Baz Castillo 12 Jul '07

12 Jul '07

Hi, I'm starting using OpenSer with Asterisk. In calls passing through Asterisk the caller or callee get music on hold of Asterisk when is put on hold. But of course, direct calls between OpenSer users don't get this music. I'm thinking in the posibility of detecting "on hold" reinvites (maybe reading the "a=sendonly" of SDP body) and rewriting the SDP IP contact to a music on hold server. I have no idea if this is possible. The first issue is how to set up a RTP music streamer for pointing there the SDP c header. Does "this" RTP music streamer exist? of course Asterisk is not a solution since I don't want to manage INVITE's, just rewrite the SDP. Second issue is: could be rewriting the SDP always sucessfull? what about cases with more than one RTP session as audio+video? So, is there any solution for offering music on hold with OpenSer? Thanks a lot. -- Iñaki Baz Castillo ibc(a)in.ilimit.es

5 5

[OpenSER-Users] quick question regarding pattern matching
by Zahid Mehmood 11 Jul '07

11 Jul '07

Hi all, I'm still trying to get a handle on using regular expression in openser. I can't seem to find any documentation on openser wiki on regular expression usage. I have the following in my openser.cfg and a call to sip: 48911(a)ourdomain.com is logged as emergency call. What am I doing wrong? if (uri=~"^sip:(99)|(9911)|(45555)|((93)?911)@") { xlog ("L_INFO","Emergency call \n"); } I am using this as a work around: if ((uri=~"^sip:(99)|(9911)|(45555)|(93911)@") || (uri=~"^sip: 911@")) Thanks in advance for your help. -- Zahid

2 2

[OpenSER-Users] Performance metric
by Pande, Piyush 11 Jul '07

11 Jul '07

Hi, Does anybody know what is the benchmark for calls/sec and number of simultaneous SIP calls that OpenSER can support?

1 0

Re: [Serusers] sl module functions in failure route
by Jiri Kuthan 11 Jul '07

11 Jul '07

At 16:34 11/07/2007, JF wrote: >Hi all, > >Is there any particular reason why sl module functions cannot be used >in failure routes? Yes. Failure_route is only invoked from within stateful processing. If a request was processed statelessly, SER does not really know if it failed. -jiri >I want to send a stateless reply in failure route. > >JF >_______________________________________________ >Serusers mailing list >Serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

4 5

[OpenSER-Users] Fw: Radius - prevent start record for ACK ?
by G.Jacobsen 11 Jul '07

11 Jul '07

Just discovered an acc parameter which does the trick and suppresses ACK accounting:modparam("acc", "report_ack", 0)Sorry for not reading properly.Still I am confused why radius receives start records with ACK before INVITE start records.CheersGerry----- Original Message ----- From: "G.Jacobsen" <g_jacobsen(a)yahoo.co.uk> To: <users(a)openser.org> Sent: Wednesday, July 11, 2007 8:06 PM Subject: Radius - prevent start record for ACK ? > I am using freeradius with openser 1.0.1. > > My problem is that openser is emitting TWO radius start records: One for the > INVITE with SIP method = 1 (INVITE) and also a second start record for SIP > Method = 4 (ACK) > > Is is normal that a start record is also emitted for the ACK ? > > As long as the INVITE record is sent before the ACK record that is no real > problem. > > However every-now-and-then (no pattern observed) Openser sends the Radius > start record with SIP Method = 4 (ACK) before the Record with SIP Method = 1 > for the INVITE. > > The problem is that the Radius record for the ACK does not contain the > username from the credentials so that the username is not correctly set in > the Radius record, instead of the correct username the callerid is used as > the username. > > How do I prevent that openser sends start records for the ACK ? Quite > frankly I do not understand why a start record for ACK is emitted since I > set the radius_flag only for INVITEs. > > the relevant parts from my configuration: > > modparam("acc", "radius_config", > "/usr/local/etc/radiusclient-ng/radiusclient.conf") > modparam("acc", "radius_flag", 1) > modparam("acc", "log_flag", 1) > modparam("acc", "service_type", 15) > > route{ > > ..... > # If this is an INVITE and not RE-INVITE start accounting > if(is_method("INVITE") && !has_totag()){ > # set the acc flags > setflag(1); > }; > > > if (is_method("ACK")) { #hop-by-hop ACKs are absorbed here > t_newtran(); > # drop broken ACKs > exit; > }; > > > Any hints are welcome. > > TIA > > Gerry > ___________________________________________________________ Inbox full of spam? Get leading spam protection and 1GB storage with All New Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html

1 0

[OpenSER-Users] duplicate phplib_id_key
by TCB 11 Jul '07

11 Jul '07

I have just installed OSER v 1.2.1 and i can only add one entry into my subscriber table after that i get the following error when i run openserctl add .... I can add directly into the db with phppgadmin either . I;m using pgsql. ERROR: duplicate key violates unique constraint "phplib_id_key" any ideas ? -- TC

3 2

[Serusers] nathelper timer error out of memory
by Kostas Marneris 11 Jul '07

11 Jul '07

Hello all, I have a setup with ser-0.9.6 on a x86-64 Debian Etch system with 8GB RAM. We use SIPP in order to stress test the system. As a first test we try to register about 150,000 users (the Registration requests arrival rate in not our concern at this time). We manage indeed to register 150,000 users and SER can stop/start with this location DB size. My setup concerning memory : config.h : #define PKG_MEM_POOL_SIZE 512*1024*1024 serctl file: STARTOPTIONS='-m 128' Although, at about 15,000-20,000 contacts at location DB, I get the following error, every 30 seconds : ERROR: nathelper::timer: out of memory natelper module config : modparam("nathelper", "rtpproxy_disable", 1) modparam("nathelper", "natping_interval", 30) modparam("nathelper", "ping_nated_only", 1) Searching the mailing list I found the following : http://lists.iptel.org/pipermail/serusers/2004-March/006828.html We actually changed the PKG_MEM_POOL_SIZE to 512*1024*1024 and recompile but we still get this error. thanks for any help, Kostas

1 1

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