hello,

In failure_route, how can I know the difference between 408s.

408 is hit by the fr_inv_timer and fr_timer. In the first case, ok, callee does'nt answer. In the second case, it can be a gateway error and I have to forward the call to another gateway.

How can I know wich timer has been hit?

Olivier

Hi Juha,

I am talking about calls going thru gateways in any case. How can check wich timer has been hit when I get in the failure route. I user doesn't answer for any reason, I get a 408 in failure route, what if the gateway in between had a problem and didn't anwer at all.

Hope it's more clear like that :)

Olivier

Juha Heinanen a écrit :

olivier taylor writes:

...

In failure_route, how can I know the difference between 408s.

408 is hit by the fr_inv_timer and fr_timer. In the first case, ok, callee does'nt answer. In the second case, it can be a gateway error and I have to forward the call to another gateway.

How can I know wich timer has been hit?

i'm not sure if i understood correctly your question, but you can define a separate failure route for your gw failures or test in your single failure route, if the call was going to a gw, for example, by setting a flag before t_relay.

-- juha

2009/6/22 olivier taylor olivier.taylor@gmail.com:

Hi Juha,

I am talking about calls going thru gateways in any case. How can check wich timer has been hit when I get in the failure route. I user doesn't answer for any reason, I get a 408 in failure route, what if the gateway in between had a problem and didn't anwer at all.

Hope it's more clear like that :)

You can use t_local_replied() to detect if the reply was generated locally or externally.

That fixed it thanks.. I was using utils because that is what is used in the Docs examples. Thanks you for your help.

Thanks, Carlos A. Alvarez ________________________________________ From: Henning Westerholt [henning.westerholt@1und1.de] Sent: Monday, June 22, 2009 5:05 AM To: users@lists.kamailio.org Cc: Carlos A. Alvarez Subject: Re: [Kamailio-Users] Siputils error

On Freitag, 19. Juni 2009, Carlos A. Alvarez wrote:

I keep getting this error when I try to setup ring_timeout ERROR:core:set_mod_param_regex: parameter <ring_timeout> not found in module <utils>

Hello Carlos,

this parameter don't belong to the utils module, it part of siputils.

I tried setting the modparam for siputils as well to no avail.

Hm, on my system it works:

henning@ca:~/projects/openser/branches/1.5/test$ grep "ring_*" 2.cfg modparam("siputils", "ring_timeout", 1) henning@ca:~/projects/openser/branches/1.5/test$ ./2.sh; echo $? 0

(starts kamailio). I checked the docs, indeed the parameter is given wrong here. It uses quotes, perhaps you can check in your cfg and try the setting above? I'll fix this in the docs.

Also the command options is recorded wrong in the 1.5.1 documentation:

modparam("options", "options_accept", "application/*") <-according to docs

Looking through the source I found out that the correct command is

modparam("siputils", "options_accept", "application/*")

This is also an error, i'll fix it. Thanks for the report.

Henning