Do you have any failure route trying new destinations?
A sip trace (e.g., ngrep output with -t on port 5060) for such case will
help to see what happens.
Also, be sure you have no t_set_fr() that overwrites the value from
parameters.
Not related, but I noticed that the comment doesn't match the
Hi,
fr_timer and fr_inv_timer do different things:
- fr_timer goes off when there's no response _at all_ to the INVITE, not
even 100 Trying.
- If you received a 100 Trying or other provisional (1xx) repy,
fr_inv_timer will apply instead.
-- Alex
--
Alex Balashov | Principal | Evariste Sys
