eb 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/kamaili
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 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 hav
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), Kamail
nning 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 (1
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 time
: "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, wi
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:
Dear sr-users,
I use this straight forward dispatcher config. In the failure route I am
calling this function: ds_mark_dst("i");
Also this action is logged:
Feb 2 17:20:31 node5 /openser/sbin/kamailio[15945]: INFO: : FAIL_ONE:time [Wed
Feb 2 17:20:31 2011] destination sip:10.12.19.31:5060 mar
Hello,
I tested the pdb module and the pdb_server. It is a fast solution even with a
huge amount of numbers.
But how I can update the pdb_server in a fast and effective way ? I tried it
in the following way:
- number;carrier are stored in a mysql table (20 million entries)
- 2 pdb_servers ar
Hello,I tested the pdb module and the pdb_server. It is a fast solution even with a huge amount of numbers.But how I can update the pdb_server in a fast and effective way ? I tried it in the following way:- number;carrier are stored in a mysql table (20 million entries)- 2 pdb_servers are running
11 matches
Mail list logo