<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap:break-word;line-break:after-white-space"><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)">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">manwe@sipdoc.net</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>El Wed, 29 Nov 2017 20:09:06 +0000
<br>Barry Flanagan <<a href="mailto:barry@flanagan.ie">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">Spce-user@lists.sipwise.com</a><br><a href="https://lists.sipwise.com/listinfo/spce-user">https://lists.sipwise.com/listinfo/spce-user</a><br></div></div></span></blockquote></body></html>