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

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

After upgrading kamailio from 5.4.4 to 5.4.5, the lcr module logs an error for 
outgoing calls. load_gws returns success (1), but does not populate the avps. 
Consequently, next_gw fails.

### Troubleshooting

#### Reproduction

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

```
loadmodule "lcr.so"

...

modparam("lcr", "db_url", "cluster://cls1")
modparam("lcr", "gw_uri_avp", "$avp(i:709)")
modparam("lcr", "ruri_user_avp", "$avp(i:500)")
modparam("lcr", "tag_avp", "$avp(lcr_tag)")
modparam("lcr", "flags_avp", "$avp(i:712)")
modparam("lcr", "defunct_capability", 1)
modparam("lcr", "lcr_id_avp", "$avp(s:lcr_id_avp)")
modparam("lcr", "defunct_gw_avp", "$avp(s:defunct_gw_avp)")
modparam("lcr", "ping_interval", 60)

...

route[LCR] {
        if(!($rU=~"^[+0-9]"))
                return;

        if(is_method("INVITE")) {
                if (!($fU=~"^[+0-9]+$")) {
                        append_hf("P-Asserted-Identity: 
<sip:[email protected]>\n");
                        append_hf("Privacy: id\n");
                        $fn = "Anonymous";
                        $fu = "sip:[email protected]";
                }

                if(load_gws(1, $rU, $var(caller_uri)) != 1) {
                        xlog("L_ERROR", "Couldn't load gateways\n");
                        sl_send_reply("500", "Server Internal Error - Cannot 
load gateways");
                        exit;
                } else {
                        xlog("L_INFO", "GW Selected '$avp(i:709)'\n");
                        xlog("L_INFO", "Domain of destination: $dd\n");
                        xlog("L_INFO", "To URI: $tu\n");
                }

                if(!next_gw()) {
                        xlog("L_WARN", "No gateway configured for $rU\n");
                        sl_send_reply("503", "Service not available, no 
gateways found");
                        exit;
                } else {
                        xlog("L_INFO", "Calling the first matched gateway\n");
                        xlog("L_INFO", "ruri_user_avp: '$avp(i:500)'\n");
                        xlog("L_INFO", "To URI after next_gw: $tu\n");
                        xlog("L_INFO", "Request URI: $ru\n");
                }

                t_on_failure("MANAGE_FAILURE_LCR");
                route(RELAY);
                exit;
        }
}
```

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

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

```
Apr 15 20:59:27 x /usr/sbin/kamailio[879]: ERROR: <core> [core/usr_avp.c:152]: 
create_avp(): 0 ID or NULL NAME AVP!
Apr 15 20:59:27 x /usr/sbin/kamailio[879]: ERROR: <core> [core/usr_avp.c:152]: 
create_avp(): 0 ID or NULL NAME AVP!
Apr 15 20:59:27 x /usr/sbin/kamailio[879]: INFO: <script>: GW Selected '<null>'
Apr 15 20:59:27 x /usr/sbin/kamailio[879]: INFO: <script>: Domain of 
destination: <null>
Apr 15 20:59:27 x /usr/sbin/kamailio[879]: INFO: <script>: To URI: 
sip:[email protected]:5060
Apr 15 20:59:27 x /usr/sbin/kamailio[879]: WARNING: <script>: No gateway 
configured for +49177xxxxxxx
```

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

SIP request:
```
        INVITE sip:[email protected]:5060 SIP/2.0
        Via: SIP/2.0/UDP xxx.xx.xx.xxx:xxxxx;branch=z9hG4bK5d833a50
        Max-Forwards: 70
        From: <sip:[email protected]:xxxxx>;tag=as18ff0d47
        To: <sip:[email protected]:5060>
        Contact: <sip:[email protected]:xxxxx>
        Call-ID: [email protected]:xxxxx
        CSeq: 102 INVITE
        User-Agent: Asterisk PBX 13.18.3~dfsg-1ubuntu4
        Date: Thu, 15 Apr 2021 21:52:42 GMT
        Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, 
INFO, PUBLISH, MESSAGE
        Supported: replaces, timer
        Content-Type: application/sdp
        Content-Length: 952

...
```

SIP reply:
```
        SIP/2.0 503 Service not available, no gateways found
        Via: SIP/2.0/UDP 
xxx.xx.xx.xxx:xxxxx;branch=z9hG4bK5d833a50;rport=50060;received=xx.xx.xx.xxx
        From: <sip:[email protected]:xxxxx>;tag=as18ff0d47
        To: 
<sip:[email protected]:5060>;tag=6a823999ce344a0b461cf8d85d526103.51611a36
        Call-ID: [email protected]:xxxxx
        CSeq: 102 INVITE
        Server: kamailio (5.4.5 (x86_64/linux))
        Content-Length: 0
```


### Possible Solutions

<!--
If you found a solution or workaround for the issue, describe it. Ideally, 
provide a pull request with a fix.
-->

As a workaround, I downgraded to kamailio 5.3.8 because the previous Ubuntu 
release 5.4.4 is not available anymore at 
http://deb.kamailio.org/kamailio54/pool/main/k/kamailio/ (why actually?)

### Additional Information

* **Kamailio Version** 5.4.5
* **Operating System**: Ubuntu 18.04

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

### Root Cause Assumption

https://github.com/kamailio/kamailio/commit/ca1821837dfe7dd6630f628d968ed4d1178c7040
 might be involved in the issue.

-- 
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/2709
_______________________________________________
Kamailio (SER) - Development Mailing List
[email protected]
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Reply via email to