Iñaki,
Yes, it does. Xcap module parses request url, and produces $xcapuri(u=>xuid),
which could have different formats: user, u...@domain or sip:u...@domain.
And $var{uri} is a "sip normalised" form of it, ie: sip:u...@domain.
This part was taken from Daniels tutorial as is. My question was abo
On 10/16/2010 09:18 AM, Juha Heinanen wrote:
Uriel Rozenbaum writes:
What would be best to optimize the system is to have some statistic
information, save every now and then the status of the htable and act
accordingly to:
it would indeed be nice of htable module would exports stats about
col
>
> JR, if you don't already know SIPSAK, go download it. It's what I use in
> Nagios and many other scripts.
> Nils has done a great job with it.
>
> /O=
Thanks Olle, I'll check it out.
JR
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-use
Uriel Rozenbaum writes:
> What would be best to optimize the system is to have some statistic
> information, save every now and then the status of the htable and act
> accordingly to:
it would indeed be nice of htable module would exports stats about
collisions.
-- juha
Iñaki,
Just as an addition from experience on hash tables, the first
"sweet-spot" on the design is to have a fairly good algorithm so that
different keys are mapped on different hash values. You cannot pick
this (as far as I read) but we'll think it as fair enough. What you
can do to "help" the al
Can you detail what is not working in 3.1.0?
Regards,
Ovidiu Sas
On Fri, Oct 15, 2010 at 5:24 PM, Joe Uelk wrote:
> Thanks for the information Klaus and Ovidiu!
> It seems the 4to6.cfg file referenced is for a different version of
> Kamailio. I'm using 3.1.0 and I was unable to get it to run wit
Thanks for the information Klaus and Ovidiu!
It seems the 4to6.cfg file referenced is for a different version of
Kamailio. I'm using 3.1.0 and I was unable to get it to run with that .cfg
file.
I installed Kamailio on Fedora 10 as an rpm. It runs successfully with the
default configuration.
Also
Iñaki Baz Castillo writes:
> And those collisions mean that I could look for a key name and
> retrieve another key (as both key names produce the same hash), am I
> right?
no, the values whose keys hash to the same index of hash table, are
added into a linked list and then list list will be searc
2010/10/16 Juha Heinanen :
> size=4 means that the hash table has 16 entries. it does not mean that
> the table could not contain more objects, but collisions will happen.
And those collisions mean that I could look for a key name and
retrieve another key (as both key names produce the same hash)
Iñaki Baz Castillo writes:
> Hi, in the doc of HTable module all the examples show "a=>size=4;". As
> the doc says:
>
> size - number specifying the size of hash table. The number of entries in
>the table is 2^size
>
> This is, the examples just allow 16 concurrent entries, which i
Hi, in the doc of HTable module all the examples show "a=>size=4;". As
the doc says:
size - number specifying the size of hash table. The number of entries in
the table is 2^size
This is, the examples just allow 16 concurrent entries, which is not
enough in most of the cases.
Did I m
2010/10/16 Rouskol Andrey :
> if($hu=~"^/xcap-root/")
> {
> # xcap ops
> $xcapuri(u=>data) = $hu;
> if($xcapuri(u=>xuid)=~"^sip:@.+")
> $var(uri) = $xcapuri(u=>xuid);
> else if($xcapuri(u=>xuid)=~".
15 okt 2010 kl. 17.42 skrev JR Richardson:
> On Fri, Oct 15, 2010 at 10:22 AM, Fred Posner wrote:
>> Hey JR...
>>
>> I use this:
>>
>> #! /usr/bin/perl -w
>> use IO::Socket;
>> use POSIX 'strftime';
>>
>> my ($msg,$remotehost,$callid,$socket,$date,$branch,$localip,$dest);
>>
>> $remotehost =
13 matches
Mail list logo
