Hello Dan.<br><br>Again, thanks a lot for your feedback. I have a final question, and again, I am not sure whether is a missunderstanding.<br><br>I do not see whether the avp can be changed dynamically; my approach allows to change the traced user list at execution time, and it is not necessary to restart OpenSIPS.<br>
<br>Thanks and regards.<br><br>Sergio Gutierrez.<br><br><div class="gmail_quote">On Mon, Oct 27, 2008 at 5:56 PM, Dan Pascu <span dir="ltr"><<a href="mailto:dan@ag-projects.com">dan@ag-projects.com</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;"><div class="Ih2E3d">On Monday 27 October 2008, Sergio Gutierrez wrote:<br>
> Hello Dan.<br>
><br>
</div><div class="Ih2E3d">> I think I already understand. You are right.<br>
><br>
> So, what do you think whether I change the logic for the other idea I<br>
> have, implementing a function which performs the tracing base in IP<br>
> address? I think that feature is not already implemented.<br>
<br>
</div>The functionality is already there. The traced user AVP doesn't have to<br>
contain a username. It can contain anything you want, including an IP<br>
address. Whatever it holds will be stored in the username column. So we<br>
could rename that to accommodate more than just user tracing.<br>
<br>
if (src_ip==<a href="http://1.2.3.4" target="_blank">1.2.3.4</a>) {<br>
# trace calls from this IP<br>
$avp(s:traced_user_avp) = $si;<br>
}<br>
<br>
--<br>
<font color="#888888">Dan<br>
</font></blockquote></div><br>