…g.briefing

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

IN some scenarios I found useful to have the timestamps (init, start, end) of the dialog as output of the dlg.briefing command.

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

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

Commit Summary

• dialog: add dialog init, start end end timestamps to the output of dlg.briefing

File Changes

• M src/modules/dialog/dialog.c (5)

Patch Links:

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

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.