20 Jan
2025
20 Jan
'25
10:05 p.m.
Hi Ben
Are you intending to use `t_next_contact_flow()`
rather than `t_next_contact()`? There's not enough data here to know what your
contacts look like. The definition of `t_next_contact_flow()` is:
Indeed I did not at all understand the +sip.instance part
and somehow from the example I understood that I had to use
t_branch_failure.
I changed my config to use a 'normal' failure route and call
t_next_contact() within that failure route. This now behaves as
expected!
Thanks a lot for hinting me the right direction!
Mit freundlichen Grüssen
-Benoît Panizzon-
--
I m p r o W a r e A G - Leiter Commerce Kunden
______________________________________________________
Zurlindenstrasse 29 Tel +41 61 826 93 00
CH-4133 Pratteln Fax +41 61 826 93 01
Schweiz Web http://www.imp.ch
______________________________________________________
Function adds a new branch to the request that
includes the first contact from contact_flows_avp that matches the +sip.instance value of
the flow that has failed.
If your contacts have separate +sip.instance values, then it would be expected that this
would fail. Unless you know this to be the case use `t_next_contact()` in a failure route
(as opposed to a branch failure route).