Just so you know...<br><br> <param name="accept-blind-reg" value="true"/><br>
<param name="accept-blind-auth" value="true"/><br><br>These will have no effect in the user directory. They only apply to SIP profiles.<br><br>-Steve<br><br><br><br><div class="gmail_quote">
On 27 June 2011 02:23, Kurtis Heimerl <span dir="ltr"><<a href="mailto:kheimerl@cs.berkeley.edu">kheimerl@cs.berkeley.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello FS Users!<br>
<br>
I'm trying to create the following setup. When a user registers, if<br>
they register on a known account (lets say X), they do not need a<br>
password. X's registration is immediately OK'd, and everything is<br>
great. I've gotten that working using the ACL. The IP address of our<br>
SIP clients are added through cidr and the clients do not need to give<br>
passwords.<br>
<br>
However, for some reason, if another account that does not exist in<br>
the directory (let's say Y) registers, FS returns with a 200 OK,<br>
instead of rejecting Y. I'm trying to figure out why this is the case,<br>
and how to remedy that fact.<br>
<br>
I have the following line in my internal.xml file, which I had assumed<br>
would force this function:<br>
<!-- Force the user and auth-user to match. --><br>
<param name="inbound-reg-force-matching-username" value="true"/><br>
<br>
However, it does not work. In my directory, each individual account as<br>
the following lines:<br>
<user id="1303"><br>
<params><br>
<param name="accept-blind-reg" value="true"/><br>
<param name="accept-blind-auth" value="true"/><br>
<param name="vm-password" value="1000"/><br>
</params><br>
<br>
Though I've found that removing it (from all users in the directory)<br>
doesn't help.<br>
<br>
I'm primarily concerned with the line in internal.xml; it seems<br>
possible that the fact that we do not have an auth-user (because we do<br>
not require auth) means that this won't work. However, I have yet to<br>
test that hypothesis. The ACL has been the most confusing aspect of<br>
this installation, with a lot of undocumented aspects, and I get the<br>
nagging feeling this is another. I could very well be wrong though.<br>
<br>
Thanks for any direction.<br>
<br>
_______________________________________________<br>
Join us at ClueCon 2011, Aug 9-11, Chicago<br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a> 877-7-4ACLUE<br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><div style="visibility: hidden; left: -5000px; position: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-top: 0px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 130%;" id="avg_ls_inline_popup">
</div>