<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16587" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi Iņaki,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2> yep I have ;) Sorry my config is
actually with start=yes, but Id gotten so frustrated I even tried running the
mediaproxy</FONT></DIV>
<DIV><FONT face=Arial size=2>portion on a seperate server with only the
dispatcher on the OpenSER system (this made no difference to my
problem).</FONT></DIV>
<DIV><FONT face=Arial size=2>In my syslog I see both the dispatcher and the
mediaproxy running, and the socket files are created. Sessions are
even</FONT></DIV>
<DIV><FONT face=Arial size=2>started per call as you'd expect but at the end of
the call the mediaproxy summary (in syslog) states that it has
forwarded</FONT></DIV>
<DIV><FONT face=Arial size=2>0 bytes/packets of data :((.</FONT></DIV>
<DIV><FONT face=Arial size=2>So it seems the OpenSER mediaproxy module is
correctly making the request to the dispatcher for a proxy session,
but</FONT></DIV>
<DIV><FONT face=Arial size=2>something is not updating the SIP IP and PORT to
redirect the RTP via the proxy.... </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Any ideas? There seems so little you can configure
regarding this in the route that I feel at a dead end...</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><PRE>>Have you really read the doc? ;)
>
>; start Boolean value that specifies if to start the RTP proxy server.
>; Default value: Yes
>Also, after setting tha parameter to "yes" do a "tail -f /var/log/syslog" to
>see mediaproxy and proxydispatcher messages.</PRE></DIV></BODY></HTML>