<div dir="ltr">Thanks very much!<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno mar 5 mar 2019 alle ore 18:19 Daniel Grotti <<a href="mailto:dgrotti@sipwise.com">dgrotti@sipwise.com</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF">
    <tt>Ciao Daniele!<br>
      you should open (for incoming traffic) at least all the possible
      UDP ports used by RTPengine.<br>
      You should find the min and max value in config.yml, under
      rtpproxy section (maxport and minport).<br>
      <br>
      Cheers,<br>
      <br>
    </tt>
    <pre class="gmail-m_1031711181461123546moz-signature" cols="72">--
Daniel Grotti

Head of Customer Support                               Sipwise GmbH
e: <a class="gmail-m_1031711181461123546moz-txt-link-abbreviated" href="mailto:dgrotti@sipwise.com" target="_blank">dgrotti@sipwise.com</a>                               Europaring F15
t: +43(0)130120332                          A-2345 Brunn Am Gebirge
w: <a class="gmail-m_1031711181461123546moz-txt-link-abbreviated" href="http://www.sipwise.com" target="_blank">www.sipwise.com</a>          FN: 305595f      FG: LG Wiener Neustadt
</pre>
    <div class="gmail-m_1031711181461123546moz-cite-prefix">On 3/5/19 6:05 PM, Daniele Renda wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="ltr">
        <div dir="ltr">
          <div>Thanks for your reply.</div>
          <div><br>
          </div>
          <div>I confirm I set the advertised-ip is right:</div>
          <div><br>
          </div>
          <div>interface = ext/<a href="http://172.31.25.213" target="_blank">172.31.25.213</a>!34.xx.xx.153;int/<a href="http://127.0.0.1" target="_blank">127.0.0.1</a>;int/::1</div>
          <div><br>
          </div>
          <div>That was not the problem. Thanks to your advice I
            realized my providers send the RTP flow from a different ip
            I thought, and I guess the opened 5060 UDP port is not
            enough.</div>
          <div><br>
          </div>
          <div>Any advice about opening traffic from the provider I'm
            interconnected with?</div>
          <div><br>
          </div>
          <div>Thanks<br>
          </div>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">Il giorno mar 5 mar 2019 alle
          ore 17:08 Richard Fuchs <<a href="mailto:rfuchs@sipwise.com" target="_blank">rfuchs@sipwise.com</a>>
          ha scritto:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div bgcolor="#FFFFFF">
            <div class="gmail-m_1031711181461123546gmail-m_-9015237794114334183moz-cite-prefix">On
              05/03/2019 09.59, Daniele Renda wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="ltr">
                <div dir="ltr">
                  <div dir="ltr">
                    <div>Hi,</div>
                    <div>I'm new to C5 CE, so sorry if my question is
                      too banal.</div>
                    <div>I installed C5 mr7.1.1 on a AWS t2.medium
                      instance. I followed step by step the tutorial <a href="https://www.sipwise.org/doc/mr7.1.1" target="_blank">https://www.sipwise.org/doc/mr7.1.1</a>
                      and I also set the advertised-ip.</div>
                    <div><br>
                    </div>
                    <div>I created a peer (outbound/inbound). The
                      scenario is simple: I have a DID bought from a
                      provider and I need to receive and make calls via
                      SipwiseC5.</div>
                    <div><br>
                    </div>
                    <div>I was able to create the outbound registration
                      to the provider, but in the provider side I see
                      the registration comes with the private ip of the
                      EC2 instance (i.e. 172.xx.xx.xx): so when I make a
                      call to my mobile phone for example I see the
                      phone ringing but when I pick up the call I don't
                      hear any audio. <br>
                    </div>
                    <div><br>
                    </div>
                    <div>The rtp.log shows:</div>
                    <div><br>
                    </div>
                    <div>] INFO:
                      [313535313739363530363535363736-52dacv20j9ei]:
                      ------ Media #1 (audio over RTP/AVP) using unknown
                      codec<br>
                      Mar  5 14:35:54 ip-172-31-25-213 (info)
                      rtpengine[591]: [1551796554.000202] INFO:
                      [313535313739363530363535363736-52dacv20j9ei]:
                      --------- Port   <a href="http://172.31.25.213:30114" target="_blank">172.31.25.213:30114</a>
                      <>  95.xx.xx.252:63416, SSRC 0, 0 p, 0<br>
                    </div>
                    <div><br>
                    </div>
                    <div>Where should I specify my public ip in order it
                      is used correctly also for RTP stream? I didn't
                      find hints in the guide.</div>
                  </div>
                </div>
              </div>
            </blockquote>
            <p>The advertised-ip is supposed to take care of that. You
              can confirm it by looking at the `interface=` line in
              /etc/rtpengine/rtpengine.conf, it should look something
              like this:</p>
            <p>interface = ext/<a href="http://172.31.25.213" target="_blank">172.31.25.213</a>!198.51.100.23;int/<a href="http://127.0.0.1" target="_blank">127.0.0.1</a>;int/::1</p>
            <p>In rtp.log you still see the internal private IP address
              since this is what rtpengine uses to actually send and
              receive packets.</p>
            <p>You can further confirm it by setting rtpengine's log
              level to 7 (debug) and then looking at the outgoing SDP
              body after rewrite in rtp.log.</p>
            <p>Cheers<br>
            </p>
          </div>
          _______________________________________________<br>
          Spce-user mailing list<br>
          <a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
          <a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
        </blockquote>
      </div>
      <br clear="all">
      <br>
      -- <br>
      <div dir="ltr" class="gmail-m_1031711181461123546gmail_signature">Daniele Renda</div>
      <br>
      <fieldset class="gmail-m_1031711181461123546mimeAttachmentHeader"></fieldset>
      <pre class="gmail-m_1031711181461123546moz-quote-pre">_______________________________________________
Spce-user mailing list
<a class="gmail-m_1031711181461123546moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a>
<a class="gmail-m_1031711181461123546moz-txt-link-freetext" href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a>
</pre>
    </blockquote>
    <br>
  </div>

_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature">Daniele Renda</div>