The loose_route() is marking local Route headers for deletion, so after
the msg_apply_changes() you don't see them. It should work fine if you
do not need to inspect them afterwards, but if you are not sure, it is
recommended do it before.
Cheers,
Daniel
On 02.06.20 09:49, George Diamantopoulos
Daniel, that worked instantly, thank you!
Care to elaborate on how msg_apply_changes() interferes with loose_route? I
also remember msg_apply_changes() complaining if called after
record_route(), is it related?
On Mon, 1 Jun 2020 at 21:24, Daniel-Constantin Mierla
wrote:
> Hello,
>
> use
George,
I understand. Have you considered begrudgingly adding a lightweight B2BUA such
as SEMS in the middle?
I understand it greatly increases the operational complexity and moving parts
of your setup, to say nothing of infrastructural costs. I am all for using
Kamailio alone to solve
Hello Alex,
Thank you for your reply. Well, I'm interfacing with several PSTN
operators, and some of their networks' SIP endpoints (or other obscure IMS
entity there) are very picky in that if they don't like the capabilities
you serve for telephone-event (which is if they don't match theirs),
George,
It may be orthogonal to the answer that you seek, but I’m going to ask anyway:
what is the overall motive underlying your SDP manipulation?
It seems to me that one should reason backward from that root cause. The kind
of SDP manipulation you are doing is seldom necessary in ordinarily
