[Spce-user] connect 2 sipwise as trunk

[stefanormc]

Hi all, thanks for the support.

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.

I’m using mr5.4.1
<https://centrale03.avanzati.it:1443/statistics/versions>
Please note that on this version peer_auth only works manually as described
on documentation

Thanks

Ciao

Stefano

On 29 November 2017 at 21:49:53, Jon Bonilla (Manwe) (manwe at sipdoc.net)
wrote:

El Wed, 29 Nov 2017 20:09:06 +0000
Barry Flanagan <barry at flanagan.ie> escribió:


> >
> >
> I think you would also need to do the reverse as well, so both SPCE have
a
> peer to the other for outbound, and a subscriber for the inbound. Peers
and
> Subscribers would need to use authentication as mentioned above, so that
> they don't get mixed up.
>
> Alternatively, I think you can set allow_peer_relay to "yes" in
> /etc/ngcp-config/config.yml which would allow a call to come in from one
> peer and get sent out to another peer (based on routing rules), although
> this only would work if you did not need to bill, as peer-to-peer does
not
> get billed.
>
>

If you set another system as peer and subscriber when an incoming call
comes it
will be detected as peer and won't be authenticated. No need for
authenticate
the peer, right?

Maybe it could work, yes. You would send via subscriber with permanent
contact
and it would be detected as incoming form peer in the other side. No need
for
enable_peer_relay in that case.
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20171129/ae25a0f3/attachment-0001.html>