27 May
2010
27 May
'10
6:09 p.m.
On Thursday 27 May 2010, JR Richardson wrote:
Hi JR,
from the logs:
INFO:carrierroute:cr_do_route: rewrite_uri_recursor doesn't complete, uri 65,
carrier 1, domain 2
this means that there was an error during the invocation of the cr_route in
the failure_route[2]. Can you check if you've a rule with domain 2 in your
carrierroute table?
And you probably also want to use revert_uri() and append_branch(); in the
failure_route before respectivly after the new cr_route, otherwise you'll
probably run in to problems as well. I just noticed that there is an error in
the first example in the cr docs, i'll fix it now. The second example uses
this two commands.
Regards,
Henning
i assume
according your description that the GW in question don't send a
provisional response. Then the tm module should generate a internal 408
after fr_timer interval which you could then catch in a failure_route. Do
you armed the appropriate failure_route in your cfg?
Yes, the gateway is totally off-line so no response comes back. I do
have failure_route in the config. This is related to another active
post from me "Carrierroute failover domain not working" so I'm sure
this is a redundant post, but your input is appreciated.
The pastebin has my kamailio.cfg, the kamailio debug trace and the
error received by sipp and the ngrep capture.
http://pastebin.com/VQziKYjE