[Spce-user] Best practices on Class4 setup

[Marco Teixeira]

Daniel,
Thankx.

On the second issue, that is not happening... I have subscriber on domain
x.com and invites sent out to peers are preserving the original x.com
domain...
Running 3.8.4
Any option i might check ?
Em 18/12/2015 12:36, "Daniel Grotti" <dgrotti at sipwise.com> escreveu:

> Hi Marco,
>
> On 12/18/2015 12:04 PM, Marco Teixeira wrote:
> > Good day all,
> >
> > Looking for a little advise from your best practices.
> > Having multiple peers serving the same destinations, how would you
> > manage how the routing is done ?
> > Say i want client X to go out on peer Y, (without asking costumer to add
> > prefix) ?
> > Add a prefix on inbound subscriber ?
> >
>
> You can use the field "Caller Patter" in the peering rule if you want to
> use match that particular "callee prefix" using that particular peering
> server.
>
>
> > Another question, when binding peers to different sockets (IP's), is it
> > required to create domain for each used IP ?
> > SPCE is not rewriting the domain part of the R-URI on outbound, and peer
> > throws back "forbiden"...
> >
>
> Don't understand what you mean here. But when SPCE generates and
> outbound INVITE to the peering server the RURI is :
>
> sip:called_number at peering_IP:peering_port
>
>
> That's by default.
> You can rewrite the RURI domain part with a peering domain name by
> specifying in the peering server configuration the field "hostname".
>
>
> Cheers,
> Daniel
>
> >
> > Best regards
> > Marc
> > ​o
> >
> >
> >
> > _______________________________________________
> > Spce-user mailing list
> > Spce-user at lists.sipwise.com
> > https://lists.sipwise.com/listinfo/spce-user
> >
>
>
>
> _______________________________________________
> 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/20151218/967af4f0/attachment-0001.html>