sr-users October 2008

sr-users@lists.kamailio.org

93 participants
169 discussions

Re: [Kamailio-Users] Users Digest, Vol 41, Issue 68

by Mian M Asif

Dear Abalashov, What do you mean by "no[t] getting any response? is mean this function is not working please let me know i am doing right or wrong, dear Arif, exit also is not working cheers :). regards, Asif > Today's Topics: > > 1. Re: Architecture with load-balancing (dispatcher module) > (Ovidiu Sas) > 2. i want to stop second registration request if user already > registered (Mian M Asif) > 3. Re: i want to stop second registration request if user > already registered (Alex Balashov) > 4. Re: i want to stop second registration request if user > already registered (arif.zaman) > 5. Re: Anyone doing CNAM lookups? (Klaus Darilion) > 6. Kamailio v1.4.2 Released (Daniel-Constantin Mierla) > > > Message: 2 > Date: Thu, 23 Oct 2008 19:49:21 +0500 > From: "Mian M Asif" <asif44pk(a)gmail.com> > Subject: [Kamailio-Users] i want to stop second registration request > if user already registered > To: users(a)lists.kamailio.org > Message-ID: > <b005c33b0810230749v1b00bf9auabb97cfc17e517c6(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi All, > i want to stop second registration request if use already registered i > am using below code but getting no any response. please help me how to > solve this problem. > > if (method=="REGISTER") { > if (registered("location") ) { > xlog("L_NOTICE","Asif: lookup(location) Passed\n"); > sl_send_reply("699", "User Not Found"); > return; > } > route(2); > return; > > route[2] { > > # ----------------------------------------------------------------- > # REGISTER Message Handler > # ---------------------------------------------------------------- > xlog("L_NOTICE","Danish: Entering route[2]\n"); > # if (registered("location")) { > # xlog("L_NOTICE","Asif: lookup(location) failed\n"); > # sl_send_reply("404", "User Not Found"); > # return; > # }; > > xlog("L_NOTICE","Asif: Register message IPsrcaddr [$si], > RecvdIPaddr[$Ri]\n"); > if (!search("^Contact:[ ]*\*") && nat_uac_test("2")) { > xlog("L_NOTICE","Danish: In route[2] Found Nated contact\n"); > setflag(6); > setbflag(6); > # if you want OPTIONS natpings uncomment next > setbflag(7); > fix_nated_register(); > force_rport(); > }; > > sl_send_reply("100", "Trying"); > > if (!radius_www_authorize("abc.com")) { > www_challenge("abc.com", "1"); > }; > consume_credentials(); > > if (!save("location")) { > sl_reply_error(); > }; > > } > } > > regards, > Asif > > > > ------------------------------ > > Message: 3 > Date: Thu, 23 Oct 2008 10:51:30 -0400 > From: Alex Balashov <abalashov(a)evaristesys.com> > Subject: Re: [Kamailio-Users] i want to stop second registration > request if user already registered > To: Mian M Asif <asif44pk(a)gmail.com> > Cc: users(a)lists.kamailio.org > Message-ID: <49008F72.1060700(a)evaristesys.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > What do you mean by "no[t] getting any response?" > > Mian M Asif wrote: > >> Hi All, >> i want to stop second registration request if use already registered i >> am using below code but getting no any response. please help me how to >> solve this problem. >> >> if (method=="REGISTER") { >> if (registered("location") ) { >> xlog("L_NOTICE","Asif: lookup(location) Passed\n"); >> sl_send_reply("699", "User Not Found"); >> return; >> } >> route(2); >> return; >> >> route[2] { >> >> # ----------------------------------------------------------------- >> # REGISTER Message Handler >> # ---------------------------------------------------------------- >> xlog("L_NOTICE","Danish: Entering route[2]\n"); >> # if (registered("location")) { >> # xlog("L_NOTICE","Asif: lookup(location) failed\n"); >> # sl_send_reply("404", "User Not Found"); >> # return; >> # }; >> >> xlog("L_NOTICE","Asif: Register message IPsrcaddr [$si], >> RecvdIPaddr[$Ri]\n"); >> if (!search("^Contact:[ ]*\*") && nat_uac_test("2")) { >> xlog("L_NOTICE","Danish: In route[2] Found Nated contact\n"); >> setflag(6); >> setbflag(6); >> # if you want OPTIONS natpings uncomment next >> setbflag(7); >> fix_nated_register(); >> force_rport(); >> }; >> >> sl_send_reply("100", "Trying"); >> >> if (!radius_www_authorize("abc.com")) { >> www_challenge("abc.com", "1"); >> }; >> consume_credentials(); >> >> if (!save("location")) { >> sl_reply_error(); >> }; >> >> } >> } >> >> regards, >> Asif >> >> _______________________________________________ >> Users mailing list >> Users(a)lists.kamailio.org >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > > > -- > Alex Balashov > Evariste Systems > Web : http://www.evaristesys.com/ > Tel : (+1) (678) 954-0670 > Direct : (+1) (678) 954-0671 > Mobile : (+1) (706) 338-8599 > > > > ------------------------------ > > Message: 4 > Date: Thu, 23 Oct 2008 07:59:45 -0700 (PDT) > From: "arif.zaman" <arif.zaman(a)brotecs.com> > Subject: Re: [Kamailio-Users] i want to stop second registration > request if user already registered > To: users(a)lists.kamailio.org > Message-ID: <20132764.post(a)talk.nabble.com> > Content-Type: text/plain; charset=us-ascii > > > > Mian M Asif wrote: >> >> if (method=="REGISTER") { >> if (registered("location") ) { >> xlog("L_NOTICE","Asif: lookup(location) Passed\n"); >> sl_send_reply("699", "User Not Found"); >> return; >> } >> > > Use "exit;" instead of "return;". > > Cheers, > ARIF >

15 years, 6 months

[Kamailio-Users] Anyone doing CNAM lookups?

by Brian McCrary

I've been using OpenSER 1.0.1 for the past couple of years, but I now need to add CNAM lookups. It looks like the presence module might be what I need, although from the looks if it, it's made to respond to lookups, instead of actually generate a query to another server for a lookup. I'm looking at doing CNAM lookups with Verisign which look to interface with a SUBSCRIBE message, in which in return Verising sends back a NOTIFY message with one of the fields being "calling-name" which has the CNAM info in it. Has anyone been succesful in implementing such a lookup with Verisign or another CNAM database provider? Brian

15 years, 6 months

[Serusers] SER without any fork(), It is possible?

by Samuel Ayet San Andres

Hi all, I´m trying to use SER (SIP Express Router) in a linux enbedded system with uClinux. In my enbedded processor i dont have any MMU so it cant fork(), it uses vfork() that is a cousin of fork but diferent because qhen father vfork a child, stops until the child make execve() or exit. When I run SER on my embedded plataform in a debug mode it shows me: ERROR: main_loop can´t fork(); Then I try to chage all forks for vfork() but it still not working due to the childs never make execve(). And after the explain of the context, here is the question: can I run SER without any child? Can I run SER without making any fork? I mean that only ONE process (witout deamonize) will run alone. I don´t need to manage more than 1 call...I only want to have one process listening to ONE IP. I have try to change the configuration of the ser 'ser.cfg' asi show: fork=no childrens=0 But still without working and i´m not sure if this is the right way to run SER without forking... Thank you for you support. Samuel. --

15 years, 6 months

[Kamailio-Users] presence network Agent

by suresh tattikota

Hi all I am working on Presence network Agent. please let me know any one is working on the same . thank you all suresh

15 years, 6 months

Re: [Kamailio-Users] Record Route and proxy behind static NAT

by Zappasodi Daniele

Thanks for your reply. I'm agree with your observations. I had already tried to solve the situations as described in the draft (avoiding spiral) and I have built a configuration that seem to work, at least for the basic call, but my solution needs to much tricks and I'm not sure that what I have done is safe and if it works in more complex call flows. I set the IP address in Record Route depending on position public\private of the callee and I substitute the IP address in Record Route for each reply, when it needs. First of all I suppose to know if the caller and callee is private or public (I check if the Request URI domain with RFC 1918) and I don't know if this is right. Then there is the problem to write the record route. I have moved the record route section in a branch route, because here I know the final destination for each branch. Here there is another doubt: I rewrote the record_route_preset function in order to remove the limit of one record route because in parallel forking I set more than record for each transaction, one record route for each branch. What are the consequences? I risk "only" to loose a call or to kill the proxy? I would prefer to leave the record route section at the beginning, but is it possible to substitute the record route after it is added? I remember that is possible to change only the original message and that there are some limitations on the possibility to change an header added during the message processing (I had some segmentation faults when I tryed with a custom header). Just now I'm looking on what to do with a relay from the failure route to a second destination. Before I proceding on this way I would like to know if I'm going on the wrong direction and if someone has found a simpler solution with this kind of scenarios. Regards, Daniele > Date: Wed, 22 Oct 2008 19:02:35 +0200 > From: " I?aki Baz Castillo " <ibc(a)aliax.net> > Subject: Re: [Kamailio-Users] Record Route and proxy behind static NAT > Cc: users(a)lists.kamailio.org > Message-ID: > <cc1f582e0810221002i7c95570epf585456a248811d1(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > The solution could be adding two Record-Routes, one with private IP > and the other with public IP, but I'm not sure of how to achieve it > with Kamailio. AFAIK Kamailio *already* does it when the transaction > comes via eth0 and leaves the proxy via eth1, but this is not your > case. > I recommend you reading this draft, and later trying to get it in Kamailio: > http://tools.ietf.org/html/draft-ietf-sip-record-route-fix > (5. Double Record-Routing) ********************************************************************** The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message inerror. **********************************************************************

15 years, 6 months

[Kamailio-Users] Kamailio v1.4.2 Released

by Daniel-Constantin Mierla

Hello everybody, a new release in 1.4 series is out. Kamailio 1.4.2 is based on the latest version of branch 1.4, including many fixes in code and documentation, therefore those running 1.4.0 or 1.4.1 are advised to upgrade. This is a minor release that includes updates since v1.4.1 - configuration file and database compatibility is preserved. Source tarballs are available at: http://www.kamailio.org/pub/kamailio/1.4.2/src/ <http://www.kamailio.org/pub/kamailio/1.4.2/src> Detailed changelog: http://www.kamailio.org/pub/kamailio/1.4.2/ChangeLog Download via SVN: svn co https://openser.svn.sourceforge.net/svnroot/openser/branches/1.4 kamailio Tag for this release can be browsed at: http://openser.svn.sourceforge.net/viewvc/openser/tags/1.4.2/ Project site at SourceForge.net: http://sourceforge.net/projects/openser/ Modules' documentation: http://www.kamailio.org/docs/modules/1.4.x/ <http://www.kamailio.org/docs/modules/1.4.x> What is new in 1.4.x release series is summarized in the announcement of v1.4.0: http://www.kamailio.org/mos/view/KAMAILIO-v1.4.0-Released Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

15 years, 6 months

[Kamailio-Users] Architecture with load-balancing (dispatcher module)

by Pascal Maugeri

Hi I was wondering how to achieve an architecture with two or more active load-balancer nodes (kamailio+dispatcher module). I have read how to setup two dispatcher nodes, one node as a master and the other one as a backup. The backup node doesn't process any traffic until master fails. But how to make the traffic being processed by both load-balancers ? In the case for instance the capacity of single node is not enough to process all incoming traffic. Is there any recommended configuration (eg. using frontal application-level swith) Regards, Pascal

15 years, 6 months

Re: [Kamailio-Users] Architecture with load-balancing (dispatcher module)

by Daniel-Constantin Mierla

On 10/23/08 15:05, Pascal Maugeri wrote: > > On Thu, Oct 23, 2008 at 1:47 PM, Daniel-Constantin Mierla > <miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote: > > Hello, > > a solution I am using is to do shared IP (vrrp/ucarp). The typical > scenario is active-backup, when one share IP is used. > > But you can do active-active by using two shared IP addresses, so > will be > > server1: active_ip_1 - backup_ip_2 > server2: backup_ip_1 - active_ip_2 > > So each server is active and backs-up the other. This can be > scaled, with more than 2 servers, you need an IP per server, and > you will have a chain of active servers backing up next one. Based > on who is backing up who, you may have one or more servers down > without affecting the service > > You have to take care of balancing the traffic among the IP addresses. > > > OK but how do you share traffic among the IP addresses ? You need a > kind of super load-balancer that load-balance traffic among > load-balancers ? one way you can do it is via DNS. Daniel > -pascal > > > > > Cheers, > Daniel > > > > On 10/23/08 13:16, Alex Balashov wrote: > > Any "frontal application-level switch" would simply have the > same liability. > > Kamailio is a very high-throughput proxy that can handle huge > amounts of call setups per second. I think you can count on that. > > Failing over around the load balancer node to a secondary load > balancer or distributing the traffic among multiple load > balancers is a job best left to the sending endpoint. For > example, a DID origination provider's switch or SBC can be set > up to fail over calls to a different IP endpoint for your SIP > trunk if no response is received within a certain amount of > time. That is how this is typically done. At some point > you've got to say that you've done all you can do, and it's up > to the other side. > > Pascal Maugeri wrote: > > > > Hi > > I was wondering how to achieve an architecture with two or > more active load-balancer nodes (kamailio+dispatcher module). > > I have read how to setup two dispatcher nodes, one node as > a master and the other one as a backup. > > The backup node doesn't process any traffic until master > fails. But how to make the traffic being processed by both > load-balancers ? In the case for instance the capacity of > single node is not enough to process all incoming traffic. > Is there any recommended configuration (eg. using frontal > application-level swith) > > Regards, > Pascal > > > ------------------------------------------------------------------------ > > _______________________________________________ > Users mailing list > Users(a)lists.kamailio.org <mailto:Users@lists.kamailio.org> > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users > > > > > > > > -- > Daniel-Constantin Mierla > http://www.asipto.com > > -- Daniel-Constantin Mierla http://www.asipto.com

15 years, 6 months

[Kamailio-Users] Usrloc: cache vs database inconsistencies

by CSB

I have noticed a consistent difference between the location records OpenSER has cached and those stored in the database. e.g. openserctl ul show --brief database engine 'MYSQL' loaded Control engine 'FIFO' loaded entering fifo_cmd ul_dump brief Domain:: location table=512 records=19 max_slot=2 Compared to: select count(*) from ser.location; +----------+ | count(*) | +----------+ | 10 | +----------+ 1 row in set (0.00 sec) This difference is consistent over time. When I look at the database logs OpenSER is trying to update an existing record in the database which, for some reason, doesn't exist. Our config has the following relevant parameters modparam("usrloc", "db_mode", 2) Openser 1.3.2 Any thoughts on how to prevent this circumstance from occurring and how to synchronise the cache with the db in an orderly manner? I had thought that after 120 seconds (timer_interval default)this would happen but it doesn't seem to. Any advice appreciated. Regards Cameron

15 years, 6 months

[Kamailio-Users] Hold - core dump

by Marian Piater

Hello, I tried Kamailio 1.4.1+TLS with Mediaproxy 2.1.0. Everything works fine, but when I place call to Hold (using Hold button), Kamailio sometimes crashed. When I disable mediaproxy, Kamailio works without crash. I tried using engage_media_proxy() without any end_media_proxy or use_media_proxy and I also tried using use_media_proxy and end_media_proxy without engage_media_proxy with that same result. Sometimes Kamailio crash after first place call to hold, sometimes crash after few place call to hold/unhold. Sometimes work fine. OS is Debian Etch. Kamailio generate core dump. Core was generated by `kamailio'. Program terminated with signal 11, Segmentation fault. #0 0xb7d1e19a in strnlen () from /lib/tls/i686/cmov/libc.so.6 (gdb) bt #0 0xb7d1e19a in strnlen () from /lib/tls/i686/cmov/libc.so.6 #1 0xb7cf13f1 in vfprintf () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7d0fb01 in vsnprintf () from /lib/tls/i686/cmov/libc.so.6 #3 0xb7cf6945 in snprintf () from /lib/tls/i686/cmov/libc.so.6 #4 0xb7888e10 in end_media_session (callid=<value optimized out>, from_tag={s = 0x2 "", len = 4}, to_tag= {s = 0xbf9ce1b8 "remove\r\ncall_id: \r\nfrom_tag: ?I?E?\177\017openser", len = 0}) at mediaproxy.c:1478 #5 0xb7889147 in __dialog_ended (dlg=0x6, type=2048, _params=0xb7883cbc) at mediaproxy.c:1545 #6 0xb7865378 in run_dlg_callbacks (type=2048, dlg=0xb59e6398, msg=0x0, dir=0, dlg_data=0x0) at dlg_cb.c:252 #7 0xb7876186 in destroy_dlg_table () at dlg_hash.c:118 #8 0xb7861d8e in mod_destroy () at dialog.c:529 #9 0x080b3d41 in destroy_modules () at sr_module.c:381 #10 0x08069b60 in cleanup (show_status=1) at main.c:333 #11 0x0806aaf1 in handle_sigs () at main.c:523 #12 0x0806ecc8 in main (argc=1, argv=0xbf9cecc4) at main.c:865 DEBUG from Kamailio: Oct 22 16:25:34 [7817] DBG:tm:t_relay_to: new transaction fwd'ed Oct 22 16:25:34 [7856] CRITICAL:core:receive_fd: EOF on 15 Oct 22 16:25:34 [7856] DBG:core:handle_ser_child: dead child 8, pid 7817 (shutting down?) Oct 22 16:25:34 [7856] DBG:core:io_watch_del: io_watch_del (0x8175e80, 15, -1, 0x0) fd_no=26 called Oct 22 16:25:34 [7803] INFO:core:handle_sigs: child process 7817 exited by a signal 11 Oct 22 16:25:34 [7803] INFO:core:handle_sigs: core was generated Oct 22 16:25:34 [7803] INFO:core:handle_sigs: terminating due to SIGCHLD Oct 22 16:25:34 [7856] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 144400, used+overhead=169568, free=879008 max used (+overhead)= 169568 dumping free list: hash = 115 fragments no.: 1, unused: 0 bucket size: 920 - 920 (first 920) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 873576) TOTAL: 6 free fragments = 879152 free bytes ----------------------------- Oct 22 16:25:34 [7853] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 152800, used+overhead=178088, free=870488 max used (+overhead)= 178088 dumping free list: hash = 75 fragments no.: 1, unused: 0 bucket size: 600 - 600 (first 600) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 865376) TOTAL: 6 free fragments = 870632 free bytes ----------------------------- Oct 22 16:25:34 [7850] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 152800, used+overhead=178088, free=870488 max used (+overhead)= 178088 dumping free list: hash = 75 fragments no.: 1, unused: 0 bucket size: 600 - 600 (first 600) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 865376) TOTAL: 6 free fragments = 870632 free bytes ----------------------------- Oct 22 16:25:34 [7847] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 152800, used+overhead=178088, free=870488 max used (+overhead)= 178088 dumping free list: hash = 75 fragments no.: 1, unused: 0 bucket size: 600 - 600 (first 600) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 865376) TOTAL: 6 free fragments = 870632 free bytes ----------------------------- Oct 22 16:25:34 [7844] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 152800, used+overhead=178088, free=870488 max used (+overhead)= 178088 dumping free list: hash = 75 fragments no.: 1, unused: 0 bucket size: 600 - 600 (first 600) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 865376) TOTAL: 6 free fragments = 870632 free bytes ----------------------------- Oct 22 16:25:34 [7829] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 102496, used+overhead=127784, free=920792 max used (+overhead)= 127864 dumping free list: hash = 1 fragments no.: 1, unused: 0 bucket size: 8 - 8 (first 8) hash = 10 fragments no.: 1, unused: 0 bucket size: 80 - 80 (first 80) hash = 62 fragments no.: 1, unused: 0 bucket size: 496 - 496 (first 496) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 915696) TOTAL: 8 free fragments = 920936 free bytes ----------------------------- Oct 22 16:25:34 [7826] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 102496, used+overhead=127776, free=920800 max used (+overhead)= 127784 dumping free list: hash = 1 fragments no.: 1, unused: 0 bucket size: 8 - 8 (first 8) hash = 73 fragments no.: 1, unused: 0 bucket size: 584 - 584 (first 584) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 915696) TOTAL: 7 free fragments = 920944 free bytes ----------------------------- Oct 22 16:25:34 [7823] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 102496, used+overhead=127776, free=920800 max used (+overhead)= 127784 dumping free list: hash = 1 fragments no.: 1, unused: 0 bucket size: 8 - 8 (first 8) hash = 73 fragments no.: 1, unused: 0 bucket size: 584 - 584 (first 584) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 915696) TOTAL: 7 free fragments = 920944 free bytes ----------------------------- Oct 22 16:25:34 [7820] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 102496, used+overhead=127768, free=920808 max used (+overhead)= 127768 dumping free list: hash = 75 fragments no.: 1, unused: 0 bucket size: 600 - 600 (first 600) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 915696) TOTAL: 6 free fragments = 920952 free bytes ----------------------------- Oct 22 16:25:34 [7814] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 102528, used+overhead=128304, free=920272 max used (+overhead)= 132536 dumping free list: hash = 1 fragments no.: 7, unused: 0 bucket size: 8 - 8 (first 8) hash = 2 fragments no.: 3, unused: 0 bucket size: 16 - 16 (first 16) hash = 3 fragments no.: 7, unused: 0 bucket size: 24 - 24 (first 24) hash = 4 fragments no.: 25, unused: 0 bucket size: 32 - 32 (first 32) hash = 5 fragments no.: 11, unused: 0 bucket size: 40 - 40 (first 40) hash = 6 fragments no.: 3, unused: 0 bucket size: 48 - 48 (first 48) hash = 7 fragments no.: 1, unused: 0 bucket size: 56 - 56 (first 56) hash = 9 fragments no.: 1, unused: 0 bucket size: 72 - 72 (first 72) hash = 10 fragments no.: 1, unused: 0 bucket size: 80 - 80 (first 80) hash = 15 fragments no.: 1, unused: 0 bucket size: 120 - 120 (first 120) hash = 17 fragments no.: 1, unused: 0 bucket size: 136 - 136 (first 136) hash = 27 fragments no.: 2, unused: 0 bucket size: 216 - 216 (first 216) hash = 40 fragments no.: 1, unused: 0 bucket size: 320 - 320 (first 320) hash = 92 fragments no.: 1, unused: 0 bucket size: 736 - 736 (first 736) hash = 94 fragments no.: 1, unused: 0 bucket size: 752 - 752 (first 752) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 914936) TOTAL: 68 free fragments = 920416 free bytes ----------------------------- Oct 22 16:25:34 [7811] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 102528, used+overhead=128240, free=920336 max used (+overhead)= 132296 dumping free list: hash = 1 fragments no.: 5, unused: 0 bucket size: 8 - 8 (first 8) hash = 2 fragments no.: 4, unused: 0 bucket size: 16 - 16 (first 16) hash = 3 fragments no.: 7, unused: 0 bucket size: 24 - 24 (first 24) hash = 4 fragments no.: 19, unused: 0 bucket size: 32 - 32 (first 32) hash = 5 fragments no.: 12, unused: 0 bucket size: 40 - 40 (first 40) hash = 6 fragments no.: 1, unused: 0 bucket size: 48 - 48 (first 48) hash = 8 fragments no.: 1, unused: 0 bucket size: 64 - 64 (first 64) hash = 9 fragments no.: 1, unused: 0 bucket size: 72 - 72 (first 72) hash = 14 fragments no.: 1, unused: 0 bucket size: 112 - 112 (first 112) hash = 15 fragments no.: 1, unused: 0 bucket size: 120 - 120 (first 120) hash = 16 fragments no.: 2, unused: 0 bucket size: 128 - 128 (first 128) hash = 27 fragments no.: 2, unused: 0 bucket size: 216 - 216 (first 216) hash = 58 fragments no.: 1, unused: 0 bucket size: 464 - 464 (first 464) hash = 92 fragments no.: 1, unused: 0 bucket size: 736 - 736 (first 736) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 915696) TOTAL: 60 free fragments = 920480 free bytes ----------------------------- Oct 22 16:25:34 [7841] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 111616, used+overhead=136744, free=911832 max used (+overhead)= 136744 dumping free list: hash = 118 fragments no.: 1, unused: 0 bucket size: 944 - 944 (first 944) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 907496) TOTAL: 5 free fragments = 911976 free bytes ----------------------------- Oct 22 16:25:34 [7832] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 159496, used+overhead=184608, free=863968 max used (+overhead)= 184608 dumping free list: hash = 129 fragments no.: 1, unused: 0 bucket size: 1032 - 1032 (first 1032) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 858424) TOTAL: 6 free fragments = 864112 free bytes ----------------------------- Oct 22 16:25:34 [7807] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 102528, used+overhead=127808, free=920768 max used (+overhead)= 127808 dumping free list: hash = 70 fragments no.: 1, unused: 0 bucket size: 560 - 560 (first 560) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 915696) TOTAL: 6 free fragments = 920912 free bytes ----------------------------- Oct 22 16:25:34 [7806] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 102528, used+overhead=127808, free=920768 max used (+overhead)= 127808 dumping free list: hash = 70 fragments no.: 1, unused: 0 bucket size: 560 - 560 (first 560) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 915696) TOTAL: 6 free fragments = 920912 free bytes ----------------------------- Oct 22 16:25:34 [7805] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 102528, used+overhead=127808, free=920768 max used (+overhead)= 127808 dumping free list: hash = 70 fragments no.: 1, unused: 0 bucket size: 560 - 560 (first 560) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 915696) TOTAL: 6 free fragments = 920912 free bytes ----------------------------- Oct 22 16:25:34 [7804] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 102744, used+overhead=128088, free=920488 max used (+overhead)= 128088 dumping free list: hash = 13 fragments no.: 1, unused: 0 bucket size: 104 - 104 (first 104) hash = 61 fragments no.: 1, unused: 0 bucket size: 488 - 488 (first 488) hash = 101 fragments no.: 1, unused: 0 bucket size: 808 - 808 (first 808) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 915696) TOTAL: 7 free fragments = 920632 free bytes ----------------------------- Oct 22 16:25:34 [7835] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 159496, used+overhead=184608, free=863968 max used (+overhead)= 184608 dumping free list: hash = 129 fragments no.: 1, unused: 0 bucket size: 1032 - 1032 (first 1032) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 858424) TOTAL: 6 free fragments = 864112 free bytes ----------------------------- Oct 22 16:25:34 [7838] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 159496, used+overhead=184608, free=863968 max used (+overhead)= 184608 dumping free list: hash = 129 fragments no.: 1, unused: 0 bucket size: 1032 - 1032 (first 1032) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 144 fragments no.: 1, unused: 0 bucket size: 1152 - 1152 (first 1152) hash = 147 fragments no.: 1, unused: 0 bucket size: 1176 - 1176 (first 1176) hash = 151 fragments no.: 1, unused: 0 bucket size: 1208 - 1208 (first 1208) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 858424) TOTAL: 6 free fragments = 864112 free bytes ----------------------------- Oct 22 16:25:34 [7808] INFO:core:sig_usr: signal 15 received Memory status (pkg): fm_status (0x81a6e20): heap size= 1048576 used= 102600, used+overhead=128496, free=920080 max used (+overhead)= 132720 dumping free list: hash = 1 fragments no.: 7, unused: 0 bucket size: 8 - 8 (first 8) hash = 2 fragments no.: 5, unused: 0 bucket size: 16 - 16 (first 16) hash = 3 fragments no.: 9, unused: 0 bucket size: 24 - 24 (first 24) hash = 4 fragments no.: 31, unused: 0 bucket size: 32 - 32 (first 32) hash = 5 fragments no.: 15, unused: 0 bucket size: 40 - 40 (first 40) hash = 6 fragments no.: 3, unused: 0 bucket size: 48 - 48 (first 48) hash = 8 fragments no.: 2, unused: 0 bucket size: 64 - 64 (first 64) hash = 9 fragments no.: 1, unused: 0 bucket size: 72 - 72 (first 72) hash = 12 fragments no.: 1, unused: 0 bucket size: 96 - 96 (first 96) hash = 14 fragments no.: 1, unused: 0 bucket size: 112 - 112 (first 112) hash = 15 fragments no.: 1, unused: 0 bucket size: 120 - 120 (first 120) hash = 27 fragments no.: 2, unused: 0 bucket size: 216 - 216 (first 216) hash = 46 fragments no.: 1, unused: 0 bucket size: 368 - 368 (first 368) hash = 115 fragments no.: 1, unused: 0 bucket size: 920 - 920 (first 920) hash = 140 fragments no.: 1, unused: 0 bucket size: 1120 - 1120 (first 1120) hash = 2054 fragments no.: 1, unused: 0 bucket size: 524288 - 1048576 (first 914768) TOTAL: 82 free fragments = 920224 free bytes ----------------------------- Oct 22 16:25:34 [7803] DBG:dialog:destroy_dlg: destroing dialog 0xb5a063a0 Oct 22 16:25:34 [7803] DBG:dialog:run_dlg_callbacks: dialog=0xb5a063a0, type=2048 Any suggestions? With best regards Marian Piater -- Marian Piater LAM plus s.r.o. odd. hlasové komunikace - VoIP 242 413 000 Do práce 605 267 612 Mobilní telefon marian.piater(a)lam.cz LAM plus s.r.o. Mezi vodami 19 143 00 Praha - Modřany P Prosím, uvědomte si svou zodpovědnost za životní prostředí, než vytisknete tento e-mail.

15 years, 6 months

← Newer
1
2
3
4
5
6
7
8
9
...
17
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users October 2008