• Mention when FR timeout is reached, and which of FR timers expired
• Log when starting FR/RETR timers
• log when changing default timeouts to user-set values
• log when resetting fr/retr timers on provisional replies

Pre-Submission Checklist

• Commit message has the format required by CONTRIBUTING guide
• Commits are split per component (core, individual modules, libs, utils, ...)
• Each component has a single commit (if not, squash them into one commit)
• No commits to README files for modules (changes must be done to docbook files
  in doc/ subfolder, the README file is autogenerated)

Type Of Change

• Small bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds new functionality)
• Breaking change (fix or feature that would change existing functionality)

Checklist:

• PR should be backported to stable branches
• Tested changes locally
• Related to issue #XXXX (replace XXXX with an open issue number)

Description

The main reason for these changes is that we haven't found any possibility to distinguish which of fr timeouts expires. The rest of the logs are also helpful, but secondary.
As they all are under ifdef TIMEOUT_DEBUG I hope it is not a big deal.

You can view, comment on, or merge this pull request online at:

  https://github.com/kamailio/kamailio/pull/2818

Commit Summary

• tm: enhance fr/retr timers logging

File Changes

• M src/modules/tm/t_lookup.c (6)
• M src/modules/tm/t_reply.c (3)
• M src/modules/tm/t_suspend.c (3)
• M src/modules/tm/timer.c (7)
• M src/modules/tm/timer.h (4)

Patch Links:

• https://github.com/kamailio/kamailio/pull/2818.patch
• https://github.com/kamailio/kamailio/pull/2818.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.