<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head><body bgcolor="#FFFFFF" text="#000000">Hello<br>
<br>
Thanks Richard, You were right.<br>
Now the codec is recognized, and statistics show real data.<br>
Just a quick recap what needs to be done:<br>
- enable packet forwarding<br>
- firewalld add service SIP and UDP port range to enable incoming
traffic <br>
- enable packet flow between external / internal interfaces using
FORWARD and POSTROUTING direct rules<br>
- setup masquerading for the internal network<br>
<br>
Cheers,<br>
Istvan<br>
<br>
<span>Richard Fuchs a écrit le 01/04/2019 à 20:02 :</span><br>
<blockquote type="cite"
cite="mid:bdaf4552-bd6e-6801-1d8c-c66fca84243e@sipwise.com">On
01/04/2019 09.14, Istvan Mogyorosi wrote:
<br>
<blockquote type="cite">Dear all,
<br>
<br>This is my first post after reading a lot in this mailing-list.
<br>I'm trying to use Kamailio 5.1 with the dispatcher module and
rtpengine acting as SIP + RTP proxy.
<br>I have 6 asterisk servers in a private subnet that should talk with
the peer via a single IP like this:
<br>
<br>Asterisk 1..n|---> | GW.PRIVATE.IP -o- GW.PUBLIC.IP |---->
PEER.SIP.TRUNK
<br>
<br>I'm on Centos 7, with firewalld configured, iptables module is
loaded
and the rule is well defined.
<br>Packet forwarding is also enabled.
<br>
<br>Chain rtpengine (1 references)
<br>target prot opt source destination
<br>RTPENGINE udp -- anywhere anywhere RTPENGINE id:40
<br>
<br>My call flow seems to be fine, Kamailio/rtpengine private IP is the
outboundproxy parameter of Asterisk instances.
<br>
<br>My problem is that RTP packets are not present on the public
interface, the rtpengine final log showing
<br>the 2 sessions, but I'm not sure this is what I want or simply the
firewall does not let it out ?
<br>(To be more precise PEER.SIP.TRUNK is the trunk for SIP traffic, I
have multiple IP addresses
<br>for media to connect to, reinvites are allowed)
<br>
<br>Closing call due to timeout
<br>Final packet stats:
<br>--- Tag 'as6d12caea', created 1:00 ago for branch '', in dialogue
with
'as541b1e61'
<br>------ Media #1 (audio over RTP/AVP) using unknown codec
<br>--------- Port GW.PRIVATE.IP:10000 <> 192.168.30.13:11152,
SSRC 0, 0
p, 0 b, 0 e, 60 ts
<br>--------- Port GW.PRIVATE.IP:10001 <> 192.168.30.13:11153
(RTCP),
SSRC 0, 0 p, 0 b, 0 e, 60 ts
<br>
<br>--- Tag 'as541b1e61', created 1:00 ago for branch '', in dialogue
with
'as6d12caea'
<br>------ Media #1 (audio over RTP/AVP) using unknown codec
<br>--------- Port GW.PUBLIC.IP:10000 <> PEER.SIP.TRUNK:28216,
SSRC 0,
0 p, 0 b, 0 e, 60 ts
<br>--------- Port GW.PUBLIC.IP:10001 <> PEER.SIP.TRUNK:28217
(RTCP),
SSRC 0, 0 p, 0 b, 0 e, 60 ts
<br>
<br></blockquote>
These are all reception counters, so this is a problem of packets not
being received. Having the iptables RTPENGINE rule installed does not
automatically allow the packets to pass through your firewall. You have
to do that separately.
<br>
<br>
Cheers
<br>
<br>
<br>
_______________________________________________
<br>
Kamailio (SER) - Users Mailing List
<br>
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
<br>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<div>Sent from <a
href="https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach"><span
style="color: rgb(0, 157, 247);">Postbox</span></a></div></div>
</body></html>