Thanks.<br>But I don't understand the use of aliases table.<br><br>I have defined some subscriber users, with username (like BOB) and password (BOBPWD). So, if I wanted to access the system, I would send a REGISTER message with correct username and password (authorization required). Then my proxy address will be "
sip:BOB@IP_PROXY" and my Contact will be "sip:BOB@MY_IP_ADRRESS".<br>These information are saved into USER LOCATION table (save("location") function).<br>Now, through DB_aliases module and dbaliases table, I can define some aliases for BOB (like "
sip:1234@IP_PROXY", etc...), so if an INVITE for bob has "sip:1234@IP_PROXY" as R-URI, with db_aliases_lookup() function I can rewrite R-URI with Bob's URI ("bob@IP_PROXY") and then call the lookup("location") function.
<br>But I don't understand how I can use the ALIASES table.<br>Are there any example explaining its use ?<br>Sorry.<br><br>Regards,<br>daniel<br> <br><br>Iñaki Baz Castillo wrote:
<blockquote cite="mid200711151449.30507.ibc@in.ilimit.es" type="cite">
<pre>El Thursday 15 November 2007 14:31:52 Daniel escribi�:<br></pre>
<blockquote type="cite"><pre>Hi all,<br>what is the different between Aliases table and DB aliases table? What is<br>their use ?<br></pre></blockquote>
<pre><br>"aliases" table is same as "location" table but it should be used to look for <br>alias with the function lookup("aliases").<br><br>Of course, aliases are simpler than the complex location or aliases tables
<br>that manage more info about users, so in order to implement alias system in a <br>simpler way the module ALIAS_DB exists and its table dbaliases.<br><br>Note that dbaliases table is much simpler (it's just valid for aliases),
<br>Look at the module doc:<br> <a href="http://www.openser.org/docs/modules/1.3.x/alias_db.html">http://www.openser.org/docs/modules/1.3.x/alias_db.html</a><br><br><br></pre>
</blockquote>
<br clear="all"><br>-- <br>Daniel Grotti<br>________________________<br>e-mail : <a href="mailto:d.grotti@gmail.com">d.grotti@gmail.com</a>