format as well

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

Description

There was missing information of type identifiers that can be used in rpc tutorial docs. This is an update to those docs. The most recent I could find was for 5.7.

Maybe there is a need for manual updating the page?

Also during the relevant PR #4227 , we found the t identifier is never used in the code. since it can overflow on 64bit systems due to being a long and not int type when saved/load, maybe we can remove it completely?. One can just cast the time_t to the relevant type and use the correct identifier as done in https://github.com/kamailio/kamailio/blob/2081b3aac394223b68b849fbac2a9e5ac4392334/src/modules/dispatcher/dispatcher.c#L1978-L1990

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

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

Commit Summary

e4bc468 Update type identifiers that can be used in the RPC API

File Changes

(1 file)

M doc/tutorials/rpc/kamailio_rpc.xml (86)

Patch Links:

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