[OpenSIPS-Users] RTPEngine node selection

Pete Kelly pkelly at gmail.com
Fri Oct 5 09:54:13 EDT 2018


I have a configuration with OpenSIPS 2.4.1 and an rtpengine set which
contains 2 rtpengine nodes.

At some points I notice that OpenSIPS will issue an rtpengine_offer to
node1, and then the subsequent rtpengine_answer will be sent to node2.

The rtpengine_answer call invariably fails because rtpengine cannot find
the corresponding call in its internal database.

I have checked the OpenSIPS rtpengine module code and it seems that it is
perfectly valid for OpenSIPS to select "another node in the same set" if
the first node is down. It also seems that with the hashing mechanism in
place, if the node order is reversed within the set, a different node could
also be selected for the rtpengine_answer.

It seems that as rtpengine needs to know about the offer before it can
respond to the answer, that it should be mandatory for subsequent requests
to rtpengine to always hit the same node.

Am I missing something here?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20181005/76c9f4d9/attachment.html>

More information about the Users mailing list