15 Aug
2018
15 Aug
'18
1:51 a.m.
On Tue, Aug 14, 2018 at 11:40:09PM +0200, M S wrote:
It would be good if you can provide the full sip trace
that includes the
initial INVITE processing of both call legs.
That's not going to be (easily) possible in this case, due to one leg
being TLS.
Per SIP v2.0 RFCs (3261, 3665 & 6141), when callee
needs to send a
sequential request e.g. a re-invite, it should use the Contact header it
received in initial INVITE as RURI. Since the RURI and top most Route
header(s), all point to kamailio itself, so kamailio sees it as strict
routing rather then loose routing, and as a result loop occurs.
Yes. My question was about the inconsistency between the apparent RURI
and the message attributes logged.
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/