sr-dev January 2015

sr-dev@lists.kamailio.org

38 participants
530 discussions

by Daniel-Constantin Mierla

Hello, I was considering to discuss the state of Kamailio project logo for a while. The current state is ambiguous, to say at least - various logos in different places. When OpenSER was renamed in Kamailio we were trying to get something new, but due to the 'forks and dark waters' at that time, this process was never completing, meanwhile using an adaptation of old openser logo. However, there are no high resolution or other variants suitable for using in particular conditions (e.g., black and white, big posters). First, a question that we should decide on: shall we aim for a new logo or try to get someone to make proper graphics from the current shape? (for reference, the logo from http://www.kamailio.org/wp-images/kamailio-rock-logo.jpg). I would prefer to go for a new logo, but I admit that this process can become complex, a mater of tastes, not something we can decide on technical aspects. Therefore, if it ends up in something that doesn't seem to have the acceptance of major contributors (with coding, advertising/promoting, ...) to the project, then we stick with current for a while. My preference is based on the fact that Kamailio evolved over the time, has its own identity, so a fresh look of the logo would reflect that better. I am listing here the options, that people can express preference on: A) New logo A1) variant based on Kamailio World logo (used by twitter kamailioproject account and on some materials at various events). It was a backup variant so far as we had high resolution graphics that could be adapted to get a good image for big posters. Can be seen at: - http://www.kamailio.org/pub/kamailio-logos/variants/kamailio-from-world-log… - http://www.fredposner.com/1471/kamailio-at-astricon-2013/ A2) use a professional service for that. Kamailio World logo was made with 99designs.com service, which is quite good considering there will be many submissions to choose between, options can be visible by everyone. There might be other similar services, this is one I have experience with and worked fine in the past -- anyhow, it has to be something that all management and solution can be done online. Asipto can sponsor at least the bronze package if 99designs is going to be used, maybe others want to participate with extra funds to get a better package. A3) leverage on community, in case some companies have internal designers or some of you have such skills or friends. Perhaps this has the highest risk on escalating, given that is going to be some direct involvement in proposals and selection. B) Old logo B1) get someone to produce high resolution graphics from existing logo No matter what variant, who will do the work or financial contribution, will get credits via our web site. However, all the rights of the resulting logo will belong to the Kamailio project. To conclude, the order of my preferences: A2, A1, A3, B1 Looking forward to feedback from many of you! Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

9 years, 9 months

[kamailio] Reproducible Builds (#60)

by Victor Seva

Debian has this goal https://wiki.debian.org/ReproducibleBuilds/ As you can see here https://reproducible.debian.net/rb-pkg/kamailio.html we are using __TIME__ and __DATE__ macros ``` gcc -funroll-loops -Wcast-align -m64 -minline-all-stringops -falign-loops -ftree-vectorize -fno-strict-overflow -Wall -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Werror=date-time -D_FORTIFY_SOURCE=2 -DNAME='"kamailio"' -DVERSION='"4.2.0"' -DARCH='"x86_64"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 4.9.2"' -D__CPU_x86_64 -D__OS_linux -DSER_VER=4002000 -DCFG_DIR='"/etc/kamailio/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DWITH_XAVP -DF_MALLOC -DDBG_F_MALLOC -DMEM_JOIN_FREE -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS -DSTATISTICS -DMALLOC_STATS -DWITH_AS_SUPPORT -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DUSE_RAW_SOCKS -DHAVE_EPOLL -DHAVE_ SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -c ver.c -o ver.o -MMD -MP ver.c:38:35: error: macro "__TIME__" might prevent reproducible builds [-Werror=date-time] const char ver_compiled_time[] = __TIME__ " " __DATE__ ; ^ ver.c:38:48: error: macro "__DATE__" might prevent reproducible builds [-Werror=date-time] const char ver_compiled_time[] = __TIME__ " " __DATE__ ; ^ cc1: some warnings being treated as errors ``` Can we introduce a Make option to avoid this? --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/60

9 years, 9 months

[kamailio] use of ssl causes increase of mysql connections (#58)

by juha-h

Below is an example kamailio.conf, where addition of [group] to "db_url" value increases number of mysql connections from 36 to 70. [group] is defined in in my.cfg as: [group] ssl-ca=/etc/mysql/ca-cert.pem ssl-cert=/etc/mysql/client-cert.pem ssl-key=/etc/mysql/client-key.pem With sqlops module alone the number of mysql connections is the same with or without [group]. kamailio.conf: listen=192.98.102.33:5060 fork=yes log_stderror=no log_facility=LOG_LOCAL0 debug=2 loadmodule "tm" loadmodule "auth" loadmodule "sl" loadmodule "pv" loadmodule "auth_db" loadmodule "dialplan" loadmodule "domain" loadmodule "htable" loadmodule "permissions" loadmodule "pua" loadmodule "db_mysql" loadmodule "sqlops" loadmodule "xlog" modparam("auth_db|dialplan|domain|htable|permissions|pua", "db_url", "mysql://user:pass@[group]127.0.0.1/sip_proxy") modparam("sqlops", "sqlcon", "sip_proxy => mysql://user:pass@[group]127.0.0.1/sip_proxy") route { sql_query("sip_proxy", "show status like 'ssl_cipher'", "result"); xlog("L_INFO", "**** got result <variable=$dbr(result=>[0, 0])/value=$dbr(result=>[0, 1])>\n"); sql_result_free("result"); exit; } --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/58

9 years, 9 months

[kamailio] Pipelimit on non-Linux: Repeating warning messages endlessly (#38)

by Olle E. Johansson

Pipelimit on non-Linux keeps complaining that it can't read files in /proc/net - repeatedly. While one warning is a good one, repeating it and filling log files is not a good thing imho. Tested with git head master --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/38

9 years, 9 months

[kamailio] SCA crash when db not configured (#57)

by Olle E. Johansson

Loading the module in small config with no modparams crash. Updated and installed latest git head after patch to sca for previous crash. #0 0x000000010a294823 in sca_db_get_connection () at sca_db.c:158 No locals. #1 0x000000010a2ac1e7 in sca_subscription_db_update () at sca_subscribe.c:493 db_con = (db1_con_t *) 0x0 ht = (sca_hash_table *) 0x69687720726f7272 entry = (sca_hash_entry *) 0x65203a524f525245 sub = (sca_subscription *) 0x7fff8c8362dd i = 0 rc = -1 now = 1422480694 #2 0x000000010a23f4d9 in sca_mod_destroy () at sca.c:370 No locals. #3 0x000000010932fe49 in destroy_modules () at sr_module.c:788 t = (struct sr_module *) 0x10977b620 foo = (struct sr_module *) 0x10977b090 #4 0x0000000109185dfb in cleanup (show_status=0) at main.c:512 memlog = 0 #5 0x000000010918d75b in shutdown_children (sig=15, show_status=0) at main.c:654 No locals. #6 0x00000001091a264d in main (argc=3, argv=0x7fff56b61a98) at main.c:2541 --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/57

9 years, 9 months

[kamailio] call_control :: Depends on pv (#37)

by Olle E. Johansson

Call_control depends on pv, but it's not documented in the README 0(70806) ERROR: <core> [pvapi.c:790]: pv_parse_spec2(): error searching pvar "avp" 0(70806) ERROR: <core> [pvapi.c:994]: pv_parse_spec2(): wrong char [s/115] in [$avp(s:can_uri)] at [5 (5)] 0(70806) : call_control [call_control.c:1076]: mod_init(): invalid AVP specification for canonical_uri_avp: `$avp(s:can_uri)' 0(70806) ERROR: <core> [sr_module.c:945]: init_mod(): Error while initializing module call_control --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/37

9 years, 9 months

[kamailio] rtpengine module error with new masterbranch (#32)

by ovoshlook

Hello. We Build 4.3 masterbranch (latest branch) . We install it today and not changed config from old build (4.3 masterbranch) that builded december 26. IT means - keys of rtpengine module the same for all configs. Last changes of rtpengine was nowember 28. This mean rtpengine is the same with to builds. With new branch we have an error with rtpengine module. Jan 14 05:09:58 Kamailio rtpengine[482]: [7dd25def58ced3786f99894d1c34e18a@10.0.1.17:50600 port 30080] Error parsing RTP header: invalid header version Jan 14 05:09:58 Kamailio rtpengine[482]: [7dd25def58ced3786f99894d1c34e18a@10.0.1.17:50600 port 30081] Error parsing RTCP header: invalid header version --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/32

9 years, 9 months

[kamailio] Geoip2 module (#52)

by sokhapkin

Implementation of geoip2 module based on the new Maxmind geoip2 database format. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/52 -- Commit Summary -- * Geoip2 module -- File Changes -- A modules/geoip2/Makefile (15) A modules/geoip2/README (146) A modules/geoip2/doc/Makefile (4) A modules/geoip2/doc/geoip2.xml (36) A modules/geoip2/doc/geoip2_admin.xml (175) A modules/geoip2/geoip2_mod.c (139) A modules/geoip2/geoip2_pv.c (476) A modules/geoip2/geoip2_pv.h (40) -- Patch Links -- https://github.com/kamailio/kamailio/pull/52.patch https://github.com/kamailio/kamailio/pull/52.diff --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/52

9 years, 9 months

Siremis suggestion for kamailio_cdrs procedure

by Klaus Darilion

Hi! The kamailio_cdrs procedure, as described at http://siremis.asipto.com/install-accounting/, has the database name hard coded (i.e. "openser"). I suggest to remove the hard coded DB or at least make a warning that the DB name needs to be adopted. Thanks Klaus

9 years, 9 months

[kamailio] dmq: fix memory leak (#59)

by Andrey Rybkin

You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/59 -- Commit Summary -- * dmq: fix memory leak -- File Changes -- M modules/dmq/worker.c (4) -- Patch Links -- https://github.com/kamailio/kamailio/pull/59.patch https://github.com/kamailio/kamailio/pull/59.diff --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/59

9 years, 9 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev January 2015