sr-dev May 2023

sr-dev@lists.kamailio.org

16 participants
319 discussions

[kamailio/kamailio] pua_usrloc doesn't send PUBLISH requests when a AOR has been removed by usrloc keepalive timeout (Issue #3273)

by admin-toneca

Hello, module pua_usrloc doesn't send PUBLISH when AOR has been removed by nathelper or usrloc keepalive timeout. modparam("usrloc", "timer_interval", 30) modparam("usrloc", "timer_procs", 1) modparam("usrloc", "use_domain", MULTIDOMAIN) /* enable DB persistency for location entries */ #!ifdef WITH_USRLOCDB modparam("usrloc", "db_url", DBURL_USRLOC) modparam("usrloc", "db_mode", 1) #!endif modparam("usrloc", "ka_mode", 1) modparam("usrloc", "ka_from", KEEPALIVE_FROM) modparam("usrloc", "ka_timeout", 120) modparam("presence", "db_url", FSDBURL) modparam("presence", "presentity_table", "sbc_presentity") modparam("presence", "active_watchers_table", "sbc_active_watchers") modparam("presence", "watchers_table", "sbc_watchers") modparam("presence_xml", "db_url", FSDBURL) modparam("presence_xml", "force_active", 1) modparam("presence_xml", "disable_bla", 0) modparam("presence_dialoginfo", "force_dummy_dialog", 1) modparam("presence_dialoginfo", "force_single_dialog", 1) modparam("pua", "db_url", FSDBURL) modparam("pua", "db_table", "sbc_pua") modparam("pua_usrloc", "default_domain", HOSTNAME) modparam("pua_dialoginfo", "include_callid", 0) modparam("pua_dialoginfo", "include_tags", 0) modparam("pua_dialoginfo", "include_localremote", 0) ### Additional Information ``` version: kamailio 5.6.2 (x86_64/linux) 54a9c1 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED 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: 54a9c1 compiled on 15:40:44 Nov 1 2022 with gcc 9.4.0 ``` * **Operating System**: ``` No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.5 LTS Release: 20.04 Codename: focal ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3273 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3273(a)github.com>

5 months

[kamailio/kamailio] No CDR is written on failover (Issue #3254)

by Earn330

Hi, I think there is an issue with writing CDRs on failover scenarios. I have two servers with Kamailio. Both server running Debian 11 (bulleye) and latest Kamailio 5.6.1 from git. I'm using DMQ to sync dialogs and htable between these servers, so both servers have the same knowledge of dialog state. Both Kamailio uses nobind option, so I can switch a VIP from one server to the other one. This is managed with keepalived. Switching the VIP from one server the other one works fine an while a call is running I can switch the VIP. I can see that the BYE Message is handled OK after I made a switch. I can see that acc is triggered but what is missing is acc_cdr in this case. I'm using htable to fill all necessary variables to complete the CDR an I can see that all values are synced correctly. The acc_cdr is created fine if there is no failover so i think it can't be an configuration issue. Both server holds the same Kamailio configuration except the IP. `version: kamailio 5.6.1 (x86_64/linux) bfc5c2-dirty 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED 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: bfc5c2 -dirty compiled with gcc 10.2.1` `root@voip-lab-proxy01:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye` `root@voip-lab-proxy01:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 38 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 23 Model name: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz Stepping: 10 CPU MHz: 2500.088 BogoMIPS: 5000.17 Virtualization: VT-x Hypervisor vendor: KVM Virtualization type: full L1d cache: 128 KiB L1i cache: 128 KiB L2 cache: 16 MiB L3 cache: 16 MiB NUMA node0 CPU(s): 0-3 Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Mitigation; PTE Inversion; VMX EPT disabled Vulnerability Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown Vulnerability Meltdown: Mitigation; PTI Vulnerability Mmio stale data: Unknown: No mitigations Vulnerability Retbleed: Not affected Vulnerability Spec store bypass: Vulnerable Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx pdpe1gb lm constant_tsc arch_perfmon rep_good nopl xtopology cpuid tsc_known_freq pni vmx ssse3 cx16 pdcm sse4_1 x2apic tsc_deadline_timer xsave hypervisor lahf_lm cpuid_fault pti tpr_shadow vnmi flexpriority vpid tsc_adjust arat arch_capabilit ies` If you need more information, please let me know. As I'm running this on a test system I can reproduce the issue at any time. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3254 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3254(a)github.com>

5 months

[kamailio/kamailio] packaging: cannot merge config files on system with ostree (Issue #3252)

by sergey-safarov

On Fedora Core when installed Kamailio and then installed additional packages then receive error ``` [root@caloes-1 ~]# journalctl -flu ostree-boot-complete.service -o cat Starting ostree-boot-complete.service - OSTree Complete Boot... error: ostree-finalize-staged.service failed on previous boot: During /etc merge: Modified config file newly defaults to directory 'kamailio', cannot merge ostree-boot-complete.service: Main process exited, code=exited, status=1/FAILURE ostree-boot-complete.service: Failed with result 'exit-code'. Failed to start ostree-boot-complete.service - OSTree Complete Boot. ostree-boot-complete.service - OSTree Complete Boot was skipped because all trigger condition checks failed. ostree-boot-complete.service - OSTree Complete Boot was skipped because all trigger condition checks failed. ostree-boot-complete.service - OSTree Complete Boot was skipped because all trigger condition checks failed. ``` Suggestion place default Kamailio config into dedicated package "kamailio-config-default". -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3252 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3252(a)github.com>

5 months

[kamailio/kamailio] PUBLISH presence terminated state results in NOTIFY confirmed or early (Issue #3229)

by Duncan Palmer

### Description I established a call between two extensions using TLS, and the presence state was replicated between two Kamailio servers using presence_dmq (no database backing). This all worked correctly except when it comes to sending a PUBLISH with a state terminated in the body, the presence_dmq sent the serialized data correctly, but the Kamailio server sends the wrong state and the caller is marked as busy on all subscribed phones until Kamailio is restarted. This occurs on version 5.6.1. In order generate this data, we use a separate script which responds to Asterisk events and sends the right PUBLISH at the right time to Kamailio, eg. if it sees a Hangup event, it sends a PUBLISH with the state in the body set to 'terminated' and the Expires: header set to 0. This appears to prompt Kamailio to send a NOTIFY with a state of early or confirmed to all subscribers. ### Troubleshooting #### Reproduction Install two Kamailio servers running Kamailio 5.6.1. I am using this installation command: `sudo apt install kamailio=5.6.1+bpo9 kamailio-dbg=5.6.1+bpo9 kamailio-lua-modules=5.6.1+bpo9 kamailio-memcached-modules=5.6.1+bpo9 kamailio-mysql-modules=5.6.1+bpo9 kamailio-presence-modules=5.6.1+bpo9 kamailio-redis-modules=5.6.1+bpo9 kamailio-tls-modules=5.6.1+bpo9 kamailio-utils-modules=5.6.1+bpo9` Some configuration detail for /etc/kamailio/kamailio.cfg: listen=tls:172.22.0.155:5061 # This ensures we have a UDP socket for sending HEP datagrams (we also send the plaintext UDP PUBLISH here) listen=udp:172.22.0.155:9060 port=5061 enable_tls=yes tcp_connection_lifetime=3605 #modules (this is not an exhaustive list) loadmodule "dmq.so" loadmodule "dialog.so" loadmodule "presence.so" loadmodule "presence_xml.so" loadmodule "presence_dialoginfo.so" loadmodule "pua.so" loadmodule "pua_dialoginfo.so" loadmodule "tls.so" modparam("dmq", "server_address", "sip:172.22.0.155:9060") modparam("dmq", "notification_address", "sip:172.22.1.124:9060") modparam("dialog", "db_url", DBURL) modparam("dialog", "enable_stats", 1) modparam("dialog", "db_mode", 0) # 0 - NO_DB - the memory content is not flushed into DB modparam("dialog", "dlg_flag", 9) modparam("dialog", "enable_dmq", 1) modparam("pua", "db_url", DBURL) modparam("pua", "db_mode", 0) # high speed memory based storage modparam("pua", "outbound_proxy", "sips:172.22.0.155:5061;transport=tls") modparam("pua_dialoginfo", "include_localremote", 0) modparam("presence", "db_url", DBURL) modparam("presence", "server_address", "sips:this.host.example.org:5061;transport=tls") modparam("presence", "db_table_lock_type", 0) modparam("presence", "subs_db_mode", 0) # 0 - This disables database completely. modparam("presence", "enable_dmq", 1) modparam("presence", "publ_cache", 2) modparam("presence", "subs_remove_match", 1) modparam("presence", "timeout_rm_subs", 0) modparam("presence_dialoginfo", "force_dummy_dialog", 1) modparam("presence_dialoginfo", "force_single_dialog", 1) modparam("presence_xml", "force_active", 1) modparam("presence_xml", "force_presence_single_body", 1) #### Log Messages These log aren't directly linked but Kamailio reports a 200 OK in response to the PUBLISH, but the NOTIFY to the handset is _not_ terminated. Difficult to capture this because of TLS. ``` Aug 26 13:32:26 this.host.example.org /usr/sbin/kamailio[4187]: DEBUG: presence [presence_dmq.c:467]: pres_dmq_replicate_presentity(): sending serialized data {"action":1,"presentity":{"domain":"sip.prod.example.org","user":"XXXX469","etag":"a.1661495738.4187.2612.0","expires":3600,"recv":1661520746,"event":"dialog"},"t_new":1,"cur_etag":"","ruid":"pres-630869ce-105b-43a","body":"<?xml version=\"1.0\"?>\n<dialog-info xmlns=\"urn:ietf:params:xml:ns:dialog-info\" version=\"0\" state=\"full\" entity=\"sip:XXXX469@sip.prod.example.org\">\n<dialog id=\"c95340dd-5266-450a-8c53-a5cd75c4bb67\" call-id=\"c95340dd-5266-450a-8c53-a5cd75c4bb67\" direction=\"recipient\">\n<state>confirmed</state>\n</dialog>\n</dialog-info>\n"} Aug 26 13:33:00 this.host.example.org /usr/sbin/kamailio[4187]: DEBUG: presence [presence_dmq.c:467]: pres_dmq_replicate_presentity(): sending serialized data {"action":1,"presentity":{"domain":"sip.prod.example.org","user":"XXXX469","etag":"a.1661495738.4187.2622.0","expires":0,"recv":1661520780,"event":"dialog"},"t_new":1,"cur_etag":"","ruid":"pres-630869ce-105b-e3a","body":"<?xml version=\"1.0\"?>\n<dialog-info xmlns=\"urn:ietf:params:xml:ns:dialog-info\" version=\"0\" state=\"full\" entity=\"sip:XXXX469@sip.prod.example.org\">\n<dialog id=\"c95340dd-5266-450a-8c53-a5cd75c4bb67\" call-id=\"c95340dd-5266-450a-8c53-a5cd75c4bb67\" direction=\"recipient\">\n<state>terminated</state>\n</dialog>\n</dialog-info>\n"} ``` This is a similar example: ``` Sep 1 12:37:14 this.host.example.org /usr/sbin/kamailio[5176]: INFO: presence [notify.c:1738]: send_notify_request(): NOTIFY sip:XXXX475@sip.prod.example.org via ÿÿÿÿÿÿÿÿ on behalf of sip:XXXX472@sip.prod.example.org for event dialog : 2_2191795053(a)172.31.29.18 Sep 1 12:37:14 this.host.example.org /usr/sbin/kamailio[5176]: DEBUG: presence [presence_dmq.c:400]: pres_dmq_replicate_presentity(): replicating presentity record - old etag a.1662035772.5176.17.0, new etag , ruid pres-6310a741-1438-11 Sep 1 12:37:14 this.host.example.org /usr/sbin/kamailio[5176]: DEBUG: presence [presence_dmq.c:467]: pres_dmq_replicate_presentity(): sending serialized data {"action":1,"presentity":{"domain":"sip.prod.example.org","user":"XXXX472","etag":"a.1662035772.5176.17.0","expires":0,"recv":1662035834,"event":"dialog"},"t_new":1,"cur_etag":"","ruid":"pres-6310a741-1438-11","body":"<?xml version=\"1.0\"?>\n<dialog-info xmlns=\"urn:ietf:params:xml:ns:dialog-info\" version=\"0\" state=\"full\" entity=\"sip:XXXX472@sip.prod.example.org\">\n<dialog id=\"76024a0e-2d35-47d8-afd1-a1363acbf859\" call-id=\"76024a0e-2d35-47d8-afd1-a1363acbf859\" direction=\"recipient\">\n<state>terminated</state>\n</dialog>\n</dialog-info>\n"} Sep 1 12:37:14 this.host.example.org /usr/sbin/kamailio[5176]: DEBUG: presence [presence_dmq.c:149]: pres_dmq_send(): sending dmq broadcast... ``` #### SIP Traffic ``` PUBLISH sip:XXXX469@sip.prod.example.org SIP/2.0 Via: SIP/2.0/UDP this.host.example.org;branch=656ebca4-5e71-4082-984a-7efa54bdd2cc To: sip:XXXX469@sip.prod.example.org From: sip:XXXX469@sip.prod.example.org;tag=a06f8d92-609b-4210-a1f0-f7042b871f07 CSeq: 12 PUBLISH Call-ID: d67c8bb5-f507-4ada-8f98-d7caa6d86721(a)this.host.example.org Content-Length: 323 User-Agent: Astertisk-Event-Bridge Max-Forwards: 70 Event: dialog Expires: 0 Content-Type: application/dialog-info+xml <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:XXXX469@sip.prod.example.org"> <dialog id="9fa5bf3c-63f3-4d3f-82c5-cdff374c4e13" call-id="9fa5bf3c-63f3-4d3f-82c5-cdff374c4e13" direction="recipient"> <state>terminated</state> </dialog> </dialog-info> ``` ### Possible Solutions Downgrading to Kamailio version 5.5.4 resolves this problem. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` $ kamailio -v version: kamailio 5.6.1 (x86_64/linux) 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED 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: unknown compiled with gcc 6.3.0 $ dpkg -l | egrep '^ii' | grep kamailio | awk '{ print $2, $3 }' kamailio 5.6.1+bpo9 kamailio-dbg:amd64 5.6.1+bpo9 kamailio-lua-modules:amd64 5.6.1+bpo9 kamailio-memcached-modules:amd64 5.6.1+bpo9 kamailio-mysql-modules:amd64 5.6.1+bpo9 kamailio-presence-modules:amd64 5.6.1+bpo9 kamailio-redis-modules:amd64 5.6.1+bpo9 kamailio-tls-modules:amd64 5.6.1+bpo9 kamailio-utils-modules:amd64 5.6.1+bpo9 ``` * **Operating System**: ``` $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.2 (stretch) Release: 9.2 Codename: stretch $ uname -a Linux this.host.example.org 4.9.0-16-amd64 #1 SMP Debian 4.9.272-2 (2021-07-19) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3229 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3229(a)github.com>

5 months

[kamailio/kamailio] do not generate waring when used UDP protocol and no "Content-Length" header (Issue #3210)

by sergey-safarov

### Description According to [RFC3261](https://datatracker.ietf.org/doc/html/rfc3261#section-20.14) > The Content-Length header field indicates the size of the message- > body, in decimal number of octets, sent to the recipient. > Applications SHOULD use this field to indicate the size of the > message-body to be transferred, regardless of the media type of the > entity. If a stream-based protocol (such as TCP) is used as > transport, the header field MUST be used. When UDP protocol is used then this header is optional. When Kamailio receives an OPTIONS request like in the example, then it floods Kamailio logs with messages like ``` sanity [sanity.c:612]: check_cl(): content length header missing in request ``` OPTIONS message example ``` OPTIONS sip:sbc-0.example.com:5060 SIP/2.0 Via: SIP/2.0/UDP 64.58.61.151:5060;branch=z9hG4bKl7oo3f30a0som61aeu00 Call-ID: 49bc1fcac14b779958dad4b9c43954b400149n2(a)64.58.61.151 To: sip:ping@sbc-0.example.com From: <sip:ping@64.58.61.151>;tag=8fbe5af9178677655bc3a5388c2a8b8c00149n2 Max-Forwards: 70 CSeq: 299694 OPTIONS Route: <sip:3.236.25.4:5060;lr> ``` ### Expected behavior Do not generate warnings about SIP messages that are allowed according to RFC. #### Actual observed behavior Generated warning when "Content-Length" header missing and used UDP protocol. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3210 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3210(a)github.com>

5 months

[kamailio/kamailio] [stirshaken] copy identity header and forward (Issue #3214)

by Artiom Baloian

### Description I am using STIR/SHAKEN as a third party service and wanted to know if there is a function to copy the Identity header from the 302 response into the original INVITE and then forward it. The Contact header from the 302 will make Kamailio server forward the INVITE to the SBC. Ideally having one function which does everything in one place would be a nice feature to have. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3214 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3214(a)github.com>

5 months

[kamailio/kamailio] path & RFC5626: flow-token is not added if +sip.instance and reg-id are missing (Issue #3190)

by space88man

### Description If the INVITE contains `;ob` but no `;+sip.instance=xxxx;reg-id=N` then a flow-token is not added to the record-route header. This is contrary to RFC5626. #### Reproduction Configure 2 x kamailio according to module outbound; i.e 1 x edge proxy and 1 x internal proxy/registrar. UA1 and UA2 have already REGISTER'ed with `;+sip.instance=...;reg-id=...`. ``` UA1, UA2 --- edge proxy --- internal proxy ``` Send INVITE from UA1 to UA2 with `;ob` but no other params: ``` Contact: <sip:user1250@192.168.12.45:5063;transport=TLS;ob> Record-Route: <sip:127.0.0.1;r2=on;lr> Record-Route: <sip:192.168.13.50:5061;transport=tls;r2=on;lr> ``` Observe that there is no flow-token added. Send INVITE from UA1 to UA2 with `;ob` with `;+sip.instance=...;reg-id=...`: ``` Contact: <sip:user1200@192.168.122.15;transport=tls;ob>;+sip.instance="<urn:uuid:0000 `0000-0000-0000-0000-0012341234>";reg-id=7 Record-Route: <sip:Jz0HaDIr1ZoqEAPAqA0yE8XAqAwqyAo=@127.0.0.1;r2=on;lr> Record-Route: <sip:Jz0HaDIr1ZoqEAPAqA0yE8XAqAwqyAo=@192.168.13.50:5061;transport=tls;r2=on;lr> ``` Observe that there is a flow-token added. #### Debugging Data #### SIP Traffic ### Possible Solutions ### Additional Information Version; kamailio 5.6.0 #### RFC5626 Section 9.5 https://datatracker.ietf.org/doc/html/rfc5626#section-9.5 INVITE must contain `ob;` but does not need to contain `;+sip.instance=...;reg-id=...` ``` INVITE sip:alice@a.example SIP/2.0 From: Bob <sip:bob@example.com>;tag=ldw22z To: Alice <sip:alice@a.example> Call-ID: 95KGsk2V/Eis9LcpBYy3 CSeq: 1 INVITE Route: <sip:ep1.example.com;lr> Contact: <sip:bob@192.0.2.2;transport=tcp;ob> ``` EP1 adds a Record-Route with a flow-token in message #43. ``` Record-Route: <sip:3yJEbr1GYZK9cPYk5Snocez6DzO7w+AX@ep1.example.com;lr> ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3190 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3190(a)github.com>

5 months

[kamailio/kamailio] dialog module does not update callee tag until 2xx received (Issue #3155)

by patrickarton

### Description dialog module does not update callee tag until it receives a 2xx response to an INVITE. and so we can not use is_know_dlg() function for in-dialog request like UPDATE when the session is still in early state.  ### Troubleshooting #### Reproduction  #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` (paste your log messages here) ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` kamailio 5.5.4 ``` * **Operating System**:  ``` (paste your output here) ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3155 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3155(a)github.com>

5 months

[kamailio/kamailio] RPC command app_jsdt.reload does not reload "require()" files (Issue #3145)

by Vincent Handfield

### Description If the file loaded with the modparam "load" uses CommonJS modules (Issue #3037-PR #3038), the modules are not reloaded when issuing the command app_jsdt.reload. Only the "main" file is reloaded. #### Reproduction 1 - Start Kamailio with those files as the initial configuration ```generic # kamailio.cfg ## Only the part concerning app_jsdt is included. ## The rest of the config file is ommited for the sake of clarity loadmodule "app_jsdt.so" modparam("app_jsdt", "load", "/etc/kamailio/js/index.js") modparam("app_jsdt", "mode", 1) cfgengine "jsdt" ``` ```js // index.js var myModule = require('./myModule'); function ksr_request_route() { myModule.myFunction() KSR.log("info", "KSR.log called from the index.js file"); } ``` ```js // myModule.js exports.myFunction = function() { KSR.log("info", "KSR.log called from the myModule.js file" } ``` 2 - Modify the myModule.js file ```js // myModule.js exports.myFunction = function() { KSR.log("info", "KSR.log called from the MODIFIED myModule.js file" } ``` 3 - Run the reload command ```console foo@bar:~# kamcmd app_jsdt.reload { old: 0 new: 1 } ``` > Log file > > INFO: app_jsdt [app_jsdt_api.c:1557]: app_jsdt_rpc_reload(): marking for reload js script file: /etc/kamailio/js/index.js (0 => 0) > DEBUG: app_jsdt [app_jsdt_api.c:534]: jsdt_kemi_reload_script(): reloading js script file: /etc/kamailio/js/index.js (0 => 1) 4 - The log file still show those lines: > Log file > >INFO <core> [core/kemi.c:156]: sr_kemi_core_log(): KSR.log called from the myModule.js file >INFO <core> [core/kemi.c:156]: sr_kemi_core_log(): KSR.log called from the index.js file 5 - Modify the index.js file ```js // index.js var myModule = require('./myModule'); function ksr_request_route() { myModule.myFunction() KSR.log("info", "KSR.log called from the MODIFIED index.js file"); } ``` 6 - Run the reload command ```console foo@bar:~# kamcmd app_jsdt.reload { old: 1 new: 2 } ``` > Log file > > INFO: app_jsdt [app_jsdt_api.c:1557]: app_jsdt_rpc_reload(): marking for reload js script file: /etc/kamailio/js/index.js (0 => 1) > DEBUG: app_jsdt [app_jsdt_api.c:534]: jsdt_kemi_reload_script(): reloading js script file: /etc/kamailio/js/index.js (1 => 2) 7 - The log file now show those lines: > Log file > > INFO <core> [core/kemi.c:156]: sr_kemi_core_log(): KSR.log called from the myModule.js file > INFO <core> [core/kemi.c:156]: sr_kemi_core_log(): KSR.log called from the MODIFIED index.js file 8 - Restart kamailio completly 9 - The log file now show those lines: > Log file > > INFO <core> [core/kemi.c:156]: sr_kemi_core_log(): KSR.log called from the MODIFIED myModule.js file > INFO <core> [core/kemi.c:156]: sr_kemi_core_log(): KSR.log called from the MODIFIED index.js file ### Possible Solutions Sorry, I would really like to provide one, but, as I'm a new Kamailio user, I don't know all the internals yet. ### Additional Information * **Kamailio Version** ```console foo@bar:~# kamailio -v version: kamailio 5.6.0 (x86_64/linux) 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED 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: unknown compiled with gcc 10.2.1 ``` * **Operating System**: ```console foo@bar:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye foo@bar:~# uname -a Linux localhost 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3145 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3145(a)github.com>

5 months

[kamailio/kamailio] usrloc OPTIONS not tracing with HEP (Issue #3136)

by Luke Escudé

### Description OPTIONS keepalives sent by usrloc are not being traced with HEP/Homer ### Troubleshooting #### Reproduction Module setup: modparam("siptrace", "duplicate_uri","sip:HOMERIP:9060"); modparam("siptrace", "hep_mode_on",1); modparam("siptrace", "trace_to_database",0); modparam("siptrace", "trace_flag",22); modparam("siptrace", "trace_on", 1); modparam("siptrace", "hep_version", 3); modparam("siptrace", "trace_mode", 1) I believe the above setup should duplicate ALL packets to homer, which is working just fine, except for usrloc-generated OPTIONS. The 200 OK from endpoints is showing up just fine, just not the initial request. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3136 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3136(a)github.com>

5 months

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev May 2023