<!-- 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

Hello Daniel,

https://lists.kamailio.org/pipermail/sr-users/2021-January/111628.html

On Mon, Jan 18, 2021 at 4:19 PM Julia Bo <juliabo at gmail.com> wrote:

It's my mistake, I checked a different branch. Sorry. Now I get the same result as yours. But in jason we get the result of command execution only and no sip reply result (that was in 4.4 : 200,408 etc..) I see sent OPTIONS and received reply in debug, Thank you, Julia

I have the same problem: I get no sip reply result.

[root@vict2-ims3 scherney]# kamctl ping sip:node1.pcscf-1.vict-ims.net { "jsonrpc": "2.0", "result": { }, "id": 12213 }

Hello,

I implemented an alternative rpc command that blocks waiting for the response. Try again with latest master and let's see if works.

It waits for max 80secs for the sip reply to come back (or the transaction to time out), checking every 0.1sec. Later I can make these values modparams, for now just to validate it works.

Cheers, Daniel

Can you please tell me, which commit it was, that I can test it at another version. Thanks!

BR Theo

<!-- Explain what you did, what you expected to happen, and what actually happened. -->

### Troubleshooting

#### Reproduction

[root@vict2-ims3 scherney]# kamctl ping sip:node1.pcscf-1.vict-ims.net { "jsonrpc": "2.0", "result": { }, "id": 12213 }

<!-- If the issue can be reproduced, describe how it can be done. -->

#### Debugging Data

<!-- If you got a core dump, use gdb to extract troubleshooting data - full backtrace, local variables and the list of the code at the issue location.

gdb /path/to/kamailio /path/to/corefile bt full info locals list

If you are familiar with gdb, feel free to attach more of what you consider to be relevant. -->

```none```

#### 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). -->

```none```

#### 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). -->

```[pr0071_030.zip](https://github.com/kamailio/kamailio/files/6648588/pr0071_030.zip)%60%60%60

### 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** - output of `kamailio -v` ```version: kamailio 5.1.6 (x86_64/linux) 42b01a flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 42b01a compiled on 10:29:16 May 12 2021```

* **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 vict-ims3 3.10.0-327.10.1.el7.x86_64 #1 SMP Sat Jan 23 04:54:55 EST 2016 x86_64 x86_64 x86_64 GNU/Linux```