It's probably a good idea to test the config in a test environment with the current software version for the purpose of problem isolation. If the problem doesn't occur in the latest version, then you can itemize it as something that will be fixed when your production environment is updated and something that you're probably powerless to address until that time. If the problem does persist, then you know that either it's a bug that will require a software fix and that rushing to update your production environment immediately won't yield a tangible result, OR that it's not a software issue and is a config issue, and that any config resolution can probably be addressed on your current version, and you'll have an easier time getting help here.
Regards, Kaufman ________________________________ From: James Morrison via sr-users <[email protected]> Sent: Wednesday, February 19, 2025 9:39 AM To: [email protected] <[email protected]> Cc: James Morrison <[email protected]> Subject: [SR-Users] Re: REG_MAR_REPLY never get executed CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Thanks Unfortunately I can't move a to a different version because we're using version 5.3 in production server. I just wanted to define a custom metric to count the number of successful/unsuccessful MAR requests just like what I already did for SAR/UAR/LIR requests. __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected] To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender!
__________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected] To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender!
