<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <tt>Hi Stefano,<br>
      you can just route calls to the other peer via subscribers
      aliases, indeed.<br>
      <br>
      <br>
    </tt>
    <pre class="moz-signature" cols="72">-- 
Daniel Grotti
Head of Customer Support
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)130120332
Email: <a class="moz-txt-link-abbreviated" href="mailto:dgrotti@sipwise.com">dgrotti@sipwise.com</a>
Website: <a class="moz-txt-link-freetext" href="https://www.sipwise.com">https://www.sipwise.com</a>
</pre>
    <div class="moz-cite-prefix">On 11/29/2017 09:58 PM, stefanormc
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHTRqyVhgQzBSzWnBLdHzwqmX5Q0L_3+bi_E_171ESzzpxOE1Q@mail.gmail.com">
      <style>body{font-family:Helvetica,Arial;font-size:13px}</style>
      <div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Hi
        all, thanks for the support. </div>
      <div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br>
      </div>
      <div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Trial
        is working, tomorrow I’ll check in production. I don’t think you
        have to setup 2 peers but I think you have to set all aliases
        subscriber side to route calls correctly.</div>
      <div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br>
      </div>
      <div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">I’m
        using <a
          href="https://centrale03.avanzati.it:1443/statistics/versions"
style="color:rgb(192,222,179);outline:0px;font-family:"Open
Sans",arial,sans-serif;font-size:12px;font-variant-ligatures:normal;background-color:rgb(73,119,52)"
          moz-do-not-send="true">mr5.4.1<br>
        </a></div>
      <div id="bloop_sign_1511988657300451072" class="bloop_sign">Please
        note that on this version peer_auth only works manually as
        described on documentation</div>
      <div id="bloop_sign_1511988657300451072" class="bloop_sign"><br>
      </div>
      <div id="bloop_sign_1511988657300451072" class="bloop_sign">Thanks</div>
      <div id="bloop_sign_1511988657300451072" class="bloop_sign"><br>
      </div>
      <div id="bloop_sign_1511988657300451072" class="bloop_sign">Ciao</div>
      <div id="bloop_sign_1511988657300451072" class="bloop_sign"><br>
      </div>
      <div id="bloop_sign_1511988657300451072" class="bloop_sign">Stefano </div>
      <br>
      <p class="airmail_on">On 29 November 2017 at 21:49:53, Jon Bonilla
        (Manwe) (<a href="mailto:manwe@sipdoc.net"
          moz-do-not-send="true">manwe@sipdoc.net</a>) wrote:</p>
      <blockquote type="cite" class="clean_bq"><span>
          <div>
            <div>El Wed, 29 Nov 2017 20:09:06 +0000
              <br>
              Barry Flanagan <<a href="mailto:barry@flanagan.ie"
                moz-do-not-send="true">barry@flanagan.ie</a>>
              escribió:
              <br>
              <br>
              <br>
              > >
              <br>
              > > <br>
              > I think you would also need to do the reverse as
              well, so both SPCE have a
              <br>
              > peer to the other for outbound, and a subscriber for
              the inbound. Peers and
              <br>
              > Subscribers would need to use authentication as
              mentioned above, so that
              <br>
              > they don't get mixed up.
              <br>
              > <br>
              > Alternatively, I think you can set allow_peer_relay
              to "yes" in
              <br>
              > /etc/ngcp-config/config.yml which would allow a call
              to come in from one
              <br>
              > peer and get sent out to another peer (based on
              routing rules), although
              <br>
              > this only would work if you did not need to bill, as
              peer-to-peer does not
              <br>
              > get billed.
              <br>
              > <br>
              >
              <br>
              <br>
              If you set another system as peer and subscriber when an
              incoming call comes it
              <br>
              will be detected as peer and won't be authenticated. No
              need for authenticate
              <br>
              the peer, right?
              <br>
              <br>
              Maybe it could work, yes. You would send via subscriber
              with permanent contact
              <br>
              and it would be detected as incoming form peer in the
              other side. No need for
              <br>
              enable_peer_relay in that case. <br>
              _______________________________________________<br>
              Spce-user mailing list<br>
              <a href="mailto:Spce-user@lists.sipwise.com"
                moz-do-not-send="true">Spce-user@lists.sipwise.com</a><br>
              <a href="https://lists.sipwise.com/listinfo/spce-user"
                moz-do-not-send="true">https://lists.sipwise.com/listinfo/spce-user</a><br>
            </div>
          </div>
        </span></blockquote>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Spce-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>
<a class="moz-txt-link-freetext" href="https://lists.sipwise.com/listinfo/spce-user">https://lists.sipwise.com/listinfo/spce-user</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>