I noticed it as well when switching from 5.2.0 to 5.2.1 using the docker images, but got around it by adding a row with localhost as the destination. Kamailio did start but wasnt able to connect, which was fine.
On Mon, 4 Feb 2019 at 18:22, * Paolo Visintin - evosip.cloud <paolo.visintin@evosip.cloud> wrote:
good to know for the future implementation and super for the artifacts!
Anyone else experienced the bug regarding a empty rtpengine table causing non kamailio starting ?