Hello,
quick note to remind that today I am going to release Kamailio 5.3.4 out
of stable branch 5.3. As usual, until the announcement is out, do not
push commits to branch 5.3, unless you notify via sr-dev, irc or matrix
channel and get the ack.
Cheers,
Daniel
On 30.04.20 08:33, Daniel-Constant
### Description
With rtpengine module play_media function it is possible to play media to one
of the endpoints(Kamailio is normal proxy) but I like to use
Kamailio+rtpengine as an end point playing music for caller(simple media
server).
### Expected behavior
Possible to use Kamailio+rtpen
I finally isolated the problem here. I was trying to deal with some NAT
nonsense involving dropped Contact headers from my SIP trunk provider and had a
block like this in the WITHINDLG route:
```
if (uri==myself && $ru=~";alias=10") {
# Deal with BS on ACKs
among others, we have:
> enable_tls=yes
> tcp_accept_haproxy=yes
> tcp_connection_match=1
> tcp_accept_unique=0
The issue only happens when forwarding requests. Running `kamctl` in AWS
Fargate is not a straightforward task but I will give it a try.
--
You are receiving this because you are subs
What global parameters did you set for kamailio?
If the issue is reproducible, can you list the tcp connections with:
```
kamctl rpc core.tcp_list
```
and see if what is listed there matches the connection expected to be used?
Also, I understand this happens when forwarding requests, not for ro
When an INVITE comes in, we instruct Kamailio to query a http service to know
which clients should receive the INVITE message. If multiple of these
"receiver"-clients are running on the same machine (same IP address, but
different source port), we see that Kamailio forwards multiple INVITE to on
Pre-Submission Checklist