Fabio Macchi wrote:
Greger, you are right, I was too generic, anyway your "not sensible help" was unvaluable: it focus me to the onreply route that I forgot to consider before.
I was missing the parameters "FA" in force_rtp_proxy() and this was the cause of missing RTP connection.
Now everything is working as expected.
Excellent! :-)
Just two generic questions on rtpproxy to understand a little more:
is it possible to extend this configuration from twointerface to multiple interfaces ( I mean something like rtpproxy --l x.x.x.246/10.0.0.1/192.168.1.1 ) ?
AFAIK, no. But I cannot really see how such a scenario can easily be unambiguous? What do you want to do with three interfaces? Three subnets terminated on your SER server?! You can probably set up multiple rtpproxies, but you still have a problem in making one ser talk to more than one...
when I was debbuging, I tried to start rtpproxy with --foption and I expected output directly on terminal, but I didn't obtain any output: is the output redirected to a specific file ? am I misunderstanding the use of that option ?'
stderr should be target. However, you may want to edit rtpp_defines.h and set LOG_LEVEL to RTPP_LOG_DBUG and recompile to get maximum of messages. Default you only get warnings, errors, and critical messages, not informational or debug messages.
Anyway, many thanks for your support.
Just a pleasure ;-) g-)
Hi Greger,
* Greger V. Teigre greger@teigre.com [060718 19:11]:
AFAIK, no. But I cannot really see how such a scenario can easily be unambiguous? What do you want to do with three interfaces? Three subnets terminated on your SER server?! You can probably set up multiple rtpproxies, but you still have a problem in making one ser talk to more than one...
I have´nt really followed this tread, but ser can use more then one rtpproxy. Because, you can loadbalanse with rtpproxy useing the (atleast) cvshead nathelper module.
just remember to make sure you dont mix up what signalling goes via what proxy :)
(Ps, see under for explination from nathelper.c)
Atle
* 2005-12-23 Support for selecting particular RTP proxy node has been added. * In force_rtp_proxy() it can be done via new N modifier, followed * by the index (starting at 0) of the node in the rtpproxy_sock * parameter. For example, in the example above force_rtp_proxy("N1") will * will select node udp:1.2.3.4:3456. In unforce_rtp_proxy(), the same * can be done by specifying index as an argument directly, i.e. * unforce_rtp_proxy(1). * * Since nathelper is not transaction or call stateful, care should be * taken to ensure that force_rtp_proxy() in request path matches * force_rtp_proxy() in reply path, that is the same node is selected.
-
Atle Samuelsen -
Greger V. Teigre