| Author | SHA1 | Message | Date |
|---|---|---|---|
|
|
a56577adb4 |
MT#55283 rework dict_iter
Change-Id: I2d13eeea4df474639779e7be1a7b6aecd58db941 |
1 year ago |
|
|
3f8f182119 |
MT#55283 introduce abstract parsing framework
Change-Id: I63ba6fc7e6278e989e87a3abdb66976084b403bc |
1 year ago |
|
|
ceb49c9b54 |
MT#58535 rtpp_flags: deprecate usage of dict for parsing
Deprecate a usage of intermediate dictionary for parsing of rtpp flags. Just use the `call_ng_main_flags()` function directly with a given `bencode_buffer_t` buffer. Change-Id: I0bea13b94b6e0016799dd07a50061e1367131106 |
2 years ago |
|
|
f60139cf0d |
MT#58535 Add opmode to processing of flags
Add operation mode to the flags parsing functions. Change-Id: I49147b39ebccd43dfa703ba7857f1902bdad976b |
2 years ago |
|
|
36c19b9111 |
MT#58535 rtpp_flags: introduce raw flags parsing
Add support of rtpp_flags parsing for the daemon. From now on, it's possible to parse option flags on the daemon side instead of the kamailio module. It's identical to what the module does, but the difference is: - module sends general call identification such as: call-id, From/To tags, viabranch using bencode - meanwhile all generic/non-generic option flags are added to the `rtpp_flags` bencode member as str - parsing of that is done as usually using the `call_ng_main_flags()` / `call_ng_flags_flags()` and additionally using new parser `parse_rtpp_flags()` New file implementation and header introduced: - control_ng_flags_parser.c - control_ng_flags_parser.h Otherwise no functional changes, and the parsing itself remains working following the same algorithm. Change-Id: I59e47fa1947e2aeaa0bbf3930a0f21d9a6d669ad |
2 years ago |