[Serusers] non-symmetric rtp with rtpproxy??

[Cesc]

:(

Ok ... it doesn't matter ... a few more lines in my already huge config file
won't hurt :)

On 1/24/07, Michal Matyska <michal at iptel.org> wrote:
>
> It was introduced to ottendorf version, where you can put
> force_rtp_proxy("$avp"), but with 0.9.6 you have to use suggested if
> elseif elseif...
>
> Michal
>
> On Wed, 2007-01-24 at 11:04 +0100, Cesc wrote:
> > Hehhehehe, tks Klaus!
> >
> > This was a good moment to repeat the infamous expression made popular
> > in the internet lists like this ... RTFM! :)
> > 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 ... ).
> >
> > Now, one more question.
> > 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 ...
> >
> > if( blabla )
> >      force_rtp_proxy("FX")
> > else if (bla2 )
> >      force_rtp_proxy("FXY")
> > else if ....
> >
> > Not very nice.
> > Can i do something (maybe avp? i am using ser 0.9.6) so i can have ...
> > options = F
> > if( bla )
> >        options += "X"
> > if (bla2)
> >        options +="Y"
> > if( bla3)
> >        options = "MN"
> >
> > Cesc
> >
> >
> > On 1/23/07, Klaus Darilion <klaus.mailinglists at pernau.at> wrote:
> >         Hi Cesc!
> >
> >         Check out the "a" flag:
> >
> >         http://www.openser.org/docs/modules/1.1.x/nathelper.html#AEN319
> >
> >
> >         regards
> >         klaus
> >
> >
> >
> >         Cesc wrote:
> >         > Hi,
> >         >
> >         > I know this probably is a useless question, as rtpproxy says
> >         it is a
> >         > symmetric proxy ... but i have to ask, for peace of mind :)
> >         >
> >         > In my setup, i have on one side a symmetric rtp phone
> >         (A) ... connected
> >         > to a
> >         > ser proxy + rtpproxy ... and on the other side, a
> >         non-symmetric phone (B).
> >         > This is all on a lan, so no firewalls and stuff ... but I
> >         MUST use the
> >         > rtpproxy and I MUST use this non-symmetric phone (more like
> >         a gateway,
> >         > actually).
> >         >
> >         > A ------ SER+rtpproxy ------ B (nonsym)
> >         >
> >         > So, the funny thing happens that i end up reciving audio
> >         from B to A ...
> >         > and
> >         > then I hear A's own audio after being bounced by B (funny,
> >         huh?). The
> >         > bouncing is due to rtpproxy changing the rtp port where he
> >         sends to B
> >         > ... he
> >         > starts with the one announced on SDP ... then, after the
> >         first RTP received
> >         > from B, he switches to this new port ... mmmm
> >         >
> >         > I guess this is a lost cause ... but maybe someone has a
> >         brilliant
> >         > idea?? :D
> >         > (like a hack in rtpproxy which suddenly turns it into
> >         > non-symmetrical-rtp-supported-endpoint proxy? :D )
> >         >
> >         > Regards,
> >         >
> >         > Cesc
> >         >
> >         >
> >         >
> >
> ------------------------------------------------------------------------
> >         >
> >         > _______________________________________________
> >         > Serusers mailing list
> >         > Serusers at lists.iptel.org
> >         > http://lists.iptel.org/mailman/listinfo/serusers
> >
> >
> >         --
> >         Klaus Darilion
> >         nic.at
> >
> >
> > _______________________________________________
> > Serusers mailing list
> > Serusers at lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serusers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20070124/eb635d09/attachment.htm>