Re: [OpenSIPS-Users] on routing invite's in a trunk context.

2023-10-06 Thread Johan De Clercq
It’s a very non rfc scenario. Source ip and via are the ip of a loadbalancer that I need to skip …. ;-(. The contact does have the correct ip. Anyway, you gave me a good hint. I will add the contact ip as record route and see what that gives. Verzonden vanuit Outlook voor

Re: [OpenSIPS-Users] on routing invite's in a trunk context.

2023-10-06 Thread Ben Newlin
Johan, This is actually a pretty standard SIP flow that we use all the time. I recommend this article [1] for an overview of how routing works in SIP. In short, the Contact and Record-Route headers are only used for routing of requests not responses, and mostly only sequential requests which

[OpenSIPS-Users] on routing invite's in a trunk context.

2023-10-06 Thread johan
This is a general question on routing (to be honest: it is a really strange case). A has a sip trunk to B (opensips), B has a sip trunk to C A sends an invite to B with contact header A'   and record-route header to A'' B string the record_route header , calls topology hiding and droutes

Re: [OpenSIPS-Users] rtpengine and multiple instances

2023-10-06 Thread olle
Thanks, sounds like it's time to upgrade  BR/OLle -Original Message- From: Users On Behalf Of Razvan Crainea Sent: den 6 oktober 2023 13:13 To: users@lists.opensips.org Subject: Re: [OpenSIPS-Users] rtpengine and multiple instances Hi, Olle! Yes, the offer should be taken by one

Re: [OpenSIPS-Users] rtpengine and multiple instances

2023-10-06 Thread Răzvan Crainea
Hi, Olle! Yes, the offer should be taken by one single node. How it internally works is we compute a hash of the callid of the call and based on that hash, and we consider that hash a random value to pick one available server. This means that as long as the available list does not change,

[OpenSIPS-Users] rtpengine and multiple instances

2023-10-06 Thread olle
Hi we have seen an issue with rtpengine module in 2.4. We ran a setup with two opensips edge proxies each having a local rtpengine running on it. When we start using the rtpengines in a cluster, we saw that some commands perhaps in 1-2% of the calls are send to the wrong rtpengine: