24 Jul
2009
24 Jul
'09
3:19 p.m.
Hi guys,
I was wondering what happened to this line from t_reply.h:
enum route_mode { MODE_REQUEST=1, MODE_ONREPLY, MODE_ONFAILURE };
It was there in ser 2.1.0, but not it's gone from sr, altough the tm_binds
still defines a enum route_mode* as a parameter. Maybe it was just
forgotten?
I found the solution in a k module - the route_type extern variable, just
want to make sure that this is the new right way to tell on which route a
function was called.
--
Best Regards,
Dragos Vingarzan
29 Jul
29 Jul
2:34 p.m.
On Jul 24, 2009 at 14:19, Dragos Vingarzan <dragos.vingarzan(a)gmail.com> wrote:
Hi guys,
I was wondering what happened to this line from t_reply.h:
enum route_mode { MODE_REQUEST=1, MODE_ONREPLY, MODE_ONFAILURE };
It was there in ser 2.1.0, but not it's gone from sr, altough the tm_binds
still defines a enum route_mode* as a parameter. Maybe it was just
forgotten?
It was removed doing the merge, see 1dfe92.
(http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=commit;h=1dfe92)
I found the solution in a k module - the route_type extern variable, just
want to make sure that this is the new right way to tell on which route a
function was called.
It works, but the recommended way is to use one of:
get_route_type()
or
is_route_type(type)
together with the *_ROUTE macros/flags from route.h
(e.g. if (is_route_type(FAILURE_ROUTE)) abort();)
Andrei
3:20 p.m.
I see, thanx for the answer. Fixed on my side to use the macro now.
Maybe you'd also remove the modules/tm/tm_load.h:120 line which still
references the old one, although this is undefined...
Cheers,
-Dragos
Andrei Pelinescu-Onciul wrote:
On Jul 24, 2009 at 14:19, Dragos Vingarzan
<dragos.vingarzan(a)gmail.com> wrote:
--
Best Regards,
Dragos Vingarzan
Hi guys,
I was wondering what happened to this line from t_reply.h:
enum route_mode { MODE_REQUEST=1, MODE_ONREPLY, MODE_ONFAILURE };
It was there in ser 2.1.0, but not it's gone from sr, altough the tm_binds
still defines a enum route_mode* as a parameter. Maybe it was just
forgotten?
It was removed doing the merge, see 1dfe92.
(http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=commit;h=1dfe92)
I found the solution in a k module - the
route_type extern variable, just
want to make sure that this is the new right way to tell on which route a
function was called.
It works, but the recommended way is to use one of:
get_route_type()
or
is_route_type(type)
together with the *_ROUTE macros/flags from route.h
(e.g. if (is_route_type(FAILURE_ROUTE)) abort();)
Andrei
5598
days inactive
5603
days old
2 comments
2 participants
participants (2)
-
Andrei Pelinescu-Onciul -
Dragos Vingarzan