<html>
<head>
<meta content="text/html; charset=gbk" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Andrew,<br>
I just use git... so not sure on the rpm stuff. However I believe
4.2 is to be released as stable branch tomorrow (see other recent
thread by Daniel) so the packages probably aren't far behind. <br>
<br>
The main reasons I see for using the 4.2 branch are:<br>
1) its going to be stable release very soon<br>
2) the options on rtpengine have been refactored ... makes sense
to develop on the new version so that you can move from
development to production without amending your kamailio.cfg<br>
3) rtpengine seems to be getting quite alot of rapid progress at
the moment and gaining stability and features ... I'd rather be on
the latest version.<br>
<br>
Having said all that the logic in the kamailio.cfg for version 4.1
is the same and should work for you if you want to work from the
current stable packages.<br>
<pre class="moz-signature" cols="72">
</pre>
On 13/10/14 11:10, andrew wrote:<br>
</div>
<blockquote
cite="mid:3909b34e.4b87.14908fcdbf2.Coremail.androidappaccount@163.com"
type="cite">
<div
style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial">
<div>hi,</div>
<div><br>
</div>
<div>thanks for your help.</div>
<div><br>
</div>
<div>rtpengine module is used only in kamalio 4.2.x ------
development version. where to get its rpm packet?</div>
<div><br>
</div>
<div>B.R.</div>
<div><br>
</div>
<div>andrew</div>
<div><br>
</div>
<div><br>
</div>
At 2014-10-13 16:38:47, "Paul Smith"
<a class="moz-txt-link-rfc2396E" href="mailto:paul.smith@claritytele.com"><paul.smith@claritytele.com></a> wrote:<br>
<blockquote id="isReplyContent" style="PADDING-LEFT: 1ex;
MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="moz-cite-prefix">Hi Andrew<br>
There is a condition in the NATMANAGE route which tests
whether or not to apply rtpproxy_manage() :<br>
<blockquote>
<pre>if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB)))
return;
</pre>
</blockquote>
One way to force this is to make sure that FLT_NATS is
always set. That can be done in the NATDETECT route by
moving setflag(FLT_NATS) outside of the if(nat_uac_test)
condition and putting it just before the return statement,
so the flag is always set.<br>
<br>
Another way would be to remove or comment out the if
"!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return;"
line from NATMANAGE so that the the rtp_manage() is always
called.<br>
<br>
It might be worth your while upgrading to the 4.2 branch
which has renamed the rtpproxy-ng module to rtpengine and
made the options in the call to rtpengine_manage() more
readable.<br>
<br>
Depending on why you always want to run the rtp proxy ...
you might also want to set :<br>
<pre> rtpengine_manage(replace-session-sonnection replace-origin ICE=force-relay) </pre>
to ensure that media always goes through your media proxy
and no other connections are negotiated between the
endpoints.<br>
<pre class="moz-signature" cols="72">
</pre>
On 13/10/14 08:36, andrew wrote:<br>
</div>
<blockquote
cite="mid:7eec2d1b.eadf.1490870489a.Coremail.androidappaccount@163.com"
type="cite">
<div
style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial">
<div>hi,</div>
<div><br>
</div>
<div>kamailio 4.1.5 is used with rtpengine, whose older
counterpart is rtpproxy-ng. I made some changes based on
the default configuration files(i.e. kamailio.cfg), so
that rtpproxy-ng module is enabled. Kamailio.cfg has
been uploaded. In kamailio.cfg, there is one route block
related to rtpproxy, i.e. route[NATMANAGE],
where rtpproxy_manage("co") is called. Sometimes,
rtpproxy-ng can insert new ip:port candidates in SDP.
But in some case, rtpproxy-ng doesn't rewrite SDP, so
rtpengine doesn't relay rtp packets at all.</div>
<div><br>
</div>
<div>How to setup kamailio.cfg, so that rtpproxy-ng moudle
can always rewritten new ip:port candidates, and
rtpengine always relays rtp packets?</div>
<div><br>
</div>
<div>Looking foreward to your reply. Thanks!</div>
<div><br>
</div>
<div>B.R.</div>
<div><br>
</div>
<div>Andrew</div>
</div>
<br>
<br>
<span title="neteasefooter"><span id="netease_mail_footer"></span></span><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
</blockquote>
</div>
<br>
<br>
<span title="neteasefooter"><span id="netease_mail_footer"></span></span>
</blockquote>
<br>
</body>
</html>