[sr-dev] [tracker] Task opened: force_send_socket in event route tm:local-request

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Kristian Høgh (kfhdk) Attached to Project - sip-router Summary - force_send_socket in event route tm:local-request Task Type - Improvement Category - Core Status - Unconfirmed Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - 4.0 Due in Version - Undecided Due Date - Undecided Details - Would it be possible to use force_send_socket in event route tm:local-request? In our setup we use a public IP for "normal" traffic and pua (for dialoginfo) uses outbound_proxy on other/private interface. Or could it be possible to set: * mhomed per module? * Auto "mhomed=1" on pua, when outbound_proxy is set, and kamailio listens on multiple interfaces? * Add "outbound_socket" module parameter on pua * A "much better solution"(tm) than the above Regards, Kristian Høgh Uni-tel On 21/08/14 12:00, Kristian F. Høgh wrote: Hello, I think the ougoing request is already created in that event route, the set advertise address being used too late from that perspective -- however, there is no hook before to set it. Open an enhancement issue on the tracker not to forget about it and I will check to see if there is a possibility to add this feature. Cheers, Daniel More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=462 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.