[Spce-user] Best practices on Class4 setup

[Marco Teixeira]

Sorry the leave you without a follow-up... Christmas et all, got part of my
attention :)
I will mangle with IP and HOSTNAME fields of the peer and if the issue
persists i will post a debug about this.
Thank you.


---
Marco
---


On Fri, Dec 18, 2015 at 8:45 PM, Andreas Granig <agranig at sipwise.com> wrote:

> Actually after checking once more the documentation of
> http://www.kamailio.org/docs/modules/stable/modules/lcr.html, the
> RURI-domain should be set to the IP of the peer if the "ip address" is
> set and the "hostname" is not set.
>
> So yeah, a proxy log or better a network trace of a packet from spce to
> peer and its reply message would be interesting, along with the values
> you configured in the peering server.
>
> Andreas
>
> On 12/18/2015 09:37 PM, Andreas Granig wrote:
> > Hi,
> >
> > For peering servers there is the "ip address" and the "hostname" field.
> > If you only fill in the ip, the hostname of the initial RURI-domain is
> > preserved. If you only fill in the hostname, the hostname is put into
> > RURI-domain and the ip is resolved via DNS. If you put in both IP and
> > hostname, the request is sent to the IP part and the RURI-domain part is
> > replaced by the hostname. You probably want the 3rd option here.
> >
> > Andreas
> >
> > On 12/18/2015 01:44 PM, Daniel Grotti wrote:
> >> Hi,
> >> that's sound strange, can you provide a proxy.log ?
> >>
> >>
> >> --
> >> Daniel Grotti
> >> VoIP Engineer
> >>
> >>
> >> Sipwise GmbH
> >> Europaring F15 | 2345 Brunn am Gebirge, Austria | www.sipwise.com
> >>
> >> On 12/18/2015 01:42 PM, Marco Teixeira wrote:
> >>> Daniel,
> >>> Thankx.
> >>>
> >>> On the second issue, that is not happening... I have subscriber on
> >>> domain x.com <http://x.com> and invites sent out to peers are
> preserving
> >>> the original x.com <http://x.com> domain...
> >>> Running 3.8.4
> >>> Any option i might check ?
> >>>
> >>> Em 18/12/2015 12:36, "Daniel Grotti" <dgrotti at sipwise.com
> >>> <mailto: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 <mailto:Spce-user at lists.sipwise.com>
> >>>     > https://lists.sipwise.com/listinfo/spce-user
> >>>     >
> >>>
> >>>
> >>>
> >>>     _______________________________________________
> >>>     Spce-user mailing list
> >>>     Spce-user at lists.sipwise.com <mailto: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
> >>
> > _______________________________________________
> > 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/mailman/private/spce-user_lists.sipwise.com/attachments/20160102/2e53343e/attachment.html>