for response.
- Show quoted text -
On Wed, Feb 16, 2011 at 4:59 PM, marius zbihlei marius.zbih...@1and1.ro
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
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,ThomasHelloI have
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
: [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
Westerholt henning.westerh...@1und1.de
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
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
: Daniel-Constantin Mierla
Gesendet: 03.02.2011 21:38:49
An: Thomas Baumann
Betreff: Re: [SR-Users] dispatcher - ds_mark_dst(i); is inactive only few
seconds
Hello,
On 2/3/11 7:07 PM, Thomas Baumann wrote:
Hi Daniel,
thanks for the hints, with debug_level they are some hints what happened
Hi Daniel,
thanks for the hints, with debug_level they are some hints what happened.
Normal Operation:
5(20410) DEBUG: dispatcher [dispatch.c:2305]: probing set #1, URI
sip:10.12.19.31:5060
5(20410) DEBUG: dispatcher [dispatch.c:2305]: probing set #1, URI
sip:10.12.19.21:5060
4(20409) DEBUG: