sr-dev October 2015

sr-dev@lists.kamailio.org

28 participants
236 discussions

[kamailio] kamailio 4.4.0-dev5 crashes using pua + pua_reginfo (#377)
by foucse 02 Nov '15

02 Nov '15

``` version: kamailio 4.4.0-dev5 (i386/linux) 9251a6 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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: 9251a6 compiled on 11:10:30 Oct 22 2015 with gcc 4.9.2 ``` I use db_postgres. Kamailio crashes with the following messages in logs: ``` [...] Oct 22 14:46:18 system /usr/local/sbin/kamailio[26484]: DEBUG: <core> [receive.c:278]: receive_msg(): cleaning up Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: db_postgres [km_dbase.c:272]: db_postgres_submit_query(): sending query ok: 0xb659ab2c (1) - [LOCK TABLE pua IN EXCLUSIVE MODE Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [db_res.c:116]: db_new_result(): allocate 32 bytes for result set at 0xb659b628 Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: db_postgres [km_dbase.c:552]: db_postgres_store_result(): 0xb659ab2c PQresultStatus(PGRES_COMMAND_OK) PQgetResult(0x88c62e0) Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: db_postgres [km_dbase.c:433]: db_postgres_free_query(): PQclear(0x88c62e0) result set Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 0 columns Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [db_res.c:134]: db_free_result(): freeing result set at 0xb659b628 Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: pua [send_subscribe.c:310]: subs_cback_func(): completed with status 202 Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=0 Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: pua [send_subscribe.c:383]: subs_cback_func(): lexpire= 3600 Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: tag=925159b1c018b9f775ed54c55b81927f-c2db Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=29 Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: pua [send_subscribe.c:437]: subs_cback_func(): 'To' header ALREADY PARSED: <sip:alice@proxy.example.com:5060> Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: pua [send_subscribe.c:674]: subs_cback_func(): record for subscribe from sip:reginfo@example.com:5060 to sip:alice@proxy.example.com:5060 inserted in datatbase Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: db_postgres [km_dbase.c:272]: db_postgres_submit_query(): sending query ok: 0xb659ab2c (1) - [COMMIT] Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [db_res.c:116]: db_new_result(): allocate 32 bytes for result set at 0xb659bd60 Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: db_postgres [km_dbase.c:552]: db_postgres_store_result(): 0xb659ab2c PQresultStatus(PGRES_COMMAND_OK) PQgetResult(0x88c62e0) Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: db_postgres [km_dbase.c:433]: db_postgres_free_query(): PQclear(0x88c62e0) result set Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 0 columns Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [db_res.c:134]: db_free_result(): freeing result set at 0xb659bd60 Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: db_postgres [km_dbase.c:272]: db_postgres_submit_query(): sending query ok: 0xb659ab2c (1) - [BEGIN] Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [db_res.c:116]: db_new_result(): allocate 32 bytes for result set at 0xb659bd60 Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: db_postgres [km_dbase.c:552]: db_postgres_store_result(): 0xb659ab2c PQresultStatus(PGRES_COMMAND_OK) PQgetResult(0x88c62e0) Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: db_postgres [km_dbase.c:433]: db_postgres_free_query(): PQclear(0x88c62e0) result set Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 0 columns Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [db_res.c:134]: db_free_result(): freeing result set at 0xb659bd60 Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: db_postgres [km_dbase.c:272]: db_postgres_submit_query(): sending query ok: 0xb659ab2c (1) - [LOCK TABLE pua IN EXCLUSIVE MODE Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [db_res.c:116]: db_new_result(): allocate 32 bytes for result set at 0xb659beec Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: db_postgres [km_dbase.c:552]: db_postgres_store_result(): 0xb659ab2c PQresultStatus(PGRES_COMMAND_OK) PQgetResult(0x88c62e0) Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: db_postgres [km_dbase.c:433]: db_postgres_free_query(): PQclear(0x88c62e0) result set Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [db_res.c:79]: db_free_columns(): freeing 0 columns Oct 22 14:46:21 system /usr/local/sbin/kamailio[26483]: DEBUG: <core> [db_res.c:134]: db_free_result(): freeing result set at 0xb659beec Oct 22 14:46:21 system /usr/local/sbin/kamailio[26522]: CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 8 Oct 22 14:46:21 system /usr/local/sbin/kamailio[26522]: DEBUG: <core> [tcp_main.c:3448]: handle_ser_child(): dead child 2, pid 26482 (shutting down?) Oct 22 14:46:21 system /usr/local/sbin/kamailio[26522]: DEBUG: <core> [io_wait.h:598]: io_watch_del(): DBG: io_watch_del (0x841fe40, 8, -1, 0x0) fd_no=21 called Oct 22 14:46:21 system /usr/local/sbin/kamailio[26471]: ALERT: <core> [main.c:738]: handle_sigs(): child process 26482 exited by a signal 11 Oct 22 14:46:21 system /usr/local/sbin/kamailio[26471]: ALERT: <core> [main.c:741]: handle_sigs(): core was generated [...] ``` This is not the only thing happening in the same time but I suspect the following: 1 Some entity is sending a not very well formed REGISTER (without expiration value), here is an example: ``` REGISTER sip:example.com SIP/2.0. Via: SIP/2.0/UDP 10.37.145.129;branch=z9hG4bKc5af.bf143451000000000000000000000000.0. To: <sip:alice@example.com>. From: <sip:proxy.example.com>;tag=73b08d5bebdaf32004cf12d15b90246a-2710. CSeq: 10 REGISTER. Call-ID: 67cff7c9. Max-Forwards: 70. Content-Length: 0. User-Agent: kamailio (4.4.0-dev5 (i386/linux)). Contact: <sip:alice@proxy.example.com:5060>. Authorization: Digest username="2291511132",realm="example.com",integrity-protected="auth-done",uri="sip:example.com",nonce="",response="". . ``` 2 Kamailio receives it and performs a reginfo subscribe on contact header ($ct) for my obscure needs: ``` reginfo_subscribe("$ct"); ``` 3 Kamailio crashes With the following backtrace: ``` Program terminated with signal 11, Segmentation fault. #0 0xb65374c0 in get_hash1_raw () at ../../hashes.h:109 109 hash_update_str(s, s+len, p, v, h); (gdb) backtrace #0 0xb65374c0 in get_hash1_raw () at ../../hashes.h:109 #1 0xb6542ba1 in db_postgres_replace () from /usr/local/lib/kamailio/modules/db_postgres.so #2 0xad30819c in convert_temporary_dialog_puadb () from /usr/local/lib/kamailio/modules/pua.so #3 0xad32c7bc in subs_cback_func () from /usr/local/lib/kamailio/modules/pua.so #4 0xadab8fa4 in run_trans_callbacks_internal () from /usr/local/lib/kamailio/modules/tm.so #5 0xadab90b5 in run_trans_callbacks () from /usr/local/lib/kamailio/modules/tm.so #6 0xadb11ec5 in local_reply () from /usr/local/lib/kamailio/modules/tm.so #7 0xadb14205 in reply_received () from /usr/local/lib/kamailio/modules/tm.so #8 0x080d1455 in do_forward_reply () #9 0x080d2ba5 in forward_reply () #10 0x0814ca62 in receive_msg () #11 0x08248d27 in udp_rcv_loop () #12 0x080eb1ee in main_loop () #13 0x080f19dc in main () ``` Here is the PUA module configuration: ``` #!ifdef WITH_PUA modparam("pua", "db_url" , DBURL ) modparam("pua", "db_mode" , 2 ) modparam("pua", "db_table" , "pua" ) modparam("pua", "min_expires" , 0 ) modparam("pua", "default_expires" , 3600 ) modparam("pua", "update_period" , 100 ) modparam("pua", "check_remote_contact", 0 ) modparam("pua", "hash_size" , 9 ) #!ifdef WITH_PUA_REGINFO modparam("pua_reginfo", "default_domain" , "SERVER_DOMAIN" ) modparam("pua_reginfo", "publish_reginfo", 1 ) modparam("pua_reginfo", "server_address" , "sip:reginfo@SERVER_INT_IP:SERVER_INT_PORT" ) #!endif #!ifdef WITH_PUA_USRLOC modparam("pua_usrloc" , "default_domain" , "SERVER_DOMAIN") #!endif ``` I will try with MySQL to see if I get the same results (if issue is related to DBMS). --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/377

2 13

[kamailio] Allow sipcapture callid_aleg_header to accept a list of headers (#388)
by Giacomo Vacca 02 Nov '15

02 Nov '15

Headers must be separated by ';', and first match wins (so order in the list is important). With this patch Homer's sipcapture can correlate A-leg and B-leg even when applications in the network use different custom headers to communicate on B-leg what A-leg's Call ID is. No changes are needed on DB schema or homer API. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/388 -- Commit Summary -- * Accept a list of headers for callid_aleg_header * Update sipcapture README xml with callid_aleg_header description * Update sipcapture README with callid_aleg_header description -- File Changes -- M modules/sipcapture/README (17) M modules/sipcapture/doc/sipcapture_admin.xml (20) M modules/sipcapture/sipcapture.c (75) -- Patch Links -- https://github.com/kamailio/kamailio/pull/388.patch https://github.com/kamailio/kamailio/pull/388.diff --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/388

3 3

git:master:81d35862: Merge pull request #386 from kamailio/lazedo/patch-1
by lazedo 28 Oct '15

28 Oct '15

Module: kamailio Branch: master Commit: 81d358623fb18e0a14a25eed6fde81a8a419aee9 URL: https://github.com/kamailio/kamailio/commit/81d358623fb18e0a14a25eed6fde81a… Author: lazedo <luis.azedo(a)factorlusitano.com> Committer: lazedo <luis.azedo(a)factorlusitano.com> Date: 2015-10-28T17:28:55Z Merge pull request #386 from kamailio/lazedo/patch-1 kazoo: change presence idle to available --- Modified: modules/kazoo/kz_pua.c --- Diff: https://github.com/kamailio/kamailio/commit/81d358623fb18e0a14a25eed6fde81a… Patch: https://github.com/kamailio/kamailio/commit/81d358623fb18e0a14a25eed6fde81a… --- diff --git a/modules/kazoo/kz_pua.c b/modules/kazoo/kz_pua.c index e75cad3..b1f785f 100644 --- a/modules/kazoo/kz_pua.c +++ b/modules/kazoo/kz_pua.c @@ -170,7 +170,7 @@ int kz_pua_publish_presence_to_presentity(struct json_object *json_obj) { str event = str_init("presence"); str presence_body = { 0, 0 }; str activity = str_init(""); - str note = str_init("Idle"); + str note = str_init("Available"); str status = str_presence_status_online; int expires = 0; @@ -217,9 +217,9 @@ int kz_pua_publish_presence_to_presentity(struct json_object *json_obj) { note = str_presence_note_offline; status = str_presence_status_offline; - } else { - note = str_presence_note_idle; - } + }; // else { + // note = str_presence_note_idle; +// } sprintf(body, PRESENCE_BODY, from_user.s, callid.s, status.s, note.s, activity.s, note.s);

1 0

[kamailio] kazoo: change presence idle to available (#386)
by lazedo 28 Oct '15

28 Oct '15

You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/386 -- Commit Summary -- * kazoo: change presence idle to available -- File Changes -- M modules/kazoo/kz_pua.c (8) -- Patch Links -- https://github.com/kamailio/kamailio/pull/386.patch https://github.com/kamailio/kamailio/pull/386.diff --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/386

1 1

git:master:7fc2c92e: kazoo: change presence idle to available
by lazedo 28 Oct '15

28 Oct '15

Module: kamailio Branch: master Commit: 7fc2c92e2fd8a9122440c073ba446940496ca480 URL: https://github.com/kamailio/kamailio/commit/7fc2c92e2fd8a9122440c073ba44694… Author: lazedo <luis(a)2600hz.com> Committer: lazedo <luis(a)2600hz.com> Date: 2015-10-28T16:54:54Z kazoo: change presence idle to available --- Modified: modules/kazoo/kz_pua.c --- Diff: https://github.com/kamailio/kamailio/commit/7fc2c92e2fd8a9122440c073ba44694… Patch: https://github.com/kamailio/kamailio/commit/7fc2c92e2fd8a9122440c073ba44694… --- diff --git a/modules/kazoo/kz_pua.c b/modules/kazoo/kz_pua.c index e75cad3..b1f785f 100644 --- a/modules/kazoo/kz_pua.c +++ b/modules/kazoo/kz_pua.c @@ -170,7 +170,7 @@ int kz_pua_publish_presence_to_presentity(struct json_object *json_obj) { str event = str_init("presence"); str presence_body = { 0, 0 }; str activity = str_init(""); - str note = str_init("Idle"); + str note = str_init("Available"); str status = str_presence_status_online; int expires = 0; @@ -217,9 +217,9 @@ int kz_pua_publish_presence_to_presentity(struct json_object *json_obj) { note = str_presence_note_offline; status = str_presence_status_offline; - } else { - note = str_presence_note_idle; - } + }; // else { + // note = str_presence_note_idle; +// } sprintf(body, PRESENCE_BODY, from_user.s, callid.s, status.s, note.s, activity.s, note.s);

1 0

CAC module idea
by Guillaume 28 Oct '15

28 Oct '15

Hi, I was thinking about doing a Call Admission Control module. It will allow the admin to setup limits in order to improve the global quality and to prevent overload of the service. It would have these criteria for admitting or not a call (you can propose other criteria): * Number of call attempt per second * Maximal number of concurrent sessions * CPU limit * RAM limit * Maximal bandwidth * Call priority header For now I haven't seen a module for that. And the dialog module could be useful for to implement the criteria that needs to know the number of call still active. It doesn't seem to be a too heavy task and it seems useful. What do you think about it? Guillaume

3 3

[kamailio] mem/q_malloc: log more diagnostic information in qm_debug_frag (#361)
by Alex Dowad 28 Oct '15

28 Oct '15

I had an instance of SER crash in production with this error message from qm_debug_frag: [mem/q_malloc.c:149]: BUG: qm_*: fragm. 0x4cee3b88 (address 0x4cee3ba0) end overwritten(0, 0)! The fragment end was been overwritten with zeroes... buffer overflow? Or an aliasing bug? Maybe a double-free? It would be much easier to debug problems like this if qm_debug_frag printed the call site where qm_malloc/free was invoked from. And now it does! You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/361 -- Commit Summary -- * mem/q_malloc: log more diagnostic information in qm_debug_frag -- File Changes -- M mem/q_malloc.c (33) -- Patch Links -- https://github.com/kamailio/kamailio/pull/361.patch https://github.com/kamailio/kamailio/pull/361.diff --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/361

2 7

git:master:7c9a8794: mem/q_malloc: more details in the logs from qm_debug_frag()
by Daniel-Constantin Mierla 28 Oct '15

28 Oct '15

Module: kamailio Branch: master Commit: 7c9a87948d9db5be511e94877c1eb3cdc411622c URL: https://github.com/kamailio/kamailio/commit/7c9a87948d9db5be511e94877c1eb3c… Author: Alex Dowad <alexinbeijing(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2015-10-28T14:18:59+01:00 mem/q_malloc: more details in the logs from qm_debug_frag() - print file and line from where the memory operation was triggered - makes it easier to troubleshoot and find the location in the code --- Modified: mem/q_malloc.c --- Diff: https://github.com/kamailio/kamailio/commit/7c9a87948d9db5be511e94877c1eb3c… Patch: https://github.com/kamailio/kamailio/commit/7c9a87948d9db5be511e94877c1eb3c… --- diff --git a/mem/q_malloc.c b/mem/q_malloc.c index 0c23639..46b0c3a 100644 --- a/mem/q_malloc.c +++ b/mem/q_malloc.c @@ -112,32 +112,37 @@ inline static unsigned long big_hash_idx(unsigned long s) #define END_CHECK_PATTERN2 0xabcdefed -static void qm_debug_frag(struct qm_block* qm, struct qm_frag* f) +static void qm_debug_frag(struct qm_block* qm, struct qm_frag* f, + const char* file, unsigned int line) { if (f->check!=ST_CHECK_PATTERN){ LOG(L_CRIT, "BUG: qm_*: fragm. %p (address %p) " - "beginning overwritten(%lx)!\n", + "beginning overwritten (%lx)! Memory allocator was called " + "from %s:%u. Fragment marked by %s:%lu.\n", f, (char*)f+sizeof(struct qm_frag), - f->check); + f->check, file, line, f->file, f->line); qm_status(qm); abort(); }; if ((FRAG_END(f)->check1!=END_CHECK_PATTERN1)|| (FRAG_END(f)->check2!=END_CHECK_PATTERN2)){ - LOG(L_CRIT, "BUG: qm_*: fragm. %p (address %p)" - " end overwritten(%lx, %lx)!\n", + LOG(L_CRIT, "BUG: qm_*: fragm. %p (address %p) " + "end overwritten (%lx, %lx)! Memory allocator was called " + "from %s:%u. Fragment marked by %s:%lu.\n", f, (char*)f+sizeof(struct qm_frag), - FRAG_END(f)->check1, FRAG_END(f)->check2); + FRAG_END(f)->check1, FRAG_END(f)->check2, + file, line, f->file, f->line); qm_status(qm); abort(); } if ((f>qm->first_frag)&& ((PREV_FRAG_END(f)->check1!=END_CHECK_PATTERN1) || (PREV_FRAG_END(f)->check2!=END_CHECK_PATTERN2) ) ){ - LOG(L_CRIT, "BUG: qm_*: prev. fragm. tail overwritten(%lx, %lx)[%p:%p]!" - "\n", + LOG(L_CRIT, "BUG: qm_*: prev. fragm. tail overwritten(%lx, %lx)[%p:%p]! " + "Memory allocator was called from %s:%u. Fragment marked by " + "%s:%lu.\n", PREV_FRAG_END(f)->check1, PREV_FRAG_END(f)->check2, f, - (char*)f+sizeof(struct qm_frag)); + (char*)f+sizeof(struct qm_frag), file, line, f->file, f->line); qm_status(qm); abort(); } @@ -370,7 +375,7 @@ void* qm_malloc(void* qmp, unsigned long size) /* we found it!*/ /*detach it from the free list*/ #ifdef DBG_QM_MALLOC - qm_debug_frag(qm, f); + qm_debug_frag(qm, f, file, line); #endif qm_detach_free(qm, f); /*mark it as "busy"*/ @@ -453,7 +458,7 @@ void qm_free(void* qmp, void* p) f=(struct qm_frag*) ((char*)p-sizeof(struct qm_frag)); #ifdef DBG_QM_MALLOC - qm_debug_frag(qm, f); + qm_debug_frag(qm, f, file, line); if (f->u.is_free){ LOG(L_CRIT, "BUG: qm_free: freeing already freed pointer (%p)," " called from %s: %s(%d), first free %s: %s(%ld) - aborting\n", @@ -487,7 +492,7 @@ void qm_free(void* qmp, void* p) if (((char*)next < (char*)qm->last_frag_end) && (next->u.is_free)){ /* join next packet */ #ifdef DBG_QM_MALLOC - qm_debug_frag(qm, next); + qm_debug_frag(qm, next, file, line); #endif qm_detach_free(qm, next); size+=next->size+FRAG_OVERHEAD; @@ -503,7 +508,7 @@ void qm_free(void* qmp, void* p) if (prev->u.is_free){ /* join prev packet */ #ifdef DBG_QM_MALLOC - qm_debug_frag(qm, prev); + qm_debug_frag(qm, prev, file, line); #endif qm_detach_free(qm, prev); size+=prev->size+FRAG_OVERHEAD; @@ -575,7 +580,7 @@ void* qm_realloc(void* qmp, void* p, unsigned long size) #endif f=(struct qm_frag*) ((char*)p-sizeof(struct qm_frag)); #ifdef DBG_QM_MALLOC - qm_debug_frag(qm, f); + qm_debug_frag(qm, f, file, line); MDBG("qm_realloc: realloc'ing frag %p alloc'ed from %s: %s(%ld)\n", f, f->file, f->func, f->line); if (f->u.is_free){

1 0

[kamailio] permissions: time period in rules and trailing space removing (#384)
by Tetram100 28 Oct '15

28 Oct '15

Possibility to specify a time period following the RFC 2445 (explained in the TMREC module readme) at the end of a rule in the allow and deny files. The rule will be valid only during this period. Usefull for company or people that don't want calls during night or want to receive calls from someone only during a specific period of time. It was already possible with the TMREC module in a routing script but this was redundant with the permission module so it simplifies the conf. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/384 -- Commit Summary -- * permissions: possibility to specify time period in routing rules * permissions: remove bad trailing space -- File Changes -- M modules/permissions/Makefile (3) M modules/permissions/README (34) M modules/permissions/address.c (8) M modules/permissions/address.h (10) M modules/permissions/config/permissions.allow (16) M modules/permissions/config/permissions.deny (16) M modules/permissions/doc/permissions.xml (13) M modules/permissions/doc/permissions_admin.xml (184) M modules/permissions/hash.c (74) M modules/permissions/hash.h (48) M modules/permissions/mi.c (18) M modules/permissions/mi.h (4) M modules/permissions/parse_config.c (117) M modules/permissions/parse_config.h (6) M modules/permissions/permissions.c (26) M modules/permissions/permissions.h (6) M modules/permissions/rule.c (101) M modules/permissions/rule.h (13) M modules/permissions/trusted.c (44) M modules/permissions/trusted.h (6) -- Patch Links -- https://github.com/kamailio/kamailio/pull/384.patch https://github.com/kamailio/kamailio/pull/384.diff --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/384

1 1

[kamailio] permissions: possibility to specify time period in routing rules, fun… (#382)
by Tetram100 28 Oct '15

28 Oct '15

…ction to generate simple call logs * Possibility to specify a time period following the RFC 2445 (explained in the TMREC module readme) at the end of a rule in the allow and deny files. The rule will be valid only during this period. Usefull for company or people that don't want calls during night or want to receive calls from someone only during a specific period of time. It was already possible with the TMREC module in a routing script but this was redundant with the permission module so it simplifies the conf. * New function log_attempt that can be use in the routing part. Usefull to log in a specific file the calls that have been prevented to do security inspection after. Was surely possible with a script in the routing part but it simplifies also the conf. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/382 -- Commit Summary -- * permissions: possibility to specify time period in routing rules, function to generate simple call logs -- File Changes -- M modules/permissions/Makefile (3) M modules/permissions/README (34) M modules/permissions/config/permissions.allow (16) M modules/permissions/config/permissions.deny (16) M modules/permissions/doc/permissions.xml (13) M modules/permissions/doc/permissions_admin.xml (210) M modules/permissions/parse_config.c (117) M modules/permissions/parse_config.h (7) M modules/permissions/permissions.c (110) M modules/permissions/rule.c (101) M modules/permissions/rule.h (13) -- Patch Links -- https://github.com/kamailio/kamailio/pull/382.patch https://github.com/kamailio/kamailio/pull/382.diff --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/382

2 3

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev October 2015