Re: [SR-Users] dialog expire, acc

2014-03-28 Thread Alex Balashov
Sweet! On 28 March 2014 15:24:10 GMT-04:00, Kelvin Chua wrote: >It worked! perfect > >Kelvin Chua > > >On Fri, Mar 28, 2014 at 1:34 AM, Alex Balashov >wrote: > >> On 03/28/2014 04:32 AM, Kelvin Chua wrote: >> >> I tried, AVPs, they are not accessible on the >>> event_route[tm:local-request] >>>

Re: [SR-Users] dialog expire, acc

2014-03-28 Thread Kelvin Chua
It worked! perfect Kelvin Chua On Fri, Mar 28, 2014 at 1:34 AM, Alex Balashov wrote: > On 03/28/2014 04:32 AM, Kelvin Chua wrote: > > I tried, AVPs, they are not accessible on the >> event_route[tm:local-request] >> > > That's because AVPs are only transaction-persistent, not dialog-persistent

Re: [SR-Users] dialog expire, acc

2014-03-28 Thread Alex Balashov
On 03/28/2014 04:32 AM, Kelvin Chua wrote: I tried, AVPs, they are not accessible on the event_route[tm:local-request] That's because AVPs are only transaction-persistent, not dialog-persistent. however, your idea on $dlg_vars was spot on, why didn't i think of that. Thanks a bunch! Well..

Re: [SR-Users] dialog expire, acc

2014-03-28 Thread Kelvin Chua
Hi Alex, yes, locally generated BYEs I was trying to avoid the unique constraint approach as it is not very elegant. I tried, AVPs, they are not accessible on the event_route[tm:local-request] however, your idea on $dlg_vars was spot on, why didn't i think of that. Thanks a bunch! Kelvin Chua

Re: [SR-Users] dialog expire, acc

2014-03-28 Thread Alex Balashov
Oh, you were talking about the BYEs that are internally generated by 'dialog'. In that case, ignore my advice; it's not applicable, because locally generated BYEs will not have the RR header and this won't work. In those situations, in my personal opinion, your best bet is to use a database-si

Re: [SR-Users] dialog expire, acc

2014-03-28 Thread Alex Balashov
On 03/28/2014 03:53 AM, Kelvin Chua wrote: I have a situation here, when a dialog expires, it sends a BYE to both call legs and this does not generate an entry on acc table. however, when i use acc_db_request() on event_route[tm:local-request], i get 2 entries on acc, 1 for the downstream, and

[SR-Users] dialog expire, acc

2014-03-28 Thread Kelvin Chua
I have a situation here, when a dialog expires, it sends a BYE to both call legs and this does not generate an entry on acc table. however, when i use acc_db_request() on event_route[tm:local-request], i get 2 entries on acc, 1 for the downstream, and 1 for the upstream. is there a way of handli