Hi Iñaki.<br><br>I think it is a good idea; there are other cases as user agents not intended to register in a particular class of service (For example, asterisk PBX in a registrar for home users), or buggy firmware versions of terminals.<br>
<br>Would it not be better to have the reference of forbidden user agents in database, instead of text file?<br><br>what do you think.<br><br>Regards.<br><br>Sergio.<br><br><div class="gmail_quote">On Fri, Dec 26, 2008 at 11:58 AM, Iñaki Baz Castillo <span dir="ltr"><<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi, for now in order to avoid pua_usrloc generating PUBLISH for UA's<br>
supporting presence I do the following test:<br>
<br>
### PUA_USRLOC PUBLISH<br>
if $ua !~ "UAS_SUPPORTING_PRESENCE" {<br>
xlog("L_INFO","--- pua_set_publich for $fu ($ua)\n");<br>
pua_set_publish();<br>
}<br>
<br>
<br>
Where:<br>
define(`UAS_SUPPORTING_PRESENCE', `^(Twinkle/1|Snom|Linphone|eyeBeam|X-Lite|SIP<br>
Communicator|SIPp|PJSUA)')<br>
<br>
<br>
I think it would be useful to do it in a more ellegant way, perhaps by<br>
having a text file containing User-Agent regular expressions loaded<br>
during OpenSIPS startup (and hopefully also with a FIFO command).<br>
Something like "permissions.allow" file.<br>
<br>
Any tip about how to start with it? is something as<br>
"permissions.allow" a good way to start? suggestions?<br>
<font color="#888888"><br>
--<br>
Iñaki Baz Castillo<br>
<<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>><br>
_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/devel" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/devel</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Sergio Gutiérrez<br>