Hello List users:
I am trying to upgrade to the current version of Kamailio from the older
4.4 version to the current version. The 4.4 is functional but there are
some features of 5.1 that we wanted to test with.
It seems that my version of Linux (RHEL 6.9 or Oracle 6.9) has an issue
with a
PS. As a general rule of thumb, the size (in terms of buckets) of the
htable should be at least 2x the maximum number of entries you expect to
put in it, and the bigger the better.
Hash tables are inherently inefficient in that regard; it would require
a perfect hash algorithm and a perfect
Hello List,
I have a working setup with a kamailio + freeswitch where i can register
extension and make succesfull calls between them.
I added now a "external" path for outbound call to which i can
successfully route using the dialplan + dispatcher combo.
My problem is that my outbound path
Hi,
I might be mistaken in my interpretation of the situation, but my first
guess would be multiple entries ending up in the same slot is simply a
reflection of some values being hashed to the same bucket. Hash table
implementations usually deal with collisions by implementing a linked
list
On Thursday 31 May 2018 at 21:49:15, Daniel-Constantin Mierla wrote:
> Hello,
>
> older versions of kamailio packages included self signed certificates,
> but, afaik, the newer do not include as Debian imposed reproducible
> builds. The certificate being generated at build time, was always
>
Apologies if the initial report was unclear. The issue isn't with the actual
counts (which appear to be accurate), but that we are intermittently ending up
with 2 keys in the same entry instead of one per entry.
This makes parsing the data very difficult, and I cannot determine a reason it
Did you monitor the values of those statistics over the time? If yes,
was there a moment when the value evolved unexpected?
Cheers,
Daniel
On 31.05.18 19:30, Brooks Bridges wrote:
>
> Let me preface this with the statement that as best I can tell from
> docs and code, this function is supposed
Hello,
older versions of kamailio packages included self signed certificates,
but, afaik, the newer do not include as Debian imposed reproducible
builds. The certificate being generated at build time, was always different.
So you have to generate the certificates yourself. One option is to get
a
Hello,
does the OPTIONS request have To header tag parameter?
Cheers,
Daniel
On 31.05.18 18:20, Minh Phan wrote:
> Hi List,
>
> I have this warning message in kamailio log when Kamailio handle an
> OPTIONS message with topos module enabled (I am using Kamailio 5.1.2):
>
> WARNING: topos
Let me preface this with the statement that as best I can tell from docs and
code, this function is supposed to be 100% atomic and this shouldn't be able to
happen. I also have not found anything in the module's github commit logs that
would indicate this behavior has changed from previous
Hi List,
I have this warning message in kamailio log when Kamailio handle an OPTIONS
message with topos module enabled (I am using Kamailio 5.1.2):
WARNING: topos [tps_storage.c:400]: tps_storage_record(): no local address
- do record routing for all initial requests
In my config file, OPTIONS
Am Dienstag, 29. Mai 2018, 10:13:56 CEST schrieb Narasimhaiah, Vinod
Maralenahalli:
> I upgraded kamailio 4.4.2 to kamailio5.1.3 and i am getting this error
> *"Unable to load certificate file '/etc/kamailio/kamailio-selfsigned.pem",*
> kamilio 4.4.2 does not need the ssl file, but kamailio 5.1.3
Am Mittwoch, 30. Mai 2018, 10:55:07 CEST schrieb Kristijan Vrban:
> Hi Henning
>
> > if you don't use the tables (and the belonging rls modules), it save to
> > skip them.
>
> Yes, i do not use them. So for me does not matter. But i am 100% sure, the
> documentation
> at:
Am Mittwoch, 30. Mai 2018, 23:29:42 CEST schrieb Henning Westerholt:
> Am Mittwoch, 30. Mai 2018, 11:45:25 CEST schrieb Kristijan Vrban:
> thank you for the report, indeed its not working. Its only working for
> logged in users, which is of course not sensible. :-)
>
> I investigated this
Am Mittwoch, 30. Mai 2018, 01:55:38 CEST schrieb User 721:
> I am adding a kamailio module that references an external C library that
> maintains a hashtable in global scope. I am wondering what practice I
> should follow so that:
> - This hashtable (which I don't control directly) is shared by
Am Mittwoch, 30. Mai 2018, 13:33:27 CEST schrieb Robert Barrera:
> Good morning!
>
> We operate a VoIP platform and are interested in integrating the PIKE
> module.
>
> Is it possible for someone to assist us to discuss how this can be done and
> our options?
Hello Robert,
if you are looking
Am Donnerstag, 31. Mai 2018, 08:37:02 CEST schrieb Konstantin Polyakov:
> There is a structure sip_msg which is passed into a module and represents a
> received sip message. It contains number of pointers to hdr_field members.
> In its turn hdr_field contains member void* parsed
>
> In the
Hello All,
There is a structure sip_msg which is passed into a module and represents a
received sip message.
It contains number of pointers to hdr_field members.
In its turn hdr_field contains member void* parsed
In the sanity module we assign to parsed member a pointer to newly allocated
Good morning!
We operate a VoIP platform and are interested in integrating the PIKE
module.
Is it possible for someone to assist us to discuss how this can be done and
our options?
Thank you
logo_nop
Robert Barrera
305-663-8989
305-600-4786 fax
i...@myrealmobile.com
19 matches
Mail list logo
