QoS Media Stats are not appearing on Homer with Kamailio w/ RTPEngine #697
Description
Hi,
I have an issue where I'm trying to implement sending RTCP stats over HEP packets from RTPEngine (w/ Kamailio). I cannot see the QoS tab when I'm going inside a call ladder.
The entire SIP ladder is working as expected, I can see the entire SIP ladders that are being collected from all the SIP components (as Kamailio w/ RTPEngine are not the only one in my signaling & media flow) based on a correlation SIP header which I am using, called: "X-Orig-Call-ID".
Deployment:
- Using AWS EKS, and all SIP components are in fact EKS pods.
- Using the latest Docker image of the Heplify server and web app.
- Using Kamailio 5.8.1
- Using RTPEngine 13.4.1.1
on Kamailio & RTPEngine side (2 components which are residing on the same pod) I'm using TCP/9061 to send the traffic to the Homer server. Not UDP.
The way I tested it is by opening a "tcpdump" on that pod that has the Kamailio & RTPEngine on it, and I can clearly see there's HEP/RTCP packets flowing for the calls. Due to using TCP, as I'm getting TCP ACK back from Homer, I can understand that from connectivity perspective the packet reached to Homer just fine.
Attaching you a packet capture from that pod:
kamailio-rtpengine-hep.zip
The IPs you'll see there:
- 10.10.127.251 - Is the Kamailio w/ RTPEngine pod.
- 172.20.81.129 - Is the Kubernetes service ClusterIP endpoint that is eventually relaying the traffic to the Homer server pod IP address.
- 10.10.83.132 - Is the direct IP address of the Homer server - which is somehow being discovered by the RTPEngine, instead of sending it to the Kubernetes ClusterIP endpoint, but still the traffic is being sent and acked.
There are several packets of HTP3/JSON/RTCP sent by RTPEngine to Homer, like packets: 364, 366, 368, 370 and 372
But that doesn't seem like it is sending them after the call has been ended, but around the answering of that call.
Once I'm ending the call, I do not see such packets being sent by the RTPEngine at all.
Or else I'm not sure how it should work, but common sense that I should see the RTCP flowing to Homer when call is ended.
I didn't see any additional & unique configurations required on the RTPEngine for this matter besides what I've already configured, for example:
homer={{HOMER_IP}}:9061 homer-protocol=tcp homer-id={{some-random-id}}
Please let me know if you need anything else. I would love to get some assistance on this matter.
Thanks! :)
Slavik