New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kamailio 5.4.5: "0 ID or NULL NAME AVP!" in lcr module #2709
Comments
Thanks for reporting, I will look into it, the commit ca18218 was related to a fix on a potential issue reported by a static analyzer/fuzzer. As a workaround to try for now would be to change the next parameters to use string avp name:
|
Thanks for your quick reaction. I can confirm that for both solutions, the lcr module works well:
Since I don't want to use the git version in production, I would be grateful for a quick official 5.4.6 release. Also, I assume this problem may affect most of kamailio 5.4.5 deployments using lcr because the Integer avp names are suggested by the official documentation (https://www.kamailio.org/docs/modules/stable/modules/lcr.html). |
Thanks for testing and confirming the fix and the workaround! There are nightly builds from the 5.4.x branch: It is what you can use to get the fix in deb packages. There will be a 5.4.6 at some point, but for packaging pointing view that's just to have a milestone, because the packages for it are from the branch 5.4, exactly as it is done in the nightly ones. You can also build debs locally, specs are in the |
Description
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
kamailio.cfg:
Debugging Data
Log Messages
SIP Traffic
SIP request:
SIP reply:
Possible Solutions
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
Root Cause Assumption
ca18218 might be involved in the issue.
The text was updated successfully, but these errors were encountered: