<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<tt>Hi,<br>
if they can send request with IP into the URI, then you should add
a domain with that IP.<br>
You can create those subscribers under that domain.<br>
<br>
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.<br>
<br>
Daniel<br>
<br>
<br>
</tt>
<div class="moz-cite-prefix">On 01/18/2018 02:46 PM, Theo wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+9+E=WqxAz_XPJj=ni1OOj2NzA4MEJDyF3yMF+a+LQh7oozTg@mail.gmail.com">
<div dir="ltr">
<div>
<div>Hi<br>
<br>
</div>
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.<br>
<br>
</div>
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?<br>
<br>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Spce-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>
<a class="moz-txt-link-freetext" href="https://lists.sipwise.com/listinfo/spce-user">https://lists.sipwise.com/listinfo/spce-user</a>
</pre>
</blockquote>
<br>
</body>
</html>