sr-dev December 2020

sr-dev@lists.kamailio.org

18 participants
205 discussions

git:master:7fa61a98: modules: readme files regenerated - dispatcher ... [skip ci]
by Kamailio Dev 10 Dec '20

10 Dec '20

Module: kamailio Branch: master Commit: 7fa61a98a52723ee6f990e9cc3aee252f23d433a URL: https://github.com/kamailio/kamailio/commit/7fa61a98a52723ee6f990e9cc3aee25… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2020-12-10T16:31:24+01:00 modules: readme files regenerated - dispatcher ... [skip ci] --- Modified: src/modules/dispatcher/README --- Diff: https://github.com/kamailio/kamailio/commit/7fa61a98a52723ee6f990e9cc3aee25… Patch: https://github.com/kamailio/kamailio/commit/7fa61a98a52723ee6f990e9cc3aee25… --- diff --git a/src/modules/dispatcher/README b/src/modules/dispatcher/README index 7db3838dec..27d35e78cc 100644 --- a/src/modules/dispatcher/README +++ b/src/modules/dispatcher/README @@ -1063,8 +1063,8 @@ modparam("dispatcher", "reload_delta", 1) (serial forking ordered by priority). + “9” - use weight based load distribution. You have to set the attribute 'weight' for each address (gateway) in destination - set. For more see the description of the 'weight' attribute in - the 'Special Attributes' section. + set. See also the description of the 'weight' attribute in the + 'Special Attributes' section. + “10” - use call load distribution. You have to set the attribute 'duid' (as an unique string id) per each address in destination set. Also, you must set the parameter @@ -1086,10 +1086,14 @@ modparam("dispatcher", "reload_delta", 1) active host rweights in destination group). The major difference from the weight distribution is the probability recalculation according to rweight value in case - of host enabling/disabling - For example, 100 calls in 3-hosts group with rweight params - 1/2/1 will be distributed as 25/50/25. After third host - failing distribution will be changed to 33/67/0. + of destinations being active or inactive. + For example, 100 calls in 3-destinations group with rweight + params 1/2/1 will be distributed as 25/50/25. If the third + destination becomes inactive, the distribution is changed to + 33/67/0. If the computation of percentage per destination is + not an exact integer number, the value is trucated and the + last destination is used to fill the remaining percentage till + 100. Using this algorithm, you can also enable congestion control by setting the attribute 'cc=1', when 'cc' is enabled the 'weight' attribute will also be used to control congestion @@ -1102,6 +1106,8 @@ modparam("dispatcher", "reload_delta", 1) above their congestion threshold(weight), the load distribution is instead done using the ratio of estimated congestion ms. + See also the description of the 'rweight' attribute in the + 'Special Attributes' section. + “12” - dispatch to all destination in setid at once (parallel forking). Note that the XAVPs are no longer set with the values of the destination records, no re-routing making sense @@ -1714,11 +1720,17 @@ kamctl rpc dispatcher.hash 4 bob server.com If set to 0, then no active call limit is used.> * 'weight' - used for weight based load distribution. It must be set to a positive integer value beteen 0 and 100. The value represents - the percent of calls to be sent to that gateways.> + the percent of calls to be sent to that gateways. The sum must not + exceed 100, otherwise the destinations whose weight added to the + sum go over 100 are ignored. If the sum is less than 100, then the + last destination is used to fill the missing percentage. See also + the description of the corresponding algorithm parameter for + ds_select_dst(). * 'rweight' - used for relative weight based load distribution. It must be set to a positive integer value between 1 and 100 (otherwise host will be excluded from relative weight distribution - type). + type). See also the description of the corresponding algorithm + parameter for ds_select_dst(). * 'socket' - used to set the sending socket for the gateway. It is used for sending the SIP traffic as well as OPTIONS keepalives. * 'sockname' - used to set by name the sending socket for the

1 0

git:master:db557150: dispacher: docs - more details about weight and rweight attributes
by Daniel-Constantin Mierla 10 Dec '20

10 Dec '20

Module: kamailio Branch: master Commit: db55715003cd9af5ef3d32b51b5246643eea10d1 URL: https://github.com/kamailio/kamailio/commit/db55715003cd9af5ef3d32b51b52466… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2020-12-10T16:25:49+01:00 dispacher: docs - more details about weight and rweight attributes - cross reference sections that have info about weight and rweight attributes --- Modified: src/modules/dispatcher/doc/dispatcher_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/db55715003cd9af5ef3d32b51b52466… Patch: https://github.com/kamailio/kamailio/commit/db55715003cd9af5ef3d32b51b52466… --- diff --git a/src/modules/dispatcher/doc/dispatcher_admin.xml b/src/modules/dispatcher/doc/dispatcher_admin.xml index 953c6b0b57..53eea613ce 100644 --- a/src/modules/dispatcher/doc/dispatcher_admin.xml +++ b/src/modules/dispatcher/doc/dispatcher_admin.xml @@ -1193,7 +1193,7 @@ modparam("dispatcher", "reload_delta", 1) <para> <quote>9</quote> - use weight based load distribution. You have to set the attribute 'weight' for each address (gateway) in - destination set. For more see the description of the 'weight' + destination set. See also the description of the 'weight' attribute in the 'Special Attributes' section. </para> </listitem> @@ -1232,12 +1232,15 @@ modparam("dispatcher", "reload_delta", 1) <para> The major difference from the weight distribution is the probability recalculation according to rweight value in case of - host enabling/disabling + destinations being active or inactive. </para> <para> - For example, 100 calls in 3-hosts group with rweight params 1/2/1 - will be distributed as 25/50/25. After third host failing - distribution will be changed to 33/67/0. + For example, 100 calls in 3-destinations group with rweight params 1/2/1 + will be distributed as 25/50/25. If the third destination becomes + inactive, the distribution is changed to 33/67/0. If the computation + of percentage per destination is not an exact integer number, the value + is trucated and the last destination is used to fill the remaining + percentage till 100. </para> <para> Using this algorithm, you can also enable congestion control by setting the @@ -1252,6 +1255,10 @@ modparam("dispatcher", "reload_delta", 1) If all the gateways in a set are above their congestion threshold(weight), the load distribution is instead done using the ratio of estimated congestion ms. </para> + <para> + See also the description of the 'rweight' attribute in the + 'Special Attributes' section. + </para> </listitem> <listitem> <para> @@ -2141,13 +2148,19 @@ kamctl rpc dispatcher.hash 4 bob server.com <listitem> <para>'weight' - used for weight based load distribution. It must be set to a positive integer value beteen 0 and 100. The value represents - the percent of calls to be sent to that gateways.></para> + the percent of calls to be sent to that gateways. The sum must not + exceed 100, otherwise the destinations whose weight added to the + sum go over 100 are ignored. If the sum is less than 100, then the + last destination is used to fill the missing percentage. See also + the description of the corresponding algorithm parameter for + ds_select_dst().</para> </listitem> <listitem> <para>'rweight' - used for relative weight based load distribution. It must be set to a positive integer value between 1 and 100 (otherwise host will be excluded from relative weight distribution - type).</para> + type). See also the description of the corresponding algorithm + parameter for ds_select_dst().</para> </listitem> <listitem> <para>'socket' - used to set the sending socket for the gateway. It is

1 0

[kamailio/kamailio] Microsoft Teams and Survivable Branch Appliance (SBA) (#2580)
by MarkMasiak 10 Dec '20

10 Dec '20

Support for Teams Survivable Branch Appliance Direct Routing Occasionally, a customer site using Direct Routing to connect to Microsoft Phone System may experience an internet outage. Assume that the customer site--called a branch--temporarily cannot connect to the Microsoft cloud through Direct Routing. However, the intranet inside the branch is still fully functional and users can connect to the Session Border Controller (SBC) that is providing PSTN connectivity. https://docs.microsoft.com/en-us/microsoftteams/direct-routing-survivable-b… -- -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2580

2 2

[kamailio/kamailio] Deadlocks after ungracefully terminated TLS connections (#2395)
by Laszlo 09 Dec '20

09 Dec '20

This bug report concerns a Kamailio instance that's functioning as an edge proxy, accepting requests from clients over TLS and forwarding them to internal components over UDP. I've observed occasional "deadlocks" that all take place after there were connectivity issues between Kamailio and one or more of the clients (logging messages such as "tcp_send failed", "handle_tcpconn_ev(): connect x failed", "tcp_read_data(): error reading: Connection reset by peer"). Environment: * Ubuntu 16.04 * Kamailio 5.2.7 (5.2.7+ubuntu16.04) Relevant config: ``` # for TLS clients socket_workers=10 listen=tls:wan.ip:TLS_PORT # to be able to forward incoming TCP requests to UDP destinations socket_workers=10 listen=udp:wan.ip:TLS_PORT # for RPC commands socket_workers=2 listen=tcp:127.0.0.1:HTTP_PORT ``` ## Reproduction After a lot of trial and error, I've found a way to somewhat reproducibly trigger the problem using sipp. It involves setting up a large amount of simultaneous calls dialing into the edge proxy using TLS, to a destination UA that will answer the call and keep it open for a few seconds, then using `ctrl-c` to suddenly quit sipp which will ungracefully terminate the TCP/TLS connections. It takes me a couple of iterations to trigger the problem, e.g repeat until Kamailio starts failing: * start sipp * terminate sipp with ctrl-c * (quickly) restart sipp * terminate sipp * etc The amount of simultaneous calls has to be sufficiently large. In my environment I'm unable to reproduce the problem at all with 10-20 calls, while 50 calls always triggers the problem after a couple of iterations. Example sipp commandline: `sipp -nd -sf caller.xml -d 2000 -r 50 -l 500 -m 5000 -max_socket 1000 -t ln -tls_cert cert.crt -tls_key key.key kamailio.edge.proxy:5061` ## Failure mode 1 In one of the failure modes, it appears that all available TCP/TLS workers are permanently bricked; sipp's calls will simply timeout and not trigger any dialplan handling. Interestingly, even though I have dedicated workers for TLS (SIP client) and TCP (RPC commands), and my reproduction scenario doesn't connect to the HTTP_PORT at all, this failure scenario bricks the TCP (RPC) listeners as well; any curl requests to it will simply timeout as well. Kamailio will hang for a while on (systemd) restart. ## Failure mode 2 In another failure mode, it looks like the TCP workers are unaffected but the UDP perform forwarding to UDP destinations are broken. Sipp's calls will enter Kamailio, but forwarding (`relay()`) to the next hop will timeout even though the destination is functioning just fine. Since this failure mode doesn't break RPC I was able to enable debug logging: ``` 2020-07-07T17:26:58.770411+02:00 kamailio[24056]: INFO: From Customer 2020-07-07T17:26:58.770697+02:00 kamailio[24056]: DEBUG: pv [pv_trans.c:590]: tr_eval_string(): i=0 j=2 2020-07-07T17:26:58.770971+02:00 kamailio[24056]: DEBUG: dispatcher [dispatch.c:2055]: ds_manage_routes(): set [4] 2020-07-07T17:26:58.771248+02:00 kamailio[24056]: DEBUG: dispatcher [dispatch.c:2161]: ds_manage_routes(): using alg [0] hash [250849449] 2020-07-07T17:26:58.771535+02:00 kamailio[24056]: DEBUG: dispatcher [dispatch.c:2205]: ds_manage_routes(): selected [0-4-0/1] <sip:wan.ip:8065> 2020-07-07T17:26:58.771817+02:00 kamailio[24056]: DEBUG: dispatcher [dispatch.c:2226]: ds_manage_routes(): using first entry [4/1] 2020-07-07T17:26:58.772090+02:00 kamailio[24056]: DEBUG: dispatcher [dispatch.c:2269]: ds_manage_routes(): using entry [4/0] 2020-07-07T17:26:58.772362+02:00 kamailio[24056]: DEBUG: dispatcher [dispatch.c:2016]: ds_select_dst_limit(): selected target destinations: 2 2020-07-07T17:26:58.773001+02:00 kamailio[24056]: DEBUG: pv [pv_core.c:2611]: pv_set_force_sock(): trying to set send-socket to [udp:wan.ip:5061] 2020-07-07T17:26:58.773353+02:00 kamailio[24056]: DEBUG: <core> [core/socket_info.c:559]: grep_sock_info(): checking if host==us: 13==13 && [wan.ip] == [wan.ip] 2020-07-07T17:26:58.773829+02:00 kamailio[24056]: DEBUG: <core> [core/socket_info.c:566]: grep_sock_info(): checking if port 5061 (advertise 0) matches port 5061 2020-07-07T17:26:58.774122+02:00 kamailio[24056]: NOTICE: Relaying (cid: 1-9151(a)sipp.ip). 2020-07-07T17:26:58.774417+02:00 kamailio[24056]: DEBUG: siputils [checks.c:120]: has_totag(): no totag 2020-07-07T17:26:58.774708+02:00 kamailio[24056]: DEBUG: tm [t_lookup.c:1344]: t_newtran(): msg (0x7f69d1cc4980) id=1265/24056 global id=1265/24056 T start=(nil) 2020-07-07T17:26:58.774989+02:00 kamailio[24056]: DEBUG: tm [t_lookup.c:499]: t_lookup_request(): start searching: hash=43232, isACK=0 2020-07-07T17:26:58.775315+02:00 kamailio[24056]: DEBUG: tm [t_lookup.c:457]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK-9151-1-1] 2020-07-07T17:26:58.775612+02:00 kamailio[24056]: DEBUG: tm [t_lookup.c:682]: t_lookup_request(): no transaction found 2020-07-07T17:26:58.775908+02:00 kamailio[24056]: DEBUG: <core> [core/md5utils.c:67]: MD5StringArray(): MD5 calculated: 0a5d4a8d13f9606523da9c4d193b2261 2020-07-07T17:26:58.776270+02:00 kamailio[24056]: DEBUG: <core> [core/dns_cache.c:3197]: dns_srv_sip_resolve(): (wan.ip, 0, 0), ip, ret=0 2020-07-07T17:26:58.776701+02:00 kamailio[24056]: DEBUG: <core> [core/msg_translator.c:1765]: check_boundaries(): no multi-part body 2020-07-07T17:26:58.777012+02:00 kamailio[24056]: DEBUG: <core> [core/msg_translator.c:2935]: create_via_hf(): id added: <;i=a701>, rcv proto=3 2020-07-07T17:26:58.777596+02:00 kamailio[24056]: DEBUG: tm [t_funcs.c:375]: t_relay_to(): new transaction forwarded 2020-07-07T17:26:58.777948+02:00 kamailio[24056]: DEBUG: <core> [core/receive.c:354]: receive_msg(): request-route executed in: 1927 usec 2020-07-07T17:26:58.778243+02:00 kamailio[24056]: DEBUG: <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) 2020-07-07T17:26:58.779265+02:00 kamailio[24056]: message repeated 5 times: [ DEBUG: <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil)] 2020-07-07T17:26:58.779431+02:00 kamailio[24056]: DEBUG: <core> [core/xavp.c:507]: xavp_destroy_list(): destroying xavp list (nil) 2020-07-07T17:26:58.779753+02:00 kamailio[24056]: DEBUG: <core> [core/receive.c:458]: receive_msg(): cleaning up 2020-07-07T17:27:00.705303+02:00 kamailio[24053]: DEBUG: tm [t_reply.c:1266]: t_should_relay_response(): ->>>>>>>>> T_code=0, new_code=408 2020-07-07T17:27:00.705917+02:00 kamailio[24053]: DEBUG: tm [t_lookup.c:1041]: t_check_msg(): msg (0x7f69b1017e80) id=1264/24056 global id=1264/24056 T start=0x7f69b10167c0 2020-07-07T17:27:00.706187+02:00 kamailio[24053]: DEBUG: tm [t_lookup.c:1116]: t_check_msg(): T (0x7f69b10167c0) already found for msg (0x7f69b1017e80)! 2020-07-07T17:27:00.706533+02:00 kamailio[24053]: DEBUG: tmx [t_var.c:539]: pv_get_tm_reply_code(): reply code is <408> 2020-07-07T17:27:00.706879+02:00 kamailio[24053]: DEBUG: tm [t_lookup.c:1041]: t_check_msg(): msg (0x7f69b1017e80) id=1264/24056 global id=1264/24056 T start=0x7f69b10167c0 2020-07-07T17:27:00.707198+02:00 kamailio[24053]: DEBUG: tm [t_lookup.c:1116]: t_check_msg(): T (0x7f69b10167c0) already found for msg (0x7f69b1017e80)! 2020-07-07T17:27:00.707522+02:00 kamailio[24053]: DEBUG: tmx [t_var.c:594]: pv_get_tm_reply_reason(): reply reason is [Request Timeout] { "DSC": "tcp receiver (tls:wan.ip:5061) child=0", "IDX": 14, "PID": 24056 }, { "DSC": "slow timer", "IDX": 11, "PID": 24053 }, ``` Kamailio will restart (systemd) normally and everything will function normally again afterwards. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2395

3 19

[kamailio/kamailio] htable + dmq: sht_rm_name does not replicate (#2573)
by marcinkowalczyk 09 Dec '20

09 Dec '20

### Description I'm using htable DMQ replication to relicate call details over kamailio nodes. I've noticed that htable items are not removed when sht_rm_name is called inside script ### Troubleshooting #### Reproduction put in script: ``` $sht(cidParam=>$ci::callee_socket) = $sas; sht_rm_name("cidParam", "sw", "$ci"); ``` make a call and see what gets replicated `ngrep -W byline -d any '"htname":"cidParam"' | grep action ` When htable item is removed from htable using CLI removal it's replicated `{"action":3,"htname":"cidParam","cname":"x","mode":0}. ` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.4.1 (x86_64/linux) 09fd6a flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 09fd6a compiled on 11:07:49 Sep 1 2020 with gcc 4.8.5 ``` * **Operating System**: CentOS7 ``` Linux 3.10.0-1127.18.2.el7.x86_64 #1 SMP Sun Jul 26 15:27:06 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2573

2 7

git:master:41040a04: core: tcp - log connection state and flags on debug message
by Daniel-Constantin Mierla 08 Dec '20

08 Dec '20

Module: kamailio Branch: master Commit: 41040a0420ee48f51901bf32e29526c8948ecea0 URL: https://github.com/kamailio/kamailio/commit/41040a0420ee48f51901bf32e29526c… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2020-12-08T13:07:44+01:00 core: tcp - log connection state and flags on debug message --- Modified: src/core/tcp_read.c --- Diff: https://github.com/kamailio/kamailio/commit/41040a0420ee48f51901bf32e29526c… Patch: https://github.com/kamailio/kamailio/commit/41040a0420ee48f51901bf32e29526c… --- diff --git a/src/core/tcp_read.c b/src/core/tcp_read.c index 13a21f6ddd..50853cc5b6 100644 --- a/src/core/tcp_read.c +++ b/src/core/tcp_read.c @@ -296,9 +296,11 @@ int tcp_read_data(int fd, struct tcp_connection *c, } }else if (unlikely((bytes_read==0) || (*flags & RD_CONN_FORCE_EOF))){ - LM_DBG("EOF on %p, FD %d, bytes %d, flags %x ([%s]:%u -> [%s]:%u)", - c, fd, bytes_read, *flags, ip_addr2a(&c->rcv.src_ip), - c->rcv.src_port, ip_addr2a(&c->rcv.dst_ip), c->rcv.dst_port); + LM_DBG("EOF on connection %p (state: %u, flags: %x) - FD %d," + " bytes %d, rd-flags %x ([%s]:%u -> [%s]:%u)", + c, c->state, c->flags, fd, bytes_read, *flags, + ip_addr2a(&c->rcv.src_ip), c->rcv.src_port, + ip_addr2a(&c->rcv.dst_ip), c->rcv.dst_port); c->state=S_CONN_EOF; *flags|=RD_CONN_EOF; tcp_emit_closed_event(c, TCP_CLOSED_EOF);

1 0

git:master:efb9c5f8: core: tcp - debug messages merged, print bytes read and flags
by Daniel-Constantin Mierla 08 Dec '20

08 Dec '20

Module: kamailio Branch: master Commit: efb9c5f83b37c316b848ae7b6dc829e2f8ca6275 URL: https://github.com/kamailio/kamailio/commit/efb9c5f83b37c316b848ae7b6dc829e… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2020-12-08T12:50:56+01:00 core: tcp - debug messages merged, print bytes read and flags --- Modified: src/core/tcp_read.c --- Diff: https://github.com/kamailio/kamailio/commit/efb9c5f83b37c316b848ae7b6dc829e… Patch: https://github.com/kamailio/kamailio/commit/efb9c5f83b37c316b848ae7b6dc829e… --- diff --git a/src/core/tcp_read.c b/src/core/tcp_read.c index 3ae21a71d9..13a21f6ddd 100644 --- a/src/core/tcp_read.c +++ b/src/core/tcp_read.c @@ -296,12 +296,12 @@ int tcp_read_data(int fd, struct tcp_connection *c, } }else if (unlikely((bytes_read==0) || (*flags & RD_CONN_FORCE_EOF))){ + LM_DBG("EOF on %p, FD %d, bytes %d, flags %x ([%s]:%u -> [%s]:%u)", + c, fd, bytes_read, *flags, ip_addr2a(&c->rcv.src_ip), + c->rcv.src_port, ip_addr2a(&c->rcv.dst_ip), c->rcv.dst_port); c->state=S_CONN_EOF; *flags|=RD_CONN_EOF; tcp_emit_closed_event(c, TCP_CLOSED_EOF); - LM_DBG("EOF on %p, FD %d ([%s]:%u ->", c, fd, - ip_addr2a(&c->rcv.src_ip), c->rcv.src_port); - LM_DBG("-> [%s]:%u)\n", ip_addr2a(&c->rcv.dst_ip), c->rcv.dst_port); }else{ if (unlikely(c->state==S_CONN_CONNECT || c->state==S_CONN_ACCEPT)){ TCP_STATS_ESTABLISHED(c->state);

1 0

git:master:d80ae5e8: htable: set the value for dmq replicate of rm with sw operation
by Daniel-Constantin Mierla 08 Dec '20

08 Dec '20

Module: kamailio Branch: master Commit: d80ae5e88edec8471ade209f9984bef488cbb06f URL: https://github.com/kamailio/kamailio/commit/d80ae5e88edec8471ade209f9984bef… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2020-12-08T11:32:16+01:00 htable: set the value for dmq replicate of rm with sw operation --- Modified: src/modules/htable/htable.c --- Diff: https://github.com/kamailio/kamailio/commit/d80ae5e88edec8471ade209f9984bef… Patch: https://github.com/kamailio/kamailio/commit/d80ae5e88edec8471ade209f9984bef… --- diff --git a/src/modules/htable/htable.c b/src/modules/htable/htable.c index d449839c2f..d05cf5227d 100644 --- a/src/modules/htable/htable.c +++ b/src/modules/htable/htable.c @@ -493,6 +493,7 @@ static int ht_rm_items(sip_msg_t* msg, str* hname, str* op, str *val, } return 1; } else if(strncmp(op->s, "sw", 2)==0) { + isval.s = *val; if (ht_dmq_replicate_action(HT_DMQ_RM_CELL_SW, &ht->name, NULL, AVP_VAL_STR, &isval, mkey)!=0) { LM_ERR("dmq relication failed (op %d)\n", mkey);

1 0

git:master:1a532a57: modules: readme files regenerated - rtpengine ... [skip ci]
by Kamailio Dev 07 Dec '20

07 Dec '20

Module: kamailio Branch: master Commit: 1a532a57f568da3e9c2f2d953b0d5d8336baab44 URL: https://github.com/kamailio/kamailio/commit/1a532a57f568da3e9c2f2d953b0d5d8… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2020-12-07T14:31:13+01:00 modules: readme files regenerated - rtpengine ... [skip ci] --- Modified: src/modules/rtpengine/README --- Diff: https://github.com/kamailio/kamailio/commit/1a532a57f568da3e9c2f2d953b0d5d8… Patch: https://github.com/kamailio/kamailio/commit/1a532a57f568da3e9c2f2d953b0d5d8…

1 0

[kamailio/kamailio] rtpengine: query rtt per call leg (#2576)
by Julien Chavanton 07 Dec '20

07 Dec '20

#### Type Of Change - [x] New feature (non-breaking change which adds new functionality) #### Checklist: - [x] Tested changes locally #### Description This modification is to provide access to the new exposed metrics. RTPengine is now keeping track of RTT per call leg https://github.com/sipwise/rtpengine/pull/1116 You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2576 -- Commit Summary -- * rtpengine: query rtt per call leg -- File Changes -- M src/modules/rtpengine/doc/rtpengine_admin.xml (185) M src/modules/rtpengine/rtpengine.c (17) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2576.patch https://github.com/kamailio/kamailio/pull/2576.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/2576

3 2

← Newer
1
...
14
15
16
17
18
19
20
21
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev December 2020