[SR-Users] Re: rtpproxy -- timeout_socket

Hey James, Thanks for your interest! Indeed this functionality is somewhat broken (in the module), not very well documented and some of the documentation is not actually correct, so let me explain some basics: 1. The rtpproxy notification mechanism is rather low-level, it has no notion of http/xmlrpc in it. 2. Apart from timeout_socket, you are also supposed to provide an arbitrary "notify tag", which could be either a single no-spaces string or URL-encoded binary blob. Now looking at the Kamailio rtpproxy module code, it seems that this functionality has been added in 2010 with a reference to "ngcp-mediaproxy-ng" (that has later become rtpengine), so I suppose it was never really working with the "real" RTPProxy. :( To make it useful it needs to be extended to also take a timeout_tag parameter. Assuming it is there, the usage pattern should look something like the following: --- modparam("rtpproxy", "timeout_socket", "tcp:192.168.155.64:8888") modparam("rtpproxy", "timeout_tag_pv", "$avp(rtpp_ntag)") route { .... $avp( rtpp_ntag) = "POST%20/XMLRPC%20HTTP/1.0%0AContent-Type%3A%20text/xml%0AContent-Length%3A%20175%0A%0A%3C%3Fxml%20version%3D%221.0%22%3F%3E%0A%3CmethodCall%3E%0A%3CmethodName%3Esess_disc%3C/methodName%3E%0A%3Cparams%3E%0A%3Cparam%3E%0A%3Cvalue%3E%3Cstring%3Efoobar%40123.456.789.000%3C/string%3E%3C/value%3E%0A%3C/param%3E%0A%3C/params%3E%0A%3C/methodCall%3E%0A"; .... } --- This would make the RTPProxy issue the following request: --- POST /XMLRPC HTTP/1.0 Content-Type: text/xml Content-Length: 175 <?xml version="1.0"?> <methodCall> <methodName>sess_disc</methodName> <params> <param> &lt;value&gt;&lt;string&gt;foobar(a)123.456.789.000&lt;/string&gt;&lt;/value&gt; </param> </params> </methodCall> --- Of course this is not a very practical method to generate the XMLRPC, so in practice you may look at using some built-in languages (or string operations) to generate one automatically. Better yet, someone might come over and add a XMLRPC accounting module into rtpproxy to provide a more high level interface. Until then, however, I've added a pull request to implement the feature in question here, please feel free to give it a spin and let me know if something is still not working: https://github.com/kamailio/kamailio/pull/3598 Regards, Maksym On Mon, Oct 9, 2023 at 6:23 PM James Lipski via sr-users < sr-users(a)lists.kamailio.org&gt; wrote: -- Maksym Sobolyev Sippy Software, Inc. Internet Telephony (VoIP) Experts Tel (Canada): +1-778-783-0474 Tel (Toll-Free): +1-855-747-7779 Fax: +1-866-857-6942 Web: http://www.sippysoft.com MSN: sales(a)sippysoft.com Skype: SippySoft