Hehhehehe, tks Klaus!<br>
<br>
This was a good moment to repeat the infamous expression made popular in the internet lists like this ... RTFM! :)<br>
I saw it just after sending the email ... the A flag ... and the S flag
(to set symmetric, as in bridged mode asymmetric is the default ... ).<br>
<br>
Now, one more question.<br>
To fulfill my needs, I had to add a few extra rtpproxy flags to the
already existing ... say M, N, X, Y ... But, they are not used all at
the same time, so I was wondering how could i simplify the call of
force_rtp_proxy ... Now I do something like ...<br>
<br>
if( blabla )<br>
force_rtp_proxy("FX")<br>
else if (bla2 )<br>
force_rtp_proxy("FXY")<br>
else if ....<br>
<br>
Not very nice. <br>
Can i do something (maybe avp? i am using ser 0.9.6) so i can have ...<br>
options = F<br>
if( bla )<br>
options += "X"<br>if (bla2)<br>
options +="Y"<br>
if( bla3)<br>
options = "MN"<br>
<br>
Cesc<br>
<br>
<br>
<div><span class="gmail_quote">On 1/23/07, <b class="gmail_sendername">Klaus Darilion</b> <<a href="mailto:klaus.mailinglists@pernau.at">klaus.mailinglists@pernau.at</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Cesc!<br><br>Check out the "a" flag:<br><br><a href="http://www.openser.org/docs/modules/1.1.x/nathelper.html#AEN319">http://www.openser.org/docs/modules/1.1.x/nathelper.html#AEN319</a><br><br><br>regards<br>
klaus<br><br><br><br>Cesc wrote:<br>> Hi,<br>><br>> I know this probably is a useless question, as rtpproxy says it is a<br>> symmetric proxy ... but i have to ask, for peace of mind :)<br>><br>> In my setup, i have on one side a symmetric rtp phone (A) ... connected
<br>> to a<br>> ser proxy + rtpproxy ... and on the other side, a non-symmetric phone (B).<br>> This is all on a lan, so no firewalls and stuff ... but I MUST use the<br>> rtpproxy and I MUST use this non-symmetric phone (more like a gateway,
<br>> actually).<br>><br>> A ------ SER+rtpproxy ------ B (nonsym)<br>><br>> So, the funny thing happens that i end up reciving audio from B to A ...<br>> and<br>> then I hear A's own audio after being bounced by B (funny, huh?). The
<br>> bouncing is due to rtpproxy changing the rtp port where he sends to B<br>> ... he<br>> starts with the one announced on SDP ... then, after the first RTP received<br>> from B, he switches to this new port ... mmmm
<br>><br>> I guess this is a lost cause ... but maybe someone has a brilliant<br>> idea?? :D<br>> (like a hack in rtpproxy which suddenly turns it into<br>> non-symmetrical-rtp-supported-endpoint proxy? :D )
<br>><br>> Regards,<br>><br>> Cesc<br>><br>><br>> ------------------------------------------------------------------------<br>><br>> _______________________________________________<br>> Serusers mailing list
<br>> <a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a><br>> <a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a><br><br><br>--<br>Klaus Darilion
<br><a href="http://nic.at">nic.at</a><br><br></blockquote></div><br>