4.3 rtpengine has new force_send_interface parameter. i noticed it because rtpengine module generated several of these kind of messages at startup:
May 8 11:06:43 siika /usr/bin/sip-proxy[26572]: INFO: rtpengine [rtpengine.c:455]: bind_force_send_ip(): force_send_ip_str not specified in .cfg file!
two questions:
1) is info level message really necessary? i would prefer debug level message.
2) since there can be several (sets) of rtpengines running on the same host as sip proxy, on private network, and on the internet, how can one force_send_interface parameter be enough?
-- juha
Hello Juha,
Related to your questions:
two questions:
- is info level message really necessary? i would prefer debug level
message.
Sure, it also sounds ok for us to decrease to debug level and we will do this.
- since there can be several (sets) of rtpengines running on the same
host as sip proxy, on private network, and on the internet, how can one force_send_interface parameter be enough?
You are right, in case of multiple rtpengines in different networks, connections to both may fail with the "can't connect to a RTP proxy" error message. However, force_send_interface parameter is optional and if you don't set it, the kamailio will select an appropriate socket and the behaviour will be as expected.
Suppose one has a PC with 2 interfaces connected to the same network and wants to force traffic going through a certain interface, this parameter is helpful.
Maybe in the future we could improve the functionality of this parameter; we are open to suggestions.
Greetings, 1and1 VoIP Team
smititelu writes:
Sure, it also sounds ok for us to decrease to debug level and we will do this.
Thanks.
Suppose one has a PC with 2 interfaces connected to the same network and wants to force traffic going through a certain interface, this parameter is helpful.
Yes, it is useful is some scenarios.
Maybe in the future we could improve the functionality of this parameter; we are open to suggestions.
It may get too complicated, since it would need to be possible to associate an interface to each rtpengine. I'm personally fine with the current functionality.
-- Juha
-
Juha Heinanen -
smititelu