looking at the trace, it seems to me that the 407 is not sent
by Kamailio but by the FS1 server ("User-Agent:
IMX" in the 407, as for the 1st 407 sent by FS2), and that you
are probably missing in the trace the messages between
Kamailio and FS1.
This shouldn't be the case as the tcpdump was executed on that
server itself, but it seems plausible (perhaps lo -vs- ethX).
-
store the custom header when receiving the 302 and use it to
set $du upon receiving the 2nd INVITE
For
the latter you can have several solutions, I suggest you to
have a a look at the htable module. For example you could
use it to store the key USERID::CALLID with the value of
your custom header and retrieve it when you receive the
authenticated INVITE from the client. Something like
sht(TABLE_NAME=>$fU::$ci)
= $avp(imx-redirect);
to
store it, and then
$avp(imx-redirect)
= sht(TABLE_NAME=>$fU::$ci);
This is very useful, thank you. I'll investigate this option.