Re: [SR-Users] TCP stack is not doing load distribution among children for SIP

On 08/03/2017 08:01, Juha Heinanen wrote: > Daniel-Constantin Mierla writes: > >>> So, for example, if k2 is a presence server and k1 is forwarding >>> subscribes/publish requests to it, only one process at k2 would be >>> processing them since the tcp connection between k1 and k2 is reused? >>>

Re: [SR-Users] TCP stack is not doing load distribution among children for SIP

Daniel-Constantin Mierla writes: > > So, for example, if k2 is a presence server and k1 is forwarding > > subscribes/publish requests to it, only one process at k2 would be > > processing them since the tcp connection between k1 and k2 is reused? > > > Those were the observations described by the

Re: [SR-Users] TCP stack is not doing load distribution among children for SIP

On 08/03/2017 01:36, Juha Heinanen wrote: > Daniel-Constantin Mierla writes: > >> So, I expect kamailio wil reuse the connection between kamailio1 and >> kamailio2. The tcp manager process selects the least loaded tcp worker >> when a new connection is accepted, and the worker start consuming

Re: [SR-Users] TCP stack is not doing load distribution among children for SIP

Daniel-Constantin Mierla writes: > So, I expect kamailio wil reuse the connection between kamailio1 and > kamailio2. The tcp manager process selects the least loaded tcp worker > when a new connection is accepted, and the worker start consuming the > packets on it until there is nothing to be

Re: [SR-Users] new keepalive module ?

Hello, On 07/03/2017 21:22, Guillaume Bour wrote: > Hi all, > > I would like to implement destinations keepalive in drouting module (as it is > done in dispatcher). > But instead of duplicating what's implemented in dispatcher, I think it would > be more clever to create a new module >

Re: [SR-Users] problem with avpops and mongodb modules

Hello, I pushed another patch to fix a similar case in a different function. Can you try with it (6bd32088de1d7ae816643aea4a60c70911e46b5e)? Cheers, Daniel On 07/03/2017 14:50, hdssdsdsdsfsdf hdssdsdsdsfsdf wrote: > Hi, thanks, we have a similar error further on after succesfully applying >

Re: [SR-Users] TCP stack is not doing load distribution among children for SIP

Hello, On 07/03/2017 08:50, Surendra Pullaiah wrote: > Dear Daniel, > > > A small concern in kamailio, existing TCP stack is not doing load > distribution among children for SIP messages. For example UE-->kamailio1 (TCP > listen (4 children)) ->kamailio2 (TCP Listen 4 children) > >

[SR-Users] new keepalive module ?

Hi all, I would like to implement destinations keepalive in drouting module (as it is done in dispatcher). But instead of duplicating what's implemented in dispatcher, I think it would be more clever to create a new module dedicated to pinging destinations, and to plug drouting, dispatcher and

Re: [SR-Users] rtpengine sending rtp to wrong endpoint after reinvite

Hello, On 07/03/2017 13:10, Grant Bagdasarian wrote: > > Hi, > > > > One of our customers is using a SEMS box to place two outbound calls > using our sip trunk. > > Once the first call is connected a second call is placed and when the > second call answers their server sends a re-invite to

Re: [SR-Users] SIP contact header question

On Tue, Mar 07, 2017 at 03:44:31PM -0600, Jack Davis wrote: > What kind of problems can arise from inserting said header? Theoretically, none. It should be ignored, as per the RFC. Moreover, the RFC doesn't _prohibit_ such a header in an in-dialog request, so you are probably clear to add it.

Re: [SR-Users] SIP contact header question

What kind of problems can arise from inserting said header? I'm trying to find a way to get a pesky setup to start behaving, of course, without requiring them to make any changes. Thank you, Jack Davis On Fri, Mar 3, 2017 at 2:39 PM, Alex Balashov wrote: > On Fri,

[SR-Users] new keepalive module ?

Hi all, I would like to implement destinations keepalive in drouting module (as it is done in dispatcher). But instead of duplicating what's implemented in dispatcher, I think it would be more clever to create a new module dedicated to pinging destinations, and to plug drouting, dispatcher and

Re: [SR-Users] Kamailio Presence help required.

Looks fairly sane. Try setting “pua” db_mode to 0. db_mode 2 takes a very different path through the code of the pua module and we have found it to be somewhat broken beyond repair. Our config is as follows. You may not have some of the stuff highlighted in yellow as I recently added those

Re: [SR-Users] Cdr on shutdown

Hi Daniel! Thanks for your answer. Sorry, i didn't provide enough data for what I need. I'm using kamailio as a statefull proxy and I all ready have dialog module working too but with no database. Today I started testing dialog with db_mode = 3 (shutdown). The thing is that when I kill kamailio

Re: [SR-Users] problem with avpops and mongodb modules

Hi, thanks, we have a similar error further on after succesfully applying your patch on 4.4.4. The setup is the same as it was before, and the result this time is: Mar 7 14:45:32 slb04 /usr/local/sbin/kamailio[28073]: ERROR:

Re: [SR-Users] Cdr on shutdown

On Tue, Mar 07, 2017 at 10:34:05AM -0300, Diego Nadares wrote: > Is it possible to generate cdrs or to save dialogs to db when kamailio > receives a kill signal from terminal? Killing kamailio doesn't end running calls. So if you restart kamailio before a BYE, accounting will be correct on

[SR-Users] Cdr on shutdown

Hi Guys, Is it possible to generate cdrs or to save dialogs to db when kamailio receives a kill signal from terminal? Thanks in advance. Diego ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org

[SR-Users] rtpengine sending rtp to wrong endpoint after reinvite

Hi, One of our customers is using a SEMS box to place two outbound calls using our sip trunk. Once the first call is connected a second call is placed and when the second call answers their server sends a re-invite to switch audio ports so the rtp traffic doesn't flow through their server

Re: [SR-Users] Kamailio core dumped

Hello, Daniel! Sure, issue is here - https://github.com/kamailio/kamailio/issues/1021 Thanks! 07.03.2017 12:58, Daniel-Constantin Mierla wrote: > Hello, > > can you open an issue on bug tracker? Having it there ensure that it is > not forgotten and properly handles -- sometimes people travel

Re: [SR-Users] Kamailio core dumped

Hello, can you open an issue on bug tracker? Having it there ensure that it is not forgotten and properly handles -- sometimes people travel and miss various messages on the mailing list. As a matter of fact for this specific case, your messages is put in spam folder for me by the gmail server

Re: [SR-Users] Kamailio 4.2 crashed

Hello, There were 3 additional crashes. The two last coredump are (for the same crash): (gdb) bt full #0 0x003f5d232925 in raise () from /lib64/libc.so.6 No symbol table info available. #1 0x003f5d234105 in abort () from /lib64/libc.so.6 No symbol table info available. #2

Re: [SR-Users] SCTP support for CDP

Hi Sergey, The peer looks correct and established/up. could you perhaps send me debug output for CDP module when you try and route? Please also share your xml configuration file for CDP module - there is most likely a configuration problem in the routing section... Cheers Jason On Tue, Mar 7,

Re: [SR-Users] SCTP support for CDP

Hi Carsten, Does this look ok on i-cscf: kamcmd cdp.list_peers { Realm: ims.mnc06.mcc240.3gppnetwork.org Identity: icscf.mnc06.mcc240.3gppnetwork.org Accept unknown peers: 1 Connect timeout: 5 Transaction timeout: 5 Default auth session timeout:

Re: [SR-Users] Kamailio core dumped

Hello, 01.03.2017 13:51, Alexey V. Panfilov wrote: > Hi there, > > I've kamailio 4.2.3 (i386/freebsd) which works perfectly with 200-300 > cps for years. > > Now I need migrate to freebsd amd64. I've installed kamailio 4.4.5 > (amd64/freebsd), copied kamailio.cfg, made a test call - it was all

Re: [SR-Users] problem with avpops and mongodb modules

Hello, can you try with current master branch or using the patch from next commit in your version? - https://github.com/kamailio/kamailio/commit/501c41dd35fb9f15fdf96f4f3778860395e37a84 I am not able to test these days, but if you report it is working fine, then I can backport to stable