Hi Daniel
> the B should not do record_route() when forwards back INVITE to A.
Right, moving record_route() from the beginning of request_route{} to
the branch routes requiring this, solved this for the RR header on my
registrar node.
> Via is for routing back replies, if you remove it, node B
Hello,
On 27.11.23 14:04, Benoit Panizzon via sr-users wrote:
> Hi List
>
> Two Kamailio Nodes situation.
>
> Node A: Routing Instance.
> Node B: Registrar Instance.
>
> An invite is sent from Node A to B.
>
> Customer registered on B is 'busy' as example.
>
> B initiates Call Forwarding by
Hi Alex
> If you're having to think about how to do things that break basic SIP
> semantics, it may be time to rethink your design.
:-) We went into production far down that rabbit hole now. It would be
quite hard to pull out from that far in.
> More particularly, passing requests from A to B
If you're having to think about how to do things that break basic SIP
semantics, it may be time to rethink your design.
More particularly, passing requests from A to B back to A, when A and B are
both proxies, is problematic. It will lead to potential call loops if the
request should find
