[Spce-user] clients having difficulty with domain concept

[Theo]

Apologies, I see I accidentally replied to the posters only. My response
was:



The issue is that I have multiple resellers. I can't create that domain and
assign it to multiple resellers or am I seeing that wrong - so the solution
of just adding the ip as a domain won't work for that.

Another option would be to create the IP domain (in order to accept
incoming reqeust), leave the subscriber on the URL-domain and enable the
"ignore_auth_realm", so the domain is not used in the AUTH process.

I did this and that solves the problem but there is another snatch. Calls
for various clients have to go out through different peers using remote
authentication settings in the subscriber. The way those calls are forced
out over peer x y or z is by using the domain as a pattern. Because the
domain is not present in the header, it does not select the correct peer
anymore. I am getting around that for the moment by asking the client to
prefix their calls and select the peer based on that but that's not ideal.
What would work is if a peer could be selected based on who the client is.
Any way of doing that?



On Thu, Jan 18, 2018 at 4:04 PM, Daniel Grotti <dgrotti at sipwise.com> wrote:

> Hi,
> if they can send request with IP into the URI, then you should add a
> domain with that IP.
> You can create those subscribers under that domain.
>
> Another option would be to create the IP domain (in order to accept
> incoming reqeust), leave the subscriber on the URL-domain and enable the
> "ignore_auth_realm", so the domain is not used in the AUTH process.
>
> Daniel
>
>
> On 01/18/2018 02:46 PM, Theo wrote:
>
> Hi
>
> I have a number of rather large clients who I am wanting to move to our
> sipwise CE edition. However, they claim they can't use domains - so the
> header only contains the IP address. I have set them up under trusted
> sources with their IP but that still requires the correct domain to be sent.
>
> Their argument is "no other carrier requires this - so sort it out". I
> cannot use the ip as a domain because this problem is across resellers.Is
> there a way around this?
>
>
>
>
> _______________________________________________
> Spce-user mailing listSpce-user at lists.sipwise.comhttps://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/20180119/78e8fa57/attachment-0001.html>