I think you're right, but this is the way our db was contructed, it would be very expensive to change it now.<br>I probably will call an external webservice to save users location.<br><br>Thank you very much.<br><br clear="all">
Santiago Soares<br>Fone: (41) 8488-0537<br>
<br><br><div class="gmail_quote">On Mon, Apr 11, 2011 at 5:51 AM, Henning Westerholt <span dir="ltr"><<a href="mailto:henning.westerholt@1und1.de">henning.westerholt@1und1.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Sunday 10 April 2011, Santiago Soares wrote:<br>
> I'm trying to use kamailio 1.5.3 as a registrar server. I have a table<br>
> on my db that contains all user information, like username, password,<br>
> expire time and ip address, so kamailio should use the same table to<br>
> authenticate users AND save their location.<br>
> The problem is that kamailio complains about table version when<br>
> starts. It expects a different version number for location table and<br>
> auth_db table. Is there any way I could use the same table for both<br>
> functions? I'd appreciate any help!<br>
<br>
</div>Hi Santiago,<br>
<br>
so you want to store subscriber data (which is mostly read-only) in the same<br>
table as location data (which gets updated frequently)? I don't think this is<br>
a good idea. Furthermore booth tables are not really compatible, you probably<br>
need to change something in the code to be able to do this.<br>
<br>
If you need to present this data in one point, what about just using the two<br>
standard tables and then creating a view that presents it appropriately?<br>
<br>
Cheers,<br>
<font color="#888888"><br>
Henning<br>
</font></blockquote></div><br>