Ruchir wrote:
> I added "modparam("tm", "onreply_avp_mode", 1)" in config file. I've 
> stored the diversion header in reply route using following code.
>
>     if($hdr(Diversion)!=null)
>             {
>                 avp_delete("$avp(s:src_user_reply)");
>                 $avp(s:src_user_reply) = $hdr(Diversion);
>                 xlog("Client call forwarding to
>     $avp(s:src_user_reply)\n ");
>             }
>
>
> But I always get NUll value in $avp(s:src_user_reply) when I check in 
> script when new invite arrives.
The AVP will not be visible in a different transaction (for another 
invite). The AVP will be present only when doing acc for the transaction 
you set the AVP for.

Regards,
Bogdan
>
> On Mon, Jul 21, 2008 at 1:48 PM, Bogdan-Andrei Iancu 
> <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
>
>     Hi Ruchir,
>
>     You may try the following approach:
>
>     1) in onreply_route, if 3xx, store the info from the reply in an
>     AVP (be sure an enable onreply_avp_mode -
>     http://www.openser.org/docs/modules/1.3.x/tm.html#AEN313)
>
>     2) in failure route, if the 3xx was selected as final response,
>     use the AVP for extra accouting.
>
>     regards,
>     Bogdan
>
>     Ruchir wrote:
>
>         I'm using uac_redirect module to handle redirect and
>         accounting from openser. Redirect works fine so as cdr but I'm
>         not getting how to write redirect reason in cdr. I didn't find
>         any way to find and store redirect reason(call forward, busy,
>         no answer) in CDR. Does anyone know how to do it?
>         
> ------------------------------------------------------------------------
>
>
>
>         _______________________________________________
>         Users mailing list
>         Users@lists.openser.org <mailto:Users@lists.openser.org>
>         http://lists.openser.org/cgi-bin/mailman/listinfo/users
>          
>
>
>


_______________________________________________
Users mailing list
Users@lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users

Reply via email to