On 08/01/2025 13.27, Knserbrave via sr-users wrote:
I'm not quite sure why websocket is even a viable transport for rtpengine if a new websocket is created for every request. I suspect I am missing configuration that would achieve the functionality I seek.
I don't think so. The WS transport is a simple wrapper over the same request/response mechanism that is also used for the UDP transport. What you're asking for would require persistent connections across multiple requests, and tracking which connection belongs to which call, which isn't implemented. Furthermore it would require sharing connections between the multiple processes that Kamailio is using, which poses and entirely new challenge due to the multi-process nature of Kamailio.
Cheers