- sr-users - kamailio.org

Kamailio not responding after stress test
by Igor Olhovskiy 27 Jan '23

27 Jan '23

Hello, I'm continuing investigations on Kamailio and stress test. Got it again in the state where it's not accepting any new TCP/TLS connections (UDP still works though), but all looks good from lsof/netnstat part, like system is not reporting any zombie connections. Restart of Kamailio process helps This time I got output of kamctl trap Put it here: https://pastebin.com/iYrNZ8U9 kamailio --version 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 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 14:01:01 Oct 18 2022 with gcc 4.8.5 It's statically linked with tlsa pointing on openssl-1.1.1q Settings related to TLS are: fork=yes children=4 tcp_children=12 enable_tls=yes tcp_accept_no_cl=yes tcp_max_connections=63536 tls_max_connections=63536 tcp_accept_aliases=no tcp_async=yes tcp_connect_timeout=10 tcp_conn_wq_max=63536 tcp_crlf_ping=yes tcp_delayed_ack=yes tcp_fd_cache=yes tcp_keepalive=yes tcp_keepcnt=3 tcp_keepidle=30 tcp_keepintvl=10 tcp_linger2=30 tcp_rd_buf_size=80000 tcp_send_timeout=10 tcp_wq_blk_size=2100 tcp_wq_max=10485760 open_files_limit=63536 Can you please help to read gdb output and understand where I missed in config? Thanks in advance! -- Best regards, Ihor (Igor)

3 7

Kamailio 5.6 on AlmaLinux 8 TLS crash
by Ihor Olkhovskyi 27 Jan '23

27 Jan '23

Hello! Currently testing Kamailio on Almalinux 8 (stated to be RHEL 8 binary compatible) and got this while trying to get TLS working: /usr/sbin/kamailio[32858]: INFO: tls [tls_domain.c:347]: ksr_tls_fill_missing(): TLSc<default>: ca_list='(null)' /usr/sbin/kamailio[32858]: INFO: tls [tls_domain.c:354]: ksr_tls_fill_missing(): TLSc<default>: ca_path='(null)' /usr/sbin/kamailio[32858]: INFO: tls [tls_domain.c:361]: ksr_tls_fill_missing(): TLSc<default>: crl='(null)' /usr/sbin/kamailio[32858]: INFO: tls [tls_domain.c:365]: ksr_tls_fill_missing(): TLSc<default>: require_certificate=1 /usr/sbin/kamailio[32858]: INFO: tls [tls_domain.c:372]: ksr_tls_fill_missing(): TLSc<default>: cipher_list='(null)' /usr/sbin/kamailio[32858]: INFO: tls [tls_domain.c:379]: ksr_tls_fill_missing(): TLSc<default>: private_key='(null)' /usr/sbin/kamailio[32858]: INFO: tls [tls_domain.c:383]: ksr_tls_fill_missing(): TLSc<default>: verify_certificate=1 /usr/sbin/kamailio[32858]: INFO: tls [tls_domain.c:386]: ksr_tls_fill_missing(): TLSc<default>: verify_depth=9 /usr/sbin/kamailio[32858]: INFO: tls [tls_domain.c:389]: ksr_tls_fill_missing(): TLSc<default>: verify_client=0 /usr/sbin/kamailio[32858]: INFO: tls [tls_domain.c:736]: set_verification(): TLSc<default>: Server MUST present valid certificate /usr/sbin/kamailio[32862]: ERROR: rtpengine [rtpengine.c:3070]: send_rtpp_command(): can't send command "ping" to RTPEngine <udp: 127.0.0.1:19999> /usr/sbin/kamailio[32862]: ERROR: rtpengine [rtpengine.c:2919]: rtpp_test(): proxy did not respond to ping /usr/sbin/kamailio[32883]: INFO: snmpstats [snmpstats.c:519]: spawn_sysUpTime_child(): A snmpVersion parameter was not provided. Defaulting to 3 /usr/sbin/kamailio[32883]: ERROR: snmpstats [snmpstats.c:561]: spawn_sysUpTime_child(): snmpget failed to run. Did you supply the snmpstats module with a proper snmpgetPath parameter? The kamailioSIPServiceStartTime is defaulting to zero /usr/sbin/kamailio[32881]: INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) /usr/sbin/kamailio[32870]: CRITICAL: <core> [core/mem/q_malloc.c:145]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten(0, abcdefed)[0x7fe8375d3820:0x7fe8375d3858]! Memory allocator was called from tls: tls_init.c:293. Fragment marked by tls: tls_init.c:293. Exec from core/mem/q_malloc.c:391. /usr/sbin/kamailio[32870]: CRITICAL: <core> [core/mem/q_malloc.c:153]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten [0x7fe8375d3790:0x7fe8375d37c8] - fragment marked by tls: tls_init.c:293 systemd[1]: Started Process Core Dump (PID 32923/UID 0). systemd-coredump[32924]: Process 32870 (kamailio) of user 0 dumped core.#012#012Stack trace of thread 32870:#012#0 0x00007fe841786aff raise (libc.so.6)#012#1 0x00007fe841759ea5 abort (libc.so.6)#012#2 0x00000000006eec2f qm_debug_check_frag (kamailio)#012#3 0x00000000006f09a6 qm_malloc (kamailio)#012#4 0x00000000006fc930 qm_shm_malloc (kamailio)#012#5 0x00007fe83b5b9c31 ser_malloc (tls.so)#012#6 0x00007fe83fa4090d CRYPTO_zalloc (libcrypto.so.1.1)#012#7 0x00007fe8364b8163 sc_hash_type (libnetsnmp.so.35)#012#8 0x00007fe8364b49df hash_engineID (libnetsnmp.so.35)#012#9 0x00007fe8364b4b11 search_enginetime_list (libnetsnmp.so.35)#012#10 0x00007fe8364b4f8e set_enginetime (libnetsnmp.so.35)#012#11 0x00007fe8364b4885 init_snmpv3_post_config (libnetsnmp.so.35)#012#12 0x00007fe8364b9c92 snmp_call_callbacks (libnetsnmp.so.35)#012#13 0x00007fe836f3601b register_with_master_agent (snmpstats.so)#012#14 0x00007fe836f37f14 run_alarm_check (snmpstats.so)#012#15 0x0000000000531cde compat_old_handler (kamailio)#012#16 0x000000000053284e slow_timer_main (kamailio)#012#17 0x000000000042e3e1 main_loop (kamailio)#012#18 0x0000000000438d14 main (kamailio)#012#19 0x00007fe841772d85 __libc_start_main (libc.so.6)#012#20 0x000000000041cfce _start (kamailio) /usr/sbin/kamailio[32915]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 24 /usr/sbin/kamailio[32858]: ALERT: <core> [main.c:774]: handle_sigs(): child process 32870 exited by a signal 6 ... version: kamailio 5.6.3 (x86_64/linux) fe0c4d 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: fe0c4d compiled on 11:02:26 Jan 19 2023 with gcc 8.5.0 Same config is starting without issues on CentOS 7. OpenSSL version is 1.1.1k Kamailio is installed from official RPM repos. Is core dump would be useful here or best to compile from source and redo? -- Best regards, Ihor (Igor)

3 6

topos vs topoh, any reason for putting a private IP in the Contact header?
by Benoit Panizzon 27 Jan '23

27 Jan '23

Hi I'm trying to work around Route-Header and Via Issues with the two topology hiding modules topoh and topos and trying to figure out, which one works better for our environment. My conclusion so far: topos creates very clean header, but needs a database or redis. I'm always reluctant in adding more components which could fail or cause load. topoh also works, but it worries me a bit that according to the manual: https://www.kamailio.org/docs/modules/devel/modules/topoh.html#topoh.p.mask… a private IP is used to mask the contact header. I have come across a CPE which, as far as I see, is misbehaving by ALWAYS sending a PRACK to the Hostname or IP found in the Contact header, and ignoring Route and Via Header. So why using a private IP as 'mask' and not the IP or Hostname of the actual kamailio instance? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 6

Re: [sr-dev] Is there any Function or parameter to check Initial Invite Response on Kamailio
by Henning Westerholt 25 Jan '23

25 Jan '23

(removed sr-dev from CC) Hello, you can do that with the reply_route and/or onreply_route, for an example check out example cfg or this: https://www.kamailio.org/docs/modules/devel/modules/tm.html#tm.f.t_on_reply Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: HimaBindu G <himabindu.garadareddy(a)gmail.com> Sent: Tuesday, January 24, 2023 3:16 PM To: sr-users(a)lists.kamailio.org; sr-dev(a)lists.kamailio.org Subject: [sr-dev] Is there any Function or parameter to check Initial Invite Response on Kamailio Hi All, Can you please suggest any function or parameter to check Initial Invite Response from the backend. Thanks & Regards, Hima Bindu.

1 0

RTPengine multiple setID sockets
by John Hardiman 24 Jan '23

24 Jan '23

Hi All, Hope you are all well? I am hoping you can help with a bit of syntax I am struggling to get working in the intended way. (We are using Kamailio 5.5.3 and using Kemi/python.) The scenario is in AWS where we have separate Kamailio and RTPengine instances, with a cluster of FreeSWITCH EC2's on private addresses only. In the current setup, all RTP routes via the NAT gateway and back to the private IP of the selected FreeSWITCH (and vice versa). This works in the current config, but I would want this traffic not going via the NAT gateway and use the private address and route internally on the VPC. (These EC'2 have only 1 network interface and that cannot be changed for this work.) So anything between FreeSWITCH and Kamailio/RTPengine uses the private IP's for media, the rest use public IP's. It is good to note that the RTPengine's are the same in each set (3 total RTPengine's), just using the public/private IP's based on set ID. My first aim is to use KSR.permissions.allow_source_address() to check if the source address is from the FreeSWITCH cluster and set the rtpengine setID based on this. I have used this method for different parts of the config and it works. I am failing at this first step it seems, as no matter what I use in the function (below) it defaults and uses the public IP's in SDP. (No matter if I use the same setID in each set) kamailio.cfg snippet: # ----- rtpengine params ----- modparam("rtpengine", "setid_avp", "$avp()") # Public IP's ID 1: modparam("rtpengine", "rtpengine_sock", "1 == udp:5.5.5.5:2223 udp:6.6.6.6:2223 udp:7.7.7.7:2223") # Internal IP's ID 2: modparam("rtpengine", "rtpengine_sock", "2 == udp:10.0.0.1:2223 udp:10.0.0.2:2223 udp:10.0.0.3:2223") Kemi file snippet: # RTPengine Options for different SetID def ksr_route_rtpengine(self, msg): if KSR.textops.has_body_type("application/sdp") > 0 : # Source address is private subnet - use RTPengine set 2 (private IP's) if KSR.permissions.allow_source_address(400) == 1: KSR.rtpengine.set_rtpengine_set(2) KSR.rtpengine.rtpengine_manage( "RTP/AVP replace-session-connection replace-origin port-latching ICE=remove") else: # Source address is NOT private - use RTPengine set 1 (public) KSR.rtpengine.set_rtpengine_set(1) KSR.rtpengine.rtpengine_manage( "RTP/AVP replace-session-connection replace-origin port-latching ICE=remove") KSR.xlog.xlog("L_INFO", "RTPengine handling Block") return 1 Group 400 is the private subnet of the FreeSWITCH clusters we have behind on private addresses and the list contains the subnet of private IP's. Using the above, the Kamailio starts fine and understands/loads each set of RTPengine's and calls work with audio. but regardless of the set number used (even only using set 2 in both) it defaults to public IP's in the SDP. (This is the only place in the config where this function is defined) My SDP from FreeSWITCH egress to Kamailio/RTPengine has private IP's in the SDP. The only thing I do not fully understand is the setid_avp - specifically $avp() block and if this needs to stay empty, or be duplicated with the set ID in each one. Any help would be greatly appreciated in understanding where I am going wrong here. Thanks, John.

3 2

[SR-Users]: Port number in To: field
by Olivier 24 Jan '23

24 Jan '23

Hello, While trunking with an Oracle SBC, I was lately required to include a port number in INVITE To: field. Would you qualify this as a "legal requirement" (according to SIP Standards) ? Best regards

4 3

dialog: db_mode => 1, enable_dmq => 1 but entries not replicated to 2nd node DB
by Benoit Panizzon 24 Jan '23

24 Jan '23

Hi I am struggling with DMQ and dialog DB storage leading to orphan or duplicate entries in database and not loading all dialog information upon restart. usrloc on the other side, also using local db storage and dmq, works flawlessly even when restarting one node. All location information is replicated between the databases via DMQ. So trying to find what is different. usrloc module: modparam("usrloc", "db_url", DBLOCAL) modparam("usrloc", "db_mode", 2) modparam("dmq_usrloc", "enable", 1) modparam("dmq_usrloc", "sync", 1) dialog module: modparam("dialog", "db_url", DBLOCAL ) modparam("dialog", "db_mode", 1 ) modparam("dialog", "db_skip_load", 0) modparam("dialog", "enable_dmq", 1) via kamcmd dlg.list I see that dialog information is being replicated between the two nodes. But I can only find the dialog in the local database of the node which is handling the call. Is this the expected behavior? I also just found how to create duplicate entries in the database... * Run a call on Node A, verify the dialog information is store in the local database and replicated to node B via DMQ. * Restart Kamailio on Node A. There I suspect, node A is restoring Dialog Information via DMQ from Node B and loading the same information from database, leaving duplicates in dialog_vars. Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

Kamailio World 2023 - Call For Presentations
by Daniel-Constantin Mierla 23 Jan '23

23 Jan '23

Hello, I would like to announce that Call for Presentations at Kamailio World 2023 is now open. You can submit your proposal or see more details at: - https://www.kamailioworld.com/k2023/call-for-speakers/ The 11th edition of the conference returns to Berlin, Germany, during June 5-7, 2023, as an in-person event. Expect a large range of participants, developers and community members as well as representatives of other popular open source VoIP projects such as Asterisk or FreeSwitch. Looking forward to meeting many of you there! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

1 0

Performances issue when freeing shared memory in custom module (Kamailio 5.5.2)
by Chaigneau, Nicolas 23 Jan '23

23 Jan '23

Hello, I'm encountering performance issues with Kamailio (5.5.2). I'm using a custom Kamailio module that loads routing data in memory, using Kamailio shared memory. This routing data is very large. It can be fully reloaded through a Kamailio RPC command (which is done once each day). When reloading, two sets of data are maintained, one "loading" and another "current" (the latter being used to handle SIP requests). When loading of the new data is finished, it is swapped to "current". Then, memory of the old (now unused) data is freed. I've noticed that when Kamailio is freeing the old data, there is a very significant performance impact on SIP requests. This is surprising to me, because the SIP requests do not use this old data. This is not a CPU issue, idle CPU% is at about 99% at that moment. I'm using the following functions : - shm_mallocxz - shm_free From what I understand, shm_free is actually "qm_shm_free" defined in "src\core\mem\q_malloc.c" (the default shared memory manager being "qm"). I've noticed that there is also a variant shm_free_unsafe ("qm_free"), which does not perform locking. I'm wondering if the lock could be the cause of my performances issues ? (But I'm not sure how this could be possible, because although the SIP requests need to access the shared memory allocated, they do not use directly the functions from the share memory manager.) If the performances issues are causes by the lock, could I use the unsafe version "safely" ? (considering that it is guaranteed that the old data cannot be used by anyone else) Thanks for your help. Regards, Nicolas. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

2 6

dialog.dlg_filter_mode has ambiguous definition with double negation
by Дилян Палаузов 23 Jan '23

23 Jan '23

Hello, https://www.kamailio.org/docs/modules/devel/modules/dialog#dialog.p.dlg_fil… says for dialog.dlg_filter_mode (int) Set dialog fitering mode, which can specify what dialogs are processed. Its value can be a combination (the sum) of following flags: 1 - do not send keepalives and do not execute timeout function if dialog is not local (if the associated bind address is not a local socket). Default value is “0”. As you can see, the definition of 1 is a double negation and there is no definition for 0. What means 0: - do not send keepalives and do not execute timeout function if dialog is local - send keepalives and execute timeout function if dialog is not local - send keepalives and execute timeout function if dialog is local

1 0

Does tm.t_relay() create a transaction?
by Дилян Палаузов 20 Jan '23

20 Jan '23

Hello, the documentation for tm.t_newtran() says „This is the only way a script can add a new transaction in an atomic way.“ Moreover tm.t_send_reply() “creates the transaction if it does not exist (executing internally t_newtran()) and sends a stateful reply (executing internally t_reply())”. This means that only t_newtrans() and t_send_reply() can create transactions in an atomic way. The documentation of tm.t_relay() does not say whether the function creates a transaction. It also does not say what happens if t_reply() is not called after t_newtrans(). But for tm.t_set_retr() and tm.t_set_retr() is written “If the transaction is already created (e.g called after t_relay() or in an onreply_route) …” This suggests that tm.t_relay() does create atomically or not-atomically a transaction. - What does it mean to create a transaction in a non-atomic way? - Does tm.t_relay() create a transaction? Greetings Dilyan

2 2

sslmode in db_postgres
by Centelles Martin, Joel 20 Jan '23

20 Jan '23

Hello everybody, I'm working on a kamailio instance as a basic registrar service and I thought to use db_postgres to connect a postgres service only allowing SSl connections. I see that that module doesn't provide any parameters to select sslmode and I was wondering if this module actually supports TLS connections. Does anybody know if this is supported and, if so, how to enable it? or should that support be added into db_postgres module code? Thank you very much in advance. BR, Joel Centelles RTC Lead Engineer | Care Communications R&D joel_centellesmartin(a)baxter.com<mailto:joel_centellesmartin@baxter.com> | baxter.com<https://baxter.com/> [cid:9ee6bcbd-9c30-45ec-bb43-8f439f19f724]<https://baxter.com>

1 0

[core/tcp_main.c:617]: _wbufq_add(): (1244714 bytes): write queue full or timeout
by Benoît Panizzon 20 Jan '23

20 Jan '23

Hi I'm trying to get dlg.list on a busy system via jsonrpc and xhttp. I already increased: tcp_conn_wq_max=2048 tcp_wq_max=20480 modparam("ctl", "binrpc_max_body_size", 2048) modparam("ctl", "binrpc_struct_max_body_size", 2048) But it looks like the tcp write queue overflows up at shy over 1MB reply no matter what I change. Any ideas what else to toggle? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 9

What are extended flags?
by Дилян Палаузов 20 Jan '23

20 Jan '23

Hello, The corex module manages extended flags with functions the setxflag(), isxflagset(), and resetxflag(). tmx.t_flush_xflags() does “flush the extended flags from the current SIP message into the already created transaction. It makes sense only in routing block if the transaction was created via t_newtran() and the extended flags have been altered since. It is not needed to execute this function when using t_relay() (or similar tm relay functions, xflags are synchronized automatically in that case).” The documentation of the tm module does not say anything about extended flags - in particular it does not say that t_relay() synchronizes them. Moreover, while the corex module utilizes the extended flags, the documentation of tm and tmx do not state, that they depend on the corex module. So, what are extended flags? Greetings Дилян

1 0

SIP Trunk with multiple phone numbers for account
by Carlos Escalona 19 Jan '23

19 Jan '23

Hello all! I have a question. In my system we use a series of VoIP providers to receive external calls to our telephone numbers, for the same provider we have several registered numbers and we need our providers to send that information in some way, so far it does not seem that there is a common way to do it (report the number that was dialed by the person who made the call). From what I understand, SIP does not have a place for that information because there are no things like phone numbers in the specification, my question is, is there a correct place to send such information, or is it entirely up to each provider? (Now, the most common is to have in the RURI and To header, the id of the trunk registered in the uacreg table) I have seen a couple of options that seem to me the most “correct”: send the information in the To header or send in a custom header. I really appreciate any help you can provide. Atenciosamente, [image: photo] <https://www.techer.com.br/> *Carlos Escalona* IT - Development 41 3073-0091 | R 1011 www.techer.com.br -- O conteúdo desta mensagem é confidencial. Se você não se encontra na lista de destinatários ou tenha recebido por engano, não a copie, imprima, envie, ou utilize, de qualquer forma, seu conteúdo. Neste caso, destrua a mensagem e, por favor, notifique o remetente.

3 3

Setting socket_workers does not work if using interface name
by Kaufman 19 Jan '23

19 Jan '23

At a quick glance it looks like using socket_workers when the listen parameter uses the interface name does not work. For example: children = 4 socket_workers=2 listen=udp:10.10.10.10:5060 Gives two listeners on udp:10.10.10.10:5060 children = 4 socket_workers=2 listen=udp:eth0:5060 Gives four listeners on the socket. Note this is just a quick cursory observation. Is it by design or a design limitation? Kaufman

3 3

RTC/Kamailio dinner at Fosdem 2023
by Daniel-Constantin Mierla 17 Jan '23

17 Jan '23

Hello, Fosdem 2023 returns to Brussels, Belgium, for a physical event and I'm writing to see if there are many people from the community going to the event and want to organize again the usual RTC/Kamailio dinner on Saturday evening (Feb 4, 2023). Each person should pay for himself, likely to be some price increase comparing with the last one. If there is enough interest, Torrey will help to book a place to accommodate us (first choice could be the same restaurant like in the past, if available). Reply if you want to join the dinner and say how many other people are joining you. Note that RTC Devroom got at this edition a half a day room allocation, on the afternoon of Feb 5, 2023 (Sunday). Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

7 8

Re: rtp lost package in 300 concurrent calls and above
by Henning Westerholt 16 Jan '23

16 Jan '23

Hello, please keep the list in CC. Ok, the machine seems to not really using all its cores. Regarding playing a file, this can be also done with rtpengine: https://kamailio.org/docs/modules/5.5.x/modules/rtpengine.html#rtpengine.f.… Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Mohammad Reza Keshavarzianpoor <keshavarzianpoorm(a)gmail.com> Sent: Monday, January 16, 2023 3:35 PM To: Henning Westerholt <hw(a)gilawa.com> Subject: Re: [SR-Users] rtp lost package in 300 concurrent calls and above thanks for your reply my kamailio server has 8GB of ram and 4core*2.6 on esxi(dedicated)Ubuntu 22.04.1 LTS. is it low? htop on server shows load average 1.04 at max and I didn't see more than 10% load on any core of the server. I've selected rtp media server because of playback of a voice file over incoming calls in the future usage On Mon, Jan 16, 2023 at 5:45 PM Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> wrote: Hello, do you observe (too) high load on the system with the standard system management tools? If you want to just proxy calls, my recommendation would be to use rtpengine. Here you should be able to achieve higher concurrent calls rates, if you have a few CPUs on a decent machine. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Mohammad Reza Keshavarzianpoor <keshavarzianpoorm(a)gmail.com<mailto:keshavarzianpoorm@gmail.com>> Sent: Monday, January 16, 2023 2:50 PM To: sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Subject: [SR-Users] rtp lost package in 300 concurrent calls and above Hi, I've installed last version of kamailio over ubuntu. I need to broadcast machine calls to destinations. my concurrent call should be around 300(my pstn channels), so I start calls with cps around 20, because my calls contains a less than 30 second and if destination answer the call it will hanged up in less than or equal to 30 seconds. My problem is: to test my kamailio config, I'm using startrinity sip tester over an win server 2019 on local network. and it shows about 20% lost package on rtp and a jitter about 500ms. what should I do? my config is based on rtp media server module. Is there a complete working sample config for kamailio with rtp media server module? I tried rtpproxy and rtp engine in past and the same problem happened. Thanks for any help you can provide Best regards

4 10

rtp lost package in 300 concurrent calls and above
by Mohammad Reza Keshavarzianpoor 16 Jan '23

16 Jan '23

Hi, I've installed last version of kamailio over ubuntu. I need to broadcast machine calls to destinations. my concurrent call should be around 300(my pstn channels), so I start calls with cps around 20, because my calls contains a less than 30 second and if destination answer the call it will hanged up in less than or equal to 30 seconds. My problem is: to test my kamailio config, I'm using startrinity sip tester over an win server 2019 on local network. and it shows about 20% lost package on rtp and a jitter about 500ms. what should I do? my config is based on rtp media server module. Is there a complete working sample config for kamailio with rtp media server module? I tried rtpproxy and rtp engine in past and the same problem happened. Thanks for any help you can provide Best regards

4 5

Authenticated ACK: $au not set?
by Benoit Panizzon 16 Jan '23

16 Jan '23

Hi Gang I have this code snipplet: if (has_credentials("$fd")) { xlog("L_INFO", "$cfg(route): got $rm with credentials. Validate them!\n"); if ($aU == $null) { xlog("L_INFO", "$cfg(route): no auth user, send challenge\n"); } auth_challenge("$fd", "0"); exit; } } Please don't ask if this makes sense, it's a constructed snipplet to show the situation. If $rm is INVITE, this works fine, no challenge is being sent, $au is populated. If $rm is ACK (some CPE seem to send the Credentials with each message) then $au is $null, auth_challenge is called and fails. Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 1

Parallel call forking with call authorization
by Mathias Schneuwly 13 Jan '23

13 Jan '23

Hi As a first notice; I already wrote to the mailing list, but without registration. I read afterwards that I should register first because of spam reasons. If this is a duplicate, then I'm sorry. I'm new to mailing lists... I've an issue with parallel call forking together with call authentication. I hope somebody can give me some hints about what the problem could be and how I could solve this problem. I'm using Kamailio 5.5.4 with the python KEMI binding. Kamailio is in front of an Asterisk, which requires call authorization. RTPEngine is also inplace which does SRTP to RTP bridging. Simple calls from and to Asterisk through Kamailio and RTPEngine work without any issue. So the basic setup seems to work fine. The problem starts when I do parallel call forking where both calls are sent to Asterisk. If I use "KSR.tm.t_on_failure("trunk_authentication")" for authentication, the first branch is authenticating and the device rings, but the second branch does not authenticate. Well, that's not 100% true, if the SIP timeout appears on the first branch, I can see in the log, that the second branch enters the trunk_authentication method, but then, the call is already terminated. Call forking to two devices (not behind Asterisk and without call authentication) works also as expected. I made some trials with "KSR.tm.t_on_branch_failure("trunk_authentication")" but in this case, the behavior is strange. Then the authentication for both branches work and both devices are ringing. If a device hooks up, the second device does not stop ringing. And after a few seconds, the first device cancels the call, because it did not get the ACKs. I can also see that the CANCEL is sent from Kamailio to Asterisk, but Asterisk does not react to it. For trunk authentication, I'm using the implementation from the well known examples plus a few own stuff. Btw, NAT is not enabled...: def trunk_authentication(self, msg): scode = KSR.pv.get("$T_reply_code") self.log('notice', 'trunk_authentication {}'.format(scode)) if WITH_NAT and self.ksr_route_natmanage(msg) == -255: return 1 # Call manage_rtp_engine to destroy RTPEngine if it has been used. call_context = self.get_call_context(msg=msg) callee_object = call_context.callee.get_callee_object() if callee_object.connection_type: call_context.manage_rtp_engine() if KSR.tm.t_is_canceled() > 0: return 1 if scode in [401, 407]: KSR.pv.sets('$avp(auser)', KSR.pv.get('$sel(cfg_get.asterisk.trunk_username)')) KSR.pv.sets('$avp(apass)', KSR.pv.get('$sel(cfg_get.asterisk.trunk_password)')) if KSR.uac.uac_auth(): # enable additional event routes for forwarded requests # - serial forking, RTP relaying handling, a.s.o. if KSR.is_method_in('IBSU'): if KSR.tm.t_is_set("branch_route") < 0: KSR.tm.t_on_branch("ksr_branch_manage") self.log('notice', 'Authentication Asterisk trunk') if KSR.tm.t_relay() < 0: KSR.sl.sl_reply_error() return 1 Any ideas? Best regards Mathias

3 6

src/modules.lst - difference between skipping a module from compile list and excluding a module from compile list
by Дилян Палаузов 13 Jan '23

13 Jan '23

Hello, the generated src/modules.lst file contains: # the list of modules to skip from compile list skip_modules= … # the list of modules to exclude from compile list exclude_modules= … For me excluding a module from the compile list and skipping the module when compiling is the same. Please describe what is the difference between skipping and excluding, either in modules.lst, at https://www.kamailio.org/wikidocs/devel/makefile-system/ or at https://kamailio.org/docs/tutorials/devel/kamailio-install-guide-git/ . Thanks Дилян

2 1

Newbie question
by Joao Paulo Vaz 12 Jan '23

12 Jan '23

Hello masters, I am a newbie who recently got to know Kamailio. I have a scenario and I would like to know if this tool would suit: a central asterisk server with all user accounts and three remote units with Kamailio acting as a proxy. Is there any module or configuration that if the central asterisk server fails to respond, would the remote proxies act in survival mode, allowing local communication by users until the central asterisk server returns a response? Att, Joao Paulo

3 4

unsubscribe.pls
by Stanly Levyy 11 Jan '23

11 Jan '23

*** THIS E-MAIL MESSAGE AND ANY DOCUMENTS ATTACHED IS/ARE INTENDED ONLY FOR THE USE OF THE INDIVIDUAL(S) OR ENTITY TO WHICH IT IS ADDRESSED; AND MAY CONTAIN INFORMATION THAT IS LEGALLY PRIVILEGED, CONFIDENTIAL AND/OR EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW, including the Electronic Communications Privacy Act, 18 U.S.C. Secs 2510-2521 *** On Wednesday, January 11, 2023, 01:36:44 AM PST, <sr-users-request(a)lists.kamailio.org> wrote: Send sr-users mailing list submissions to sr-users(a)lists.kamailio.org To subscribe or unsubscribe via email, send a message with subject or body 'help' to sr-users-request(a)lists.kamailio.org You can reach the person managing the list at sr-users-owner(a)lists.kamailio.org When replying, please edit your Subject line so it is more specific than "Re: Contents of sr-users digest..." Today's Topics: 1. Re: Performing async_http calls on stateless Loadbalancers (Julius Flohr) 2. Re: Releasing v5.6.3 (Daniel-Constantin Mierla) 3. Performing async_http calls on stateless Load balancers (Lewis Hutchinson) ---------------------------------------------------------------------- Message: 1 Date: Tue, 10 Jan 2023 18:50:44 +0100 From: Julius Flohr <flohr(a)sipgate.de> Subject: [SR-Users] Re: Performing async_http calls on stateless Loadbalancers To: Henning Westerholt <hw(a)gilawa.com> Cc: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org>, Alles wird besser <alleswirdbesser(a)sipgate.de> Message-ID: <34C7487C-0900-4C49-BBB4-49A0291D83E6(a)sipgate.de> Content-Type: multipart/alternative; boundary=Apple-Mail-0AF7C672-1C85-4A98-9DDC-EED95FFB4B7E A message part incompatible with plain text digests has been removed ... Name: not available Type: text/html Size: 7117 bytes Desc: not available ------------------------------ Message: 2 Date: Wed, 11 Jan 2023 08:30:17 +0100 From: Daniel-Constantin Mierla <miconda(a)gmail.com> Subject: [SR-Users] Re: Releasing v5.6.3 To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org>, "Kamailio (SER) - Devel Mailing List" <sr-dev(a)lists.kamailio.org> Message-ID: <454ae3b5-a810-f393-4196-e71c4482e9d3(a)gmail.com> Content-Type: text/plain; charset=UTF-8 Hello, the usual note that preparing the release of Kamailio v5.6.3 starts soon, therefore any commits to branch 5.6 should be announced first on sr-dev mailing list and wait for the ack before pushing to repo. Once the announcement is out, commits can go in the branch directly. Cheers, Daniel On 06.01.23 16:44, Daniel-Constantin Mierla wrote: > Hello, > > I am considering to release Kamailio v5.6.3 (out of branch 5.6) next > week (likely on Wednesday, Jan 11, 2023). If anyone is aware of > issues not yet on the bug tracker, report them there asap in order to > have a better chance to be fixed. > > Cheers, > Daniel > > -- > Daniel-Constantin Mierla -- www.asipto.com > www.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com > -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com ------------------------------ Message: 3 Date: Wed, 11 Jan 2023 09:20:28 +0000 From: Lewis Hutchinson <lewis.hutchinson(a)missionlabs.co.uk> Subject: [SR-Users] Performing async_http calls on stateless Load balancers To: "sr-users(a)lists.kamailio.org" <sr-users(a)lists.kamailio.org> Cc: "flohr(a)sipgate.de" <flohr(a)sipgate.de>, "alleswirdbesser(a)sipgate.de" <alleswirdbesser(a)sipgate.de> Message-ID: <CWXP265MB2517CB6E3E8188F3E3BB5B2AC5FC9(a)CWXP265MB2517.GBRP 265.PROD.OUTLOOK.COM> Content-Type: text/plain; charset="us-ascii" Hi Julius If I have understood this correctly, I think you can achieve this using KEMI Python leveraging aiohttp & asyncio i.e async with aiohttp.ClientSession() as session: This can be done outside of REQUEST_ROUTE Requires a rewrite from Native to KEMI so might be a bit excessive but would work. Regards Lewis ------------------------------ Subject: Digest Footer _______________________________________________ sr-users mailing list -- sr-users(a)lists.kamailio.org To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org ------------------------------ End of sr-users Digest, Vol 212, Issue 33 *****************************************

1 0

Performing async_http calls on stateless Load balancers
by Lewis Hutchinson 11 Jan '23

11 Jan '23

Hi Julius If I have understood this correctly, I think you can achieve this using KEMI Python leveraging aiohttp & asyncio i.e async with aiohttp.ClientSession() as session: This can be done outside of REQUEST_ROUTE Requires a rewrite from Native to KEMI so might be a bit excessive but would work. Regards Lewis

1 0

Releasing v5.6.3
by Daniel-Constantin Mierla 11 Jan '23

11 Jan '23

Hello, I am considering to release Kamailio v5.6.3 (out of branch 5.6) next week (likely on Wednesday, Jan 11, 2023). If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

1 1

Help with rtpengine_delete()
by Jose Figueroa 10 Jan '23

10 Jan '23

Hello everyone! I've been struggling with a kamailio scenario with the rtpengine_delete. My scenario is the following: I've setup a Kamailio multihomed, since some of my vendors has provided us a direct link using a different local subnet in eth2 and I have my public IP in eth1. The kamailio i've been working on is using app_lua module. SIP A <---------> 200.XXX.XXX.14 (eth1) [Kamailio 5.6] (eth2) 10.203.5.8 <------> Vendor 10.203.5.20 100.XXX.XXX.22 Basically, I receive a call from public IP eth1 and according to the logic from the vendor I forward statefully the call to 10.203.5.20 in second branch. I've been reading a lot of issues and documentation such as:[#840 rptengine], [#875 rtpengine] and [#2222 kamailio], but I don't really get working the rtpengine_delete() correctly, since I go to netstat -plan|grep rtpengine and I see some sessions still that are not freed. My second case is the following when I receive a 503 from another GW: SIP A <---------> 200.XXX.XXX.14 (eth1) [Kamailio 5.6] (eth1) 200.XXX.XXX.14 <-----------> Vendor GW 233.XXX.XXX.19 100.XXX.XXX.22 In that case I still see the rtpengine ports, mostly with my public IP 200.XXX.XXX.14 but some of them with the LAN 10.203.5.8 IP. Also, something curious I see on my 2nd use case is the following: https://pastebin.com/raw/B4vCgExX So, it would be great if someone can point me to the right direction, how and when I should use rtpengine_delete in order to finish the rtpengine sessions correctly and the ports can be freed up. Any help will be great! [840] https://github.com/sipwise/rtpengine/issues/840 [875] https://github.com/sipwise/rtpengine/issues/875 [2222] https://github.com/kamailio/kamailio/issues/2222 -- Regards, Jose Figueroa

3 2

Why do htable Keys have two colons?
by Noah Mehl 10 Jan '23

10 Jan '23

Hey everyone, Whenever I read documentation for htable usage, and other examples of other scripts in Kamailio, htable keys are typically named: something::something Examples are: $au::auth_count, $ci::srcip, join::$rU Why are there two colons (as opposed to a | )? Is this just a standard semantic thing in Kamailio? Is there something about that double character that’s unusual and easy to parse with SIP values? Or is it just what people do, and that’s a good choice to continue for all other Kamailio script writers to have understanding? Any insight would be appreciated. Thanks! ~Noah

3 6

Kamailio Crypto module and 3rd party openssl
by Arsenijs Kabihno 10 Jan '23

10 Jan '23

Hello, I am trying to make use of crypto module. The scenario is the following: 1. Encrypt plaintext passwords on kamailio side using crypto_aes_encrypt function of crypto module 2. Decrypt them outside of kamailio using 3rd party tools, such as PHP openssl_decrypt Crypto module parametrs are the following: modparam("crypto", "salt", "") modparam("crypto", "key_derivation", 0) If encryption and decription are handled by kamailio, the initial password matches the decrypted string (initial password -> encrypted string -> decrypted string) For example: sql_query("ds_dburl", "select secret from kamailio_sip_buddies where username='$au'", "secret"); $avp(secret_plain) = $dbr(secret=>[0,0]); //value: 'kamailio' crypto_aes_encrypt("$avp(secret_plain)", "YUZySHVtdlVTYjI0TGJNd3JTeVV0MlRaRWFraFNBRlM=", "$var(encrypted)"); //value: 'qfOqTMoJMgGAherGCqLRRQc4zTlqsEj3MEtcORurFf0=' crypto_aes_decrypt("$avp(secret_plain)", "YUZySHVtdlVTYjI0TGJNd3JTeVV0MlRaRWFraFNBRlM=", "$var(decrypted)"); //value: 'kamailio' But in case I try to decrypt the value of $var(encrypted) using PHP openssl_decrypt or online tool like https://www.devglan.com/online-tools/aes-encryption-decryption, I am getting the result 'kamailio' prepended by 16 random bytes, like: 6“¤›¿Ð+IÊ\ñžïZkamailio or 6��+I\��Zkamailio I believe this 16 bytes are actually random initialization vector in some encoding. Possibly kamailio is trimming them from result here: https://github.com/kamailio/kamailio/blob/master/src/modules/crypto/crypto_… Moreover, if secret was encrypted using crypto_aes_encrypt and random IV, you can use any IV while decrypting and get 16 different bytes+result Please advice if someone have used crypto module in similar way and what are the possible ways to acheive results consistency

2 5

pkg memory leak when acc module cdr_enabled
by Juha Heinanen 10 Jan '23

10 Jan '23

In latest stable K release, we noticed pkg memory leak (pgk memory usage increases by each processed call). It turned out that the leak goes away if acc module cdr_enable is not enabled. Could be a bug in dialog or acc module. Any debug instructions if the bug is not obvious? -- Juha

4 14

wrong char / bad PVE format
by Nathan Stratton 09 Jan '23

09 Jan '23

Trying to rename rtpengine files with: exec_msg("mv /var/spool/rtpengine/rtpengine-recording/$ci* /var/spool/rtpengine/rtpengine-recording/$ci.wav"); But get this error: Jan 06 13:59:19 proxy1 /usr/sbin/kamailio[2929]: ERROR: <core> [core/pvapi.c:924]: pv_parse_spec2(): error searching pvar "ci.wav" Jan 06 13:59:19 proxy1 /usr/sbin/kamailio[2929]: ERROR: <core> [core/pvapi.c:1127]: pv_parse_spec2(): wrong char [v/118] in [$ci.wav] at [6 (0)] Jan 06 13:59:19 proxy1 /usr/sbin/kamailio[2929]: ERROR: <core> [core/sr_module.c:1157]: fix_param(): bad PVE format: "mv /var/spool/rtpengine/rtpengine-recording/$ci* /var/spool/rtpengine/rtpengine-recording/$ci.wav" Jan 06 13:59:19 proxy1 /usr/sbin/kamailio[2929]: ERROR: <core> [core/mod_fix.c:564]: fixup_spve_null(): Cannot convert function parameter 1 to space Any ideas? ><> Nathan Stratton Founder, CTO Vocinity, Inc. <https://www.vocinity.com/gabbi>

3 2

RABBITMQ and AWS
by Fred Posner 06 Jan '23

06 Jan '23

Has anyone had any success connecting to RabbitMQ via a TLS 1.2 connection (such as the AWS MQ product)? Fred Posner https://pgpx.io

3 3

TypeError exception in Kemi with python3
by Michel Pelletier 06 Jan '23

06 Jan '23

Hello, I am using Kemi with Python3. I am getting a TypeError exception when using the following: KSR.presence.handle_subscribe() 40(208) INFO: PY3 {SUBSCRIBE}: app_python3 [apy_kemi.c:1839]: sr_apy_kemi_exec_func(): alert - action KSR.presence.handle_subscribe(...) took too long [2004761 ms] (file:(null) func:(null) line:733) 40(208) ERROR: PY3 {SUBSCRIBE}: app_python3 [python_support.c:156]: python_handle_exception(): apy_exec: ksr_request_route((null)): Unhandled exception in the Python code: TypeError: expected bytes, str found The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/etc/kamailio/kamailio.py", line 152, in ksr_request_route if self.ksr_route_presence(msg) == -255: File "/etc/kamailio/kamailio.py", line 733, in ksr_route_presence KSR.presence.handle_subscribe() SystemError: <built-in function handle_subscribe> returned a result with an error set Using the following appears to be a good workaround, as it does not exhibit the issue at all: KSR.presence.handle_subscribe_uri(KSR.pv.get("$fu")) Cheers, Michel Pelletier

1 0

Call drop when reinvite is proceed
by nathan.castillo＠snapcom.fr 05 Jan '23

05 Jan '23

Hello all, I'm trying to figure out one problem on my Kamailio server. When kamailio receive a reinvite from the infra, I get the error message "477 - Unforunately error on sending to next hop" and the call drop. I don't understand why this message appears as the first invite is well answered and the call is going well. Any ideas how to resolve this issue ? Thanks in advance for your help. Regards, Nathan

6 6

Too many 200:OK sip responses
by Waqar 40 05 Jan '23

05 Jan '23

Dear All, For a normal call, Kamailio receives 200:OK sip response for the method invite only once but for some calls, it receives 200:OK too many times around 6 to 7. And I also do not receive BYE or any other packets for this kind of call. How can I detect such calls in Kamailio and cancel them? I am inserting data of the calls in the database when the call occurs and deleting it when BYE is received but for these calls as I don't receive BYE so I am unable to delete the record of such calls. Is there a way to detect such calls? Like How can I count if the number of 200:OK responses is more than one or anything like that? Regards Vicky

4 4

How to have Kamailio retry backends
by Unai Rodriguez 04 Jan '23

04 Jan '23

Dear List, We’re using Kamailio to load balance MRCP requests to multiple backend groups with a configuration as follows: # kamailio.cfg ... ... route[DISPATCH] { if($ua=="mrcp_backend_1") { if(!ds_select_dst("1", "4")) { send_reply("404", "No destination"); exit; } } if($ua=="mrcp_backend_2") { if(!ds_select_dst("2", "4")) { send_reply("404", "No destination"); exit; } } xlog("L_DBG", "--- SCRIPT: going to <$ru> via <$du>\n"); t_on_failure("RTF_DISPATCH"); route(RELAY); exit; } ... ... # dispatcher.list 1 sip:mrcp01.server.int:8060;transport=tcp 1 sip:mrcp02.server.int:8060;transport=tcp 2 sip:mrcp03.server.int:8060;transport=tcp 2 sip:mrcp04.server.int:8060;transport=tcp With this configuration, Kamailio load balances the initial SIP INVITE among the MRCP servers. After the INVITE, the service communicates directly to the MRCP servers via SIP (for hanging up the call), MRCPv2 (for sending speech control messages), and RTP (for sending audio). We would like to implement a configurable number of retries, so that if a particular backend times out, Kamailio would retry X times to other backend(s). In short, something equivalent to HAProxy’s retries, but for Kamailio. This probably implies having Kamailio always as part of our communication (not just load balancing the initial SIP INVITE). I haven’t been able to find much information about this, could someone provide some pointers? Thank you so much With best wishes, Unai Rodriguez

3 6

Recover call in ringing state
by Devang Dhandhalya 04 Jan '23

04 Jan '23

Hello All I have below setup : SBC -> kamailio -> Media server(remote) -> web-client Call comes from sbc to kamilio and it relays to Remote server to end user, In Ringing state if remote server goes down then in kamailio there is any way to Recover that ringing call like we can generate new invite for other Remote server which is active state, for relaying call i am using dispatcher module.. I tried with tm.cancel RPC command but it works only if the remote server is running , when I crash the remote server at that time tm.cancel is not generating cancel to remote server. Please suggest if there is any other way to generate INVITE. Regards Devang Dhandhalya -- * <https://www.ecosmob.com/> * *Disclaimer* In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis of any of the information contained in this email is hereby excluded. *Confidentiality* This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error. *Caution for viruses, malware etc.* This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware, interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems.

2 3

Job offer Kamailio/VoIP developer
by Henning Westerholt 03 Jan '23

03 Jan '23

Hello and Happy New Year, we are looking for a new Kamailio & VoIP developer colleague to join and grow our international team. More detail about the position can be found at: https://gilawa.com/en/about/careers If you are interested, please send me a (direct) email. Please include the information described in the linked job description. Best regards, Henning Westerholt -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/>

1 0

Localy generate BYE message from ims_charging
by masoud96＠mail.ru 03 Jan '23

03 Jan '23

Hello! I have a problem with writing the BYE message from the ACC module to the database, because the messages are generated locally by the ims_charging module at the end of the credit and the flag will not work. You can help catch such local messages and make a record in the database.

2 2

Question about UAC and PUA modules routing behavior
by Jean-Francois Lemieux 03 Jan '23

03 Jan '23

Hello, I have some trouble to figure out how routing works when the request coming from the kamailio itself (used as a user agent per example) .I try to use presence PUA... modules. The issue I have is the NOTIFY requests aren't sent to the good destination; it doesn't seems to obey to the contact or other informations when the device did a SUBSCRIBE. I don't want to ask to troubleshoot the presence module directly I just want to know how Kamailio deals with request coming from Kamailio itself (in the case of a NOTIFY generated by PUA_... modules My mains questions are: Does the pua modules when generating request like NOTIFY will pass through request_route ? Does the pua modules when generating request like NOTIFY will be sent only when t_relay() is used or UA kamailio based request bypass all the logic of the Kamailio proxy behavior ? I'm trying to understand if I can modify the NOTIFY request to change destination before the "routing decision" is made by Kamailio Kamailio 5.6.0 used as : -proxy to remote pbx for call dialog -registrar/location server -media relaying and nat management -...and I try to use it as a presence server instead to use the pbx behind kamailio

3 2

Steering egress on replies
by Alex Balashov 03 Jan '23

03 Jan '23

Hi, Happy New Year! From what I understand, replies are always sent back out of the listener on which they were received, though `reply_to_via` (off by default) can override this and cause the exit listener to be recalculated based on a real-time assessment of the best way to reach the last Via hop. Two questions arise: 1) If turning `mhomed` off, can `$fs` be used to override the exit interface of locally generated replies, too? If so, where should it be done? In a request_route prior to a send_reply() / sl_send_reply() / t_reply() call? Or should it be done inside a local reply route or onsend_route? 2) Does this differ for locally generated replies vs. relayed replies, either statefully or statelessly? Thanks! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 1

Registration Proxy
by nutxase 02 Jan '23

02 Jan '23

Hi Guys, can someone point me in the right direction as to how i can use kamailio as a registration proxy similar to how opensips does mid_registrar? i want to proxy all sip registrations through kamailio to asterisk or freeswitch Sent with [Proton Mail](https://proton.me/) secure email.

3 2

Happy New Year 2023!
by Daniel-Constantin Mierla 01 Jan '23

01 Jan '23

A Happy, Peaceful And Prosperous Year 2023 to everyone using Kamailio and helping to improve the project! Looking forward to meeting many of you around this world during 2023 and collaborating in a friendly environment! Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com

1 0

Re: Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST)
by Lewis Hutchinson 30 Dec '22

30 Dec '22

Hi Brandon Apologies if you have provided this but do you have a PCAP of the INVITE / 400 Bad Request rather than the Pastebin of the INVITE The last time I had this was because of a missing /r/n on the SDP granted it was not with teams but still difficult to track down. Also, what is the MTU Size, have you checked to see if the is causing packet fragmentation and manifesting in a Bad Request. Are there any clues in the Teams - Call Analytics. Regards Lewis -----Original Message----- From: sr-users-request(a)lists.kamailio.org <sr-users-request(a)lists.kamailio.org> Sent: 29 December 2022 20:17 To: sr-users(a)lists.kamailio.org Subject: sr-users Digest, Vol 211, Issue 67 Send sr-users mailing list submissions to sr-users(a)lists.kamailio.org To subscribe or unsubscribe via email, send a message with subject or body 'help' to sr-users-request(a)lists.kamailio.org You can reach the person managing the list at sr-users-owner(a)lists.kamailio.org When replying, please edit your Subject line so it is more specific than "Re: Contents of sr-users digest..." Today's Topics: 1. Re: Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST) (Brandon Armstead) 2. Re: Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST) (Brandon Armstead) ---------------------------------------------------------------------- Message: 1 Date: Thu, 29 Dec 2022 12:15:16 -0800 From: Brandon Armstead <brandon(a)cryy.com> Subject: [SR-Users] Re: Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST) To: Henning Westerholt <hw(a)gilawa.com> Cc: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Message-ID: <CABAX3EoF+hfruLiV2Nh_g117_q8diaKxVEyp5hMFO=wyKbQidQ(a)mail.gmail.com> Content-Type: multipart/alternative; boundary="0000000000005692d905f0fd2538" Henning, There was no reply (reason) available in my case. - Brandon On Thu, Dec 29, 2022 at 11:48 AM Henning Westerholt <hw(a)gilawa.com> wrote: > Hello, > > > > as mentioned before, have a look to the 400 reply reason phrase. This > was done quite good from their side, better than many other vendors. > > Usually, Teams is not too bad if you are using a defined > infrastructure that do not introduce too many variables. We are > usually using a B2BUA in our customer projects for that purpose. > > > > Cheers, > > > > Henning > > > > -- > > Henning Westerholt - > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fskal > atan.de%2Fblog%2F&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk% > 7Ce1670c8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b% > 7C0%7C0%7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM > DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdat > a=QU%2BzOgPdbmRYh51a9PvptIvVjnTZrGxT8z1G7b2RRGQ%3D&reserved=0 > > Kamailio services - > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgila > wa.com%2F&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk%7Ce1670c > 8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b%7C0%7C0% > 7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQI > joiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=PuDqkZ > QCj2IlxvRsLQGoKFv19K3uVE5RBxvcPKPODwQ%3D&reserved=0 > > > > *From:* Brandon Armstead <brandon(a)cryy.com> > *Sent:* Thursday, December 29, 2022 7:52 PM > *To:* Kamailio (SER) - Users Mailing List > <sr-users(a)lists.kamailio.org> > *Subject:* [SR-Users] Re: Direct Routing, SIP, INVITE TO TEAMS (400 > BAD > REQUEST) > > > > Alex & Kaufman, > > > > Appreciate the feedback. The pastebin is one example of about > 1000+ iterations literally of changes. So I'm finally reaching out > :). I haven't tested the socket attribute in record-route change, I > will try this now. As for the angle brackets I've tried with and > without, etc (already) to no effect. The SDP unknown media type seems > to be a Poly thing, so I > *want* to rule this out as its not in my other SDP's and still receive > 400 bad request. > > One more iteration here we go... please feel free to let me know if > you have any other thoughts on the matter :). > > > > Thanks! > > > > - Brandon > > > > On Thu, Dec 29, 2022 at 8:08 AM Alex Balashov > <abalashov(a)evaristesys.com> > wrote: > > Yeah, the grammar says that rr-params are just generic-params, in > which case it's not. I didn't see that -- nicely spotted! > > I think that may be the basis of the 400 Bad Request. I'd be shocked > if it weren't. > > The broken clock of "Microsoft SIP" can still be right twice a day. > > > On Dec 29, 2022, at 10:31 AM, Kaufman <bkaufman(a)bcmone.com> wrote: > > > > In your top Record-Route you have: > > > > socket=; > > > > Not sure if that is legal. > > > > Kaufman > > > > -----Original Message----- > > From: Alex Balashov <abalashov(a)evaristesys.com> > > Sent: Thursday, December 29, 2022 9:02 AM > > To: Kamailio (SER) - Users Mailing List > > <sr-users(a)lists.kamailio.org> > > Subject: [SR-Users] Re: Direct Routing, SIP, INVITE TO TEAMS (400 > > BAD > REQUEST) > > > > Sorry to hear you're having to interoperate with Teams. It's a > > unique > form of sadism I wouldn't wish upon anyone. > > > > A few theories: > > > > 1) Microsoft doesn't like the "bare" Contact header-value here: > > > > Contact: > sip:+MY_FROM_PHONE_NUMBER_HERE@MY_FQDN_WAS_HERE:5061;transport=tls > > > > Unlike the careted one right above: > > > > P-Asserted-Identity: > > <sip:+MY_FROM_PHONE_NUMBER_HERE@MY_FQDN_WAS_HERE> > > > > A bare URI absent other header-params is of course completely legal, > > but > I'm really trying to get inside the imaginary world of antisocial > "Microsoft SIP" here. > > > > 2) Could it be that antisocial "Microsoft SIP" sends 400 as a way of > objecting to something in the SDP, e.g. where a non-demented SIP stack > would send "488 Not Acceptable Here" or "415 Unsupported Media Type"? > > > > I know you've said you tried multiple clients to rule that out, but > > I > wonder if the thing it's objecting to hasn't been ruled out that way. > > > > 3) I saw this media line in the SDP: > > > > m=application 41356 <unknown media type> > > > > What's that? > > > > -- Alex > > > >> On Dec 29, 2022, at 9:51 AM, Brandon Armstead <brandon(a)cryy.com> wrote: > >> > >> Outbound calls from my SBC into Teams (Polycom -> SBC -> Teams) > >> always > result in a 400 BAD REQUEST. > >> Example invite below: > >> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fn > >> am11.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%25 > >> 2Fpast&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk%7Ce1670c > >> 8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b%7C0%7 > >> C0%7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA > >> iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sda > >> ta=5v20CvNnmdiHwfWMBX6tgjMlE1i2aKpFgTnuVFfpyl0%3D&reserved=0 > >> ebin.com%2FF1G1Ce59&data=05%7C01%7Cbkaufman%40bcmone.com%7C55672dbf > >> 739 > >> a4ff447f008dae9b0c9b2%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C > >> 638 > >> 079242759152531%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjo > >> iV2 > >> luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Cbff6B4g > >> Nr8 > >> A9zs89smJ129y8IyNM9%2B3zVkGhlzpa54%3D&reserved=0 > >> I've taken care to make sure numbers are all E.164 format in > From/To/Contact. I've also taken care to make sure that FQDN is used > in Contact and Record-Route header. > >> I've tried many different variations and have followed the SIP > information here: > >> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fn > >> am11.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%25 > >> 2Flear&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk%7Ce1670c > >> 8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b%7C0%7 > >> C0%7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA > >> iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sda > >> ta=ELk0UD1Pleq%2FG9j1%2BT18tiuFe0yjflimR9ztnW%2F7oPM%3D&reserved=0 > >> n.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fdirect-routing-protocols > >> -si > >> p&data=05%7C01%7Cbkaufman%40bcmone.com%7C55672dbf739a4ff447f008dae9 > >> b0c > >> 9b2%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638079242759152531 > >> %7C > >> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6I > >> k1h > >> aWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GO26A9FOOoS42yMCWPPGo5PkKo > >> 75c > >> kjSJSkjAeYRsU0%3D&reserved=0 I've also tried several different > >> clients (Bria, Polycom CCX 600, Grandstream, etc) to see if maybe > >> it was > something in the SDP or otherwise causing an issue. > >> SIP Transport is TLS, RTP is SRTP > >> I might also add that OPTION pings are active and Direct Routing > Endpoint is active, so this is successful. I also am able to receive > calls FROM teams to my IP phone(s) without issue. It is only when I > try and call INTO teams (INVITE -> Microsoft Teams) that I always > receive a 400 BAD REQUEST to my INVITE. > >> Any help is appreciated, thank you! > >> > >> - Brandon > >> > >> __________________________________________________________ > >> Kamailio - Users Mailing List - Non Commercial Discussions To > >> unsubscribe send an email to sr-users-leave(a)lists.kamailio.org > >> Important: keep the mailing list in the recipients, do not reply > >> only > to the sender! > >> Edit mailing list options or unsubscribe: > > > > -- > > Alex Balashov | Principal | Evariste Systems LLC > > > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > > Web: > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.e > varistesys.com%2F&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk% > 7Ce1670c8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b% > 7C0%7C0%7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM > DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdat > a=hbww6wEEztE85YqxcN92bpMR%2BkiI9%2BE3jF1i6fQpjEk%3D&reserved=0, > > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.c > srpswitch.com%2F&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk%7 > Ce1670c8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b%7 > C0%7C0%7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD > AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata > =4E7a5ZxSvttBiMxl1VTtolmTvS4T5VGZHA00CsbPR2c%3D&reserved=0 > > > > __________________________________________________________ > > Kamailio - Users Mailing List - Non Commercial Discussions To > unsubscribe send an email to sr-users-leave(a)lists.kamailio.org > > Important: keep the mailing list in the recipients, do not reply > > only to > the sender! > > Edit mailing list options or unsubscribe: > > __________________________________________________________ > > Kamailio - Users Mailing List - Non Commercial Discussions To > > unsubscribe send an email to sr-users-leave(a)lists.kamailio.org > > Important: keep the mailing list in the recipients, do not reply > > only to > the sender! > > Edit mailing list options or unsubscribe: > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.e > varistesys.com%2F&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk% > 7Ce1670c8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b% > 7C0%7C0%7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM > DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdat > a=hbww6wEEztE85YqxcN92bpMR%2BkiI9%2BE3jF1i6fQpjEk%3D&reserved=0, > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.c > srpswitch.com%2F&data=05%7C01%7Clewis.hutchinson%40missionlabs.co.uk%7 > Ce1670c8a21444edf0ed408dae9f91fac%7C97c26f550a7a4661bd8f7b43b50d3f2b%7 > C0%7C0%7C638079553431377130%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD > AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata > =4E7a5ZxSvttBiMxl1VTtolmTvS4T5VGZHA00CsbPR2c%3D&reserved=0 > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions To > unsubscribe send an email to sr-users-leave(a)lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only > to the sender! > Edit mailing list options or unsubscribe: > >

1 0

Direct Routing, SIP, INVITE TO TEAMS (400 BAD REQUEST)
by Brandon Armstead 29 Dec '22

29 Dec '22

Outbound calls from my SBC into Teams (Polycom -> SBC -> Teams) always result in a 400 BAD REQUEST. Example invite below: https://pastebin.com/F1G1Ce59 I've taken care to make sure numbers are all E.164 format in From/To/Contact. I've also taken care to make sure that FQDN is used in Contact and Record-Route header. I've tried many different variations and have followed the SIP information here: https://learn.microsoft.com/en-us/microsoftteams /direct-routing-protocols-sip I've also tried several different clients (Bria, Polycom CCX 600, Grandstream, etc) to see if maybe it was something in the SDP or otherwise causing an issue. SIP Transport is TLS, RTP is SRTP I might also add that OPTION pings are active and Direct Routing Endpoint is active, so this is successful. I also am able to receive calls FROM teams to my IP phone(s) without issue. It is only when I try and call INTO teams (INVITE -> Microsoft Teams) that I always receive a 400 BAD REQUEST to my INVITE. Any help is appreciated, thank you! - Brandon

5 9

Remove all Via Header or create custome Via Header
by Benoit Panizzon 27 Dec '22

27 Dec '22

Hi out there! While experimenting with the listen and adverize 'hostname' option I came across a voice switch, which I suppose fails if the Via header is not an IPv4 address. There is a record_route_advertised_address(address) in the RR module, to set a customer Record-Route Header. Is there something similar for the Via header so I could try if having an IP address instead of a hostname in the top-most Via would solve the issue? Or is there a way to remove all via header? Remove_hf("Via") in the branch route trigger garbles the From: HF. Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 4

Proxy edge
by Giovanni Iamonte 26 Dec '22

26 Dec '22

Dear List We have configured kamailio to work as a proxy edge and register. As a proxy edge cfg file we have used the example *edge_websocket.cfg.** * We are developing two different client the first one based on *PJSIP* and the other one based *JsSIP*. Client PJSIP (no websockets) everything work perfectly, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, MESSAGE, INVITE Client JsSIP (with websockets) The REGISTER, SUBSCRIBE works, the NOTIFY does not work. In more in details we have: Browser Proxy Edge Register Client JsSIP Websocket | | | | | | | ----------Register-----------> | -----------Register----------> | | <----------200 OK ----------- | <----------200 OK ----------- | | | | | ----------Subscribe----------> | -----------Subscribe---------> | | <----------200 OK ----------- | <----------200 OK ----------- | | | | | X<--- | <----------NOTIFY ----------- | | | | As you can see the NOTIFY start from Register and reach the proxy, beloe the Register log file and the sip messages. Could somebody put me in the right direction. Thanks Bye *Log File* Dec 20 10:51:58 kr-server /usr/sbin/kamailio[87875]: DEBUG: <core> [core/tcp_read.c:1533]: tcp_read_req(): content-length=0 Dec 20 10:51:58 kr-server /usr/sbin/kamailio[87875]: DEBUG: <core> [core/parser/parse_fline.c:249]: parse_first_line(): first line type 2 (reply(status)) flags 1 Dec 20 10:51:58 kr-server /usr/sbin/kamailio[87875]: DEBUG: <core> [core/parser/msg_parser.c:689]: parse_msg(): SIP Reply (status): Dec 20 10:51:58 kr-server /usr/sbin/kamailio[87875]: DEBUG: <core> [core/parser/msg_parser.c:690]: parse_msg(): version: <SIP/2.0> Dec 20 10:51:58 kr-server /usr/sbin/kamailio[87875]: DEBUG: <core> [core/parser/msg_parser.c:692]: parse_msg(): status: <478> Dec 20 10:51:58 kr-server /usr/sbin/kamailio[87875]: DEBUG: <core> [core/parser/msg_parser.c:694]: parse_msg(): reason: <Unresolvable destination (478/SL)> Dec 20 10:51:58 kr-server /usr/sbin/kamailio[87875]: DEBUG: <core> [core/parser/parse_hname2.c:301]: parse_sip_header_name(): parsed header name [Via] type 1 *Sip Messages* *REGISTER* sip:sip-register.quintetto.it SIP/2.0 Via: SIP/2.0/WSS 13569868356.invalid;branch=z9hG4bK7825787 Max-Forwards: 69 To: <sip:quintetto00@sip-register.quintetto.it> From: "quintetto00" <sip:quintetto00@sip-register.quintetto.it>;tag=2tnuk9btmp Call-ID: unrnseei8924hf67khoi3g CSeq: 2 REGISTER Authorization: Digest algorithm=MD5, username="quintetto00", realm="sip-register.quintetto.it", nonce="Y6GUq2Ohk3//HTza7ZYMfd85XMdavgnc", uri="sip:sip-register.quintetto.it", response="c9cc56d2d5e36b0a68873c1d5258d062" Contact: <sip:quintetto00@13569868356.invalid;transport=ws>;+sip.ice;reg-id=1;+sip.instance="<urn:uuid:64e71c57-fd55-4868-be2b-a4a3fa546ac8>";expires=3600 Expires: 3600 Allow: INVITE,ACK,CANCEL,BYE,UPDATE,MESSAGE,OPTIONS,REFER,INFO,NOTIFY,SUBSCRIBE,PUBLISH Supported: path,gruu,outbound User-Agent: JsSIP 3.10.0 Content-Length: 0 SIP/2.0 *200 OK* Via: SIP/2.0/WSS 13569868356.invalid;rport=37566;received=192.168.100.192;branch=z9hG4bK7825787 To: <sip:quintetto00@sip-register.quintetto.it>;tag=2b789d0fa67ad6c2da65f0cce35dd60b.71a84df9 From: "quintetto00" <sip:quintetto00@sip-register.quintetto.it>;tag=2tnuk9btmp Call-ID: unrnseei8924hf67khoi3g CSeq: 2 REGISTER Contact: <sip:quintetto00@13569868356.invalid;transport=ws>;expires=3600;+sip.instance="<urn:uuid:64e71c57-fd55-4868-be2b-a4a3fa546ac8>";reg-id=1 Server: kamailio (5.6.2 (x86_64/linux)) Content-Length: 0 *SUBSCRIBE* sip:quintetto03@sip-register.quintetto.it SIP/2.0 Via: SIP/2.0/WSS 13569868356.invalid;branch=z9hG4bK3648599 Max-Forwards: 69 To: <sip:quintetto03@sip-register.quintetto.it> From: "quintetto00" <sip:quintetto00@sip-register.quintetto.it>;tag=o261bh2uh7 Call-ID: 4beh90hur8hdhptnbjt8 CSeq: 5813 SUBSCRIBE Proxy-Authorization: Digest algorithm=MD5, username="quintetto00", realm="sip-register.quintetto.it", nonce="Y6GU+mOhk86y3fnrMzoKgiVAdkaTvBId", uri="sip:quintetto03@sip-register.quintetto.it", response="04ca6d83661ac338810baa95ffaa568b" Event: presence Expires: 3600 Accept: application/pidf+xml, application/xpidf+xml Contact: <sip:quintetto00@13569868356.invalid;transport=ws> Content-Type: application/pidf+xml Allow: INVITE,ACK,CANCEL,BYE,UPDATE,MESSAGE,OPTIONS,REFER,INFO,NOTIFY,SUBSCRIBE,PUBLISH Supported: outbound User-Agent: JsSIP 3.10.0 Content-Length: 35 SIP/2.0 *200 OK* Record-Route: <sip:192.168.100.24:15006;transport=tcp;r2=on;lr> Record-Route: <sip:192.168.100.24:16005;transport=ws;r2=on;lr> Via: SIP/2.0/WSS 13569868356.invalid;rport=37566;received=192.168.100.192;branch=z9hG4bK3648599 To: <sip:quintetto03@sip-register.quintetto.it>;tag=c906ce7d8b5c7cc84a3505ebe369640b-e45527ec From: "quintetto00" <sip:quintetto00@sip-register.quintetto.it>;tag=o261bh2uh7 Call-ID: 4beh90hur8hdhptnbjt8 CSeq: 5813 SUBSCRIBE Expires: 3600 Contact: <sip:192.168.100.23:15006;transport=tcp> Server: kamailio (5.6.2 (x86_64/linux)) Content-Length: 0 *NOTIFY*.sip:quintetto00@13569868356.invalid;transport=ws.SIP/2.0 Via:.SIP/2.0/TCP.1 92.168.100.23:15 006;branch=z9hG4bK28ad.a5d3bdf6000000000000000000000000.0 To: <sip:quintetto00@sip-register.quintetto.it>;tag=o261bh2uh7 From: <sip:quintetto03@sip-register.quintetto.it>;tag=c906ce7d8b5c7cc84a3505ebe369640b-e45527ec CSeq : 2 NOTIFY Call-ID:.4beh90hur8h dhptnbjt8 Route : <sip:192.168.1 00.24:15006;transport=tcp;r2=on;lr>,.<sip:192.16 8.100.24:16005;transport=ws;r2=on;lr> Content-Length:.0 User-Agent: kamailio.(5.6.2.(x86_64/li nux)) Max-Forwards:.70 Event: presence Contact:.<sip:192.168.100.23:15006;transport=tcp> Subscription-State: active;expires= 3600 SIP/2.0.478.Unresolvable.destination.(478/SL) Via: SIP/2.0/TC P.192.168.100.23 :15006;branch=z9hG4bK28ad.a5d3bdf6000000000000000000000000.0;rport=38019 To:.<sip:quintetto00@s ip-register.quintetto.it>;tag=o261bh2uh7 From: <sip:quintetto03 @sip-register.quintetto.it>;tag=c906ce7d8b5c7cc84a3505ebe369640b-e45527ec CSeq: 2 NOTIFY Call-ID: 4beh90hur8hdhptnbjt8 Server :.kamailio.(5.6.2.(x86_64/linux)) Content-Length: 0 SIP/2.0.478.Unresolvable.destination.(478/TM) Via: SIP/2.0/TC P.192.168.100.23:15006;branch=z9hG4bK28ad.a5d3bdf6000000000000000000000000.0;rport=38019 To: <sip:quintetto00@s ip-register.quintetto.it>;tag=o261bh2uh7 From: <sip:quintetto03 @sip-register.quintetto.it>;tag=c906ce7d8b5c7cc84a3505ebe369640b-e45527ec CSeq: 2 NOTIFY Call-ID: 4beh90hur8hdhptnbjt8 Server : kamailio.(5.6.2.(x86_64/linux)) Content-Length: 0 -- ------------------------------------------------------------------------ Ing. Giovanni Iamonte Developments and technologies area Quintetto Srl Via Monte Navale, 1 10015 - Ivrea (TO)  mobile: +39 393 9196310  tel: +39 0165 1845290  e-mail: giovanni.iamonte(a)quintetto.it  web: www.quintetto.it

3 4

ACK received instead of Status Code
by Waqar 40 26 Dec '22

26 Dec '22

Dear All, Attached in this email, is the screenshot of Kamailio logs for a call that did not originate. When Kamailio sends the call to the media destination which is an asterisk server, it should start sending status codes 100, 183, and 180 but instead, it sends ACK and the call did not originate. This happens only for some calls and I want to know why this is happening. Also, I want to identify these cases and do some further logic like trying some other media destination. How can I do that? [image: image.png] Regards, Vicky

1 0

Re: Call drops after 1 minute
by James Browne 23 Dec '22

23 Dec '22

Hi Christian I read your trace. There's no ACK after the SIP-200 response. It's cumbersome to read the trace because the client and server are at the same IP address, but I did it anyway. There's no ACK after the SIP-200 response, so it looks like the client (213.52.37.107) either doesn't sent it, or sends it directly to the server (213.52.37.107, the same IP address) without properly using the RR header field in the SIP-200 response. If you can set up a similar test and have a different host set up for the client and server (instead of 213.52.37.107 for both), and if you then trace the traffic again at all hosts, then you may find the rogue ACK request or be able to prove that the client never sent it (which might prove a broken client). When you use the client and server at the same IP address, it's not always straightforward to trace any traffic that might go directly from client to server, because it won't leave any network interface. Also I find strange that your call ends after "about a minute or so". I expect that they should end after about 31.5 seconds. It's almost certainly a SIP problem, and not any RTP/rtpproxy problem, so I recommend that you focus on the SIP. (I wrote this message before noticing that the thread is two weeks old.) James On Wed, 7 Dec 2022 at 08:41, Henning Westerholt <hw(a)gilawa.com> wrote: > > Hello, > > > > it looks that the 200 OK is not properly transmitted, as they seem to be retransmits. > > Maybe you should read a bit about SIP if you have not done it yet. It will help you debugging this problem (and probably others in the future). 😉 > > > > Cheers, > > > > Henning > > > > -- > > Henning Westerholt – https://skalatan.de/blog/ > > Kamailio services – https://gilawa.com > > > > From: Christian B Wiik <cbw(a)itf-as.no> > Sent: Wednesday, December 7, 2022 9:13 AM > To: Henning Westerholt <hw(a)gilawa.com> > Cc: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> > Subject: Re: [SR-Users] Call drops after 1 minute > > > > Link to entire trace: > > > > https://docs.google.com/document/d/1yWFJ_Cv13p5cYk-d8m5HMBSeLalkutV0cKZHjHf… > > > > -- > > Regards > > Christian > > > > > > ons. 7. des. 2022 kl. 08:57 skrev Henning Westerholt <hw(a)gilawa.com>: > > Hi Christian, > > > > this ACK is the reply to the 407 and not the relevant one for the dialog. > > > > Please have a look to the full SIP dialog. > > > > Cheers, > > > > Henning > > > > -- > > Henning Westerholt – https://skalatan.de/blog/ > > Kamailio services – https://gilawa.com > > > > From: Christian B Wiik <cbw(a)itf-as.no> > Sent: Wednesday, December 7, 2022 8:14 AM > To: Henning Westerholt <hw(a)gilawa.com> > Cc: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> > Subject: Re: [SR-Users] Call drops after 1 minute > > > > Thanks Henning. > > > > These are the first 3 packets filtering on my user. I see the ACK but I'm not able to spot the error. > > > > U 213.52.37.107:50336 -> 10.1.2.10:5060 #1 > INVITE sip:kmm@sip2.itf-as.com SIP/2.0..Via: SIP/2.0/UDP 213.52.37.107:35270;rport;branch=z9hG4bKPj398365dc9 > 706413f868bdd222cadbed8..Max-Forwards: 70..From: <sip:cbwlap@sip2.itf-as.com>;tag=4183d760c26e4531a7a39f45d1 > 4fb4c6..To: <sip:kmm@sip2.itf-as.com>..Contact: <sip:cbwlap@213.52.37.107:35270;ob>..Call-ID: b3dd380f0c1d4e > 0ebdd7fc223710d938..CSeq: 23860 INVITE..Route: <sip:sip2.itf-as.com;lr>..Allow: PRACK, INVITE, ACK, BYE, CAN > CEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS..Supported: replaces, 100rel, timer, norefersu > b..Session-Expires: 1800..Min-SE: 90..User-Agent: MicroSIP/3.21.3..Content-Type: application/sdp..Content-Le > ngth: 345....v=0..o=- 3879388988 3879388988 IN IP4 213.52.37.107..s=pjmedia..b=AS:84..t=0 0..a=X-nat:0..m= > audio 35276 RTP/AVP 8 0 101..c=IN IP4 213.52.37.107..b=TIAS:64000..a=rtcp:35277 IN IP4 213.52.37.107..a=send > recv..a=rtpmap:8 PCMA/8000..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000..a=fmtp:101 0-16..a=ssrc > :1053777612 cname:28d400de4b7d5918.. > # > U 10.1.2.10:5060 -> 213.52.37.107:50336 #2 > SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP 213.52.37.107:35270;rport=50336;branch=z9hG4bKPj > 398365dc9706413f868bdd222cadbed8;received=213.52.37.107..From: <sip:cbwlap@sip2.itf-as.com>;tag=4183d760c26e > 4531a7a39f45d14fb4c6..To: <sip:kmm@sip2.itf-as.com>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.f003010a..Call-ID: > b3dd380f0c1d4e0ebdd7fc223710d938..CSeq: 23860 INVITE..Proxy-Authenticate: Digest realm="sip2.itf-as.com", no > nce="Y5A72WOQOq3afsXxs6AD2ihlmLAlgNOe"..Server: kamailio (5.6.2 (x86_64/linux))..Content-Length: 0.... > # > U 213.52.37.107:50336 -> 10.1.2.10:5060 #3 > ACK sip:kmm@sip2.itf-as.com SIP/2.0..Via: SIP/2.0/UDP 213.52.37.107:35270;rport;branch=z9hG4bKPj398365dc9706 > 413f868bdd222cadbed8..Max-Forwards: 70..From: <sip:cbwlap@sip2.itf-as.com>;tag=4183d760c26e4531a7a39f45d14fb > 4c6..To: <sip:kmm@sip2.itf-as.com>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.f003010a..Call-ID: b3dd380f0c1d4e0eb > dd7fc223710d938..CSeq: 23860 ACK..Route: <sip:sip2.itf-as.com;lr>..Content-Length: 0.... > > > > -- > > Regards > > Christian > > > > > > ons. 7. des. 2022 kl. 07:51 skrev Henning Westerholt <hw(a)gilawa.com>: > > Hello, > > > > as you’ve guessed, this can be a common problem related to the routing of the ACK message. > > > > Have a look e.g. with ngrep or sngrep to the SIP signalisation on the server side and check if everything is correct in the SIP messages. > > > > > > From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Christian B Wiik > Sent: Wednesday, December 7, 2022 7:43 AM > To: sr-users(a)lists.kamailio.org > Subject: [SR-Users] Call drops after 1 minute > > > > Greetings! > > > > I have a CentOS setup in AWS where all my calls are dropped after about a minute or so. I realize this typically is a NAT problem, but I can't see where my error is. > > Sound is fine both ways. > > > > Kamailio is set with WITH_NAT and I use rtpproxy like this: > > OPTIONS="-l 10.1.2.10 -s udp:127.0.0.1:7722 -d INFO:LOG_LOCAL5 -m 35010 -M 35110 -A 54.171.168.48" > > (10.1.2.10 is the local IP for CentOS) > > > > Tested with MicroSIP and Linphone and tried numerous configurations. It seems the receiving client is not able to verify the call has been set up, and disconnects. MicroSIP has the status "Connecting..." until it disconnects. > > > > All tips appreciated. Will post configuration and logs if needed. > > Kamailio version 5.6.2 from rpm and rtpproxy 2.1.0 compiled from source. > > > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions > sr-users(a)lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to the sender! > Edit mailing list options or unsubscribe: > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

1 0

Kamailio Lagging or Unreachable in Asterisk Peer
by Waqar 40 23 Dec '22

23 Dec '22

Dear All, I have three Kamailio in my production environment and I have written some code in Kamailio.cfg using SqlOps to insert data into the database on another remote server for every call. I deployed the code in one of the Kamailio and it inserted data perfectly fine into the database but as soon as I deployed it in the other two Kamailios. All three Kamailio's become unreachable or lagging in asterisk. I don't know if it has anything to do with SqlOps or queries being stuck somewhere as I am receiving logs consistently for every call in Kamailios. How can I identify if the queries are being stuck somewhere and that is why Kamailio is unreachable or lagging? Calls are not dependent on that database, this I know because even if I stop the mysql service calls will still be dialed. If it is due to the SqlOps, is there any other way to save information on every call without Kamailio being stuck? Regards VIcky

2 1

Dockerized VoIP Stack
by Terrance Devor 22 Dec '22

22 Dec '22

Hello Everyone, Does anyone have experience in deploying Kamailio, Asterisk and RTPProxy to a dockerized environment with K8s? In short, we are looking to deploy the following applications to our Kubernetes environment to support a SIP based PBX for our company: - Kamailio (Sip Proxy with DID, Outbound, edge routing and LB capabilities) - Asterisk Realtime (PBX, IVR) - RTPProxy (Media Relay) Has anyone been successful, or failed, in doing this? I would love to hear from you. Terrance

8 21

Re: sr-users Digest, Vol 211, Issue 47
by Luke Escudé 22 Dec '22

22 Dec '22

It's not easy and takes a long time to perfect, but our entire VoIP infrastructure is Dockerized, and composed of Asterisk, MySQL, Redis, NodeJS and Kamailio+RTPEngine (not rtpproxy, since rtpproxy isn't maintained anymore). No docker-level port forwarding required anywhere, since the entire system is designed to be volatile (see below). We have over 500 Asterisk docker containers running, supporting many thousands of users across the world at this point, and it works quite well, so it can be done. The concept behind the Asterisk containers is designing everything to be completely volatile: Outages happen, even in datacenters, so assume a container will reboot at some point on some random node at some random datacenter location. You don't know Asterisk's private IP, you don't even know where it might pop back up in the cluster. If you can ensure service continuity in that scenario, then you've built a solid setup. Our uptime has been 100% for over 4 years now (this is 3rd-party monitored and validated, in addition to our internal monitoring systems) so I assure you it is very possible. I also HIGHLY recommend not using a cloud provider for any of the core infrastructure. We tried this, with AWS and GCP, and the voip quality was... meh. The cloud outages were frequent, although customers generally don't notice them when you're using lightweight containers to run everything. So we are fully operating on our own hardware across multiple colo locations, and only using cloud for file storage (eFaxes, voicemails, greetings/recordings, MMS content, phone LCD background images for provisioning, etc). I am unable to help with your project, but I can at least provide the above pointers/experiences in case they get you in the right direction. An alternative to building your own infrastructure might be reselling (white label) an existing service provider as well, in case the decision to build your own infrastructure is still up in the air. Luke Escudé 972.600.1150 support(a)primevox.net Schedule a meeting!<https://outlook.office365.com/owa/calendar/PrimeVOXCommunications@primevox.…> View the PrimeVOX R&D Roadmap here<https://trello.com/b/pzpoyn8m/primevox-engineering> View the PrimeVOX Status Page here<https://status.primevox.net/> ________________________________ From: sr-users-request(a)lists.kamailio.org <sr-users-request(a)lists.kamailio.org> Sent: Thursday, December 22, 2022 9:44 AM To: sr-users(a)lists.kamailio.org <sr-users(a)lists.kamailio.org> Subject: sr-users Digest, Vol 211, Issue 47 Send sr-users mailing list submissions to sr-users(a)lists.kamailio.org To subscribe or unsubscribe via email, send a message with subject or body 'help' to sr-users-request(a)lists.kamailio.org You can reach the person managing the list at sr-users-owner(a)lists.kamailio.org When replying, please edit your Subject line so it is more specific than "Re: Contents of sr-users digest..." Today's Topics: 1. Re: Dockerized VoIP Stack (Terrance Devor) 2. Re: Dockerized VoIP Stack (Terrance Devor) 3. Re: Dockerized VoIP Stack (Terrance Devor) ---------------------------------------------------------------------- Message: 1 Date: Thu, 22 Dec 2022 09:31:33 -0500 From: Terrance Devor <ter.devor(a)gmail.com> Subject: [SR-Users] Re: Dockerized VoIP Stack To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Message-ID: <CA+w+2f8CtdwkiDtz+Md-pZz5xA4-59gv768b_vq4bkdjf2V3hw(a)mail.gmail.com> Content-Type: multipart/alternative; boundary="000000000000398ece05f06b87af" I did see the CyCore project and tried to connect with Laurel Lauson and Sean McCord on LinkedIn On Wed, Dec 21, 2022 at 9:18 PM Fred Posner <fred(a)palner.com> wrote: > On Dec 21, 2022, at 8:41 PM, Terrance Devor <ter.devor(a)gmail.com> wrote: > > > Does anyone have experience in deploying Kamailio, Asterisk and RTPProxy > to a dockerized environment with K8s? > > > Check out some past Kamailio World and Astricon presentations, including > some from Sean McCord. He even has a GitHub demo: > > * https://github.com/CyCoreSystems/asterisk-k8s-demo > > -- Fred > The Palner Group, Inc. > +1 (212) 937-7844 > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions > To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: >

2 1

Which KEMI-language has the lowest runtime overhead?
by Дилян Палаузов 22 Dec '22

22 Dec '22

Hello, KEMI can be programmed in Java, JavaScript, Lua(sr), Squirrel, Mono, Perl, Python(2,3,3s), Ruby. Which language binding has the lowest runtime overhead in CPU-terms? How about lowest overhead in terms of RAM? Kind regards Дилян

4 3

IMS integration with AS
by Oleg Belousov 22 Dec '22

22 Dec '22

Hi. Can you please advise if existing ims implementation supports integration with ims AS (Application Server), in particular for the third party registration: - upon UE registration is completed, S-CSCF constructs Register message (which keeps all details of subscriber register message) and submits it to AS server as regular SIP-message (TS 24.229 5.4.1.7 Notification of Application Servers about registration status). S-CSCF obtains AS address from SAA (Server Assignment Answer) diameter message, received from HSS upon successful registration. -- obelousov.tel

2 2

How to make a branch trigger persistent (still being active after failure route is triggered)?
by Benoît Panizzon 20 Dec '22

20 Dec '22

Hi List Some time ago, during my learning curve with kamailio, I learned that a branch route is where you make modifications to callerId's. So I extensively re-engineered the config to move as much as possible of callerid modification into branch routes. But now I discovered, when a call is dispatched via dispatch group with multiple destinations and one destination fails, therefore the failure route is triggered, the branch route is not being called on the second attempt, thus callerid being in the wrong format. Example: dispatcher.lst As an example, consider having dispatcher group 2001 for national traffic over two dedicated links and Dispatcher group 2002 for international traffic. 2001 sip:192.168.1.1:5060 0 0 name="Carrier1" 2001 sip:192.168.2.1:5060 0 0 name="Carrier1" 2002 sip:192.168.1.3:5060 0 0 name="Carrier2" request_route { # We determine where we want to send the call # and choose dispatch group 2001, the 'national' one. # But there are are other dispatch groups and branch triggers # set this way and routed to DISPATCHCALL $avp(dispgroup) = 2001; t_on_branch("BR_TO_NATIONAL"); route(DISPATCHCALL); } route[DISPATCHCALL] { t_set_fr(120000,1500); # Fast Failover t_set_max_lifetime(300000,0); t_set_retr(200,800); if (ds_select_dst("$avp(dispgroup)", "6")) { if (ds_is_from_list(-1,0,"$du")) { t_on_failure("DISPATCH_FAILURE"); route(RELAY); } } } branch_route[BR_TO_NATIONAL] { # Here I make sure, all CallerId and Header are correct for the # national Carrier } failure_route[DISPATCH_FAILURE] { if (t_check_status("(5[0-9][0-9])") or (t_branch_timeout() and !t_branch_replied())) { # Try next DS. if (ds_next_dst()) { xlog("L_INFO", " --> retargeting request\n"); t_on_failure("DISPATCH_FAILURE"); route(RELAY); #### RIGHT HERE! exit; } } # We fail xlog("L_ERROR", "Call Failed\n"); } My issue is not, that if the call is routed after the first path failed (marked with #### RIGHT HERE!) then the appropriate branch route is not triggered again and the headers are wrong. But I can not set t_on_branch within route[DISPATCHCALL] or route[DISPATCH_FAILURE] because this is called with a different pre-set branch trigger, depending on the target dispatch group. Is there a way to make a branch trigger more persistent? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

4 7

Topoh module not decoding the BYE received from the callee
by Michel Pelletier 20 Dec '22

20 Dec '22

Hello, I am using the topoh module and it works fine except for the BYE requests coming from the callee (the person receiving the call). When a BYE is received from the destination of the call, then Kamailio relays it to the dummy IP 127.0.0.8. This is exemplified in the topoh:msg-outgoing and topoh:msg-sending events where the $sndto(ip) is set to 127.0.0.8. I am using all default modparams with topoh. The only modparam I have is for setting the event_callback. I am using Kamailio 5.6.2 with Kemi using python3. Michel Pelletier

2 3

dialog_vars accumulating in database?
by Benoit Panizzon 20 Dec '22

20 Dec '22

Hi List I noticed that the database is accumulating entries on dialog_vars. I don't know when and why this is happening. Are there any special measures that have to be taken like making sure to unset variables after using them to prevent this? Or is this something which is supposed to happen when kamailio is restarted? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 5

How to unset_dlg_profile in request_route or react more quickly to CANCEL?
by Benoit Panizzon 20 Dec '22

20 Dec '22

Hi List Testing failure situations, I discovered unset_dlg_profile can not be used in request_route: I count the channels per customer in a dlg_profile to know when they are busy. Residential POTS customer have 1 channel. Now this situation (Trying to mimik POTS behavior) Kamailio <=> CPE of 'John-Doe' => INVITE set_dlg_profile of John-Doe is 0: Not busy set_dlg_profile of John-Doe +1 <= 100 trying <= 180 ringing == LINK to CPE DISRUPTED == X<= 200 OK (not reaching kamailio) CPE is sending 200 a couple of times and fails. Caller is still hearing ringing tone as it never got 200 OK. The caller does not want to wait longer and hangs up =>X CANCEL (NOT reaching CPE) This is the moment, on which I would like to unset_dlg_profile of John-Doe to mark his channel available again. But the CPE is never going to acknowledge this CANCEL with 487. Unfortunately: unset_dlg_profile(): dialog delete profile cannot be used in request route Only when kamailio has sent CANCEL a couple of times and the failure_route for this CANCEL is triggered, I can remove the call from the dlg_profile of that customer within failure_route. If I am unlucky, in the meantime other calls get 'busy' instead of being re-routed to the configured backup number of that customer. Agreed, after a couple of seconds, the call goes to the failure route and the dialogue is ending thus calls work as expected. But wouldn't it be nice to be able to unset the dlg_profile upon receiving the CANCEL instead on when the CANCEL transaction is successful? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 2

DNS Host-Names in Via and Record-Route for more redundancy?
by Benoit Panizzon 20 Dec '22

20 Dec '22

Hi Folks We use two 'core' instances and two 'registrar' instances. The pairs sync their information (Dialogues + Locations) via DMQ. But I noticed that they record the Via and Record-Routes by IP addresses. So I guess if one fails, signaling would not automatically switch to the remaining host as the IP of the failed one is in the header, right? So, is there a way to put a DNS resolvable host-name in the Via and Record-Route header, so that DNS round-robin would make sure requests reach the available server if one of the pairs fails? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 6

Multiple websocket connections with the same port
by Benjamín Visón 19 Dec '22

19 Dec '22

Hello! I'm examining the WebSocket module and I am wondering how it handles multiple connections from the same port. For context, imagine the following scenario: UA1 ==> Load Balancer:41914 ==> Kamailio (WS) UA2 ==> Load Balancer:41914 ==> Kamailio (WS) Now, imagine Kamailio perceives UA1 from port 41914. What happens if that UA1 suddenly drops and another UA2 comes in from the same port? (before the connection closed event is fired for UA1) I understand by looking at the source code that `wsconn_add` is called and that this new connection is added to the list. But what happens with the previous UA entry? does it gets overwritten or does it stays there? The reason for my question is: I am perceiving the above scenario like this: Let's say UA1 is *sip:d3315cf8@9a431b1f90e5.invalid;transport=ws SIP/2.0* and UA2 is *sip:asd08a08@555343439666.invalid;transport=ws. *If UA2 comes in and takes over the port that UA1 was using, and I send an INVITE to UA1 UA2 ends up receiving the invite (obviously because it now has that port allocated). So what I am thinking is that both *d3315cf8(a)9a431b1f90e5.invalid *and *asd08a08(a)555343439666.invalid *are mapped to the same port for a short period of time. Thoughts? Saludos, [image: Twitter] <https://twitter.com/benjaminvison>[image: Instagram] <https://instagram.com/bvisonl/> Benjamín Visón / IT Engineer / Software Developer bvisonl(a)gmail.com / (829)-664-5163 https://www.linkedin.com/in/bvisonl/

3 2

auth_challenge() and async
by Alex Balashov 19 Dec '22

19 Dec '22

Hi, Is there any good solution for the scenario of an auth_challenge() with two separate transaction suspensions? To clarify (simplified): request_route { ... t_newtran(); if(!is_present_hf("Authorization") && !is_present_hf("Proxy-Authorization")) { auth_challenge("$fd", "1"); exit; } # TM suspend/continue t_newtran(); async credentials query("RESUME_AUTH"); } route[RESUME_AUTH] { # Credentials received into PVs. if(!pv_auth_check("...")) { auth_challenge("$fd", "1"); exit; } # Create transaction shell if not exists already from auth query. if(!t_lookup_request()) t_newtran(); # TM suspend/continue async route query("RESUME_ROUTING"); } route[RESUME_ROUTING] { # Unmarshal etc. t_relay(); # etc. } What happens here is that the first auth_challenge() results in a retransmission of its 407 challenge without absorbing the negative ACK. This is despite the ostensibly stateful behaviour of auth_challenge() without "force_stateless_reply" enabled. In this case, it eclipses the second, unrelated 407 challenge from the subsequent routing query (407 challenge with +1 CSeq): -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 17

Dealing with failed SRV peers
by Sebastian Damm 17 Dec '22

17 Dec '22

Hi, we have some Kamailios working as outboundproxy. So they get requests from internal systems and send them to different providers. From time to time, one provider returns a server as primary resource which is currently unavailable. I guess if the internal systems connected directly to the target, they would remember the failed server and remember to always use the server with second priority at least until DNS refresh time. In our setup, since every request is "new" for Kamailio, it doesn't remember, which host is reachable or not. Example: target: example.com _sip._udp.example.com SRV resolves to: 10 192.0.2.42 5060 20 198.51.100.42 5060 30 203.0.113.42 5060 192.0.2.42 is unavailable. Still, Kamailio uses it for every new request and failover to 198.51.100.42 occurs only after timeouts hit. Is there a best practice for solving this? I have played around with the dst_blocklist settings, but that caused even more trouble because Kamailio started blocking requests to peers that have only one server in the record having a short hickup. Thanks in advance for every input, as this is causing trouble every time we run into such a situation. Regards, Sebastian

4 7

Redundancy
by Jawaid Bazyar 16 Dec '22

16 Dec '22

Hi, I am exploring different redundancy / load-balancing models for a Kamailio cluster. When I say cluster, I mean, a number (N) of Kamailio nodes acting as stateful proxies. Each node is configured the same as the others, and all have access to the same lookup data to make routing decisions. I would appreciate any advice or experience any of you can share on these different models. Overall model: Direct to proxies Redirect servers first, which redirect to proxies Selecting the first node to talk to. Each model could use either type of selection. DNS-based (SRV or NAPTR, client makes call to dns name) Anycast with ECMP (equal-cost multi-path routing) Cluster with a mobile IP and service-down detection (this would just provide 1:1 protection) Have clients make calls through the proxy using a DNS record containing an SRV record for each node (or, alternatively, done with NAPTR). Would rely on the client to switch nodes in the event of a node failure mid-call. (Is that even possible?) Anycast would only work with UDP signaling. Use Anycast to find the first proxy, then use stateful responses to direct client back to same node for subsequent messages in a dialog. So for anyone who has tried any of these methods, I would love to hear the pros and cons.. Thanks in advance! Jawaid

2 4

Must openssl_mutex_shared.so be preloaded?
by Дилян Палаузов 16 Dec '22

16 Dec '22

Hello, The documentation on using openssl_mutex_shared.so is contradicting. https://github.com/kamailio/kamailio/blob/master/src/modules/tls/README#L293 says: > For OpenSSL (libssl) v1.1.x, it is required to preload 'openssl_mutex_shared' library shipped by Kamailio. For more details see 'src/modules/tls/openssl_mutex_shared/README.md'. https://github.com/kamailio/kamailio/blob/master/src/modules/tls/utils/open… says: > IMPORTANT: the workaround of using this preloaded shared library is no longer needed starting with Kamailio v5.3.0-pre1 (git master branch after September 14, 2019). The code of this shared library has been included in the core of Kamailio and the same behaviour is now achieved by default. It is unclear, if openssl_mutex_shared.so must be preloaded. In case the library is not needed anymore, it shall not be compiled and installed. Kind regards Дилян

1 1

Logs suddenly inundated with qm_malloc errors
by George Diamantopoulos 16 Dec '22

16 Dec '22

Hello all, I'm testing out release 5.6.2 on one production kamailio instance, and today our monitoring system triggered an alarm for lack of disk space on /. Indeed, kamailio.log started growing at an alarming rate at some point. At about the same time disk space started being depleted, the following line was frequently logged in the logs (no instances of it before that time): qm_malloc(): qm_malloc(0x7f5ade9c0010, 536) called from rtpengine: bencode.c: __bencode_piece_new(79), module: rtpengine; Free fragment not found! They don't only concern rtpengine, core has produced similar "free fragment not found" errors as well. There's additional multiple "had header field", "bad header" and "invalid header name" errors appearing after that too, but I'm guessing that's only a symptom of the qm_malloc issue? kamailio is started with -m 2048 -M 16 and there's another instance with almost identical traffic and configuration, but running on 5.6.1, which has never exhibited such failures in several months uptime. So I'm wondering, is there anything in 5.6.2 that could explain this? Thanks! Best regards, George

3 4

NAT issues with Kamailio + Asterisk with 2 NICs
by Sergio Charrua 15 Dec '22

15 Dec '22

Hi all! Got a random issue with NAT which I really have no clue how to solve. Setup is as follows: - Client A sends SIP INVITE through Public IP 1.2.3.4, where a Cisco Firewall forwards NATed data to a Kamailio instance (acting as a SIPProxy with dispatcher) listening with internal address 192.168.0.1 on port 5060. RTPEngine is in the same server and address too. - Kamailio will forward the invite to Asterisk NIC 1 (192.168.0.2) which will do some provisioning and accounting stuff and redirect the call (if authorized) to Client B's public IP address (all clients are outside the network, reachable via WWW) using NIC 2 (192.168.1.2) and public address 4.3.2.1. The issue is that from time to time, calls will not have audio. Here is what I have found: - when Client A sends INVITE, Asterisk NIC 1 will reply SIP 183 with SDP IP Address set to the internal IP of NIC 1 (192.168.0.2) - when Asterisk forwards call to Client B public IP address the SDP IP address is 192.168.1.2 (NIC 2) And I think the issue is the SDP address is wrong: when Asterisk forwards call to Client B, the SDP address should be the public IP 4.3.2.1 but it sends 192.168.1.2. And when Asterisk replies to Kamailio the SDP is 192.168.0.1. Correct me if I am wrong but i think the solution should be: - when Kamailio receives a reply from Asterisk to be forwarded to Client A, it should modify the SDP address to public IP 1.2.3.4 - when Asterisk forwards call to Client B, the sip.conf should have the parameter externip set to the public IP 4.3.2.1 Questions: - are my analysis & solution correct? - is there an example of the above setup where I could get some ideas? - how do I set Kamailio to modify the SDP address for me? Any examples? Thanks in advance. *Sérgio Charrua*

2 1

kamailio.org server maintenance - Dec 14, 2022 (tomorrow)
by Daniel-Constantin Mierla 15 Dec '22

15 Dec '22

Hello, not that tomorrow, Dec 14, 2022 starting after 09:00UTC (10:00Berlin), is planned some maintenance work on kamailio.org server. It will be unavailable from time to time, hopefully not for long time. Affected services: - web site - mailing lists - wiki site (alternative use the github repo: https://github.com/kamailio/kamailio-wiki) - html version of modules' documentation (text variant README is every module folder of git clones or on github.org repository) Short notifications will be sent when it starts and ends. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 2

Failover - how does it work?
by Jawaid Bazyar 15 Dec '22

15 Dec '22

I have the following basic script: request_route{ record_route(); $var(enumres) = enum_query(); switch( $var(enumres) ) { case -1: xlog("enum_query lookup failure - To URI $tU"); sl_reply("503", "Temporary lookup failure"); return(0); case 1: break; # uri replaced } xlog("INVITE ENUM query - To URI $tU"); t_relay(); I have the following ENUM records for a test setup: ;; ANSWER SECTION: x.x.x.1.5.1.8.3.0.3.1.e164.arpa. 60 IN NAPTR 100 10 "U" "E2U+sip" "!^.*$!sip:+13038151xxx@10.20.20.198!" . x.x.x.1.5.1.8.3.0.3.1.e164.arpa. 60 IN NAPTR 110 10 "U" "E2U+sip" "!^.*$!sip:+13038151xxx@10.20.20.75!" . What happens is the following: tcpdump: listening on ens3, link-type EN10MB (Ethernet), capture size 262144 bytes 17:57:19.961041 IP (tos 0x10, ttl 64, id 59648, offset 0, flags [none], proto UDP (17), length 1481) 10.20.20.40.5060 > 10.20.20.198.5060: SIP, length: 1453 INVITE sip:+13038151xxx@10.20.20.198 SIP/2.0 … 17:57:19.961058 IP (tos 0x10, ttl 64, id 24143, offset 0, flags [none], proto UDP (17), length 1480) 10.20.20.40.5060 > 10.20.20.75.5060: SIP, length: 1452 INVITE sip:+13038151xxx@10.20.20.75 SIP/2.0 … These basically go out at the same time. Eventually I get a ICMP Port Unreachable on the .198 one because that’s a dummy I just set up for testing. My question is, with this kind of setup, is there a way to tell Kamailio to respect the NAPTR order value (note, 100, 110 above) and only try the 2nd route if the first fails? Thanks, Jawaid

2 5

testing mailing list
by Daniel-Constantin Mierla 14 Dec '22

14 Dec '22

after mailing list service upgrade - ignore!! -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

None
by None 14 Dec '22

14 Dec '22

ACK messages SER keeps sending the 487 Request cancelled message as if the ACK didn't match. Any suggestion of what it can be? I'm using as the endpoint an ATA186, v2.15, and ser version 0.8.11. Best Regards, Alejandro _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers ------=_NextPart_000_0009_01C322CD.41C9F360 Content-Type: text/plain; name="remote.ata.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="remote.ata.txt" interface: eth0 (200.75.73.0/255.255.255.0) filter: ip and ( port 5060 ) # U 200.75.73.22:5060 -> 200.75.91.137:5060 INVITE sip:2001@200.75.91.137:5060;user=phone;transport=udp SIP/2.0..M ax-Forwards: 10..Record-Route: <sip:2001@200.75.73.22;branch=0>..Via: SIP/2.0/UDP 200.75.73.22;branch=z9hG4bK6258.c171e2f6.0..Via: SIP/2.0/U DP 192.168.0.15:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=9 28411572..To: <sip:2001@vozsobreip.biz;user=phone>..Call-ID: 329755117 1@192.168.0.15..CSeq: 1 INVITE..Contact: <sip:1010@200.75.73.22:5061;u ser=phone;transport=udp>..User-Agent: Cisco ATA 186 v2.15 ata18x (030 122a)..Expires: 300..Content-Length: 245..Content-Type: application/sd p....v=0..o=1010 8066 8066 IN IP4 192.168.0.15..s=ATA186 Call..c=IN IP 4 200.75.73.22..t=0 0..m=audio 20002 RTP/AVP 4 8 0 101..a=rtpmap:4 G72 3/8000/1..a=rtpmap:8 PCMA/8000/1..a=rtpmap:0 PCMU/8000/1..a=rtpmap:101 telephone-event/8000..a=fmtp:101 0-15.. # U 200.75.91.137:5060 -> 200.75.73.22:5060 SIP/2.0 100 Trying..Via: SIP/2.0/UDP 200.75.73.22;branch=z9hG4bK6258.c 171e2f6.0..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip:1010@vozsobr eip.biz;user=phone>;tag=928411572..To: <sip:2001@vozsobreip.biz;user=p hone>;tag=3742565922..Call-ID: 3297551171@192.168.0.15..CSeq: 1 INVITE ..Server: Cisco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0.... # U 200.75.91.137:5060 -> 200.75.73.22:5060 SIP/2.0 180 Ringing..Via: SIP/2.0/UDP 200.75.73.22;branch=z9hG4bK6258. c171e2f6.0..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip:1010@vozsob reip.biz;user=phone>;tag=928411572..To: <sip:2001@vozsobreip.biz;user= phone>;tag=3742565922..Call-ID: 3297551171@192.168.0.15..CSeq: 1 INVIT E..Server: Cisco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0... . # U 200.75.73.22:5060 -> 200.75.91.137:5060 CANCEL sip:2001@200.75.91.137:5060;user=phone;transport=udp SIP/2.0..M ax-Forwards: 10..Via: SIP/2.0/UDP 200.75.73.22;branch=z9hG4bK6258.c171 e2f6.0..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip:1010@vozsobreip .biz;user=phone>;tag=928411572..To: <sip:2001@vozsobreip.biz;user=phon e>..Call-ID: 3297551171@192.168.0.15..CSeq: 1 CANCEL..User-Agent: Cisc o ATA 186 v2.15 ata18x (030122a)..Content-Length: 0.... # U 200.75.73.22:5060 -> 200.75.91.137:5060 ACK sip:2001@200.75.91.137:5060;user=phone;transport=udp SIP/2.0..Max- Forwards: 10..Via: SIP/2.0/UDP 200.75.73.22;branch=0..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928 411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360 b3e454593e5079b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..U ser-Agent: Cisco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0... . # U 200.75.91.137:5060 -> 200.75.73.22:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 200.75.73.22;branch=z9hG4bK6258.c171e 2f6.0..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip:1010@vozsobreip. biz;user=phone>;tag=928411572..To: <sip:2001@vozsobreip.biz;user=phone >;tag=3742565922..Call-ID: 3297551171@192.168.0.15..CSeq: 1 CANCEL..Se rver: Cisco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0.... # U 200.75.91.137:5060 -> 200.75.73.22:5060 SIP/2.0 487 Request Cancelled..Via: SIP/2.0/UDP 200.75.73.22;branch=z9 hG4bK6258.c171e2f6.0..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip:1 010(a)vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@vozsobreip .biz;user=phone>;tag=3742565922..Call-ID: 3297551171@192.168.0.15..CSe q: 1 INVITE..Server: Cisco ATA 186 v2.15 ata18x (030122a)..Content-Le ngth: 0.... # U 200.75.73.22:5060 -> 200.75.91.137:5060 ACK sip:2001@200.75.91.137:5060;user=phone;transport=udp SIP/2.0..Via: SIP/2.0/UDP 200.75.73.22;branch=z9hG4bK6258.c171e2f6.0..From: <sip:10 10(a)vozsobreip.biz;user=phone>;tag=928411572..Call-ID: 3297551171(a)192.1 68.0.15..To: <sip:2001@vozsobreip.biz;user=phone>;tag=3742565922..CSeq : 1 ACK..User-Agent: Sip EXpress router(0.8.10 (i386/linux))..Content- Length: 0.... # U 200.75.73.22:5060 -> 200.75.91.137:5060 ACK sip:2001@200.75.91.137:5060;user=phone;transport=udp SIP/2.0..Max- Forwards: 10..Via: SIP/2.0/UDP 200.75.73.22;branch=0..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928 411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360 b3e454593e5079b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..U ser-Agent: Cisco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0... . # U 200.75.73.22:5060 -> 200.75.91.137:5060 ACK sip:2001@200.75.91.137:5060;user=phone;transport=udp SIP/2.0..Max- Forwards: 10..Via: SIP/2.0/UDP 200.75.73.22;branch=0..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928 411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360 b3e454593e5079b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..U ser-Agent: Cisco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0... . # U 200.75.73.22:5060 -> 200.75.91.137:5060 ACK sip:2001@200.75.91.137:5060;user=phone;transport=udp SIP/2.0..Max- Forwards: 10..Via: SIP/2.0/UDP 200.75.73.22;branch=0..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928 411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360 b3e454593e5079b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..U ser-Agent: Cisco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0... . # U 200.75.73.22:5060 -> 200.75.91.137:5060 ACK sip:2001@200.75.91.137:5060;user=phone;transport=udp SIP/2.0..Max- Forwards: 10..Via: SIP/2.0/UDP 200.75.73.22;branch=0..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928 411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360 b3e454593e5079b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..U ser-Agent: Cisco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0... . # U 200.75.73.22:5060 -> 200.75.91.137:5060 ACK sip:2001@200.75.91.137:5060;user=phone;transport=udp SIP/2.0..Max- Forwards: 10..Via: SIP/2.0/UDP 200.75.73.22;branch=0..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928 411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360 b3e454593e5079b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..U ser-Agent: Cisco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0... . # U 200.75.73.22:5060 -> 200.75.91.137:5060 ACK sip:2001@200.75.91.137:5060;user=phone;transport=udp SIP/2.0..Max- Forwards: 10..Via: SIP/2.0/UDP 200.75.73.22;branch=0..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928 411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360 b3e454593e5079b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..U ser-Agent: Cisco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0... . # U 200.75.73.22:5060 -> 200.75.91.137:5060 ACK sip:2001@200.75.91.137:5060;user=phone;transport=udp SIP/2.0..Max- Forwards: 10..Via: SIP/2.0/UDP 200.75.73.22;branch=0..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928 411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360 b3e454593e5079b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..U ser-Agent: Cisco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0... . exit ------=_NextPart_000_0009_01C322CD.41C9F360 Content-Type: text/plain; name="local.ata.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="local.ata.txt" interface: eth1 (192.168.0.0/255.255.255.0) filter: ip and ( port 5060 ) # U 192.168.0.15:5061 -> 200.75.73.22:5060 INVITE sip:2001@vozsobreip.biz;user=phone SIP/2.0..Via: SIP/2.0/UDP 19 2.168.0.15:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928411 572..To: <sip:2001@vozsobreip.biz;user=phone>..Call-ID: 3297551171@192 .168.0.15..CSeq: 1 INVITE..Contact: <sip:1010@200.75.73.22:5061;user=p hone;transport=udp>..User-Agent: Cisco ATA 186 v2.15 ata18x (030122a) ..Expires: 300..Content-Length: 245..Content-Type: application/sdp.... v=0..o=1010 8066 8066 IN IP4 192.168.0.15..s=ATA186 Call..c=IN IP4 200 .75.73.22..t=0 0..m=audio 20002 RTP/AVP 4 8 0 101..a=rtpmap:4 G723/800 0/1..a=rtpmap:8 PCMA/8000/1..a=rtpmap:0 PCMU/8000/1..a=rtpmap:101 tele phone-event/8000..a=fmtp:101 0-15.. # U 200.75.73.22:5060 -> 192.168.0.15:5061 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 1 92.168.0.15:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=92841 1572..To: <sip:2001@vozsobreip.biz;user=phone>..Call-ID: 3297551171@19 2.168.0.15..CSeq: 1 INVITE..Server: Sip EXpress router (0.8.10 (i386/l inux))..Content-Length: 0..Warning: 392 200.75.73.22:5060 "Noisy feedb ack tells: pid=32747 req_src_ip=192.168.0.15 in_uri=sip:2001@vozsobrei p.biz;user=phone out_uri=sip:2001@200.75.91.137:5060;user=phone;transp ort=udp via_cnt==1".... # U 200.75.73.22:5060 -> 192.168.0.15:5061 SIP/2.0 180 Ringing..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip:10 10(a)vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@vozsobreip. biz;user=phone>;tag=3742565922..Call-ID: 3297551171@192.168.0.15..CSeq : 1 INVITE..Server: Cisco ATA 186 v2.15 ata18x (030122a)..Content-Len gth: 0.... # U 192.168.0.15:5061 -> 200.75.73.22:5060 CANCEL sip:2001@vozsobreip.biz;user=phone SIP/2.0..Via: SIP/2.0/UDP 19 2.168.0.15:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928411 572..To: <sip:2001@vozsobreip.biz;user=phone>..Call-ID: 3297551171@192 .168.0.15..CSeq: 1 CANCEL..User-Agent: Cisco ATA 186 v2.15 ata18x (03 0122a)..Content-Length: 0.... # U 200.75.73.22:5060 -> 192.168.0.15:5061 SIP/2.0 200 cancelling..Via: SIP/2.0/UDP 192.168.0.15:5061..From: <sip :1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@vozsobre ip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e5079b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 CANCEL..Server: Sip EXpress router ( 0.8.10 (i386/linux))..Content-Length: 0..Warning: 392 200.75.73.22:506 0 "Noisy feedback tells: pid=32746 req_src_ip=192.168.0.15 in_uri=sip: 2001(a)vozsobreip.biz;user=phone out_uri=sip:2001@200.75.91.137:5060;use r=phone;transport=udp via_cnt==1".... # U 200.75.73.22:5060 -> 192.168.0.15:5061 SIP/2.0 487 Request cancelled..Via: SIP/2.0/UDP 192.168.0.15:5061..Fro m: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@v ozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e5079b-f4f8..C all-ID: 3297551171@192.168.0.15..CSeq: 1 INVITE..Server: Sip EXpress r outer (0.8.10 (i386/linux))..Content-Length: 0..Warning: 392 200.75.73 .22:5060 "Noisy feedback tells: pid=32746 req_src_ip=192.168.0.15 in_u ri=sip:2001@vozsobreip.biz;user=phone out_uri=sip:2001@200.75.91.137:5 060;user=phone;transport=udp via_cnt==1".... # U 192.168.0.15:5061 -> 200.75.73.22:5060 ACK sip:2001@vozsobreip.biz:5060 SIP/2.0..Via: SIP/2.0/UDP 192.168.0.1 5:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e50 79b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..User-Agent: C isco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0.... # U 200.75.73.22:5060 -> 192.168.0.15:5061 SIP/2.0 487 Request cancelled..Via: SIP/2.0/UDP 192.168.0.15:5061..Fro m: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@v ozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e5079b-f4f8..C all-ID: 3297551171@192.168.0.15..CSeq: 1 INVITE..Server: Sip EXpress r outer (0.8.10 (i386/linux))..Content-Length: 0..Warning: 392 200.75.73 .22:5060 "Noisy feedback tells: pid=32746 req_src_ip=192.168.0.15 in_u ri=sip:2001@vozsobreip.biz;user=phone out_uri=sip:2001@200.75.91.137:5 060;user=phone;transport=udp via_cnt==1".... # U 192.168.0.15:5061 -> 200.75.73.22:5060 ACK sip:2001@vozsobreip.biz:5060 SIP/2.0..Via: SIP/2.0/UDP 192.168.0.1 5:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e50 79b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..User-Agent: C isco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0.... # U 200.75.73.22:5060 -> 192.168.0.15:5061 SIP/2.0 487 Request cancelled..Via: SIP/2.0/UDP 192.168.0.15:5061..Fro m: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@v ozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e5079b-f4f8..C all-ID: 3297551171@192.168.0.15..CSeq: 1 INVITE..Server: Sip EXpress r outer (0.8.10 (i386/linux))..Content-Length: 0..Warning: 392 200.75.73 .22:5060 "Noisy feedback tells: pid=32746 req_src_ip=192.168.0.15 in_u ri=sip:2001@vozsobreip.biz;user=phone out_uri=sip:2001@200.75.91.137:5 060;user=phone;transport=udp via_cnt==1".... # U 192.168.0.15:5061 -> 200.75.73.22:5060 ACK sip:2001@vozsobreip.biz:5060 SIP/2.0..Via: SIP/2.0/UDP 192.168.0.1 5:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e50 79b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..User-Agent: C isco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0.... # U 200.75.73.22:5060 -> 192.168.0.15:5061 SIP/2.0 487 Request cancelled..Via: SIP/2.0/UDP 192.168.0.15:5061..Fro m: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@v ozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e5079b-f4f8..C all-ID: 3297551171@192.168.0.15..CSeq: 1 INVITE..Server: Sip EXpress r outer (0.8.10 (i386/linux))..Content-Length: 0..Warning: 392 200.75.73 .22:5060 "Noisy feedback tells: pid=32746 req_src_ip=192.168.0.15 in_u ri=sip:2001@vozsobreip.biz;user=phone out_uri=sip:2001@200.75.91.137:5 060;user=phone;transport=udp via_cnt==1".... # U 192.168.0.15:5061 -> 200.75.73.22:5060 ACK sip:2001@vozsobreip.biz:5060 SIP/2.0..Via: SIP/2.0/UDP 192.168.0.1 5:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e50 79b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..User-Agent: C isco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0.... # U 200.75.73.22:5060 -> 192.168.0.15:5061 SIP/2.0 487 Request cancelled..Via: SIP/2.0/UDP 192.168.0.15:5061..Fro m: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@v ozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e5079b-f4f8..C all-ID: 3297551171@192.168.0.15..CSeq: 1 INVITE..Server: Sip EXpress r outer (0.8.10 (i386/linux))..Content-Length: 0..Warning: 392 200.75.73 .22:5060 "Noisy feedback tells: pid=32746 req_src_ip=192.168.0.15 in_u ri=sip:2001@vozsobreip.biz;user=phone out_uri=sip:2001@200.75.91.137:5 060;user=phone;transport=udp via_cnt==1".... # U 192.168.0.15:5061 -> 200.75.73.22:5060 ACK sip:2001@vozsobreip.biz:5060 SIP/2.0..Via: SIP/2.0/UDP 192.168.0.1 5:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e50 79b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..User-Agent: C isco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0.... # U 200.75.73.22:5060 -> 192.168.0.15:5061 SIP/2.0 487 Request cancelled..Via: SIP/2.0/UDP 192.168.0.15:5061..Fro m: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@v ozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e5079b-f4f8..C all-ID: 3297551171@192.168.0.15..CSeq: 1 INVITE..Server: Sip EXpress r outer (0.8.10 (i386/linux))..Content-Length: 0..Warning: 392 200.75.73 .22:5060 "Noisy feedback tells: pid=32746 req_src_ip=192.168.0.15 in_u ri=sip:2001@vozsobreip.biz;user=phone out_uri=sip:2001@200.75.91.137:5 060;user=phone;transport=udp via_cnt==1".... # U 192.168.0.15:5061 -> 200.75.73.22:5060 ACK sip:2001@vozsobreip.biz:5060 SIP/2.0..Via: SIP/2.0/UDP 192.168.0.1 5:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e50 79b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..User-Agent: C isco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0.... # U 200.75.73.22:5060 -> 192.168.0.15:5061 SIP/2.0 487 Request cancelled..Via: SIP/2.0/UDP 192.168.0.15:5061..Fro m: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@v ozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e5079b-f4f8..C all-ID: 3297551171@192.168.0.15..CSeq: 1 INVITE..Server: Sip EXpress r outer (0.8.10 (i386/linux))..Content-Length: 0..Warning: 392 200.75.73 .22:5060 "Noisy feedback tells: pid=32746 req_src_ip=192.168.0.15 in_u ri=sip:2001@vozsobreip.biz;user=phone out_uri=sip:2001@200.75.91.137:5 060;user=phone;transport=udp via_cnt==1".... # U 192.168.0.15:5061 -> 200.75.73.22:5060 ACK sip:2001@vozsobreip.biz:5060 SIP/2.0..Via: SIP/2.0/UDP 192.168.0.1 5:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e50 79b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..User-Agent: C isco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0.... # U 200.75.73.22:5060 -> 192.168.0.15:5061 SIP/2.0 487 Request cancelled..Via: SIP/2.0/UDP 192.168.0.15:5061..Fro m: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@v ozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e5079b-f4f8..C all-ID: 3297551171@192.168.0.15..CSeq: 1 INVITE..Server: Sip EXpress r outer (0.8.10 (i386/linux))..Content-Length: 0..Warning: 392 200.75.73 .22:5060 "Noisy feedback tells: pid=32746 req_src_ip=192.168.0.15 in_u ri=sip:2001@vozsobreip.biz;user=phone out_uri=sip:2001@200.75.91.137:5 060;user=phone;transport=udp via_cnt==1".... # U 192.168.0.15:5061 -> 200.75.73.22:5060 ACK sip:2001@vozsobreip.biz:5060 SIP/2.0..Via: SIP/2.0/UDP 192.168.0.1 5:5061..From: <sip:1010@vozsobreip.biz;user=phone>;tag=928411572..To: <sip:2001@vozsobreip.biz;user=phone>;tag=0a96755a1d32d0360b3e454593e50 79b-f4f8..Call-ID: 3297551171@192.168.0.15..CSeq: 1 ACK..User-Agent: C isco ATA 186 v2.15 ata18x (030122a)..Content-Length: 0.... exit ------=_NextPart_000_0009_01C322CD.41C9F360--

1 0

None
by None 14 Dec '22

14 Dec '22

ACK messages SER keeps sending the 487 Request cancelled message as if the ACK didn't match. Any suggestion of what it can be? I'm using as the endpoint an ATA186, v2.15, and ser version 0.8.11. Best Regards, Alejandro

1 0

None
by None 14 Dec '22

14 Dec '22

/bin/sh -c 'cd /usr/local/mysql ; ./bin/safe_mysqld --user=mysql &' Gary Goodloff KALG Communications, LTD T: 402-898-4152 C: 402-208-5183 F: 413-294-3404 -----Original Message----- From: serusers-admin(a)iptel.org [mailto:serusers-admin@lists.iptel.org] On Behalf Of Todd Sent: Wednesday, May 21, 2003 5:05 PM To: Sip Questions List Subject: [Serusers] Mysql Connection Errors Ok..I have setup SER according to the guide on the iptel site. Here is a copy of what's in my ser.cfg _________________________________________ # # $Id: ser.cfg,v 1.12 2002/10/21 02:40:06 jiri Exp $ # # simple quick-start config script # # ----------- global configuration parameters ------------------------ debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E) check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) port=5060 children=4 fifo="/tmp/ser_fifo" # ------------------ module loading ---------------------------------- # Uncomment this if you want to use SQL database loadmodule "//usr/lib/ser/modules/mysql.so" loadmodule "//usr/lib/ser/modules/sl.so" loadmodule "//usr/lib/ser/modules/tm.so" loadmodule "//usr/lib/ser/modules/rr.so" loadmodule "//usr/lib/ser/modules/maxfwd.so" loadmodule "//usr/lib/ser/modules/usrloc.so" loadmodule "//usr/lib/ser/modules/registrar.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! loadmodule "//usr/lib/ser/modules/auth.so" # ----------------- setting module-specific parameters --------------- # -- usrloc params -- #modparam("usrloc", "db_mode", 0) # Uncomment this if you want to use SQL database # for persistent storage and comment the previous line modparam("usrloc", "db_mode", 2) # -- auth params -- # Uncomment if you are using auth module # #modparam("auth", "secret", "alsdkhglaksdhfkloiwr") modparam("auth", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # modparam("auth", "password_column", "password") # ------------------------- request routing logic ------------------- # main routing logic route{ # initial sanity checks -- messages with # max_forwars==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; if (len_gt( max_len )) { sl_send_reply("513", "Message too big"); break; }; # Do strict routing if pre-loaded route headers present rewriteFromRoute(); # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri=~"computergeeks.hopto.org") { if (method=="REGISTER") { # Uncomment this if you want to use digest authentication if (!www_authorize("computergeeks.hopto.org", "subscriber")) { www_challenge("computergeeks.hopto.org", "0"); break; }; save("location"); break; }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; # forward to current uri now if (!t_relay()) { sl_reply_error(); }; } _________________________________________________ The modules are all where they say they are but when I try to start SER I get this in my messages log file May 21 18:58:45 computergeeks ser: ser startup succeeded May 21 18:58:45 computergeeks /usr/sbin/ser[13089]: connect_db(): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) May 21 18:58:45 computergeeks /usr/sbin/ser[13089]: db_init(): Error while trying to connect database May 21 18:58:45 computergeeks /usr/sbin/ser[13089]: mod_init(): Error while connecting database May 21 18:58:45 computergeeks /usr/sbin/ser[13089]: init_modules(): Error while initializing module usrloc Can someone please tell me what I'm doing wrong? I've searched all over the net for information on this...I'm sure it's something simple..but I'm overlooking it. If I disable the Mysql integration is works perfect, so I'm thinking it has something to do with the mysql.so module?!? Thanks Todd ------=_NextPart_000_00B1_01C31FBD.C81364A0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <html xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dus-ascii"> <meta name=3DProgId content=3DWord.Document> <meta name=3DGenerator content=3D"Microsoft Word 10"> <meta name=3DOriginator content=3D"Microsoft Word 10"> <link rel=3DFile-List href=3D"cid:filelist.xml@01C31FBD.C730CCD0">  <style>  </style>  </head> <body lang=3DEN-US link=3Dblue vlink=3Dpurple = style=3D'tab-interval:.5in'> <div class=3DSection1> Those SQL = Errors:<o:p></o:p> <o:p> </o:p> May 21 18:58:45 computergeeks ser: ser startup succeeded May 21 18:58:45 = computergeeks /usr/sbin/ser[13089]: connect_db(): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) May 21 18:58:45 = computergeeks /usr/sbin/ser[13089]: db_init(): Error while trying to connect = database May 21 18:58:45 = computergeeks /usr/sbin/ser[13089]: mod_init(): Error while connecting = database May 21 18:58:45 = computergeeks /usr/sbin/ser[13089]: init_modules(): Error while initializing = module usrloc<o:p></o:p> <o:p> </o:p><= /p> This means that the mysql daemon is either not running or is not running on the default = port.<o:p></o:p> <o:p> </o:p><= /p> On freebsd – this is how I start my sql daemon:<o:p></o:p> From /etc/rc.local<o:p></o:p> /bin/sh = -c 'cd /usr/local/mysql ; ./bin/safe_mysqld = --user=3Dmysql &'<o:p></o:p> <o:p> </o:p> <div> Gary Goodloff KALG Communications, LTD T: 402-898-4152 C: 402-208-5183 F: 413-294-3404 <o:p></o:p> </div> -----Original = Message----- From: = serusers-admin(a)lists.iptel.org [mailto:serusers-admin@lists.iptel.org] On = Behalf Of Todd Sent: Wednesday, May 21, = 2003 5:05 PM To: Sip Questions = List Subject: [Serusers] Mysql Connection Errors <o:p> </o:p> Ok..I have setup SER according to the guide on the iptel site. Here is a copy of what's in my ser.cfg _________________________________________ # # $Id: ser.cfg,v 1.12 = 2002/10/21 02:40:06 jiri Exp $ # # simple quick-start = config script # # ----------- global = configuration parameters ------------------------ debug=3D3       &= nbsp;  # debug level (cmd line: -dddddddddd) fork=3Dyes = log_stderror=3Dno # (cmd = line: -E) check_via=3Dno # (cmd. = line: -v) dns=3Dno       &n= bsp;   # (cmd. line: -r) rev_dns=3Dno      # (cmd. line: -R) port=3D5060 = children=3D4 = fifo=3D"/tmp/ser_fifo" # ------------------ = module loading ---------------------------------- # Uncomment this if you = want to use SQL database loadmodule "//usr/lib/ser/modules/mysql.so" loadmodule "//usr/lib/ser/modules/sl.so" loadmodule "//usr/lib/ser/modules/tm.so" loadmodule "//usr/lib/ser/modules/rr.so" loadmodule "//usr/lib/ser/modules/maxfwd.so" loadmodule "//usr/lib/ser/modules/usrloc.so" loadmodule "//usr/lib/ser/modules/registrar.so" # Uncomment this if you = want digest authentication # mysql.so must be loaded = ! loadmodule "//usr/lib/ser/modules/auth.so" # ----------------- = setting module-specific parameters --------------- # -- usrloc params = -- #modparam("usrloc", "db_mode",   0) # Uncomment this if you = want to use SQL database # for persistent storage = and comment the previous line modparam("usrloc", "db_mode", 2) # -- auth params = -- # Uncomment if you are = using auth module # #modparam("auth", "secret", "alsdkhglaksdhfkloiwr") modparam("auth", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), = # uncomment also the = following parameter) # modparam("auth", "password_column", "password") # = -------------------------  request routing logic ------------------- # main routing = logic route{ # initial sanity checks -- = messages with # max_forwars=3D=3D0, or = excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; if (len_gt( max_len )) = { sl_send_reply("513", "Message too big"); break; }; # Do strict routing if = pre-loaded route headers present rewriteFromRoute(); # if the request is for = other domain use UsrLoc # (in case, it does not = work, use the following command # with proper names and = addresses in it) if (uri=3D~"computergeeks.hopto.org") { if = (method=3D=3D"REGISTER") { # Uncomment this if you = want to use digest authentication if (!www_authorize("computergeeks.hopto.org", = "subscriber")) { www_challenge("computergeeks.hopto.org", "0"); break; }; save("location"); break; }; # native SIP destinations = are handled using our USRLOC DB if = (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; # forward to current uri = now if (!t_relay()) = { sl_reply_error(); }; } _________________________________________________ The modules are all where they say they are but when I try to start SER = I get this in my messages log file May 21 18:58:45 = computergeeks ser: ser startup succeeded May 21 18:58:45 = computergeeks /usr/sbin/ser[13089]: connect_db(): Can't connect to local MySQL server = through socket '/var/lib/mysql/mysql.sock' (2) May 21 18:58:45 = computergeeks /usr/sbin/ser[13089]: db_init(): Error while trying to connect = database May 21 18:58:45 = computergeeks /usr/sbin/ser[13089]: mod_init(): Error while connecting = database May 21 18:58:45 = computergeeks /usr/sbin/ser[13089]: init_modules(): Error while initializing module = usrloc Can someone please tell me what I'm doing wrong?  I've searched all = over the net for information on this...I'm sure it's something simple..but = I'm overlooking it. If I disable the Mysql integration is works perfect, so I'm thinking it = has something to do with the mysql.so module?!? Thanks Todd <o:p></o:p> </div> </body> </html> ------=_NextPart_000_00B1_01C31FBD.C81364A0--

1 0

None
by None 14 Dec '22

14 Dec '22

stream, for such cases, is it possible? Any pointers would be great. -- Michael Vasilenko

1 0

None
by None 14 Dec '22

14 Dec '22

fgets failed: Illegal seek. It happens when 2 end points try to set up a session and one of them cancels it before any end-to-end connection is established. Has anyone found this problem before? (See attached file: cancelsegdump.tar.gz) Jaime --0__=PnXC9kr0ykdwrnb6uT2PR1PNFM05c9HrUcAPjHVL7TjiDE1fTDc3v998 Content-type: application/octet-stream; name="cancelsegdump.tar.gz" Content-Disposition: attachment; filename="cancelsegdump.tar.gz" Content-transfer-encoding: base64 H4sIAAseXj4AA+0da3PaSDKfqcp/mMuHjX0HRKM32Lg2cew912adLezsfkilVIM0Aq2FRPSI7b3a /e3XM5KwhAQIG5LYqykbBOrumenp6ackTOKZ1A3p2Iqns250Ez3bfhOwIKiy/ExIWvEdCyLGyjNB U0VNxqqkSAAvYVl5hoQdjKXU4jAiAULPAt9fOfd15x9pQ8IeliRR3keuTyzHG6Opb8UuRd1XyUH4 anobfnaT127ot2pghC781YSdBY4XJa81MaIp/NWEjcPA9c30rSZOEMBfXVg6dsIoIMHdUU1MEkcT /lJ31vQm8mfz95pY9Iaa/KU2fMT+a0Lb5oz9F6Ftx7OMGQnI1KA3Mz+I+sj2Y89Ch9bIAEx6hBwv o5UsDPq4fMU+1SIdOVMaGCBDNPhC3F30AIOPg69EmYlFnm5eVko0F6iBDDpmZAR+HBU4HQR5ipmM r6VGvhSpZFJeIFa5CdaRdn3/Kp7tiHjoGiGFrwM6c2/zfcCJ9OhjWV+towpspS4p0IumeUKZaqox PD4ygwaBH9xrfGyB2aaMyAiAhX7uFIIdTAOPZKQMk7juXm5ExiwKDoUbWRAUiyjC0d2p/QN098Gx UQ5rSqOJb919Hgzujl8MT346u7g8Gb7IkUL/u8+QsNjT7PyQ2ugF7CYSOb73YslArcCf5YhFtzN6 uHRWfyHm7+QH91f+NN84OWK4Yc7mzKkLt1SecV6ei6w+f3+5h+7HPN3UN2TejqnvP1giBFnTtIVu ZUF+Ufji3I/QKdM8X0NGtrVaWCuK+n3XZTWd7awAWdpBw9nHwNmcsvn99fD87PynPoomFE0JWGZu qRf0kxMiOp1Ft605uOeDcQ+umB2neXpvT958gNOO50Rswn3EA6kWf0Ud/r1DXOdPoL0Ka+4XtCBe jSh4BeFa7MRhAr/YdmzfMKdAxqPXyPSnUwJeyB5zkoBYuD+HpFaZyi9vFQRLZMYu9AskdF0eybKs WKomSpaiYtNSsCjII6rrKu7hVbPgYR50agEzW/zDBiyIprmzl78sYHa73c05EBkxMQ3LHa9mwXoy ExJOVtMAW3BlzAdMky/uZsDtBGK5iOh+I1i1ksev3707e7vQWR8pljgSbAntudQb6PslBGEgpCDr pULs2VhUZL0nyqps2aIiyRbGPcvSpNFIF/X1FCRZ7umarPQI0BJFVZAUSkmvJ5o6ljFRV4lGEnFt zra41g6oQSWYboGEYfpeRMzowaRYLu/BRGw3XifTNagQy3owjXDiX6/hTVWQ9TcLrENqcI2dj7ES 3ftxWYZrXfDG6DLR2zJJ0/XDbQ/zc0yD2y3TDMj1TujaAaU7Iex4IQ22vVoWmOBo28sVzyxyb6IA wcVyb7+P3hIQegIOD+waj5rctvgz6lELhbFpgvNgx+7tKo0aBK0hNf3AQkMWy21gpudpmm+Sovmb adJMpcSWzzy4BybtKnpIRMqIA86i7dNPpGt39Md0h4Pnns7OWB97u6UfAOth5+yOPZnspAZtd8Kz sw649OyMeqIEt9BBSTOxDHrjMzQ+Q+Mz7NYulyP3pGbZSt83cCZY6bLFXjbAsc1ZC/6XY1RXo4hl RNOHl3bmzkc0NUcPJ5eWnIzI3xqtbRBK0ybbGdOCnD2IkHHtRBNj5FtbIemEzJspFpTvS4tZTXCL vdBwLOpF2yCZlFC3R8/2g2sSWIbne8S8qklRYNRuWGq0XF5G+Wr0UuDKCi9ipecUJYxHU9jdXNGz 8CYERWpG4A7QoJ26CW2YjBPQsP25zfLJjtU2Q/oZ2YE/RVkZBm04goS9y5AyzYcKCnMZdMYylG7C OlRzJeIU/Oz89H0fxdaMOxN9dPHeGB7/9ubDKUtIp9rOvUWqokhKipKqxzucKLhlXc5R+whLWNCE InxIo6gAdsC+GiSg7S80cOzbQRXiqo5EVcRyvY4S0FUdlRDRhIQsDU9tG6Rjk+lLGOs1p89AHz6q lesIe5OvYkYe802rspx3n0fxXPuydFnykXXHPvEM+Bw4HQ87gUD0Zq/CNMeWJgLavFIxkCWYuciR tGxcHGoW+CxPkKSkoQvOJ1HLAS8YXsOcOK6F9sT9JFW/CJdsSyOMbRD6Purwsz/intjFqt5Vu1iR 6hHPkr11YIOgDFdKPGNLUmVRo6Rnij3J1LAqE1EaCRLVqKXJ9XpKgos6kOAE1QNkjsxSPycDFPYX KiMr2C0vsrsO8RK7L06GJTnkIgMSBjsDxTNEoqLMVRZnqjoLgjLc5utVp6eFYHAFJF+vOoDF9bo4 +xUNKdisMCpcnJNcKtJH6DC7LuQofzoOHDgH7TB0Zn0CHKR/0K4PjsOYdk2/G18VwIHhIS/mHEJ/ r8SukD87IwHEshNKLICC8blkHA7yBTowW8i3UQKBAkrMCdMMvMQ4UJZT+s0hidfQriC6ABtNmG0K eT3VdoIwQl8ckgN/bYO3nCJNw4U63gxsIAl43dVHQezNy7ChGTizKFyArpqvqKh1Z9wrrzPz2iYW k2LqwqIdXoIf/lGSPx2whRp8ZGv0B3Gm9MeqlfpUUQiGeTDvFH08XI179LyVd9gWxsGdm8PjC/r5 CAaFj6qFaWEOvN8+ywlH4DAaLvXG0WQg5N1C7gkWeLToNPIlTBw65oqd+2mCOOV6QiKHlPcAGcLl BObK5MHLMP97um4JO3nxGsWw4bJyEKN4DKsIigEdJ18BvX523E92EdbEroi7oPc0vY9VTZeODj4P hK4gHKRu4wCLgvC8tdFAQHLMK1bgAvxwL99HGxU/CfnaakBN6nzhsg5r4VLCDXi8meq4+PDm4nh4 9uZkhe6YkuCqWrQaBfKtFYiUVyBLF2q9/li+xhuqj0qBeoT6I4nZGOBLxpuXiF37lgwLotnSdQJP Y5eHzTb/Pre5vLjNq1eq3j5fssrNRufMefo7fUZnS1zFZqN/641esOdLF2r9Pl++xv/QbR5cB04C OKTskC11upU6H4ZniKX70cs56wqevqQIgvCyguVskzu2R6/7CAQMOdZARm00dv0RcbNvBPjmEvke zJ5l7U06EG7stG2kVioh1DyX54n8INURSdINhZQE5oTn3tj1pQNVkQW5Dbx6ffxzYZnSefGUHbXS zQE7pTM8PZZEFSNedyDJdUBTEnGiVXxZHAesSR51cS1TvOmVAV3f3PaR5bPO355fpOp5Ie/zJs1L jYh5xS/YRhJMx0ISY/LCFX3r2XZPfZ0OGvCMyDci4riGbxv8BsKP8qc+Em5kURwRXa7gcCWSkENS 8he68kQZu5ixwMNr62VhorXtB7sKHe0xxRSH+/3aOh8lGMzKYKF4BrRdyNBAi/Gs+PZMxRNTnPzm GcTv3kzkVpTENjocMcUwOUIDdPhnb/KTPPrZ1Gy7q2Msi5rK1uEg5QeubXK+ByOb7KyQujbqJB+Y SDowZD+MBgMmTFgaDLCEfvgBoY+FpPIndu/bwlcFi5KUGHltKys9zouMbRhRGLLOkpsuYI2diuRr ZPBBzbW3kulurskvE/W5gb7GWlUfSfktU5eJDkZcByOXjKiLVFkRRNzTVJQIAqrQGGUyycz4Z2qh vctBqjs0Qd//12ZzVWCuIEw5ClX4vpdx2w/G3VQdoJiEA6ENbyYoMLB2vM4N705oON4XsLmDgtbs HGUNXRomqxwBMui25BgUS7nn5MKFtOuEQwyJ1XXZOz9dNJWrtKy2TDU3+bTG/27yaU0+rcmnPf1t 3uTTmnxak0/7B2z0xxEWPsJt/pXyaXopn6b88/Jpnu91gHQW69VJuJWybQsB4mI2jYWXHIddH5uG Wp4fTbINPT/ZKNhGwTYK9uko2F5JweqNgm0UbKNgGwXbKNhtKFgslDRsr9Gw372GXbz/hRcPUpVA +1o7cgd3VQTk0ZtosOc57n4Zc95xyLSnMSGe5QIpdoLPFN7ZbV+s470oN8E2mu80BLoH5UmvrqIo gpQfRrlarvBquXxXLS+PuUbJJX9L0VJZnUNslsWZo2XPRfvyeQrjCfkTr5J3dv8Tm1b1+Pmj1tgw qdVFo9gGxupCz1YVvY9S84UUYCtMajKl05TvIwnnz6/mosC5iCuuOchuneG3dLjUjkoWu6nBfzNT 1dTgv+saPMa5wjQYz6ddhS/OFj+wDg+Kf16Jh+PNa/GcwNOpxp+d/3Z2uSrwWXHb1PYin1q+MRZr 6+MKoajWx+IW7i5bjbqhPi6vx3pl/PoYK7Isn+j6Gz35vY9TqXeqvVV6x1oHS/9+rHp56+HmY4qo yjfS1QymxFIwBUrzu4umdE36ni6vnV8/muy/jZhyz+JrPbe9bFuYMYVoKEIgXXm/3ZZyfjku+e2m kPfbK5TvPCKEfeCElRHoN7r6OO39jNvnLrpIn/vAHjzEoFnk9/DlqHet8kg1N79WeaRa/5xrlWvH Dj1V6gpUtrUeVprQ4WuFDlLemRYfGjo8At9Eq7fyIQVv01pY+tz25nMEFDIeCLhn2kQxOzKR9A7G ltbpgbXqwNxUZSSbGJujulMR62YONGnnnuoD/dRKaal4QsiSOBMcgjTKxJKq97CERWEbYeZI0euF mYWdIRXCTEZjszATVOrKC77x6iCTo3/NIBMvM1Zf0wzpy8zQEPps7NCTskPy4m5r7FBjhxo7tLgz 5C3aITh+sCXS72uJ8njIdy2UBLxST+Pks49SfvMljx+CMM5gz5Y0QGrYB5YXnDk0o+AHzrivi5xK H4mYdcgCfgkrjKWD1jzk1QWUGpLnLdif82D41Ye3v6Jy7fogncpazfG8dQrD66OVdZkDtmM7mt7r abqiAM6ln2As3wcHdTf589YxxNqds7d9pMuioEuiJohgzVQ40gtVeYCEvQO2IM1zPG99gI47r8cQ lvfR745n+dchGl4ev8JdGONxkoDtvOMJWPAQnrcKD25aV0q8f0pik1Ji7QTCjjyfVen149fnxyfv vnV6/YnmysvMfQR+wGPJlT/py5XunVxXysl1uUmu13t2RYb3Hiw2e+7uZf9u4Ix/3P1iTLxlTlgt fJPx2wVfoOJKqLzbVaWSFqmx38GasV8NKAz9ET1Hw1RrGz0hh6RVGAAqst+KZLzlxymfc5LzHRZI Nq2n1HAx5s/hPRkO3w+TR+8a6aN3bdCMoLGArexBuWdAfQxKIaT06hHiJQ+jDp0xbAQESi71ffIs +IVOfdiZaWyxN7sasyzP/DQwPTvFfT+qm0IBgCn5GffZBwgLsorF/NOw2QPmLXZCBylgx//xYfBM qAaShsGGs58fgWBEFmVml+/wpuSGw6O9Ocb+AEmanH+WNPuRPqZkYLXZv29eMT/VDsh4CmsdFobJ m9BF5wilEps6s6Kso2T8klhCwFUI2goEsQqBZAhyTy1hyBUYsrm8C1w1CVWp7iLjEGMzch3wPfiP NaI8a7hpSeY6Zx2o/m7izYoVkGJtSLUmJJa0Skicg+ysaq137CdDvNTktFChFXJgiymxfl8RQMG+ dh1wXUHRpQ4s/xZVebPJmVb6S0ppxmzhl1LOch/ufs4tBW6xB2cvQXzWtKY1rWlNa1rTmta0pjWt aU1rWtOa1rSmNa1pTWta05rWtG/d/g/YEn7NAKAAAA== --0__=PnXC9kr0ykdwrnb6uT2PR1PNFM05c9HrUcAPjHVL7TjiDE1fTDc3v998-- ------<80256CDA.004DFAC0.00@ruddick> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit ******************************************************************************* Important. Confidentiality: This communication is intended for the above-named person and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of the company. If it has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender immediately. Monitoring/Viruses Orange may monitor all incoming and outgoing emails in line with current legislation. Although we have taken steps to ensure that this email and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. Orange PCS Limited is a subsidiary of Orange SA and is registered in England No 2178917, with its address at St James Court, Great Park Road, Almondsbury Park, Bradley Stoke, Bristol BS32 4QJ. ******************************************************************************* ------<80256CDA.004DFAC0.00@ruddick>

1 0

None
by None 14 Dec '22

14 Dec '22

Please give me an example of their interaction. Could I use B2BUA without SER(and without any SIP proxy)? Thanks Igor Vasiliev >

1 0

Re: [SR-Users] sr-users Digest, Vol 211, Issue 8
by Pooja Yadav 13 Dec '22

13 Dec '22

Hi Daniel and Everyone, Thanks for the inputs. We understand that Kamailio is a SIP signalling server irrespective of any core. But we have seen a thread in Open5Gs community where they established the call with Kamailio IMS. Below thread is for your reference. https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/ If you have any inputs on this it is most welcome. We just want to check the feasibility of establishing voice/video call with 5G core. Your inputs will be appreciated. Thanks and regards Pooja Yadav > On 09-Dec-2022, at 4:33 PM, sr-users-request(a)lists.kamailio.org wrote: >

2 1

Delays sending over WSS
by Alex Balashov 12 Dec '22

12 Dec '22

Hi, I’ve run into stubbornly persistent problems with packets not reaching WSS clients until some seconds (5-6s or more!) after they were supposedly sent. The symptom is that Kamailio logs the event as sent at 20:00:00, including in the onsend_route, but in actual reality it takes quite a bit longer to send at the OS network stack level. This happens occasionally and quite universally, with no discernible pattern tied to particular endpoints, networks, etc. For a long time, I’ve just assumed this was a receive delay, since Kamailio logged an expectedly prompt relay time. I figured it was an application or browser execution delay and had nothing to do with networking. Based on what we know about the capriciousness of browsers and their internal task scheduling, this seemed rather plausible. However, I’ve since been able to ascertain that this is not the right understanding of the problem, because a parallel and unrelated WS keepalive, going from a different backend to the same application/browser tab/event loop, is consistently replied to in a timely manner. Anyway, I’m curious what else can be done to debug and/or fix this. I did turn up the size of my write buffers — tcp_wq_conn_max and the global one — quite a lot, some time ago and for unrelated reasons. I wonder if this might actually make the problem worse, since it leads to more bytes queued to send to an endpoint on the other side that could, conceivably, not be reading them fast enough. But I also wonder if this is tied up in some low-level TLS or WS parameters unrelated to more general TCP configuration. Thanks much! — Alex — Sent from mobile, apologies for brevity and errors.

2 2

Kamailio SIP client registration issue
by Shiva Shankar Chittallu 09 Dec '22

09 Dec '22

Hi Team, I have installed kamailio sip server 5.5.5 version in ubuntu 20.04 in AWS instance with public IP. When im trying to register an device im getting below error in the syslog. Thanks & Regards Shiva 9100663346

2 1

Does Kamailio supports Voice and Video call support for 5G Core
by Pooja Yadav 09 Dec '22

09 Dec '22

Hi Kamailio community, We just want to check does Kamailio IMS supports the functionality of Voice and Video call support (Vo5G) with 5G core? If yes, please share the document reference. Else, please guide us when it will be available. Any plans in upcoming release to support HTTP2 based SBI interface between P- CSCF and PCF. Your inputs will be highly appreciated. Thanks & Regards, Pooja Yadav

4 4

Next online devel meeting - Thu, Dec 8, 2022, 15:00UTC
by Daniel-Constantin Mierla 08 Dec '22

08 Dec '22

Hello, to summarize what happened at the devel meeting in Dusseldorf a few weeks ago and plan the next steps for the project, we are planning an online development meeting on Thu, Dec 8, 2022, 15:00UTC. As usual, one of the targets is to sketch the roadmap to next major release so the developers and community members can syncronize and plan what should be done till Kamailio v5.7 (or 6.0) will be out as well as discuss about current state of the project, look for new ideas to improve collaboration within the community, a.s.o. The meeting will be done on a matrix chat room. More details are in the wiki page of the event, available at: * https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings… Feel free to add there topics that you want to be discussed. The proposed date is Thursday, December 08, 2022, at 15:00UTC (15:00 London/Dublin, 16:00 most of West Europe, 10:00 New York), but other dates can be proposed if they suit for more participants. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda _______________________________________________ Kamailio (SER) - Development Mailing List sr-dev(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

1 3

Outgoing SIP/TLS connection error (msg_send_buffer(): tcp_send failed)
by Denys Pozniak 08 Dec '22

08 Dec '22

Hello! We use trunk with Twilio through a SIP/TLS. They establish incoming calls from random ports, like: (Twilio)3.3.3.3:54321 --> (Kamailio)2.2.2.2:5061 In case of sending in-dialog requests to them, Kamailio should establish an outgoing connection to the dst port 5061 (as per Route), like: (Kamailio)2.2.2.2 --> (Twilio)3.3.3.3:5061 But as per tcpdump traces and logs, Kamailio does not even try to establish an outgoing connection to Twilio. There should be no problems with routes and the network on that server, as regular telnet to Twilio shows that 5061 is open. What could be the reason and how to debug? *Script:* onsend_route { xlog("L_ERR","[$cfg(route)]*RELAY ONSEND* $rm / $du / $fs / $fsn / [$ci]\n"); } *Syslog:* DEBUG <core> [core/resolve.c:1259]: srv_sip_resolvehost(): 3.3.3.3:5061 proto=3 DEBUG <core> [core/resolve.c:1371]: srv_sip_resolvehost(): returning 0x55acd63a63c0 (3.3.3.3:5061 proto=3) ERROR <script>: [DEFAULT_SEND]*RELAY ONSEND* REFER / sip:3.3.3.3:5061;transport=tls / tls:10.1.1.1:5061 / sip_wan_tls / [123] DEBUG tm [../../core/forward.h:277]: msg_send_buffer(): sending to: 3.3.3.3:5061, force_socket=4, send_sock=0x7f090049b8e8 DEBUG tm [../../core/forward.h:292]: msg_send_buffer(): tcp_send failed DEBUG tm [t_fwd.c:1568]: t_send_branch(): send to 3.3.3.3:5061 (3) failed WARNING: tm [t_fwd.c:1588]: t_send_branch(): sending request on branch 0 failed DEBUG tm [t_funcs.c:335]: t_relay_to(): t_forward_nonack returned error -1 (-477) DEBUG tm [t_funcs.c:353]: t_relay_to(): -477 error reply generation delayed DEBUG sl [sl_funcs.c:558]: sl_run_callbacks(): execute callback for event type 1 *Software:* - Kamailio is listening on (+udp, +tcp): tls: 10.1.1.1:5061 name sip_wan_tls advertise 2.2.2.2:5061 - OS is Debian 11.5 - # kamailio -v version: kamailio 5.6.2 (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 - # dpkg -l | grep ssl ii libssl1.1:amd64 1.1.1n-0+deb11u3 amd64 Secure Sockets Layer toolkit - shared libraries ii openssl 1.1.1n-0+deb11u3 amd64 Secure Sockets Layer toolkit - cryptographic utility -- BR, Denys Pozniak

2 2

KAMCTL error
by Govind Swamy 08 Dec '22

08 Dec '22

[image: Error in KAMCTL.png] Hi am unable to create using kamctl

3 2

Re: [SR-Users] uac_req_send() multi-process synchronization problem
by Henning Westerholt 08 Dec '22

08 Dec '22

Hello, please keep the list in CC. Not sure what you mean by multi-process safe. The functions are safe to use in a kamailio multi-process context, relevant sections should be protected by internal locks etc.. Regarding query location manually by SQL client, its better to use the provided functions from the usrloc/registrar module instead. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: riffs(a)sina.cn <riffs(a)sina.cn> Sent: Thursday, December 1, 2022 10:47 AM To: Henning Westerholt <hw(a)gilawa.com> Subject: Re: Re: [SR-Users] uac_req_send() multi-process synchronization problem To confirm that. Are reg_fetch_contacts and unregister_ruid multi-process safe? ________________________________ riffs(a)sina.cn<mailto:riffs@sina.cn> From: riffs(a)sina.cn<mailto:riffs@sina.cn> Date: 2022-12-01 16:35 To: Henning Westerholt<mailto:hw@gilawa.com> Subject: Re: RE: [SR-Users] uac_req_send() multi-process synchronization problem Hello Thank you for your reply very much. My LOCATION is stored in the MYSQL database, and I also set the event_callback parameter of TCPOPS. modparam("tcpops", "event_callback", "ksr_tcpops_event") At the same time.I also deleted the contact inside the function function ksr_tcpops_event(evname) local tcpconnid = KSR.pv.get("$conid") or "0" if (evname == "tcp:reset" or evname == "tcp:closed") and (tonumber(tcpconnid) ~= 0) then local sql = string.format("select * from location where tcpconnid=%s", tcpconnid) local count, rows = execute_select(sql) if count > 0 then KSR.registrar.unregister_ruid("location", rows[1].contact, rows[1].ruid) end end return 1 end When I use use_req_send(), I use the following sql statement to query location string.format("select * from location where username='%s'", reciever) I think because the query sql is executed before the execution of unregister_ruid completes, the location of user A can still be queried. If unregister_ruid and reg_fetch_contacts are multi-process safe. I use reg_fetch_contacts query location to avoid this problem. Is that so? thanks very much ________________________________ riffs(a)sina.cn<mailto:riffs@sina.cn> From: Henning Westerholt<mailto:hw@gilawa.com> Date: 2022-11-30 18:18 To: Kamailio (SER) - Users Mailing List<mailto:sr-users@lists.kamailio.org> CC: 刘建峰<mailto:riffs@sina.cn> Subject: RE: [SR-Users] uac_req_send() multi-process synchronization problem Hello, not sure if I fully understand the problem. But regarding another user is registered with the same IP address as a previous user, there are several mitigations. To give two options: you could choose a really short re-registration time, you could use TCP and when you lose the connection you delete the contact. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of ??? Sent: Wednesday, November 30, 2022 2:57 AM To: sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Subject: [SR-Users] uac_req_send() multi-process synchronization problem When I use uac_req_send() to send a MESSAGE to the client. Will the following occur? The result of the message sent to user A is that B has received it. From the logs, the address of user A in the location table is the same as the IP address and port of user B, and the information of user A in the location table is not deleted in time. I took the address of user A directly from the location table without using KSR.registrar.reg_fetch_contacts(). If I use KSR.registrar.reg_fetch_contacts() can this be avoided. This is a multi-process synchronization problem, after user A registers, the IP port information in the address is 172.16.22.222:12345, and then user A disconnects the link because of some abnormal conditions, but it is not normal to cancel the registration, the socket link has failed, but it has not had time to delete the location, at this time user B registers, whether will it get the same IP port information as user A 172.16.22.222 : 12345, if possible? User A's location still exists, Using KSR.registrar.reg_fetch_contacts() TO query user A's location, and then using uac_req_send() to send a message to user A, User B will receive the MESSAGE. Whether this problem occurs? 从 Windows 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>发送

2 2

Fosdem 2023 - CfP
by Daniel-Constantin Mierla 07 Dec '22

07 Dec '22

Hello, should anyone be interested to present or just go to FOSDEM 2023, note that it is going to take place in Brussels during February 4-5, 2023. With a increasing demand on topics to be covered, many more devrooms were accepted and Real Time Communication devroom has half a day available on the afternoon of February 5, 2023. The RTC Devroom call for presentations is open, more details at; - https://lists.fosdem.org/pipermail/fosdem/2022q4/003479.html Check also the other accepted devrooms, maybe one suits better for your work with open source nowadays and you can submit proposals to them: - https://fosdem.org/2023/news/2022-11-07-accepted-developer-rooms/ Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Call drops after 1 minute
by Christian B Wiik 07 Dec '22

07 Dec '22

Greetings! I have a CentOS setup in AWS where all my calls are dropped after about a minute or so. I realize this typically is a NAT problem, but I can't see where my error is. Sound is fine both ways. Kamailio is set with WITH_NAT and I use rtpproxy like this: OPTIONS="-l 10.1.2.10 -s udp:127.0.0.1:7722 -d INFO:LOG_LOCAL5 -m 35010 -M 35110 -A 54.171.168.48" (10.1.2.10 is the local IP for CentOS) Tested with MicroSIP and Linphone and tried numerous configurations. It seems the receiving client is not able to verify the call has been set up, and disconnects. MicroSIP has the status "Connecting..." until it disconnects. All tips appreciated. Will post configuration and logs if needed. Kamailio version 5.6.2 from rpm and rtpproxy 2.1.0 compiled from source. -- Regards Christian B. Wiik

2 4

How to configure Kamailio to send only DNS A query
by Arun Kumar 07 Dec '22

07 Dec '22

Hello All, I have a setup where the DNS server is configured with only A record. When the Kamailio receives the request it performs a DNS SRV query for which it receives a response with "no such name". But later a DNS A query is sent which gets resolved and the request is forwarded. I would like to know that is there any configuration that can be done in Kamailio so that it will perform only DNS A query directly instead of SRV query? If so could you please help me know how to do it Thanks and Regards Arun

2 1

outbound Edge Proxy
by Giovanni Iamonte 06 Dec '22

06 Dec '22

Dear List In the last week I try to figure out how I can put in place a configuration that use an edge proxy and a register by using kamailio 5.6, but i am facing some issues. Scenario: We are using on ubuntu 20.04, HAproxy and Kamailio 5.6. We have configured a Kamailio register that, in the following case, perfectly works. ______ __ __________ TLS | | TLS | | Client ------------------ > | NAT |-----------> | Kamalio | in |_HAProxy | out in | Register | |_________| | | |________ _| Now we want to put a kamailio edge proxy before the kamailio Register, please take a look to the below picture ______ ______ __ _________ ___________ TLS | | TLS | | TCP | | Client ------------------ > | NAT |-----------> | Kamalio | -------------> | Kamailio | in |_HAProxy | out in | Edge | out in | Register | |_________| | Proxy | | | |_________| |___________| HAproxy -> sip-test.example.com Kamailio edge proxy -> 192.168.58.1 Kamailio Register -> 192.168.58.15 The kamailio Edge has been configured as indicated in the outbound module example. When a transaction such as REGISTER or SUBSCRIBE reach the "Kamailio Register" the Record-Route and Via headers are correct and it works. When the transaction such as MESSAGE or INVITE reach the "Kamailio Register" it does not work and below you can see the message and the error. Note that the Record-Route and Via headers are the same as the previous message REGISTER and SUBSCRIBE. Dec 6 11:57:09 qcast-webserver-dev /usr/sbin/kamailio[15340]: INFO: {1 40742 MESSAGE YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET} <script>: SIPMessage-in-request = 192.168.58.1:53606-sip:s-user.02@sip-dev.example.com-MESSAGE sip:s-user.02@sip-dev.example.com SIP/2.0 Record-Route: <sip:192.168.58.1:15006;transport=tcp;r2=on;lr> Record-Route: <sip:sip-test.example.com:16005;transport=tls;r2=on;lr> Via: SIP/2.0/TCP 192.168.58.1:15006;branch=z9hG4bKa257.add27f134dd83c78aef13ca7798f87ca.0;i=6 Via: SIP/2.0/TLS 192.168.58.1:39592;received=192.168.58.1;rport=39592;branch=z9hG4bKPjajkY.0NlW2AFuz3.BRaKH4EdvdmQTs9L;alias Max-Forwards: 69 From: <sip:s-user.03@sip-dev.example.com>;tag=VnOekkKsq4tLhFAywXzbxLXxIesWscn3 To: <sip:s-user.02@sip-dev.example.com> Call-ID: YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET CSeq: 40742 MESSAGE Accept: text/plain, application/im-iscomposing+xml Content-Type: text/plain Content-Length: 59 ################## MESSAGE ################### Dec 6 11:57:09 qcast-webserver-dev /usr/sbin/kamailio[15340]: INFO: {1 40743 MESSAGE YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET} <script>: SIPMessage-in-request = 192.168.58.1:53606-sip:s-user.02@sip-dev.example.com-MESSAGE sip:s-user.02@sip-dev.example.com SIP/2.0 Record-Route: <sip:192.168.58.1:15006;transport=tcp;r2=on;lr> Record-Route: <sip:sip-test.example.com:16005;transport=tls;r2=on;lr> Via: SIP/2.0/TCP 192.168.58.1:15006;branch=z9hG4bKb257.83b972054df1675806975159ae1f1e43.0;i=6 Via: SIP/2.0/TLS 192.168.58.1:39592;received=192.168.58.1;rport=39592;branch=z9hG4bKPjfan-Tte.vtL8brkWb20wm.5b8iuVEtQV;alias Max-Forwards: 69 From: <sip:s-user.03@sip-dev.example.com>;tag=VnOekkKsq4tLhFAywXzbxLXxIesWscn3 To: <sip:s-user.02@sip-dev.example.com> Call-ID: YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET CSeq: 40743 MESSAGE Accept: text/plain, application/im-iscomposing+xml Proxy-Authorization: Digest username="s-user.03", realm="sip-dev.example.com", nonce="Y48hMWOPIAW7JeSQ7/a+cuJ1gKwT8hrC", uri="sip:s-user.02@sip-dev.example.com", response="3b7c34476443e5f1125fa460a4981180", cnonce="3AT-ZMwyfpgaMwlulh5cq5vJHi75-wnz", qop=auth, nc=00000001 Content-Type: text/plain Content-Length: 59 Dec 6 11:57:09 qcast-webserver-dev /usr/sbin/kamailio[15340]: WARNING: {1 40743 MESSAGE YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET} <core> [core/forward.c:228]: get_send_socket2(): protocol/port mismatch (forced tcp:192.168.58.15:15006, to tls:192.168.58.1:60982) Dec 6 11:57:09 qcast-webserver-dev /usr/sbin/kamailio[15340]: ERROR: {1 40743 MESSAGE YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET} tm [ut.h:315]: uri2dst2(): no corresponding socket found for "192.168.58.1" af 2 (tls:192.168.58.1:60982) Dec 6 11:57:09 qcast-webserver-dev /usr/sbin/kamailio[15340]: ERROR: {1 40743 MESSAGE YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET} tm [t_fwd.c:471]: prepare_new_uac(): can't fwd to af 2, proto 3 (no corresponding listening socket) Dec 6 11:57:09 qcast-webserver-dev /usr/sbin/kamailio[15340]: ERROR: {1 40743 MESSAGE YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET} tm [t_fwd.c:1754]: t_forward_nonack(): failure to add branches Dec 6 11:57:09 qcast-webserver-dev /usr/sbin/kamailio[15340]: ERROR: {1 40743 MESSAGE YsfZ7Rq-WGw33NUn9AFMWEuurzryvzET} sl [sl_funcs.c:372]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (7/SL) based on what we have understood in the message headers "Via" and Record-Route" there are the right information to reach back the proxy Edge, but looking to the error message it seems that the kamailio register try to reach back the proxy edge through the TLS instead of using the TCP. Could someone put me in the right direction. Thanks Regards -- ------------------------------------------------------------------------ Ing. Giovanni Iamonte Developments and technologies area Quintetto Srl Via Monte Navale, 1 10015 - Ivrea (TO)  mobile: +39 393 9196310  tel: +39 0165 1845290  e-mail: giovanni.iamonte(a)quintetto.it  web: www.quintetto.it

2 4

Packet processing order
by Jawaid Bazyar 06 Dec '22

06 Dec '22

Hi, I have experienced out of order packet processing when testing a simple Kamailio config. The configuration is as follows, basically: request_route{ record_route(); enum_query(); xlog("INVITE ENUM query - To URI $tU"); forward(); } I saw this thread from 2020: https://www.mail-archive.com/sr-users@lists.kamailio.org/msg11786.html The issue seems to be that kamailio process scheduling is naïve – i.e., incoming SIP packets are processed without regard to whether packets received before this one, are currently being processed. This means any packets after the initial INVITE that require more processing, can get reordered. In my test lab I have: SIPp – UAC Kamailio Proxy SIPp – UAS The proxy uses enum NAPR lookups to route calls to +13038151000 to the UAS. Now, if I do SIPp UAC o SIPp UAS directly, I have no problems – no out of order packets. It is only when I introduce Kamailio in the middle that I get OOO packets. See the images attached: uac-to-proxy, proxy, and proxy-to-uas. In this example, Kamailio OOO causes SIPp UAC to fail to “generate audio” – because UAC does not see packets in the correct order, I never turns on the simulated audio. Calls that have in-order dialogs, work fine, and SIPP UAC “pauses” 10 seconds to simulate a phone call. So far, the error rate runs from 1/1000 to around 1/200 – pretty bad. In the thread, a few things were suggested. Have fewer kamailio processes than cores: Did not resolve issue. Try route_locks_size = 256 Did not resolve issue. Though, it did alter it somewhat. But, it is not clear to me how this works – would this setting restrict the number of open calls to 256? Have only one kamailio process: (“children=1”) This works. “Works”, I should say, because this would greatly restrict total platform scalability to a point where it is probably useless for my application. I saw the same issue discussed in the OpenSIPS mailing list from 2010, and the response was “this is not a bug”. Well, I respectfully beg to differ with both OpenSIPS and Kamailio – it IS a bug. I don’t think a proxy should reorder packets involved in a call in a non-deterministic way. In the Kamailio list thread, Alex Balashov discusses the contortions he has to go through to avoid repercussions from this issue. Kamailio as-is probably works fine for relatively low-volume operations. And a lot of the feedback is “why are out of order packets a problem?” OK, sure, in the very specific example given in the 2020 thread, maybe who cares. But in my thinking, there is absolutely nothing preventing Kamailio from generating much more serious OOO scenarios that would cause calls to fail. In my example, Kamailio OOO causes SIPp to fail to “generate audio”. Who knows how other SIP stacks will behave? But the more one will try to scale Kamailio, the more significantly this out of order processing issue will become. The solution to this seems very simple and straightforward – put packets to be processed into a queue PER Call-ID, or something along those lines. In short, the parallelism should be by call, not by packet. What say ye? Have I misunderstood something here? Cheers, Jawaid

4 11

Database Failure Detection at runtime
by Waqar 40 06 Dec '22

06 Dec '22

Hello Everyone, I am using Kamailio sqlops module to write to a remote database which is not the database of Kamailio. It is working fine. But for redundancy purpose, if this database goes down, I want the Kamailio to detect the failure at runtime and write the data to another database (standby database). Is it possible? Can anybody please guide me on this asap? Regards, Vicky

3 3

ds_is_from_list not matching dispatcher listed with hostname
by Benoît Panizzon 03 Dec '22

03 Dec '22

Hi On our devevelpment system, we have this dispatcher list: 3200 sip:reg1.dev.example.com:5060 0 0 name="Registrar01"; 3200 sip:reg2.dev.example.com:5060 0 0 name="Registrar02"; The names or course are in the DNS: A,AAAA and PTR. ds_is_from_list() returns the groupId 3200 Now I have started building the production system... 3200 sip:reg1.prod.example.com:5060 0 0 name="Registrar01"; 3200 sip:reg2.prod.example.com:5060 0 0 name="Registrar02"; DNS ist set up the same. I have double-checked: Names and IP addresses do resolve as they should. ds_is_from_list() returns nothing. I have also sniffed the connection. The ip addresses in the packets are the ones I expect. modparam("dispatcher", "ds_ping_from", "sip:survivability@sip.example.com") pings the machines and is getting answers. What else could cause this not to match? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 2

imc sends all messages with Content-Type: text/plain
by Joey Golan 02 Dec '22

02 Dec '22

Hello, I'm checking the imc module and it appears that imc sends all messages with hard-coded content type header so if client sends an application/im-iscomposing+xml message, other clients receives the message with content-type text/plain which is very confusing. I think the right behavior is to take the content-type header from the original message and use it in the messages imc sends. Is there a workaround that might help me achieve that?

3 3

RLS is not sending Notify on resource list updated
by Lewis Hutchinson 01 Dec '22

01 Dec '22

Have you confirmed if the NOTIFY is sent? Attempted to be sent? Noticed you said "but no NOTIFY is received" -----Original Message----- From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of sr-users-request(a)lists.kamailio.org Sent: 19 November 2022 11:00 To: sr-users(a)lists.kamailio.org Subject: sr-users Digest, Vol 210, Issue 19 Send sr-users mailing list submissions to sr-users(a)lists.kamailio.org To subscribe or unsubscribe via the World Wide Web, visit https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.kam… or, via email, send a message with subject or body 'help' to sr-users-request(a)lists.kamailio.org You can reach the person managing the list at sr-users-owner(a)lists.kamailio.org When replying, please edit your Subject line so it is more specific than "Re: Contents of sr-users digest..." Today's Topics: 1. RLS is not sending Notify on resource list updated (Joey Golan) ---------------------------------------------------------------------- Message: 1 Date: Fri, 18 Nov 2022 21:33:29 +0200 From: Joey Golan <joeygo(a)gmail.com> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Subject: [SR-Users] RLS is not sending Notify on resource list updated Message-ID: <CAAOPBYfHikYXKSRga5Mnf+fgUisrDk5PgHoCZ7anMgqqAmnU-w(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello, I'm using Kamailio v5.6.2 with presence, presence_xml, xcap_server, and rls modules. I pushed 2 documents to the xcap server: 1. urn:ietf:params:xml:ns:resource-lists <?xml version="1.0" encoding="UTF-8" standalone="no"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists"> <list name="friends"> <entry uri="sip:1001@example.com"> <display-name>1001</display-name> </entry> <entry uri="sip:1002@example.com"> <display-name>1002</display-name> </entry> </list> </resource-lists> 2. urn:ietf:params:xml:ns:rls-services <?xml version="1.0" encoding="UTF-8" standalone="no"?> <rls-services xmlns="urn:ietf:params:xml:ns:rls-services" xmlns:rl="urn:ietf:params:xml:ns:resource-lists" xmlns:xsi=" https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org…"> <service uri="sip:1000+presence@example.com"> <resource-list> https://kamailio:5061/xcap-root/resource-lists/users/sip:1000@example.com/i… "friends"]</resource-list> <packages> <package>presence</package> </packages> </service> </rls-services> I'm subscribing to presence event on rls-service SUBSCRIBE sip:1000+presence@example.com SIP/2.0 Via: SIP/2.0/TLS 10.255.0.3:33883 ;rport;branch=z9hG4bKPjbe079f60-d0e0-4f1e-9f93-b18e467be5e8;alias Max-Forwards: 70 From: "1000" <sip:1000@example.com>;tag=97ef0748-da39-442f-9a02-468b67134ad6 To: <sip:1000+presence@example.com> Contact: <sip:20416583@10.255.0.3:5061;transport=tls> Call-ID: 9773a68c-b001-49f0-9ffa-093beb3d8e36 CSeq: 18636 SUBSCRIBE Event: presence Expires: 600 Supported: 100rel, replaces, norefersub, gruu Accept: multipart/related, application/rlmi+xml, application/pidf+xml Allow-Events: presence Supported: eventlist User-Agent: sipsimple 5.2.6 Content-Length: 0 The RLS sends a NOTIFY immediately upon accepting the subscription according to RFC 4662 and also the RLS is virtually subscribing to the presence event on the 2 resources in the friends list NOTIFY sip:20416583@10.255.0.3:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS joey-local-proxy.example.com:5061 ;branch=z9hG4bKa93d.b63e0697000000000000000000000000.0 To: <sip:1000@example.com>;tag=97ef0748-da39-442f-9a02-468b67134ad6 From: <sip:1000+presence@example.com >;tag=e02a02cb113b2bdb8ebdb022d767e6d2-a1677c19 CSeq: 1 NOTIFY Call-ID: 9773a68c-b001-49f0-9ffa-093beb3d8e36 Content-Length: 468 Max-Forwards: 70 Event: presence Contact: <sip:kamailio@example.com:5060> Subscription-State: active;expires=600 Require: eventlist Content-Type: multipart/related;type="application/rlmi+xml";start="<1668755827.sip:1000+presence@example.com.1700642067 >";boundary="1W1NaaaIIq6dOtLRXODFwqmC" --1W1NaaaIIq6dOtLRXODFwqmC Content-Transfer-Encoding: binary Content-ID: <1668755827.sip:1000+presence@example.com.1700642067> Content-Type: application/rlmi+xml;charset="UTF-8" <?xml version="1.0"?> <list uri="sip:1000+presence@example.com" xmlns="urn:ietf:params:xml:ns:rlmi" version="1" fullState="true"> <resource uri="sip:1001@example.com"/> <resource uri="sip:1002@example.com"/> </list> --1W1NaaaIIq6dOtLRXODFwqmC-- Now I?m changing the resource list using XCAP. I?m sending a PUT request with a new document and I see that the change is pushed to the DB but user 1000 is not receiving a NOTIFY with the updated list. This is the updated document: <?xml version="1.0" encoding="UTF-8" standalone="no"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists"> <list name="friends"> <entry uri="sip:1001@example.com"> <display-name>1001</display-name> </entry> <entry uri="sip:1002@example.com"> <display-name>1002</display-name> </entry> <entry uri="sip:1003@example.com"> <display-name>1003</display-name> </entry> </list> </resource-lists> I see that Kamailio is virtually subscribing on 1003 (The newly added user) but NOTIFY is not received. Also tried to subscribe on xcap-diff event, and the subscription was accepted successfully but no NOTIFY is received. Am I missing something? Thanks, Joey

1 0

Unable to install kamailio-mysql on CentOS 9
by Shailendra Paliwal 01 Dec '22

01 Dec '22

Hello, I'm trying to set up kamailio on a Cent OS 9 server but I'm unable to install the kamailio-mysql module. Can someone suggest any possible solutions here, Tried to setup kamdbctl after changing the configuration to use mysql, ➜ ~ kamdbctl create ERROR: could not load the script in /usr/lib64/kamailio//kamctl/kamdbctl.mysql for database engine MYSQL ERROR: database engine not loaded - tried 'MYSQL' Contents of /usr/lib64/kamailio/kamctl/, I'm not sure why there's a double slash in the message above ➜ ~ ls /usr/lib64/kamailio/kamctl/ dbtextdb kamctl.base kamctl.ctlbase kamctl.dbtext kamctl.rpcfifo kamctl.ser kamctl.sqlbase kamdbctl.base kamdbctl.dbtext I'm unable to install kamailio-mysql ➜ ~ dnf install kamailio-mysql Last metadata expiration check: 0:00:23 ago on Thursday 01 December 2022 03:53:45 AM. Error: Problem: conflicting requests - nothing provides libmysqlclient.so.21()(64bit) needed by kamailio-mysql-5.6.2-0.el9.centos.x86_64 - nothing provides libmysqlclient.so.21(libmysqlclient_21.0)(64bit) needed by kamailio-mysql-5.6.2-0.el9.centos.x86_64 - nothing provides mysql-libs needed by kamailio-mysql-5.6.2-0.el9.centos.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) I've checked that I do have the following repolists, ➜ kamctl dnf repolist repo id repo name appstream CentOS Stream 9 - AppStream baseos CentOS Stream 9 - BaseOS epel Extra Packages for Enterprise Linux 9 - x86_64 epel-next Extra Packages for Enterprise Linux 9 - Next - x86_64 extras-common CentOS Stream 9 - Extras packages kamailio Kamailio - latest - Packages for the Kamailio latest release mariadb-main MariaDB Server mariadb-maxscale MariaDB MaxScale mariadb-tools MariaDB Tools tailscale-stable Tailscale stable This is after a fresh installation of CentOS 9. I believe that I might have a missing repolist or probably have something incorrect in the configuration.

5 7

Re: [SR-Users] kamctl cr reload doesn't reload all routes
by Henning Westerholt 30 Nov '22

30 Nov '22

Hello Igor, yes - you can use a RPC command, I think its in corex module. Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/> From: Igor Potjevlesch <igor.potjevlesch(a)gmail.com> Sent: Wednesday, November 30, 2022 5:14 PM To: Henning Westerholt <hw(a)gilawa.com> Subject: RE: [SR-Users] kamctl cr reload doesn't reload all routes Hello Henning, Not really. I just place a call to the prefix and I can see that the route is still the previous one, not the one updated in DB. Can I set INFO loglevel without restarting? Regards, Igor. De : Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> Envoyé : mercredi 30 novembre 2022 15:03 À : Igor Potjevlesch <igor.potjevlesch(a)gmail.com<mailto:igor.potjevlesch@gmail.com>>; 'Kamailio (SER) - Users Mailing List' <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Objet : RE: [SR-Users] kamctl cr reload doesn't reload all routes Hello Igor, Strange. If not already done, you can try to set INFO loglevel to get maybe a bit more information. How do you verify the routes, but looking to RPC output probably? Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/> From: Igor Potjevlesch <igor.potjevlesch(a)gmail.com<mailto:igor.potjevlesch@gmail.com>> Sent: Wednesday, November 30, 2022 2:58 PM To: Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>>; 'Kamailio (SER) - Users Mailing List' <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Subject: RE: [SR-Users] kamctl cr reload doesn't reload all routes Hi Henning, The problem is still there on the concerned instance. I tried to reload again, and I didn't see the error but the routes are not updated. Regards, Igor. De : Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> Envoyé : mercredi 30 novembre 2022 14:44 À : Igor Potjevlesch <igor.potjevlesch(a)gmail.com<mailto:igor.potjevlesch@gmail.com>>; 'Kamailio (SER) - Users Mailing List' <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Objet : RE: [SR-Users] kamctl cr reload doesn't reload all routes Hi Igor, ok, might be some issue with the DB, if it does not happen anymore. You probably notice when it happens again and can investigate then. Regarding the table, just note that there is also a fourth table involved, domain_name: https://kamailio.org/docs/db-tables/kamailio-db-5.5.x.html#idm812 Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/> From: Igor Potjevlesch <igor.potjevlesch(a)gmail.com<mailto:igor.potjevlesch@gmail.com>> Sent: Wednesday, November 30, 2022 2:35 PM To: Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>>; 'Kamailio (SER) - Users Mailing List' <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Subject: RE: [SR-Users] kamctl cr reload doesn't reload all routes Hello Henning, I tried to review all the routes. Unfortunately, I didn't have access to the logs of the last reboot and its not easy to reboot the instance. I tried to copy the same tables (carrierroute, carrierfailureroute and carrier_name) on another instance and cr reload has been executed without any issue. Not easy to highlight where the problem comes from. Regards, Igor. De : Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> Envoyé : mardi 29 novembre 2022 21:13 À : Igor Potjevlesch <igor.potjevlesch(a)gmail.com<mailto:igor.potjevlesch@gmail.com>>; 'Kamailio (SER) - Users Mailing List' <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Objet : RE: [SR-Users] kamctl cr reload doesn't reload all routes Hello Igor, This is usually caused from wrong or incomplete routing data in the DB. Review if you e.g. have some missing domains or carrier entries in the respective tables. Also look for some errors or warnings related to carrierroute at a restart. Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/> From: Igor Potjevlesch <igor.potjevlesch(a)gmail.com<mailto:igor.potjevlesch@gmail.com>> Sent: Tuesday, November 29, 2022 6:08 PM To: Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>>; 'Kamailio (SER) - Users Mailing List' <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Subject: RE: [SR-Users] kamctl cr reload doesn't reload all routes Hello Henning, That's a good point. I tried again and I could see this: ERROR: carrierroute [cr_rpc.c:60]: cr_rpc_reload_routes(): failed to load routing data Nothing more precise. Regards, Igor. De : Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> Envoyé : mardi 29 novembre 2022 16:12 À : Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Cc : Igor Potjevlesch <igor.potjevlesch(a)gmail.com<mailto:igor.potjevlesch@gmail.com>> Objet : RE: [SR-Users] kamctl cr reload doesn't reload all routes Hello, any error message in the logs from carrierroute reload? Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/> From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of Igor Potjevlesch Sent: Tuesday, November 29, 2022 4:04 PM To: sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Subject: [SR-Users] kamctl cr reload doesn't reload all routes Hello! I'm facing a problem with one of my Kamailio instance: "kamctl cr reload" returns OK, but, finally, the route I modified, or I added are not takes. I'm still on a previous route. If I completely reboot Kamailio it's okay. So, the last time, I rebooted with more memory, and I was thinking that it could fix the problem, but not. Do you have any idea? Regards, Igor. [Das Bild wurde vom Absender entfernt.]<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Sans virus.www.avast.com<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>

1 0

kamctl cr reload doesn't reload all routes
by Igor Potjevlesch 30 Nov '22

30 Nov '22

Hello! I'm facing a problem with one of my Kamailio instance: "kamctl cr reload" returns OK, but, finally, the route I modified, or I added are not takes. I'm still on a previous route. If I completely reboot Kamailio it's okay. So, the last time, I rebooted with more memory, and I was thinking that it could fix the problem, but not. Do you have any idea? Regards, Igor. -- Cet e-mail a été vérifié par le logiciel antivirus d'Avast. www.avast.com

2 7

Removing the dmq list entry in version 5.4.7.
by satyaprakash ch 30 Nov '22

30 Nov '22

Hi Team, I need a help to remove the dmq list entry from the kamailio, I have executed the command *kamcmd dmq.list_nodes, below is the output*{ host: xx.xx.xx.xx port: 5080 resolved_ip: xx.xx.xx.xx status: active last_notification: 0 local: 0 } { host: yy.yy.yy.yy port: 5060 resolved_ip: yy.yy.yy.yy status: active last_notification: 0 local: 0 } I need to remove the *yy.yy.yy.yy.Note: I have used to remove the node with below command but it is not able to delete the entry.* kamctl rpc dmq.remove sip:yy.yy.yy.yy:5060

1 0

redis template config for topos module
by Patrick Karton 30 Nov '22

30 Nov '22

Hello not a usual question but i would like to know if somebody using topos module with redis backend can provide me an optimized redis conf for redis for using it topos module. and possibly also when using it with dialog module. Thanks.

2 3

Re: [SR-Users] uac_req_send() multi-process synchronization problem
by Henning Westerholt 30 Nov '22

30 Nov '22

Hello, not sure if I fully understand the problem. But regarding another user is registered with the same IP address as a previous user, there are several mitigations. To give two options: you could choose a really short re-registration time, you could use TCP and when you lose the connection you delete the contact. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of ??? Sent: Wednesday, November 30, 2022 2:57 AM To: sr-users(a)lists.kamailio.org Subject: [SR-Users] uac_req_send() multi-process synchronization problem When I use uac_req_send() to send a MESSAGE to the client. Will the following occur? The result of the message sent to user A is that B has received it. From the logs, the address of user A in the location table is the same as the IP address and port of user B, and the information of user A in the location table is not deleted in time. I took the address of user A directly from the location table without using KSR.registrar.reg_fetch_contacts(). If I use KSR.registrar.reg_fetch_contacts() can this be avoided. This is a multi-process synchronization problem, after user A registers, the IP port information in the address is 172.16.22.222:12345, and then user A disconnects the link because of some abnormal conditions, but it is not normal to cancel the registration, the socket link has failed, but it has not had time to delete the location, at this time user B registers, whether will it get the same IP port information as user A 172.16.22.222 : 12345, if possible? User A's location still exists, Using KSR.registrar.reg_fetch_contacts() TO query user A's location, and then using uac_req_send() to send a message to user A, User B will receive the MESSAGE. Whether this problem occurs? 从 Windows 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>发送

1 0

uac_req_send() multi-process synchronization problem
by 刘建峰 30 Nov '22

30 Nov '22

When I use uac_req_send() to send a MESSAGE to the client. Will the following occur? The result of the message sent to user A is that B has received it. From the logs, the address of user A in the location table is the same as the IP address and port of user B, and the information of user A in the location table is not deleted in time. I took the address of user A directly from the location table without using KSR.registrar.reg_fetch_contacts(). If I use KSR.registrar.reg_fetch_contacts() can this be avoided. This is a multi-process synchronization problem, after user A registers, the IP port information in the address is 172.16.22.222:12345, and then user A disconnects the link because of some abnormal conditions, but it is not normal to cancel the registration, the socket link has failed, but it has not had time to delete the location, at this time user B registers, whether will it get the same IP port information as user A 172.16.22.222 : 12345, if possible? User A's location still exists, Using KSR.registrar.reg_fetch_contacts() TO query user A's location, and then using uac_req_send() to send a message to user A, User B will receive the MESSAGE. Whether this problem occurs? 从 Windows 版邮件发送

1 0

[Users] checking route return codes
by Candida Benge 29 Nov '22

29 Nov '22

1 0

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