Thomas Ries

Hello Simon, of course, you may :-)

Hello Simon, are you using the latest code from Github? According to configure.log this is likely an issue that has been fixed in July 2025 in the master branch (but no release has been made since). -> https://github.com/hb9xar/siproxd/commit/0bb5dd4aac9f5578db664d82f67091bc83c3780d best regards, /Thomas

Hi Simon, can you please provide the full output of ./configure and the resulting "config.log" file? Regards, /Thomas

year-2038 issue in plugin_blacklist

Thank you for reporting this issue. The suggested fix has been implemented with commit 879925a80b5d80f425abeb82d934b1425c7830cd

year-2038 issue in plugin_blacklist

1) conditional rewriting using plugin_regex: plugin_regex_desc = prefix outgoing 10 digit numbers with a leading '1' #plugin_regex_pattern = ^(sips?:)(\+?)(.{10}@) plugin_regex_pattern = ^(sips?:)(\+?)([0-9]{10}@) plugin_regex_replace = \1\21\3 or maybe (without '+' prefixed, 10 digit numbers only) plugin_regex_desc = prefix outgoing 10 digit numbers without leading '+' with a leading '1' plugin_regex_pattern = ^(sips?:)([0-9]{10}@) plugin_regex_replace = \11\2 only 10 digit numbers will be processed....

Please try without plugin_prefix being active. Looking at the log, I have the impression that the PBX issues a re-INVITE (directed towards flowroute) for the ongoing call that is being affected by plugin_prefix and causes the call to fail. If plugin_prefix is causing an issue in this setup, there are other ways to prefix outgoing calls with the digit 1 (plugin_regex, allows conditionally rewriting outgoing call targets via regular expressions).