xadhoom created an issue (kamailio/kamailio#4301)
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio…
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-dev.lists.kamailio.o…
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
Note that an issue report may be closed automatically after about 2 months
if there is no interest from developers or community users on pursuing it, being
considered expired. In such case, it can be reopened by writing a comment that includes
the token `/notexpired`. About two weeks before considered expired, the issue is
marked with the label `stale`, trying to notify the submitter and everyone else
that might be interested in it. To remove the label `stale`, write a comment that
includes the token `/notstale`. Also, any comment postpone the `expire` timeline,
being considered that there is interest in pursuing the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
When topos receives an in-dialog REFER, it correctly unmask everywhing as expected, but not the Refer-To header, which breaks transfers.
### Troubleshooting
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
For example, this is the refer from a client:
```
REFER sip:atpsh-685d3cd2-69-2@172.23.42.1;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.23.42.1:23045;rport;branch=z9hG4bKlaklhcax
Max-Forwards: 70
To: <sip:3338063766@example.voismart.com>;tag=Brcm20gBS5eZe
From: "Joe" <sip:1001@example.voismart.com>;tag=xbdlk
Call-ID: kpjiixyvombnlkw(a)fedora.fritz.box
CSeq: 340 REFER
Contact: <sip:1001@172.23.42.1:23045;transport=tcp>
Refer-To: <sip:atpsh-685d3cd2-69-4@172.23.42.1;transport=tcp?Replaces=lmhzfrkbucirwbc%40fedora.fritz.box%3bto-tag%3dXDQD403r30jeS%3bfrom-tag%3dtwbnd>
Referred-By: "Joe" <sip:1001@example.voismart.com>
User-Agent: Twinkle/1.10.3
Content-Length: 0
```
And this is what exits from topos proxy:
```
REFER sip:3338063766@172.23.42.211:5060;transport=udp SIP/2.0
Via: SIP/2.0/TCP 172.23.42.250;branch=z9hG4bK89f.32493a6f0ee894aad0bf66f581e5053a.0;i=3
Max-Forwards: 69
To: <sip:3338063766@example.voismart.com>;tag=Brcm20gBS5eZe
From: "Joe" <sip:1001@example.voismart.com>;tag=xbdlk
Call-ID: kpjiixyvombnlkw(a)fedora.fritz.box
CSeq: 340 REFER
Refer-To: <sip:atpsh-685d3cd2-69-4@172.23.42.1;transport=tcp?Replaces=lmhzfrkbucirwbc%40fedora.fritz.box%3bto-tag%3dXDQD403r30jeS%3bfrom-tag%3dtwbnd>
Referred-By: "Joe" <sip:1001@example.voismart.com>
User-Agent: Twinkle/1.10.3
Content-Length: 0
Route: <sip:172.23.42.3;transport=tcp;r2=on;lr=on;ftag=xbdlk;did=c84.2b02>
Route: <sip:172.23.42.3;r2=on;lr=on;ftag=xbdlk;did=c84.2b02>
Contact: <sip:btpsh-685d3cd2-69-2@172.23.42.250>
```
### Possible Solutions
Will try to find a solution, I see that in `tps_msg.c` `parse_refer_to.h` is included so perhaps there was some idea about it, but since I'm not an expert in kamailio internals may need some time.
### Additional Information
v6.0.x and master
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4301
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4301(a)github.com>
Module: kamailio
Branch: master
Commit: 0e0ab85583241533e21bbea317a1fb9dbf8a8f72
URL: https://github.com/kamailio/kamailio/commit/0e0ab85583241533e21bbea317a1fb9…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2025-07-03T08:20:48+02:00
dispatcher: docs for algprithm 14 (round-robin or serial)
---
Modified: src/modules/dispatcher/doc/dispatcher_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/0e0ab85583241533e21bbea317a1fb9…
Patch: https://github.com/kamailio/kamailio/commit/0e0ab85583241533e21bbea317a1fb9…
---
diff --git a/src/modules/dispatcher/doc/dispatcher_admin.xml b/src/modules/dispatcher/doc/dispatcher_admin.xml
index 126ad986724..1f897f8335b 100644
--- a/src/modules/dispatcher/doc/dispatcher_admin.xml
+++ b/src/modules/dispatcher/doc/dispatcher_admin.xml
@@ -1466,6 +1466,13 @@ With congestion control the formula becomes :
load control rate).
</para>
</listitem>
+ <listitem>
+ <para>
+ <quote>14</quote> - round-robin (4) if all the destinations
+ in the group have the same priority and the priority is greater
+ than 0, otherise serial dispatching (8).
+ </para>
+ </listitem>
<listitem>
<para>
<quote>X</quote> - if the algorithm is not implemented, the
IgorrG created an issue (kamailio/kamailio#4268)
### Description
We use RPC dlg.end_dlg command to terminate dialog. In most cases it does operate properly and send BYE from kamailio to both sides of dialog (as show on screenshot).

We found that in some cases we have only first BYE sent to calling party. Second BYE never sent, when called party tries to terminate call by timeout it get responded with 481.


In logs we have such warning:
мая 27 15:11:46 service-proxy.iqtek.ru kamailio[3518388]: 2(3518388) WARNING: {1 1 BYE 541d3f2c-43fd-43b6-af24-bad1fbf85eb6} dialog [dlg_handlers.c:1343]: dlg_onroute(): unable to find dialog for BYE with route param 'e1e.4f22' [3614:8948] and call-id '541d3f2c-43fd-43b6-af24-bad1fbf85eb6'
We also found that in this case this warning shown in logs 0.04 seconds after kamailio receive 200ok.
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
# ./kamailio -V
version: kamailio 5.8.6 (x86_64/linux) fb71db
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, 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_SEND_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: fb71db
compiled on 17:38:27 May 26 2025 with gcc 12.2.0
```
* **Operating System**:
```
# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm
# uname -a
Linux rtp-kamailio2 6.1.0-32-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.129-1 (2025-03-06) x86_64 GNU/Linux
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4268
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4268(a)github.com>
hubgurujr created an issue (kamailio/kamailio#4287)
Seeing a lot of warning messages in logs, running version: kamailio 5.8.4 (x86_64/linux) 1e6738, but I think this is false positive and should be informational, not a warning.
Jun 10 14:14:17 siprouter1-pve186 /usr/local/sbin/kamailio[8111]:WARNING: <core> [core/dns_cache.c:170]: dns_hash_put(): unlinked item 0x7fa0f9b9fcc0
Jun 10 14:14:19 siprouter1-pve186 /usr/local/sbin/kamailio[8122]:WARNING: <core> [core/dns_cache.c:185]: dns_hash_put_shm_unsafe():unlinked item 0x7fa0f9b9fcc0
This is occurring when a DNS URL changes IP but I see no processing issues with SIP Messages.
[emal-thread.txt](https://github.com/user-attachments/files/20776557/emal-th…
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4287
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4287(a)github.com>
IgorrG created an issue (kamailio/kamailio#4266)
### Description
While implementing mid-register inspired by pull request (https://github.com/kamailio/kamailio/pull/3360) we found the case when it goes impossible to handle responses for registrar servers. In case some of registrars busy and respond with 401 after 200ok received - it is not possible using any routes and configuration options to handle responses received in branch transactions.
According to documentation I think that setting wt_timer should allow to absorb and handle responses on failure-route while transaction kept in memory. In fact wt_timer does not affect handling responses in any way.

### Troubleshooting
To reproduce this case we have configured sipp to response instant with 200ok on registration request.
#### Reproduction
To reproduce issue SIPP could be setup as one of the dispatcher nodes with instant 200ok reply to register. Kamailio should use following configuration snippet: https://github.com/ovoshlook/kamailio-mid-registrar-config-snippets/blob/ma…
#### Log Messages
REGISTER|401tm [t_lookup.c:912]: t_reply_matching(): t_reply_matching: hash 12337 label 0 branch 1
REGISTER|401tm [t_lookup.c:986]: t_reply_matching(): reply (0x7f1fc67f83a8) matched an active transaction (T=0x7f1fc0f0f740)!
REGISTER|401tm [t_lookup.c:1122]: t_check_msg(): msg (0x7f1fc67f83a8) id=13/1915035 global id=13/1915035 T end=0x7f1fc0f0f740
REGISTER|401tm [t_reply.c:2363]: reply_received(): transaction found - T:0x7f1fc0f0f740 branch:1
REGISTER|401tm [t_reply.c:2376]: reply_received(): original status uas=200, uac[1]=0 local=0 is_invite=0)
REGISTER|401tm [t_reply.c:1363]: t_should_relay_response(): ->>>>>>>>> T_code=200, new_code=401
REGISTER|401tm [t_reply.c:1374]: t_should_relay_response(): final reply already sent
REGISTER|401tm [t_reply.c:1625]: t_should_relay_response(): finished with rps discarded - uas status: 200
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version**
```
version: kamailio 5.6.4 (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 on 16:35:08 Jun 5 2023 with gcc 10.2.1
```
* **Operating System**:
```
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
Linux pbxKamaTest 5.10.0-23-amd64 #1 SMP Debian 5.10.179-1 (2023-05-12) x86_64 GNU/Linux
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4266
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4266(a)github.com>