[OpenSER-Users] Problem getting redirect reason in uac_redirect
Ruchir
ruchir.lists at gmail.com
Fri Jul 18 15:40:40 CEST 2008
But after forward, new invite will be generated so avp will be lost, isn't
it?
On Fri, Jul 18, 2008 at 7:00 PM, kokoska rokoska <kokoska.rokoska at post.cz>
wrote:
>
>
>
> Ruchir napsal(a):
>
>> This is for explicit call forwarding. I'm testing call forwarding from
>> linksys pap2 call forward features which generates "302 moved temporarily"
>> message.
>>
>>
> I too :-)
> May be I don't understand what you are looking for...
>
> From my point of view it is simple:
> 1. If IS present Diversion header in 302 reply, than push it to avp
> 2. If Diversion header IS NOT present, than use "unknow" reason - like in
> SS7...
>
> Best regards,
>
> kokoska.rokoska
>
>
> On Fri, Jul 18, 2008 at 6:20 PM, kokoska rokoska <kokoska.rokoska at post.cz<mailto:
>> kokoska.rokoska at post.cz>> wrote:
>>
>>
>>
>>
>> Ruchir napsal(a):
>> > 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?
>> >
>> >
>>
>>
>> I'm using something like this (shortened):
>>
>> in config:
>>
>> modparam("acc",
>> "multi_leg_info", "src_leg=$avp(i:901);dst_leg=$avp(i:902)")
>>
>>
>> in routing script:
>>
>> $avp(s:acc_state) = "cfu";
>> avp_printf("$avp(i:901)", "$avp(s:caller_uuid)|$avp(s:acc_state)");
>>
>>
>> Works very well :-)
>>
>> Hope this helps, best regards,
>>
>> kokoska.rokoska
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.openser.org <mailto:Users at lists.openser.org>
>> http://lists.openser.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20080718/0929e2f3/attachment.htm>
More information about the sr-users
mailing list