Hi Denys,
Could you please open a Feature Request on github tracker, with this
item? It will be easier to manage for me :)
Thanks and regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 11.12.2024 19:13, Denys Pozniak wrote:
Hello!
True, it makes sense to have both options.
пн, 9 дек. 2024 г. в 10:16, Bogdan-Andrei Iancu <[email protected]>:
Hi Denys,
Unfortunately there is no option to do that, but your case sounds
reasonable - maybe a core param to mute such errors? Maybe
toggle-able via MI ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 20.11.2024 10:32, Denys Pozniak wrote:
Hello!
I'm dealing with a significant amount of unwanted traffic due to
a problematic SIP, which is causing rsyslog to be heavily loaded
with messages such as:
/ERROR:core:parse_msg: message=<>/
/ERROR:core:receive_msg: Unable to parse msg received from
[1.1.1.1:40327 <http://1.1.1.1:40327>]/
/ERROR:core:parse_to_param: unexpected char [,] in status 29:
<<;tag=tmnb>> ./
/ERROR:core:get_hdr_field: bad to header/
I'm looking for a way to suppress these messages directly from
the OpenSIPS level, rather than creating filters in rsyslog.
Any guidance on how to achieve this would be greatly appreciated.
--
BR,
Denys Pozniak
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
BR,
Denys Pozniak
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
