Hi,
After upgrading to Kamailio v4.4, I receive the following error on boot:
May 03 17:18:22 allegro-4.evaristesys.com /usr/local/sbin/kamailio[24972]: ERROR: rtpengine [rtpengine.c:2691]: select_rtpp_set(): script error-invalid id_set to be selected May 03 17:18:22 allegro-4.evaristesys.com /usr/local/sbin/kamailio[24972]: ERROR: rtpengine [rtpengine.c:2691]: select_rtpp_set(): script error-invalid id_set to be selected May 03 17:18:22 allegro-4.evaristesys.com /usr/local/sbin/kamailio[24972]: NOTICE: rtpengine [rtpengine.c:1788]: mod_init(): Default rtpp set 0 NOT found
My rtpengine module config is:
--- #!ifdef WITH_RTPENGINE
#!subst "/RTPENGINE_SOCK/udp:127.0.0.1:5050/"
modparam("rtpengine", "rtpengine_sock", "1 == RTPENGINE_SOCK") modparam("rtpengine", "rtpengine_disable_tout", 30) modparam("rtpengine", "rtpengine_tout_ms", 2000) modparam("rtpengine", "rtpengine_retr", 2)
#!endif ---
Furthermore, I have set_rtpengine_set("1") before every call to the rtpengine_* module function(s) in my route script.
Subsequently to that, Kamailio starts normally and connects to rtpengine:
May 03 17:18:22 allegro-4.evaristesys.com /usr/local/sbin/kamailio[24972]: INFO: rtpengine [rtpengine.c:2542]: rtpp_test(): rtp proxy udp:127.0.0.1:5050 found, support for it enabled May 03 17:18:22 allegro-4.evaristesys.com /usr/local/sbin/kamailio[24975]: INFO: rtpengine [rtpengine.c:2542]: rtpp_test(): rtp proxy udp:127.0.0.1:5050 found, support for it enabled May 03 17:18:22 allegro-4.evaristesys.com /usr/local/sbin/kamailio[24974]: INFO: rtpengine [rtpengine.c:2542]: rtpp_test(): rtp proxy udp:127.0.0.1:5050 found, support for it enabled [...]
It might be something on my end, but my guess is that in v4.4 there is a fixup that runs beforehand and looks for a default set.
Strictly speaking, I don't need an explicitly identified set, since I'm only using one rtpengine instance. However, I explicitly specify it because I'd like the code to be open in the future to selecting a given rtpengine relay based on some criteria.
-- Alex
Hi,
On 04.05.2016 00:23, Alex Balashov wrote:
Hi,
After upgrading to Kamailio v4.4, I receive the following error on boot:
May 03 17:18:22 allegro-4.evaristesys.com /usr/local/sbin/kamailio[24972]: ERROR: rtpengine [rtpengine.c:2691]: select_rtpp_set(): script error-invalid id_set to be selected May 03 17:18:22 allegro-4.evaristesys.com /usr/local/sbin/kamailio[24972]: ERROR: rtpengine [rtpengine.c:2691]: select_rtpp_set(): script error-invalid id_set to be selected May 03 17:18:22 allegro-4.evaristesys.com /usr/local/sbin/kamailio[24972]: NOTICE: rtpengine [rtpengine.c:1788]: mod_init(): Default rtpp set 0 NOT found
There have been quite a lot of changes in rtpengine module mainly relate to the possibility to store/get rtpengine machine URL in/from database.
Among those changes, [1] has been introduced also. This is useful when you have many sets of rtpengine stored in database and want to select the active set, currently possible only at startup-time (devault those with setid 0). A further improvement here would be to be able to "kamctl fifo change it".
The message notices that you should set [1] to your wanted, active set.
Subsequently to that, Kamailio starts normally and connects to rtpengine:
May 03 17:18:22 allegro-4.evaristesys.com /usr/local/sbin/kamailio[24972]: INFO: rtpengine [rtpengine.c:2542]: rtpp_test(): rtp proxy udp:127.0.0.1:5050 found, support for it enabled May 03 17:18:22 allegro-4.evaristesys.com /usr/local/sbin/kamailio[24975]: INFO: rtpengine [rtpengine.c:2542]: rtpp_test(): rtp proxy udp:127.0.0.1:5050 found, support for it enabled May 03 17:18:22 allegro-4.evaristesys.com /usr/local/sbin/kamailio[24974]: INFO: rtpengine [rtpengine.c:2542]: rtpp_test(): rtp proxy udp:127.0.0.1:5050 found, support for it enabled [...]
It might be something on my end, but my guess is that in v4.4 there is a fixup that runs beforehand and looks for a default set.
Strictly speaking, I don't need an explicitly identified set, since I'm only using one rtpengine instance. However, I explicitly specify it because I'd like the code to be open in the future to selecting a given rtpengine relay based on some criteria.
-- Alex
Now, having "modparam("rtpengine", "setid_avp", "$avp(setid)")" overwrites [1]'s behaviour, explaining why it's "found, support for it enabled".
Regards, Stefan
[1] http://kamailio.org/docs/modules/4.4.x/modules/rtpengine.html#rtpengine.p.se...
Stefan,
Thank you for the insights!
-- Alex