20 Aug
2006
20 Aug
'06
4:52 p.m.
Is there a reason why the avp_check() function cannot be used in the
ONREPLY_ROUTE, while it can be used for example in the FAILURE_ROUTE?
Using OpenSER 1.1.0 from CVS of a few days ago.
Thanks.
--
___________________________________________________
__
|- giannici(a)neomedia.it
|ederico Giannici http://www.neomedia.it
___________________________________________________
21 Aug
21 Aug
10:42 a.m.
Good question. I find this restriction very annoying, too.
Sometimes you can get around by checking the things in the forward route
and using setflag() / resetflag() / isflagset() .
Greetings, Gerry.
Federico Giannici schrieb:
Is there a reason why the avp_check() function cannot
be used in the
ONREPLY_ROUTE, while it can be used for example in the FAILURE_ROUTE?
Using OpenSER 1.1.0 from CVS of a few days ago.
Thanks.
10:55 a.m.
Hello,
On 08/21/06 11:42, Gerry wrote:
Good question. I find this restriction very annoying, too.
Sometimes you can get around by checking the things in the forward
route and using setflag() / resetflag() / isflagset() .
Greetings, Gerry.
Federico Giannici schrieb:
> Is there a reason why the avp_check() function cannot be used in the
> ONREPLY_ROUTE, while it can be used for example in the FAILURE_ROUTE?
>
> Using OpenSER 1.1.0 from CVS of a few days ago.
this restriction comes because
the replies are not processed under
mutex, therefore the access to avps is not synchronized. We look for a
solution to this issue, since it affects other features we want to have.
Cheers,
Daniel
Thanks.
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
12:56 p.m.
Daniel-Constantin Mierla wrote:
Hello,
On 08/21/06 11:42, Gerry wrote:
So, it shouldn't be usable in the FAILURE_ROUTEs too.
Or not?
Bye.
--
___________________________________________________
__
|- giannici(a)neomedia.it
|ederico Giannici http://www.neomedia.it
___________________________________________________
Good question. I find this restriction very annoying, too.
Sometimes you can get around by checking the things in the forward
route and using setflag() / resetflag() / isflagset() .
Greetings, Gerry.
Federico Giannici schrieb:
> Is there a reason why the avp_check() function cannot be used in the
> ONREPLY_ROUTE, while it can be used for example in the FAILURE_ROUTE?
>
> Using OpenSER 1.1.0 from CVS of a few days ago.
this restriction comes because
the replies are not processed under
mutex, therefore the access to avps is not synchronized. We look for a
solution to this issue, since it affects other features we want to have. 
22 Aug
22 Aug
11:48 a.m.
Federico Giannici wrote:
Daniel-Constantin Mierla wrote:
from failure route is safe to use since the route is protected by a lock
from TM - a transaction has only one final reply, but have several
provisional replies that can be processed in parallel.
regards,
bogdan
Hello,
On 08/21/06 11:42, Gerry wrote:
So, it shouldn't be usable in the FAILURE_ROUTEs too.
Or not?
Good question. I find this restriction very annoying, too.
Sometimes you can get around by checking the things in the forward
route and using setflag() / resetflag() / isflagset() .
Greetings, Gerry.
Federico Giannici schrieb:
this restriction comes
because the replies are not processed under
mutex, therefore the access to avps is not synchronized. We look for
a solution to this issue, since it affects other features we want to
have. Is there a reason why the avp_check() function
cannot be used in
the ONREPLY_ROUTE, while it can be used for example in the
FAILURE_ROUTE?
Using OpenSER 1.1.0 from CVS of a few days ago.
6676
days inactive
6678
days old
4 comments
4 participants
participants (4)
-
Bogdan-Andrei Iancu -
Daniel-Constantin Mierla -
Federico Giannici -
Gerry