<!--
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:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot 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
I wanted to change 478 response to 503 in case of t_relay() failure, but leave default behavior in rest error cases. I used part of code from "Example 1.1." inside https://www.kamailio.org/docs/modules/devel/modules/outbound.html. When I get -478 from t_relay() it works fine, but when this code is different sl_reply_erorr() don't use it as it should be.
This is my part of kamailio.cfg:
```
route[RELAY] {
if (!t_relay()) {
switch($rc) {
case -478:
xlog("L_WARN","T_Relay returned 478, sending back 503.\n");
sl_send_reply("503", "Service Unavailable");
exit;
default:
sl_reply_error();
exit;
}
}
exit;
}
```
When I log $rc value before sl_reply_error() it is valid, but not used by sl_reply_error() as SIP error value, it sends 500 instead.
### Troubleshooting
#### Reproduction
I've added incorrect hostnames with flag 16 to set where the message should be sent and t_relay() returns -478. To check the default case inside switch I changed case -478 to -479.
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
1(8) ERROR: <core> [core/resolve.c:1731]: sip_hostport2su(): could not resolve hostname: "va4brhino"
1(8) ERROR: tm [ut.h:309]: uri2dst2(): failed to resolve "va4brhino"
1(8) ERROR: tm [t_fwd.c:1759]: t_forward_nonack(): failure to add branches
1(8) ERROR: sl [sl_funcs.c:414]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (1/SL)
```
Logs with different route relay
```
route[RELAY] {
if (!t_relay()) {
switch($rc) {
case -479:
xlog("L_WARN","T_Relay returned 479, sending back 503.\n");
sl_send_reply("503", "Service Unavailable");
exit;
default:
xlog("L_WARN","Return code: $rc\n");
sl_reply_error();
exit;
}
}
exit;
}
```
```
1(8) ERROR: <core> [core/resolve.c:1731]: sip_hostport2su(): could not resolve hostname: "va4brhino"
1(8) ERROR: tm [ut.h:309]: uri2dst2(): failed to resolve "va4brhino"
1(8) ERROR: tm [t_fwd.c:1759]: t_forward_nonack(): failure to add branches
1(8) WARNING: <script>: Return code: -478
1(8) ERROR: sl [sl_funcs.c:414]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (1/SL)
```
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.5.0 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_
DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES
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 4.8.4
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `uname -a`)
-->
```
Linux v4bkamailio 5.10.25-linuxkit #1 SMP Tue Mar 23 09:27:39 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2802
### Description
Can we have async connection/communication between Kamailio and RTPEngine
#### Actual observed behavior
Currently, if there is a network latency or unstable network between Kamailio and RTPEngine, the Kamailio is keep waiting/polling on RTPEngine. That can be overcome if we have async connection.
-Miteshkumar
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2807
Hello,
given the current situation across the world, no physical Kamailio World
Conference is planned in 2021. However, this year the project celebrates
20 years of development -- according to commit history, the first one
was done on the 3rd of September, 2021:
> ❯ git log --reverse
> commit 512dcd9838f5aeb0bfccd02cfc156067b7f02b71
> Author: Andrei Pelinescu-Onciul <andrei(a)iptel.org>
> Date: Mon Sep 3 21:27:11 2001 +0000
> Initial revision
To mark this notable milestone, we are going to organize an online event
during Sep 1-2, 2021, similar to the one from 2020 -- the website for
the event is available at:
* https://www.kamailioworld.com/k09-online/
Mark the date in your calendar, more details about the content of the
event will be published in the near future!
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Dear sir:
I have some problems。the kamailio version is 5.3.0. My linux version is centos 7. the kamailio log:
ERROR: <core> [core/tcp_main.c:3508]: send_fd_queue_run(): send_fd failed on socket 63 , queue entry 1, retries 90, connection 0x7ff46e6b1b60, tcp socket 218, errno=11 (Resource temporarily unavailable)
ERROR: {1 12529 MESSAGE 359bf0410a7e471c950623e3f7a3b17b} <core> [core/kemi.c:94]: sr_kemi_core_err(): 202->408
CRITICAL: <core> [core/tcp_main.c:4218]: send2child(): tcp child 6, socket 65: queue full, 291 requests queued (total handled 10665748)
This problem does not happen every time。When the number of user registrations increases significantly, errors will appear。I tried to set the parameter tcp_children is adjusted to 8, it will not appear frequently, but when the number of user registrations increases to about 5000, errors will still appear. My kamailio.cfg global parameters are set as follows:tls_max_connections=65536,tcp_max_connections=65536,open_max_files=65536。
I hope you can reply to me,thanks.