<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi,<br>
      I'm not sure if I understood correctly, but in general what you
      can do is to create 2 Peering, let's see with the same IP:port:<br>
      <br>
      <div>Peering A</div>
      <div>Remote_IP:Remote_Port <-> Local_IP:5060</div>
      <br>
      <br>
      <div><span style="background-color: rgba(255, 255, 255, 0);">Peering
          B</span></div>
      <div><span style="background-color: rgba(255, 255, 255, 0);">Remote_IP:Remote_Port
          <-> Local_IP:5566<br>
          <br>
          <br>
          <br>
          In this way remote Peering A should connecto to your port 5060
          and remote peer B should configure itself to connect to you to
          port 5566.<br>
          Now, they expect you to send them packet via the same ports,
          so from 5060 to peer A, from 5566 to peer B.<br>
          What you need to do is to set up the peer preferences
          'outbound_socket' on peer A, selecting Local_IP:5060 and on
          peer B the other socket Local_IP:5566.<br>
        </span></div>
      <br>
      Is it what you were looking for ?<br>
      <br>
      <br>
      Daniel<br>
      <br>
      <br>
      <br>
      <br>
      <br>
      On 11/06/2014 09:35 PM, Marc Storck wrote:<br>
    </div>
    <blockquote
      cite="mid:7761144B-F0E9-4278-B9AE-13C9FA9B2A2E@voipgate.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div>I'm interested by this featute as well.</div>
      <div><br>
      </div>
      <div>In my case a peering could be setup between an remote ip:port
        tuple and an alternative local port. I don' necessarily need to
        use an alias Local IP.</div>
      <div><br>
      </div>
      <div>In the end this should provide the following:</div>
      <div><br>
      </div>
      <div>Peering A</div>
      <div>Remote_IP:Remote_Port <-> Local_IP:5060</div>
      <div><br>
      </div>
      <div>
        <div><span style="background-color: rgba(255, 255, 255, 0);">Peering
            B</span></div>
        <div><span style="background-color: rgba(255, 255, 255, 0);">Remote_IP:Remote_Port
            <-> Local_IP:5566</span></div>
        <div><span style="background-color: rgba(255, 255, 255, 0);"><br>
          </span></div>
        <div><span style="background-color: rgba(255, 255, 255, 0);">Where
            for Peering A and B the remote_ip and remote_port are
            identical, e.g. In both cases 203.0.113.1:5060.</span></div>
        <div><span style="background-color: rgba(255, 255, 255, 0);"><br>
          </span></div>
        <div><span style="background-color: rgba(255, 255, 255, 0);">While
            on the SPCE side Peering A would use 198.51.100.1:5060 and
            Peering B would use 198.51.100.1:5566, alternatively Peering
            A uses 198.51.100.1:5060 and Peering B uses
            198.51.100.2:5060.</span></div>
        <div><span style="background-color: rgba(255, 255, 255, 0);"><br>
          </span></div>
        <div><span style="background-color: rgba(255, 255, 255, 0);">Of
            course SPCE would have to comply with this as well for
            outbound calls to Peering A and Peering B respectively.</span></div>
        <div><span style="background-color: rgba(255, 255, 255, 0);"><br>
          </span></div>
        <div><span style="background-color: rgba(255, 255, 255, 0);">Regards,</span></div>
        <div><span style="background-color: rgba(255, 255, 255, 0);"><br>
          </span></div>
        <div><span style="background-color: rgba(255, 255, 255, 0);">Marc</span></div>
        <div><br>
        </div>
        <br>
      </div>
      <div><br>
        On 6 nov. 2014, at 20:38, Aziz Palmer <<a
          moz-do-not-send="true" href="mailto:Aziz.Palmer@AirFIBER.com">Aziz.Palmer@AirFIBER.com</a>>
        wrote:<br>
        <br>
      </div>
      <blockquote type="cite">
        <div>
          <div style="direction: ltr;font-family: Tahoma;color:
            #000000;font-size: 10pt;">
            <div>Good Afternoon,</div>
            <div><span style="font-size: 10pt;">Not sure if this is
                possible but here is what i'm hoping for:</span></div>
            <div><span style="font-size: 10pt;"><br>
              </span></div>
            <div>Currently when an inbound calls comes from a sip peer
              it matches the source ip address of the sip peer. I have
              setup multiple alias IP addresses and would like to match
              up not only the ip address of the peer but the alias ip
              address it is listening on?</div>
            <div><br>
            </div>
            <div><br>
              Thank you again for all your help SPCE Team has been
              providing us!</div>
          </div>
        </div>
      </blockquote>
      <blockquote type="cite">
        <div><span>_______________________________________________</span><br>
          <span>Spce-user mailing list</span><br>
          <span><a moz-do-not-send="true"
              href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a></span><br>
          <span><a moz-do-not-send="true"
              href="https://lists.sipwise.com/listinfo/spce-user">https://lists.sipwise.com/listinfo/spce-user</a></span><br>
        </div>
      </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>