<div dir="ltr">There is also:<div><br><div><ol style="margin:0px;padding:0px 0px 0px 48px;color:rgb(172,172,172);font-family:Consolas,Menlo,Monaco,'Lucida Console','Liberation Mono','DejaVu Sans Mono','Bitstream Vera Sans Mono',monospace,serif;font-size:12px;line-height:21px;background-color:rgb(248,248,248)">
<li class="" style><div class="" style="padding:0px 5px;vertical-align:top;color:rgb(0,0,0);border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);background-color:rgb(255,255,255)">modparam("auth_db|usrloc|uri", "use_domain", 1)</div>
</li></ol></div></div><div style>Please change that to 0. It's been a while since I have dealt with REGISTER authentiacation issues. Are you sure</div><div style>you need it? It's quite a resourceful process as the number of clients increase. What we do now, is use:</div>
<div style><br></div><div style>1) The address table</div><div style>2) Dialplan</div><div style>3) Dynamic Routing</div><div style>4) IPTables</div><div style><br></div><div style>To enforce who's INVITE gets processed by our servers. No registration required.<br>
</div><div style><br></div><div style>If you really want to handle REGISTER, I will take a closer look. Until then maybe look at Chapter 5 (Page 90),</div><div style>of <a href="ftp://115.146.120.141/voIP/Building%20Telephony%20Systems%20with%20OpenSIPS%201.6.pdf">ftp://115.146.120.141/voIP/Building%20Telephony%20Systems%20with%20OpenSIPS%201.6.pdf</a>. I know the</div>
<div style>answer is in there because I dealt with your issue a long time ago.</div><div style><br></div><div style>Kind Regards,</div><div style><br></div><div style>Nick</div></div>