Re: [SR-Users] pdb module timeouts
On 02/18/2011 12:53 PM, Thomas Baumann wrote:
Hello Marius,
the main problem I had was caused with wrong debug-level in the
script. Debug level 3 is not a good choice for loadtesting, my
mistake.
After changing to debug level 2, it looks a lot better. I did more
testing with the right settings, and yes the change in pdb.c had some
influence on the timeouts.
Hello Thomas,
Good to hear that, I couldn't replicate the problems you were having
with pdb. Are you sure you have asynchronous syslogd configured for
kamailio? If not performance is a killer
BTW, my patch doesn't really do anything afaik (i am not 100% sure on
linux but my tests seemed to confirm it).
Cheers,
Marius
With the patch I did not see any timeouts after running a loadtest
overnight (200.000 calls executed with max. 12 cps for one application
server). But with the old code where are still few timeouts:
Completed Calls:9732 Failed Calls:13 Failure Rate:0.133 perc. Loop Count:2336
Have a nice weekend,
Thomas
On Wed, Feb 16, 2011 at 8:20 PM, bt047265 wrote:
Hi Marius, Hi Henning,
sorry for the wrong information, the patch did not work for me. I did
not see any timeouts if only one server was used. If more than 2
Servers are used, where are failed calls.
regards,
Thomas
One server old pdb.c:
modparam("pdb", "server", "10.12.18.41:10001")
Feb 16 19:28:03 m-lab-prx-as-2 /openser/sbin/kamailio[29622]: INFO:
pdb [pdb.c:291]: got an answer in 0.99 ms
Feb 16 19:28:03 m-lab-prx-as-2 /openser/sbin/kamailio[29619]: INFO:
pdb [pdb.c:291]: got an answer in 36.197000 ms
Feb 16 19:28:03 m-lab-prx-as-2 /openser/sbin/kamailio[29619]: INFO:
pdb [pdb.c:291]: got an answer in 0.151000 ms
two servers old pdb.c:
modparam("pdb", "server", "10.12.18.41:10001,10.12.19.51:10001")
Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29688]: INFO:
pdb [pdb.c:291]: got an answer in 0.179000 ms
Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29693]: INFO:
pdb [pdb.c:291]: got an answer in 0.248000 ms
Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29692]: WARNING:
pdb [pdb.c:260]: exceeded timeout while waiting for response.
Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29688]: INFO:
pdb [pdb.c:291]: got an answer in 0.489000 ms
Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29692]: INFO:
pdb [pdb.c:291]: got an answer in 0.596000 ms
One server new pdb.c:
modparam("pdb", "server", "10.12.18.41:10001")
Feb 16 19:55:31 m-lab-prx-as-2 /openser/sbin/kamailio[1079]: INFO: pdb
[pdb.c:291]: got an answer in 48.584000 ms
Feb 16 19:55:31 m-lab-prx-as-2 /openser/sbin/kamailio[1084]: INFO: pdb
[pdb.c:291]: got an answer in 0.29 ms
Feb 16 19:55:31 m-lab-prx-as-2 /openser/sbin/kamailio[1079]: INFO: pdb
[pdb.c:291]: got an answer in 0.19 ms
Feb 16 19:55:31 m-lab-prx-as-2 /openser/sbin/kamailio[1079]: INFO: pdb
[pdb.c:291]: got an answer in 0.241000 ms
two servers old pdb.c:
modparam("pdb", "server", "10.12.18.41:10001,10.12.19.51:10001")
Feb 16 20:08:36 m-lab-prx-as-1 /openser/sbin/kamailio[17348]: INFO:
pdb [pdb.c:291]: got an answer in 0.314000 ms
Feb 16 20:08:36 m-lab-prx-as-1 /openser/sbin/kamailio[17348]: INFO:
pdb [pdb.c:291]: got an answer in 0.202000 ms
Feb 16 20:08:36 m-lab-prx-as-1 /openser/sbin/kamailio[17349]: WARNING:
pdb [pdb.c:260]: exceeded timeout while waiting for response.
- Show quoted text -
On Wed, Feb 16, 2011 at 4:59 PM, marius zbihlei wrote:
On 02/16/2011 04:47 PM, Thomas Baumann wrote:
Hello Marius,
thanks a lot for submitting the patch. It works like a charm now. But to
be honest I had troubles to find this patch, I just checked the daily
tarball [http://sip-router.org/tarballs/sr/] and found this change.
How I can get patch e914f97b4 in a better way ?
regards,
Hello
You can find here a tutorial on installing kamailio from GIT.
http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-3.1.x-from-git
Glad the patch worked. I really doubted the usefulness of the patch as
revents member should be cleared by the poll() method before setting the
POLLIN event for a fd. I will have to test it with a small test case on my
machine before I commit this to master branch(anyway no wrong can come to
it, the change has no impact on performance and stability of the pdb module)
Cheers
Marius
Thomas
Hello
I have made a patch to 3.1(e914f97b4) . The poll() event list was not
cleared when a response was received so when 2 servers responded one
after the other it might block in an incorrect recv(). Can you please
test with this?
Marius
___
Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die
Toolbar eingebaut! http://produkte.web.de/go/toolbar
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://list
Re: [SR-Users] pdb module timeouts
Hello Marius,
the main problem I had was caused with wrong debug-level in the
script. Debug level 3 is not a good choice for loadtesting, my
mistake.
After changing to debug level 2, it looks a lot better. I did more
testing with the right settings, and yes the change in pdb.c had some
influence on the timeouts.
With the patch I did not see any timeouts after running a loadtest
overnight (200.000 calls executed with max. 12 cps for one application
server). But with the old code where are still few timeouts:
Completed Calls:9732 Failed Calls:13 Failure Rate:0.133 perc. Loop Count:2336
Have a nice weekend,
Thomas
On Wed, Feb 16, 2011 at 8:20 PM, bt047265 wrote:
> Hi Marius, Hi Henning,
>
> sorry for the wrong information, the patch did not work for me. I did
> not see any timeouts if only one server was used. If more than 2
> Servers are used, where are failed calls.
>
> regards,
>
> Thomas
>
>
> One server old pdb.c:
>
> modparam("pdb", "server", "10.12.18.41:10001")
>
> Feb 16 19:28:03 m-lab-prx-as-2 /openser/sbin/kamailio[29622]: INFO:
> pdb [pdb.c:291]: got an answer in 0.99 ms
> Feb 16 19:28:03 m-lab-prx-as-2 /openser/sbin/kamailio[29619]: INFO:
> pdb [pdb.c:291]: got an answer in 36.197000 ms
> Feb 16 19:28:03 m-lab-prx-as-2 /openser/sbin/kamailio[29619]: INFO:
> pdb [pdb.c:291]: got an answer in 0.151000 ms
>
> two servers old pdb.c:
>
> modparam("pdb", "server", "10.12.18.41:10001,10.12.19.51:10001")
>
> Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29688]: INFO:
> pdb [pdb.c:291]: got an answer in 0.179000 ms
> Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29693]: INFO:
> pdb [pdb.c:291]: got an answer in 0.248000 ms
> Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29692]: WARNING:
> pdb [pdb.c:260]: exceeded timeout while waiting for response.
> Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29688]: INFO:
> pdb [pdb.c:291]: got an answer in 0.489000 ms
> Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29692]: INFO:
> pdb [pdb.c:291]: got an answer in 0.596000 ms
>
>
> One server new pdb.c:
>
> modparam("pdb", "server", "10.12.18.41:10001")
>
> Feb 16 19:55:31 m-lab-prx-as-2 /openser/sbin/kamailio[1079]: INFO: pdb
> [pdb.c:291]: got an answer in 48.584000 ms
> Feb 16 19:55:31 m-lab-prx-as-2 /openser/sbin/kamailio[1084]: INFO: pdb
> [pdb.c:291]: got an answer in 0.29 ms
> Feb 16 19:55:31 m-lab-prx-as-2 /openser/sbin/kamailio[1079]: INFO: pdb
> [pdb.c:291]: got an answer in 0.19 ms
> Feb 16 19:55:31 m-lab-prx-as-2 /openser/sbin/kamailio[1079]: INFO: pdb
> [pdb.c:291]: got an answer in 0.241000 ms
>
> two servers old pdb.c:
>
> modparam("pdb", "server", "10.12.18.41:10001,10.12.19.51:10001")
>
> Feb 16 20:08:36 m-lab-prx-as-1 /openser/sbin/kamailio[17348]: INFO:
> pdb [pdb.c:291]: got an answer in 0.314000 ms
> Feb 16 20:08:36 m-lab-prx-as-1 /openser/sbin/kamailio[17348]: INFO:
> pdb [pdb.c:291]: got an answer in 0.202000 ms
> Feb 16 20:08:36 m-lab-prx-as-1 /openser/sbin/kamailio[17349]: WARNING:
> pdb [pdb.c:260]: exceeded timeout while waiting for response.
> - Show quoted text -
>
> On Wed, Feb 16, 2011 at 4:59 PM, marius zbihlei
> wrote:
>> On 02/16/2011 04:47 PM, Thomas Baumann wrote:
>>>
>>> Hello Marius,
>>>
>>> thanks a lot for submitting the patch. It works like a charm now. But to
>>> be honest I had troubles to find this patch, I just checked the daily
>>> tarball [http://sip-router.org/tarballs/sr/] and found this change.
>>> How I can get patch e914f97b4 in a better way ?
>>>
>>> regards,
>>>
>>
>> Hello
>>
>> You can find here a tutorial on installing kamailio from GIT.
>> http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-3.1.x-from-git
>>
>> Glad the patch worked. I really doubted the usefulness of the patch as
>> revents member should be cleared by the poll() method before setting the
>> POLLIN event for a fd. I will have to test it with a small test case on my
>> machine before I commit this to master branch(anyway no wrong can come to
>> it, the change has no impact on performance and stability of the pdb module)
>>
>> Cheers
>> Marius
>>>
>>> Thomas
>>>
>>>
Hello
>>>
>>>
I have made a patch to 3.1(e914f97b4) . The poll() event list was not
cleared when a response was received so when 2 servers responded one
after the other it might block in an incorrect recv(). Can you please
test with this?
>>>
>>>
Marius
>>>
>>> ___
>>> Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die
>>> Toolbar eingebaut! http://produkte.web.de/go/toolbar
>>>
>>> ___
>>> 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
>>>
>>
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
Re: [SR-Users] pdb module timeouts
Hi Marius, Hi Henning,
sorry for the wrong information, the patch did not work for me. I did
not see any timeouts if only one server was used. If more than 2
Servers are used, where are failed calls.
regards,
Thomas
One server old pdb.c:
modparam("pdb", "server", "10.12.18.41:10001")
Feb 16 19:28:03 m-lab-prx-as-2 /openser/sbin/kamailio[29622]: INFO:
pdb [pdb.c:291]: got an answer in 0.99 ms
Feb 16 19:28:03 m-lab-prx-as-2 /openser/sbin/kamailio[29619]: INFO:
pdb [pdb.c:291]: got an answer in 36.197000 ms
Feb 16 19:28:03 m-lab-prx-as-2 /openser/sbin/kamailio[29619]: INFO:
pdb [pdb.c:291]: got an answer in 0.151000 ms
two servers old pdb.c:
modparam("pdb", "server", "10.12.18.41:10001,10.12.19.51:10001")
Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29688]: INFO:
pdb [pdb.c:291]: got an answer in 0.179000 ms
Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29693]: INFO:
pdb [pdb.c:291]: got an answer in 0.248000 ms
Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29692]: WARNING:
pdb [pdb.c:260]: exceeded timeout while waiting for response.
Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29688]: INFO:
pdb [pdb.c:291]: got an answer in 0.489000 ms
Feb 16 19:35:13 m-lab-prx-as-2 /openser/sbin/kamailio[29692]: INFO:
pdb [pdb.c:291]: got an answer in 0.596000 ms
One server new pdb.c:
modparam("pdb", "server", "10.12.18.41:10001")
Feb 16 19:55:31 m-lab-prx-as-2 /openser/sbin/kamailio[1079]: INFO: pdb
[pdb.c:291]: got an answer in 48.584000 ms
Feb 16 19:55:31 m-lab-prx-as-2 /openser/sbin/kamailio[1084]: INFO: pdb
[pdb.c:291]: got an answer in 0.29 ms
Feb 16 19:55:31 m-lab-prx-as-2 /openser/sbin/kamailio[1079]: INFO: pdb
[pdb.c:291]: got an answer in 0.19 ms
Feb 16 19:55:31 m-lab-prx-as-2 /openser/sbin/kamailio[1079]: INFO: pdb
[pdb.c:291]: got an answer in 0.241000 ms
two servers old pdb.c:
modparam("pdb", "server", "10.12.18.41:10001,10.12.19.51:10001")
Feb 16 20:08:36 m-lab-prx-as-1 /openser/sbin/kamailio[17348]: INFO:
pdb [pdb.c:291]: got an answer in 0.314000 ms
Feb 16 20:08:36 m-lab-prx-as-1 /openser/sbin/kamailio[17348]: INFO:
pdb [pdb.c:291]: got an answer in 0.202000 ms
Feb 16 20:08:36 m-lab-prx-as-1 /openser/sbin/kamailio[17349]: WARNING:
pdb [pdb.c:260]: exceeded timeout while waiting for response.
- Show quoted text -
On Wed, Feb 16, 2011 at 4:59 PM, marius zbihlei wrote:
> On 02/16/2011 04:47 PM, Thomas Baumann wrote:
>>
>> Hello Marius,
>>
>> thanks a lot for submitting the patch. It works like a charm now. But to
>> be honest I had troubles to find this patch, I just checked the daily
>> tarball [http://sip-router.org/tarballs/sr/] and found this change.
>> How I can get patch e914f97b4 in a better way ?
>>
>> regards,
>>
>
> Hello
>
> You can find here a tutorial on installing kamailio from GIT.
> http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-3.1.x-from-git
>
> Glad the patch worked. I really doubted the usefulness of the patch as
> revents member should be cleared by the poll() method before setting the
> POLLIN event for a fd. I will have to test it with a small test case on my
> machine before I commit this to master branch(anyway no wrong can come to
> it, the change has no impact on performance and stability of the pdb module)
>
> Cheers
> Marius
>>
>> Thomas
>>
>>
>>>
>>> Hello
>>>
>>
>>
>>>
>>> I have made a patch to 3.1(e914f97b4) . The poll() event list was not
>>> cleared when a response was received so when 2 servers responded one
>>> after the other it might block in an incorrect recv(). Can you please
>>> test with this?
>>>
>>
>>
>>>
>>> Marius
>>>
>>
>> ___
>> Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die
>> Toolbar eingebaut! http://produkte.web.de/go/toolbar
>>
>> ___
>> 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
>>
>
>
> ___
> 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
>
___
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] pdb module timeouts
On Wednesday 16 February 2011, Thomas Baumann wrote: > Hello Marius, > > thanks a lot for submitting the patch. It works like a charm now. But to be > honest I had troubles to find this patch, I just checked the daily tarball > http://sip-router.org/tarballs/sr/ and found this change. How I can get > patch e914f97b4 in a better way ? Hi Thomas, you can find it in a better format also on the web interface of the project: http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=shortlog;h=refs/heads/3.1 (this is 3.1 branch) 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] pdb module timeouts
On 02/16/2011 04:47 PM, Thomas Baumann wrote: Hello Marius, thanks a lot for submitting the patch. It works like a charm now. But to be honest I had troubles to find this patch, I just checked the daily tarball [http://sip-router.org/tarballs/sr/] and found this change. How I can get patch e914f97b4 in a better way ? regards, Hello You can find here a tutorial on installing kamailio from GIT. http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-3.1.x-from-git Glad the patch worked. I really doubted the usefulness of the patch as revents member should be cleared by the poll() method before setting the POLLIN event for a fd. I will have to test it with a small test case on my machine before I commit this to master branch(anyway no wrong can come to it, the change has no impact on performance and stability of the pdb module) Cheers Marius Thomas Hello I have made a patch to 3.1(e914f97b4) . The poll() event list was not cleared when a response was received so when 2 servers responded one after the other it might block in an incorrect recv(). Can you please test with this? Marius ___ Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://produkte.web.de/go/toolbar ___ 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 ___ 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] pdb module timeouts
Hello Marius, thanks a lot for submitting the patch. It works like a charm now. But to be honest I had troubles to find this patch, I just checked the daily tarball [http://sip-router.org/tarballs/sr/] and found this change. How I can get patch e914f97b4 in a better way ? regards, Thomas >Hello >I have made a patch to 3.1(e914f97b4) . The poll() event list was not >cleared when a response was received so when 2 servers responded one >after the other it might block in an incorrect recv(). Can you please >test with this? >Marius ___ Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://produkte.web.de/go/toolbar ___ 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] pdb module timeouts
Hello Marius, thanks a lot for submitting the patch. It works like a charm now. But to be honest I had troubles to find this patch, I just checked the daily tarball http://sip-router.org/tarballs/sr/ and found this change.How I can get patch e914f97b4 in a better way ?regards,Thomas>Hello>I have made a patch to 3.1(e914f97b4) . The poll() event list was not >cleared when a response was received so when 2 servers responded one >after the other it might block in an incorrect recv(). Can you please >test with this?>Marius WEB.DE DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt mit gratis Handy-Flat! http://produkte.web.de/go/DSL_Doppel_Flatrate/2 ___ 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] pdb module timeouts
On 02/15/2011 06:31 PM, Thomas Baumann wrote:
Hello
I have made a patch to 3.1(e914f97b4) . The poll() event list was not
cleared when a response was received so when 2 servers responded one
after the other it might block in an incorrect recv(). Can you please
test with this?
Marius
Hello,
I did a fallback to the original source, without sucess. I still have massive
timeouts. So far I have no idea, how to go on.
ps. what lenght of the carrier codes would be ok ? 3...10 digits, additional
characters needed like A,B,C,D,E,F?
regards,
Thomas
Hi Henning,
this change was done at pdbt.c:
$ diff pdbt.c pdbt_changed.c
245c245
<bufsize = slen + 1 + 1 + 3 + 1 + 1; // line
buff
er (telephone number + colon + white space + carrier ID + newline + \0)
---
bufsize = slen + 1 + 1 + 4 + 1 + 1; // line buff
er (telephone number + colon + white space + carrier ID + newline + \0)
257,258c257,258
<ret = snprintf(p, 5, "%d\n", node->carrier);
<if (ret< 1 || ret> 4) {
---
ret = snprintf(p, 6, "%d\n", node->carrier);
if (ret< 1 || ret> 5) {
If I run querys in filemode against the server, where is no timeout.
pdbt query -f /tmp/numbers3 -r 10.12.18.21:10001 -q 1 | grep answer
regards,
Thomas
-Ursprüngliche Nachricht-
Von: "Henning Westerholt"
Gesendet: 11.02.2011 09:33:05
An: sr-users@lists.sip-router.org
Betreff: Re: [SR-Users] pdb module timeouts
On Wednesday 09 February 2011, Thomas Baumann wrote:
I am using the PDB module and server components for number portability. 2
instances of PDB Server runs on (10.12.19.51/10001/10002), Kamailio on
(10.12.19.21). With a small amount of traffic (-cmax 150 -cps 10
-callduration 3), where are timeouts: WARNING: pdb [pdb.c:260]: exceeded
timeout while waiting for response.
One requested number was 307111094, where the module prints out a timeout.
The funny part is, that I can see the responses at least arriving at the
10.12.19.21 interface on time.
Request send: 0,200855 s
Answer received: 0,201027 s
That are 0,172 ms and far away from a timeout.
What could be the reason ?
Hi Thomas,
a bit difficult to say on a first sight.. Maybe some scheduling or load issues
on the local machine? I've just checked two production server here, i don't
see it so far in the available logs.
How much load do you've on the machine? And what kind of timeout value do you
specified?
ps. A small change on the server part was done: handle 4 digit carrier
codes.
Ah, i see. I guess its not a big change?
Regards,
Henning
___
Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die
Toolbar eingebaut! http://produkte.web.de/go/toolbar
___
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
___
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] pdb module timeouts
Hello,
I did a fallback to the original source, without sucess. I still have massive
timeouts. So far I have no idea, how to go on.
ps. what lenght of the carrier codes would be ok ? 3...10 digits, additional
characters needed like A,B,C,D,E,F?
regards,
Thomas
Hi Henning,
this change was done at pdbt.c:
$ diff pdbt.c pdbt_changed.c
245c245
< bufsize = slen + 1 + 1 + 3 + 1 + 1; // line buff
er (telephone number + colon + white space + carrier ID + newline + \0)
---
> bufsize = slen + 1 + 1 + 4 + 1 + 1; // line buff
er (telephone number + colon + white space + carrier ID + newline + \0)
257,258c257,258
< ret = snprintf(p, 5, "%d\n", node->carrier);
< if (ret < 1 || ret > 4) {
---
> ret = snprintf(p, 6, "%d\n", node->carrier);
> if (ret < 1 || ret > 5) {
If I run querys in filemode against the server, where is no timeout.
pdbt query -f /tmp/numbers3 -r 10.12.18.21:10001 -q 1 | grep answer
regards,
Thomas
-Ursprüngliche Nachricht-
Von: "Henning Westerholt"
Gesendet: 11.02.2011 09:33:05
An: sr-users@lists.sip-router.org
Betreff: Re: [SR-Users] pdb module timeouts
On Wednesday 09 February 2011, Thomas Baumann wrote:
> I am using the PDB module and server components for number portability. 2
> instances of PDB Server runs on (10.12.19.51/10001/10002), Kamailio on
> (10.12.19.21). With a small amount of traffic (-cmax 150 -cps 10
> -callduration 3), where are timeouts: WARNING: pdb [pdb.c:260]: exceeded
> timeout while waiting for response.
>
> One requested number was 307111094, where the module prints out a timeout.
>
> The funny part is, that I can see the responses at least arriving at the
> 10.12.19.21 interface on time.
>
> Request send: 0,200855 s
> Answer received: 0,201027 s
>
> That are 0,172 ms and far away from a timeout.
>
> What could be the reason ?
Hi Thomas,
a bit difficult to say on a first sight.. Maybe some scheduling or load issues
on the local machine? I've just checked two production server here, i don't
see it so far in the available logs.
How much load do you've on the machine? And what kind of timeout value do you
specified?
> ps. A small change on the server part was done: handle 4 digit carrier
> codes.
Ah, i see. I guess its not a big change?
Regards,
Henning
___
Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die
Toolbar eingebaut! http://produkte.web.de/go/toolbar
___
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] pdb module timeouts
Henning Westerholt writes: > > ps. A small change on the server part was done: handle 4 digit carrier > > codes. > > Ah, i see. I guess its not a big change? i have done the same change. perhaps it would make sense to make the module a bit more flexible in terms of length of carrier code. -- juha ___ 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] pdb module timeouts
On Friday 11 February 2011, Thomas Baumann wrote: > the load I have on one machine is about 10 cps max. The timeout is > configured to the standard value of 50ms. I the logs I can see that the > response times are not continuous. > Feb 11 17:28:34 m-lab-prx-as-2 /openser/sbin/kamailio[7609]: INFO: pdb > [pdb.c:290]: got an answer in 35.95 ms > Feb 11 17:28:34 m-lab-prx-as-2 /openser/sbin/kamailio[7607]: INFO: pdb > [pdb.c:290]: got an answer in 0.201000 ms Hi Thomas, this is not much load, and a long timeout. Maybe its something special about the used scheduler, or some other process that causes delays? The response times looks indeed somehow strange. 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] pdb module timeouts
Hello Henning, the load I have on one machine is about 10 cps max. The timeout is configured to the standard value of 50ms. I the logs I can see that the response times are not continuous. Feb 11 17:28:34 m-lab-prx-as-2 /openser/sbin/kamailio[7609]: INFO: pdb [pdb.c:290]: got an answer in 35.95 ms Feb 11 17:28:34 m-lab-prx-as-2 /openser/sbin/kamailio[7607]: INFO: pdb [pdb.c:290]: got an answer in 0.201000 ms Feb 11 17:28:38 m-lab-prx-as-2 /openser/sbin/kamailio[7609]: INFO: pdb [pdb.c:290]: got an answer in 0.626000 ms Feb 11 17:28:38 m-lab-prx-as-2 /openser/sbin/kamailio[7605]: INFO: pdb [pdb.c:290]: got an answer in 41.026000 ms Feb 11 17:28:38 m-lab-prx-as-2 /openser/sbin/kamailio[7607]: INFO: pdb [pdb.c:290]: got an answer in 29.807000 ms Feb 11 17:28:38 m-lab-prx-as-2 /openser/sbin/kamailio[7609]: INFO: pdb [pdb.c:290]: got an answer in 0.32 ms Feb 11 17:28:38 m-lab-prx-as-2 /openser/sbin/kamailio[7607]: INFO: pdb [pdb.c:290]: got an answer in 0.173000 ms I will do a fallback to the original source and check it again. Maybe there is something from with my modifications. thanks, Thomas -Ursprüngliche Nachricht- Von: "Henning Westerholt" Gesendet: 11.02.2011 09:33:05 An: sr-users@lists.sip-router.org Betreff: Re: [SR-Users] pdb module timeouts On Wednesday 09 February 2011, Thomas Baumann wrote: > I am using the PDB module and server components for number portability. 2 > instances of PDB Server runs on (10.12.19.51/10001/10002), Kamailio on > (10.12.19.21). With a small amount of traffic (-cmax 150 -cps 10 > -callduration 3), where are timeouts: WARNING: pdb [pdb.c:260]: exceeded > timeout while waiting for response. > > One requested number was 307111094, where the module prints out a timeout. > > The funny part is, that I can see the responses at least arriving at the > 10.12.19.21 interface on time. > > Request send: 0,200855 s > Answer received: 0,201027 s > > That are 0,172 ms and far away from a timeout. > > What could be the reason ? Hi Thomas, a bit difficult to say on a first sight.. Maybe some scheduling or load issues on the local machine? I've just checked two production server here, i don't see it so far in the available logs. How much load do you've on the machine? And what kind of timeout value do you specified? > ps. A small change on the server part was done: handle 4 digit carrier > codes. Ah, i see. I guess its not a big change? Regards, Henning ___ NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://produkte.web.de/go/webdefreephone ___ 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] pdb module timeouts
On Wednesday 09 February 2011, Thomas Baumann wrote: > I am using the PDB module and server components for number portability. 2 > instances of PDB Server runs on (10.12.19.51/10001/10002), Kamailio on > (10.12.19.21). With a small amount of traffic (-cmax 150 -cps 10 > -callduration 3), where are timeouts: WARNING: pdb [pdb.c:260]: exceeded > timeout while waiting for response. > > One requested number was 307111094, where the module prints out a timeout. > > The funny part is, that I can see the responses at least arriving at the > 10.12.19.21 interface on time. > > Request send: 0,200855 s > Answer received: 0,201027 s > > That are 0,172 ms and far away from a timeout. > > What could be the reason ? Hi Thomas, a bit difficult to say on a first sight.. Maybe some scheduling or load issues on the local machine? I've just checked two production server here, i don't see it so far in the available logs. How much load do you've on the machine? And what kind of timeout value do you specified? > ps. A small change on the server part was done: handle 4 digit carrier > codes. Ah, i see. I guess its not a big change? Regards, 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
[SR-Users] pdb module timeouts
Hello, I am using the PDB module and server components for number portability. 2 instances of PDB Server runs on (10.12.19.51/10001/10002), Kamailio on (10.12.19.21). With a small amount of traffic (-cmax 150 -cps 10 -callduration 3), where are timeouts: WARNING: pdb [pdb.c:260]: exceeded timeout while waiting for response. One requested number was 307111094, where the module prints out a timeout. The funny part is, that I can see the responses at least arriving at the 10.12.19.21 interface on time. Request send: 0,200855 s Answer received: 0,201027 s That are 0,172 ms and far away from a timeout. What could be the reason ? regards, Thomas ps. A small change on the server part was done: handle 4 digit carrier codes. level3_logs: Feb 9 17:19:42 node2 /openser/sbin/kamailio[21200]: DEBUG: pdb [pdb.c:201]: querying '307111094'... Feb 9 17:19:42 node2 /openser/sbin/kamailio[21200]: WARNING: pdb [pdb.c:260]: exceeded timeout while waiting for response. ___ Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://produkte.web.de/go/toolbar pdb2.cap Description: Binary data ___ 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
