13 Jan
2011
13 Jan
'11
6:32 p.m.
Hi!
I would like to use probing implementation in dispatcher module to keep
track of the state of the gateways, but I want to choosing a gateway
manually in the config.
For example I defined a dispatcher set with 6 entries. Then in .cfg I
want to retrieve a certain entry from the set (by index) and its state
(active, inactive, probing).
AFAIS there is currently now way to do this. Does anybody knows a
workaround or maybe another way for manual dispatching but automatic
probing?
Thanks
Klaus
13 Jan
13 Jan
7:11 p.m.
Am 13.01.2011 17:32, schrieb Klaus Darilion:
Hi!
I would like to use probing implementation in dispatcher module to keep
track of the state of the gateways, but I want to choosing a gateway
manually in the config.
For example I defined a dispatcher set with 6 entries. Then in .cfg I
want to retrieve a certain entry from the set (by index) and its state
(active, inactive, probing).
AFAIS there is currently now way to do this. Does anybody knows a
workaround or maybe another way for manual dispatching but automatic
probing?
Just as an idea - do you think that will work?
- use htable for storage of the GW-list and their state
- use rtimer to execute 'probe' route every few seconds
- in probe route iterate over GW-list and send OPTIONS requests (with
short timeout) to the GWs
- use response_route/failure_route to get the OPTIONS response and set
the GW state accordingly
- In normal routing logic then I could use the htable to retrive the GW
address and the state.
Is it possible to get the response status (200 OK, internally generated
408) of local generated transactions in response route? Is it possible
to activate a failure route for local generated transactions?
Thanks
Klaus
11:49 p.m.
Klaus Darilion wrote:
Just as an idea - do you think that will work?
- use htable for storage of the GW-list and their state
- use rtimer to execute 'probe' route every few seconds
- in probe route iterate over GW-list and send OPTIONS requests (with
short timeout) to the GWs
- use response_route/failure_route to get the OPTIONS response and set
the GW state accordingly
- In normal routing logic then I could use the htable to retrive the GW
address and the state.
Is it possible to get the response status (200 OK, internally generated
408) of local generated transactions in response route? Is it possible
to activate a failure route for local generated transactions?
The problem is, that the a failed transaction without any response
(local timeout) can not be detected from script. Local generated 408 of
local generated request do not enter any reply route nor the failure
route :-(
Does anyone have another idea?
thanks
klaus
5068
days inactive
5068
days old
2 comments
1 participants
participants (1)
-
Klaus Darilion