[SR-Users] preparing kamailio 3.0.3
Hello, I am planning to release minor version 3.0.3 by beginning of next week. Please commit there what you think it needs to be fixed for this release. Thanks, Daniel -- Daniel-Constantin Mierla http://www.asipto.com/ ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] PDT ran out of pkg memory using pdt_list
On 07/20/2010 07:45 PM, JR Richardson wrote: On Tue, Jul 20, 2010 at 12:04 PM, Elena-Ramona Modroiu ram...@asipto.com wrote: On 07/20/2010 05:06 PM, JR Richardson wrote: [..] When I added 180K records in the database, I got the no more pkg mem error again. I increased again: #define PKG_MEM_POOL_SIZE 32*1024*1024 This allowed me to execute pdt_list with 180K records loaded. I increased database record count to 240K and got the no more pkg mem error again. So I don't think it is prudent to just keep increasing PKG_MEM_POOL_SIZE. Is this an architectural limitation with fifo pkg_mem, shouldn't this be a dynamic allocation if it's not within shmem and has no affect on core sip-router function? While the pdt_reload and pdt_list is going on (takes a few seconds to load and list), I don't see any problems with the sip-router executions. I guess I can just use the old fashion database query to look up routes instead of fifo pdt_list. Hi Jr, if you don't use the PKG_MALLOC MM in your system at least the kamailio 1.5 will fallback to the system malloc, which don't have this size restrictions. For 3.x/ sr there is an option to build the MI interface with system malloc as well, it this commit: commit 85f2302e8448ee20edb12bc3b4e2911ca3b111ec Author: Daniel-Constantin Mierlamico...@gmail.com Date: Mon Jun 29 12:34:08 2009 +0200 lib/kmi: option to build it with system malloc - MI lib can be built independently of core with system malloc for pkg memory (see Makefile) this is the option added to overcome the MI design limitations - while most of dumped structures are in shared memory, MI builds the output in PKG memory, resulting in insufficient space since shm is much bigger than pkg - also this sometime ended as well in lot of mem fragmentation for mi process in the past. It needs to edit lib/kmi/Makefile and enable system malloc, recompile and reinstall. Regards, Ramona Hi Ramona, Thanks for your suggestions. I started over with default mem parameters in config.h and compiled with: ## uncomment next line for using system malloc with MI DEFS+= -DMI_SYSTEM_MALLOC I loaded the pdt database table with 360K records and also started kamailio with '-m 512' but the table still has a max record limitation, will not load propperly and I get these errors: 0(22456) ERROR: pdt [pdtree.c:283]: bad parameters 0(22456) INFO: pdt [pdt.c:490]: no prefix found in [2000171212] Of course wihout a propper table load, pdt_list does not produce any results (but i don;t get the pkg_mem error any more). sip-router2:~# kamctl fifo get_statistics all shmem:total_size = 536870912 shmem:used_size = 1229472 shmem:real_used_size = 1247560 shmem:max_used_size = 1255376 shmem:free_size = 535623352 There seems to still be a bottleneck with shmem, even through I have 512M+ available, I only seem to be using ~1.2M. Is there an internal shmem hard limit that can be adjusted? Hi JR, There is no limit hard-coded, I just loaded 1mio records in pdt (sdomain=*, prefix=1mio..2mio, domain=test.org) and statistics show: shmem:total_size = 268435456 shmem:used_size = 26594256 shmem:real_used_size = 80148548 shmem:max_used_size = 80148548 shmem:free_size = 188286908 So the records are reflected in shared memory. What is the output of kamailio -V? What are the parameters for pdt? Regards, Ramona sip-router2:~# kamailio -V version: kamailio 3.0.2 (i386/linux) a6141a flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. @(#) $Id$ main.c compiled on 09:25:15 Jul 20 2010 with gcc 4.3.2 sip-router2:~# # - pdt params - modparam(pdt, db_url, mysql://openserro:opense...@localhost/openser) modparam(pdt, char_list, 0123456789) modparam(pdt, check_domain, 0) modparam(pdt, fetch_rows, 5000) Here is an interesting observation: When I have 300K+ records in the pdt table, it seems like it will not load properly and the shmem is very low, as expected without a large memory pool needed to hold the records. Statistics show: shmem:total_size = 33554432 shmem:used_size = 1229472 shmem:real_used_size = 1247512 shmem:max_used_size = 1247512 shmem:free_size = 32306920 shmem:fragments = 11 When I decrease the table recrods to 240K, the complete table loads ok and shmem reflect properly: shmem:total_size = 33554432 shmem:used_size = 6349784 shmem:real_used_size = 8501144 shmem:max_used_size = 8501144 shmem:free_size = 25053288 shmem:fragments = 1 So maybe I'm not having an issue with shmem at all but a loading problem with the pdt tabe after a certain record count. I changed the modparam(pdt,
Re: [SR-Users] PDT ran out of pkg memory using pdt_list
On Tuesday 20 July 2010, JR Richardson wrote: [..] Here is an interesting observation: When I have 300K+ records in the pdt table, it seems like it will not load properly and the shmem is very low, as expected without a large memory pool needed to hold the records. Statistics show: shmem:total_size = 33554432 [..] When I decrease the table recrods to 240K, the complete table loads ok and shmem reflect properly: shmem:total_size = 33554432 Hi JR, it seems you've a problem with your SHM pool size configuration. 33.554.432 ~ 34MB It should normally output the proper size, like this: test-proxy:~# grep MEM /etc/default/kamailio MEMORY=1024 test-proxy:~# kamctl fifo get_statistics all | grep total_size shmem:total_size = 1073741824 1073.741.824 = 1024 MB Cheers, Henning ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] freezing for major release 3.1
Hi, for me, it's fine. I have some changes, which i will commit to the trunk in the next few days: Nathelper-Improvements: - allow the configuration of a timeout socket which will be sent to the RTP-Proxy (i have a patch for the rtpproxy in order to terminate calls via XML-RPC) - if time allows and the change is finished by then: Retrieve RTP-Statistics from the RTP-Proxy. Carsten 2010/7/21 Daniel-Constantin Mierla mico...@gmail.com Hello, as discussed during our devel meeting, next major release 3.1 is scheduled for this autumn. Therefore the freezing should happen soon. Would be 2 weeks from now enough for everyone to push planned new features to repo? Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com/ ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Carsten Bock Schomburgstr. 80 22767 Hamburg Germany Mobile +49 179 2021244 Home +49 40 34927217 Fax +49 40 34927218 mailto:cars...@bock.info ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [sr-dev] freezing for major release 3.1
2010/7/21 Carsten Bock li...@bock.info: - allow the configuration of a timeout socket which will be sent to the RTP-Proxy (i have a patch for the rtpproxy in order to terminate calls via XML-RPC) Couuld you please ellaborate this a bit more? it sound really interesting :) -- Iñaki Baz Castillo i...@aliax.net ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [sr-dev] preparing kamailio 3.0.3
On Jul 21, 2010 at 09:58, Daniel-Constantin Mierla mico...@gmail.com wrote: Hello, I am planning to release minor version 3.0.3 by beginning of next week. Please commit there what you think it needs to be fixed for this release. I'll have to backport some tcp fixes (which are now only in adnrei/tcp_tls_changes), so for my point of view this minor release should happen after the 3.1 freeze (so that we have some time to do backports). Andrei ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [sr-dev] preparing kamailio 3.0.3
On 7/21/10 1:04 PM, Andrei Pelinescu-Onciul wrote: On Jul 21, 2010 at 09:58, Daniel-Constantin Mierlamico...@gmail.com wrote: Hello, I am planning to release minor version 3.0.3 by beginning of next week. Please commit there what you think it needs to be fixed for this release. I'll have to backport some tcp fixes (which are now only in adnrei/tcp_tls_changes), so for my point of view this minor release should happen after the 3.1 freeze (so that we have some time to do backports). I was thinking for 3.0.3 mainly to incorporate in an official release the fixes for xmlrpc module. Probably the fixes coming from 3.1 branches will be done in about 1 month and we can release then 3.0.4. Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com/ ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [sr-dev] freezing for major release 3.1
Hi, it is rather simple: The command specification (http://rtpproxy.org/wiki/RTPproxy/Protocol) states the following: Update session, creating a new one if it doesn't exist. U[args] callid addr port from_tag [to_tag [notify_socket [notify_args]]] The NATHelper Module currently does not send the optional notify socket to the RTPProxy. The enhancement makes this notify_socket configurable and will send it to the RTP-Proxy, if set. On the other end, i have modified the RTP-Proxy to check, if it is an HTTP-Socket (XML-RPC) or an Unix-Socket. If it is a Unix-Socket, it works as it does now. If the Socket starts with http://;, it will query the Proxy by executing dlg_list with the Call-ID and the From-Tag. If the dialog is found, it will call dlg_end_dlg with the according parameters... Rather simple - that's it. Currently i have this running using some wrappers in Python, which is rather quick and dirty. Kind regards, Carsten 2010/7/21 Iñaki Baz Castillo i...@aliax.net 2010/7/21 Carsten Bock li...@bock.info: - allow the configuration of a timeout socket which will be sent to the RTP-Proxy (i have a patch for the rtpproxy in order to terminate calls via XML-RPC) Couuld you please ellaborate this a bit more? it sound really interesting :) -- Iñaki Baz Castillo i...@aliax.net -- Carsten Bock Schomburgstr. 80 22767 Hamburg Germany Mobile +49 179 2021244 Home +49 40 34927217 Fax +49 40 34927218 mailto:cars...@bock.info ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [sr-dev] freezing for major release 3.1
2010/7/21 Carsten Bock li...@bock.info: Hi, it is rather simple: The command specification (http://rtpproxy.org/wiki/RTPproxy/Protocol) states the following: Update session, creating a new one if it doesn't exist. U[args] callid addr port from_tag [to_tag [notify_socket [notify_args]]] The NATHelper Module currently does not send the optional notify socket to the RTPProxy. The enhancement makes this notify_socket configurable and will send it to the RTP-Proxy, if set. On the other end, i have modified the RTP-Proxy to check, if it is an HTTP-Socket (XML-RPC) or an Unix-Socket. If it is a Unix-Socket, it works as it does now. If the Socket starts with http://;, it will query the Proxy by executing dlg_list with the Call-ID and the From-Tag. If the dialog is found, it will call dlg_end_dlg with the according parameters... It's great :) However take into account that dlg_end_dlg just works for confirmed dialogs (state 4). There are new fixes about it by Timo so it doesn't leak when running dlg_end_dlg for an in-progress dialog. Also I think that a new commit from Time makes dlg_end_dlg just to work in case the dialog state is 4 so nothing would be required from the Rtpproxy. Terminating in-progress dialog is still not implemented (but planned AFAIK). Regards. -- Iñaki Baz Castillo i...@aliax.net ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [sr-dev] freezing for major release 3.1
Iñaki Baz Castillo wrote: 2010/7/21 Carsten Bock li...@bock.info: Hi, it is rather simple: The command specification (http://rtpproxy.org/wiki/RTPproxy/Protocol) states the following: Update session, creating a new one if it doesn't exist. U[args] callid addr port from_tag [to_tag [notify_socket [notify_args]]] The NATHelper Module currently does not send the optional notify socket to the RTPProxy. The enhancement makes this notify_socket configurable and will send it to the RTP-Proxy, if set. On the other end, i have modified the RTP-Proxy to check, if it is an HTTP-Socket (XML-RPC) or an Unix-Socket. If it is a Unix-Socket, it works as it does now. If the Socket starts with http://;, it will query the Proxy by executing dlg_list with the Call-ID and the From-Tag. If the dialog is found, it will call dlg_end_dlg with the according parameters... It's great :) However take into account that dlg_end_dlg just works for confirmed dialogs (state 4). There are new fixes about it by Timo so it doesn't leak when running dlg_end_dlg for an in-progress dialog. Also I think that a new commit from Time makes dlg_end_dlg just to work in case the dialog state is 4 so nothing would be required from the Rtpproxy. Terminating in-progress dialog is still not implemented (but planned AFAIK). All correct; little addendum: Proxy-initiated dialog termination works both in state 3 (2xx response received but ACK request from UAC yet missing) and 4 (2xx response and ACK request received) because the dialog module stores caller data already in state 3. I neglected that detail in the commit message as both states are denoted committed in Kamailio but it doesn't make much of a difference. Cheers, --Timo ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [sr-dev] freezing for major release 3.1
2010/7/21 Timo Reimann timo.reim...@1und1.de: All correct; little addendum: Proxy-initiated dialog termination works both in state 3 (2xx response received but ACK request from UAC yet missing) and 4 (2xx response and ACK request received) because the dialog module stores caller data already in state 3. Sure, from the point of view of a SIP dialog, it's established after the 200 OK, regardless the ACK arrives or not as the ACK doesn't provide new info to the SIP dialog (perhaps it does for the media negociation, but just it). Regards. -- Iñaki Baz Castillo i...@aliax.net ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [sr-dev] freezing for major release 3.1
Timo Reimann wrote: Iñaki Baz Castillo wrote: 2010/7/21 Carsten Bock li...@bock.info: Hi, it is rather simple: The command specification (http://rtpproxy.org/wiki/RTPproxy/Protocol) states the following: Update session, creating a new one if it doesn't exist. U[args] callid addr port from_tag [to_tag [notify_socket [notify_args]]] The NATHelper Module currently does not send the optional notify socket to the RTPProxy. The enhancement makes this notify_socket configurable and will send it to the RTP-Proxy, if set. On the other end, i have modified the RTP-Proxy to check, if it is an HTTP-Socket (XML-RPC) or an Unix-Socket. If it is a Unix-Socket, it works as it does now. If the Socket starts with http://;, it will query the Proxy by executing dlg_list with the Call-ID and the From-Tag. If the dialog is found, it will call dlg_end_dlg with the according parameters... It's great :) However take into account that dlg_end_dlg just works for confirmed dialogs (state 4). There are new fixes about it by Timo so it doesn't leak when running dlg_end_dlg for an in-progress dialog. Also I think that a new commit from Time makes dlg_end_dlg just to work in case the dialog state is 4 so nothing would be required from the Rtpproxy. Terminating in-progress dialog is still not implemented (but planned AFAIK). All correct; little addendum: Proxy-initiated dialog termination works both in state 3 (2xx response received but ACK request from UAC yet missing) and 4 (2xx response and ACK request received) because the dialog module stores caller data already in state 3. I neglected that detail in the commit message as both states are denoted committed in Kamailio but it doesn't make much of a difference. s/committed/confirmed/ --Timo ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [sr-dev] freezing for major release 3.1
2010/7/21 Timo Reimann timo.reim...@1und1.de: All correct; little addendum: Proxy-initiated dialog termination works both in state 3 (2xx response received but ACK request from UAC yet missing) and 4 (2xx response and ACK request received) because the dialog module stores caller data already in state 3. I neglected that detail in the commit message as both states are denoted committed in Kamailio but it doesn't make much of a difference. s/committed/confirmed/ commited would be a cool new state for SIP dialogs, and also merged XD -- Iñaki Baz Castillo i...@aliax.net ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [sr-dev] freezing for major release 3.1
Iñaki Baz Castillo wrote: 2010/7/21 Timo Reimann timo.reim...@1und1.de: All correct; little addendum: Proxy-initiated dialog termination works both in state 3 (2xx response received but ACK request from UAC yet missing) and 4 (2xx response and ACK request received) because the dialog module stores caller data already in state 3. I neglected that detail in the commit message as both states are denoted committed in Kamailio but it doesn't make much of a difference. s/committed/confirmed/ commited would be a cool new state for SIP dialogs, and also merged XD Oh how I wish I could revert some of the dialogs I established in the past. ;) Cheers, --Timo ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] PDT ran out of pkg memory using pdt_list
sip-router2:~# kamailio -V version: kamailio 3.0.2 (i386/linux) a6141a flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. @(#) $Id$ main.c compiled on 09:25:15 Jul 20 2010 with gcc 4.3.2 sip-router2:~# # - pdt params - modparam(pdt, db_url, mysql://openserro:opense...@localhost/openser) modparam(pdt, char_list, 0123456789) modparam(pdt, check_domain, 0) modparam(pdt, fetch_rows, 5000) Here is an interesting observation: When I have 300K+ records in the pdt table, it seems like it will not load properly and the shmem is very low, as expected without a large memory pool needed to hold the records. Statistics show: shmem:total_size = 33554432 shmem:used_size = 1229472 shmem:real_used_size = 1247512 shmem:max_used_size = 1247512 shmem:free_size = 32306920 shmem:fragments = 11 When I decrease the table recrods to 240K, the complete table loads ok and shmem reflect properly: shmem:total_size = 33554432 shmem:used_size = 6349784 shmem:real_used_size = 8501144 shmem:max_used_size = 8501144 shmem:free_size = 25053288 shmem:fragments = 1 So maybe I'm not having an issue with shmem at all but a loading problem with the pdt tabe after a certain record count. I changed the modparam(pdt, fetch_rows, 5000) to see if that would help. When the table loads properly is is quicker than with the default 1000 rows, but that is the only difference I experience. When the pdt table has more than 300K records, it just does not load into memory. Could there be a pdt module timeout that is being met when loading? For instance, if it takes more than N seconds to load, consider a fault and not load? sip-router2:/etc/kamailio# mysql -V mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2 sip-router2:/etc/kamailio# try to play with mysql module timeout parameter in case the records are not loaded fast enough: http://kamailio.org/docs/modules/stable/modules/db_mysql.html#id2928400 Regards, Ramona Ok, I figured out that sr was taking about 9-10 seconds to load 300K records so I increased: # - db_mysql params - modparam(db_mysql, timeout_interval, 20) And found that the table would load, so I started increasing the record count by 60K, then the fault condition occurred again at around 400K records, then went away by itself. I got all the way to 760K records without a problem then hit another wall at 800K records. I think there is something flaky going on, I can not reproduce it reliable, sometimes the table loads just fine and other times it does not load at all. I started monitoring mysqld. When I restart sr or issue pdt_reload and msqld has a load, the table seems to load fine, regardless of the table size or timeout_interval setting. When the problem is occurring, myslqd has zero usage. When the issue was occurring, I restarted the mysql process and the table loaded into sr. I'm now suspecting I have a buggy mysqld so I'm going to try to update that and see if I can reproduce the problem. So for now I can't isolate the issue, but I'm still working on it. I do see a difference with the timeout_interval during sr restarts, the longer the time the better it does. Also there is a time difference when loading the table, sometimes it takes 30 seconds, sometimes 90 seconds. I think maybe there is a combination of issues going on here. I need to rebuild a fresh install and test a bit more methodically to find a root cause. Also I want to grab a newer version of mysql-server. I'll update with my findings. Thanks. JR -- JR Richardson Engineering for the Masses ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] PDT ran out of pkg memory using pdt_list [SOLVED}
try to play with mysql module timeout parameter in case the records are not loaded fast enough: http://kamailio.org/docs/modules/stable/modules/db_mysql.html#id2928400 Regards, Ramona Ok, I figured out that sr was taking about 9-10 seconds to load 300K records so I increased: # - db_mysql params - modparam(db_mysql, timeout_interval, 20) And found that the table would load, so I started increasing the record count by 60K, then the fault condition occurred again at around 400K records, then went away by itself. I got all the way to 760K records without a problem then hit another wall at 800K records. I think there is something flaky going on, I can not reproduce it reliable, sometimes the table loads just fine and other times it does not load at all. I started monitoring mysqld. When I restart sr or issue pdt_reload and msqld has a load, the table seems to load fine, regardless of the table size or timeout_interval setting. When the problem is occurring, myslqd has zero usage. When the issue was occurring, I restarted the mysql process and the table loaded into sr. I'm now suspecting I have a buggy mysqld so I'm going to try to update that and see if I can reproduce the problem. So for now I can't isolate the issue, but I'm still working on it. I do see a difference with the timeout_interval during sr restarts, the longer the time the better it does. Also there is a time difference when loading the table, sometimes it takes 30 seconds, sometimes 90 seconds. I think maybe there is a combination of issues going on here. I need to rebuild a fresh install and test a bit more methodically to find a root cause. Also I want to grab a newer version of mysql-server. I'll update with my findings. # - db_mysql params - modparam(db_mysql, timeout_interval, 20) Time interval (in seconds) after that an connection attempt, read or write request is aborted. The value counts three times, as several retries are done from the driver before it gives up. The values counts 3 times this was my issue, as I was adjusting the value between 10, 20, 30, 60, 120, and having inconsistent table load times from mysqld. After a reboot, mysql started performing better, more consistent with load times. My table with 800K records was taking between 30-38 seconds to load. With timeout_interval set to 10 (30 second timeout), I was right on the edge of the table loading or not loading, sometimes it would and other times it would not. So giving a bit of cushion on the timeout_interval seems to resolve the problem. Adjusting this value I could consistently reproduce the problem. So for large database tables, this timeout value should be set to about 1 second per 20K records. As far as the other issue goes with using pdt_list and pkg memory size, compileing mi using system mem solved this issue as well. Also pdt_list has the option to search for prefixes which works in my case without the need to increase pkg memory or system memory: sip-router2:~# kamctl fifo pdt_list . 9 PDT:: SDOMAIN=* PREFIX=90 DOMAIN=2 PDT:: SDOMAIN=* PREFIX=91 DOMAIN=2 PDT:: SDOMAIN=* PREFIX=92 DOMAIN=2 PDT:: SDOMAIN=* PREFIX=93 DOMAIN=2 PDT:: SDOMAIN=* PREFIX=94 DOMAIN=2 PDT:: SDOMAIN=* PREFIX=95 DOMAIN=2 PDT:: SDOMAIN=* PREFIX=96 DOMAIN=2 PDT:: SDOMAIN=* PREFIX=97 DOMAIN=2 PDT:: SDOMAIN=* PREFIX=98 DOMAIN=2 PDT:: SDOMAIN=* PREFIX=99 DOMAIN=2 Using the list prefix search option will pipe out about 10,000 records, but errors out with no more pkg mem past that. Thanks for all your input on this thread to help me isolate the issue. JR -- JR Richardson Engineering for the Masses ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Help needed for OpenSer with Radius
Dear All, I am very new to OpenSer. I want to use latest version of OpenSer with Radius. I need the documentation/tutorial on how to do this. Googling, Ionly found for the old version. Please help me. Regards, Pratik ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
