sr-users March 2016

sr-users@lists.kamailio.org

88 participants
128 discussions

Multiple LCR instances with LCR module
by DanB 25 Mar '16

25 Mar '16

Hey Guys, I was wondering if any of you use multiple LCR instances with LCR module since I could see that the documentation allows it, however for some reason the queries to load data (both on restart or kamcmd lcr.reload) somehow hardcode the value of 1 inside: """ select `gw_name`,`ip_addr`,`port`,`uri_scheme`,`transport`,`params`,`hostname`,`strip`,`prefix`,`tag`,`flags`,`defunct`,`id` from `lcr_gw` where `lcr_id`=0 select `gw_name`,`ip_addr`,`port`,`uri_scheme`,`transport`,`params`,`hostname`,`strip`,`prefix`,`tag`,`flags`,`defunct`,`id` from `lcr_gw` where `lcr_id`=1 select `id`,`prefix`,`from_uri`,`stopper`,`enabled`,`request_uri` from `lcr_rule` where `lcr_id`=1 select `rule_id`,`gw_id`,`priority`,`weight` from `lcr_rule_target` where `lcr_id`=1 """ My kamailio version: """ # kamailio -V version: kamailio 4.3.5 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 4.9.2 """ Many thanks in advance for any kind of tip! DanB

2 1

kamailio memory issue
by Volodymyr Rykhva 25 Mar '16

25 Mar '16

Hi, I have started using kamailio recently. Added to db almost 100K users. And now I am trying to increase shared and private memory with this command when server is running: kamailio -M 12 -m 128. But then I check it with `kamailio -l` and the same values (64 and 8 respectively) are there. Can I change it with config? or what I do wrong. And what's the purpose of child process? - Will kamailio process requests faster if I set child=32 (for example)? Thanks and best regards, Volodymyr

2 1

Re: [SR-Users] htable - banning users
by meres 24 Mar '16

24 Mar '16

Thank u Vasiliy and Daniel, I used -3 condition as you suggested! Regards, meres

1 0

dynamic weighting for dispatcher
by Brooks Bridges 24 Mar '16

24 Mar '16

So I'm building a load balancer solution that needs to monitor remote devices at a specific interval via snmp for certain data (channels and cps) and use that data to create a dynamically updated weight for each of the destinations. I can't find any reasonable mechanism for updating the weight attribute in the dispatcher module itself without having to do some hacky "update the database column then trigger dispatcher.reload" script, which I very much want to avoid. Is this something I should just be thinking of ditching the dispatcher module and rolling my own design or am I missing something obvious? Brooks Bridges | Sr. Voice Services Engineer O1 Communications 5190 Golden Foothill Pkwy El Dorado Hills, CA 95762 office: 916.235.2097 | main: 888.444.1111, Option 2 email: bbridges(a)o1.com<mailto:bbridges@o1.com> | web: www.o1.com<http://www.o1.com/>

2 2

Dispatching Registrations to Weight based servers
by SamyGo 24 Mar '16

24 Mar '16

Hi All, I'm having a wee little bit of difficulty in trying to load-balance registrations to multiple servers based on their weights. Kind of similar scenario as discussed in this thread: http://lists.sip-router.org/pipermail/sr-users/2014-December/086235.html The problem I'm facing is that dispatcher is always choosing the first destination from the group. I do suspect that dispatcher is not considering registrations as load at all and only counts INVITES as load. If above is correct then is there a way to use dispatcher to count registrations as load ? Thanks, Sammy

2 3

Kamailio 5.0 - B2BUA
by Alex Balashov 24 Mar '16

24 Mar '16

Hi, I wanted to raise the possibility of an inline signalling-only B2BUA component to Kamailio. I know that's an extremely poor fit for Kamailio, and not at all what it's supposed to do. And there are many things about the OpenSIPS B2BUA module that reveal how awkwardly it is situated, as a square peg in a round hole. I myself am philosophically opposed to a B2BUA in Kamailio to the threshold of physical violence. However, the reason I bring it up for discussion is that there are very few viable, high-performance signalling-only B2BUA alternatives that are FOSS. There is enormous demand for a B2BUA, mainly for topology concealment purposes, from the short-duration traffic industry, which many users of Kamailio deal with. It's why a lot of them end up going to OpenSIPS; they need the B2BUA, and prefer to consolidate on one OpenSER brand. Anyone who has tried to run high-CPS traffic through the existing FOSS signalling-only B2BUAs out there situated in front of Kamailio has discovered, sometimes in a very financially painful way, that: - FreeSWITCH falls over at around +/- 300 CPS. This is with RTP relay disabled -- signalling-only. It requires horizontally scaling a large number of FreeSWITCH boxes to meet a capacity requirement of, say, 2000 CPS, which is unfortunate given the favourable proposition offered by Kamailio for the infrastructure unit economics. In other words, it's ironic to have to build a fleet of 10 FreeSWITCH boxes for the 1% problem of topology concealment when Kamailio can otherwise churn through 2000 CPS with no issues. - SEMS' 'sbc' module is a good candidate and can handle the load, but Frafos offers practically no support for it, with all efforts focused on their commercial ABC SBC product. That's very understandable, but just not practical given the high technical knowledge SEMS requires to deploy and maintain in this capacity. - None of the other userspace B2BUA folk traditions can handle the load. So, like I said, I personally recoil in shock and horror at the idea of introducing a B2BUA into something that was designed to be anything but a B2BUA. But, there is a huge market opportunity for this functionality in North America, and at the moment, users who need it are mostly ending up in OpenSIPS land. -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

8 15

Presence Publish expires
by Igor Olhovskiy 24 Mar '16

24 Mar '16

Hi! Is there any possibility to set Expires in PUBLISH message to never in Presence module? I want to have BLF’s that indicates states, that driven via PUBLISH, but can be really irregular (let’s say once a week) -- Best regards, Igor

3 5

dialog rpc functions.
by Yasin CANER 24 Mar '16

24 Mar '16

1 0

kamailio in a multi-site configuration
by Sébastien Brice 24 Mar '16

24 Mar '16

Hi everyone i am installing Kamailio to scale asterisk on a remote hosted server in a way to manage calls dialogs in a real-time fashion. (and to manage many customers) Several users (maybe 80) are working at the head-office and i want them register their hardphone on the remote Kamailio Ipbx, to free them of ours end-of-life PABX (alcatel-Lucent). Can kamailio help me to achieve that ? What kind of software have I to install locally (mysql to replicate the master mysql db? a replicated asterisk instance?) ? Taking into consideration disaster recovery plan What could be my options to maintain internal call if my internet provider get down by exemple. thx you for your idea. Sébastien BRICE VoIP, Support et Intégration

3 2

set_advertised_address() / set_advertised_port() + PVs?
by Alex Balashov 23 Mar '16

23 Mar '16

Hello, I have a need to deploy Kamailio in AWS in a scenario of this sort: [Public Internet] <---> Kamailio <---> (Internal AWS servers) In such a scenario, Kamailio would be multihomed. Furthermore, in addition to sending out of two distinct network interfaces, the networking idiosyncrasies of AWS needs to be taken into account. AWS hosts only have an RFC1918 address homed natively, front-ended by 1:1 NAT externally. Normally, this is taken care of by advertised_address, which allows Kamailio to make outward representations about the network address by which it can be reached that are different to the IP to which it is bound. The problem here is that I need to do this conditionally, only on traffic going out the public interface. It should not be done on messages going to the "internal AWS servers". So, the questions that arise are: 1. Is this sane? Any unforeseen effects, e.g. vis-a-vis RR, provided enable_double_rr is enabled and that two genuinely different network interfaces are used? 2. Do set_advertised_address()/set_advertised_port() accept PV arguments, or are they pre-PV "core function folk traditions" in the same way as rewritehostport() and force_send_socket()? Thanks! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 1447 Peachtree Street NE, Suite 700 Atlanta, GA 30309 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 10

← Newer
1
2
3
4
5
6
7
8
9
...
13
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users March 2016