sr-users January 2009

sr-users@lists.kamailio.org

85 participants
110 discussions

[Kamailio-Users] debian packages not found
by Amit Agarwal 15 Jan '09

15 Jan '09

Hi, I have looked into the following paths, But I could not find the required package. http://www.kamailio.org/debian/dists/stable/main/binary-i386/ http://www.kamailio.org/debian/dists/stable/non-free/binary-i386/ http://www.kamailio.org/debian/dists/etch/main/binary-i386/ http://www.kamailio.org/debian/dists/etch/non-free/binary-i386/ Also, I wish to know the difference in the packages contained in the above folders. Thanks, Regards, Amit

2 1

[Kamailio-Users] new developer: Inaki Baz Castillo
by Daniel-Constantin Mierla 14 Jan '09

14 Jan '09

Hello, here it is the proper welcome of Iñaki Baz Castillo as developer -- SourceForge id: ibc_sf. Log time community member and active contributor with troubleshooting, patches and support emails, Inaki committed his first module today (announcements sent hours ago): http://lists.kamailio.org/pipermail/devel/2009-January/017544.html He has an extensive knowledge of SIP and he is know as PITA for those writing confusing RFCs. Thanks for your work and looking forward to collaborating in the project. Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

3 2

[Kamailio-Users] New module "Regex"
by Iñaki Baz Castillo 14 Jan '09

14 Jan '09

Hi all, I announce the first commit of "Regex" module to Kamailio trunk. This module offers matching operations against regular expressions using the powerful PCRE library. A text file containing regular expressions categorized in groups is compiled when the module is loaded, storing the compiled PCRE objects in an array. A function to match a string or pseudo-variable against any of these groups is provided. The text file can be modified and reloaded at any time via a MI command. The module also offers a function to perform a PCRE matching operation against a regular expression provided as function parameter. The module documentation is already online: http://kamailio.org/docs/modules/devel/regex.html The commit has been done in rev 5458: http://openser.svn.sourceforge.net/viewvc/openser?view=rev&revision=5458 Any suggestion is really welcome. -- Iñaki Baz Castillo <ibc(a)aliax.net>

3 2

[Kamailio-Users] snmpstats error
by Noel R. Morais 14 Jan '09

14 Jan '09

Hi guys, I'm trying to use the snmpstats module but on kamailio initialization it shows me the error: kamailio: ERROR:core:sr_load_module: could not open module </usr/local/lib/kamailio/modules/snmpstats.so>: /usr/lib/libnetsnmpagent.so.10: undefine d symbol: make_tempfile I've found in this lists a post asking to remove the follow line from Makefile: BUILDAGENTLIBS:=$(filter-out %netsnmpmibs, $(BUILDAGENTLIBS)) but this line doesn't exists. Does anyone know how to fix that? My system: Kamailio 1.4.2 notls CentOS 5 Kernel 2.6.18-92 Thanks in advance, Noel

3 4

[Kamailio-Users] perlvdb
by victorpy 13 Jan '09

13 Jan '09

Hello, i could be wrong but what i read from perlvdb is that using that module you abstract from the DB engine. I want to know if it's posible with this module to load a database in memory. I want to do this for performance. if is posible could you give an example, otherwise you could give a hint to solve this thanks bye -- View this message in context: http://www.nabble.com/perlvdb-tp21421051p21421051.html Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.

4 5

[Kamailio-Users] playing different announcements to user
by Luciano Afranllie 13 Jan '09

13 Jan '09

Hi, I have not experience doing this so I want to ask you what is the best approach to instruct a media server about what announcement to play to the user. For example, if I use asterisk, should I define one extension per announcement type? Is this the common approach? Thanks Luciano

4 4

Re: [Kamailio-Users] WARNING:core:send2child: no free tcp receiver
by Ali Jawad 13 Jan '09

13 Jan '09

Adding to the below I am getting these errors Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]: ERROR:core:tcpconn_connect: tcp_blocking_connect failed Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]: ERROR:core:tcp_send: connect failed Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]: ERROR:sl:msg_send: tcp_send failed Jan 12 12:35:30 sero /usr/local/sbin/openser[30076]: ERROR:auth:challenge: failed to send the response Jan 12 12:35:31 sero /usr/local/sbin/openser[30076]: ERROR:core:tcp_blocking_connect: poll error: flags 18 Jan 12 12:35:31 sero /usr/local/sbin/openser[30076]: ERROR:core:tcp_blocking_connect: failed to retrieve SO_ERROR (111) Connection refused With Regards Ali Jawad System Administrator Splendor Telecom (www.splendor.net <outbind://210/www.splendor.net> ) Beirut, Lebanon Phone: +961 1 373725 Fax: + 961 1 375554 ________________________________ From: Ali Jawad Sent: 2009-01-12 12:33 To: Ali Jawad; users(a)lists.opensips.org Cc: users(a)lists.kamailio.org Subject: RE: [OpenSIPS-Users] WARNING:core:send2child: no free tcp receiver As an update I have retrieved this [root@sero ~]# /usr/local/sbin/openserctl ps Process:: ID=0 PID=30033 Type=attendant Process:: ID=1 PID=30036 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=2 PID=30037 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=3 PID=30038 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=4 PID=30039 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=5 PID=30041 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=6 PID=30042 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=7 PID=30043 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=8 PID=30044 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=9 PID=30045 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=10 PID=30046 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=11 PID=30047 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=12 PID=30048 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=13 PID=30049 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=14 PID=30050 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=15 PID=30051 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=16 PID=30052 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=17 PID=30053 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=18 PID=30054 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=19 PID=30055 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=20 PID=30056 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=21 PID=30057 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=22 PID=30060 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=23 PID=30062 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=24 PID=30064 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=25 PID=30065 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=26 PID=30066 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=27 PID=30067 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=28 PID=30068 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=29 PID=30069 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=30 PID=30070 Type=SIP receiver udp:xx.yy.zz.aa:5060 Process:: ID=31 PID=30071 Type=timer Process:: ID=32 PID=30072 Type=timer Process:: ID=33 PID=30073 Type=MI FIFO Process:: ID=34 PID=30074 Type=TCP receiver Process:: ID=35 PID=30075 Type=TCP receiver Process:: ID=36 PID=30076 Type=TCP receiver Process:: ID=37 PID=30077 Type=TCP receiver Process:: ID=38 PID=30079 Type=TCP receiver Process:: ID=39 PID=30080 Type=TCP receiver Process:: ID=40 PID=30081 Type=TCP receiver Process:: ID=41 PID=30082 Type=TCP receiver Process:: ID=42 PID=30084 Type=TCP receiver Process:: ID=43 PID=30085 Type=TCP receiver Process:: ID=44 PID=30086 Type=TCP receiver Process:: ID=45 PID=30087 Type=TCP receiver Process:: ID=46 PID=30090 Type=TCP receiver Process:: ID=47 PID=30091 Type=TCP receiver Process:: ID=48 PID=30092 Type=TCP receiver Process:: ID=49 PID=30094 Type=TCP receiver Process:: ID=50 PID=30095 Type=TCP receiver Process:: ID=51 PID=30096 Type=TCP receiver Process:: ID=52 PID=30097 Type=TCP receiver Process:: ID=53 PID=30098 Type=TCP receiver Process:: ID=54 PID=30099 Type=TCP receiver Process:: ID=55 PID=30100 Type=TCP receiver Process:: ID=56 PID=30101 Type=TCP receiver Process:: ID=57 PID=30102 Type=TCP receiver Process:: ID=58 PID=30103 Type=TCP receiver Process:: ID=59 PID=30104 Type=TCP receiver Process:: ID=60 PID=30105 Type=TCP receiver Process:: ID=61 PID=30107 Type=TCP receiver Process:: ID=62 PID=30109 Type=TCP receiver Process:: ID=63 PID=30110 Type=TCP receiver Process:: ID=64 PID=30111 Type=TCP main With Regards Ali Jawad System Administrator Splendor Telecom (www.splendor.net <outbind://206/www.splendor.net> ) Beirut, Lebanon Phone: +961 1 373725 Fax: + 961 1 375554 ________________________________ From: users-bounces(a)lists.opensips.org [mailto:users-bounces@lists.opensips.org] On Behalf Of Ali Jawad Sent: 2009-01-12 02:31 To: users(a)lists.opensips.org Cc: users(a)lists.kamailio.org Subject: [OpenSIPS-Users] WARNING:core:send2child: no free tcp receiver Hi All I am getting a lot of WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (7) I tried setting children to 20 that did not help, these warning start being displayed right after I start openser. Users frequently get service unavailable errors randomly when they try to connect, but I dont know if this is related to this warning message or not. As for the server there is plenty of CPU and RAM left, users range from 140 to 250 online all using tls. As for server limits I have set them to the following : You have new mail in /var/spool/mail/root [root@sero openser]# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited pending signals (-i) 1024 max locked memory (kbytes, -l) 32 max memory size (kbytes, -m) unlimited open files (-n) 101024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 16382 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Is this warning message related to the serice unavailable problem, what does the warning message mean in more depth and how to get rid of it ? Thanks Getting alot of Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (7) Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (7) Jan 12 00:00:32 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (7) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (8) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (8) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (8) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (8) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (9) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (9) Jan 12 00:00:33 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (9) Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (9) Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:34 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10) Jan 12 00:00:35 sero /usr/local/sbin/openser[28281]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (10)

3 4

Re: [Kamailio-Users] About Kamailio-1.4.0-notls.
by Sunil Teli 13 Jan '09

13 Jan '09

And also when I(Application A) send the Subscribe message with the Dialog event to the kamailio server, The kamailio server is not forwarding that Subscribe message to party B. Since kamailio acts as proxy it has to forward the Subscribe message to the party to whom I have Subscribed(ie Party B an x-lite phone). The call flow is as follows. REISTER A(APP) kamailio B(x-lite) C(x-lite) | | | | 200 OK | | | | | | | | REGISTER REGISTER | | | | | | | | 200 OK | | | | | | | | 200 OK | | | | | | | | SUBSCRIBE | | | | | | | | 202 OK | | | | | | | | NOTIFY | | | | Call Established between B and C | | | | 200 OK | | | | | | | | | | | | | | | | I am using kamailio-1.4.0-notls and trying to use dialog event package. The above call flow is as follows. 1) B an x-lite phone is Registered(B@kamailio) then C another x-lite phone is registered(c@kamailio) 2) Now from my application I am registering A and got registered(A@kamailio). 3) Now A is subscribing to B for the dialog event, so I am sending SUBSCRIBE message to kamailio server, that is I am sending SUBSCRIBE message from A@application to B@kamailio with the Event header. 4) Now I got 202 for the SUBSCRIBE. 5) Server Kamailio sends NOTIFY and then my application A sends 200 OK. 6) Now I will establish call between two x-lite phones B and C. Now My Question? When I establish call between B and C, I(Application A) have to get NOTIFY from kamailio server about the dialog event, I am not getting the NOTIFY for the dialog event since I have Subscribed to B for the Dialog event Package. Finally I(A application) want to know that dialog changes in the B. But Dialog module is present in the kamailio code. So for what purpose is it used? Is there any modules I have to include or provision in the config file or make file, If yes then where I have to make the changes. Thank You Regards, Sunil Teli -----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Monday, January 12, 2009 7:08 PM To: Sunil Teli Cc: users Subject: Re: [Kamailio-Users] About Kamailio-1.4.0-notls. Hi Sunil! Kamailio 1.4 does not support the "dialog" event package. You have to use Kamailio "trunk" version. Trunk includes 2 new modules: PUA_DIALOGINFO: generates PUBLISH requests to publish the dialog state PRESENCE_DIALOGINFO: processes PUBLISH requests, aggregate dialog information and send it with NOTIFY to the watcher Please see the detailed READMEs of these modules. http://www.kamailio.org/docs/modules/devel/ regards klaus ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra. ============================================================================================================================

3 4

[Serusers] db_query in failure_route
by John G. Rose 12 Jan '09

12 Jan '09

I noticed that a db_query in a failure route works in some situations but not in others. Is there way to make it work all the time? I know in SER <2.0 you are supposed to not do this. In 2.0 it works sometimes. Also I noticed in some db_ops documentation there is the db_proper() failure route hack fix but this is not in SER 2.0 db_ops code apparently... John

1 0

[Kamailio-Users] Segment fault with trunk version and default config file
by Iñaki Baz Castillo 12 Jan '09

12 Jan '09

Hi, I've upgraded Kamailio to the trunk version (ref 5440). i've compiled in with "make deb-etch" in my Debian Etch 64 bits as so many times. If I start Kamailio "with /etc/init.d/kamailio start" I get the following logs in which no error appear, but are obviously incomplete: ------------------------- Not starting kamailio: invalid configuration file! Jan 12 18:10:02 [8915] DBG:core:yyparse: loading module /usr/lib/kamailio/modules/sl.so Jan 12 18:10:02 [8915] DBG:core:yyparse: loading module /usr/lib/kamailio/modules/tm.so Jan 12 18:10:02 [8915] DBG:core:register_module: register_pv: tm Jan 12 18:10:02 [8915] DBG:core:pv_table_add: PV table not initialized, doing it now Jan 12 18:10:02 [8915] DBG:core:yyparse: loading module /usr/lib/kamailio/modules/rr.so Jan 12 18:10:02 [8915] DBG:core:yyparse: loading module /usr/lib/kamailio/modules/pv.so Jan 12 18:10:02 [8915] DBG:core:tr_table_add: TR table not initialized, doing it now Jan 12 18:10:02 [8915] DBG:core:register_module: register_pv: pv Jan 12 18:10:02 [8915] DBG:core:yyparse: loading module /usr/lib/kamailio/modules/maxfwd.so Jan 12 18:10:02 [8915] DBG:core:yyparse: loading module /usr/lib/kamailio/modules/usrloc.so Jan 12 18:10:02 [8915] DBG:core:yyparse: loading module /usr/lib/kamailio/modules/registrar.so Jan 12 18:10:02 [8915] DBG:core:register_module: register_pv: registrar Jan 12 18:10:02 [8915] DBG:core:yyparse: loading module /usr/lib/kamailio/modules/textops.so Jan 12 18:10:02 [8915] DBG:core:yyparse: loading module /usr/lib/kamailio/modules/mi_fifo.so Jan 12 18:10:02 [8915] DBG:core:yyparse: loading module /usr/lib/kamailio/modules/uri_db.so Jan 12 18:10:02 [8915] DBG:core:yyparse: loading module /usr/lib/kamailio/modules/siputils.so Jan 12 18:10:02 [8915] DBG:core:yyparse: loading module /usr/lib/kamailio/modules/xlog.so Jan 12 18:10:02 [8915] DBG:core:register_module: register_pv: xlog Jan 12 18:10:02 [8915] DBG:core:yyparse: loading module /usr/lib/kamailio/modules/acc.so Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: mi_fifo matches module mi_fifo Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <fifo_name> in module mi_fifo [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: rr matches module rr Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <enable_full_lr> in module rr [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: rr matches module rr Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <append_fromtag> in module rr [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: registrar matches module registrar Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <method_filtering> in module registrar [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: uri_db matches module uri_db Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <use_uri_table> in module uri_db [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: uri_db matches module uri_db Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <db_url> in module uri_db [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: acc matches module acc Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <early_media> in module acc [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: acc matches module acc Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <report_ack> in module acc [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: acc matches module acc Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <report_cancels> in module acc [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: acc matches module acc Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <detect_direction> in module acc [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: acc matches module acc Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <failed_transaction_flag> in module acc [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: acc matches module acc Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <log_flag> in module acc [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: acc matches module acc Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <log_missed_flag> in module acc [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: acc matches module acc Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <db_flag> in module acc [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: acc matches module acc Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <db_missed_flag> in module acc [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: usrloc matches module usrloc Jan 12 18:10:02 [8915] DBG:core:set_mod_param_regex: found <db_mode> in module usrloc [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <mf_process_maxfwd_header>(1) in module maxfwd [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <sl_send_reply>(2) in module sl [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <has_totag>(0) in module siputils [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <loose_route>(0) in module rr [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <is_method>(1) in module textops [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <is_method>(1) in module textops [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <t_check_trans>(0) in module tm [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <t_relay>(0) in module tm [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <sl_send_reply>(2) in module sl [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <is_method>(1) in module textops [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <t_check_trans>(0) in module tm [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <t_relay>(0) in module tm [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <t_check_trans>(0) in module tm [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <is_method>(1) in module textops [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <record_route>(0) in module rr [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <is_method>(1) in module textops [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <append_hf>(1) in module textops [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <is_method>(1) in module textops [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <sl_send_reply>(2) in module sl [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <is_method>(1) in module textops [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <save>(1) in module registrar [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <sl_reply_error>(0) in module sl [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <sl_send_reply>(2) in module sl [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <lookup>(1) in module registrar [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <t_newtran>(0) in module tm [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <t_reply>(2) in module tm [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <sl_send_reply>(2) in module sl [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <is_method>(1) in module textops [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <t_on_branch>(1) in module tm [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <t_on_reply>(1) in module tm [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <t_on_failure>(1) in module tm [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <t_relay>(0) in module tm [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <sl_reply_error>(0) in module sl [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <xlog>(1) in module xlog [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <xlog>(1) in module xlog [/usr/lib/kamailio/modules/] Jan 12 18:10:02 [8915] DBG:core:find_cmd_export_t: found <t_was_cancelled>(0) in module tm [/usr/lib/kamailio/modules/] ---------------------------------- If I run directly "kamailio" I get a segmentation fault, this explain that there is no error log above. -- Iñaki Baz Castillo <ibc(a)aliax.net>

1 0

← Newer
1
...
5
6
7
8
9
10
11
Older →

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 January 2009