<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><font color="#000000" class=""></font>On 11/02/2017, at 3:40 am, Frank Vanoni <<a href="mailto:mailinglist@linuxista.com" class="">mailinglist@linuxista.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">On Thu, 2017-02-09 at 14:58 +0200, Антон Сацкий wrote:<br class=""><br class=""><br class=""><blockquote type="cite" class="">so the main question is -- how to Disallow CALLS without registering<br class="">on PBX<br class=""></blockquote><br class="">sip.conf configuration<br class="">In the [general] section, define:<br class=""><br class=""><br class="">[general]<br class="">...<br class="">allowguest=no<br class="">alwaysauthreject=yes<br class="">...<br class=""></div></blockquote></div><br class=""><div class="">I don't think either of these configuration attributes achieve what the OP requested ("<span style="font-family: Menlo-Regular;" class="">how to Disallow CALLS without registering on PBX").</span></div><div class=""><br class=""></div><div class="">In fact, I'm not sure that it's actually possible to disallow [authenticated] calls from a peer that hasn't registered!</div><div class=""><br class=""></div><div class="">As far as I can tell, 'registration' was never intended to be part of the authentication process. It's sole purpose is to inform the PBX as to the current location of the endpoint. I suspect this means that what the OP is asking for cannot be achieved with the current code bases.</div><div class=""><br class=""></div><div class="">But each time I'm proven wrong I learn something, so if I'm wrong then please by all means correct me! :)</div><div class=""><br class=""></div><div class="">Pete</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>