<div dir="ltr"><div><div><div>Hi Walter<br><br></div>Yes that of course could work but we won't have sufficient IP addresses for that in the long run I reckon.<br><br></div>I have stuck with the prefix which is now working as expected I think. Rather than bothering the client with prefixing it, I use a rewrite rule to prefix it with "peer1" or "peer2" etc. That prefix I use in the peering rules to ensure it selects the correct one, and then strip it again when it goes out to the peer. I will test it in production but this should do it then.<br><br></div>Cheers<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 19, 2018 at 1:43 AM, Walter Klomp <span dir="ltr"><<a href="mailto:walter@myrepublic.net" target="_blank">walter@myrepublic.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space">Hi Theo,<div><br></div><div>If “ip addresses” is all you can work with then assign multiple IP addresses to the server and use that as authentication.<div><br></div><div>reseller A - 1.1.1.1</div><div>reseller B - 1.1.1.2 </div><div>…etc…</div><div><br></div><div>(provided you have enough IP addresses as they are getting scarce...<br><div><br class="m_6281801836347911235webkit-block-placeholder"></div><div>
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><font face="Times New Roman" size="3">Regards</font></div><span class="HOEnZb"><font color="#888888"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><font face="Times New Roman" size="3">Walter.<br></font><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br></div><table class="m_6281801836347911235x_MsoNormalTable" style="font-family:Helvetica;letter-spacing:normal;text-indent:0px;text-transform:none;word-spacing:0px;width:259.8pt" width="400" cellspacing="0" cellpadding="0" border="0"><tbody><tr><td style="padding:0in" valign="top"><br></td></tr></tbody></table></div></font></span></div>
</div><div><div class="h5">
<div><br><blockquote type="cite"><div>On 19 Jan 2018, at 7:24 AM, Theo <<a href="mailto:axessofficetheo@gmail.com" target="_blank">axessofficetheo@gmail.com</a>> wrote:</div><br class="m_6281801836347911235Apple-interchange-newline"><div><div dir="ltr"><div>Apologies, I see I accidentally replied to the posters only. My response was:<br><br><br><br>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.<br><br><span class="m_6281801836347911235gmail-im"><tt>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></tt></span></div><span class="m_6281801836347911235gmail-im"><tt>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?<br><br></tt></span><div><br><div class="m_6281801836347911235gmail-yj6qo m_6281801836347911235gmail-ajU"><div id="m_6281801836347911235gmail-:14x" class="m_6281801836347911235gmail-ajR"><img class="m_6281801836347911235gmail-ajT" src="https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif"></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 18, 2018 at 4:04 PM, Daniel Grotti <span dir="ltr"><<a href="mailto:dgrotti@sipwise.com" target="_blank">dgrotti@sipwise.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div 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.<span class="m_6281801836347911235HOEnZb"><font color="#888888"><br>
<br>
Daniel<br>
<br>
<br>
</font></span></tt><div><div class="m_6281801836347911235h5">
<div class="m_6281801836347911235m_8599597055001749377moz-cite-prefix">On 01/18/2018 02:46 PM, Theo wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="m_6281801836347911235h5">
<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="m_6281801836347911235m_8599597055001749377mimeAttachmentHeader"></fieldset>
<br>
</div></div><span><pre>______________________________<wbr>_________________
Spce-user mailing list
<a class="m_6281801836347911235m_8599597055001749377moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a>
<a class="m_6281801836347911235m_8599597055001749377moz-txt-link-freetext" href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/list<wbr>info/spce-user</a>
</pre>
</span></blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/list<wbr>info/spce-user</a><br>
<br></blockquote></div><br></div>
______________________________<wbr>_________________<br>Spce-user mailing list<br><a href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br><a href="https://lists.sipwise.com/listinfo/spce-user" target="_blank">https://lists.sipwise.com/<wbr>listinfo/spce-user</a><br></div></blockquote></div><br></div></div></div></div></div></blockquote></div><br></div>