Done. Here is the link.<br><a href="http://sourceforge.net/tracker/index.php?func=detail&aid=1999353&group_id=139143&atid=743023">http://sourceforge.net/tracker/index.php?func=detail&aid=1999353&group_id=139143&atid=743023</a><br>
<br><div class="gmail_quote">On Sat, Jun 21, 2008 at 12:46 PM, Juha Heinanen <<a href="mailto:jh@tutpro.com">jh@tutpro.com</a>> 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><div></div><div class="Wj3C7c">Ruchir writes:<br>
<br>
> I have a problem. I use avp_load_radius to load caller or callee preferences<br>
> and use them. But when I do call forwarding, it will load original caller's<br>
> preferences for further processing instead of the user who has configured<br>
> call forwarding. Ideally we should load the preferences of the user who<br>
> forwarded the call as caller preferences. We can do this using avp_db_load<br>
> but I think there should be provision in avp_load_radius as well. Currently<br>
> it supports "caller", "callee" & "digest". I think it should support<br>
> parameters same as avp_db_load. Let me know your thoughts about this.<br>
<br>
</div></div>i agree with you. avp_load_radius should take a pvar param and load<br>
avps of that user.<br>
<br>
also, i don't like prefixing of avp names with caller_ or callee_,<br>
because that would mean that avp names must be strings. because there<br>
is two different service types (caller_service_type and<br>
callee_service_type), radius server can take care of the prefixing if<br>
some user wants that.<br>
<br>
submit a feature request and i'll take care of it after 1.4 comes out.<br>
<font color="#888888"><br>
-- juha<br>
</font></blockquote></div><br>